Distributed chassis agent for distributed network management

• US 5,522,042 A
• Filed: 01/28/1994
• Issued: 05/28/1996
• Est. Priority Date: 01/28/1994
• Status: Expired due to Term

• Current Assignee: Enterasys Networks Incorporated (Extreme Networks, Inc.)
• Original Assignee: Cabletron Systems Incorporated (Extreme Networks, Inc.)
• Inventors: Fee, Brendan, Dobbins, Kurt, Arneson, Dave, Mullaney, Pat
• Primary Examiner(s): Geckil, Mehmet B.
• Application Number:
  US08/187,856
• Time in Patent Office: 851 Days
• Field of Search: 395/800, 395/200, 395/700, 395/575, 395/200.10, 395/200.11, 395/200.01, 395/181
• 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/042 comprising distributed management centres cooperatively managing the network
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/24 using dedicated network management hardware
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

An apparatus and method for allocating the performance of applications in a networking chassis among one or more modules in the chassis. In particular, the system acts as a chassis agent for performing network management functions. The agent performs a discovery function whereby each module discovers the location and current utilization of resources and applications for itself and transmits that information to other modules, and wherein each module maintains a slot table of such information for all modules. Based on the information in the slot table, each module performs an election function for allocating applications among the various modules in the chassis. The agent uses Management Information Bases MIBs to gather information about the chassis and to effect control on the chassis, wherein each managed object is registered both locally and remotely in a MIB tree maintained on each module, and the data is maintained locally on the module on which the managed object resides. The system enables the chassis to be managed "as a whole" while the management functions are distributed across the system, and the system is both fault tolerant and enables ready expansion and modification of the management applications.

Claims

1. A system for allocating applications in a networking chassis comprising:

a networking chassis having a backplane and a plurality of module-receiving slots;

a plurality of modules disposed in a plurality of respective slots and connected to the backplane for intermodule communication;

each module having means for performing applications and each module having a slot table therein;

each module having means for determining and storing in the respective slot table module information regarding the respective module, and means for sending a message containing respective module information to other modules;

each module having means for listening to the messages of other modules and storing in the respective slot table module information regarding other modules received in the messages; and

each module having means for electing, based on the module information in the slot table, one or more modules in the chassis to perform applications, and wherein a malfunction in one or more modules enables the electing means in the remaining modules to elect which of the remaining modules will perform applications.

2. The system of claim 1, wherein:

the system has a Management Information Base MIB of managed objects;

a MIB tree located on each module in the system for identifying locations of all managed objects;

means for assigning an identifier to each managed object; and

means for registering a local managed object in the MIB tree on the module on which the local managed object resides, and a means for registering remotely to the other modules.

3. The system of claim 1, wherein each module includes resources and applications and the module information includes one or more of:

a chassis in which the respective module is disposed;

a slot in which the respective module is disposed;

resources of the respective module;

applications of the respective module; and

availability of the resources.

4. The system of claim 1, wherein each module has a clock and broadcasts asynchronously.

5. The system of claim 1, wherein each module has a clock and sends unsolicited messages after a specified announcement period.

6. The system of claim 1, wherein each module has means for polling another module for the module information in the slot table of the other module.

7. The system of claim 1, wherein the backplane includes a pair of management buses for transmitting messages, and each module has means for electing one or more of the management buses for messages of the respective module and for making a re-election if there is a fault on one of the management buses.

8. The system of claim 1, wherein the applications performed are networking management applications.

9. A method for allocating applications in a networking chassis comprising the steps of:

providing a networking chassis having a backplane and a plurality of module-receiving slots;

providing a plurality of modules disposed in a plurality of respective slots and connected to the backplane for intermodule intercommunication, each module having means for performing applications and each module having a slot table therein;

each module determining and storing in the respective slot table module information regarding the respective module;

each module sending a message containing respective module information to other modules;

each module listening to the messages of the other modules and storing in the respective slot table module information regarding other modules received in the messages; and

each module electing, based on the module information in the respective slot table, one or more modules in the chassis to perform applications, and wherein when a malfunction occurs in one or more modules the remaining modules can elect which of the remaining modules will perform applications.

10. The method of claim 9, wherein each module sends unsolicited messages after a specified announcement period.

11. The method of claim 9, wherein the modules send messages asynchronously.

12. The method of claim 9, wherein the modules include resources and applications and each module determines module information which identifies one or more of:

a chassis in which the respective module is disposed;

a slot in which the respective module is disposed;

resources of the respective module;

applications of the respective module; and

availability of the resources.

13. The method of claim 9, including polling other modules for the module information in respective slot tables of the other modules.

14. The method of claim 9, including:

providing a Management Information Base MIB of managed objects;

providing a MIB tree on every module for identifying locations of all managed objects;

assigning an identifier to each managed object; and

registering the identifier both locally in the MIB tree on the module on which the local managed object resides and remotely on the other modules.

15. The method of claim 9, further comprising:

adding an additional module to the backplane to further distribute a processing load of the applications.

16. The method of claim 9, further comprising:

replacing at least some of the modules on the backplane with new modules having different resources and applications.

17. The method of claim 9, wherein:

the applications performed are network management applications.

18. A method for allocating applications in a networking chassis having a backplane and a plurality of module-receiving slots, a plurality of modules disposed in the plurality of respective slots and connected to the backplane for intermodule intercommunication, each module having means for performing applications, the method comprising the steps of:

providing a slot table in each module;

determining module information regarding a respective module;

storing the module information in the respective slot table in the respective module;

sending a message containing module information of the respective module to other modules;

listening to messages of other modules and storing, in the respective slot table of a module, information regarding the other modules received in the messages; and

electing, based on module information in a respective slot table, one or more modules in the chassis to perform applications, and wherein when a malfunction occurs in one or more modules the remaining modules can elect which of the remaining modules will perform applications.

19. The method of claim 18, further comprising sending unsolicited messages after a specified announcement period.