Out-of-band network management channels

• US 20020116485A1
• Filed: 02/21/2001
• Published: 08/22/2002
• Est. Priority Date: 02/21/2001
• Status: Abandoned Application

• Current Assignee: Ciena Corporation
• Original Assignee: Equipe Communications Corporation
• Inventors: Perry, James R., Black, Darryl, Snow, Kevin D.
• Application Number:
  US09/789,665
• Publication Number:
  US 20020116485A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 41/024 using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/085 Retrieval of network configuration; Tracking network configuration history
• CPC Class Codes: H04L 41/0863 by rolling back to previous configuration versions
• CPC Class Codes: H04L 41/0866 Checking the configuration
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 41/344 Out-of-band transfers
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The present invention provides a method and apparatus for improving management and network availability by providing out-of-band management channels between network/element management system (NMS) clients and servers. High priority client requests and server notifications may be sent over the out-of-band management channels to ensure fast response times. In addition, periodic roll calls between NMS clients and NMS servers may be executed over the out-of-band management channels to allow for quick discovery of any disconnects and reclaiming associated client resources. Further, periodic roll calls may be conducted between the NMS servers and the network devices to which they are connected, and if a server discovers that a network device has gone down, it may send a high priority notification to appropriate NMS clients over the out-of-band management channels to ensure a fast response by the clients. Sending high priority messages over out-of-band management channels maximizes client/server management availability and, hence, network availability.

Claims

1. A management system for a telecommunications network, comprising:

a server program capable of connecting to at least one network device in the telecommunications network; and

a client program capable of connecting to the server program and capable of registering a high priority application programming interface (API) with the server program, wherein the server program is capable of sending messages to the client program through the high priority API.

2. The management system of claim 1, wherein registering a high priority API with the server program comprises sending the server program a high priority call back address.

3. The management system of claim 1, wherein sending messages to the client program through the high priority API comprises sending high priority messages to the client program through the high priority API.

4. The management system of claim 1, wherein sending messages to the client program through the high priority API comprises sending roll call messages to the client program through the high priority API.

5. The management system of claim 1, wherein registering a high priority API with the server program comprises establishing an out-of-band management channel.

6. The management system of claim 1, wherein the high priority API is a first high priority API and wherein the client program is further capable of registering a second high priority API with the server program and wherein the server program is capable of sending messages to the client program through the second high priority API.

7. The management system of claim 6, wherein the first and second high priority APIs have different priority levels.

8. The management system of claim 1, wherein the high priority API is a first high priority API and wherein the server program is further capable of registering a second high priority API with the client program, wherein the client program is capable of sending messages to the server program through the second high priority API.

9. The management system of claim 8, wherein registering a second high priority API with the client program comprises sending the client program a high priority call back address.

10. The management system of claim 8, wherein sending messages to the server program through the second high priority API comprises sending high priority messages to the server program through the second high priority API.

11. The management system of claim 8, wherein sending messages to the server program through the second high priority API comprises sending roll call messages to the server program through the second high priority API.

12. The management system of claim 8, wherein registering a second high priority API with the client program comprises establishing an out-of-band management channel.

13. The management system of claim 8, wherein the client program is further capable of registering a third high priority API with the server program and wherein the server program is capable of sending messages to the client program through the third high priority API and wherein the server program is further capable of registering a fourth high priority API with the client program and wherein the client program is capable of sending messages to the server program through the fourth high priority API.

14. The management system of claim 1, wherein the server program is a first server program and wherein the system further comprises:

a second server program capable of connecting to at least one network device in the telecommunications network, wherein the client program is capable of connecting to the second server program and capable of registering the high priority API with the second server program and wherein the second server program is capable of sending messages to the client program through the high priority API.

15. The management system of claim 1, wherein the server program is a first server program and the high priority API is a first high priority API and wherein the system further comprises:

a second server program capable of connecting to at least one network device in the telecommunications network, wherein the client program is capable of connecting to the second server program and capable of registering a second high priority API with the second server program and wherein the second server program is capable of sending messages to the client program through the second high priority API.

17. The management system of claim 16, wherein registering a high priority API with the client program comprises sending the client program a high priority call back address.

18. The management system of claim 16, wherein sending messages to the server program through the high priority API comprises sending high priority messages to the server program through the high priority API.

19. The management system of claim 16, wherein sending messages to the server program through the high priority API comprises sending roll call messages to the server program through the high priority APT.

20. The management system of claim 16, wherein registering a high priority API with the client program comprises establishing an out-of-band management channel.

21. The management system of claim 16, wherein the high priority API is a first high priority API and wherein the server program is further capable of registering a second high priority API with the client program and wherein the client program is capable of sending messages to the server program through the second high priority API.

22. The management system of claim 21, wherein the first and second high priority API have different priority levels.

23. The management system of claim 16, wherein the client program is a first client program and wherein the system further comprises:

a second client program capable of connecting to the server program, wherein the server program is capable of registering the high priority API with the second client program and wherein the second client program is capable of sending messages to the server program through the high priority API.

24. The management system of claim 16, wherein the client program is a first client program and the high priority API is a first high priority API and wherein the system further comprises:

a second client program capable of connecting to the server program, wherein the server program is capable of registering a second high priority API with the second client program and wherein the second client program is capable of sending messages to the server program through the second high priority API.

26. The management system of claim 25, wherein the client program is further capable of registering a third high priority API with the server program and the server program is capable of sending messages to the client program through the third high priority API and wherein the server program is further capable of registering a fourth high priority API with the client program and the client program is capable of sending messages to the server program through the fourth high priority API.

27. The management system of claim 25, wherein the server program is a first server program and wherein the system further comprises:

a second server program capable of connecting to at least one network device in the telecommunications network, wherein the client program is further capable of connecting to the second server program and capable of registering the first high priority API with the second server program, wherein the second server program is capable of sending messages to the client program through the first high priority API.

28. The management system of claim 25, wherein the server program is a first server program and wherein the system further comprises:

a second server program capable of connecting to at least one network device in the telecommunications network, wherein the client program is further capable of connecting to the second server program and capable of registering a third high priority API with the second server program, wherein the second server program is capable of sending messages to the client program through the third high priority API.

29. The management system of claim 25, wherein the client program is a first client program and wherein the system further comprises:

a second client program capable of connecting to the server program, wherein the server program is further capable of registering the second high priority API with the second client program and the second client program is capable of sending messages to the server program through the second high priority API.

30. The management system of claim 25, wherein the client program is a first client program and wherein the system further comprises:

a second client program capable of connecting to the server program, wherein the server program is further capable of registering a third high priority API with the second client program and the second client program is capable of sending messages to the server program through the third high priority API.

16. A management system for a telecommunications network, comprising:

a server program capable of connecting to at least one network device in the telecommunications network; and

a client program capable of connecting to the server program, wherein the server program is capable of registering a high priority application programming interface (API) with the client program and wherein the client program is capable of sending messages to the server program through the high priority API.

25. A management system for a telecommunications network, comprising:

a server program capable of connecting to at least one network device in the telecommunications network; and

a client program capable of connecting to the server program and capable of registering a first high priority application programming interface (API) with the server program, wherein the server program is capable of sending messages to the client program through the first high priority API; and

wherein the server program is further capable of registering a second high priority API with the client program and the client program is capable of sending messages to the server program through the second high priority API.

31. A management system for a telecommunications network, comprising:

a plurality of server programs capable of connecting to plurality of network devices in the telecommunications network; and

a plurality of client programs capable of connecting to the server programs and capable of registering a plurality of high priority application programming interfaces (APIs) with the server programs, wherein the server programs are capable of sending messages to the client programs through the high priority APIs.

32. The management system of claim 31, wherein the high priority APIs are a first plurality of high priority APIs and wherein the server programs are further capable of registering a second plurality of high priority APIs with the client programs, wherein the client programs are capable of sending messages to the server programs through the second plurality of high priority APIs.

33. A management system for a telecommunications network, comprising:

a plurality of server programs capable of connecting to a plurality of network devices in the telecommunications network; and

a plurality of client programs capable of connecting to the server programs, wherein the server programs are capable of registering a plurality of high priority application programming interfaces (APIs) with the client programs and wherein the client programs are capable of sending messages to the server programs through the high priority APIs.

36. The method of claim 35, wherein registering a high priority API with the server program comprises:

sending a high priority call back address from the client program to the server program.

37. The method of claim 35, wherein initiating a connection between the client program and the server program, comprises:

sending a password from the client program to the server program; and

sending a handle from the server program to the client program.

38. The method of claim 35, wherein initiating a connection between the client program and the server program, further comprises:

sending user credentials from the client program to the server program.

39. The method of claim 35, wherein sending messages from the server program to the client program through the high priority API comprises sending high priority messages from the server program to the client program through the high priority API.

40. The method of claim 35, wherein sending messages from the server program to the client program through the high priority API comprises sending roll call messages from the server program to the client program through the high priority API.

41. The method of claim 35, wherein registering a high priority API with the server program comprises establishing an out-of-band management channel.

42. The method of claim 35, wherein the high priority API is a first high priority API and wherein the method further comprises:

registering a second high priority API with the server program; and

sending messages from the server program to the client program through the second high priority API.

43. The method of claim 35, wherein the high priority API is a first high priority API and wherein the method further comprises:

registering a second high priority API with the client program; and

sending messages from the client program to the server program through the second high priority API.

44. The method of claim 43, further comprising:

registering a third high priority API with the client program; and

sending messages from the client program to the server program through the third high priority API.

45. The method of claim 35, wherein the server program is a first server program and wherein the method further comprises:

executing a second server program;

initiating a connection between the client program and the second server program;

registering the high priority API with the second server program; and

sending messages from the second server program to the client program through the high priority API.

46. The method of claim 35, wherein the server program is a first server program and the high priority API is a first high priority API and wherein the method further comprises:

executing a second server program;

initiating a connection between the client program and the second server program;

registering a second high priority API with the second server program; and

sending messages from the second server program to the client program through the second high priority API.

47. The method of claim 35, further comprising:

sending roll call messages from the server program to a network device in the telecommunications network;

detecting that the network device has gone down; and

sending a message from the server program to the client program through the high priority API indicating that the network device has gone down.

49. The method of claim 48, wherein registering a high priority application programming interface (API) with the client program comprises:

sending a high priority call back address from the server program to the client program.

50. The method of claim 48, wherein sending messages from the client program to the server program through the high priority API comprises sending high priority messages from the client program to the server program through the high priority API.

51. The method of claim 48, wherein sending messages from the client program to the server program through the high priority API comprises sending roll call messages from the client program to the server program through the high priority API.

52. The method of claim 48, wherein registering a high priority API with the client program comprises establishing an out-of-band management channel.

53. The method of claim 48, wherein the high priority API is a first high priority API, and further comprising:

registering a second high priority API with the client program; and

sending messages from the client program to the server program through the second high priority API.

54. The method of claim 48, wherein the client program is a first client program and wherein the method further comprises:

executing a second client program;

initiating a connection between the second client program and the server program;

registering the high priority API with the second client program; and

sending messages from the second client program to the server program through the high priority API.

55. The method of claim 48, wherein the client program is a first client program and the high priority API is a first high priority API and wherein the method further comprises:

executing a second client program;

initiating a connection between the second client program and the server program;

registering a second high priority API with the second client program; and

sending messages from the second client program to the server program through the second high priority API.

34. A management system for a telecommunications network, comprising:

a plurality of server programs capable of connecting to a plurality of network devices in the telecommunications network; and

a plurality of client programs capable of connecting to the server programs and capable of registering a first plurality of high priority application programming interfaces (APIs) with the server programs, wherein the server programs are capable of sending messages to the client programs through the first plurality of high priority APIs; and

wherein the server programs are further capable of registering a second plurality of high priority APIs with the client programs and the client programs are capable of sending messages to the server programs through the second plurality of high priority APIs.

35. A method of managing a telecommunications network comprising:

executing a server program;

executing a client program;

initiating a connection between the client program and the server program;

registering a high priority application programming interface (API) with the server program; and

sending messages from the server program to the client program through the high priority API.

48. A method of managing a telecommunications network comprising:

executing a server program;

executing a client program;

initiating a connection between the client program and the server program;

registering a high priority application programming interface (API) with the client program; and

sending messages from the client program to the server program through the high priority API.