CN100440801C - A method to realize the fusion of multi-standard management information base on the agent side - Google Patents

Abstract

The invention discloses a method for realizing the fusion of multi-standard management information databases on the agent side. First, a fusion MIB including all OID nodes in these databases is established for the fusion of multiple MIB standards; and each OID node of the fusion MIB is added to the management of the SNMP agent. In the information base tree, and provide processing function GET/SET for each OID node; according to the MIB standard supported by the network management environment that the agent needs to work, configure the configuration item used to identify the MIB standard currently supported by the agent; the agent When reporting the Trap message to the simple SNMP manager, identify the currently supported MIB standard according to the configuration value of the configuration item, bind the OID in the standard to the Trap message and report it to the manager. The invention makes the SNMP manager and the SNMP agent do not need to be upgraded, and the SNMP agent device can work in different network management environments.

Description

A method to realize the fusion of multi-standard management information base on the agent side

technical field

The invention relates to network management technology, in particular to an SNMP network management method.

Background technique

With the rapid development of network technology, NGN (Next Generation Network: Next Generation Network) network has stepped out of the laboratory and developed into the era of large-scale commercial use. There are a large number of terminal devices in the NGN network, such as: HGW (Home Gateway: Home Gateway), IAD (Integrated Access Device: Integrated Access Device) and so on. With the large-scale operation of the network, the effective management of these devices has become a problem that must be solved. Now the management of these terminal devices usually adopts SNMP (Simple Network Management Protocol: Simple Network Management Protocol) protocol. As shown in FIG. 1 , the implementation of the SNMP protocol is completed jointly by the SNMP manager 10 and the SNMP agent 11 . SNMP manager 10 and SNMP agent 11 share a MIB (Management Information Base: ManagementInformation Base) 12 to describe the information of the device where SNMP agent 11 is located, and SNMP manager 10 is operated by GET/GET-NEXT/SET/GET-RESPONSE/ To communicate with the SNMP agent 11, the SNMP agent 11 actively communicates with the SNMP manager 10 using TRAP (self-trap). The SNMP manager 10 is a server, and the SNMP agent 11 is realized on the terminal equipment managed by the SNMP manager 10 .

One characteristic of terminal equipment is that the use environment is variable. For example, the same IAD equipment may work in different network management environments, that is, work under different SNMP network managers, and each SNMP manager has a different MIB. So the question arises, when the terminal equipment changes the environment, can the network management environment also be required to change to support more MIBs? In the actual environment, the SNMP manager is maintained by the operator and will not be updated frequently due to changes in the managed devices. Therefore, in order to enhance the adaptability of terminal equipment to the network management environment, it is necessary to implement multi-standard MIB integration on the SNMP agent side.

The Chinese patent with the patent application number CN200410009251.2 discloses a "MIB version coordination method between SNMP management station and agent". A device with an SNMP agent supports the requirements of various network management environments.

The U.S. patent "SYSTEM AND METHODFOR CONTROLLING TRAP GENERATION OF SIMPLE NETWORKMANAGEMENT PROTOCOL (SNMP) BY DEFINING AND USING A TRAPFLAG FIELD AND A TRAP PEER FIELD IN THE MANAGE DINFORMATION passed the BASE (MI Controls the method by which TRAP is generated. This patent only proposes a method for generating different TRAPs, but also does not integrate MIBs of different standards, and cannot meet the requirement that a device with an SNMP agent support multiple network management environments.

Contents of the invention

The technical problem to be solved by the present invention is to provide a method for realizing the fusion of multi-standard management information bases on the agent side, so that neither the SNMP manager nor the SNMP agent needs to be upgraded, and the SNMP agent device can work in different network management environments.

The invention provides a method for realizing the fusion of multi-standard management information bases on the agent side, which includes the following steps:

(a) Establishing a fusion management information base obtained by merging multiple standard management information bases including all object identifier nodes of these standard management information bases;

(b) adding each object identifier node of the fusion management information base to the management information base tree of the simple network management protocol agent, and providing a processing function GET/SET for each of the object identifier nodes;

(c) according to the management information base standard supported by the network management environment where the agent needs to work, configuring configuration items for identifying the management information base standard currently supported by the agent;

(d) When the agent reports the Trap message to the Simple Network Management Protocol manager, it recognizes the currently supported MIB standard according to the configuration value of the configuration item, and binds the object identifier in the standard to the Trap message reported to the manager.

Further, the above method can also have the following characteristics: in the step (a), the establishment of the integrated management information base is based on any standard management information base tree, and the different objects in other standard management information base trees are identified A symbol node is added to the base MIB tree for implementation.

Further, the above-mentioned method may also have the following features: it also includes the following step: the manager manages the object identifier nodes contained in the management information base standards supported by itself in the agent by operating them.

Further, the above method may also have the following characteristics: when the agent needs to be connected to a simple network management protocol manager supporting another management information base standard, only the configuration of the configuration item of the agent needs to be modified The value is a configuration value that identifies the other MIB criteria.

It can be seen from the above that the method of the present invention greatly enhances the adaptability of the terminal equipment to the network management environment. When the network management environment changes, it is only necessary to modify the configuration item identifying the current MIB standard, and there is no need to upgrade the version of the terminal device or the SNMP management station.

Description of drawings

Fig. 1 is a schematic diagram of the working process of the existing SNMP manager and SNMP agent.

Fig. 2 is a structural block diagram of the SNMP management system in the embodiment of the present invention.

Fig. 3 is a flowchart of a method for realizing multi-standard MIB fusion according to an embodiment of the present invention.

Detailed ways

The present invention will be further described below in conjunction with the accompanying drawings and specific embodiments.

This embodiment takes the fusion of two standard MIBs as an example. Figure 2 shows the system formed by connecting the same SNMP agent to SNMP manager MANAGER_A and the system formed by connecting the SNMP agent to SNMP manager MANAGER_B. . The structure of SNMP management system includes SNMP manager, SNMP agent and MIB module. in:

The SNMP manager does not have to make any changes. The MIB module shall store a fusion MIB file containing each standard MIB, and the file includes all OID nodes in each standard MIB. In order to achieve multi-standard MIB fusion, the SNMP agent needs to save each OID node in the fusion MIB_AB, and add GET/SET processing functions for each OID node. It is also necessary to complete the configuration of the configuration item MIB_CFG_STANDARD used to identify the MIB standard currently supported by the SNMP agent through a configuration interface. In addition, when SNMP sends a TRAP message to the SNMP manager, it should bind the OID in the standard according to the currently configured MIB standard.

This embodiment realizes the method for two standard MIB fusions, as shown in Figure 3, comprising the following steps:

Step 110, establish the MIB_AB file that standard MIB_A and standard MIB_B merge and obtain, and this MIB_AB file includes all OID nodes of standard MIB-A and standard MIB_B;

Since the MIB is a tree structure, it is only necessary to add the OID (Object Identifier: Object Identifier) node that is not in the MIB_B tree in the MIB_A tree to the MIB_B tree during fusion. OID node, MIB_B is the fused MIB_AB. There is an equivalence relationship between MIB_A and MIB_B. Adding OID nodes that are not in the MIB_A tree in the MIB_B tree to the MIB_A tree can also obtain the integrated MIB_AB.

Step 120, adding each OID node of the fusion MIB_AB into the MIB tree of the SNMP agent, and providing the processing function GET/SET for each OID node;

Step 130, according to the MIB standard supported by the network management environment that the SNMP agent needs to work, configure the configuration item MIB_CFG_STANDARD for identifying the MIB standard supported by the current SNMP agent through the configuration interface;

When the SNMP agent is connected to the SNMP manager MANAGER_A, set the configuration value of the configuration item MIB_CFG_STANDARD to A_MIB, indicating that the SNMP manager MANAGER_A uses the MIB_A standard MIB; when the SNMP agent is connected to the SNMP manager MANAGER_B When above, set the configuration value of the configuration item MIB_CFG-STANDARD to B_MIB, indicating that the SNMP manager MANAGER_B uses the MIB_B standard MIB.

Step 140, the SNMP manager MANAGER_A or MANAGER_B manages it through operations such as GET/SET of the OID nodes contained in MIB_A or MIB_B in the SNMP agent;

In this embodiment, the merged MIB_AB is transparent to the SNMP manager, and there is no need to make any changes to the SNMP manager.

Step 150, when the SNMP agent reports TRAP to the SNMP manager, recognize the MIB standard of the current configuration according to the configuration value of the current MIB_CFG_STANDARD, bind the OID in the standard to the TRAP message and report to the SNMP manager;

Step 160, when it is necessary to connect the SNMP agent to an SNMP manager that supports another MIB standard, it is only necessary to modify the configuration item MIB_CFG_STANDARD of the SNMP agent. Of course, the MIB standard used by the SNMP manager should be the merged MIB standard.

For example, when the SNMP agent is originally connected to the SNMP manager MANAGER_A and is changed to connect to the SNMP manager MANAGER_B, only need to modify the configuration value of the configuration item MIB_CFG_STANDARD of the SNMP agent through the configuration interface to B_MIB to make the SNMP agent work In the network management environment of SNMP manager MANAGER_B.

In another embodiment of the present invention, set up the MIB file that merges a plurality of standard MIBs in the SNMP agent, because be peer-to-peer tree relationship between each standard MIB, always can constantly combine the MIB of a plurality of standards It is convenient and feasible to combine multiple standard MIBs by synthesizing a fusion MIB. Correspondingly, in this embodiment, the MIB_CFG_STANDARD configuration item also adopts multiple configuration values to identify multiple MIBs of different standards, so that the SNMP agent can be used in a network management environment of multiple SNMP managers using different MIB standards. can work.

In summary, with the system and method of the present invention, when the SNMP agent works in different network management environments, the SNMP agent only needs to change the configuration value of the configuration item, without the need for an SNMP agent or SNMP network management upgrade or reboot.

Claims (4)

1. A method for realizing the fusion of agent-side multi-standard management information bases, comprising the following steps: (a) Establishing a fusion management information base obtained by merging multiple standard management information bases including all object identifier nodes of these standard management information bases; (b) adding each object identifier node of the fusion management information base to the management information base tree of the simple network management protocol agent, and providing a processing function GET/SET for each of the object identifier nodes; (c) according to the management information base standard supported by the network management environment where the agent needs to work, configuring configuration items for identifying the management information base standard currently supported by the agent; (d) When the agent reports the Trap message to the Simple Network Management Protocol manager, it recognizes the currently supported MIB standard according to the configuration value of the configuration item, and binds the object identifier in the standard to the Trap message reported to the manager. 2. The method according to claim 1, characterized in that, in the step (a), establishing the integrated management information base is based on any standard management information base tree in the plurality of standard management information bases , adding different object identifier nodes in standard MIB trees other than the basic standard MIB tree among the multiple standard MIB trees to the basic MIB tree . 3. The method according to claim 1, further comprising the step of: the manager identifies the object by operating the object identifier node contained in the MIB standard supported by the agent The symbol node is managed. 4. The method according to claim 1, characterized in that, when the agent needs to be connected to a simple network management protocol manager supporting another management information base standard, it is only necessary to modify the The configuration value of the configuration item identifies the configuration value of the another management information base standard.

Images