Network equipment data display method and device, equipment, storage medium and product

Abstract

The invention relates to a network equipment data display method and device, equipment, a storage medium and a product, and relates to the technical field of network equipment state monitoring. The method comprises the steps of obtaining equipment topology of network equipment of a resource pool from a digital server, obtaining equipment configuration data corresponding to the equipment topology from a first database, obtaining equipment performance data corresponding to the equipment topology from a second database, and displaying the equipment configuration data and the equipment performance data based on the equipment topology, the device topology is obtained according to the entity of the network device and the link layer discovery protocol information, the entity is obtained according to the device configuration data of the network device in the first database and the device performance data of the network device in the second database, and the link layer discovery protocol information is obtained from the first database. By adopting the method, the condition of the network equipment can be intuitively known and problems can be positioned.

Description

Technical Field

[0001] This application relates to the field of network device status monitoring technology, and in particular to a method, apparatus, computer device, computer-readable storage medium, and computer program product for displaying network device data. Background Technology

[0002] The resource pool contains multiple physical network devices, and the normal operation of these network devices ensures the stable operation of the system.

[0003] In traditional technologies, the inspection and status monitoring of network devices are carried out periodically by operations and maintenance personnel, who also need to log into the machines in the resource pool to check the situation. This makes it difficult to quickly understand the status of the devices and locate the problems, and it is difficult to carry out efficient troubleshooting of resource pool issues. Summary of the Invention

[0004] Therefore, it is necessary to provide a method, apparatus, computer device, computer-readable storage medium, and computer program product for displaying network device data, in response to the above-mentioned technical problems.

[0005] Firstly, this application provides a method for displaying network device data, including:

[0006] The device topology of the network devices in the resource pool is obtained from the digital server; the device topology is obtained based on the entity and link layer discovery protocol information of the network devices; the entity is obtained based on the device configuration data of the network devices in the first database and the device performance data of the network devices in the second database; the link layer discovery protocol information is obtained from the first database;

[0007] Obtain device configuration data corresponding to the device topology from the first database, and obtain device performance data corresponding to the device topology from the second database;

[0008] The device configuration data and device performance data are displayed based on the device topology.

[0009] In one embodiment, the digital server is configured to obtain the neighbor relationships of the network devices from the first database, determine the connection links between the entities of the network devices and the entities of the neighboring network devices of the network devices based on the neighbor relationships, and obtain the device topology based on the entities of the network devices and the connection links; wherein the neighbor relationships are obtained based on the link layer discovery protocol information.

[0010] In one embodiment, the first database is used to obtain the device identification information of the network device and the device identification information of the neighboring network devices according to the link layer discovery protocol information, match the device identification information with each device identifier in the first database to obtain a second matching result, determine the network device corresponding to the link layer discovery protocol information and the neighboring network devices of the network device in each network device of the resource pool according to the second matching result, and obtain the neighbor relationship according to the network device and the neighboring network devices of the network device.

[0011] In one embodiment, the device identification information includes one or more of a Management Internet Protocol (IIP) address, a Media Access Control (MAC) address, and a system name; the step of matching the device identification information with each device identifier in the first database to obtain a second matching result includes:

[0012] If the device identification information includes the management Internet Protocol address, then the management Internet Protocol address is matched with each device identifier in the first database to obtain a second matching result;

[0013] If the device identification information does not include the management Internet Protocol address but includes the media access control address, then the media access control address is matched with each device identifier in the first database to obtain a second matching result;

[0014] If the device identification information does not include the management Internet Protocol address and the media access control address but includes the system name, then the system name is matched with each device identifier in the first database to obtain a second matching result.

[0015] In one embodiment, the first database is used to obtain the port identifier of the network device and the port identifier of the neighboring network device according to the link layer discovery protocol information, determine the port name corresponding to the port identifier according to the port interface mapping table, match the port name with the device interface information of each network device in the resource pool to obtain a first matching result, determine the interface of the network device and the interface of the neighboring network device according to the first matching result, and obtain the neighbor relationship according to the interface of the network device and the interface of the neighboring network device; wherein, the port interface mapping table is used to indicate the mapping relationship between port identifiers and port names.

[0016] In one embodiment, the connection link includes a reachable link or an unreachable link; determining the connection link between an entity of the network device and the entities of its neighboring network devices based on the network device's neighbor relationships includes:

[0017] Based on the neighbor relationship, the interface operating status between the network device and the neighboring network devices is obtained;

[0018] If the interface is in an available operating state, then a reachable link is generated between the entity of the network device and the entity of the neighboring network device;

[0019] If the interface is in an unavailable state, an unreachable link is generated between the entity of the network device and the entity of the neighboring network device.

[0020] In one embodiment, the device performance data is read from the network devices in the resource pool according to a data acquisition script corresponding to the device attributes of the network devices; the device attributes are determined according to the device configuration data of the network devices.

[0021] Secondly, this application also provides a network device data display device, comprising:

[0022] The first acquisition module is used to acquire the device topology of network devices in the resource pool from the digital server; the device topology is obtained based on the entity and link layer discovery protocol information of the network devices; the entity is obtained based on the device configuration data of the network devices in the first database and the device performance data of the network devices in the second database; the link layer discovery protocol information is obtained from the first database.

[0023] The second acquisition module is used to acquire device configuration data corresponding to the device topology from the first database and device performance data corresponding to the device topology from the second database.

[0024] The display module is used to display the device configuration data and device performance data based on the device topology.

[0025] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0026] The device topology of the network devices in the resource pool is obtained from the digital server; the device topology is obtained based on the entity and link layer discovery protocol information of the network devices; the entity is obtained based on the device configuration data of the network devices in the first database and the device performance data of the network devices in the second database; the link layer discovery protocol information is obtained from the first database;

[0027] Obtain device configuration data corresponding to the device topology from the first database, and obtain device performance data corresponding to the device topology from the second database;

[0028] The device configuration data and device performance data are displayed based on the device topology.

[0029] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0030] The device topology of the network devices in the resource pool is obtained from the digital server; the device topology is obtained based on the entity and link layer discovery protocol information of the network devices; the entity is obtained based on the device configuration data of the network devices in the first database and the device performance data of the network devices in the second database; the link layer discovery protocol information is obtained from the first database;

[0031] Obtain device configuration data corresponding to the device topology from the first database, and obtain device performance data corresponding to the device topology from the second database;

[0032] The device configuration data and device performance data are displayed based on the device topology.

[0033] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0034] The device topology of the network devices in the resource pool is obtained from the digital server; the device topology is obtained based on the entity and link layer discovery protocol information of the network devices; the entity is obtained based on the device configuration data of the network devices in the first database and the device performance data of the network devices in the second database; the link layer discovery protocol information is obtained from the first database;

[0035] Obtain device configuration data corresponding to the device topology from the first database, and obtain device performance data corresponding to the device topology from the second database;

[0036] The device configuration data and device performance data are displayed based on the device topology.

[0037] The aforementioned network device data display method, apparatus, computer equipment, computer-readable storage medium, and computer program product obtain the device topology of network devices in the resource pool from a digital server, obtain the device configuration data corresponding to the device topology from a first database, obtain the device performance data corresponding to the device topology from a second database, and display the device configuration data and device performance data based on the device topology. The device topology is obtained based on the entity and link layer discovery protocol information of the network devices, the entity is obtained based on the device configuration data of the network devices in the first database and the device performance data of the network devices in the second database, and the link layer discovery protocol information is obtained from the first database. Compared to traditional methods, this solution can intuitively display the device configuration and performance data of network devices in the resource pool based on the device topology, without requiring users to log in to the devices to view their configuration and performance status information. This reduces tedious operations. Furthermore, based on the device topology, anomalies can be clearly identified, allowing for rapid identification of resource pool issues in the malfunctioning network devices or the connection links between them. This avoids aimless and time-consuming troubleshooting. It can also clearly identify all downstream devices and links affected by a particular faulty device, enabling rapid tracing of the root cause of the problem. Consequently, this significantly improves the reliability, availability, and maintainability of the resource pool network, providing strong data support and decision-making basis for the stable operation of the system. Attached Figure Description

[0038] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0039] Figure 1 This is an application environment diagram of a network device data display method in one embodiment;

[0040] Figure 2 This is a flowchart illustrating a method for displaying network device data in one embodiment;

[0041] Figure 3(a) is a flowchart illustrating a network device data display method in another embodiment;

[0042] Figure 3(b) is a schematic diagram of the data acquisition process in another embodiment;

[0043] Figure 3(c) is a schematic diagram of the LLDP information acquisition process in another embodiment;

[0044] Figure 4 This is a structural block diagram of a network device data display device in one embodiment;

[0045] Figure 5 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0047] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various objects, but these objects are not limited by these terms. These terms are only used to distinguish the first object from the second object. The term "comprising" and any variations thereof, as used in this application, are intended to cover non-exclusive inclusion. The term "multiple" as used in this application refers to two or more.

[0048] The network device data display method provided in this application embodiment can be applied to, for example, Figure 1 The application environment is illustrated. In this environment, the terminal communicates with the server via a network. The data storage system stores the data that the server needs to process. The data storage system can be integrated onto the server, or it can be located in the cloud or on other network servers. The terminal can be, but is not limited to, various personal computers, laptops, smartphones, tablets, drones, low-altitude aircraft, IoT devices, and portable wearable devices. The server can be a standalone physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server providing cloud computing services.

[0049] In one exemplary embodiment, such as Figure 2 As shown, a method for displaying network device data is provided, which can be applied to... Figure 1 In the terminal, the method may include the following steps:

[0050] It should be noted that the use cases of this embodiment can include the reproduction of the current physical environment of the resource pool, mainly including the reproduction of switches and routers in a multi-vendor situation and the implementation of network topology (including switches, routers and network devices from other vendors connected to them).

[0051] Step 201: Obtain the device topology of the network devices in the resource pool from the digital server.

[0052] The aforementioned device topology is obtained based on the entity and Link Layer Discovery Protocol (LLDP) information of the network devices; the aforementioned entities are obtained based on the device configuration data of the network devices in the first database and the device performance data of the network devices in the second database; the aforementioned LLDP information is obtained from the aforementioned first database. Network devices in the resource pool can refer to switches, routers, and other connected devices within the resource pool. LLDP is a data link layer protocol that enables devices in a network to discover each other, announce their status, and exchange information.

[0053] For example, the first database can be MySQL, and the second database can be ClickHouse. MySQL is a relational database that can be used to store structured data such as LLDP information and device configuration data; ClickHouse is a column-oriented open-source database that can be used to store time-series data such as device performance data.

[0054] Step 202: Obtain device configuration data corresponding to the device topology from the first database and device performance data corresponding to the device topology from the second database.

[0055] The device configuration data corresponding to the device topology can refer to the device configuration data corresponding to the network devices of the physical nodes in the device topology. Device configuration data may include parameters such as community name, SNMP (Simple Network Management Protocol) port, device model, and device operating system. SNMP is a standard protocol specifically designed for managing network nodes (servers, workstations, routers, switches, and hubs, etc.) in IP (Internet Protocol) networks; it is an application layer protocol.

[0056] Among them, the device performance data corresponding to the device topology can refer to the device performance data corresponding to the network devices corresponding to the physical nodes in the device topology; the device performance data can include data such as CPU (Central Processing Unit) utilization, disk utilization, memory utilization, packet loss rate, and battery status.

[0057] Step 203: Display the device configuration data and device performance data based on the above device topology.

[0058] For example, a device topology may include a topology diagram. In this embodiment, device configuration data and device performance data are added to the corresponding positions in the topology diagram, thereby displaying the device configuration data and device performance data based on the topology diagram.

[0059] In the aforementioned network device data display method, the device topology of the network devices in the resource pool is obtained from a digital server, the device configuration data corresponding to the device topology is obtained from a first database, and the device performance data corresponding to the device topology is obtained from a second database. Based on the device topology, the device configuration and performance data are displayed. The device topology is obtained from the entity and link layer discovery protocol information of the network devices; the entity is obtained from the device configuration data in the first database and the device performance data in the second database; and the link layer discovery protocol information is obtained from the first database. Compared to traditional methods, this solution can intuitively display the device configuration and performance data of the network devices in the resource pool based on the device topology, without requiring users to log in to the devices to view their configuration and performance status information, reducing tedious operations. Furthermore, based on the device topology, anomalies can be clearly identified, quickly pinpointing resource pool problems to the malfunctioning network devices or the connection links between them, avoiding aimless and time-consuming troubleshooting. It can also clearly identify all downstream devices and links affected by a faulty object, quickly tracing the root cause of the problem. This significantly improves the reliability, availability, and maintainability of the resource pool network, providing strong data support and decision-making basis for the stable operation of the system.

[0060] In an exemplary embodiment, the aforementioned digital server is configured to obtain the neighbor relationships of the network devices from the aforementioned first database, determine the connection links between the entities of the network devices and the entities of the neighboring network devices of the network devices based on the neighbor relationships of the network devices, and obtain the device topology based on the entities of the network devices and the connection links; wherein the neighbor relationships are obtained based on the aforementioned link layer discovery protocol information.

[0061] Among them, the neighbor relationship of network devices can be used to characterize the physical connection topology and topology status between network devices and their neighboring network devices. Based on this, the connection links between the entities of a network device and the entities of its neighboring network devices can be determined.

[0062] For example, a digital server is configured to create an entity of the network device based on device configuration data of the network device in a first database and device performance data of the network device in a second database, obtain the neighbor relationship of the network device from the first database, determine the connection link between the entity of the network device and the entities of the neighboring network devices of the network device based on the neighbor relationship of the network device, and generate a device topology based on the entity of the network device and the connection link.

[0063] In an exemplary embodiment, the first database is used to obtain the device identification information of the network device and the device identification information of the neighboring network devices based on the link layer discovery protocol information, match the device identification information with each device identifier in the first database to obtain a second matching result, determine the network device corresponding to the link layer discovery protocol information and the neighboring network devices of the network device in each network device of the resource pool based on the second matching result, and obtain the neighbor relationship based on the network device and the neighboring network devices of the network device.

[0064] The device identifier (Device ID) is used to uniquely identify network devices.

[0065] For example, network devices provide device names, while LLDP information provides device identification information such as SysName (SystemName), MAC (Media Access Control) address, and / or management IP address (Management Internet Protocol address). It is not possible to directly match the device name and device identification information to determine the unique network device corresponding to the LLDP information. Therefore, a first database is used to obtain the device identification information of the network device and the device identification information of neighboring network devices based on the LLDP information. The device identification information of the network device and the device identification information of the neighboring network devices are then matched with each device identifier in the first database. Through matching, the network device corresponding to the link layer discovery protocol information and the neighboring network devices of that network device are determined, and the neighbor relationships of the network device are obtained based on the network device and its neighboring network devices.

[0066] In an exemplary embodiment, the device identification information includes one or more of the following: Internet Protocol address, Media Access Control address, and system name; the process of matching the device identification information with the device identifiers in the first database to obtain a second matching result includes:

[0067] If the device identification information includes the management Internet Protocol (IP) address, then the IP address is matched with each device identifier in the first database to obtain a second matching result; if the device identification information does not include the IP address but includes the media access control (MAC) address, then the MAC address is matched with each device identifier in the first database to obtain a second matching result; if the device identification information does not include the IP address and the MAC address but includes the system name, then the system name is matched with each device identifier in the first database to obtain a second matching result.

[0068] For example, the LLDP information includes first device identification information and second device identification information; the first device identification information is used to indicate the device identification information of the aforementioned network device, and the second device identification information is used to indicate the device identification information of the neighboring network devices of the aforementioned network device. If the second device identification information included in the LLDP information includes a management IP address, MAC address, and SysName, then the management IP address is preferentially matched with each device identifier in the first database to determine the neighboring network devices of the aforementioned network device; if the second device identification information does not include a management IP address but includes a MAC address, then the MAC address is matched with each device identifier in the first database to determine the neighboring network devices of the aforementioned network device; if the second device identification information does not include a management IP address and MAC address but includes a SysName, then the SysName is matched with each device identifier in the first database using similarity matching or fuzzy matching to determine the neighboring network devices of the aforementioned network device.

[0069] In an exemplary embodiment, the first database is used to obtain the port identifier of the network device and the port identifier of the neighboring network device according to the link layer discovery protocol information, determine the port name corresponding to the port identifier according to the port interface mapping table, match the port name with the device interface information of each network device in the resource pool to obtain a first matching result, determine the interface of the network device and the interface of the neighboring network device according to the first matching result, and obtain the neighbor relationship according to the interface of the network device and the interface of the neighboring network device; wherein, the port interface mapping table is used to indicate the mapping relationship between port identifiers and port names.

[0070] A network device / neighboring network device can contain one or more ports. The interface of a network device refers to the port that connects to the interface of a neighboring network device; the interface of a neighboring network device refers to the port that connects to the interface of the network device.

[0071] For example, since the current scenario involves cross-vendor associations, the port name in the LLDP information (such as "GigabitEthernet1 / 0 / 1") may not be completely consistent with the ifName (Interface Name) and ifDescr (Interface Description) in SNMP. Some network devices may even display the port ID (such as the interface number) instead of the interface name in their LLDP. Based on this, the aforementioned first database is used to obtain the port identifier (port_id) of the network device and the port identifier of the neighboring network device from the LLDP information. It then determines the port name (port_name) corresponding to the port identifier of the network device and the port name corresponding to the port identifier of the neighboring network device according to the port interface mapping table. Finally, it matches the port name of the network device and the port name of the neighboring network device with the device interface information of each network device in the resource pool, thereby determining the interface of the network device and the interface of the neighboring network device. The device interface information may include ifIndex (Interface Index), ifDescr, ifName, and ifAlias ​​(Interface Alias).

[0072] In an exemplary embodiment, the aforementioned connection link includes a reachable link or an unreachable link; determining the connection link between an entity of the network device and the entities of its neighboring network devices based on the neighbor relationships of the network devices includes:

[0073] Based on the aforementioned neighbor relationships, the interface operating status between the aforementioned network device and the aforementioned neighboring network devices is obtained; if the interface operating status is available, a reachable link is generated between the entity of the aforementioned network device and the entity of the aforementioned neighboring network device; if the interface operating status is unavailable, an unreachable link is generated between the entity of the aforementioned network device and the entity of the aforementioned neighboring network device.

[0074] Among them, the interface operating status can characterize the connectivity of the connection link between the network device and its neighboring network devices; the reachable link can characterize that the connection link is connected, that is, the two ends of the connection link can communicate based on the connection link; the unreachable link can characterize that the connection link is not connected, that is, the two ends of the connection link cannot communicate based on the connection link.

[0075] For example, due to the presence of STP (Spanning Tree Protocol), ACL (Access Control List), or physical faults, the interface of a network device may be in a blocked state when the LLDP information shows that the connection link between the network device and its neighboring network devices is "available". Based on this, this embodiment uses SNMP to obtain the ifOperStatus (Interface Operational Status) between the network device and its neighboring network devices. When ifOperStatus is up (1), the interface operation status is determined to be available, that is, the interface is available, and the connection link established based on the interface is connected.

[0076] In an exemplary embodiment, the device performance data is obtained from the network devices in the resource pool according to the data acquisition script corresponding to the device attributes of the network devices; the device attributes are determined according to the device configuration data of the network devices.

[0077] Among them, the data acquisition script can refer to a script used to collect corresponding device performance data based on the device attributes of network devices; device attributes can refer to device type.

[0078] For example, a Python script is used to read / collect device configuration data (such as basic configuration information of switches and routers) from network devices in the resource pool. Based on the device configuration data, the device attributes of the network devices are determined, and a Telegraf collection script corresponding to the device attributes is generated. This Telegraf collection script is used as a data collection script, which uses SNMP to periodically read / collect device performance data from network devices in the resource pool. Device configuration data, device performance data, and link layer discovery protocol information are uniformly stored in Kafka. The data / information in Kafka is processed by topic to distinguish device configuration data, device performance data, and link layer discovery protocol information. The device configuration data and link layer discovery protocol information are stored in MySQL, and the device performance data is stored in ClickHouse. This embodiment facilitates later retrieval and processing by storing data / information in different databases according to different data / information topics (i.e., different data / information attributes).

[0079] In this embodiment, if it is determined that the device attributes of the network device match the device attributes of the special switch, then SNMP is used to read the switch module information corresponding to the special switch, and the corresponding Telegraf collection script is generated based on the switch module information.

[0080] Telegraf, in this context, refers to an open-source data acquisition proxy tool that uses Python scripts to generate its configuration file. It can be used to collect performance data from switches and routers, such as CPU usage, disk usage, memory usage, packet loss rate, and battery status. Kafka, on the other hand, can be a data hub that centrally receives and temporarily stores collected device configuration and performance data, achieving decoupling of data flow.

[0081] It should be noted that before generating Telegraf collection scripts, vendor compatibility work needs to be carried out first. For example, a "communication manual" (which specifies how to connect, how to collect / read, and how to parse the returned data) needs to be tailored for each type of network device that needs to be monitored. Through the adaptation work, Telegraf collection scripts can transform raw data with different formats collected from multi-vendor, heterogeneous resource pool physical environments into data with a unified format.

[0082] Currently, the normal operation of each network device in the resource pool is a crucial guarantee for system stability. In general use, the inspection and status monitoring of network devices typically rely on regular manual maintenance by operations and maintenance personnel. However, this method requires personnel to log into specific machines within the resource pool to troubleshoot, a cumbersome and time-consuming process. This hinders a quick and comprehensive understanding of the network device status and makes it difficult to rapidly locate fault points, thus creating significant difficulties and efficiency bottlenecks in troubleshooting resource pool issues.

[0083] In an exemplary embodiment, as shown in FIG3(a), a method for displaying network device data is also provided, which can be applied to Figure 1 In the terminal, the method may include the following steps:

[0084] Step 301: Use a Python script to read device data.

[0085] For example, a Python script can be used to read the device configuration data (such as device model, device operating system, etc.) of the network devices (such as switches, routers, and other physical network devices) in the resource pool.

[0086] Step 302: Use a Python script to generate a Telegraf collection script.

[0087] For example, based on the network device's device configuration data, the network device's device attributes are determined, and a Telegraf collection script corresponding to the network device's device attributes is generated. In this embodiment, if it is determined that the network device's device attributes match those of a special switch, i.e., the network device is determined to be a special switch, then SNMP is used to read the switch module information corresponding to the special switch, and a corresponding Telegraf collection script is generated based on this switch module information.

[0088] Step 303: Use SNMP via Telegraf collection script to read device performance data of network devices in the resource pool.

[0089] For example, device performance data includes CPU utilization, disk utilization, memory utilization, packet loss rate, and / or battery status.

[0090] Step 304: Using the Telegraf collection script, store the device configuration data (configuration_data) and LLDP information (link_data) of the network devices in the resource pool into MySQL.

[0091] Step 305: Use the Telegraf collection script to store the device performance data (performance_data) of the network devices in the resource pool into ClickHouse.

[0092] Among them, the device performance data of the network devices in the resource pool is a type of time-series data.

[0093] Steps 301 to 305 describe a data acquisition process, as shown in Figure 3(b).

[0094] Step 306: Query LLDP information from MySQL via the digital server.

[0095] Step 307: Return the neighbor relationships of network devices to the digital server via MySQL.

[0096] Specifically, MySQL is used to obtain the device identification information of network devices and neighboring network devices based on LLDP information. If the device identification information includes the management Internet Protocol (IP) address, the IIP address is matched with each device identifier in MySQL to obtain a second matching result. If the device identification information does not include the IIP address but includes the Media Access Control (MAC) address, the MAC address is matched with each device identifier in MySQL to obtain a second matching result. If the device identification information does not include the aforementioned IIP address and MAC address but includes the system name, the system name is matched with each device identifier in MySQL to obtain a second matching result. Based on the second matching result, the network device corresponding to the LLDP information and the neighboring network devices of the network device are determined among the network devices in the resource pool. Based on the network device and the neighboring network devices of the network device, the neighbor relationship of the network device is obtained.

[0097] Among them, MySQL is also used to obtain the port identifiers of network devices and neighboring network devices based on LLDP information, determine the port name corresponding to the port identifier based on the port interface mapping table, match the port name with the device interface information of each network device in the resource pool to obtain the first matching result, determine the interface of the network device and the interface of the neighboring network device based on the first matching result, and obtain the neighbor relationship based on the interface of the network device and the interface of the neighboring network device; wherein, the port interface mapping table is used to indicate the mapping relationship between port identifiers and port names.

[0098] The digital server is used to obtain the entity of the network device based on the device configuration data of the network device in MySQL and the device performance data of the network device in ClickHouse.

[0099] The digital server is also used to obtain the interface operating status between the network device and its neighboring network devices based on the neighbor relationship; if the interface operating status is available, it generates reachable links between the entities of the network device and the entities of its neighboring network devices; if the interface operating status is unavailable, it generates unreachable links between the entities of the network device and the entities of its neighboring network devices; it determines the connection links between the entities of the network device and the entities of its neighboring network devices based on the neighbor relationship of the network devices; and it generates the device topology based on the entities of the network devices and the reachable and / or unreachable links.

[0100] The interface operating status can characterize the connectivity of the connection links between a network device and its neighboring network devices. Device topology can refer to a topology diagram.

[0101] Steps 306 to 307 describe an LLDP information acquisition process, as shown in Figure 3(c).

[0102] Step 308: The terminal obtains the device topology of the network devices in the resource pool from the digital server through the visualization platform.

[0103] Step 309: The terminal obtains device performance data corresponding to the device topology from ClickHouse through the visualization platform.

[0104] Step 310: The terminal obtains the device configuration data corresponding to the device topology from MySQL through the visualization platform.

[0105] In this embodiment, by automatically collecting device configuration information and performance data of network devices such as switches and routers in the resource pool, the cumbersome operation of logging into devices to view data is reduced, and a prerequisite for subsequent customized development is provided. Moreover, based on LLDP information, the neighbor relationships of network devices are obtained, and the connection links are determined according to the neighbor relationships to generate device topology. This collects the physical connection topology relationships and topology status between devices, and completes real-time updated automated topology, ensuring the integrity and timeliness of topology data. As a result, device performance data and device configuration data can be displayed based on device topology, realizing device data visualization, facilitating the synchronous observation of topology alarms and various attributes, and helping to quickly locate device and link anomalies.

[0106] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0107] Based on the same inventive concept, this application also provides a network device data display apparatus for implementing the network device data display method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more network device data display apparatus embodiments provided below can be found in the limitations of the network device data display method described above, and will not be repeated here.

[0108] In one exemplary embodiment, such as Figure 4 As shown, a network device data display device is provided, including: a first acquisition module 401, a second acquisition module 402, and a display module 403, wherein:

[0109] The first acquisition module 401 is used to acquire the device topology of the network devices in the resource pool from the digital server; the device topology is obtained based on the entity and link layer discovery protocol information of the network devices; the entity is obtained based on the device configuration data of the network devices in the first database and the device performance data of the network devices in the second database; the link layer discovery protocol information is obtained from the first database.

[0110] The second acquisition module 402 is used to acquire device configuration data corresponding to the device topology from the first database and device performance data corresponding to the device topology from the second database.

[0111] The display module 403 is used to display the device configuration data and device performance data based on the device topology.

[0112] In an exemplary embodiment, the aforementioned digital server is configured to obtain the neighbor relationships of the network devices from the aforementioned first database, determine the connection links between the entities of the network devices and the entities of the neighboring network devices of the network devices based on the neighbor relationships of the network devices, and obtain the device topology based on the entities of the network devices and the connection links; wherein the neighbor relationships are obtained based on the aforementioned link layer discovery protocol information.

[0113] In an exemplary embodiment, the first database is used to obtain the device identification information of the network device and the device identification information of the neighboring network devices based on the link layer discovery protocol information, match the device identification information with each device identifier in the first database to obtain a second matching result, determine the network device corresponding to the link layer discovery protocol information and the neighboring network devices of the network device in each network device of the resource pool based on the second matching result, and obtain the neighbor relationship based on the network device and the neighboring network devices of the network device.

[0114] In an exemplary embodiment, the device identification information includes one or more of a Management Internet Protocol (WLAN) address, a Media Access Control (MAC) address, and a system name. The first database is further configured to: if the device identification information includes the WLAN address, match the WLAN address with each device identifier in the first database to obtain a second matching result; if the device identification information does not include the WLAN address but includes the MAC address, match the MAC address with each device identifier in the first database to obtain a second matching result; if the device identification information does not include the WLAN address and the MAC address but includes the system name, match the system name with each device identifier in the first database to obtain a second matching result.

[0115] In an exemplary embodiment, the first database is further configured to obtain the port identifier of the network device and the port identifier of the neighboring network device based on the link layer discovery protocol information, determine the port name corresponding to the port identifier based on the port interface mapping table, match the port name with the device interface information of each network device in the resource pool to obtain a first matching result, determine the interface of the network device and the interface of the neighboring network device based on the first matching result, and obtain the neighbor relationship based on the interface of the network device and the interface of the neighboring network device; wherein, the port interface mapping table is used to indicate the mapping relationship between port identifiers and port names.

[0116] In an exemplary embodiment, the aforementioned connection link includes a reachable link or an unreachable link. The aforementioned digital server is further configured to obtain the interface operating status between the aforementioned network device and the aforementioned neighboring network devices based on the aforementioned neighbor relationship; if the interface operating status is available, a reachable link is generated between the entity of the aforementioned network device and the entity of the aforementioned neighboring network device; if the interface operating status is unavailable, an unreachable link is generated between the entity of the aforementioned network device and the entity of the aforementioned neighboring network device.

[0117] In an exemplary embodiment, the device performance data is obtained from the network devices in the resource pool according to the data acquisition script corresponding to the device attributes of the network devices; the device attributes are determined according to the device configuration data of the network devices.

[0118] Each module in the aforementioned network device data display device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of the computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0119] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 5 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a method for displaying data from a network device. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen, which can be used to display the device topology of the network devices in the resource pool, such as displaying a topology diagram of the network devices. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs or touchpads set on the computer device casing, or external keyboards, touchpads or mice, etc.

[0120] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0121] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the network device data display method described above.

[0122] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the above-described method for displaying network device data.

[0123] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the network device data display method described above.

[0124] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0125] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0126] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A network device data presentation method, characterized by, The method comprises: obtaining a device topology of network devices of a resource pool from a digital server; the device topology is obtained according to entity and link layer discovery protocol information of the network devices; the entity is obtained according to device configuration data of the network devices in a first database and device performance data of the network devices in a second database; the link layer discovery protocol information is obtained from the first database; obtaining device configuration data corresponding to the device topology from the first database and obtaining device performance data corresponding to the device topology from the second database; displaying the device configuration data and device performance data based on the device topology.

2. The method of claim 1, wherein, The digital server is configured to obtain a neighbor relationship of the network devices from the first database, determine a connection link between the entity of the network device and the entity of a neighbor network device of the network device according to the neighbor relationship of the network devices, and obtain the device topology according to the entity of the network device and the connection link; wherein the neighbor relationship is obtained according to the link layer discovery protocol information.

3. The method of claim 2, wherein, The first database is configured to obtain device identification information of the network devices and device identification information of the neighbor network devices according to the link layer discovery protocol information, match the device identification information with each device identifier in the first database to obtain a second matching result, determine the network device and the neighbor network device of the network device corresponding to the link layer discovery protocol information among each network device of the resource pool according to the second matching result, and obtain the neighbor relationship according to the network device and the neighbor network device of the network device.

4. The method of claim 3, wherein, The device identification information comprises one or more of a management Internet Protocol address, a media access control address and a system name; and the matching of the device identification information with each device identifier in the first database to obtain the second matching result comprises: if the device identification information comprises the management Internet Protocol address, matching the management Internet Protocol address with each device identifier in the first database to obtain the second matching result; if the device identification information does not comprise the management Internet Protocol address but comprises the media access control address, matching the media access control address with each device identifier in the first database to obtain the second matching result; if the device identification information does not comprise the management Internet Protocol address and the media access control address but comprises the system name, matching the system name with each device identifier in the first database to obtain the second matching result.

5. The method of claim 2, wherein, The first database is configured for obtaining a port identifier of the network device and a port identifier of the neighbor network device according to the link layer discovery protocol information, determining a port name corresponding to the port identifier according to a port interface mapping table, matching the port name with device interface information of each network device of the resource pool to obtain a first matching result, determining an interface of the network device and an interface of the neighbor network device according to the first matching result, and obtaining the neighbor relationship according to the interface of the network device and the interface of the neighbor network device.

6. The method of claim 2, wherein, The connection link includes a reachable link or an unreachable link. According to the neighbor relationship, an interface running state between the network device and the neighbor network device is obtained. If the interface running state is available, a reachable link between the entity of the network device and the entity of the neighbor network device is generated. If the interface running state is unavailable, an unreachable link between the entity of the network device and the entity of the neighbor network device is generated.

7. The method according to any one of claims 1 to 6, characterized in that, The device performance data is obtained by reading from the network device of the resource pool according to a data collection script corresponding to a device attribute of the network device.

8. A network device data presentation apparatus, comprising: The device attribute is determined according to device configuration data of the network device. The apparatus includes: A first obtaining module is configured for obtaining a device topology of network devices of a resource pool from a digital server. The device topology is obtained according to an entity and link layer discovery protocol information of the network device. The entity is obtained according to device configuration data of the network device in a first database and device performance data of the network device in a second database. The link layer discovery protocol information is obtained from the first database. A second obtaining module is configured for obtaining device configuration data corresponding to the device topology from the first database and obtaining device performance data corresponding to the device topology from the second database. 9.A computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer device is configured to perform the method according to any one of claims 1-8 when the computer program is executed by the processor. A display module is configured for displaying the device configuration data and the device performance data based on the device topology.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that, The processor executes the computer program to implement the steps of the method in any one of claims 1 to 7.

11. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the method in any one of claims 1 to 7. The computer program is executed by the processor to implement the steps of the method in any one of claims 1 to 7.

Images