CN102387031A - Simple network management protocol (SNMP) network equipment identification and data acquisition method based on state machine - Google Patents

Abstract

The invention relates to a state machine-based SNMP network proxy device identification and data acquisition method. This method is used in the management software of related network devices to query and manage device information. Only through configuration files, SNMP community strings, MIB information databases, device identification processes, and device management processes can be flexibly configured in various device management processes. Relevant information, device agent identification and data acquisition. Thereby reducing the complexity of system implementation and maintenance, and improving the flexibility of the system and the compatibility of agents.

Description

SNMP Network Device Identification and Data Acquisition Method Based on State Machine

technical field

The invention relates to a data acquisition method applied to an active IP network device based on the SNMP (Simple Network Management Protocol, Simple Network Management Protocol) protocol. It is a method that can be flexibly configured to deal with the identification of different device agents and obtain relevant data.

Background technique

SNMP is currently the most widely used network management protocol in TCP/IP networks. It can be used in embedded systems and is used to exchange management information correctly between the management terminal and the agent. Using the SNMP protocol, a management terminal can remotely manage all network devices that support this protocol, including monitoring network status, modifying network device configuration, receiving network event alarms, etc. The SNMP protocol is built on the UDP (User Datagram Protocol, User Datagram Protocol) layer and is a high-level communication protocol.

Refer to Figure 1, which is a schematic diagram of the working mode of SNMP. The SNMP protocol adopts a management terminal/agent mode. For the management side, a unified network management interface is provided. Regardless of the number and types of agents, all agent data can be obtained only by interacting with the agents. All agent data is stored on the agent side in the form of OID (OBJECT IDENTIFIER, object identifier). These OIDs are recorded in the corresponding MIB (Management Information Base, Management Information Base) files, which describe the details of the data OID, including location, type, scope, allowed operations, and so on. The management terminal can clearly understand the OID information of the agent through the MIB file, and obtain relevant data.

The SNMP protocol has a variety of operation modes, including GET, GET-NEXT, GET-BULK, etc. Through different commands and OIDs, one or more data of the OID or the next OID can be obtained. At the same time, the SNMP protocol has the concept of Community (community string). An agent generally has two Communities, which identify different operation permissions, read-only permissions and read-write permissions. Only the management end that includes the same Community in the command has the relevant authority to read and write the agent.

At present, a large number of devices based on SNMP protocol are being used more and more, and the remote real-time management of such devices becomes very important. However, due to different manufacturers, the community strings, MIBs, and data acquisition methods among various device agents are different, resulting in no general method for device identification and data acquisition.

Contents of the invention

The technical problem to be solved by the present invention is to provide a state machine-based SNMP network device agent identification and data acquisition method, overcome the differences in community strings, MIBs and data acquisition between devices, and reduce the complexity of system implementation and maintenance. Improve system flexibility and agent compatibility.

In order to solve the above technical problems, the present invention adopts the following technical solutions:

A state machine-based SNMP network device agent identification and data acquisition method is used for the management end to send different orders to various agents to obtain data records therein, and the method comprises the following steps:

(1) The management side loads the configuration file in the file system and generates a state set;

(2) The management end sets the current state of the input IP address as the initial state;

(3) The management side loads the MIB data corresponding to the current state through the state set;

(4) The management side loads the transition conditions through the state set, obtains the type, community and OID of the sent command, and sends the command;

(5) The agent obtains the command and returns the corresponding data information;

(6) The management terminal obtains the command return packet, translates the data through the MIB, and compares the transition conditions. If the transition conditions are met, the current state is migrated to the corresponding next state;

(7) Repeat step 3 until the current state is set to the end state.

Further, the next state in step (6) is the same as the current state, that is, a state in the state set, which includes the type of the device, the corresponding community string, MIB file, OID of the query required by the migration condition, migration Information such as the type of query command required by the condition, the next state to be migrated if the migration condition is met, and so on.

It can be seen from the method and system in the above scheme that since the method of the present invention can effectively obtain a large number of different community strings, MIBs and data acquisitions contained in different device agents, it can effectively avoid the occurrence of different devices when managing different devices. The complexity brought by the difference to the system, all the relevant information is concentrated in the configuration file, the system can use a unified method to identify the device, which reduces the complexity of system implementation and maintenance, and improves the flexibility and flexibility of the system. Proxy Compatibility.

Description of drawings

Fig. 1 is the mode schematic diagram of SNMP;

Fig. 2 is method flowchart of the present invention;

Fig. 3 is a state machine diagram of the embodiment.

Detailed ways

The invention implements identification and data acquisition for various SNMP device agents by introducing a state machine, thereby managing the devices.

Preferred embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings.

Embodiment one: referring to Fig. 2, this state machine-based SNMP network device agent identification and data acquisition method are used for the management end to send different orders to various agents to obtain data records therein, and the described method comprises the following steps:

(1) The management side loads the configuration file in the file system and generates a state set;

(2) The management end sets the current state of the input IP address as the initial state;

(3) The management side loads the MIB data corresponding to the current state through the state set;

(4) The management side loads the transition conditions through the state set, obtains the type, community and OID of the sent command, and sends the command;

(5) The agent obtains the command and returns the corresponding data information;

(6) The management terminal obtains the command return packet, translates the data through the MIB, and compares the transition conditions. If the transition conditions are met, the current state is migrated to the corresponding next state;

(7) Repeat step 3 until the current state is set to the end state.

Further, the next state in step (6) is the same as the current state, that is, a state in the state set, which includes the type of the device, the corresponding community string, MIB file, OID of the query required by the migration condition, migration Information such as the type of query command required by the condition, the next state to be migrated if the migration condition is met, and so on.

Embodiment 2: Referring to FIG. 2 , which is a flow chart of the method of this example, the method includes the following steps. The device managed in this embodiment is an optical amplifier. The device type can be identified and the device data can be obtained.

Step 1: Manage files Load relevant configuration files to generate state sets. The status set includes information about the current device type, community string, MIB, and transition conditions. The status set in the embodiment is shown in Table 1.

Table 1

Step 2: Set the input IP address to the initial state, namely S0.

Step 3: Through the state set (that is, Table 1), load the MIB file. The current state is S0, so load the System file.

Step 4: Obtain transition conditions through the state set, the community is Public, the command method is Get, the node to be queried is sysName, and the corresponding OID is 1.3.6.1.2.1.1.5.0 according to the loaded MIB file. Send the corresponding command.

Step 5: The agent receives the command, compares the community to be correct, and returns the value corresponding to sysName as "A Device".

Step 6: After receiving the command return packet, the management end migrates the state of the IP address to the second state S1 according to the transition condition matching.

Step 7: Analyze the current state S1 according to the state set, and load the System and CommonMIB files.

Step 8: Obtain transition conditions through the state set, the community is Public, the command method is Get, the node to be queried is deviceType, and the corresponding OID is 1.3.6.1.4.1.10871.1.3.1 according to the loaded MIB file. 18.0, and send the corresponding command.

Step 9: The agent receives the command, compares the community to be correct, and returns the value corresponding to sysName as "oaDevice".

Step 10: The management terminal receives the command return packet, and according to the transition condition matching, the state of the IP address is transferred to the next state S3, and the device type is confirmed as an optical amplifier.

Step 11: Analyze the current state S1 according to the state set, and load the MIB files of System, Common, and oaDevice. And obtain the note condition, the transition condition here is Walk, that is, use the Get-Next command of SNMP to inquire until no such name is returned.

Step 12: After receiving the return value, translate all OID point information using the MIB file and save it. The transition condition of this state is special, and it is an unconditional migration. After the data is obtained, the state is directly migrated to S3, and so on.

Embodiment 3: The device is a special optical receiver, the community string is different from the MIB file, and the value cannot be obtained by using the Get-Next command, so only the Get method can be used in the data acquisition method. It can identify the device type, obtain the device data and alarm information.

Step 1: Manage files Load relevant configuration files to generate state sets. The status set includes information about the current device type, community string, MIB, and transition conditions. The status set in the embodiment is also shown in Table 1.

Step 2: Set the input IP address to the initial state, namely S0.

Step 3: Through the state set (that is, Table 1), load the MIB file. The current state is S0, so load the System file.

Step 4: Obtain transition conditions through the state set, the community is Public, the command method is Get, the node to be queried is sysName, and the corresponding OID is 1.3.6.1.2.1.1.5.0 according to the loaded MIB file. And send the corresponding command.

Step 5: The agent receives the command, the comparison group is incorrect, and there is no return value.

Step 6: The management terminal does not receive any command return packet, and according to the transition condition matching, the state of the IP address is migrated to the next state S4.

Step 7: Analyze the current state S4 according to the state set, and load the System file.

Step 8: Obtain transition conditions through the state set, the community is Public, the command method is Get, the node to be queried is sysName, and the corresponding OID is 1.3.6.1.2.1.1.5.0 according to the loaded MIB file. Send the corresponding command.

Step 9: The agent receives the command, compares the group to be correct, and returns the value corresponding to sysName as "B Device".

Step 10: The management terminal receives the command return packet, and according to the transition condition matching, the state of the IP address is migrated to the next state S5, and the equipment type is confirmed as a B-brand optical receiver.

Step 11: Obtain the transition conditions and related data inputPower and outputRF through the state set, translate and save the data through the MIB file. Jump to S6 unconditionally.

Step 12: Go through the state set, obtain the transition conditions, obtain the relevant data AlarmInfo, and translate and decode the MIB file to obtain and save the data. Jump to S5 unconditionally. so repeatedly.

Through the above steps, we can identify and acquire data for all SNMP-based network devices. Through this unified method, the complexity of system implementation and maintenance can be reduced, and the system's compatibility with agents can be improved. Certainly, the above-mentioned embodiments are not further limitations on the technical solution of the present invention, and any equivalent replacement or corresponding modification to the technical features of the present invention by those skilled in the art is still within the protection scope of the present invention.

Claims (1)

1. one kind based on the SNMP network equipment of state machine agency identification and data capture method, is used for management end and sends different commands to various agencies and obtain data record wherein, and described method may further comprise the steps:

Management end loads the configuration file in the file system and generate state set;

Management end is changed to initial state with the present status of the IP address of input;

Management end loads the pairing MIB data of present status through state set;

Management end loads the transition condition through state set, obtains the type, corporations and the OID that send order, the concurrent order of losing one's life;

The agency obtains order, and returns corresponding data information;

Management end obtains order and returns bag, through MIB data is translated, and through contrast transition condition, if satisfy transition condition, then the present status migration is corresponding next state;

Repeating step 3, state is changed to done state until now;

Further; Next state in the step (6) is identical with present status; Promptly be a kind of state in the state set, wherein comprise the kind of this equipment, pairing corporations string, mib file, the OID of the needed inquiry of transition condition, the needed inquiry command kind of transition condition, meet the information such as next state that transition condition then moves.

Images