Network topology data collection and generation method and system based on snmp and lldp protocol

Abstract

The application provides a network topology data collection and generation method and system based on SNMP and LLDP protocols, comprising the following steps: step 1, standardization modeling of network equipment; step 2, based on the SNMP protocol, system information, physical asset information and interface routing information of the network equipment are acquired; step 3, the model of the network equipment is instantiated; step 4, based on the LLDP protocol, local port information and remote neighbor information of the network equipment are acquired; step 5, the neighbor relationship between the network equipment is established; and step 6, based on the model instance and the neighbor relationship of the network equipment, a network topology graph with observability is constructed, including device alarm states and real-time collection data. The application instantiates the network equipment based on the collected information, establishes the connection relationship for different network equipment, and finally combines the network equipment alarm and the real-time collection data to construct the network topology with observability for the operation and maintenance personnel.

Description

Technical Field

[0001] This invention relates to the field of network topology data acquisition and generation technology, specifically to a method and system for network topology data acquisition and generation based on SNMP and LLDP protocols. Background Technology

[0002] With the rapid development of mobile internet and cloud computing, the requirements for network environment stability are constantly increasing. During the long-term iterative updates of cloud environments, changes in network architecture and deployment are inevitable. Providing operations and maintenance personnel with stable, intuitive, and convenient operation and management tools is a problem that needs to be solved.

[0003] Patent application CN110401568A discloses a network topology discovery method and device, comprising: receiving a Link Layer Discovery Protocol (LLDP) message sent by a sender; obtaining information of the receiving panel port that receives the LLDP message; generating neighbor information based on the LLDP message and the receiving panel port information; and sending the neighbor information to a server, wherein the neighbor information is used to trigger the server to determine network topology information based on the neighbor information sent by all network devices. However, this patent cannot completely solve the existing technical problems, nor can it meet the needs of this invention. Summary of the Invention

[0004] To address the shortcomings of existing technologies, the purpose of this invention is to provide a method and system for acquiring and generating network topology data based on SNMP and LLDP protocols.

[0005] The network topology data acquisition and generation method based on SNMP and LLDP protocols provided by the present invention includes:

[0006] Step 1: Perform standardized modeling of network devices;

[0007] Step 2: Obtain system information, physical asset information, and interface routing information of network devices based on the SNMP protocol;

[0008] Step 3: Instantiate the network device model based on the network device's system information, physical asset information, and interface routing information;

[0009] Step 4: Based on the LLDP protocol, obtain the local port information and remote neighbor information of the network devices;

[0010] Step 5: Based on the system information, physical asset information, and interface routing information of the network devices, as well as the local port information and remote neighbor information of the network devices, establish neighbor relationships between network devices;

[0011] Step 6: Based on the model instances and neighbor relationships of network devices, construct an observable network topology graph, including device alarm status and real-time collected data.

[0012] Preferably, the network device model includes physical network hardware, boards, daughter cards, and physical interfaces, wherein:

[0013] Physical network hardware devices are defined as entities that have zero or more boards and form a one-to-one relationship with stacked devices;

[0014] A board is defined as a component that is hosted in a chassis and contains 0 to a dozen daughter cards;

[0015] A daughter card is defined as a component that is hosted on a board and contains 0 or more physical interfaces;

[0016] A physical interface is defined as a component that is hosted on a board or daughterboard and contains 0 to 1 transceivers.

[0017] Preferably, step 3 includes:

[0018] Physical network hardware devices are identified by the first entity type value in the physical entity table;

[0019] The board is identified by the second entity type value in the physical entity table, and the association between the board and the physical network hardware is established through the parent entity index;

[0020] The physical interface is identified by the third entity type value in the physical entity table, and the association between the physical interface and the board is established through the parent entity index.

[0021] Preferably, step 5 includes:

[0022] Based on the local port number field, the local device port information and remote neighbor information are associated in a one-to-many manner, and the remote neighbor information and remote device management address are associated in a one-to-one manner.

[0023] Based on the port ID field, a one-to-one association is established between the local device port information and the interface; based on the interface index field, a one-to-one association is established between the interface and the interface IPv4 address.

[0024] Based on the system name field, remote neighbor information and system information are associated one-to-one, while also meeting the following conditions: the device ID of the remote neighbor information exists in the interface; based on the port ID field, remote neighbor information and interface are associated one-to-one. If no neighbor device is found, the management address of the remote device's management address is used as the remote device's management IP, along with the current device's SNMP version number, SNMP port, and SNMP community information, to attempt data collection; if collection is successful, the above operation is repeated; if collection fails, the failure result is recorded, and no further collection will be performed during this execution.

[0025] Preferably, step 6 includes: generating the nodes and edges required for the network topology map, wherein the nodes correspond to network devices, the edges correspond to the connection relationships between network device ports, each node contains node ID, node name and node type information, each edge contains start point ID, start point name, end point ID and end point name information, and alarm status, attribute information and real-time collected information are added as needed.

[0026] The network topology data acquisition and generation system based on SNMP and LLDP protocols provided by the present invention includes:

[0027] Module M1: Performs standardized modeling of network devices;

[0028] Module M2: Based on the SNMP protocol, it obtains system information, physical asset information, and interface routing information of network devices;

[0029] Module M3: Instantiates the model of the network device based on the network device's system information, physical asset information, and interface routing information;

[0030] Module M4: Based on the LLDP protocol, it obtains local port information and remote neighbor information of network devices;

[0031] Module M5: Based on the system information, physical asset information, and interface routing information of network devices, as well as the local port information and remote neighbor information of network devices, establish neighbor relationships between network devices;

[0032] Module M6: Based on model instances of network devices and neighbor relationships, it constructs an observable network topology graph, including device alarm status and real-time collected data.

[0033] Preferably, the network device model includes physical network hardware, boards, daughter cards, and physical interfaces, wherein:

[0034] Physical network hardware devices are defined as entities that have zero or more boards and form a one-to-one relationship with stacked devices;

[0035] A board is defined as a component that is hosted in a chassis and contains 0 to a dozen daughter cards;

[0036] A daughter card is defined as a component that is hosted on a board and contains 0 or more physical interfaces;

[0037] A physical interface is defined as a component that is hosted on a board or daughterboard and contains 0 to 1 transceivers.

[0038] Preferably, the module M3 includes:

[0039] Physical network hardware devices are identified by the first entity type value in the physical entity table;

[0040] The board is identified by the second entity type value in the physical entity table, and the association between the board and the physical network hardware is established through the parent entity index;

[0041] The physical interface is identified by the third entity type value in the physical entity table, and the association between the physical interface and the board is established through the parent entity index.

[0042] Preferably, the module M5 includes:

[0043] Based on the local port number field, the local device port information and remote neighbor information are associated in a one-to-many manner, and the remote neighbor information and remote device management address are associated in a one-to-one manner.

[0044] Based on the port ID field, a one-to-one association is established between the local device port information and the interface; based on the interface index field, a one-to-one association is established between the interface and the interface IPv4 address.

[0045] Based on the system name field, remote neighbor information and system information are associated one-to-one, while also meeting the following conditions: the device ID of the remote neighbor information exists in the interface; based on the port ID field, remote neighbor information and interface are associated one-to-one. If no neighbor device is found, the management address of the remote device's management address is used as the remote device's management IP, along with the current device's SNMP version number, SNMP port, and SNMP community information, to attempt data collection; if collection is successful, the above operation is repeated; if collection fails, the failure result is recorded, and no further collection will be performed during this execution.

[0046] Preferably, the module M6 includes: nodes and edges required to generate a network topology map, wherein nodes correspond to network devices, edges correspond to the connection relationships between network device ports, each node contains node ID, node name and node type information, each edge contains start point ID, start point name, end point ID and end point name information, and alarm status, attribute information and real-time collected information are added as needed.

[0047] Compared with the prior art, the present invention has the following beneficial effects:

[0048] (1) This invention can be widely applied to scenarios that improve the observability of network devices in the cloud environment: by collecting SNMP and LLDP protocol data of network devices and modeling network devices based on a standardized modeling system, an observable network topology diagram is finally generated, providing operation and maintenance personnel with stable, intuitive and convenient operation and maintenance and management methods.

[0049] (2) The design mechanism described in this invention is as follows: Standardized modeling of network devices is performed, and the system information, physical information, interface information, and LLDP protocol information of network devices are collected through SNMP and LLDP protocols. The network devices are then instantiated, and finally an observable network topology is constructed. The operation and maintenance team can view the network architecture based on this network topology and view real-time network device alarms and collected data. Developers can also use this invention to obtain the above-mentioned collected data and network topology data, thereby enabling them to quickly start developing custom network topologies.

[0050] (3) This invention enhances the ability to manage and observe network devices in the cloud environment: Based on a standardized modeling system, the asset information of network devices can be quickly registered in the cloud environment; at the same time, based on the network topology, alarms and real-time data collection in the cloud environment are supplemented, improving the efficiency of operation and maintenance personnel in obtaining information on network architecture and network status in the cloud environment, and enabling rapid network fault analysis and location; developers can also use this invention to obtain network collection data and network topology data, thereby enabling them to quickly start developing custom network topologies. Attached Figure Description

[0051] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0052] Figure 1 Example of modeling a network device;

[0053] Figure 2 The main working principle and flow of the device;

[0054] Figure 3 Join the lldp table;

[0055] Figure 4 To supplement local machine information for lldp;

[0056] Figure 5 Supplement neighbor information for LLDP;

[0057] Figure 6 Here is an example of a network topology;

[0058] Figure 7 For node details;

[0059] Figure 8 For edge details. Detailed Implementation

[0060] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the protection scope of the present invention.

[0061] Example 1

[0062] This invention provides a method for collecting and generating network topology data based on SNMP and LLDP protocols in a cloud environment, such as... Figure 2 Its working principle mainly includes the following process:

[0063] Step 1: Standardize network device modeling: Establish physical models and relationships for network devices, such as... Figure 1 .

[0064] Step 2: Based on the SNMP protocol, obtain system information, physical asset information, interface routing information, etc. of network devices.

[0065] Step 3: Instantiate the network device model by collecting data based on the SNMP process.

[0066] Step 4: Based on the LLDP protocol, obtain the local port information and remote neighbor information of the network device.

[0067] Step 5: Collect data based on SNMP and LLDP to establish neighbor relationships between network devices, that is, links between physical interfaces.

[0068] Step 6: Based on the model instances and neighbor relationships of network devices, construct an observable network topology graph, including device alarm status, real-time collected data, etc.

[0069] The network device models mainly involved in step 1 include:

[0070] Physical network hardware devices: commonly known as chassis or racks, a physical network hardware device has 0 to many cards, and has a one-to-one relationship with stacked devices. Core switches and physical firewalls can be considered as physical network hardware devices.

[0071]

[0072]

[0073] Table 1 Physical Network Hardware Model

[0074] Boards: Boards are divided into two types: daughter cards and board cards (non-daughter cards); board cards are hosted in the chassis while daughter cards are hosted in the board cards; a board card has 0 to more daughter cards, and a board card / daughter card has 0 to more physical interfaces.

[0075] field name Field type illustrate If Subcard String Is it a child card? installSlot String Installation slot number Firmware String Firmware version softwareVersion String Software version HardwareVersion String Hardware version Vendor String Manufacturers DeviceType String model SerialsNO String Serial Number Comments String Remark manufactureDate String Manufacturing date

[0076] Table 2 Board Model

[0077] Physical interface: The physical interface is hosted on the board (including daughter card). One physical interface has 0 to 1 transceivers.

[0078] field name Field type illustrate interfaceLabel String Interface identifier InterfaceNo String Interface number PhsicalInterfaceType String Physical interface type Physical Interface Protocol String Physical Interface Protocol phsicalInterfaceIfOptical String Is the physical interface an optical port? MacAddress String Mac address InterfaceStatus String Interface status Comments String Remark

[0079] Table 3 Physical Interface Model

[0080] The core data structures involved in step 2 are:

[0081] SystemInfoTable: Device system information table, with only one record for each device.

[0082]

[0083]

[0084] Table 4 SystemInfoTable structure entPhysicalTable: Device physical entity information table, indexed by entPhysicalIndex.

[0085]

[0086]

[0087] Table 5. Structure of entPhysicalTable: ifTable: Interface table, the number of entries is determined by the value of ifNumber, and the index is ifIndex.

[0088]

[0089]

[0090] Table 6 ifTable structure ipAddrTable: Interface IPv4 address table, the index of this table is ipAdEntAddr.

[0091]

[0092] Table 7. Structure of ipAddrTable

[0093] Step 3 instantiates the network device based on four tables: SystemInfoTable, entPhysicalTable, ifTable, and ipAddrTable. Instantiation rules:

[0094] Physical network hardware device identification method: Records in the physical entity table whose entity type value is equal to 3.

[0095] Board identification method: Records in the physical entity table with an entity type value equal to 9; at the same time, the parent entity index of this record is equal to the entity index of the physical network hardware record. Based on this index, the association between the board and the physical network hardware can be established.

[0096] Physical interface identification method: The physical entity table contains records with an entity type value of 10; at the same time, the parent entity index of this record is equal to the entity index of the board record. Based on this index, the association between the physical interface and the board can be established.

[0097] The core data structures involved in step 4 are:

[0098] lldpLocPortTable: Local device port information table, the index of which is lldpLocPortNum.

[0099]

[0100] Table 8. Structure of lldpLocPortTable

[0101] lldpRemTable: Remote neighbor information table. The indexes of this table are lldpRemTimeMark, lldpRemLocalPortNum, and lldpRemIndex.

[0102]

[0103]

[0104] Table 9. Structure of lldpRemTable

[0105] lldpRemManAddrTable: Remote device management address table. The indexes of this table are lldpRemTimeMark, lldpRemLocalPortNum, lldpRemIndex, lldpRemManAddrSubtype, and lldpRemManAddr.

[0106]

[0107] Table 10lldpRemManAddrTable Structure

[0108] In step 5, the neighbor relationships between network devices can be calculated based on three tables: the local device port information table lldpLocPortTable, the remote neighbor information table lldpRemTable, and the remote device management address table lldpRemManAddrTable.

[0109] The three tables related to device neighbors are linked as follows: A one-to-many association is established between the local device port information table and the remote neighbor information table based on the local port number field; a one-to-one association is established between the remote neighbor information table and the remote device management address table based on the local port number field. Figure 3 .

[0110] Supplementing local device port information: Associating the local device port information table and interface table one-to-one based on the port ID field; associating the interface table and interface IPv4 address table one-to-one based on the interface index field, such as... Figure 4 .

[0111] Supplementing Neighbor Device and Port Information: Associating the remote neighbor information table and system information one-to-one based on the system name field, while also ensuring that the device ID (MAC address) in the remote neighbor information table exists in the interface table; associating the remote neighbor information table and interface table one-to-one based on the port ID field. If no neighbor device is found, using the management address from the remote device management address table as the remote device management IP, along with the current device's SNMP version number, SNMP port, and SNMP community information, an attempt is made to collect data; if data collection is successful, the above operations are repeated; if data collection fails, the failure result is recorded, and no further data collection will be performed during this execution. Figure 5 .

[0112] Step 6 generates the nodes (devices) and edges (links) needed to create the network topology. Nodes correspond to network devices, and edges correspond to the connections between network device ports. A complete topology consists of multiple node objects and edge objects, such as... Figure 6 .

[0113] Network topology node basic structure: A topology node must contain at least a node ID, a node name, and a node type.

[0114]

[0115] Table 11 Network Topology Node Basic Structure

[0116] Network topology edge basic structure: An edge must contain at least a start point ID, a start point name, an end point ID, and an end point name. Note: Edges can be undirected.

[0117] field name Field type illustrate source String edge starting point ID sourceLabel String The starting point name of the edge target String End point ID of the edge targetLabel String End point name of the edge

[0118] Table 12 Network Topology and Edge Basic Structure

[0119] Network topology node structure: The basic topology node structure has been enhanced with features including node alarm status, attribute information, and real-time collected information, such as... Figure 7 .

[0120]

[0121]

[0122] Table 13 Network Topology Node Structure

[0123] Network topology edge structure: Alarm status, attribute information, and real-time collected information have been added to the basic topology edge structure, such as... Figure 8 .

[0124]

[0125]

[0126] Table 14 Network Topology and Edge Structure

[0127] Example 2

[0128] The present invention also provides a network topology data acquisition and generation system based on SNMP and LLDP protocols. The network topology data acquisition and generation system based on SNMP and LLDP protocols can be implemented by executing the process steps of the network topology data acquisition and generation method based on SNMP and LLDP protocols. That is, those skilled in the art can understand the network topology data acquisition and generation method based on SNMP and LLDP protocols as a preferred embodiment of the network topology data acquisition and generation system based on SNMP and LLDP protocols.

[0129] The operation of the network topology data acquisition and generation system requires the following conditions to be met: a) Management IP address, SNMP version number, SNMP port, and SNMP community word information of the network device have been provided; b) The network topology data acquisition and generation device can access the SNMP service of the network device; c) The network device supports and has enabled the SNMP protocol; d) The network device supports and has enabled the LLDP protocol.

[0130] Specifically, the network topology data acquisition and generation system based on SNMP and LLDP protocols includes: Module M1: performing standardized modeling of network devices; Module M2: acquiring system information, physical asset information, and interface routing information of network devices based on the SNMP protocol; Module M3: instantiating the network device model based on the network device's system information, physical asset information, and interface routing information; Module M4: acquiring local port information and remote neighbor information of network devices based on the LLDP protocol; Module M5: establishing neighbor relationships between network devices based on the network device's system information, physical asset information, interface routing information, local port information, and remote neighbor information; Module M6: constructing an observable network topology map based on the network device model instances and neighbor relationships, including device alarm status and real-time acquired data.

[0131] The network device model includes physical network hardware, boards, daughter cards, and physical interfaces, wherein:

[0132] Physical network hardware devices are defined as entities that have zero or more boards and form a one-to-one relationship with stacked devices;

[0133] A board is defined as a component that is hosted in a chassis and contains 0 to a dozen daughter cards;

[0134] A daughter card is defined as a component that is hosted on a board and contains 0 or more physical interfaces;

[0135] A physical interface is defined as a component that is hosted on a board or daughterboard and contains 0 to 1 transceivers.

[0136] The module M3 includes:

[0137] Physical network hardware devices are identified by the first entity type value in the physical entity table;

[0138] The board is identified by the second entity type value in the physical entity table, and the association between the board and the physical network hardware is established through the parent entity index;

[0139] The physical interface is identified by the third entity type value in the physical entity table, and the association between the physical interface and the board is established through the parent entity index.

[0140] The module M5 includes:

[0141] Based on the local port number field, the local device port information and remote neighbor information are associated in a one-to-many manner, and the remote neighbor information and remote device management address are associated in a one-to-one manner.

[0142] Based on the port ID field, a one-to-one association is established between the local device port information and the interface; based on the interface index field, a one-to-one association is established between the interface and the interface IPv4 address.

[0143] Based on the system name field, remote neighbor information and system information are associated one-to-one, while also meeting the following conditions: the device ID of the remote neighbor information exists in the interface; based on the port ID field, remote neighbor information and interface are associated one-to-one. If no neighbor device is found, the management address of the remote device's management address is used as the remote device's management IP, along with the current device's SNMP version number, SNMP port, and SNMP community information, to attempt data collection; if collection is successful, the above operation is repeated; if collection fails, the failure result is recorded, and no further collection will be performed during this execution.

[0144] The module M6 includes: nodes and edges required to generate a network topology map, wherein nodes correspond to network devices, and edges correspond to the connection relationships between network device ports. Each node contains node ID, node name, and node type information, and each edge contains start point ID, start point name, end point ID, and end point name information. Alarm status, attribute information, and real-time collected information are added as needed.

[0145] This invention utilizes a network topology data acquisition and generation system based on SNMP and LLDP protocols to collect and generate network topology data within a cloud platform. This platform is characterized by a complex network environment, a wide variety of network devices, and increasing network-related operational pressures. The demonstration and operation process of using this invention to complete network topology data acquisition and generation are as follows:

[0146] a) The platform administrator creates a standardized model for network devices, including physical network hardware, cards, and physical interfaces.

[0147] b) The operations and maintenance personnel register the network device information in the cloud platform: management IP, SNMP version number, SNMP port, and SNMP community word information. They also check whether the cloud platform can access the network device's SNMP service.

[0148] c) The operations and maintenance personnel enter the network device details page or the network device system details page, and turn on the switch to build network topology.

[0149] d) Wait for the network topology building job to start, which usually takes place in the early morning of the following day. This step is invisible to operations and maintenance personnel and includes five main processes: SNMP data collection, model instantiation, LLDP data collection, establishing neighbor relationships, and topology building.

[0150] e) Operations personnel can access the corresponding system or a custom network topology diagram to check whether the newly added network devices and connections are successfully displayed in the topology, including node (network device) attribute information, alarm status, real-time collected data, and edge (link) attribute information, alarm status, and real-time collected data.

[0151] Those skilled in the art will understand that, in addition to implementing the system, apparatus, and their modules provided by this invention in purely computer-readable program code, the same program can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, the system, apparatus, and their modules provided by this invention can be considered a hardware component, and the modules included therein for implementing various programs can also be considered structures within the hardware component; alternatively, modules for implementing various functions can be considered both software programs implementing the method and structures within the hardware component.

[0152] Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. Unless otherwise specified, the embodiments and features described in this application can be arbitrarily combined with each other.

Claims

1. A network topology data collection and generation method based on SNMP and LLDP protocols, characterized in that, include: Step 1: Perform standardized modeling of network devices; Step 2: Obtain system information, physical asset information, and interface routing information of network devices based on the SNMP protocol; Step 3: Instantiate the network device model based on the network device's system information, physical asset information, and interface routing information; Step 4: Based on the LLDP protocol, obtain the local port information and remote neighbor information of the network devices; Step 5: Based on the system information, physical asset information, and interface routing information of the network devices, as well as the local port information and remote neighbor information of the network devices, establish neighbor relationships between network devices; Step 6: Based on the model instances and neighbor relationships of network devices, construct a network topology map, including device alarm status and real-time collected data.

2. The method for collecting and generating network topology data based on SNMP and LLDP protocols according to claim 1, characterized in that, The network device model includes physical network hardware, boards, daughter cards, and physical interfaces, wherein: Physical network hardware devices are defined as entities that have zero or more boards and form a one-to-one relationship with stacked devices; A board is defined as a component that is hosted in a chassis and contains 0 to a dozen daughter cards; A daughter card is defined as a component that is hosted on a board and contains 0 or more physical interfaces; A physical interface is defined as a component that is hosted on a board or daughterboard and contains 0 to 1 transceivers.

3. The method for collecting and generating network topology data based on SNMP and LLDP protocols according to claim 1, characterized in that, Step 3 includes: Physical network hardware devices are identified by the first entity type value in the physical entity table; The board is identified by the second entity type value in the physical entity table, and the association between the board and the physical network hardware is established through the parent entity index; The physical interface is identified by the third entity type value in the physical entity table, and the association between the physical interface and the board is established through the parent entity index.

4. The method for collecting and generating network topology data based on SNMP and LLDP protocols according to claim 1, characterized in that, Step 5 includes: Based on the local port number field, the local device port information and remote neighbor information are associated in a one-to-many manner, and the remote neighbor information and remote device management address are associated in a one-to-one manner. Based on the port ID field, a one-to-one association is established between the local device port information and the interface; based on the interface index field, a one-to-one association is established between the interface and the interface IPv4 address. Based on the system name field, remote neighbor information and system information are associated one-to-one, while also meeting the following conditions: the device ID of the remote neighbor information exists in the interface; based on the port ID field, remote neighbor information and interface are associated one-to-one. If no neighbor device is found, the management address of the remote device's management address is used as the remote device's management IP, along with the current device's SNMP version number, SNMP port, and SNMP community information, to attempt data collection; if collection is successful, the above operation is repeated; if collection fails, the failure result is recorded, and no further collection will be performed during this execution.

5. The method for acquiring and generating network topology data based on SNMP and LLDP protocols according to claim 1, characterized in that, Step 6 includes generating the nodes and edges required for the network topology map, where nodes correspond to network devices and edges correspond to the connection relationships between network device ports. Each node contains node ID, node name and node type information, and each edge contains start point ID, start point name, end point ID and end point name information. Alarm status, attribute information and real-time collected information are added as needed.

6. A network topology data acquisition and generation system based on SNMP and LLDP protocols, characterized in that, include: Module M1: Performs standardized modeling of network devices; Module M2: Based on the SNMP protocol, it obtains system information, physical asset information, and interface routing information of network devices; Module M3: Instantiates the model of the network device based on the network device's system information, physical asset information, and interface routing information; Module M4: Based on the LLDP protocol, it obtains local port information and remote neighbor information of network devices; Module M5: Based on the system information, physical asset information, and interface routing information of network devices, as well as the local port information and remote neighbor information of network devices, establish neighbor relationships between network devices; Module M6: Based on model instances of network devices and neighbor relationships, it constructs a network topology map, including device alarm status and real-time collected data.

7. The network topology data acquisition and generation system based on SNMP and LLDP protocols according to claim 6, characterized in that, The network device model includes physical network hardware, boards, daughter cards, and physical interfaces, wherein: Physical network hardware devices are defined as entities that have zero or more boards and form a one-to-one relationship with stacked devices; A board is defined as a component that is hosted in a chassis and contains 0 to a dozen daughter cards; A daughter card is defined as a component that is hosted on a board and contains 0 or more physical interfaces; A physical interface is defined as a component that is hosted on a board or daughterboard and contains 0 to 1 transceivers.

8. The network topology data acquisition and generation system based on SNMP and LLDP protocols according to claim 6, characterized in that, The module M3 includes: Physical network hardware devices are identified by the first entity type value in the physical entity table; The board is identified by the second entity type value in the physical entity table, and the association between the board and the physical network hardware is established through the parent entity index; The physical interface is identified by the third entity type value in the physical entity table, and the association between the physical interface and the board is established through the parent entity index.

9. The network topology data acquisition and generation system based on SNMP and LLDP protocols according to claim 6, characterized in that, The module M5 includes: Based on the local port number field, the local device port information and remote neighbor information are associated in a one-to-many manner, and the remote neighbor information and remote device management address are associated in a one-to-one manner. Based on the port ID field, a one-to-one association is established between the local device port information and the interface; based on the interface index field, a one-to-one association is established between the interface and the interface IPv4 address. Based on the system name field, remote neighbor information and system information are associated one-to-one, while also meeting the following conditions: the device ID of the remote neighbor information exists in the interface; based on the port ID field, remote neighbor information and interface are associated one-to-one. If no neighbor device is found, the management address of the remote device's management address is used as the remote device's management IP, along with the current device's SNMP version number, SNMP port, and SNMP community information, to attempt data collection; if collection is successful, the above operation is repeated; if collection fails, the failure result is recorded, and no further collection will be performed during this execution.

10. The network topology data acquisition and generation system based on SNMP and LLDP protocols according to claim 6, characterized in that, The module M6 includes: nodes and edges required to generate a network topology map, wherein nodes correspond to network devices, and edges correspond to the connection relationships between network device ports. Each node contains node ID, node name, and node type information, and each edge contains start point ID, start point name, end point ID, and end point name information. Alarm status, attribute information, and real-time collected information are added as needed.

Images