CN102185703B - A kind of network equipment management method and main equipment based on SNMP protocol - Google Patents

Abstract

The invention relates to a network device management method based on an SNMP protocol and a primary device. The method is characterized in that the primary device reads and analyzes a device template file and a device instance file, integrates the information, such as a device name, a device ID, a template ID, a signal ID and a control ID, in the two files according to the template ID and then saves in an integrated information array, generates an MIB file and a mapping relational file according to the data in the information array and uploads the generated MIB file to a network management center; and during the management operation, the primary device receives an SNMP protocol message sent by the network management center, extracts an OID and an operational order in the message, seeks a corresponding sub-device through the mapping relational file and performing the corresponding operational order for completing the management operation. The primary device in the invention is the primary device for implementing the above-mentioned method. The method and device in the invention realize dynamic update of the MIB file in the network device management, improve management efficiency and have evident advantages.

Description

A kind of network equipment management method and main equipment based on SNMP protocol

technical field

The invention relates to the field of SNMP network management, in particular to a method for managing network equipment based on the SNMP protocol and its main equipment.

Background technique

With the development of networking, more and more devices and solutions need to provide SNMP protocol support to access the network, so that the center can be managed through a unified SNMP protocol. In the SNMP network management system, the managed data variables of the managed devices are abstracted into objects, and the collection of managed objects is organized as a management information base (MIB) and stored in the main device (AGENT). An object identifier (OID) is given in the MIB, and the network management system (NMS) locates the managed object through the OID, and realizes the management of the sub-device by reading and modifying the value of the object in the MIB. Among them, the master device also uses the TRAP message report to report important events to the NMS.

In SNMP network management, all managed resources need to be abstracted and recorded in MIB. With the development of technology, the number of devices in SNMP network management increases, and the addition and replacement of devices become more frequent. It is necessary to update the MIB file and install and debug the device. In the prior art, the MIB file in the main device generally cannot be dynamically updated, but requires complex writing, debugging, etc., and the management efficiency is low.

Contents of the invention

The technical problem to be solved by the present invention is to provide a network device management method based on the SNMP protocol, which can realize dynamic updating of MIB files.

Another technical problem to be solved by the present invention is to provide a master device of a network device management system based on the SNMP protocol. When the master device accesses a new managed sub-device or receives an instruction, it can Data files generate or update MIB files in time to realize compatibility and management of devices.

In order to solve the above-mentioned first technical problem, the present invention provides a network device management method based on the SNMP protocol, the master device communicates with the network management center through the SNMP protocol and executes the operation instructions of the network management center to the sub-equipment, including the following steps:

A. The master device reads and parses the device template and the device instance file in the memory of the master device, and matches and integrates the device template and the sub-device information in the device instance file into the integrated information array;

B. The master device generates or updates the MIB file and the mapping relationship file in the master device according to the data in the integrated information array, and the mapping file is used to record the OID, device ID and signal ID of the leaf node in the MIB file, and control ID mapping relationship;

C. The main device uploads the MIB file to the network management center and receives the SNMP protocol message sent by the network management center, extracts the OID and operation instructions in the message, and searches for the corresponding MIB file according to the extracted OID and the mapping relationship file. The sub-device of the sub-device executes the corresponding operation instruction on the sub-device.

Due to the adoption of the above steps, when a new sub-device is connected to the management system or receives an administrator instruction, the method can dynamically update the MIB file in real time through the device template in the main device and the data in the instance information file Or generate a new MIB file, so as to quickly realize the management of the sub-device, simplify the device debugging process, and improve the efficiency of network management. Especially in remote management, this method can quickly realize the access of new devices.

As an implementation form of the method of the present invention, in step A, the sub-device information in the device template includes: the template ID and the signal ID and control ID of the corresponding sub-device; the sub-device information in the device instance file includes: Template ID and device ID; the main device matches and integrates the device template and the sub-device information in the device instance file through the template ID.

Preferably, the integrated information array also includes the following information: sub-device name, number of signals, number of controls, the number of signals and number of controls respectively represent the number of signals and the number of controls contained in the sub-device . As a further preferred solution, signal name and control name information are also included.

Preferably, the mapping relationship file also includes management type information, and the management type information is used to determine whether the corresponding OID leaf node is a signal or control in the corresponding sub-device. This preferred solution can optimize the table of the mapping relationship file structure, which makes the mapping relationship file structure simpler.

Like the existing SNMP network management, the master device of the present invention also informs the network management center of the abnormal event of the sub-device, and the abnormal event is transmitted to the network management center through a message report in a fixed format.

In order to solve the foregoing second technical problem, the present invention provides a main device of a network device management system based on the SNMP protocol, including a management program module and a MIB module, wherein the MIB module contains MIB files, and is characterized in that: it also includes data File module, MIB generation module, described data file module comprises equipment template and equipment instance file, is recorded in the information of all signal IDs and control ID of corresponding sub-equipment in the described equipment template; Described equipment instance file is used for recording and master The sub-device information actually connected to the device;

The MIB generation module is used to read the information of the device template and the device instance file, match and integrate it and store it in the integrated information array, and generate a MIB file according to the integrated information array and send it to the MIB module or update An existing MIB file in the MIB module.

Preferably, the device template is assigned a template ID, and the sub-device information includes the template ID of the device template applicable to the sub-device; the MIB generation module matches the information of the device template and the device instance file through the template ID .

Preferably, the MIB module also includes a mapping relationship file, and the mapping relationship file is used to record the mapping relationship between the OID of the leaf node in the MIB file and the device ID, signal ID, and control ID; the MIB generation module according to the The integrated information array generates the mapping relationship file or updates the mapping relationship file.

Preferably, the mapping relationship file includes management type information, and the management type information is used to indicate that the corresponding OID leaf node is a signal or control in the corresponding sub-device.

The beneficial effect of the network device management device based on the SNMP protocol of the present invention is that when an administrator instruction is received or the device detects that a new sub-device is connected, the master device can dynamically update the MIB and the mapping relationship file in time, Improve network management efficiency.

Description of drawings

Fig. 1 is a schematic diagram of the device connection relationship of a specific embodiment of the present invention;

Fig. 2 is a flow diagram of network management in a specific embodiment of the present invention;

Fig. 3 is a schematic diagram of the data structure of the mapping relationship file raw.cfg table according to the specific embodiment of the present invention.

Detailed ways

In order to illustrate the present invention in more detail, the present invention will be described below in conjunction with specific embodiments.

As shown in FIG. 1 , it is a schematic diagram of the device connection relationship in this specific embodiment.

The network device management system based on the SNMP protocol of this specific embodiment includes a network management center (NMS), a master device, a temperature sensor, a UPS (in practical applications, more sub-equipment can be included); the NMS and The main equipment is connected, the temperature sensor and the UPS are respectively connected to the main equipment through the 232 interface and the RS485 interface, and the NMS communicates with the main equipment through the SNMP protocol. Among them, each sub-device (such as temperature sensor, etc.) is designed with its own device template based on XML format. The template contains elements such as signal, control and event. Each template has a template ID number, and the signal and control also have their own ID number.

The master device also includes a MIB generating module and a data file module, wherein the data file module includes a device template type file and a device instance file, and the device template type file includes the device templates of all sub-devices supported by the master device ( The beginning of the file name is EquipmentTemplate, and the file is in XML format), and the information in the equipment template includes: template ID and the number of signals of corresponding sub-equipment, signal ID and signal name; control number, control ID and control name. Described device instance file is also the file of XML form (the beginning of file name is MonitorUnits, hereinafter referred to as MU file), and MU file is used for recording the device ID of the sub-device that is connected with master device in the actual operation environment, device name and used for Specifies the template ID of which device template applies to this sub-device.

Include a MIB generation application program in the described MIB generation module, when receiving the administrator's operation instruction or detecting that new sub-equipment is connected to the master device, the MIB generation module runs the MIB generation application program, and the MIB generation application program The operation process of the system is shown in Figure 2, and the temperature sensor and UPS power supply are used as examples for a specific description below:

Program operation, the first step: first read the storage directory of the data file module and the output directory to generate MIB files and mapping relationship files (file name is raw.cfg);

Step 2: Read all the equipment templates and MU files in the data file module according to the file name (that is, when the file name starts with EquipmentTemplate and the file format is in XML format, it is regarded as an equipment template, the file starts with MonitorUnits, and the file format is in XML format, then considered as MU files), where the file names of the temperature sensor and UPS power supply templates are EquipmentTemplateIDU_S.xml and EquipmentTemplate Libert Anson Three-Input Single-Output UPS(UH31).xml respectively; the file name of the MU file is MonitorUnitsIDU_S2.xml .

Step 3: Parse the MonitorUnitsIDU_S2.xml file, obtain the device ID, device name and device template ID data stored in the file, and store this data in the template information array.

Step 4: Analyze the EquipmentTemplateIDU_S.xml and EquipmentTemplate Libert Anson Three-Input Single-Output UPS(UH31).xml files, extract the equipment template ID, signal, control or event ID in the above two files, and store them in the equipment information array.

Step 5: According to the common data template ID in the template information array and the device information array, match the data in the two arrays one by one, and integrate the data in the two arrays into the integrated information array, so that the data in the array The information includes: device ID, device name, device template ID, signal ID and signal number, control ID and control number, control name, and signal name.

Step 6: Generate a standard MIB file and a mapping relationship file raw.cfg according to the integrated information array.

The following is a detailed description of the above process by taking the temperature sensor of the sub-device and the UPS power supply as examples: (The following is an example of the output of the execution command, and the content in brackets is the text description added)

(Step: get MU file name and device template file name)

MU file MonitorUnitsIDU_S2.xml (this is the MU file name)

EquipFile[0] EquipmentTemplateIDU_S.xml (the device template file name of the temperature sensor)

EquipFile[1] EquipmentTemplate Libert Anson three-in and one-out UPS(UH31).xml

(Device template file name for UPS power supply)

(Step: Obtain the device instance information in the MU file)

pStruEquipInfo[0]: (equipment instance information of temperature sensor)

EquipId 1000 (equipment ID of temperature sensor)

EquipTemplateId 755000021 (equipment template ID corresponding to the equipment ID)

EquipName SerialTH0 (equipment name)

pStruEquipInfo[1]: (equipment instance information of UPS power supply)

EquipId 1001

EquipTemplateId 755000022

EquipName UPS(UH31)

(Step: Obtain the device information in the device template)

[0]EquipmentTemplateIDU_S.xml (the equipment template file name corresponding to the equipment template of the temperature sensor, the following information is obtained from this file)

iEquipTempId 755000021 (equipment template ID value of temperature sensor)

iSigNum 9       (the number of signals contained in the device template)

iSigId 51160000 szSigName Temperaturel (signal ID and signal name)

iSigId 51160001 szSigName Temperature2

iSigId 51160002 szSigName Temperature3

iSigId 51160003 szSigName Temperature4

iSigId 51160004 szSigName Temperature5

iSigId 51160005 szSigName Temperature6

iSigId 51160006 szSigName Temperature7

iSigId 51160007 szSigName Temperature8

iSigId 51160008 szSigName Temperature

iSigId 51160009 szSigName Humidity

iCtrlNum 2 2 (the number of controls contained in the device template)

iCtrlId 51360000 szCtrlName Relay1 (control ID value and control name)

iCtrlId 51360001 szCtrlName Relay2

[1]EquipmentTemplate Libert Anson Three-Input Single-Output UPS(UH31).xml (the file name of the equipment template corresponding to the second equipment template, the following information is obtained from this file)

iEquipTempId 755000022

iSigNum 13

iSigId 3110001 szSigName AC input phase A voltage

iSigId 3110002 szSigName AC input phase B voltage

iSigId 3110003 szSigName AC input phase C voltage

iSigId 3110004 szSigName AC output phase A voltage

iSigId 3110005 szSigName AC output B-phase voltage

iSigId 3110006 szSigName AC output phase C voltage

iSigId 3110007 szSigName AC output phase A current

iSigId 3110008 szSigName AC output B-phase current

iSigId 3110009 szSigName AC output phase C current

iSigId 3110010 szSigName DC input voltage (positive group)

iSigId 3110011 szSigName output frequency

iSigId 3110012 szSigName Indicates the number of batteries

iSigId 3110013 szSigName Indicates the number of temperatures

iCtrlNum 3

iCtrlId 3130001 szCtrlName Battery total voltage upper limit

iCtrlId 3130002 szCtrlName battery total voltage lower limit

iCtrlId 3136000 szCtrlName New control 3136000

(Steps: match and integrate to obtain an array of integrated information)

[0]SerialTH0 (information corresponding to the first sub-device, this line is the device name)

iEquipId 1000 (equipment ID)

iEquipTempId 755000021 (Equipment template ID, according to this value, you can know that its corresponding equipment template is EquipmentTemplateIDU_S.xml)

iSigNum 9 (according to the equipment template corresponding to the sub-device, the signal and control information owned by the sub-device can be known, which is the same as that in EquipmentTemplateIDU_S.xml)

iSigId 51160000 szSigName temperature1

iSigId 51160001 szSigName temperature2

iSigId 51160002 szSigName temperature3

iSigId 51160003 szSigName temperature4

iSigId 51160004 szSigName temperature5

iSigId 51160005 szSigName temperature6

iSigId 51160006 szSigName temperature7

iSigId 51160007 szSigName temperature8

iSigId 51160008 szSigName temperature

iSigId 51160009 szSigName humidity

iCtrlNum 2

iCtrlId 51360000 szCtrlName relay1

iCtrlId 51360001 szCtrlName relay2

[1]UPS(UH31) (information corresponding to the second sub-device, this line is the name of the sub-device)

iEquipId 1001 (equipment ID)

iEquipTempId 755000022 (equipment template ID, according to this value, it can be known that its corresponding equipment template is EquipmentTemplate Liberte Ansheng three-in single-out UPS(UH31).xml)

iSigNum 13 (according to the equipment template corresponding to the equipment instance, the signal and control information owned by the equipment instance is known, which is the same as that in the EquipmentTemplate Libert Anson Three-Input Single-Output UPS(UH31).xml file)

iSigId 3110001szSigName AC input phase A voltage

iSigId 3110002szSigName AC input phase B voltage

iSigId 3110003szSigName AC input phase C voltage

iSigId 3110004szSigName AC output phase A voltage

iSigId 3110005szSigName AC output B-phase voltage

iSigId 3110006szSigName AC output phase C voltage

iSigId 3110007szSigName AC output phase A current

iSigId 3110008szSigName AC output B-phase current

iSigId 3110009szSigName AC output phase C current

iSigId 3110010szSigName DC input voltage (positive group)

iSigId 3110011szSigName output frequency

iSigId 3110012szSigName indicates the battery quantity

iSigId 3110013szSigName Indicates the number of temperatures

iCtrlNum 3

iCtrlId 3130001szCtrlName Battery total voltage upper limit

iCtrlId 3130002szCtrlName battery total voltage lower limit

  iCtrlId 3136000 szCtrlName Added control 3136000

According to the characteristics of the target MIB file, only the leaf nodes and the second node are changed, and the information of these nodes is included in the above-mentioned integrated information array, and the MIB generating module is based on the data in the above-mentioned integrated information array and the Format features, assign OID number for each information or control (that is, leaf node of MIB), generate standard MIB file or update existing MIB file; at the same time generate a mapping relationship file raw.cfg or update existing mapping relationship file , the mapping relationship table file is a table in cfg format, which records: the mapping relationship between the OID of the leaf node in the MIB file and the management type information (ID_TYPE), equipment ID and signal ID or control ID, and the ID_TYPE is used for The difference indicates whether the corresponding OID leaf node corresponds to the signal or control of the sub-equipment. The data structure diagram of the mapping relationship table is shown in FIG. 3 .

After the MIB file and the mapping relationship file are generated or updated, the master device transmits the updated MIB file to the network management center, and the network management center analyzes the updated MIB file and uses the SNMP protocol message to implement the OID and operation of the object to be managed The instruction is sent to the main device, and after receiving the SNMP protocol message, the main device extracts the OID and the operation instruction in the message, searches for its corresponding sub-device through the mapping relationship file, and executes the corresponding operation instruction.

The master device in this embodiment can also actively send the abnormal event message (TRAP message) of the sub-device to the network management center, and the process of generating and receiving the message is the same as that of the prior art.

The above content is a further detailed description of the present invention in conjunction with specific preferred embodiments, and it cannot be assumed that the specific implementation of the present invention is limited to these descriptions. For those skilled in the technical field of the present invention, without departing from the concept of the present invention, some simple deduction or replacement can be made, which should be regarded as belonging to the protection scope of the present invention.

Claims (10)

1. network device management method based on snmp protocol, main equipment communicates and carries out network management center to the operational order of subset by snmp protocol and network management center; When the operating instruction of receiving the keeper or when detecting new subset access main equipment, carry out following steps:

A, main equipment read and resolve equipment template and the device instance file in the main equipment memory, and deposit in the integrate information array after the subset information in described equipment template and the described device instance file mated, integrates;

B, main equipment are according to mib file and mapping relations file in the generation of the data in the described integrate information array or the renewal main equipment, and described mapping relations file is used for recording OID and the device id of subset and the mapping relations of signal ID, control ID of described mib file leaf node;

C, main equipment are uploaded to described mib file the snmp protocol message of network management center and the transmission of receiving network managing center, extract OID and operational order in the message, and according to extracting OID and subset corresponding to described mapping relations ff that obtains, subset is carried out corresponding operational order.

2. the network device management method based on snmp protocol according to claim 1, it is characterized in that: in the described steps A, the subset information in the described equipment template comprises: the signal ID of template ID and corresponding subset, control ID; Subset information in the described device instance file comprises: template ID and device id; Main equipment mates the subset information in described equipment template and the described device instance file, integrate by template ID.

3. the network device management method based on snmp protocol according to claim 1 is characterized in that: also comprise step D: when subset had anomalous event to occur, described main equipment initiatively sent the report of subset unexpected message to network management center.

4. the network device management method based on snmp protocol according to claim 2, it is characterized in that: also comprise following information in the described integrate information array: subset title, signal number, control number, described signal number, control number represent respectively signal number, the control number that corresponding subset comprises.

5. it is characterized in that: also comprise following information in the described integrate information array according to claim 2 or 4 described network device management methods based on snmp protocol: signal name, control title.

6. the network device management method based on snmp protocol according to claim 1, it is characterized in that: also comprise management type information in the described mapping relations file, described management type information is used for representing that corresponding with it OID leaf node is signal or the control that corresponds in the subset.

7. main equipment based on the network apparatus management system of snmp protocol, comprise management program module, MIB module, comprise mib file in the described MIB module, it is characterized in that: also comprise data file module, MIB generation module, described data file module comprises equipment template and device instance file, records the information of all signal ID and the control ID of corresponding subset in the described equipment template; Described device instance file is used for record and the actual subset information that is connected of main equipment;

Described MIB generation module is used for when the operating instruction of receiving the keeper or when detecting new subset and accessing main equipment, read the information of described equipment template and device instance file, coupling, deposit in the integrate information array after integrating, and generate mib file and be sent to described MIB module or upgrade existing mib file in the described MIB module according to described integrate information array;

Also comprise the mapping relations file in the described MIB module, described mapping relations file is used for recording OID and the device id of subset and the mapping relations of signal ID, control ID of described mib file leaf node; Described MIB generation module is also for generating described mapping relations file according to described integrate information array or described mapping relations file being upgraded.

8. main equipment according to claim 7, it is characterized in that: described equipment template is assigned template ID, and described subset information comprises the template ID of the equipment template that this subset is applicable; Described MIB generation module mates the information of described equipment template and device instance file by template ID.

9. main equipment according to claim 7, it is characterized in that: described MIB module also comprises the mapping relations file, and described mapping relations file is for the mapping relations of the OID that records described mib file leaf node and subset device id and signal ID, control ID; Described MIB generation module generates described mapping relations file according to described integrate information array or described mapping relations file is upgraded.

10. main equipment according to claim 9 is characterized in that: comprise management type information in the described mapping relations file, described management type information be used for expression with it corresponding OID leaf node be signal or the control that corresponds in the subset.

Images