System and method for recovering management of network element(s) responsive to failure of a distributed gateway

• US 7,209,968 B1
• Filed: 05/29/2001
• Issued: 04/24/2007
• Est. Priority Date: 05/29/2001
• Status: Active Grant

• Current Assignee: Objective Systems Integrators, Inc. (Mycom Group Ltd.)
• Original Assignee: Agilent Technologies, Inc.
• Inventors: Secer, Semih
• Primary Examiner(s): DINH, KHANH Q
• Application Number:
  US09/870,159
• Time in Patent Office: 2,156 Days
• Field of Search: 709/224, 709/226, 709/228, 709/232, 709/217, 709/220, 709/227, 709/223, 709/225, 709/219, 709/235, 709/229, 714/4, 707/100, 707/10, 713/153
• US Class Current: 709/226
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route

Abstract

A system and method are disclosed which enable efficient recovery of management of one or more network elements responsive to failure of a gateway responsible for managing such one or more network elements. According to at least one embodiment, operation of a plurality of distributed gateways that are each responsible for managing one or more network elements is monitored. Through such monitoring, failure of one of the distributed gateways may be efficiently detected, and responsive to detection of a failed gateway, management of the network element(s) for which such failed gateway had management responsibility may be efficiently recovered by allocating responsibility of management activities for which a detected failed gateway had responsibility to one or more available gateways. Allocation of such management activities may be performed in a manner that balances the operational load placed on such available gateways.

Claims

1. A method of recovering management of one or more network elements, said method comprising:

communicatively coupling the one or more network elements with at least one a plurality of distributed gateways;

communicatively coupling the at least one distributed gateway with at least one gateway monitoring system;

communicatively coupling the at least one gateway monitoring system with a central management system;

monitoring operation, by the at least one gateway monitoring system, of the plurality of distributed gateways, each of the plurality of distributed gateways responsible for managing the one or more network elements;

detecting failure by the at least one gateway monitoring system, of one of the plurality of distributed gateways, wherein the detecting comprises the steps of;

means for determining at least one type of the failure,

means for distinguishing at least one source of the failure selected from the group consisting of hardware failures, software failures, and communication port failures,

means for presenting to the user at least one reason for the failure based on the at least one type of the failure and the at least one source of the failure,

means for presenting to the user at least one action that could be taken by the central management system to resolve the at least one failure, and

means for receiving at least one selection of the at least one action;

receiving a notice of the detected failure from the at least one gateway monitoring system at the central management system; and

responsive to said receiving step, recovering, by the central management system, management of the one or more network elements for which the failed one of the plurality of distributed gateways had management responsibility by assigning management responsibility to at least one other of the plurality of distributed gateways.

2. The method of claim 1 wherein said managing the one or more network elements includes translating from one protocol utilized by the one or more network elements to another protocol.

3. The method of claim 1 wherein said plurality of distributed gateways are communicatively coupled to a processor-based management system.

4. The method of claim 3 further comprising the step of:

said management system controlling said recovering step.

5. The method of claim 1 wherein said detecting step further includes the step of:

said one or more gateway monitoring systems polling said plurality of distributed gateways.

6. The method of claim 1 further comprising the step of:

said one or more gateway monitoring systems controlling said recovering step.

7. The method of claim 1 further comprising the step of:

determining management activities for which a detected failed gateway is responsible for performing.

8. The method of claim 7 further comprising the step of:

determining one or more available gateways from said plurality of distributed gateways, which are available for assuming at least a portion of said management activities of said detected failed gateway.

9. The method of claim 8 wherein said one or more available gateways are a subset of said plurality of distributed gateways.

10. The method of claim 8 wherein said available gateways are gateways local to said detected failed gateway.

11. The method of claim 8 further comprising the step of:

grouping two or more of said plurality of distributed gateways.

12. The method of claim 11 wherein said step of determining one or more available gateways, includes determining gateways that are included in a common grouping with said detected failed gateway.

13. The method of claim 11 wherein said grouping is predetermined based at least in part on a criteria selected from the group consisting of:

gateway communication protocol, gateway location, and any user-defined criteria.

14. The method of claim 8 wherein said recovering step further includes the step of:

distributing said management activities of said detected failed gateway to at least one of said one or more available gateways.

15. The method of claim 14 wherein said distributing step further includes the steps of:

determining operational load of said available gateways; and

performing load balancing in distributing said management activities to said at least one of said one or more available gateways.

16. The method of claim 15 wherein said load balancing is performed autonomously by a processor-based system.

17. The method of claim 16 wherein said load balancing further comprises the steps of:

determining the operational load for each of said management activities; and

allocating said management activities to one or more of said available gateways in a manner that approximately balances each of their operational loads.

18. The method of claim 17 wherein said operational load of said available gateways is determined dynamically, and allocation of said management activities is determined based at least in part on said determined operational load of said available gateways.

19. The method of claim 16 wherein said load balancing is performed according to a greedy algorithm.

20. The method of claim 7 wherein said recovering step further includes the step of:

distributing said management activities of said detected failed gateway to at least one other of said plurality of distributed gateways.

21. The method of claim 20 wherein said distributing step is autonomously performed by a processor-based system.

22. The method of claim 20 wherein said distributing step further includes the steps of:

determining operational load of said available gateways; and

performing load balancing in distributing said management activities to said at least one other of said plurality of distributed gateways.

23. The method of claim 1 wherein said plurality of distributed gateways are operable to translate from one plurality of different protocols to another plurality of different protocols.

24. The method of claim 1 further comprising the step of:

user predefining at least one of said plurality of distributed gateways to be used in recovering management of one or more network elements for which a particular one of said plurality of distributed gateways has management responsibility in the event of a failure of said particular one of said plurality of distributed gateways.

25. The method of claim 1 further comprising the step of:

user predefining criteria to be used in recovering management of one or more network elements in the event of a failure of one of said plurality of distributed gateways.

26. A system comprising:

plurality of network elements;

plurality of distributed gateways each communicatively coupled to one or more of said plurality of network elements, wherein each of said plurality of distributed gateways is responsible for managing one or more of said plurality of network elements;

gateway monitoring system communicatively coupled to said plurality of distributed gateways, wherein said gateway monitoring system is operable to detect failure of at least one of said distributed gateways;

means for determining at least one type of the failure;

means for distinguishing at least one source of the failure selected from the group consisting of hardware failures, software failures, and communication port failures;

means for presenting to the user at least one reason for the failure based on the at least one type of the failure and the at least one source of the failure;

means for presenting to the user at least one action that could be taken by the central management system to resolve the at least one failure;

means for receiving at least one selection of the at least one action; and

management recovery system communicatively coupled to said plurality of distributed gateways,

wherein said management recovery system is operable to autonomously recover management of said one or more network elements for which a detected failed gateway had management responsibility.

27. The system of claim 26 wherein said management recovery system is operable to assign management responsibility of said one or more network elements for which said detected failed gateway had management responsibility to at least one other of said plurality of distributed gateways.

28. The system of claim 26 wherein said managing one or more of said network elements includes translation from one protocol utilized by said one or more network elements to another protocol.

29. The system of claim 26 wherein said gateway monitoring system and said management recovery system are integrated on a common platform.

30. The system of claim 26 wherein said gateway monitoring system is operable to poll said plurality of distributed gateways.

31. The system of claim 26 wherein said management recovery system is operable to determine management activities for which said detected failed gateway is responsible for performing.

32. The system of claim 31 wherein said management recovery system is operable to determine one or more available gateways from said plurality of distributed gateways, which are available for assuming at least a portion of said management activities of said detected failed gateway.

33. The system of claim 32 wherein said one or more available gateways are a subset of said plurality of distributed gateways.

34. The system of claim 32 wherein said available gateways are gateways local to said detected failed gateway.

35. The system of claim 32 wherein said available gateways are gateways operable to translate a common communication protocol as said detected failed gateway.

36. The system of claim 32 wherein said management recovery system is further operable to distribute said management activities of said detected failed gateway to at least one of said one or more available gateways.

37. The system of claim 36 wherein said management recovery system is operable to determine operational load of said available gateways, and perform load balancing in distributing said management activities to said at least one of said one or more available gateways.

38. The system of claim 37 wherein in performing said load balancing said management recovery system is operable to determine the operational load for each of said management activities, and allocate said management activities to one or more of said available gateways in a manner that approximately balances each of their operational loads.

39. The system of claim 37 wherein said management recovery system further comprises:

software code executable by said management recovery system, said software code implementing a greedy algorithm for controlling said load balancing.

40. The system of claim 26 wherein said management recovery system further comprises:

software code executable by said management recovery system to present a user interface for alerting a user of said detected failed gateway.

41. The system of claim 26 wherein said management recovery system further comprises:

software code executable by said management recovery system to present a user interface that enables a user to predefine, before said gateway monitoring system detects a failed gateway, at least one of said plurality of distributed gateways to be used in recovering management of one or more network elements for which a particular one of said plurality of distributed gateways has management responsibility in the event of a failure of said particular one of said plurality of distributed gateways.

42. The system of claim 26 wherein said management recovery system further comprises:

software code executable by said management recovery system to present a user interface that enables a user to predefine criteria, before said gateway monitoring system detects a failed gateway, to be used in recovering management of one or more network elements in the event of a failure of one of said plurality of distributed gateways.

43. A system for recovering management of one or more network elements responsive to failure of a distributed gateway, said system comprising:

plurality of distributed gateways, each for managing one or more network elements;

a gateway monitoring system communicatively coupled to said plurality of distributed gateways, said gateway monitoring system capable of detecting failure of anyone of said distributed gateways;

means for determining at least one type of the failure;

means for distinguishing at least one source of the failure selected from the group consisting of hardware failures, software failures, and communication port failures;

means for presenting to the user at least one reason for the failure based on the at least one type of the failure and the at least one source of the failure;

means for presenting to the user at least one action that could be taken by the central management system to resolve the at least one failure;

means for receiving at least one selection of the at least one action;

means communicatively coupled to said gateway monitoring system for receiving a notice of the detected failure at a central management system; and

means, responsive to said means for receiving a notice of the detected failure of one of said distributed gateways, for autonomously recovering, by the central management system, management of one or more network elements for which the detected failed gateway had management responsibility.

44. The system of claim 43 wherein the means for autonomously recovering management comprises logic for assigning management responsibility of said one or more network elements for which said detected failed gateway had management responsibility to at least one other of said plurality of distributed gateways.

45. The system of claim 44 wherein said logic includes software code executable by said means for autonomously recovering management.

46. The system of claim 43 wherein said managing one or more network elements includes translation from one protocol utilized by said one or more network elements to another protocol.

47. The system of claim 43 wherein said means for detecting failure comprises logic for polling said plurality of distributed gateways.

48. The system of claim 47 wherein said logic includes software code executable by said means for detecting failure.

49. The system of claim 43 further comprising:

means for determining management activities for which said detected failed gateway is responsible for performing.

50. The system of claim 49 further comprising:

means for determining one or more available gateways from said plurality of distributed gateways, which are available for assuming at least a portion of said management activities of said detected failed gateway.

51. The system of claim 50 wherein said one or more available gateways are a subset of said plurality of distributed gateways.

52. The system of claim 50 wherein said available gateways are determined as gateways local to said detected failed gateway.

53. The system of claim 50 wherein said available gateways are determined as gateways operable to translate a common protocol as said detected failed gateway.

54. The system of claim 50 wherein said means for autonomously recovering management comprises logic for allocating said management activities of said detected failed gateway to at least one of said one or more available gateways.

55. The system of claim 54 further comprising:

means for determining operational-load of said available gateways, wherein said means for autonomously recovering management comprises logic for performing load balancing in allocating said management activities to said at least one of said one or more available gateways.

56. The system of claim 55 further comprising:

means for determining the operational load for each of said management activities, wherein said means for autonomously recovering management comprises logic for allocating said management activities to one or more of said available gateways in a manner that approximately balances each of their operational loads.