Architecture for network manager

• US 6,266,694 B1
• Filed: 06/19/1997
• Issued: 07/24/2001
• Est. Priority Date: 06/19/1997
• Status: Expired due to Term

• Current Assignee: Ciena Corporation, Ciena Luxembourg S.a.r.l. (Ciena Corporation)
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: OʼNeill, Mary, Wee, Dennis, Pedneault, Michel, Wippel, Roland, Kairouz, Joseph, Duguay, Daniel, Fulford, Fraser, Do Rego, Yves
• Primary Examiner(s): Rinehart, Mark H.
• Assistant Examiner(s): YUAN, ALMARI ROMERO
• Application Number:
  US08/878,636
• Time in Patent Office: 1,496 Days
• Field of Search: 370/221, 370/222, 370/228, 370/410, 709/223, 709/224, 709/227, 709/228, 709/239
• US Class Current: 709/223
• CPC Class Codes: H04L 41/042 comprising distributed management centres cooperatively managing the network
• CPC Class Codes: H04L 41/044 comprising hierarchical management structures

Abstract

A distributed network management architecture, where a plurality of network managers share information about network elements by building the necessary infrastructure to discover alternate routes to element controllers when possible. A large number of network elements and operation controllers or managed object agents spans are simultaneously accessible to multiple graphical network browser instances on physical workstations. Each network manager can manage an element controller directly, through a direct connection, or indirectly, through an indirect connection to a second network manager which directly manages that element controller. As well, a plurality of telecommunication networks can be federated for transparently increasing the number of users and the reliability of each network. By allowing each network manager to be configured individually, more flexibility over both engineering and survivability is achieved.

Claims

1. A method of managing an element controller (EC) of a communications network comprising a first network manager (NM1) logically connected to the EC via a direct management path for direct management of the EC by the NM1, the method comprising the steps of:

a) dynamically selecting, from at least two management paths, a preferred management path between a second network manager (NM2) and the EC; and

b) establishing a logical connection between the NM2 and the EC over the selected preferred management path to enable management of the EC by the NM2.

2. A method as claimed in claim 1, wherein the at least two management paths comprise one or more of:

an indirect management path via a federated connection between the NM2 and the NM1; and

a reluctantly promoted direct management path between the NM2 and the EC.

3. A method as claimed in claim 2, wherein the step of dynamically selecting a preferred management path comprises the steps of, from the NM2:

a) querying the EC to obtain information identifying the NM1;

b) determining if the NM1 is directly managing the EC;

c) if the NM1 is directly managing the EC, selecting the preferred management path as the indirect management path via the federated connection between the NM2 and the NM1;

d) if the NM1 is not directly managing the EC;

i) assuming a reluctantly promoted state at the NM2 to enable direct management of the EC by the NM2; and

ii) selecting the preferred management path as the reluctantly promoted direct management path between the NM2 and the EC.

4. A method as claimed in claim 3, further comprising, if the NM1 is not directly managing the EC, the step of periodically attempting to demote the NM2 from the reluctantly promoted state.

5. A method as claimed in claim 4, wherein the step of periodically attempting to demote the NM2 comprises the steps of:

a) periodically determining if the NM1 has recovered direct management of the EC; and

b) when the NM1 has recovered direct management of the EC;

i) demoting the reluctantly promoted state of the NM2; and

ii) selecting the preferred management path as the indirect management path via the federated connection between the NM2 and the NM1.

6. A method as claimed in claim 2, wherein, when the preferred management path is the indirect management path via a federated connection, the step of establishing a logical connection over the preferred management path comprises the steps of:

a) establishing the federated connection between the NM2 and the NM1, the NM2 acting as an indirect client for the NM1, and the NM1 acting as an indirect server for the NM2; and

b) establishing a logical connection between the NM2 and the EC through the NM1 using the federated connection.

7. A method as claimed in claim 3, wherein the step of querying the EC comprises the steps of:

a) sending a query message to the EC, and receiving a response message from the EC containing information identifying each network manager logically connected to the EC over a direct management path; and

b) selecting the information identifying the NM1 from among the information identifying each network manager logically connected to the EC over a direct management path.

8. A method as claimed in claim 3, wherein the step of determining if the NM1 is available for communication with the EC comprises the steps of:

a) sending a connection request message to the NM1 and awaiting a response message from the MN1;

b) if the response message is received from the MN1, determining that the NM1 is available; and

c) otherwise, determining that the NM1 is not available.

9. A method of federating first and second communications networks comprising a respective plurality of element controllers (ECs) logically connected to a corresponding network manager (NM) over respective direct management paths for direct management of the EC'"'"'s by the corresponding NM, the method comprising the steps of:

a) dynamically selecting, from at least two management paths, a preferred management path between an element controller (EC2) of the second network and a network manager (NM1) of the first network; and

b) establishing a logical connection between the NM1 and the EC2 over the selected preferred management path, to enable management of the EC2 by the NM1.

10. A method as claimed in claim 9, wherein the at least two management paths comprise one or more of:

an indirect management path via a federated connection between the NM1 and a network manager (NM2) of the second network logically connected to the EC2 over a direct management path; and

a reluctantly promoted direct management path between the NM1 and the EC2.

11. A method as claimed in claim 10, wherein the step of dynamically selecting a preferred management path comprises the steps of, from the NM1:

a) querying the EC2 to obtain information identifying the NM2;

b) determining if the NM2 is directly managing the EC2;

c) if the NM2 is directly managing the EC2, selecting the preferred management path as the indirect management path via the federated connection between the NM1 and the NM2;

d) if the NM2 is not directly managing the EC2;

i) assuming a reluctantly promoted state at the NM1 to enable direct management of the EC2 by the NM1; and

ii) selecting the preferred management path as the reluctantly promoted direct management path between the NM1 and the EC2.

12. A method as claimed in claim 11, further comprising, if the NM2 is not directly managing the EC2, the step of periodically attempting to demote the NM1 from the reluctantly promoted state.

13. A method as claimed in claim 12, wherein the step of periodically attempting to demote the NM1 comprises the steps of:

a) periodically determining if the NM2 has recovered direct management of the EC2; and

ii) when the NM2 has recovered direct management of the EC2;

ii) demoting the reluctantly promoted state of the NM1; and

ii) selecting the preferred management path as the indirect management path via the federated connection between the NM1 and the NM2.

14. A method as claimed in claim 11, wherein the step of querying the EC comprises:

a) sending a query message to the EC2, and receiving a response message from the EC2 containing information identifying each network manager logically connected to the EC2 over a direct management path; and

68) selecting the information identifying the NM2 from among the information identifying each network manager logically connected to the EC2 over a direct management path.

15. A method as claimed in claim 11, wherein the step of determining if the NM2 is available for communication with the EC2 comprises the steps of:

a) sending a connection request message to the NM2 and waiting for a response message from the MN2;

b) if the response message is received from the MN2, determining that the NM2 is available; and

c) otherwise, determining that the NM2 is not available.

16. A method as claimed in claim 11, wherein, when the preferred management path is the indirect management path via a federated connection, the step of establishing a logical connection over the preferred management path comprises:

a) establishing a federated connection between the NM1 and the NM2, the NM1 acting as an indirect client for the NM2, and the NM2 acting as an indirect server for the NM1; and

69) establishing a logical connection between the NM1 and the EC2 through the NM2 using the federated connection.

17. A scalable communication network having a plurality of element controllers (ECs) adapted to control operations of a respective plurality of network elements, and two or more network managers (NMs) adapted for managing each of the element controllers (ECs), the network comprising:

a) a first network manager (NM1) logically connected to a first element controller (EC1) via a direct management path for direct management of the EC1 by the NM1; and

b) a second network manager (NM2) adapted to;

i) dynamically select, from at least two management paths, a preferred management path between the NM2 and the EC1; and

70) establish a logical connection between the NM2 and the EC1 over the selected preferred management path to enable management of the EC1 by the NM2.

18. A scalable communication network as claimed in claim 17, wherein the at least two management paths comprise one or more of:

an indirect management path via a federated connection between the NM2 and the NM1; and

a reluctantly promoted direct management path between the NM2 and the EC1.

19. A scalable communication network as claimed in claim 18, wherein the first network manager (NM1) comprises an indirect server manger (ISM) component adapted to enable a federated connection between the first network manager (NM1) and the second network manager (NM2).

20. A scalable communication network as claimed in claim 19, wherein the indirect server manger (ISM) component is further adapted to enable a logical connection between the first element controller (EC1) and the second network manager (NM2) through the federated connection.

21. A scalable communication network as claimed in claim 18, wherein the second network manager (NM2) comprises an indirect client manager (ICM) component adapted to enable management of the first element controller (EC1) using the selected preferred management path.

22. A scalable communication network as claimed in claim 21, wherein the ICM component is adapted to dynamically select the preferred management path by:

a) querying the EC1 to obtain information identifying the NM1 logically connected to the EC1 via a direct management path;

b) determining if the NM1 is directly managing the EC1;

c) if the NM1 is directly managing the EC1, selecting the preferred management path as the indirect management path via the federated connection between the NM2 and the NM1;

d) if the NM1 is not directly managing the EC1;

i) assuming a reluctantly promoted state to enable direct management of the EC1 by the NM2; and

73) selecting the preferred management path as the reluctantly promoted direct management path between the NM2 and the EC1.

23. A scalable communication network as claimed in claim 22, wherein, if the NM1 is not directly managing the EC1, the ICM component is adapted to periodically attempt to demote the NM2 from the reluctantly promoted state.

24. A scalable communication network as claimed in claim 23, wherein the ICM component is adapted to periodically attempt to demote the NM2 by:

a) periodically determining if the NM1 has recovered direct management of the EC; and

b) when the NM1 has recovered direct management of the EC;

i) demoting the reluctantly promoted state of the NM2; and

75) selecting the preferred management path as the indirect management path via the federated connection between the NM2 and the NM1.

25. A scalable communication network as claimed in claim 17, wherein each element controller comprises a respective collector name server including information identifying each network manager to which the element controller is logically connected over a direct management path.

26. A scalable communication network as claimed in claim 25, wherein the collector name server is responsive to a query from the NM1 to send a response message to the NM1 containing the information identifying each network manager to which the element controller is logically connected over a direct management path.

27. A scalable communication network as claimed in claim 17, wherein each network manager (NM) comprises a respective indirect access database (IAD) including information respecting devices to which the network manager can logically connect.

28. A scalable communication network as claimed in claim 27, wherein the IAD further comprises information identifying other network managers from which connection requests will be accepted to permit indirect management of any element controllers directly managed by the respective network manager (NM).

29. A scalable communication network as claimed in claim 28, wherein the IAD further comprises a list of paths available for selection as a preferred management path to enable management of an element controller.

30. A self healing communication network in which a plurality of element controllers (ECs) are connected for controlling operations of a respective plurality of network elements, and two or more network managers (NMs) are adapted for managing each of the element controllers (ECs), the network comprising:

a) a first network manager (NM1) logically connected to a first element controller (EC1) over a direct management path for direct management of the first element controller (EC1); and

b) connection means adapted for;

i) dynamically selecting, from at least two management paths, a preferred management path between the EC1 and a second network manager NM2; and

77) establish a logical connection between the NM2 and the EC over the selected preferred management path to enable management of the EC1 by the NM2.

31. A self healing communication network as claimed in claim 30, wherein the at least two management paths comprise one or more of:

an indirect management path via a federated connection between the NM2 and the NM1; and

a reluctantly promoted direct management path between the NM2 and the EC.

32. A self healing communication network as claimed in claim 31, wherein the connection means further comprises an indirect server manger (ISM) component operatively connected to the first network manager (NM1), the ISM component being adapted to enable a federated connection between the second network manager (NM2) and the first network manager (NM1).

33. A self healing communication network as claimed in claim 31, wherein the connection means further comprises an indirect client manager (ICM) component operatively connected to the second network manager (NM2), the ICM component being adapted to enable management of the first element controller (EC1) over the selected preferred management path.

34. A self healing communication network as claimed in claim 33, wherein the ICM component is adapted to dynamically select the preferred management path by:

a) querying the EC1 to obtain information identifying the NM1 logically connected to the EC1 via a direct management path;

b) determining if the NM1 is directly managing the EC1;

c) if the NM1 is directly managing the EC1, selecting the preferred management path as the indirect management path via a federated connection between the NM2 and the NM1;

d) if the NM1 is not directly managing the EC1;

i) assuming a reluctantly promoted state to enable direct management of the EC1 by the NM2; and

ii) selecting the preferred management path as the reluctantly promoted direct management path between the NM2 and the EC1.

35. A self healing communication network as claimed in claim 34, wherein, if the NM1 is not directly managing the EC1, the ICM component is adapted to periodically attempt to demote the NM2 from the reluctantly promoted state.

36. A self healing communication network as claimed in claim 35, wherein the ICM component is adapted to periodically attempt to demote the NM2 by:

a) periodically determining if the NM1 has recovered direct management of the EC; and

b) when the NM1 has recovered direct management of the EC;

i) demoting the reluctantly promoted state of the NM2; and

ii) selecting the preferred management path as the indirect management path via the federated connection between the NM2 and the NM1.

37. A self healing communication network as claimed in claim 30, wherein the connection means comprises a collector name server including information respecting each network manager (NM) logically connected to the first element controller (EC1) over a direct management path.

38. A self healing communication network as claimed in claim 37, wherein an instance of the collector name server is operatively connected to the first element controller (EC₁).

39. A self healing communication network as claimed in claim 37, wherein the connection means further comprises an indirect access database (IAD) including information respecting devices to which a respective network manager can connect.

40. A self healing communication network as claimed in claim 39, wherein the IAD further comprises means for identifying other network managers from which connection requests will be accepted to permit indirect management of any element controllers directly managed by the respective network manager (NM).

41. A self healing communication network as claimed in claim 40, wherein the IAD further comprises means for determining management paths available for selection as the preferred management path to enable management of the element controller.

42. A self healing communication network as claimed in claim 37, wherein the collector name server is responsive to a query from the NM1 to send a response message to the NM1 containing the information identifying each network manager to which the element controller is logically connected over a direct management path.

43. A network manager (NM) for managing a plurality of element controllers (ECs) of a communication network, the network manager (NM) comprising:

a) direct connection means for logically connecting the network manager (NM) to a first element controller (EC1) over a direct management path for direct management of the first element controller (EC1); and

b) indirect connection means adapted for;

i) dynamically selecting, from at least two management paths a preferred management path between the NM and a second element controller EC2; and

ii) establishing a logical connection over the preferred management path to enable management of the (EC2) by the NM.

44. A network manager as claimed in claim 43, wherein the at least two management paths comprise one or more of of:

an indirect management path via a federated connection between the NM and a second network manager (NM2) directly managing the EC2; and

a reluctantly promoted direct management path between the NM and the EC2.

45. A network manager as claimed in claim 44, wherein the indirect connection means comprises an indirect client manger (ICM) component adapted to enable management of the EC2 by the NM over the preferred management path.

46. A network manager as claimed in claim 45, wherein the ICM component is adapted to dynamically select the preferred management path by:

a) querying the EC2 to obtain information identifying the NM2 logically connected to the EC2 over a direct management path;

b) determining if the NM2 is directly managing the EC2;

c) if the NM2 is directly managing the EC2, selecting the preferred management path as the indirect management path via the federated connection between the NM and the NM2;

d) if the NM2 is not directly managing the EC2;

i) assuming a reluctantly promoted state to enable direct management of the EC2 by the NM; and

ii) selecting the preferred management path as the reluctantly promoted direct management path between the NM2 and the EC2.

47. A network manager as claimed in claim 46, wherein, if the NM2 is not directly managing the EC2, the ICM component is adapted to periodically attempt to demote the NM from the reluctantly promoted state.

48. A self healing communication network as claimed in claim 47, wherein the ICM component is adapted to periodically attempt to demote the NM by:

a) periodically determining if the NM2 has recovered direct management of the EC2; and

b) when the NM2 has recovered direct management of the EC2;

i) demoting the reluctantly promoted state of the NM; and

ii) selecting the preferred management path as the indirect management path via the federated connection between the NM and the NM2.

49. A network manager as claimed in claim 44, wherein the indirect connection means further comprises an indirect server manager ISM component adapted to enable indirect management of the first element controller (EC1) by another network manager using an indirect management path via a federated connection between the other network manager and the NM.

50. A network manager as claimed in claim 45, wherein the indirect connection means further comprises an indirect access database (IAD) including information respecting devices to which the network manager can connect.

51. A network manager as claimed in claim 50, wherein the IAD further comprises, in respect of each device to which the network manager can connect, information respecting a preferred connection path.

52. A network manager as claimed in claim 51, wherein the IAD further comprises means for determining other network managers from which connection requests will be accepted to permit indirect management of any element controllers directly managed by the network manager (NM).