A SNMP-based network management system and network architecture

Abstract

The application provides an SNMP-based network management system and a network architecture, the SNMP-based network management system comprising a data storage module, an SNMP management module and an SNMP agent module, wherein the data storage module is configured to store at least one OID information set, and the specified position of each OID in each OID information set carries a string in a predetermined format configured by a same manufacturer; the SNMP management module is configured to query a target OID corresponding to a to-be-managed object from the data storage module based on the manufacturer information of the to-be-managed object, send the target OID to the SNMP agent module, and manage the to-be-managed object based on the returned result of the SNMP agent module; and the SNMP agent module is configured to obtain a query result bound with the to-be-managed object according to the target OID and return the query result to the SNMP management module. The system shortens the query time and improves the query target OID efficiency by querying in the OID information set of the data storage module.

Description

Technical Field

[0001] This application relates to the field of SNMP network management, and more particularly to an SNMP-based network management system and an SNMP-based network architecture. Background Technology

[0002] Currently, SNMP (Simple Network Management Protocol) is the standard protocol used for communication between network management devices and managed devices. It specifies that a set of manageable entities should be described using a MIB (Management Information Base). The MIB defines a series of attributes for the managed devices, including OIDs (Object Identifiers). Administrators, through the NMS (Network Management System), use the OIDs in the MIB to send commands to the SNMP agent in the managed device, thereby managing the manageable objects within the managed device.

[0003] In related technologies, the SNMPWALK tool, based on the IP address of the managed device, traverses the MIB database of the managed device, starting from the root node, to query the OIDs of all manageable objects within the managed device and displays them to the administrator. However, SNMPWALK traverses and queries a large amount of data, and the administrator must filter the large amount of data displayed after the query to obtain the target OID. This technical solution is time-consuming and inefficient in querying the target OID. Summary of the Invention

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

[0005] To achieve the above objectives, this application provides the following technical solution: According to a first aspect of the present invention, an SNMP-based network management system is provided, comprising a data storage module, an SNMP management module, and an SNMP agent module, wherein, The data storage module is used to store at least one OID information set, wherein a specified position of each OID in each OID information set carries a string of a predetermined format configured by the same manufacturer; The SNMP management module is used to query the target OID corresponding to the managed object from the data storage module based on the manufacturer information of the managed object, send the target OID to the SNMP agent module, and manage the managed object based on the results returned by the SNMP agent module. The SNMP agent module is used to obtain the query results bound to the object to be managed based on the target OID, and return them to the SNMP management module.

[0006] According to a second aspect of the present invention, an SNMP-based network architecture is provided, including a network asset fingerprint MIB database, a management device equipped with an NMS, and a node set equipped with an SNMP agent module, wherein... The network asset fingerprint MIB database is used to store at least one set of OID information, and each OID in each set of OID information carries a string of a predetermined format configured by the same vendor at a specified position. The management device equipped with NMS is used to query the target OID corresponding to the managed object from the network asset fingerprint MIB database based on the manufacturer information of the managed object, send the target OID to the node set equipped with the SNMP agent module, and manage the managed object based on the results returned by the node set equipped with the SNMP agent module. The node set equipped with the SNMP agent module is used to obtain the query results bound to the object to be managed based on the target OID, and return them to the management device equipped with NMS.

[0007] As can be seen from the above technical solutions, in the SNMP-based network management system of this application, the OID information set stored in the data storage module is used. Each OID in the data storage module carries a string of a predetermined format configured by the same manufacturer at a specified position. When the administrator needs to obtain the target OID of the object to be managed, he can start querying 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 related technologies, the amount of data to be queried is reduced. Furthermore, the administrator can filter the data in the OID information set according to the needs, which reduces the amount of data to be filtered compared with related technologies, greatly shortens the query time, and improves the efficiency of querying the target OID.

[0008] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0009] Figure 1 This is a schematic diagram of an exemplary embodiment of the SNMP architecture of this application; Figure 2 This is a schematic diagram of an exemplary embodiment of the SNMP management model of this application; Figure 3 This is a schematic diagram of the structure of an SNMP-based network management system according to an exemplary embodiment of this application; Figure 4 This is a schematic diagram of another SNMP-based network management system according to an exemplary embodiment of this application; Figure 5 This is a schematic diagram of the data storage module of an exemplary embodiment of this application; Figure 6-1 This is a schematic diagram of a dataset collected from a cyberspace mapping website, which is an exemplary embodiment of this application; Figure 6-2 This is a schematic diagram of the original dataset of an exemplary embodiment of this application; Figure 6-3 This is a schematic diagram of an exemplary embodiment of the OID information set of this application; Figure 6-4 This is a schematic diagram of a rule dataset according to an exemplary embodiment of this application; Figure 6-5 This is a schematic diagram of the target OID information set of an exemplary embodiment of this application; Figure 7 This is a schematic diagram of a network architecture based on SNMP, as exemplified in an embodiment of this application. Figure 8 This is a schematic diagram of another SNMP-based network architecture according to an exemplary embodiment of this application; Figure 9 This is a schematic diagram of the structure of a network asset fingerprint MIB library according to an exemplary embodiment of this application. Detailed Implementation

[0010] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

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

[0012] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0013] SNMP is a set of network management protocols defined by the Internet Engineering Task Force (IETF). This protocol is based on the Simple Gateway Monitoring Protocol. Management devices can remotely manage all network devices that support SNMP, such as monitoring network status, modifying network device configurations, and receiving network event alerts. The main function of SNMP is to allow network administrators to manage and monitor devices on the network through management devices.

[0014] For example Figure 1 As shown, management device 11 can remotely manage network devices on management node set 12 via the SNMP protocol. Node set 12 includes network devices supporting the SNMP protocol, such as printer 120, switch 121, server 122, and router 123.

[0015] The management device sends configuration information query or modification requests to the managed device via the SNMP protocol. The agent process running on the managed device responds to the management device's request messages. The managed device can also proactively report alarm information to the management device so that network administrators can promptly detect faults. SNMP specifies the use of a Management Information Base (MIB) to describe a set of manageable entities. An MIB is a tree-structured database that specifies the variables maintained by the managed device—information that can be queried and set by the agent process. Each node in the MIB has a unique OID and a unique name, and each leaf node represents a manageable object.

[0016] For example Figure 2 As shown, the NMS 210 in the management device 21 sends a request to the SNMP agent module 220 in the managed device 22 via the SNMP protocol to query configuration information. The SNMP agent module 220, based on the target OID in the request information, queries the MIB database 221 for the SNMP information of the managed object 222 corresponding to the target OID, and returns the query result to the NMS 210.

[0017] Figure 3This is a schematic diagram of the structure of an exemplary embodiment of an SNMP-based network management system. The SNMP-based network management system includes a data storage module 31, an SNMP management module 32, and an SNMP agent module 33, wherein... Data storage module 31 is used to store at least one OID information set, wherein a specified position of each OID in each OID information set carries a string of a predetermined format configured by the same manufacturer; The SNMP management module 32 is used to query the target OID corresponding to the managed object from the data storage module 31 based on the manufacturer information of the managed object, send the target OID to the SNMP agent module 33, and manage the managed object based on the results returned by the SNMP agent module 33. The SNMP agent module 33 is used to obtain the query results bound to the object to be managed based on the target OID and return them to the SNMP management module 32.

[0018] In the MIB tree database, there is a dedicated node for identifying different vendors, and its child nodes are the IDs obtained by each vendor. For example, if vendor A's ID is X, then all of its network devices will have the same OID prefix: 1.3.6.1.4.1.X.

[0019] In this embodiment, if the SNMP management module 32 knows the pre-formatted string configured at the specified location of the OID of the manufacturer to which the managed object belongs, it first queries the OID information set to which the managed object belongs from the data storage module 31 based on the manufacturer information of the managed object. Since the OID information set uniquely corresponds to the manufacturer to which the managed object belongs, the SNMP management module 32 can query the OID corresponding to the device model from the OID information set based on the device model of the managed object. This OID is the target OID corresponding to the managed object.

[0020] For example, suppose the object to be managed belongs to vendor A, and the device model of the object to be managed is A1. The SNMP management module 32 knows that vendor A's fixed OID prefix is ​​1.3.6.1.4.1.X, which is a predefined string configured by vendor A at a specified location in the OID. Figure 6-3 As shown, this fixed OID prefix uniquely corresponds to the OID information set M1, meaning that 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 the OID corresponding to device model A1 in the OID information set M1, finding it to be 1.3.6.1.4.1.X.1.1. This OID is the target OID corresponding to the object to be managed.

[0021] As an example, after the SNMP management module 32 obtains the target OID, it sends an SNMP message carrying the GET query command and the target OID to the SNMP agent module 33 through the SNMP protocol to communicate with the SNMP agent module 33.

[0022] After receiving the SNMP message sent by the SNMP management module 32, the SNMP agent module 33 queries the MIB database on the object to be managed for the SNMP information corresponding to the target OID and returns the query result to the SNMP management module 32. The SNMP agent module 33 is responsible for maintaining the MIB database on the object to be managed, which is used to store data variables such as control and status information of the object.

[0023] The SNMP management module 32 obtains control and status information of the object to be managed based on the return result of the SNMP agent module 33, and manages the object to be managed.

[0024] Figure 4 This is a schematic diagram of another SNMP-based network management system according to an exemplary embodiment of this application. The SNMP-based network management system further includes: The raw data storage module 34 is used to store the raw dataset of devices with SNMP service enabled. The data in the raw dataset is collected from a cyberspace mapping website and deduplicated, with each deduplicated data uniquely corresponding to a device model. The raw dataset includes the OID of the devices with SNMP service enabled. Of course, data can also be collected from the manufacturer's official website, connected network devices, or other channels that can obtain SNMP information of network devices; this application does not impose any restrictions on this.

[0025] The SNMP management module 32 is also used to group the original dataset into at least one OID information set and then send it to the data storage module 31.

[0026] In this embodiment, the dataset collected from the cyberspace mapping website is first deduplicated to obtain the original dataset, where each device model in the original dataset uniquely corresponds to an OID. Then, the SNMP management module 32 groups the original dataset into at least one OID information set and sends it to the data storage module 31.

[0027] For example, suppose the dataset collected from a cyberspace mapping website is as follows: Figure 6-1 As shown, equipment models A1, B2, and C3 each have two duplicate entries. After deduplication, each equipment model uniquely corresponds to one entry, resulting in the following: Figure 6-2The original dataset is shown. The SNMP management module 32 groups the original dataset based on the predefined string format configured by the manufacturer at the specified location of the OID. That is, data with the OID prefix 1.3.6.1.4.1.X belongs to OID information set M1, data with the prefix 1.3.6.1.4.1.X belongs to OID information set M2, and data with the prefix 1.3.6.1.4.1.X belongs to OID information set M3, resulting in the following... Figure 6-3 After the OID information set shown is displayed, it is sent to the data storage module 31.

[0028] The deduplication operation can reduce the amount of data that needs to be processed for grouping, shorten the grouping processing time, and improve grouping efficiency. Of course, the deduplication operation can be to group the original dataset by device model, retain the data with the earliest collection time or the smallest serial number in the same group, or other operations that make one data point uniquely correspond to one device model. This application does not limit this to any specific operation.

[0029] Figure 5 This is a schematic diagram of the data storage module of an exemplary embodiment of this application. The data storage module 31 includes a matching rule storage submodule 310, a data storage submodule 311, and a matching result storage submodule 312, wherein... The matching rule storage submodule 310 is used to store the rule dataset; wherein, the rule dataset includes the manufacturer name and the manufacturer OID that uniquely corresponds to the manufacturer name; The data storage submodule 311 is used to store at least one of the OID information sets, wherein a specified position of each OID in each OID information set carries a string of a predetermined format configured by the same manufacturer; The SNMP management module 32 is also used to determine the target OID information set that matches the string at a specified position of the OID with the manufacturer OID, and send the target OID information set to the matching result storage submodule 312; The matching result storage submodule 312 is used to store at least one of the target OID information sets, each target OID information set including the OID information set that matches the manufacturer OID, and the manufacturer name corresponding to the manufacturer OID.

[0030] In this embodiment, if the SNMP management module 32 does not know the predefined format string configured at the specified position of the OID of the manufacturer to which the managed object belongs, the SNMP management module 32 needs to match the string at the specified position of the OID in the OID information set with the manufacturer OID in the rule dataset to obtain the target OID information set.

[0031] The SNMP management module 32 first queries the target OID information set to which the managed object belongs from the matching result storage submodule 312 based on the manufacturer information of the managed object. This target OID information set uniquely corresponds to the manufacturer to which the managed object belongs. Then, based on the device model of the managed object, the SNMP management module 32 queries the OID corresponding to the device model from the target OID information set. This OID is the target OID corresponding to the managed object.

[0032] For example, suppose the object to be managed belongs to vendor A, and the device model of the object to be managed is A1. The SNMP management module does not know the predefined string format configured by vendor A at the specified location of the OID, and needs to... Figure 6-3 The string at the specified position of the OID in the OID information set shown is similar to... Figure 6-4 The rules dataset shown is used to match vendor OIDs. Specifically, OIDs with the prefix 1.3.6.1.4.1.X correspond to vendor A, OIDs with the prefix 1.3.6.1.4.1.Y correspond to vendor B, and OIDs with the prefix 1.3.6.1.4.1.Z correspond to vendor C, resulting in the following: Figure 6-5 The target dataset is shown. In the target OID information set T1, the SNMP management module 32 queries the OID corresponding to device model A1, which is 1.3.6.1.4.1.X.1.1. This OID is the target OID corresponding to the object to be managed.

[0033] In the above embodiments, the data storage module 11 and the SNMP management module 12 can be located in the same device or in different devices; the SNMP management module 12 can be located on a management device, which can be any host with network management software installed; the SNMP agent module 13 can be located on a managed device, which can be a network device such as a router, switch, or gateway.

[0034] Figure 7 This is a schematic diagram of an exemplary embodiment of an SNMP-based network architecture. The SNMP-based network architecture includes a network asset fingerprint MIB database 71, a management device 72 equipped with an NMS, and a node set 73 equipped with an SNMP agent module. The network asset fingerprint MIB library 71 is used to store at least one set of OID information, where a specified position of each OID in each OID set carries a string in a predefined format configured by the same vendor. The management device 72 equipped with NMS is used to query the target OID corresponding to the managed object from the network asset fingerprint MIB database 71 based on the manufacturer information of the managed object, send the target OID to the node set 73 equipped with the SNMP agent module, and manage the managed object based on the result returned by the node set 73 equipped with the SNMP agent module. The node set 73 equipped with the SNMP agent module is used to obtain the query result bound to the object to be managed based on the target OID and return it to the management device 72 equipped with NMS.

[0035] In the MIB tree database, there is a dedicated node for identifying different vendors, and its child nodes are the IDs obtained by each vendor. For example, if vendor A's ID is X, then all of its network devices will have the same OID prefix: 1.3.6.1.4.1.X.

[0036] If the management device 72 equipped with NMS knows the predefined string configured at the specified location of the OID of the manufacturer to which the object to be managed belongs, it first queries the network asset fingerprint MIB database 71 for the OID information set to which the object to be managed belongs based on the manufacturer information of the object to be managed. Since the OID information set uniquely corresponds to the manufacturer to which the object to be managed belongs, the management device 72 equipped with NMS can query the OID corresponding to the device model from the OID information set based on the device model of the object to be managed. This OID is the target OID corresponding to the object to be managed.

[0037] For example, suppose the object to be managed belongs to vendor A, the device model of the object to be managed is A1, and the management device 72 equipped with NMS is known to have a fixed OID prefix of 1.3.6.1.4.1.X, which is a predefined string configured by vendor A at a specified position in the OID. Figure 6-3 As shown, this fixed OID prefix uniquely corresponds to the OID information set M1, meaning that 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 NMS queries the OID corresponding to device model A1 in the OID information set M1, finding it to be 1.3.6.1.4.1.X.1.1. This OID is the target OID corresponding to the object to be managed.

[0038] As an example, after the management device 72 equipped with NMS obtains the target OID, it uses NMS to send an SNMP message carrying a GET query command and the target OID to the node set 73 equipped with the SNMP agent module via the SNMP protocol, and communicates with the node set 73 equipped with the SNMP agent module.

[0039] After receiving an SNMP message from the management device 72 equipped with an SNMP agent module, the node set 73 queries the MIB database on the object to be managed for the SNMP information corresponding to the target OID and returns the query result to the management device 72 equipped with the NMS. The SNMP agent module in the node set 73 is responsible for maintaining the MIB database on the object to be managed, which stores data variables such as control and status information of the object.

[0040] The management device 72 equipped with NMS obtains control and status information of the object to be managed based on the return results of the node set 73 equipped with the SNMP agent module, and then manages the object to be managed.

[0041] Figure 8 This is a schematic diagram of another SNMP-based network architecture according to an exemplary embodiment of this application. The SNMP-based network architecture further includes: The raw database 74 is used to store the raw dataset of devices with SNMP service enabled. The data in the raw dataset is collected from a cyberspace mapping website and deduplicated. Each deduplicated data uniquely corresponds to a device model. The raw dataset includes the OID of the device with SNMP service enabled. The management device 72 equipped with NMS is also used to group the original dataset into at least one set of OID information and then send it to the network asset fingerprint MIB database 71.

[0042] In this embodiment, the dataset collected from the cyberspace mapping website is first deduplicated to obtain the original dataset, where each device model in the original dataset uniquely corresponds to an OID. Then, the management device 72 equipped with NMS groups the original dataset into at least one OID information set and sends it to the network asset fingerprint MIB database 71.

[0043] For example, suppose the dataset collected from a cyberspace mapping website is as follows: Figure 6-1 As shown, equipment models A1, B2, and C3 each have two duplicate entries. After deduplication, each equipment model uniquely corresponds to one entry, resulting in the following: Figure 6-2 The original dataset is shown. Management devices 72 equipped with NMS group the original datasets based on strings in a predetermined format configured by the manufacturer at a specified location in the OID. Specifically, data with the OID prefix 1.3.6.1.4.1.X belongs to OID information set M1, data with 1.3.6.1.4.1.X belongs to OID information set M2, and data with 1.3.6.1.4.1.X belongs to OID information set M3, resulting in the following... Figure 6-3After displaying the OID information set, it is sent to the network asset fingerprint MIB database 71.

[0044] The deduplication operation can reduce the amount of data that needs to be processed for grouping, shorten the grouping processing time, and improve grouping efficiency. Of course, the deduplication operation can be to group the original dataset by device model, retain the data with the earliest collection time or the smallest serial number in the same group, or other operations that make one data point uniquely correspond to one device model. This application does not limit this to any specific operation.

[0045] Figure 9 This is a schematic diagram of the structure of a network asset fingerprint MIB database according to an exemplary embodiment of this application. The network asset fingerprint MIB database 71 includes a matching rule table 710, a data storage table 711, and a matching result table 712, wherein... Matching rule table 710 is used to store rule datasets; wherein, the rule datasets include the manufacturer name and the manufacturer OID that uniquely corresponds to the manufacturer name; Data storage table 711 is used to store at least one of the OID information sets, wherein a specified position of each OID in each OID information set carries a string of a predetermined format configured by the same manufacturer; The management device 712 equipped with NMS is also used to determine the target OID information set that matches the string at a specified position of the OID with the vendor OID, and send the target OID information set to the matching result table 712; The matching result table 712 is used to store at least one of the target OID information sets; each target OID information set includes the OID information set that matches the vendor OID, and the vendor name corresponding to the vendor OID.

[0046] In this embodiment, if the management device 72 equipped with NMS does not know the predefined format string configured at the specified position of the OID of the manufacturer to which the managed object belongs, the management device 72 equipped with NMS needs to match the string at the specified position of the OID in the OID information set with the manufacturer OID in the rule dataset to obtain the target OID information set.

[0047] The management device 72 equipped with NMS first queries the target OID information set to which the managed object belongs from the matching result table 712 based on the manufacturer information of the managed object. This target OID information set uniquely corresponds to the manufacturer to which the managed object belongs. Then, the management device 72 equipped with NMS queries the OID corresponding to the device model from the target OID information set based on the device model of the managed object. This OID is the target OID corresponding to the managed object.

[0048] For example, suppose the object to be managed belongs to vendor A, the device model of the object to be managed is A1, and the management device 72 equipped with NMS is unknown. Vendor A has configured a predefined string at a specified location in the OID, which needs to be... Figure 6-3 The string at the specified position of the OID in the OID information set shown is similar to... Figure 6-4 The rules dataset shown is used to match vendor OIDs. Specifically, OIDs with the prefix 1.3.6.1.4.1.X correspond to vendor A, OIDs with the prefix 1.3.6.1.4.1.Y correspond to vendor B, and OIDs with the prefix 1.3.6.1.4.1.Z correspond to vendor C, resulting in the following: Figure 6-5 The target dataset is shown. The management device 72 equipped with NMS queries the target OID information set T1. The OID corresponding to device model A1 is 1.3.6.1.4.1.X.1.1, which is the target OID corresponding to the object to be managed.

[0049] In the above embodiments, the network asset fingerprint MIB database 71 can be located on the management device 72 equipped with NMS, or it can be located on other network devices connected to the management device.

[0050] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A network management system based on SNMP, characterized in that, It includes a raw data storage module, a data storage module, an SNMP management module, and an SNMP agent module, among which, The raw data storage module is used to store the raw dataset of the device with SNMP service enabled. The data in the raw dataset is collected from the cyberspace mapping website and deduplicated. The deduplicated data uniquely corresponds to a device model. The raw dataset includes the OID of the device with SNMP service enabled. The data storage module is used to store at least one OID information set, wherein a specified position of each OID in each OID information set carries a string of a predetermined format configured by the same manufacturer; The SNMP management module is used to group the original dataset into at least one OID information set and send it to the data storage module; query the target OID corresponding to the managed object from the data storage module based on the manufacturer information of the managed object and send the target OID to the SNMP agent module; and manage the managed object based on the results returned by the SNMP agent module. The SNMP agent module is used to obtain the query results bound to the object to be managed based on the target OID, and return them to the SNMP management module.

2. The system according to claim 1, characterized in that, The data storage module includes a matching rule storage submodule, a data storage submodule, and a matching result storage submodule, wherein, The matching rule storage submodule is used to store the rule dataset; wherein, the rule dataset includes the manufacturer name and the manufacturer OID that uniquely corresponds to the manufacturer name; The data storage submodule is used to store at least one of the OID information sets, wherein a specified position of each OID in each OID information set carries a string of a predetermined format configured by the same manufacturer; The SNMP management module is further configured to determine a target OID information set that matches the string at a specified position of the OID with the manufacturer's OID, and send the target OID information set to the matching result storage submodule; The matching result storage submodule is used to store at least one target OID information set, each target OID information set including the OID information set that matches the manufacturer OID, and the manufacturer name corresponding to the manufacturer OID.

3. The system according to claim 1, characterized in that, The data storage module and the SNMP management module are located in the same device.

4. The system according to claim 1, characterized in that, The SNMP management module is located on the management device.

5. The system according to claim 1, characterized in that, The SNMP agent module is located on the managed device.

6. A network architecture based on SNMP, characterized in that, This includes the original database, the network asset fingerprint MIB database, management devices equipped with NMS, and a set of nodes equipped with SNMP agent modules. The original database is used to store the original dataset of devices with SNMP service enabled. The data in the original dataset is collected from a cyberspace mapping website and deduplicated. Each deduplicated data uniquely corresponds to a device model. The original dataset includes the OID of the device with SNMP service enabled. The network asset fingerprint MIB database is used to store at least one set of OID information, and each OID in each set of OID information carries a string of a predetermined format configured by the same vendor at a specified position. The management device equipped with NMS is used to group the original dataset into at least one set of OID information and send it to the network asset fingerprint MIB database. Based on the vendor information of the object to be managed, it queries the target OID corresponding to the object to be managed from the network asset fingerprint MIB database and sends the target OID to the node set equipped with the SNMP agent module. Based on the results returned by the node set equipped with the SNMP agent module, it manages the object to be managed. The node set equipped with the SNMP agent module is used to obtain the query results bound to the object to be managed based on the target OID, and return them to the management device equipped with NMS.

7. The network architecture according to claim 6, characterized in that, The network asset fingerprint MIB database includes a matching rule table, a data storage table, and a matching result table, wherein... The matching rule table is used to store the rule dataset; wherein, the rule dataset includes the manufacturer name and the manufacturer OID that uniquely corresponds to the manufacturer name; The data storage table is used to store at least one of the OID information sets, and each OID in each OID information set carries a string of a predetermined format configured by the same manufacturer at a specified position; The management device equipped with NMS is also used to determine the target OID information set that matches the string at a specified position of the OID with the manufacturer's OID, and send the target OID information set to the matching result table; The matching result table is used to store at least one of the target OID information sets; each target OID information set includes the OID information set that matches the vendor OID, and the vendor name corresponding to the vendor OID.

8. The network architecture according to claim 6, characterized in that, The network asset fingerprint MIB database is located on the management device equipped with NMS.

Images