Network topology data acquisition and generation method and system based on SNMP (Simple Network Management Protocol) and LLDP (Link Layer Distribution Protocol)

Abstract

The invention provides a network topology data acquisition and generation method and system based on SNMP and LLDP protocols. The method comprises the following steps: step 1, carrying out standardized modeling on network equipment; step 2, acquiring system information, physical asset information and interface routing information of the network equipment based on an SNMP (Simple Network Management Protocol); 3, instantiating the model of the network equipment; step 4, acquiring local port information and far-end neighbor information of the network equipment based on an LLDP protocol; step 5, establishing a neighbor relationship between the network devices; and step 6, based on the model instance and the neighbor relationship of the network equipment, constructing a network topological graph with observability, including an equipment alarm state and real-time acquisition data. According to the method, the network equipment is instantiated based on the acquired information, the connection relationship is established for different network equipment, and finally, the observable network topology is constructed for operation and maintenance personnel in combination with network equipment alarm and real-time data acquisition.

Description

Technical Field

[0001] The present invention relates to the technical field of network topology data collection and generation, and in particular to a method and system for collecting and generating network topology data based on SNMP and LLDP protocols. Background Art

[0002] With the rapid development of mobile Internet and cloud computing, the requirements for the stability of network environment operation are constantly increasing. In the long-term iterative update process of cloud environment, the network architecture and deployment of cloud environment will inevitably change. How to provide stable, intuitive and convenient operation and management methods for operation and maintenance personnel is a problem that needs to be solved at present.

[0003] Patent application document CN110401568A discloses a network topology discovery method and device, including: receiving a link layer discovery protocol LLDP message sent by a sender; obtaining information about a receiving panel port that receives the LLDP message; generating neighbor information based on the LLDP message and the information about the receiving panel port; sending the neighbor information to a server, and 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 the present invention. Summary of the invention

[0004] In view of the defects in the prior art, the object of the present invention is to provide a method and system for collecting and generating network topology data based on SNMP and LLDP protocols.

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

[0006] Step 1: Conduct standardized modeling of network equipment;

[0007] Step 2: Based on the SNMP protocol, obtain the system information, physical asset information and interface routing information of the network device;

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

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

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

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

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

[0013] A physical network hardware device is defined as an entity that has zero or more cards and forms a one-to-one relationship with stacking devices;

[0014] A card is defined as a component that is hosted in a chassis and contains zero or more daughter cards;

[0015] A daughter card is defined as a component that is hosted on a motherboard and contains zero to multiple physical interfaces;

[0016] A physical interface is defined as a component that is hosted on a card or daughter card and contains zero or one transceiver.

[0017] Preferably, the step 3 comprises:

[0018] The physical network hardware device is 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 relationship between the board and the physical network hardware device 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 relationship between the physical interface and the board is established by the parent entity index.

[0021] Preferably, step 5 comprises:

[0022] According to the local port number field, the local device port information and the remote neighbor information are associated one-to-many, and the remote neighbor information and the remote device management address are associated one-to-one;

[0023] According to the port ID field, the local device port information is associated with the interface one-to-one; according to the interface index field, the interface is associated with the interface IPv4 address one-to-one;

[0024] According to the system name field, the remote neighbor information and the system information are associated one-to-one, and the following conditions are met: the device ID of the remote neighbor information exists in the interface; according to the port ID field, the remote neighbor information and the interface are associated one-to-one. When the neighbor device is not found, the management address of the remote device management address is used as the remote device management IP, and the SNMP version number, SNMP port, and SNMP community word information of the current device are used to try to collect data; after successful collection, the above operations are repeated; if the collection fails, the failure result is recorded, and no collection will be performed during this execution.

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

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

[0027] Module M1: Standardized modeling of network equipment;

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

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

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

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

[0032] Module M6: Based on the model instances and neighbor relationships of network devices, a network topology diagram with observability is constructed, including device alarm status and real-time collection data.

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

[0034] A physical network hardware device is defined as an entity that has zero or more cards and forms a one-to-one relationship with stacking devices;

[0035] A card is defined as a component that is hosted in a chassis and contains zero or more daughter cards;

[0036] A daughter card is defined as a component that is hosted on a motherboard and contains zero to multiple physical interfaces;

[0037] A physical interface is defined as a component that is hosted on a card or daughter card and contains zero or one transceiver.

[0038] Preferably, the module M3 comprises:

[0039] The physical network hardware device is 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 relationship between the board and the physical network hardware device 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 relationship between the physical interface and the board is established by the parent entity index.

[0042] Preferably, the module M5 comprises:

[0043] According to the local port number field, the local device port information and the remote neighbor information are associated one-to-many, and the remote neighbor information and the remote device management address are associated one-to-one;

[0044] According to the port ID field, the local device port information is associated with the interface one-to-one; according to the interface index field, the interface is associated with the interface IPv4 address one-to-one;

[0045] According to the system name field, the remote neighbor information and the system information are associated one-to-one, and the following conditions are met: the device ID of the remote neighbor information exists in the interface; according to the port ID field, the remote neighbor information and the interface are associated one-to-one. When the neighbor device is not found, the management address of the remote device management address is used as the remote device management IP, and the SNMP version number, SNMP port, and SNMP community word information of the current device are used to try to collect data; after successful collection, the above operations are repeated; if the collection fails, the failure result is recorded, and no collection will be performed during this execution.

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

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

[0048] (1) The present invention can be widely used in scenarios that improve the observability of network devices in cloud environments: 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 a stable, intuitive, and convenient operation and management method;

[0049] (2) The design mechanism described in the present invention: standardizes modeling for network devices, collects system information, physical information, interface information, and LLDP protocol information of network devices through SNMP and LLDP protocols, and then instantiates the network devices, ultimately building an observable network topology; the operation and maintenance personnel can view the network architecture based on the network topology, and view real-time network device alarms and collected data; developers can also obtain the above-mentioned collected data and network topology data based on the present invention, so as to quickly develop customized network topologies;

[0050] (3) The present invention enhances the management and observability of network equipment in a cloud environment: based on a standardized modeling system, the asset information of network equipment can be quickly registered in the cloud environment; based on the network topology, the alarm and real-time collection data in the cloud environment are supplemented, which improves the efficiency of operation and maintenance personnel in obtaining information about the network architecture and network status in the cloud environment, and can quickly perform network fault analysis and location; developers can also obtain network collection data and network topology data based on the present invention, so that they can quickly get started with developing customized network topologies. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0052] Figure 1 Modeling examples for network devices;

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

[0054] Figure 3 Associated with lldp table;

[0055] Figure 4 Supplement local machine information for lldp;

[0056] Figure 5 Supplement neighbor information for lldp;

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

[0058] Figure 7 Node details information;

[0059] Figure 8 For edge details. DETAILED DESCRIPTION

[0060] The present invention is described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those of ordinary skill in the art, several changes and improvements can also be made without departing from the concept of the present invention. These all belong to the protection scope of the present invention.

[0061] Example 1

[0062] The present invention provides a network topology data collection and generation method based on SNMP and LLDP protocols in a cloud environment. Figure 2 , its working principle mainly includes the following processes:

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

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

[0065] Step 3: Based on the process SNMP data collection, the network device model is instantiated.

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

[0067] Step 5: Based on SNMP and LLDP data collection, 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 diagram, including device alarm status, real-time collection data, etc.

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

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

[0071]

[0072]

[0073] Table 1 Physical network hardware device model

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

[0075] Field Name Field Type illustrate IfSubcard String Is it a sub-card? installSlot String Installation slot number Firmware String Firmware version softwareVersion String Software Version HardwareVersion String Hardware version Vendor String Manufacturer DeviceType String model SerialsNO String Serial Number Comments String Remark manufactureDate String Date of manufacture

[0076] Table 2 Board Model

[0077] Physical interface: The physical interface is hosted on the board (including daughter cards), and a physical interface has 0 to 1 transceiver.

[0078] Field Name Field Type illustrate interfaceLabel String Interface ID Interface No String Interface number phsicalInterfaceType String Physical interface type phsicalInterfaceProtocol String Physical interface protocol phsicalInterfaceIfOptical String Whether the physical interface is 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 table structure entPhysicalTable: equipment physical entity information table, the index is entPhysicalIndex.

[0085]

[0086]

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

[0088]

[0089]

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

[0091]

[0092] Table 7 ipAddrTable table structure

[0093] In step 3, the network device is instantiated based on the four tables SystemInfoTable, entPhysicalTable, ifTable and ipAddrTable. Instantiation rules:

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

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

[0096] Physical interface identification method: the record whose entity type value is equal to 10 in the physical entity table; at the same time, the parent entity index of the record is equal to the entity index of the board record, and the association relationship between the physical interface and the board can be established based on the index.

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

[0098] lldpLocPortTable: local device port information table. The index of this table is lldpLocPortNum.

[0099]

[0100] Table 8 lldpLocPortTable table structure

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

[0102]

[0103]

[0104] Table 9 lldpRemTable table structure

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

[0106]

[0107] Table 10lldpRemManAddrTable table structure

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

[0109] Associate the three tables related to device neighbors: associate the local device port information table and the remote neighbor information table one-to-many according to the local port number field; associate the remote neighbor information table and the remote device management address table one-to-one according to the local port number field, such as Figure 3 .

[0110] Supplement device local port information: associate the local device port information table and the interface table one-to-one according to the field port ID; associate the interface table and the interface IPv4 address table one-to-one according to the field interface index, such as Figure 4 .

[0111] Supplement neighbor device and port information: associate the remote neighbor information table and system information one-to-one according to the field system name, and meet the following conditions: the device ID (MAC address) of the remote neighbor information table exists in the interface table; associate the remote neighbor information table and interface table one-to-one according to the field port ID. If no neighbor device is found, use the management address of the remote device management address table as the remote device management IP, as well as the SNMP version number, SNMP port, and SNMP community word information of the current device to try to collect data; after successful collection, repeat the above operation; if the collection fails, record the failure result, and no collection will be performed during this execution. Figure 5 .

[0112] In step 6, the nodes (devices) and edges (links) required for the network topology are generated. Nodes correspond to network devices, and edges correspond to the connection relationship between network device ports. A complete topology is composed of multiple node objects and edge objects, such as Figure 6 .

[0113] Network topology node infrastructure: A topology node contains at least node ID, node name, and node type.

[0114]

[0115] Table 11 Network topology node infrastructure

[0116] Network topology edge infrastructure: An edge contains at least the start point ID, the start point name, the end point ID, and the end point name. Note: Edges can be non-directional.

[0117] Field Name Field Type illustrate source String The starting point ID of the edge sourceLabel String The name of the edge's starting point target String The end point ID of the edge targetLabel String The end point name of the edge

[0118] Table 12 Network topology edge infrastructure

[0119] Network topology node structure: Added node alarm status, attribute information, and real-time collection information to the topology node infrastructure, such as Figure 7 .

[0120]

[0121]

[0122] Table 13 Network topology node structure

[0123] Network topology edge structure: Added alarm status, attribute information, and real-time collection information to the topology edge infrastructure, such as Figure 8 .

[0124]

[0125]

[0126] Table 14 Network topology edge structure

[0127] Example 2

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

[0129] The operation of the network topology data collection and generation system requires the following conditions: a) The management IP, SNMP version number, SNMP port, and SNMP community word information of the network device have been provided; b) The network topology data collection and generation device can access the SNMP service of the network device; c) The network device supports and enables the SNMP protocol; d) The network device supports and enables the LLDP protocol.

[0130] Specifically, the network topology data collection and generation system based on SNMP and LLDP protocols includes: module M1: standardizing network equipment modeling; module M2: obtaining system information, physical asset information and interface routing information of network equipment based on SNMP protocol; module M3: instantiating the model of network equipment based on the system information, physical asset information and interface routing information of network equipment; module M4: obtaining local port information and remote neighbor information of network equipment based on LLDP protocol; module M5: establishing neighbor relationships between network devices based on the system information, physical asset information and interface routing information of network equipment, as well as the local port information and remote neighbor information of network equipment; module M6: constructing an observable network topology diagram based on the model instance and neighbor relationship of network equipment, including device alarm status and real-time collection data.

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

[0132] A physical network hardware device is defined as an entity that has zero or more cards and forms a one-to-one relationship with stacking devices;

[0133] A card is defined as a component that is hosted in a chassis and contains zero or more daughter cards;

[0134] A daughter card is defined as a component that is hosted on a motherboard and contains zero to multiple physical interfaces;

[0135] A physical interface is defined as a component that is hosted on a card or daughter card and contains zero or one transceiver.

[0136] The module M3 comprises:

[0137] The physical network hardware device is 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 relationship between the board and the physical network hardware device 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 relationship between the physical interface and the board is established by the parent entity index.

[0140] The module M5 comprises:

[0141] According to the local port number field, the local device port information and the remote neighbor information are associated one-to-many, and the remote neighbor information and the remote device management address are associated one-to-one;

[0142] According to the port ID field, the local device port information is associated with the interface one-to-one; according to the interface index field, the interface is associated with the interface IPv4 address one-to-one;

[0143] According to the system name field, the remote neighbor information and the system information are associated one-to-one, and the following conditions are met: the device ID of the remote neighbor information exists in the interface; according to the port ID field, the remote neighbor information and the interface are associated one-to-one. When the neighbor device is not found, the management address of the remote device management address is used as the remote device management IP, and the SNMP version number, SNMP port, and SNMP community word information of the current device are used to try to collect data; after successful collection, the above operations are repeated; if the collection fails, the failure result is recorded, and no collection will be performed during this execution.

[0144] The module M6 includes: generating nodes and edges required for a network topology diagram, wherein nodes correspond to network devices, and edges correspond to the connection relationship between ports of network devices, each node contains node ID, node name and node type information, each edge contains starting point ID, starting point name, end point ID and end point name information, and adds alarm status, attribute information and real-time collection information as needed.

[0145] The network topology data collection and generation system based on SNMP and LLDP protocols is used to complete the network topology data collection and generation in the cloud platform. The characteristics of this platform are: complex network environment, a wide variety of network equipment, and increasing network-related operation and maintenance pressure. The display and operation process of network topology data collection and generation using the present invention is as follows:

[0146] a) Platform administrators create standardized models for network devices, including physical network hardware, boards, and physical interfaces.

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

[0148] c) The operation and maintenance personnel enter the network device details page or the system details page of the network device and turn on the switch for building the network topology.

[0149] d) Wait for the network topology construction job to start, which is usually done in the early morning of the next day. This step is imperceptible to the operation and maintenance personnel and includes five main processes: SNMP collection, instantiation model, LLDP collection, establishment of neighbor relationships, and topology construction.

[0150] e) The operation and maintenance personnel enter the corresponding system or customize the network topology diagram to check whether the newly added network devices and connection relationships 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 know that, in addition to implementing the system, device and its various modules provided by the present invention in a purely computer-readable program code, it is entirely possible to implement the same program 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, device and its various modules provided by the present invention can be considered as a hardware component, and the modules included therein for implementing various programs can also be considered as structures within the hardware component; the modules for implementing various functions can also be considered as both software programs for implementing the method and structures within the hardware component.

[0152] The above describes the specific embodiments of the present invention. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Claims

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

2. The network topology data collection and generation method based on SNMP and LLDP protocols according to claim 1 is characterized in that: The network device model includes physical network hardware, boards, daughter cards and physical interfaces, wherein: A physical network hardware device is defined as an entity that has zero or more cards and forms a one-to-one relationship with stacking devices; A card is defined as a component that is hosted in a chassis and contains zero or more daughter cards; A daughter card is defined as a component that is hosted on a motherboard and contains zero to multiple physical interfaces; A physical interface is defined as a component that is hosted on a card or daughter card and contains zero or one transceiver.

3. The network topology data collection and generation method based on SNMP and LLDP protocols according to claim 1 is characterized in that: The step 3 comprises: The physical network hardware device is 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 relationship between the board and the physical network hardware device 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 relationship between the physical interface and the board is established by the parent entity index.

4. The network topology data collection and generation method based on SNMP and LLDP protocols according to claim 1, characterized in that: The step 5 comprises: According to the local port number field, the local device port information and the remote neighbor information are associated one-to-many, and the remote neighbor information and the remote device management address are associated one-to-one; According to the port ID field, the local device port information is associated with the interface one-to-one; according to the interface index field, the interface is associated with the interface IPv4 address one-to-one; According to the system name field, the remote neighbor information and the system information are associated one-to-one, and the following conditions are met: the device ID of the remote neighbor information exists in the interface; according to the port ID field, the remote neighbor information and the interface are associated one-to-one. When the neighbor device is not found, the management address of the remote device management address is used as the remote device management IP, and the SNMP version number, SNMP port, and SNMP community word information of the current device are used to try to collect data; after successful collection, the above operations are repeated; if the collection fails, the failure result is recorded, and no collection will be performed during this execution.

5. The method for collecting and generating network topology data based on SNMP and LLDP protocols according to claim 1, characterized in that: The step 6 includes: generating nodes and edges required for the network topology diagram, wherein the nodes correspond to network devices, and the edges correspond to the connection relationship between the ports of the network devices, each node contains a node ID, a node name and a node type information, and each edge contains a starting point ID, a starting point name, an end point ID and an end point name information, and adds alarm status, attribute information and real-time collection information as needed.

6. A network topology data collection and generation system based on SNMP and LLDP protocols, characterized in that: include: Module M1: Standardized modeling of network equipment; Module M2: Based on the SNMP protocol, obtain the system information, physical asset information and interface routing information of network devices; Module M3: instantiate the model of the network device based on the system information, physical asset information and interface routing information of the network device; Module M4: Based on the LLDP protocol, obtain the local port information and remote neighbor information of the network device; Module M5: Establishing neighbor relationships between network devices based on system information, physical asset information, and interface routing information of network devices, as well as local port information and remote neighbor information of network devices; Module M6: Based on the model instances and neighbor relationships of network devices, a network topology diagram with observability is constructed, including device alarm status and real-time collection data.

7. The network topology data collection 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: A physical network hardware device is defined as an entity that has zero or more cards and forms a one-to-one relationship with stacking devices; A card is defined as a component that is hosted in a chassis and contains zero or more daughter cards; A daughter card is defined as a component that is hosted on a motherboard and contains zero to multiple physical interfaces; A physical interface is defined as a component that is hosted on a card or daughter card and contains zero or one transceiver.

8. The network topology data collection and generation system based on SNMP and LLDP protocols according to claim 6, characterized in that: The module M3 comprises: The physical network hardware device is 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 relationship between the board and the physical network hardware device 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 relationship between the physical interface and the board is established by the parent entity index.

9. The network topology data collection and generation system based on SNMP and LLDP protocols according to claim 6, characterized in that: The module M5 comprises: According to the local port number field, the local device port information and the remote neighbor information are associated one-to-many, and the remote neighbor information and the remote device management address are associated one-to-one; According to the port ID field, the local device port information is associated with the interface one-to-one; according to the interface index field, the interface is associated with the interface IPv4 address one-to-one; According to the system name field, the remote neighbor information and the system information are associated one-to-one, and the following conditions are met: the device ID of the remote neighbor information exists in the interface; according to the port ID field, the remote neighbor information and the interface are associated one-to-one. When the neighbor device is not found, the management address of the remote device management address is used as the remote device management IP, and the SNMP version number, SNMP port, and SNMP community word information of the current device are used to try to collect data; after successful collection, the above operations are repeated; if the collection fails, the failure result is recorded, and no collection will be performed during this execution.

10. The network topology data collection and generation system based on SNMP and LLDP protocols according to claim 6, characterized in that: The module M6 includes: generating nodes and edges required for a network topology diagram, wherein nodes correspond to network devices, and edges correspond to the connection relationship between ports of network devices, each node contains node ID, node name and node type information, each edge contains starting point ID, starting point name, end point ID and end point name information, and adds alarm status, attribute information and real-time collection information as needed.

Images