WO2011160497A1

WO2011160497A1 - Method and system for upgrading management information base on simple network management protocol (snmp) agent

Info

Publication number: WO2011160497A1
Application number: PCT/CN2011/073668
Authority: WO
Inventors: 许振华; 李晋; 陈潇; 胡鹏
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-06-24
Filing date: 2011-05-04
Publication date: 2011-12-29
Also published as: CN102299814A; CN102299814B

Abstract

A method and system for upgrading a Management Information Base (MIB) on a Simple Network Management Protocol (SNMP) agent are disclosed by the present invention. The method includes the following steps: after a manager initiates the upgrade, the manager performs traversal operation on all the nodes in the local MIB of the manager and transmits a request to an agent; according to the received request, the agent judges that differences exist between the MIB on the manager and the local MIB of the agent, then reports the differences to the manager; according to the reported differences, the manager determines the nodes which need to be synchronized, constructs a corresponding patch and forwards the patch to the agent; the agent synchronizes the local MIB of the agent according to the received patch.

Description

Method and system for upgrading management information base on SNMP agent

Technical field

The present invention relates to the field of remote network management of devices based on the Simple Network Management Protocol (SNMP), and specifically relates to a method and system for upgrading a Management Information Base (MIB) on an SNMP agent. Background technique

The SNMP protocol is a set of network management protocols defined by the Internet Engineering Task Force. use

SNMP, a manager can remotely manage all network devices that support this protocol.

The SNMP management model has three basic components: Manager, Agent, and Management Information Base (MIB), where:

The Manager resides in the management device. The management device is usually a stand-alone device or a member of a shared network. The Manager is the interface between the network administrator and the network management system, and converts the commands of the network administrator from the SNMP protocol to the SNMP protocol. The message is delivered to the Agent residing on the managed device, and the parameters of the managed device are read or set by the MIB of the Agent.

Agents reside in managed devices and are special software or hardware used to track the status of managed devices. Each agent has its own local MIB. The Agent translates the protocol message request from the Manager, verifies the enforceability of the operation, searches the MIB, finds the corresponding device parameters, performs the request operation, and returns the response information to the Manager.

The MIB contains all of the operational objects on the managed device that can be queried and modified, as well as the operational functions that are allowed to be performed on those operational objects. From the organizational structure, all the operation objects are organized into an object tree, usually called MIB tree. As shown in Figure 1, the operation objects on the tree are called nodes, and each node is associated with several operation functions (such as Get, Set). , Get Next, etc., these operating functions are currently not unified Chinese terms), called the operation of the node.

In the actual application, the node information to be accessed by the Manager is sent to the Agent through the SNMP message, and the node information received by the agent finds the node in the local MIB tree, and according to the packet.

1 The operation specified in , calls a different operation function to achieve access to a parameter on the device.

Through the above description, the Manager must have the same structure as the MIB on the Agent, so that access to all MIB data on the Agent can be achieved. However, in actual use, the MIB needs to be upgraded due to changes in requirements, etc., as shown in Figure 2. Generally, the Manager is a PC and the physical location is centralized. Therefore, the MIB on the Manager can be easily upgraded. However, for the MIB above the Agent, it is very difficult to upgrade the MIB due to the geographical location of the Agent. In addition, when the Agent is an embedded system, the software system running on it is a whole. If the MIB needs to be upgraded, the entire software system needs to be upgraded.

In the prior art, the foregoing problems are solved by the following methods: 1) Presetting multiple sets of MIBs or a plurality of MIB fragments on the Agent, when upgrading the currently used MIB, abandoning the MIB being used, and using presets Other MIBs; 2) Add the required and locally existing MIB fragments to the MIB being used.

It can be seen that whether the preset MIB method is used or the preset MIB fragment method is used. The MIB nodes that can be upgraded are limited by the number of preset MIB sets or the number of preset MIB fragments. The flexibility of the MIB extension is poor, and the preset MIB information necessarily brings about data redundancy on the Agent.

Summary of the invention

The technical problem to be solved by the present invention is to provide an upgrade method and system for managing an information base on an SNMP agent, which can implement remote online upgrade of the MIB on the agent.

To solve the above technical problem, the present invention provides a Simple Network Management Protocol (SNMP) proxy management information base (MIB) upgrade method, including:

After the administrator initiates the upgrade, the administrator traverses all the nodes of the manager local MIB, sends a request to the agent, and the agent determines the MIB on the manager and the proxy local MIB according to the received request. If there is a difference, the difference is sent to the manager, the manager determines the node that needs to be synchronized according to the difference reported, constructs a corresponding patch, and delivers the patch to the agent, and the agent is configured according to The received patch synchronizes the proxy local MIB.

Optional, The manager's MIB and the agent's MIB each include a node as a patch control node, and the object identifiers (OIDs) of the two nodes are the same;

The method further includes: presetting the operation corresponding to the patch control node to indicate an action performed by the agent, and the one preset operation corresponds to one or more of the following actions: determining the MIB on the manager and the proxy local MIB The difference, get the patch, parse the patch, and synchronize the proxy local MIB based on the received patch.

Optional,

The manager traverses all nodes of the local MIB, and sends a request to the proxy: the manager sends one or more SNMP message requests to the proxy to associate the OID of each node in the manager local MIB with A corresponding operation type identifier is sent to the agent.

Optional,

The step of the agent determining, according to the received request, that the MIB on the manager is different from the proxy local MIB includes:

After receiving the SNMP message request, the proxy reads the OID and the operation type identifier carried in the message request, and the operation identified by the operation type identifier triggers the proxy to be a node, and determines and records the management. The difference between the MIB on the agent and the MIB on the agent.

Optional,

The administrator determines the nodes that need to be synchronized according to the difference reported, and the steps of constructing the corresponding patches include:

When the administrator determines, according to the difference reported, that the node that needs to be synchronized includes a newly added node and a deleted node, the patch constructed by the administrator includes a registry and an operation code target file associated with the registry, and the registration The table includes the OIDs of the nodes to be synchronized and the addresses of the corresponding n operations, n > 0 and n is an integer. For the node to be deleted, the number of addresses corresponding to the OID of the node is n=0, that is, The corresponding operation address is empty; for the node to be added, the number of operations corresponding to the OID of the node is n > 0, and the address of the operation points to an area in the operation code object file, where the The content of the updated operation; or

The administrator determines, according to the difference reported, that the node that needs to be synchronized includes only the newly added node, and the patch constructed by the administrator includes a registry and an operation code target text associated with the registry. The registry includes an OID of a plurality of nodes to be synchronized and an address of the corresponding m operations, m > 0 and m is an integer, and the address of the operation points to an area in the operation code object file. Where the content of the updated operation is saved; or

The administrator determines that the node to be synchronized includes only the deleted node according to the difference of the report, the patch constructed by the administrator includes a registry, and the registry includes multiple OIDs of the node to be deleted, and the corresponding operation address Is empty.

Optional,

The administrator sends the patch to the proxy, and the step of the proxy synchronizing the proxy local MIB according to the received patch includes:

The administrator instructs the agent to acquire a patch, parse the patch, and synchronize the proxy local MIB according to the received patch by operating the patch control node.

Optional,

The step of the administrator instructing the agent to acquire a patch, parse the patch, and synchronize the proxy local MIB according to the received patch by operating the patch control node includes:

The administrator sends one or more SNMP message requests to the proxy, where the SNMP message request includes an OID of the patch control node and an operation type identifier of a preset operation, and the agent receives the SNMP protocol message. Then, performing the corresponding action according to the operation type identifier carried therein, completing the process of obtaining the patch, parsing the patch, and synchronizing the proxy local MIB according to the received patch.

Optional,

1) the agent selects an OID from the registry in the patch as the currently synchronized OID;

2) determining whether the OID corresponding operation address in the registry is empty, if it is empty, deleting the node with the same OID in the local MIB; if not, determining whether the proxy local MIB has the same OID a node, if yes, reading an operation code object file according to an operation address corresponding to the OID, obtaining an update content, synchronizing a node having the same OID in the proxy local MIB, and if not, using the OID locally at the proxy Registering a new node in the MIB, synchronizing the operation corresponding to the new node according to the updated content read from the operation code object file; 3) Select an unsynchronized OID from the registry in the patch as the currently synchronized OID, and perform the above steps 2);

Repeat steps 2) and 3) above until the OIDs in the registry are all synchronized. Optional,

The step of the operation corresponding to the preset patch control node for indicating the action performed by the agent includes: presetting that the first operation corresponding to the patch control node is used to instruct the agent to obtain the patch, and the second operation is used to instruct the agent to parse the patch. The third operation is used to indicate that the agent synchronizes the local MIB according to the patch; the step of the administrator instructing the agent to acquire the patch, parse the patch, and synchronize the proxy local MIB according to the received patch by operating the patch control node includes:

When the manager instructs the agent to obtain a patch, the manager sends the agent to the agent

The SNMP message request includes an OID of the patch control node, an operation type identifier of the first operation, and a patch content; when the manager instructs the agent to parse the patch, the SNMP message request sent by the manager to the proxy Included in the OID of the patch control node and an operation type identifier of the second operation; when the manager instructs the agent to synchronize the proxy local MIB according to the received patch, the manager sends the identifier to the proxy The SNMP message request includes an OID of the patch control node and an operation type identifier of the third operation; the proxy performs a corresponding action according to the content carried by the received SNMP message request; or

When the manager instructs the agent to obtain a patch, the SNMP message request sent by the manager to the agent includes an OID of the patch control node, an operation type identifier of the first operation, and a patch content; When the administrator instructs the agent to parse the patch and synchronize the proxy local MIB according to the received patch, the SNMP message request sent by the administrator to the proxy includes the OID of the patch control node and the operation type identifier of the second operation. The agent performs a corresponding action according to the content carried by the received SNMP message request.

The present invention also provides an Simple Management Protocol (SNMP) agent management information base (MIB) upgrade system, including administrators and agents, wherein:

The administrator is configured to: after starting the upgrade, traverse all nodes of the manager local MIB, send a request to the proxy; and determine a node that needs to be synchronized according to the difference of the proxy, construct a corresponding patch and Delivering the patch to the agent; The proxy is configured to: determine, according to the received request, that the MIB on the manager is different from the proxy local MIB, report the difference to the administrator; and synchronize the received patch according to the received Proxy local MIB.

Optional,

The administrator includes: a first MIB unit, a sending unit, and a patch construction unit, where the first MIB unit is configured to: select any node in the manager MIB as a patch control node, where the patch control node corresponds to multiple operations, the predetermined operations for performing one or more actions indicative of agent: a difference between the agent on the local MIB MIB manager determines other acquisition patch ^1, patch parsing, and synchronization based on the received patch The proxy local MIB is configured to: traverse all nodes of the manager MIB after the upgrade is started, send a request to the proxy; and issue the patch based on the trigger of the patch construction unit To the agent;

The patch construction unit is configured to: after receiving the MIB difference reported by the proxy, determine a node that needs to be synchronized according to the difference, construct a corresponding patch, and trigger the sending unit;

The proxy includes a second MIB unit, a difference judging unit, an upper unit, and a synchronization unit, where the second MIB unit is configured to: select any node in the proxy MIB as a patch control node, where the proxy MIB is The object identifier (OID) of the patch control node is the same as the OID of the patch control node in the manager MIB, and the node corresponds to a plurality of operations, and the operation is preset to perform one or more of the following actions: The difference between the MIB of the manager and the proxy local MIB, obtaining a patch, parsing the patch, and synchronizing the proxy local MIB according to the received patch;

The difference judging unit is configured to: after receiving the request sent by the sending unit of the manager, determining, according to the request, that the MIB on the manager is different from the proxy local MIB, collecting the difference and triggering the upper unit ;

The reporting unit is configured to: report the difference to the manager based on a trigger of the difference determining unit;

The synchronization unit is configured to: after receiving the patch sent by the sending unit of the manager, synchronize the proxy local MIB according to the patch. Optional,

The sending unit is configured to send a request to the proxy in the following manner: Send one or more SNMP message requests to the proxy to send the OID of each node in the administrator local MIB and its corresponding operation type identifier to the Agent

The difference judging unit is configured to: trigger the operation corresponding to the operation type identifier carried in the message request, and determine and record the difference between the manager MIB and the proxy MIB in units of nodes.

Optional,

The patch construction unit is configured to construct a corresponding patch in the following manner:

When determining that the node that needs to be synchronized includes a new node and a deleted node, constructing a patch including a registry and an operation code object file associated with the registry, where the registry includes an OID of a plurality of nodes to be synchronized and The address of the corresponding n operations, n > 0 and n is an integer; for the node to be deleted, the number of addresses of the operation corresponding to the OID of the node is η=0, that is, the corresponding operation address is empty; Node, the number of addresses of the operation corresponding to the OID of the node n > 0, and the address of the operation points to an area in the operation code object file, where the content of the updated operation is saved; or

When determining that the node that needs to be synchronized includes only the newly added node, constructing a patch including a registry and an operation code object file associated with the registry, the registry including the OIDs of the plurality of nodes to be synchronized and their corresponding The address of m operations, m > 0 and m is an integer, the address of the operation points to an area in the operation code object file, in which the content of the updated operation is saved; or

When the node that needs to be synchronized includes only the deleted node, the patch includes a registry, and the registry includes multiple OIDs of the node to be deleted, and the corresponding operation address is empty.

Optional,

The sending unit is configured to send a request to the proxy in a manner of: sending one or more SNMP message requests to the proxy, where the SNMP message request includes an OID of the patch control node and an operation of a preset operation Type identifier

The synchronization unit is configured to receive the SNMP protocol message, according to the operation carried therein The type identification performs the following actions: obtaining a patch, parsing the patch, and synchronizing the proxy local MIB according to the received patch.

The invention realizes the upgrade of the MIB on the Agent through the "patch" method has the following advantages:

1) "Patch" can be produced by borrowing other platforms (such as PC) without Agent participation;

2) Flexible extension of the MIB can be achieved by making different "patches";

3) The remote online upgrade of the MIB on the Agent can be implemented, which is more concise and flexible than the existing methods. BRIEF abstract

Figure 1 is a schematic diagram of an MIB tree in SNMP network management;

FIG. 2 is a schematic diagram showing that the MIB of the Manager and the Agent are different, and the upgrade requirement is triggered; FIG. 3 is a flowchart of an embodiment of the present invention;

4 is a structural diagram of a "patch" according to an embodiment of the present invention. Preferred embodiment of the invention

Since the MIB has a "tree" structure from the organizational structure, upgrading the MIB means adding several nodes and their corresponding operations to the MIB, or deleting several nodes and their corresponding operations from them. Therefore, the present invention considers the node of the extension part and its operation as a "patch", and the Manager dynamically enables or deletes the patch by the control agent to implement the upgrade of the MIB on the agent.

The inventive concept of the present invention is: After the Manager starts the upgrade, the Manager traverses all the nodes of the local MIB, sends a request to the Agent, and the Agent determines, according to the received request, whether the MIB on the Manager is different from the local MIB, and if there is a difference, The difference is reported to the manager, and the manager determines the node that needs to be synchronized according to the reported difference, constructs a corresponding patch, and delivers the patch to the agent, and the agent synchronizes the local MIB according to the received patch. If there is no difference, the upgrade process ends.

Preferably, when designing the MIB (including the MIB of the Manager and the MIB of the Agent),

8 Select one of the nodes as the patch control node, that is, the MIB of the Manager and the Agent each include a node as a patch control node, and the OID of the node in the Manager is the same as the OID in the agent; the patch control node is preset. The corresponding operation is used to indicate the action performed by the agent. One preset operation corresponds to one or more actions: determining whether the MIB on the Manager is different from the local MIB, obtaining a patch, parsing the patch, and synchronizing the local MIB according to the received patch. .

The agent sends the patch to the agent, and the step of the agent synchronizing the local MIB according to the received patch includes: the Manager instructs the agent to obtain a patch, parse the patch, and synchronize the local MIB according to the received patch by operating the patch control node. . Optionally, the manager sends one or more SNMP message requests to the agent, where the SNMP message request includes an OID of the patch control node and an operation type identifier of a preset operation, and the agent receives the SNMP protocol. After the message is executed, the corresponding action is performed according to the operation type identifier carried therein, and the process of obtaining the patch, parsing the patch, and synchronizing the local MIB according to the received patch is completed.

Specifically, the patch control node corresponds to a plurality of operations, and the first operation corresponding to the patch control node is used to instruct the agent to obtain a patch, the second operation is used to instruct the agent to parse the patch, and the third operation is used to instruct the agent to perform the patch according to the patch. The local MIB is synchronized; when the manager instructs the agent to obtain the patch, the SNMP message request sent by the manager to the agent includes an OID (Object Identifiers) of the patch control node, an operation type identifier of the first operation, and The content of the patch is: when the manager instructs the agent to parse the patch, the SNMP message request sent by the manager to the agent includes the OID of the patch control node and the operation type identifier of the second operation; when the manager instructs the agent to receive the When the patch is synchronized with the local MIB, the SNMP protocol message sent by the Manager to the agent includes the OID of the patch control node and the operation type identifier of the third operation. After receiving the SNMP message request, the agent performs the corresponding action according to the content carried in the received SNMP message request.

The first operation, the second operation, and the third operation may be the same or different, and the action of the agent may be specified in the process of the agent when the operation type identifier is received, but it needs to be uniformly set with the manager.

Preferably, the Manger can indicate that the Agent performs two or more actions according to an operation type identifier, for example, the Manager sends the OID of the patch control node and the operation type identifier of the second operation, and the operation type identifier of the second operation instructs the Agent to parse the patch. And synchronize the local MIB, at this time The second operation is considered to be the same as the third operation. The process of the traversal operation of all the nodes of the local MIB, the sending of the request to the agent includes: the manager sending one or more SNMP message requests to the agent, to the OID of each node in the Manager local MIB and a corresponding operation thereof The operation type identifier of X is sent to the Agent. Preferably, when there are m nodes in the Manager local MIB, the Manager sends m SNMP message requests to the Agent, and each message request carries the OID of one node and the operation type identifier of the corresponding operation X.

The operation X corresponding to the patch control node is used to indicate that the agent determines whether the MIB on the Manager is different from the local MIB. The step of determining, by the agent, whether the MIB on the Manager is different from the local MIB according to the received request includes: After receiving the message request, the agent reads the OID and the operation type identifier carried in the message request, and the operation type identifier that is identified by the operation type identifier triggers the agent to determine and record the first MIB and the second by using a node as a unit. The difference between the MIB and the specificity includes: the agent determines whether the local MIB has the same OID as the OID in the message request, and if so, determines that the local node has no difference from the node on the Manager, and if not, determines the local node and the Manager. The nodes on the difference are different, and the difference is recorded. After determining the OID in all the message requests, it is determined whether there are any nodes in the local MIB that have not been compared, and if so, it is determined that the node has a node with the Manager. Difference, and record the difference, if not, judge the operation is over. Preferably, the difference recorded by the Agent includes the node OID.

Preferably, the difference can be classified: including MIB nodes that exist on the Manager but do not exist locally, and MIB nodes that exist locally but do not exist on the Manager.

According to different situations, the patch constructed by the Manager includes different contents, which are as follows:

1) The synchronization operation includes adding a node and deleting a node, that is, when the manager determines, according to the difference reported, that the node to be synchronized includes a newly added node and a deleted node, the patch includes a registry and is associated with the registry. The operating code object file, the registry includes an OID of a plurality of nodes to be synchronized and an address of the corresponding n operations (n > 0, and n is an integer), and for the node to be deleted, the OID of the node corresponds to When the number of addresses of the operation is n=0, that is, the corresponding operation address is empty; for the node to be added, the number of addresses of the operation corresponding to the OID of the node is n>0, and the address of the operation points to the An area in the operation code object file in which the content of the updated operation is saved (the content is given in the form of object code), and the node corresponding to the OID represents the operation

10 The work needs to be updated or the node needs to be added.

2) When the synchronization operation only includes adding a new node, that is, when the management determines that the node to be synchronized includes only the newly added node according to the difference reported, the patch includes a registry and an operation code object file associated with the registry. The registry includes an OID of a plurality of nodes to be synchronized and an address of the corresponding m operations (m>0, and n is an integer), and the address of the operation points to a region in the operation code object file , where the content of the updated operation is saved (the content is given in the form of object code).

If the OIDs are the same but the corresponding operations are different, they can be updated according to the process of adding a new node.

3) The synchronization operation includes only deleting the node, that is, when the management determines that the node to be synchronized includes only the deleted node according to the reported difference, the patch includes a registry, and the registry includes multiple OIDs of the node to be deleted. , its corresponding operation address is empty.

The step of synchronizing the agent local MIB according to the patch includes: 1) the agent selects an OID from the registry in the patch as the currently synchronized OID; 2) determines whether the OID corresponding operation address in the registry is empty, and if it is empty, Then, the node with the same OID in the local MIB is deleted. If it is not empty, it is determined whether there is a node with the same OID in the local MIB. If yes, the operation code object file is read according to the operation address corresponding to the OID, and an update is obtained. Content, synchronizes the node with the same OID in the local MIB, if not, registers a new node in the local MIB with the OID, and synchronizes the operation corresponding to the new node according to the updated content read from the operation code object file; Then, select an unsynchronized OID from the registry in the patch as the currently synchronized OID, and perform the above steps 2); repeat the above steps 2) and 3) until the OIDs in the registry are all synchronized.

The registry is designed to achieve flexible configuration of dynamically extended nodes. The patch control node is extended according to the MIB node in the registry, and the MIB node does not exist in the registry, even if the operation code of the MIB exists in the operation code object file. , will not expand.

The system that implements the above upgrade method, including Manager and Agent, where:

The Manager is configured to: after the upgrade is started, the Manager traverses all nodes of the local MIB to send a request to the Agent; and is used to determine a section to be synchronized according to the difference reported by the Agent.

11 Point, construct the corresponding patch and deliver the patch to the Agent;

The agent is configured to determine, according to the received request, whether the MIB on the Manager is different from the local MIB, and if there is a difference, report the difference to the Manager; and synchronize the local MIB according to the received patch.

Preferably, the manager includes: a first MIB unit, a sending unit, and a patch construction unit, where:

The first MIB unit is configured to select any node in the MIB (first MIB) of the Manager as a patch control node, where the patch control node corresponds to multiple operations, and the operation is preset to instruct the agent to execute the following one. Or multiple actions: determining whether the MIB on the Manager is different from the local MIB, obtaining a patch, parsing the patch, and synchronizing the Agent local MIB (second MIB) according to the received patch;

The sending unit is configured to: traverse all the nodes of the first MIB, and send a request to the agent after starting the upgrade; and send the patch to the agent based on the trigger of the patch construction unit;

The patch construction unit is configured to: after receiving the MIB difference reported by the agent, determine a node that needs to be synchronized according to the difference, construct a corresponding patch, and trigger the sending unit;

Preferably, the agent includes a second MIB unit, a difference determining unit, a reporting unit, and a synchronization unit, where:

The second MIB unit is configured to select any node in the second MIB as the patch control node, where the OID of the patch control node of the second MIB is the same as the OID of the patch control node in the first MIB, where the node corresponds to a plurality of operations, the operation is preset to perform one or more of the following actions: determining whether the MIB on the Manager is different from the local MIB, obtaining a patch, parsing the patch, and synchronizing the local second MIB according to the received patch;

The difference judging unit is configured to: after receiving the request sent by the sending unit of the Manager, determine, according to the request, whether there is a difference between the first MIB on the Manager and the local second MIB, and if there is a difference, collect the difference and Trigger the upper unit;

The reporting unit is configured to report the difference to the trigger based on the difference determining unit

12 The Manager;

The synchronization unit is configured to synchronize the local second MIB according to the patch after receiving the patch sent by the sending unit of the Manager.

Preferably, the sending unit, the request sent to the agent includes one or more SNMP message requests, to send the OID of each node in the first local MIB of the Manager and its corresponding operation type identifier to the Agent;

The difference judging unit is configured to determine, according to the trigger of the operation corresponding to the operation type identifier carried in the message request, the difference between the first MIB and the second MIB by using a node; the difference includes: MIB nodes that exist on the local but do not exist locally, and MIB nodes that exist locally but do not exist on the Manager. A form of the determining operation is: determining whether the local second MIB has the same OID as the OID in the message request, and if so, determining that the local node has no difference from the node on the Manager, and if not, determining the local node Different from the node on the Manager, and record the difference; After judging the OID in all the message requests, it is determined whether there are any nodes in the local MIB that have not been compared, if any, it is determined that the node and the node on the Manager have Difference, and record the difference, if not, judge the operation is over.

Preferably, the patch construction unit, when determining that the node that needs to be synchronized includes a newly added node and a deleted node, the configured patch includes a registry and an operation code target file associated with the registry, where the registry includes The OID of the node to be synchronized and the address of the corresponding n operations, n > 0 and n is an integer; for the node to be deleted, the number of addresses corresponding to the OID of the node is n=0, that is, its corresponding The operation address is empty; for the node to be added, the number of addresses of the operation corresponding to the OID of the node is n > 0, and the address of the operation points to an area in the operation code object file, where the update operation is saved. Content; or

The patch construction unit, when determining that the node that needs to be synchronized includes only the newly added node, the constructed patch includes a registry and an operation code target file associated with the registry, where the registry includes a plurality of nodes to be synchronized. The address of the OID and its corresponding m operations, m > 0 and m is an integer, the address of the operation points to an area in the operation code object file, where the update is saved

13 The content of the operation; or

The patch construction unit, when the node that needs to be synchronized only includes the deleted node, includes a registry, and the registry includes multiple OIDs of the node to be deleted, and the corresponding operation address is empty.

Preferably, the sending unit is configured to send one or more SNMP message requests to the agent, where the SNMP message request includes an OID of the patch control node and an operation type identifier of a preset operation;

The synchronization unit is configured to: after receiving the SNMP protocol message, perform the following actions according to the operation type identifier carried in the identifier, obtain a patch, parse the patch, and synchronize the local second MIB according to the received patch.

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

As shown in FIG. 3, a patch control node is preset in the MIB design. In addition to the operations of the general MIB node, the node also has the function of controlling the MIB upgrade process on the Agent, including the MIB difference between the Agent and the Manager. The transmission, the transmission of the patch, and the notification agent are synchronized according to the patch; the methods for implementing the MIB upgrade include:

Step 1: The Manager activates the patch process on the agent, that is, the agent sends a notification to enter the patch process.

Step 2: The Agent sends a response to the Manager that has entered the patch process;

Step 3: The traversal operation of the local MIB by the Manager sends an SNMP request to the Agent, including the node OID and the corresponding operation type identifier.

Step 4: After the agent receives the request sent by the manager, the operation triggered by the operation type identifier triggers the agent to compare the difference between the local MIB of the agent and the MIB of the manager. The agent collects the difference and reports the difference to the manager. The difference includes the manager. An MIB node that exists on the local but does not exist locally, and an MIB node that exists locally but does not exist on the Manager;

Step 5: The Manager creates a corresponding patch according to the difference between the Agent local MIB of the Agent and the MIB on the Manager, and sends the patch to the Agent by operating the patch control node.

14 The patch structure is as shown in FIG. 4, and includes: an operation code object file of the MIB node to be synchronized, and an OID of the MIB node to be synchronized and a registry of the corresponding operation. Each entry in the registry corresponds to the OID and its various operations. As described above, when the operation address corresponding to the OID is empty, it indicates that the agent needs to delete the node. If the operation address corresponding to the OID is not empty, it indicates that the agent needs to update the node. Figure 4 given in this embodiment is merely an example.

Step 6: After the agent receives the patch successfully, the agent sends the trap message in the form of a trap, and the Manager is notified that the packet is successfully received.

Step 7: The Manager operates the patch control node, and starts the operation of the Agent to resolve the "patch"; Step 8: The agent parses the patch, and synchronizes the local MIB according to the patch;

Specifically, the registry in the patch is read (structure is shown in FIG. 4), and the registry is traversed to extract the OID of each node and the object code information of the related operation.

Taking the newly added node as an example, the agent registers the parsed node OID to the corresponding branch in the existing MIB, and constructs a node structure for attaching the OID according to the data structure of the node in the local MIB. Operation code. If the node OID that the agent resolves exists in the local MIB, the local node is updated in the overlay mode.

Step 9: After the synchronization is complete, the agent notifies the Manager that the newly added node OID is completed in the form of a trap.

Step 10: The Manager operates the patch control node to notify the agent that the patch process ends.

The foregoing describes an example of a method for remotely upgrading an MIB in an agent by using a "patch" technology. It can be seen that the method proposed by the present invention does not need to be re-established by the MIB of the management device agent in the near-end network. To make and replace, you only need to add a small amount of support mechanism in the "patch" mode on the Agent to realize the flexible upgrade of MIB, which has strong practicability.

One of ordinary skill in the art will appreciate that all or a portion of the steps above may be accomplished by a program to instruct the associated hardware, such as a read-only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each unit in the above embodiment can use hardware

15 The form of the implementation can also be implemented in the form of software functional modules. The invention is not limited to any specific form of combination of hardware and software.

The invention may, of course, be embodied in various other forms and modifications without departing from the spirit and scope of the invention.

In addition, the present invention may also have other improved methods, such as modification of the "patch" program making method, modification of the patch acquiring method, etc., but these corresponding changes and modifications should be protected by the appended claims. range.

Industrial applicability

2) Flexible extension of the MIB can be achieved by making different "patches";

3) The remote online upgrade of the MIB on the Agent can be implemented, which is more concise and flexible than the existing methods.

16

Claims

Claim

1. A Simple Network Management Protocol (SNMP) agent management information base (MIB) upgrade method, including:

2. The method of claim 1 wherein

The manager's MIB and the agent's MIB each include a node as a patch control node, and the object identifiers (OIDs) of the two nodes are the same;

3. The method according to claim 1, wherein the step of the administrator traversing all nodes of the local MIB and sending the request to the proxy comprises:

The manager sends one or more SNMP message requests to the agent to send the OID of each node in the administrator's local MIB and its corresponding operation type identifier to the agent.

4. The method according to claim 3, wherein the step of the agent determining, according to the received request, that the MIB on the manager is different from the proxy local MIB comprises:

5. The method according to claim 1, wherein the manager determines the node to be synchronized according to the difference reported, and the step of constructing the corresponding patch includes:

The administrator determines, according to the difference reported, that the node that needs to be synchronized includes a newly added node and a deleted node, and the patch constructed by the administrator includes a registry and an operation generation associated with the registry.

17 a code object file, the registry includes an OID of a plurality of nodes to be synchronized and an address of the corresponding n operations, n > 0 and n is an integer; for the node to be deleted, an address of the operation corresponding to the OID of the node The number n=0, that is, the corresponding operation address is empty; for the node to be added, the number of addresses of the operation corresponding to the OID of the node is 11 > 0, and the address of the operation points to the operation code object file An area in which the contents of the updated operation are stored; or

The administrator determines, according to the difference reported, that the node that needs to be synchronized only includes the newly added node, the patch constructed by the administrator includes a registry and an operation code target file associated with the registry, where the registry includes An OID of a plurality of nodes to be synchronized and an address of the corresponding m operations, m > 0 and m is an integer, and the address of the operation points to an area in the operation code object file, where the content of the updated operation is saved ; or

The method of claim 1, wherein the manager sends the patch to the agent, and the step of the agent synchronizing the proxy local MIB according to the received patch includes:

7. The method according to claim 6, wherein the step of the administrator instructing the agent to acquire a patch, parse the patch, and synchronizing the proxy local MIB according to the received patch by operating the patch control node includes:

8. The method according to claim 5 or 6 or 7, wherein the step of the agent synchronizing the proxy local MIB according to the patch comprises:

18 2) determining whether the OID corresponding operation address in the registry is empty, if it is empty, deleting the node with the same OID in the local MIB; if not, determining whether the proxy local MIB has the same OID a node, if yes, reading an operation code object file according to an operation address corresponding to the OID, obtaining an update content, synchronizing a node having the same OID in the proxy local MIB, and if not, using the OID locally at the proxy Registering a new node in the MIB, synchronizing the operation corresponding to the new node according to the updated content read from the operation code object file;

3) Select an unsynchronized OID from the registry in the patch as the currently synchronized OID, and perform the above steps 2);

Repeat steps 2) and 3) above until the OIDs in the registry are all synchronized. 9. The method according to claim 6 or 7, wherein

When the manager instructs the agent to obtain a patch, the SNMP message request sent by the manager to the agent includes an OID of the patch control node, an operation type identifier of the first operation, and a patch content; When the administrator instructs the agent to parse the patch, the SNMP message request sent by the manager to the agent includes an OID of the patch control node and an operation type identifier of the second operation; when the manager indicates the agent When the proxy local MIB is synchronized according to the received patch, the SNMP message request sent by the administrator to the proxy includes an OID of the patch control node and an operation type identifier of the third operation; the proxy receives the The content carried by the SNMP message request performs the corresponding action; or

When the manager instructs the agent to obtain a patch, the SNMP message request sent by the manager to the agent includes an OID of the patch control node, an operation type identifier of the first operation, and a patch content; When the administrator instructs the agent to parse the patch and synchronize the proxy local MIB according to the received patch, the SNMP message request sent by the administrator to the proxy includes the OID of the patch control node and the operation type identifier of the second operation. The agent is received according to

19 The content carried by the SNMP message request performs the corresponding action.

10. A Simple Management Protocol (SNMP) agent management information base (MIB) upgrade system, including managers and agents, where:

The administrator is configured to: after starting the upgrade, traverse all nodes of the manager local MIB, send a request to the proxy; and determine a node that needs to be synchronized according to the difference of the proxy, construct a corresponding patch and Delivering the patch to the agent;

The proxy is configured to: determine, according to the received request, that the MIB on the manager is different from the proxy local MIB, report the difference to the administrator; and synchronize the received patch according to the received Proxy local MIB.

11. The system of claim 10, wherein

The manager includes: a first MIB unit, a sending unit, and a patch construction unit,

The first MIB unit is configured to: select any node in the manager MIB as a patch control node, where the patch control node corresponds to multiple operations, and preset the operation to instruct the agent to perform one or more of the following Action: determining a difference between the MIB on the manager and the proxy local MIB, acquiring a patch, parsing the patch, and synchronizing the proxy local MIB according to the received patch;

The sending unit is configured to: after starting the upgrade, traverse all the nodes of the manager MIB, send a request to the agent; and deliver the patch to the agent based on the trigger of the patch construction unit;

The difference judging unit is configured to: receive a request sent by the sending unit of the manager

20 After determining, according to the request, the MIB on the manager is different from the proxy local MIB, collecting the difference and triggering the upper unit;

The synchronization unit is configured to: after receiving the patch sent by the sending unit of the manager, synchronize the proxy local MIB according to the patch.

12. The system of claim 11 wherein:

13. The system according to claim 11, wherein the patch construction unit is configured to construct a corresponding patch in the following manner:

When determining that the node that needs to be synchronized includes only the deleted node, construct a patch including the registry.

twenty one The registry includes multiple OIDs of the node to be deleted, and the corresponding operation address is empty.

14. The system of claim 13 wherein

The synchronization unit is configured to perform the following actions according to the operation type identifier carried in the SNMP protocol message: obtaining a patch, parsing the patch, and synchronizing the proxy local MIB according to the received patch.

twenty two