Dynamic SNMP network device

• US 20030177214A1
• Filed: 03/13/2002
• Published: 09/18/2003
• Est. Priority Date: 03/13/2002
• Status: Abandoned Application

• Current Assignee: D-Link Corporation
• Original Assignee: D-Link Corporation
• Inventors: Huang, Ta-Shan, Chen, Yung-Hsin
• Application Number:
  US10/095,433
• Publication Number:
  US 20030177214A1
• Time in Patent Office: Days
• US Class Current: 709/223
• 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

The present invention relates to a dynamic SNMP network device comprising at least one MIB module and a dynamic SNMP agent engine installed therein. Each of the MIB module is generated corresponding to a certain MIB, contains necessary data variables and functions and provides the same behaviors as the corresponding MIB. The dynamic SNMP agent engine may load at least one MIB module depending on applications and, alternatively, unload any one of loaded MIB modules. Thus, the dynamic SNMP network device is capable of dynamically expanding or replacing a functional module for providing additional MIB capabilities.

Claims

1. A dynamic simple network management protocol (SNMP) network device comprising:

at least one management information base (MIB) module wherein each MIB module is generated corresponding to a predetermined MIB and each MIB module contains necessary data variables and functions and provides the same behaviors provided by the corresponding MIB; and

a dynamic SNMP agent engine for loading at least one MIB module depending on applications so that the dynamic SNMP network device is capable of dynamically expanding or replacing a functional module for providing additional MIB capabilities.

2. The network device of claim 1, wherein the dynamic SNMP agent engine comprises:

a SNMP kernel implemented as a standard kernel associated with a SNMP agent, the SNMP kernel being coupled to a remote network management station (NMS) over a network so as to receive a SNMP request packet from the NMS or transmit a SNMP response packet to the NMS, and process a standard SNMP message;

an MIB module dispatcher coupled to the SNMP kernel and at least one MIB module respectively, the MIB module dispatcher being operative to analyze the SNMP request packet transmitted from the SNMP kernel prior to reading out an object identifier (OID) of the SNMP request packet, or receive a processed message from at least one MIB module; and

a registry database coupled to the MIB module dispatcher for storing a name of each MIB module and the OID corresponding to each MIB module;

wherein when the SNMP kernel receives the SNMP request packet from the NMS over the network, the SNMP request packet is transmitted to the MIB module dispatcher for analysis so as to read out the OID of the SNMP request packet, in response the MIB module dispatcher searches a corresponding MIB module in the registry database based on the OID so as to know which MIB module is in charge of processing a behavior requested by the SNMP request packet and transmit an invoke signal to the corresponding MIB module, and in response to data processed by the corresponding MIB module has been received by the MIB module dispatcher, data is transmitted to the SNMP kernel for performing a standard SNMP packet processing thereon prior to transmitting to the NMS.

3. The network device of claim 1, wherein the SNMP request packet is a PDU packet.

4. The network device of claim 2, wherein the registry database is a set of corresponding tables implemented as a tree hierarchy for storing the name of each MIB module and the OID corresponding to each MIB module.

5. The network device of claim 2, wherein the dynamic SNMP agent engine further comprises:

an MIB module loader coupled to the registry database for loading or unloading the MIB module wherein in the loading or the unloading of each MIB module, the MIB module loader is commanded to update data registered in the registry database simultaneously.

6. The network device of claim 2, wherein the dynamic SNMP agent engine further comprises:

a basic module coupled to the MIB module dispatcher, the basic module being selectable during installation and including general or network device related to basic variables and behavior functions.

7. The network device of claim 2, further comprising a managed entity implemented as an entity of hardware, application programs, or operating system being managed by the dynamic SNMP agent engine, wherein the managed entity is coupled to the basic module and each MIB module respectively so that the basic module or each MIB module is operative to control and access to the managed entity.

8. The network device of claim 1, wherein the MIB module is either a dynamic linking data file or an executable file.

9. The network device of claim 1, wherein in a Microsoft system, the MIB module is a file having an extension of .DLL.

10. The network device of claim 1, wherein in a Microsoft system, the MIB module is a file having an extension of .exe.

11. The network device of claim 1, wherein in a Unix system, the MIB module is an executable file having an extension of .so.

12. The network device of claim 1, wherein in an embedded system, the MIB module has a dynamic linking structure and comprises active processes, extended variables, and extended functions.

13. The network device of claim 12, wherein each active process means that the network device embeds an active message of the SNMP agent in a generated message and transmits the message to the SNMP kernel through the MIB module dispatcher.

14. The network device of claim 12, wherein the extended variables and the extended functions are variables and functions required in generating each MIB module, the extended variables consist of a group of extended variables, the extended functions consist of a group of extended behavior functions, and the extended variables and the extended functions are in cooperation with the active process for enabling the generated MIB module to perform a behavior defined by the MIB.