Method and apparatus for constructing a device management information base in a network management station

• US 6,219,703 B1
• Filed: 10/31/1996
• Issued: 04/17/2001
• Est. Priority Date: 10/31/1996
• Status: Expired due to Term

• Current Assignee: Google Technology Holdings LLC (Alphabet Inc.)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: Miriyala, Srinivas, Starkweather, James Alan, Nguyen, Cuong The
• Primary Examiner(s): Harrell, Robert B.
• Assistant Examiner(s): VU, THONG H
• Application Number:
  US08/740,635
• Time in Patent Office: 1,629 Days
• Field of Search: 395/615, 395/200.01, 395/200.09, 395/182.18, 370/399, 709/226, 709/235, 709/202, 709/230, 709/223, 709/201, 707/515, 707/101, 379/34
• US Class Current: 709/224
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor

Abstract

In a data communication network a network management station (NMS) (102) constructs a device Management Information Base (MIB) for interfacing with a device (104) to be managed. The device provides an agent (110) that includes a management structure MIB (114) including data describing a device MIB structure supported by the device. The NMS is programmed with an application (108) that can interpret the data of the management structure MIB in order to construct the device MIB. The NMS detects (502) that the device is present on the network, and, in response, accesses (508, 510, 512, 514) the management structure MIB to obtain the data describing the device MIB structure, when the device MIB is not known to the NMS. The NMS application interprets the data describing the device MIB structure, and constructs (516) the device MIB from the interpreted data.

Claims

1. A method in a data communication network having a network management station (NMS) for constructing in the NMS a device Management Information Base (MIB) for interfacing with a device, comprising the steps of:

providing in the device an agent that includes a self-describing management structure MIB comprising data describing a device MIB structure supported by the device;

programming the NMS with an application that can interpret the data of the self-describing management structure MIB in order to construct the device MIB;

detecting by the NMS that the device is present on the network;

accessing the self-describing management structure MIB of the device by the NMS to obtain, through conventional Simple Network Management Protocol (SNMP) commands, the data describing the device MIB structure, in response to the detecting step when the device MIB is not known to the NMS; and

interpreting by the application the data describing the device MIB structure, thereby constructing the device MIB in the NMS.

2. The method of claim 1, wherein the providing step comprises the step of providing one of a MIB identifier and a MIB identifier plus a version number.

3. The method of claim 1, wherein the providing step comprises the step of providing a list of standard MIBs supported by the agent.

4. The method of claim 3, wherein the step of providing a list of standard MIBs supported by the agent comprises the steps of:

listing a Request for Comments (RFC) number that corresponds to each of the standard MIBs; and

providing an indicator for indicating whether the corresponding MIB is supported by the agent, or merely referenced by the agent.

5. The method of claim 1, wherein the providing step comprises the step of

providing a list of Abstract Syntax Notation One (ASN.1) types defined by the agent.

6. The method of claim 5, wherein the step of providing a list of ASN.1 types defined by the agent comprises the step of listing:

a name assigned to each ASN.1 type, and

a parameter specifying how the ASN.1 type is declared.

7. The method of claim 1, wherein the providing step comprises the step of providing a list of MIB objects supported by the agent.

8. The method of claim 7, wherein the step of providing a list of MIB objects supported by the agent comprises the step of listing, for each MIB object, applicable predetermined fields specified by SNMP for defining an SNMP object.

9. The method of claim 1, wherein the providing step comprises the step of providing a list of traps supported by the agent.

10. The method of claim 9, wherein the step of providing a list of traps supported by the agent comprises the step of listing, for each trap, applicable predetermined fields required for defining an SNMP trap.

11. A network management station (NMS) in a data communication network for constructing in the NMS a device Management Information Base (MIB) for interfacing with a device, the NMS comprising:

a communication interface coupled to the network for communicating with the device; and

a processing system coupled to the communication interface for controlling the device,

wherein the processing system is programmed to;

interpret the data of a self-describing management structure MIB in order to construct the device MIB, the self-describing management structure MIB provided by the device from an agent that includes the self-describing management structure MIB, which provides data describing a device MIB structure supported by the device;

detect that the device is present on the network;

in response, access the self-describing management structure MIB of the device to obtain, through conventional Simple Network Management Protocol (SNMP) commands, the data describing the device MIB structure, when the device MIB is not known to the NMS; and

interpret the data describing the device MIB structure, thereby constructing the device MIB in the NMS.

12. A device in a data communication network having a network management station (NMS) for constructing in the NMS a device Management Information Base (MIB) for interfacing with the device, comprising:

a communication interface coupled to the network for communicating with the NMS; and

a processing system coupled to the communication interface for controlling the device,

wherein the processing system is programmed with an agent including a self-describing management structure MIB, which provides data describing a device MIB structure supported by the device, and

wherein the processing system is further programmed to communicate to the NMS the data describing the device MIB structure, in response to an access of the self-describing management structure MIB by the NMS, through conventional Simple Network Management Protocol (SNMP) commands, when the device MIB is not known to the NMS, thereby enabling the NMS to construct the device MIB in the NMS.

13. The device of claim 12, wherein the processing system is further programmed to communicate to the NMS one of a MIB identifier and a MIB identifier plus a version number.

14. The device of claim 12, wherein the processing system is further programmed to communicate to the NMS a list of standard MIBs supported by the agent.

15. The device of claim 14, wherein the processing system is further programmed to communicate to the NMS:

a Request for Comments (RFC) number that corresponds to each of the standard MIBs; and

an indicator for indicating whether the corresponding MIB is supported by the agent, or merely referenced by the agent.

16. The device of claim 12, wherein the processing system is further programmed to communicate to the NMS a list of Abstract Syntax Notation One (ASN.1) types defined by the agent.

17. The device of claim 16, wherein the processing system is further programmed to communicate to the NMS:

a name assigned to each ASN.1 type, and

a parameter specifying how the ASN.1 type is declared.

18. The device of claim 12, wherein the processing system is further programmed to communicate to the NMS a list of MIB objects supported by the agent.

19. The device of claim 18, wherein the processing system is further programmed to communicate for each MIB object, applicable predetermined fields specified by SNMP for defining an SNMP object.

20. The device of claim 12, wherein the processing system is further programmed to communicate to the NMS a list of traps supported by the agent.