System for management of Internet telephony equipment deployed behind firewalls

• US 20050105508A1
• Filed: 11/14/2003
• Published: 05/19/2005
• Est. Priority Date: 11/14/2003
• Status: Abandoned Application

• Current Assignee: Innomedia Pte Ltd
• Original Assignee: Innomedia Pte Ltd
• Inventors: Saha, Partha
• Application Number:
  US10/713,481
• Publication Number:
  US 20050105508A1
• Time in Patent Office: Days
• US Class Current: 370/352
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/044 comprising hierarchical management structures
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/25 of the same type
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Abstract

A sub-manager interfaces between a traditional SNMP network management system (NMS) a plurality of clients, each of which may be served by a network address and port translation firewall. The sub-manager operates a master management information base and receives master network management request messages from the network management server. The master network management request message includes at least one master object identifier which comprises a client identifier which identifies a particular one of the clients and a variable portion that identifies a variable value within a client management information base. The sub-manager, in response, generates one or more client network management request messages to identified clients over TCP/IP connections through the firewall. The client network management request message includes a client object identifier that identifies the variable within the client management information base.

Claims

1. A sub-manager (20) for interfacing between a network management system (22) and a plurality of clients (18), each of such clients (18) being served by a firewall (16), the sub-manager (20) comprising:

a network management agent (25) for exchanging master network management messages (190) with the network management system (22);

a connections module (24) for establishing a network connection (45) with each of the plurality of clients (18);

a message handling module (26) for;

receiving a master network management request message (170) from the network management system (22), the master network management request message (170) including a plurality of master object identifiers (182), each master object identifier (182) comprising a client identifier (46) that identifies a particular one of the clients (18) and a variable portion (210) that identifies a variable value (44) within a client management information base (34);

generating at least one client network management request message (172), each client network management request message (172) including a client object identifier (188) that identifies the variable value (44) within the client management information base (34);

providing each client network management request message (172) to the particular one of the clients (18) identified by the client identifier (46) over the network connection (45) established with such particular one of the clients (18);

receiving a client response message (206) from each of the particular one of the clients (18) to which a client network management message (172) was provided, each client response message (206) including the client object identifier (188) and the variable value (44);

aggregating each client response message (206) to generate a master response message (192), the master response message (192) including the plurality of master object identifiers (182) and each master object identifier (182) comprising the client identifier (46) and the variable value received in the client response message (206); and

providing the master response message (192) to the network management system (22).

2. The sub-manager (20) of claim 1, wherein the variable portion (210) of the master object identifier (182) is the client object identifier (188).

3. The sub-manager (20) of claim 1, wherein:

each connection (45) is a TCP/IP connection that is established with a client (18), through the firewall (16) serving such client (18) in response to receiving a connection request initiating by such client (18);

the connections module (24) further records, in an active connections table (28), for each connection (45), a client connection identifier (48) in association with the client identifier (46) identifying the client (18) that initiated the connection (45); and

a device state machine provides the client network management request message (172) to the particular one of the clients (18) by providing the client network management request (172) over the connection (45) that associates with the particular one of the clients (18) in the active connections table (28).

4. The sub-manager (20) of claim 3, wherein the client connection identifier (48) is a source IP address (50) and a source port number (52) obtained from a TCP/IP frame initiated by the client (18) with which the connection (45) is established.

5. The sub-manager (20) of claim 1 wherein the device state machine further provides for:

periodically receiving a heart beat message (113) from the client (18) over the connection (45);

each heart beat message (113) including the client identifier (46) and a time interval (114) between the heart beat message (113) and a subsequent heart beat message (113);

updating the client connection identifier (48) in the active connection table (28) if the source IP address (50) or the source port number (52) obtained from the heart beat message (113) differs from that of a previous heart beat message (113);

providing a heart beat acknowledgement message (112) to the client (18) over the connection (45); and

determining that the connection (45) is inactive if a time period in excess of the time interval (114) elapses during which a subsequent heart beat message (113) has not been received.

6. The sub-manager (20) of claim 5, wherein the master response message (192) includes an indication that the a value (44) does not exist if the value (44) is associated with a master object identifier (182) that includes a client identifier (46) associated with a client 18 with which the connection (45) is inactive.

7. The sub-manager (20) of claim 1, wherein:

the master network management request message (172) comprises at least two master object identifiers (182), each master object identifier (182) comprising a client identifier (46) that is unique from the client identifier (46) of at least one other master object identifier (182);

8. The sub-manager (20) of claim 1, wherein the message handling module 26 further provides for:

receiving an asynchronous client Trap message (220) initiated by client (18) over the connection (45) established with the client (18), the asynchronous client Trap message (220) including a client object identifier (188) and a variable value (44) associated with the client object identifier (188);

identifying the client (18) that initiated the asynchronous client Trap message (220); and

generating an asynchronous master Trap message (194) and providing the asynchronous master Trap message (194) to the network management system (22), the asynchronous master Trap message (194) including the value (44) and a master object identifier (182), the master object identifier (182) including a client identifier (46) identifying the client (18) that initiated the asynchronous client Trap message (22) and a variable portion (210) identifying the variable value (44).

9. The sub-manager (20) of claim 8, wherein the variable portion (210) of the master object identifier (182) is the client object identifier (188).

10. A method of interfacing between a network management system (22) and a plurality of clients (18), each of such clients (18) being served by a firewall (16), the method comprising:

establishing a connection (45) with each of the plurality of clients (18);

receiving a master network management request message (170) from the network management system (22), the master network management request message (170) including a plurality of master object identifiers (182), each master object identifier (182) comprising a client identifier (46) that identifies a particular one of the clients (18) and a variable portion (210) that associates with a variable value (44) within a client management information base (34);

generating at least one client network management request message (172), the client network management request message (172) including a client object identifier (188) that identifies the variable value (44) within the client management information base (34);

providing each client network management request message (172) to the particular one of the clients (18) identified by the client identifier (46) over the network connection (45) established with such particular one of the clients (18);

receiving a client response message (206) from each of the particular one of the clients (18) to which a client network management message (172) was provided, each client response message (206) including the client object identifier (188) and the variable (44);

aggregating each client response message (206) to generate master response message (192), the master response message (192) including the plurality of master object identifiers (182) and each master object identifier (182) comprising the client identifier (46) and the variable value (44) received in the client response message; and

providing the master response message to the network management system (22).

11. The method of claim 10, wherein the variable portion (210) of the master object identifier (182) is the client object identifier (188).

12. The method of claim 10, wherein:

each connection (45) is a TCP/IP connection established with a client (18), through the firewall (16) serving such client (18), in response to receiving a connection request initiating by such client (18);

the method further comprises recording in an active connections table (28), for each connection (45) established, a client connection identifier (48) in association with the client identifier (46) identifying the client (18) that initiated the connection (45); and

the step of providing each client network management request message (172) to the particular one of the clients (18) comprises providing each client network management request (172) over the connection (45) that associates with the particular one of the clients (18) in the active connections table (28).

13. The method of claim 12, wherein the client connection identifier (48) is a source IP address (50) and a source port number (52) obtained from a TCP/IP frame initiated by the client (18) with which the connection (45) is established.

14. The method of claim 10 further comprising:

periodically receiving a heart beat message (113) from the client (18) over the connection (45);

each heart beat message (113) including the client identifier (46) and a time interval (114) between the heart beat message (113) and a subsequent heart beat message (113);

updating the client connection identifier (48) in the active connection table (28) if the source IP address (50) or the source port number (52) obtained from the heart beat message (113) differs from that of a previous heart beat message (113);

providing a heart beat acknowledgement message (112) to the client (18) over the connection (45); and

determining that the connection (45) is inactive if a time period in excess of the time interval (114) elapses during which a subsequent heart beat message (113) has not been received.

15. The method of claim 14, wherein the master response message (192) includes an indication that the value (44) is unavailable if an open connection (45) does not exist with the particular on of the clients (18).

16. The sub-manager (20) of claim 10, wherein:

the master network management request message (172) comprises at least two master object identifiers (182), each master object identifier (182) comprising a client identifier (46) that is unique from the client identifier (46) of at least one other master object identifier (182);

17. The method of claim 10, further comprising:

receiving an asynchronous client Trap message (220) from a client (18) over the connection (45) established with the client (18), the asynchronous client Trap message (220) including a client object identifier (188) and a variable value (44) associated with the client object identifier (188);

identifying the client (18) that initiated the asynchronous client Trap message (220);

generating an asynchronous master Trap message (194) and providing the asynchronous master Trap message (194) to the network management system (22), the asynchronous master Trap message (194) including the variable value (44) and a master object identifier (182), the master object identifier (182) including a client identifier (46) identifying the client (18) that initiated the asynchronous client Trap message (22) and a variable portion (210) identifying the variable value (44).

18. the method of claim 17, wherein the variable portion (210) of the master object identifier (182) is the client object identifier (188).