CN116319244A - Network management system and network architecture based on SNMP - Google Patents

Abstract

The application provides a network management system and a network architecture based on SNMP, wherein the network management system based on SNMP comprises a data storage module, an SNMP management module and an SNMP agent module, wherein the data storage module is used for storing at least one OID information set, and the appointed position of each OID in each OID information set bears a character string in a preset format configured by the same manufacturer; the SNMP management module is used for inquiring a target OID corresponding to the object to be managed from the data storage module based on manufacturer information of the object to be managed, sending the target OID to the SNMP agent module, and managing the object to be managed based on a return result of the SNMP agent module; and the SNMP agent module is used for acquiring a query result bound with the object to be managed according to the target OID and returning the query result to the SNMP management module. The system shortens the query time and improves the target OID query efficiency by querying the OID information set of the data storage module.

Description

Network management system and network architecture based on SNMP

Technical Field

The present disclosure relates to the field of network management of SNMP, and in particular, to a network management system based on SNMP and a network architecture based on SNMP.

Background

Presently, SNMP (Simple Network Management Protocol ) is a standard protocol employed for communication between network management devices and managed devices that specifies a set of objects describing manageable entities through MIB (Management Information Base ). The MIB defines a series of attributes of the managed device including an OID (Object Identifier ). The administrator uses the OID in the MIB library to send instructions to SNMP agents in managed devices by operating the NMS (Network Management System ) to manage objects in the managed devices that can be managed.

In the related art, the snmp walk tool searches the OID of all manageable objects in the managed device from the MIB library of the managed device, starting from the root node, according to the IP address of the managed device, and displays the OID to the administrator. However, the snmp walk traverses the data volume of query too much, and the administrator needs to screen a large amount of data displayed after query according to the requirement, so as to obtain the target OID.

Disclosure of Invention

In view of this, the present application provides a network management system and a network architecture based on SNMP, which greatly shortens the time of querying by querying in the OID information set of the data storage module, and improves the efficiency of querying the target OID.

In order to achieve the above purpose, the present application provides the following technical solutions:

according to a first aspect of an embodiment of the present invention, there is provided an SNMP-based network management system, including a data storage module, an SNMP management module, and an SNMP agent module, wherein,

the data storage module is used for storing at least one OID information set, and the appointed position of each OID in each OID information set carries a character string in a preset format configured by the same manufacturer;

the SNMP management module is used for inquiring a target OID corresponding to the object to be managed from the data storage module based on manufacturer information of the object to be managed, sending the target OID to the SNMP agent module, and managing the object to be managed based on a return result of the SNMP agent module;

and the SNMP agent module is used for acquiring a query result bound with the object to be managed according to the target OID and returning the query result to the SNMP management module.

According to a second aspect of an embodiment of the present invention, there is provided an SNMP-based network architecture, characterized by comprising a network asset fingerprint MIB, a management device equipped with an NMS, and a node set equipped with an SNMP agent module, wherein,

the network asset fingerprint MIB library is used for storing at least one OID information set, and the appointed position of each OID in each OID information set carries a character string in a preset format configured by the same manufacturer;

the management device provided with the NMS is used for inquiring a target OID corresponding to the object to be managed from the network asset fingerprint MIB base based on manufacturer information of the object to be managed, sending the target OID to the node set provided with the SNMP agent module, and managing the object to be managed based on a return result of the node set provided with the SNMP agent module;

the node set provided with the SNMP agent module is used for acquiring a query result bound with the object to be managed according to the target OID and returning the query result to the management equipment provided with the NMS.

According to the technical scheme, in the SNMP-based network management system, through the OID information sets stored in the data storage module, and the appointed position of each OID in each OID information set bears the character string in the preset format configured by the same manufacturer, when an administrator needs to acquire the corresponding target OID of an object to be managed, the administrator can start to inquire from the OID information set corresponding to the manufacturer in the data storage module according to the manufacturer to which the object to be managed belongs, compared with the related art, the amount of data to be inquired is reduced, and the administrator screens the data in the OID information set according to the requirements.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

FIG. 1 is a schematic diagram of an SNMP architecture according to an exemplary embodiment of the present application;

FIG. 2 is a schematic diagram of an SNMP management model according to an exemplary embodiment of the present application;

fig. 3 is a schematic structural diagram of a SNMP-based network management system according to an exemplary embodiment of the present application;

FIG. 4 is a schematic diagram of another SNMP-based network management system according to an exemplary embodiment of the present application;

FIG. 5 is a schematic diagram of a data storage module according to an exemplary embodiment of the present application;

FIG. 6-1 is a schematic illustration of a dataset acquired from a cyber-space mapping website according to an exemplary embodiment of the present application;

FIG. 6-2 is a schematic illustration of an original dataset of an exemplary embodiment of the present application;

fig. 6-3 are diagrams of OID information sets according to an exemplary embodiment of the present application;

6-4 are schematic diagrams of rule data sets according to an exemplary embodiment of the present application;

fig. 6-5 are schematic diagrams of a target OID information set according to an exemplary embodiment of the present application;

FIG. 7 is a schematic diagram of a network architecture based on SNMP in accordance with an exemplary embodiment of the present application;

FIG. 8 is a schematic diagram of another SNMP-based network architecture according to an exemplary embodiment of the present application;

fig. 9 is a schematic diagram of a network asset fingerprint MIB in accordance with an exemplary embodiment of the present application.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used in this application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first message may also be referred to as a second message, and similarly, a second message may also be referred to as a first message, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

SNMP is a set of network management protocols defined by the internet engineering task force, which is formulated based on the simple gateway monitoring protocol. The management device may remotely manage all network devices supporting the protocol, such as monitoring network status, modifying configuration of the network devices, receiving network event alerts, etc., through the SNMP protocol. The main function of SNMP is to allow a network administrator to manage and monitor devices on a network by managing the devices.

For example, as shown in fig. 1, the management device 11 may remotely manage network devices on the management node set 12 through SNMP protocol. The node set 12 includes network devices supporting SNMP protocol such as a printer 120, a switch 121, a server 122, and a router 123.

The management device sends a request for inquiring the configuration information or a request for modifying the configuration information to the managed device through the SNMP protocol, and the proxy process running on the managed device responds according to the request message of the management device. The managed device may also actively report alert information to the management device so that the network administrator can discover the failure in time. SNMP specifies a set of objects describing manageable entities through MIB, which is a tree database that specifies the variables maintained by the managed devices, i.e., information that can be queried and set by the agent process, each node of MIB has a unique OID and a unique name, and each leaf node represents a manageable object.

For example, as shown in fig. 2, the NMS210 in the management device 21 transmits a query configuration information request to the SNMP agent module 220 in the managed device 22 through the SNMP protocol. The SNMP agent module 220 queries SNMP information of the managed object 222 corresponding to the target OID in the MIB 221 according to the target OID in the request information, and returns the query result to the NMS210.

Fig. 3 is a schematic structural view of an SNMP-based network management system according to an exemplary embodiment of the present application, the SNMP-based network management system including a data storage module 31, an SNMP management module 32, and an SNMP agent module 33, wherein,

a data storage module 31, configured to store at least one set of OID information, where a specified position of each OID in each set of OID information carries a character string in a predetermined format configured by the same manufacturer;

the SNMP management module 32 is configured to query, from the data storage module 31, a target OID corresponding to an object to be managed based on vendor information of the object to be managed, send the target OID to the SNMP agent module 33, and manage the object to be managed based on a return result of the SNMP agent module 33;

the SNMP agent module 33 is configured to obtain a query result bound to the object to be managed according to the target OID, and return the query result to the SNMP management module 32.

In the MIB tree database, a node is specially used for identifying different manufacturers, and its child nodes are IDs obtained by each manufacturer. For example, vendor a has an ID of X, all its network devices OID have the same OID prefix 1.3.6.1.4.1.X.

In this embodiment, if the SNMP management module 32 is capable of knowing a character string in a predetermined format configured at a designated location of an OID by a vendor to which an object to be managed belongs, the SNMP management module 32 first queries an OID information set to which the object to be managed belongs from the data storage module 31 based on vendor information of the object to be managed, and because the OID information set uniquely corresponds to the vendor to which the object to be managed belongs, the SNMP management module 32 may query an OID corresponding to the device model from the belonging OID information set based on the device model of the object to be managed, where the OID is a target OID corresponding to the object to be managed.

For example, assuming that the object to be managed belongs to vendor a, the device model of the object to be managed is A1, the SNMP management module 32 knows that the fixed OID prefix of vendor a is 1.3.6.1.4.1.X, that is, a character string in a predetermined format configured by vendor a at a specified position of the OID. As shown in fig. 6-3, the fixed OID prefix uniquely corresponds to the OID information set M1, i.e. the prefix of each OID in the OID information set M1 is 1.3.6.1.4.1.X. The SNMP management module 32 queries that the OID corresponding to the device model A1 is 1.3.6.1.4.1.x.1.1 in the OID information set M1, where the OID is a target OID corresponding to the object to be managed.

As an example, after the SNMP management module 32 queries the target OID, it sends an SNMP message carrying a GET query instruction and the target OID to the SNMP agent module 33 through the SNMP protocol, and communicates with the SNMP agent module 33.

After receiving the SNMP message sent by the SNMP management module 32, the SNMP agent module 33 queries SNMP information corresponding to the target OID in the MIB on the object to be managed, and returns the query result to the SNMP management module 32. The SNMP agent module 33 is responsible for maintaining a MIB on an object to be managed, where the MIB is used for storing data variables such as control and status information of the object to be managed.

The SNMP management module 32 obtains data such as control and status information of the object to be managed according to the returned result of the SNMP agent module 33, and manages the object to be managed.

Fig. 4 is a schematic structural diagram of another SNMP-based network management system according to an exemplary embodiment of the present application, where the SNMP-based network management system further includes:

the original data storage module 34 is configured to store an original data set of an opened SNMP service device, where data in the original data set is data acquired from a network space mapping website and subjected to duplication removal, and the duplicated data uniquely corresponds to a device model; wherein the original data set comprises the OID of the opened SNMP service device. Of course, data may also be collected from vendor official websites, connected network devices, or other channels from which network device SNMP information may be obtained, which is not limited in this application.

The SNMP management module 32 is further configured to process the original data set into the at least one OID information set, and send the at least one OID information set to the data storage module 31.

In this embodiment, first, a deduplication processing operation is performed on a data set collected from a network space mapping website, so as to obtain an original data set, where each equipment model in the original data set uniquely corresponds to one OID. The SNMP management module 32 then processes the raw data set packets into at least one OID information set and sends it to the data storage module 31.

For example, assuming that the data set collected from the network space mapping website is shown in fig. 6-1, two repeated data exist in the device models A1, B2 and C3, after the data are subjected to the deduplication processing operation, one device model corresponds to one data only, and the original data set shown in fig. 6-2 is obtained. The SNMP management module 32 performs packet processing on the original data set based on a character string in a predetermined format configured by a manufacturer at a designated location of the OID, that is, the data with the OID prefix of 1.3.6.1.4.1.X belongs to the OID information set M1, the data with the OID prefix of 1.3.6.1.4.1.X belongs to the OID information set M2, and the data with the OID information set of 1.3.6.1.4.1.X belongs to the OID information set M3, and sends the obtained OID information set to the data storage module 31.

The de-duplication processing operation can reduce the data volume to be processed by the packet, shorten the packet processing time and improve the packet efficiency. Of course, the deduplication processing operation may be to group the original data sets according to the device model, and reserve the data with the earliest acquisition time or the smallest serial number in the same group, or other operations that make one device model uniquely correspond to one piece of data, which is not limited in this application.

Fig. 5 is a schematic structural diagram of a data storage module according to an exemplary embodiment of the present application, and the data storage module 31 includes a matching rule storage sub-module 310, a data storage sub-module 311, and a matching result storage sub-module 312, wherein,

a matching rule storage sub-module 310 for storing a rule data set; the rule data set comprises manufacturer names and manufacturer OIDs uniquely corresponding to the manufacturer names;

a data storage sub-module 311, configured to store at least one set of OID information, where a specified position of each OID in each set of OID information carries a character string in a predetermined format configured by the same manufacturer;

the SNMP management module 32 is further configured to determine a target OID information set that matches the specified location of the OID with the vendor OID, and send the target OID information set to the matching result storage sub-module 312;

a matching result storage sub-module 312, configured to store at least one of the target OID information sets, where each target OID information set includes the OID information set that matches the vendor OID, and the vendor name corresponding to the vendor OID.

In this embodiment, if the SNMP management module 32 does not know a character string in a predetermined format configured at a specified position of an OID by a vendor to which an object to be managed belongs, the SNMP management module 32 needs to match the character string in the specified position of the OID in the OID information set with the vendor OID in the rule data set to obtain the target OID information set.

The SNMP management module 32 firstly queries a target OID information set of the object to be managed from the matching result storage submodule 312 based on vendor information of the object to be managed, the target OID information set uniquely corresponds to a vendor of the object to be managed, and then the SNMP management module 32 queries an OID corresponding to the device model from the target OID information set based on the device model of the object to be managed, where the OID is the target OID corresponding to the object to be managed.

For example, assuming that the object to be managed belongs to vendor a, the device model of the object to be managed is A1, the SNMP management module knows that the vendor a configures a character string in a predetermined format at a designated location of the OID, and needs to match the character string in the designated location of the OID in the OID information set shown in fig. 6-3 with the vendor OID in the rule data set shown in fig. 6-4, that is, the OID with a prefix of 1.3.6.1.4.1.X corresponds to vendor a, the OID with a prefix of 1.3.6.1.4.1.y corresponds to vendor B, and the OID with a prefix of 1.3.6.1.4.1.1.z corresponds to vendor C, to obtain the target data set shown in fig. 6-5. The SNMP management module 32 queries that the OID corresponding to the device model A1 is 1.3.6.1.4.1.x.1.1 in the target OID information set T1, where the OID is the target OID corresponding to the object to be managed.

In the above embodiment, the data storage module 11 and the SNMP management module 12 may be located in the same device or may be located in different devices; the SNMP management module 12 may be located on a management device, which may be any host equipped with network management software; the SNMP agent module 13 may be located on a managed device, which may be a network device such as a router, a switch, a gateway, or the like.

Fig. 7 is a schematic structural diagram of an SNMP-based network architecture according to an exemplary embodiment of the present application, the SNMP-based network architecture including a network asset fingerprint MIB 71, a management device 72 equipped with an NMS, and a node set 73 equipped with an SNMP agent module, wherein,

a network asset fingerprint MIB 71 for storing at least one set of OID information, wherein the designated location of each OID in each set of OID information carries a character string of a predetermined format configured by the same manufacturer;

the management device 72 provided with an NMS is configured to query a target OID corresponding to an object to be managed from the network asset fingerprint MIB 71 based on vendor information of the object to be managed, send the target OID to the node set 73 provided with the SNMP agent module, and manage the object to be managed based on a return result of the node set 73 provided with the SNMP agent module;

the node set 73 provided with the SNMP agent module is configured to obtain a query result bound to the object to be managed according to the target OID, and return the query result to the management device 72 provided with the NMS.

In the MIB tree database, a node is specially used for identifying different manufacturers, and its child nodes are IDs obtained by each manufacturer. For example, vendor a has an ID of X, all its network devices OID have the same OID prefix 1.3.6.1.4.1.X.

If the management device 72 equipped with the NMS can know the character string of the predetermined format configured by the vendor to which the object to be managed belongs at the designated position of the OID, the information set of the OID to which the object to be managed belongs is firstly queried from the network asset fingerprint MIB 71 based on the vendor information of the object to be managed, and since the information set of the OID uniquely corresponds to the vendor to which the object to be managed belongs, the management device 72 equipped with the NMS can query the OID corresponding to the device model from the information set of the OID to which the object to be managed belongs based on the device model of the object to be managed, and the OID is the target OID corresponding to the object to be managed.

For example, assuming that the object to be managed belongs to vendor a, the device model of the object to be managed is A1, the management device 72 equipped with the NMS knows that the fixed OID prefix of vendor a is 1.3.6.1.4.1.X, that is, the character string of the predetermined format configured by vendor a at the specified position of the OID. As shown in fig. 6-3, the fixed OID prefix uniquely corresponds to the OID information set M1, i.e. the prefix of each OID in the OID information set M1 is 1.3.6.1.4.1.X. The management device 72 equipped with the NMS queries that the OID corresponding to the device model A1 is 1.3.6.1.4.1.x.1.1 in the OID information set M1, and the OID is the target OID corresponding to the object to be managed.

As an example, after the management device 72 equipped with the NMS queries to obtain the target OID, the NMS is used to send an SNMP message carrying a GET query instruction and the target OID to the node set 73 equipped with the SNMP agent module through the SNMP protocol, and the SNMP message is communicated with the node set 73 equipped with the SNMP agent module.

After receiving the SNMP message sent by the management device 72 with the NMS, the node set 73 with the SNMP agent module queries SNMP information corresponding to the target OID in the MIB on the object to be managed, and returns the query result to the management device 72 with the NMS. The SNMP agent module in the node set 73 with the SNMP agent module is responsible for maintaining a MIB on an object to be managed, where the MIB is used for storing data variables such as control and status information of the object to be managed.

The NMS-equipped management device 72 acquires data such as control and status information of the object to be managed, and manages the object to be managed, based on the returned result of the node set 73 equipped with the SNMP agent module.

Fig. 8 is a schematic structural diagram of another SNMP-based network architecture according to an exemplary embodiment of the present application, where the SNMP-based network architecture further includes:

an original database 74, configured to store an original data set of an SNMP service device that has been started, where data in the original data set is data collected from a network space mapping website and subjected to duplication removal, where the duplication removal data uniquely corresponds to one device model; wherein the original data set comprises the OID of the opened SNMP service device;

the management device 72, equipped with an NMS, is further configured to send the raw data set packet to the network asset fingerprint MIB 71 after processing the raw data set packet into the at least one OID information set.

In this embodiment, first, a deduplication processing operation is performed on a data set collected from a network space mapping website, so as to obtain an original data set, where each equipment model in the original data set uniquely corresponds to one OID. The management device 72, which is equipped with the NMS, then processes the raw data set packets into at least one OID information set and sends it to the network asset fingerprint MIB 71.

For example, assuming that the data set collected from the network space mapping website is shown in fig. 6-1, two repeated data exist in the device models A1, B2 and C3, after the data are subjected to the deduplication processing operation, one device model corresponds to one data only, and the original data set shown in fig. 6-2 is obtained. The management device 72 equipped with the NMS performs grouping processing on the original data set based on the character string in the predetermined format configured by the manufacturer at the designated position of the OID, that is, the data with the OID prefix of 1.3.6.1.4.1.X belongs to the OID information set M1, the data with the OID prefix of 1.3.6.1.4.1.X belongs to the OID information set M2, and the data with the OID information set of 1.3.6.1.4.1.X belongs to the OID information set M3, and after the OID information set shown in fig. 6-3 is obtained, the data is sent to the network asset fingerprint MIB 71.

The de-duplication processing operation can reduce the data volume to be processed by the packet, shorten the packet processing time and improve the packet efficiency. Of course, the deduplication processing operation may be to group the original data sets according to the device model, and reserve the data with the earliest acquisition time or the smallest serial number in the same group, or other operations that make one device model uniquely correspond to one piece of data, which is not limited in this application.

Fig. 9 is a schematic diagram of the structure of a network asset fingerprint MIB of an exemplary embodiment of the present application, the network asset fingerprint MIB 71 including a matching rules table 710, a data storage table 711 and a matching results table 712, wherein,

a matching rule table 710 for storing a rule data set; the rule data set comprises manufacturer names and manufacturer OIDs uniquely corresponding to the manufacturer names;

a data storage table 711, configured to store at least one set of the OID information, where a specified position of each OID in each set of OID information carries a character string in a predetermined format configured by the same manufacturer;

the management device 712 provided with an NMS is further configured to determine a target OID information set in which the character string of the specified location of the OID is matched with the vendor OID, and send the target OID information set to the matching result table 712;

a matching result table 712 for storing at least one of the target OID information sets; each target OID information set includes the OID information set matched with the vendor OID and the vendor name corresponding to the vendor OID.

In this embodiment, if the management device 72 equipped with the NMS does not know the character string in the predetermined format configured at the specified position of the OID by the vendor to which the object to be managed belongs, the management device 72 equipped with the NMS needs to match the character string at the specified position of the OID in the OID information set with the vendor OID in the rule data set, so as to obtain the target OID information set.

The management device 72 equipped with the NMS first queries, from the matching result table 712, the target OID information set to which the object to be managed belongs based on vendor information of the object to be managed, the target OID information set uniquely corresponding to the vendor to which the object to be managed belongs, and then the management device 72 equipped with the NMS queries, from the target OID information set, an OID corresponding to the device model based on the device model of the object to be managed, the OID being the target OID corresponding to the object to be managed.

For example, assuming that the object to be managed belongs to vendor a, the device model of the object to be managed is A1, the management device 72 equipped with the NMS is not aware of the character string of the predetermined format configured by vendor a at the designated location of the OID, the character string of the designated location of the OID in the OID information set shown in fig. 6-3 needs to be matched with the vendor OID in the rule data set shown in fig. 6-4, that is, the OID corresponding vendor a with the prefix of 1.3.6.1.4.1.X, the OID corresponding vendor B with the prefix of 1.3.6.1.4.1.1. Z, and the OID corresponding vendor C with the prefix of 1.3.6.1.4.1.z, to obtain the target data set shown in fig. 6-5. The management device 72 equipped with the NMS queries that the OID corresponding to the device model A1 is 1.3.6.1.4.1.x.1.1 in the target OID information set T1, where the OID is the target OID corresponding to the object to be managed.

In the above embodiment, the network asset fingerprint MIB 71 may be located on the management device 72 in which the NMS is installed, or may be located on another network device connected to the management device.

The foregoing description of the preferred embodiments of the present invention is not intended to limit the invention to the precise form disclosed, and any modifications, equivalents, improvements and alternatives falling within the spirit and principles of the present invention are intended to be included within the scope of the present invention.

Claims (10)

1. A network management system based on SNMP is characterized by comprising a data storage module, an SNMP management module and an SNMP agent module, wherein,

the data storage module is used for storing at least one OID information set, and the appointed position of each OID in each OID information set carries a character string in a preset format configured by the same manufacturer;

the SNMP management module is used for inquiring a target OID corresponding to the object to be managed from the data storage module based on manufacturer information of the object to be managed, sending the target OID to the SNMP agent module, and managing the object to be managed based on a return result of the SNMP agent module;

and the SNMP agent module is used for acquiring a query result bound with the object to be managed according to the target OID and returning the query result to the SNMP management module.

2. The system of claim 1, further comprising:

the original data storage module is used for storing an original data set of the started SNMP service equipment, wherein the data in the original data set is data which is acquired from a network space mapping website and subjected to duplication removal, and the duplicated data uniquely corresponds to one equipment model; wherein the original data set comprises the OID of the opened SNMP service device;

the SNMP management module is further configured to process the original data set into the at least one OID information set in a packet, and send the at least one OID information set to the data storage module.

3. The system of claim 1, wherein the data storage module comprises a matching rule storage sub-module, a data storage sub-module, and a matching result storage sub-module, wherein,

the matching rule storage sub-module is used for storing a rule data set; the rule data set comprises manufacturer names and manufacturer OIDs uniquely corresponding to the manufacturer names;

the data storage sub-module is used for storing at least one OID information set, and the appointed position of each OID in each OID information set carries a character string in a preset format configured by the same manufacturer;

the SNMP management module is also used for determining a target OID information set of which the character string at the appointed position of the OID is matched with the vendor OID and sending the target OID information set to the matching result storage sub-module;

the matching result storage sub-module is configured to store at least one target OID information set, where each target OID information set includes the OID information set matched with the vendor OID, and the vendor name corresponding to the vendor OID.

4. The system of claim 1, wherein the data storage module is located in the same device as the SNMP management module.

5. The system of claim 1, wherein the SNMP management module is located on a management device.

6. The system of claim 1, wherein the SNMP agent module is located on a managed device.

7. A network architecture based on SNMP is characterized by comprising a network asset fingerprint MIB library, management equipment provided with NMS and node set provided with SNMP agent module, wherein,

the network asset fingerprint MIB library is used for storing at least one OID information set, and the appointed position of each OID in each OID information set carries a character string in a preset format configured by the same manufacturer;

the management device provided with the NMS is used for inquiring a target OID corresponding to the object to be managed from the network asset fingerprint MIB base based on manufacturer information of the object to be managed, sending the target OID to the node set provided with the SNMP agent module, and managing the object to be managed based on a return result of the node set provided with the SNMP agent module;

the node set provided with the SNMP agent module is used for acquiring a query result bound with the object to be managed according to the target OID and returning the query result to the management equipment provided with the NMS.

8. The network architecture of claim 7, further comprising:

the original database is used for storing an original data set of the started SNMP service equipment, wherein the data in the original data set is data which is acquired from a network space mapping website and subjected to duplication removal, and the data subjected to duplication removal uniquely corresponds to one equipment model; wherein the original data set comprises the OID of the opened SNMP service device;

the management device equipped with the NMS is further configured to process the original data set into the at least one OID information set, and send the at least one OID information set to the network asset fingerprint MIB.

9. The network architecture of claim 7, wherein the network asset fingerprint MIB library comprises a matching rules table, a data storage table, and a matching results table, wherein,

the matching rule table is used for storing a rule data set; the rule data set comprises manufacturer names and manufacturer OIDs uniquely corresponding to the manufacturer names;

the data storage table is used for storing at least one OID information set, and the appointed position of each OID in each OID information set carries a character string in a preset format configured by the same manufacturer;

the management device provided with the NMS is also used for determining a target OID information set matched with the vendor OID by the character string of the appointed position of the OID and sending the target OID information set to the matching result table;

the matching result table is used for storing at least one target OID information set; each target OID information set includes the OID information set matched with the vendor OID and the vendor name corresponding to the vendor OID.

10. The network architecture of claim 7 wherein the network asset fingerprint MIB library is located on the NMS-equipped management device.

Images