Connection checking method, electronic equipment and computer readable storage medium

Abstract

The invention discloses a connection checking method, electronic equipment and a computer readable storage medium, and belongs to the technical field of communication. The connection checking method comprises the following steps: generating a management interface of a target server according to server configuration information of the target server; sending link layer discovery protocol LLDP opening information to the target server through a management interface of the target server; and determining a connection check result between the target server and the network equipment according to the port LLDP neighbor information of the network equipment. Through the mode, the requirements on equipment hardware configuration and a network environment can be reduced, and the checking efficiency of the connection between the server and the network equipment is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a connection checking method, an electronic device, and a computer-readable storage medium. Background Technology

[0002] With the development and popularization of 5G technology, the demand for data is increasing dramatically, and related industries are building data centers on a large scale. New data centers typically contain a large number of hardware devices, primarily servers. These servers are very large in scale, ranging from hundreds to thousands. The physical connections between servers and other network devices, especially switches, resemble a complex, intertwined network, making them highly susceptible to connection errors and omissions. Any connection error can lead to anomalies in later service deployments, forcing technicians to spend a significant amount of time and effort troubleshooting each issue.

[0003] In related technologies, a preboot execute environment (PXE) can be used to install an image on the server and load the corresponding scripts to enable the Link Layer Discovery Protocol (LLDP) function of the network interface card (NIC) to obtain the actual connection relationships. However, this method depends on whether the server's NIC has PXE enabled, the PXE network connectivity conditions, and the server's network bandwidth and computing performance. It has high requirements for device hardware configuration and network environment, and the check process requires loading a temporary file system, resulting in long execution time and low efficiency in connection checking. Summary of the Invention

[0004] This application provides a connection checking method, electronic device, and computer-readable storage medium to at least solve the problems of low efficiency and high requirements for device hardware configuration and network environment in connection checking between large-scale servers and network devices in data centers and resource pools.

[0005] In a first aspect, embodiments of this application provide a connection check method, comprising: generating a management interface for the target server based on server configuration information of the target server; sending Link Layer Discovery Protocol (LLDP) enable information to the target server through the management interface of the target server; and determining the connection check result between the target server and the network device based on the port LLDP neighbor information of the network device.

[0006] Secondly, embodiments of this application provide a connection inspection device, including: an LLDP function enabling module, used to generate a management interface for the target server based on the server configuration information of the target server; and to send LLDP (Link Layer Discovery Protocol) enabling information to the target server through the management interface of the target server; and an information processing module, used to determine the connection inspection result between the target server and the network device based on the port LLDP neighbor information of the network device.

[0007] Thirdly, embodiments of this application provide an electronic device, which includes a processor and a memory. The memory stores programs or instructions that can run on the processor, and when the programs or instructions are executed by the processor, they implement the steps of the method described in the first aspect above.

[0008] Fourthly, embodiments of this application provide a computer-readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0009] Fifthly, embodiments of this application provide a computer program product, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions, which, when executed by a computer, cause the computer to perform the steps of the method described in the first aspect above.

[0010] In this embodiment, a management interface for the target server is generated based on the server configuration information of the target server. Through this management interface, Link Layer Discovery Protocol (LLDP) enable information is sent to the target server. Based on the LLDP neighbor information of the network device's ports, the connection check result between the target server and the network device is determined. This method of generating a management interface based on the target server's configuration information, which can be implemented using an out-of-band management protocol such as Redfish, and controlling the LLDP function enable on the target server, while determining the connection check result based on the LLDP neighbor information of the network device's ports, reduces the requirements for device hardware configuration and network environment, and improves the efficiency of connection check between the server and network device.

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

[0012] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0013] Figure 1 This illustration shows an application scenario diagram of the connection detection method provided in the embodiments of this application;

[0014] Figure 2 This paper illustrates a flowchart of a connection detection method provided in an embodiment of this application.

[0015] Figure 3 A schematic diagram of the wiring detection device provided in an embodiment of this application is shown;

[0016] Figure 4 It shows Figure 3 A schematic diagram of the LLDP function enabling module in the middle;

[0017] Figure 5 It shows Figure 3 A schematic diagram of the structure of the information acquisition module;

[0018] Figure 6 It shows Figure 3 A schematic diagram of the information processing module in the middle;

[0019] Figure 7 It shows Figure 3 Schematic diagram of the middle connection detection device;

[0020] Figure 8 This paper illustrates another flowchart of the interconnection detection method provided in an embodiment of this application;

[0021] Figure 9 A schematic diagram of the structure of an electronic device provided in an embodiment of this application is shown. Detailed Implementation

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

[0023] Currently, data centers and resource pools typically contain a large number of hardware devices, and misconnections and omissions are common between servers and other hardware devices, especially switches. Traditional connection checks rely on manual methods such as checking cable labels or repeatedly plugging and unplugging fiber optic cables to verify the correctness of the connections. This method is inefficient, inflexible, and prone to errors. With technological advancements, new connection checking methods have emerged. This method uses PXE to install a server image and load the corresponding scripts to enable the LLDP function of the network interface card, thereby obtaining the actual connection relationships. Specifically:

[0024] (1) Perform batch PXE boot on the target server;

[0025] (2) The local device enables the Dynamic Host Configuration Protocol (DHCP) service, discovers the target server through DHCP broadcast messages, assigns a temporary IP address to the target server, and simultaneously distributes a batch of temporary operating system (OS) kernels and temporary OS initrd file systems containing the Link Layer Discovery Protocol Daemon (lldpad) component to the target server.

[0026] (3) Each target server runs the LLDP startup program to collect the actual connection information of the target server;

[0027] (4) Based on the temporary Internet Protocol (IP) address assigned by the target server, the local device obtains the actual connection information from the target server;

[0028] (5) Compare the designed connection information with the actual connection information to determine the correctness of the connection relationship.

[0029] However, the above method of using PXE to install the server image and load the corresponding script to enable the LLDP function of the network card depends on whether the server's network card has PXE enabled, the PXE network connectivity conditions, and the network bandwidth and computing performance of the server providing DHCP service. It has high requirements for device hardware configuration and network environment. In addition, the connection check process requires loading a temporary OS initrd file system, which takes a long time and has low connection check efficiency.

[0030] To address the aforementioned issues in the connection check process, this application provides a connection check method. This method uses an out-of-band management interface to control the LLDP function of the target server and determines the connection check result between the target server and the network device based on the LLDP neighbor information of the network device's port. This reduces the requirements for device hardware configuration and network environment, and improves the efficiency of connection check between the server and the network device.

[0031] Figure 1The illustration shows an application scenario diagram of the connection detection method provided in this application embodiment. As shown in the figure, the execution subject of the connection detection method can be a terminal device or a server. The terminal device can be a device such as a personal computer, or a mobile terminal device such as a mobile phone or tablet computer. The terminal device can be a user-used terminal device. The server can be an independent server or a server cluster composed of multiple servers. Moreover, the server can be a backend server for a certain business, or a backend server for a certain platform or application (e.g., a network management system, network monitoring tool, network diagnostic tool, etc.). In this application embodiment, a personal computer 110 is used as an example for the execution subject. The personal computer 110 can be temporarily connected to the network environment 120 through a network cable to ensure that the personal computer 110 can access all leaf switches 121 and servers 122, in preparation for connection checks. Figure 2 A schematic flowchart of a wiring detection method provided in an embodiment of this application is shown. As shown in the figure, the wiring detection method 200 may include the following steps:

[0032] S201: Generate the management interface of the target server based on the server configuration information of the target server.

[0033] The server configuration information includes the target server's management IP address, username, password, and network interface card slot number. The target server's management interface can be implemented through out-of-band management protocols, such as the Intelligent Platform Management Interface (IPMI) or the Redfish interface. This management interface allows administrators to remotely manage the target server over the network.

[0034] In practice, you can log in to the target server using a username and password. After logging in, you can use relevant commands to obtain server configuration information such as the management IP address and network card slot number of the target server. Based on the obtained server configuration information, you can generate management interfaces for the target server, such as power-on status query interface, LLDP service status query interface, and network card LLDP service enable interface.

[0035] S202: Send Link Layer Discovery Protocol (LLDP) activation information to the target server through the management interface of the target server.

[0036] In practice, LLDP enable information can be sent to the target server through the management interface of the generated target server, so that the target server enables the LLDP function and sends its device status information to neighboring devices.

[0037] S203: Determine the connection check result between the target server and the network device based on the port LLDP neighbor information of the network device.

[0038] The network device can be a leaf switch 121, or a router, wireless access point, or other devices that are pre-planned to connect to the target server.

[0039] In practical implementation, the port LLDP neighbor information of network devices includes the port and device identification information of neighboring devices. By parsing the port LLDP neighbor information of network devices, the connection check result between the target server and the network device can be determined. For example, by parsing the port LLDP neighbor information of network devices, the device identification information of the target server can be determined. By comparing the device identification information of the target server with the actual device identification information of the target device, the connection check result between the target server and the network device can be determined.

[0040] Through the above steps, since a management interface is generated based on the server configuration information of the target server, this management interface can be implemented through an out-of-band management protocol, such as Redfish. This management interface controls the LLDP function of the target server and determines the connection check result between the target server and the network device based on the port LLDP neighbor information of the network device. Therefore, this embodiment only needs to ensure that the out-of-band network connectivity is normal, without relying on the in-band network for communication. This reduces the requirements for device hardware configuration and network environment. At the same time, when using this embodiment to perform large-scale server connection checks, the impact of network bandwidth is very small. Especially when dealing with large-scale server clusters, its check efficiency increases significantly with the expansion of the cluster size.

[0041] Taking a single server connection check as an example, the connection check method using the installation image may take several minutes or even more than ten minutes. However, the embodiment of this application enables the LLDP function of the server network card in out-of-band and then performs the connection check, which only takes a few seconds, significantly improving efficiency.

[0042] In one possible implementation, in S202 above, sending Link Layer Discovery Protocol (LLDP) activation information to the target server through the target server's management interface includes:

[0043] The system queries the LLDP service status of the target server through its management interface. If the system determines that the LLDP service status of the target server is off, it sends LLDP enable information to the target server.

[0044] In this embodiment of the application, the LLDP server status of the target server is queried through the management interface of the target server, such as the Redfish interface. If it is determined that the LLDP service status of the target server is enabled, subsequent connection checks are performed; if it is determined that the LLDP service status of the target server is disabled, LLDP link layer discovery protocol enabled information is sent to the target server.

[0045] Prior to querying the LLDP service status of the target server, the process also includes:

[0046] Query the power status of the target server; if the target server is determined to be in a power-off state, power on the target server; if the target server is determined to be in a power-on state, query the LLDP service status of the target server.

[0047] By querying the target server's power status and LLDP service status, it can be ensured that the target server can receive and respond to LLDP enable information normally, thus improving the accuracy of network discovery and management.

[0048] In one possible implementation, in S202 above, sending Link Layer Discovery Protocol (LLDP) activation information to the target server through the target server's management interface includes:

[0049] A communication connection is established between the target server's management interface and the target server's baseboard management controller; the LLDP enable information is sent to the target server's baseboard management controller, and the baseboard management controller communicates with the target server's network interface card (NIC) module so that the NIC module sends the target server's device status information to adjacent devices.

[0050] In this embodiment, a communication connection can be established with the Baseboard Management Controller (BMC) of the target server through the target server's management interface, such as Redfish or IPMI. The BMC is used for out-of-band management of the target server, allowing remote operation and monitoring. LLDP enable information is sent to the target server's BMC, and the BMC communicates with the target server's network interface card (NIC) module, enabling the NIC module to send the target server's device status information to adjacent devices. Specifically, the target server's BMC can enable the LLDP function in the following ways:

[0051] After receiving the LLDP enable information, the target server's BMC calls the BMC's network interface card (NIC) module. The NIC module communicates with the corresponding NIC through an out-of-band channel, such as the I2C channel. After receiving the information, the NIC extracts the NIC status information from the local Management Information Base (MIB) and encapsulates the NIC status information into an LLDP frame. The LLDP frame is then sent out at certain time intervals to notify neighboring devices.

[0052] In one possible implementation, in S203 above, the connection check result between the target server and the network device is determined based on the port LLDP neighbor information of the network device, including:

[0053] Based on the network device configuration information of the network device, obtain the port LLDP neighbor information of the network device; by parsing the port LLDP neighbor information of the network device, obtain the MAC address of the target server; based on the consistency between the MAC address of the target server and the actual MAC address of the target server, determine the connection check result between the target server and the network device.

[0054] The network device configuration information includes login information such as the network device's username, password, and IP address.

[0055] In this embodiment, the actual MAC address of the target server is obtained, denoted as MAC_A. A communication connection is established with the network device using login information such as username, password, and IP address. Corresponding commands are executed to collect the network device's port LLDP neighbor information. The target server's MAC address, denoted as MAC_B, is obtained by parsing the network device's port LLDP neighbor information. Based on the consistency between MAC_A and MAC_B, the connection check result between the target server and the network device is determined.

[0056] The aforementioned determination of the connection check result between the target server and the network device based on the consistency between the target server's MAC address and the target server's actual MAC address includes:

[0057] If the MAC address of the target server matches the actual MAC address of the target server, the connection check result between the target server and the network device is determined to be a correct connection.

[0058] If the MAC address of the target server is inconsistent with the actual MAC address of the target server, the connection check result between the target server and the network device is determined to be an incorrect connection.

[0059] In one exemplary embodiment, the string values ​​of MAC_A and MAC_B are compared. If the two strings are exactly the same, it can be determined that MAC_A and MAC_B are consistent, and the connection between the target server and the network device is correct. If the two strings are different, it can be determined that MAC_A and MAC_B are inconsistent, and the connection between the target server and the network device is incorrect.

[0060] In one possible implementation, after determining that the connection check result between the target server and the network device is a connection error, the method further includes:

[0061] Based on the server configuration information and the network device configuration information, determine the connection check failure type that matches the connection relationship error;

[0062] Based on the connection failure type, generate at least one abnormal connection rectification suggestion.

[0063] Among the connection check failure types are server configuration information errors, failure to obtain LLDP neighbor information for network devices, and abnormal connection between the target server and the network device.

[0064] In this embodiment, after determining that the connection relationship between the target server and the network device is incorrect, the connection check failure type matching the connection relationship error can be analyzed based on the obtained server configuration information and network device configuration information. Then, based on the connection check failure type, at least one abnormal connection rectification suggestion can be generated. For example, when the connection check failure type is an incorrect server configuration information, the generated abnormal connection rectification suggestion can be: Please check the server configuration information of the target server, such as whether the network card port actually exists. If the network card port does not exist, please verify and add the correct port configuration. As another example, when the connection check failure type is the failure to obtain the port LLDP neighbor information of the network device, the generated abnormal connection rectification suggestion can be: (1) Please check whether the network connectivity and power-on status of the network device are normal; (2) Please check whether the IP address, username and password of the network device are correct. For example, when the connection check failure type is abnormal connection between the target server and the network device, the generated abnormal connection rectification suggestions can be: (1) Please check whether there is an actual physical connection between the port of the target server and the network device, and whether the connection is misaligned; (2) Please check whether the port of the network device is in the closed state. If the port is in the closed state, please set it to the open state.

[0065] In one possible implementation, after determining the connection check result of the target server in S203 above, the method further includes:

[0066] An inspection report is generated based on the connection check results of the target server. The inspection report includes at least one of the following: the device pass rate of the target server and the connection entry pass rate of the target server.

[0067] In this embodiment, an inspection report is generated based on the connection check results of the target server. This report includes the device pass rate and the connection entry pass rate of the target server. The target server typically has multiple ports, each connected to a different network device, such as a leaf switch or router. That is, the target server has multiple connection entries. When the connection relationship between the target server's ports and the corresponding network devices is correct, the corresponding connection pass the connection check. When all ports of the target server have correct connection relationships with their corresponding network devices, the connection check of the target server passes.

[0068] In one possible implementation, the inspection report also includes rectification suggestions for abnormal connections to the target server; after generating the inspection report based on the connection inspection results of the target server, it also includes:

[0069] If the inspection report includes suggestions for rectifying abnormal connections of the target server, the connection relationships of the target server shall be investigated and rectified according to the suggestions for rectifying abnormal connections, and the connection of the target server shall be checked again until the inspection report no longer includes suggestions for rectifying abnormal connections of the target server.

[0070] In one possible implementation, before generating the management interface of the target server based on the server configuration information of the target server in step S201 above, the method further includes:

[0071] Obtain pre-configured planning connection information; obtain the server configuration information of the target server by parsing the planning connection information.

[0072] The planning connection information includes equipment information and connection information. The equipment information includes server login information and network device login information, and the connection information is the connection port information between the server and the network device.

[0073] In this embodiment, the user can pre-configure planned connection information and obtain the server configuration information of the target server by parsing the planned connection information. Then, connection detection is performed on the target server to determine whether the actual connection information between the target server and the network device matches the planned connection information.

[0074] The connection detection method provided in this application embodiment can be implemented by a connection detection device, such as... Figure 3As shown, this application embodiment provides a wiring detection device 300, which includes:

[0075] The LLDP function enabling module 310 is used to generate a management interface for the target server based on the server configuration information of the target server; and to send LLDP (Link Layer Discovery Protocol) enabling information to the target server through the management interface of the target server.

[0076] The information processing module 320 is used to determine the connection check result between the target server and the network device based on the port LLDP neighbor information of the network device.

[0077] In one possible implementation, such as Figure 4 As shown, the LLDP function enabling module 310 includes:

[0078] The information preprocessing unit 311 is used to obtain pre-configured planning connection information, such as device information and connection information filled in by the user; to obtain the server configuration information of the target server by parsing the planning connection information, such as the management IP address, username, password and network card slot number of the target server; and to record the parsed server configuration information into a pre-created device configuration information database.

[0079] Server control unit 312 is used to generate corresponding Redfish interfaces based on server configuration information in the device configuration information database, such as power-on status query interface, LLDP service status query interface, network card LLDP service enable interface, etc., and call the first HTTPS service unit 313 to communicate with the baseboard management controller (BMC) of the target server to control the power status of the target server, query the LLDP service status of the target server, and enable the LLDP service status of the server.

[0080] Redfish is a management standard based on HTTPS services that uses RESTful interfaces to manage devices. When processing multiple target servers in batches, this module can improve the efficiency of connection checks by enabling multi-threading.

[0081] The first HTTPS service unit 313 is used to communicate with the BMC of the target server.

[0082] In one possible implementation, the connection detection device 300 further includes:

[0083] The information acquisition module 330 is used to obtain the actual MAC address of the target server and, based on the network device configuration information, to obtain the port LLDP neighbor information of the network device.

[0084] Among them, such as Figure 5 As shown, the information acquisition module 330 includes:

[0085] The first information acquisition unit 331 is used to acquire server configuration information from the device configuration information database and network device configuration information of the network device.

[0086] Server MAC collection unit 332 is used to generate a corresponding management interface based on server configuration information and call the first HTTPS service unit 334 to communicate with the BMC of the target server to obtain the actual MAC address of the specific network port of the target server and record it in the server network port MAC database.

[0087] The LLDP neighbor information collection unit 333 is used to communicate with the BMC of the target server according to the network device configuration information and by calling the first HTTPS service unit 334, to execute corresponding commands to collect the port LLDP neighbor information of the network device and record it in the LLDP information database.

[0088] The second HTTPS service unit 334 is used to communicate with the BMC of the target server.

[0089] Among them, such as Figure 6 As shown, the information processing module 320 includes:

[0090] The second information acquisition unit 321 is used to obtain the actual MAC address of the target server from the server network port MAC database, denoted as MAC_A; and to obtain the port LLDP neighbor information of the network device from the LLDP information database.

[0091] The connection comparison unit 322 is used to parse the MAC address of the peer server's network port that is actually connected to the port of the network device from the port LLDP neighbor information, denoted as MAC_B. If MAC_A and MAC_B are consistent, the connection check result between the target server and the network device is determined to be a correct connection; if MAC_A and MAC_B are inconsistent, the connection check result between the target server and the network device is determined to be an incorrect connection. Based on the connection check failure type that matches the connection check error, at least one abnormal connection rectification suggestion is generated. The connection check result and the connection check failure type are recorded in the connection relationship status database.

[0092] To improve speed, the information processing module 320 also supports multi-threaded operation.

[0093] In one possible implementation, the connection detection device 300 further includes:

[0094] The report output module 340 is used to generate an inspection report based on the connection inspection results of the target server.

[0095] Among them, such as Figure 7 As shown, the report output module 340 includes:

[0096] The third information acquisition unit 341 is used to obtain the connection check results of the target server from the connection relationship status database, and determine the device pass rate, connection item pass rate, and abnormal connection rectification suggestions of the target server based on the connection check results of the target server.

[0097] The report output unit 342 is used to generate an inspection report based on the connection inspection results of the target server.

[0098] like Figure 8 As shown, the wiring detection method of the wiring detection device 300 described above includes the following steps:

[0099] Step 801: Enable LLDP function and start module 310;

[0100] Specifically, firstly, the information preprocessing unit 311 of the LLDP function enabling module 310 is activated to obtain the pre-configured planning connection information; by parsing the planning connection information, the server configuration information of the target server is obtained, such as the management IP address, username, password and network card slot number of the target server; the parsed server configuration information is recorded in the device configuration information database; then, the server control unit 312 is activated to generate the corresponding Redfish interface according to the server information in the database, and the first HTTPS service unit 313 is called to communicate with the baseboard management controller (BMC) of the target server to control the power status of the target server, query the LLDP service status of the target server, and enable the LLDP service status of the server;

[0101] Before starting the LLDP function enabling module 310, resource data initialization is performed, and the out-of-band link connectivity status of the target server is fully detected.

[0102] Step 802: Query the LLDP service status of the target server. If the LLDP service status of the target server is enabled, proceed to step 804. If the LLDP service status of the target server is disabled, proceed to step 803.

[0103] Step 803: Enable LLDP functionality on the target server via the Redfish interface;

[0104] Step 804: Start the information collection module 330;

[0105] Specifically, firstly, the first information acquisition unit 331 in the information acquisition module 330 is activated to obtain server configuration information and network device configuration information from the device configuration information database; then, the server MAC collection unit 332 is activated to generate a corresponding management interface based on the server configuration information, and calls the second HTTPS service unit 334 to communicate with the BMC of the target server to obtain the actual MAC address of the specific network port of the target server and record it in the server network port MAC database; finally, the LLDP neighbor information collection unit 333 is called to communicate with the BMC of the target server based on the network device configuration information and by calling the second HTTPS service unit 334, executes the corresponding commands to collect the port LLDP neighbor information of the network device and records it in the LLDP information database.

[0106] Step 805: Start information processing module 320;

[0107] Specifically, firstly, the second information acquisition unit 321 in the information processing module 320 is activated to obtain the actual MAC address of the target server from the server network port MAC database, denoted as MAC_A; and to obtain the port LLDP neighbor information of the network device from the LLDP information database; then, the connection relationship comparison unit 322 is activated to parse the MAC address of the peer server network port that is actually connected to the port of the network device from the port LLDP neighbor information, denoted as MAC_B. If MAC_A and MAC_B are consistent, the connection check result between the target server and the network device is determined to be a correct connection relationship; if MAC_A and MAC_B are inconsistent, the connection check result between the target server and the network device is determined to be an incorrect connection relationship; based on the connection check failure type that matches the connection relationship error, at least one abnormal connection rectification suggestion is generated; and the connection check result and connection check failure type are recorded in the connection relationship status database.

[0108] Step 806: Determine if the connection is correct. If the connection is correct, proceed to step 807; if the connection is incorrect, proceed to step 808.

[0109] Step 807: Start the report output module;

[0110] Specifically, the third information acquisition unit 341 in the report output module 340 is first activated to obtain the connection check results of the target server from the connection relationship status database. Based on the connection check results of the target server, the device pass rate, connection item pass rate, and abnormal connection rectification suggestions of the target server are determined. Then, the report output unit 342 is called to generate an inspection report based on the connection check results of the target server.

[0111] Step 808: Check the failure type of the matched connection and generate rectification suggestions for the abnormal connection;

[0112] Step 809: Round-robin check;

[0113] Specifically, after the initial inspection is completed, the user reviews the inspection report; whether the abnormal connection rectification items are included in the inspection report determines whether the connection needs to be rectified; if there are no abnormal connection rectification items in the inspection report, the process ends; if there are connection rectification items in the inspection report, proceed to step 810.

[0114] Step 810: Based on the corresponding abnormal connection rectification suggestions in the information of the failed entries, conduct targeted investigation and rectification;

[0115] Step 811: After the rectification is completed, continue to use the wiring inspection device to check and finally ensure the correctness of all wiring.

[0116] Figure 9 The diagram illustrates the structure of an electronic device 9000 implementing the embodiments of this application. Referring to the diagram, at the hardware level, the electronic device 9000 includes a processor 910, and optionally includes an internal bus 920, a network interface 930, and a memory 940. The memory 940 may include main memory 941, such as high-speed random-access memory (RAM), and may also include non-volatile memory 942, such as at least one disk storage device. Of course, the electronic device 900 may also include other hardware required for other services.

[0117] The processor 910, network interface 930, and memory can be interconnected via an internal bus 920. This internal bus 920 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only a single bidirectional arrow is used in this diagram, but this does not imply that there is only one bus or one type of bus.

[0118] Memory 940 stores programs. Specifically, the program may include program code, which includes computer operation instructions. Memory 940 may include main memory 941 and non-volatile memory 942, and provides instructions and data to processor 910.

[0119] The processor 910 reads the corresponding computer program from the non-volatile memory 942 into memory and then runs it, forming a device for locating the target user at the logical level. The processor 910 executes the program stored in memory and specifically performs the following: Figure 2 or Figure 8 The methods disclosed in the embodiments shown achieve the functions and beneficial effects of the methods described in the preceding method embodiments, and will not be repeated here.

[0120] The above is as stated in this application. Figure 2 or Figure 8 The methods disclosed in the illustrated embodiments can be applied to or implemented by processor 910. Processor 910 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above methods can be completed by integrated logic circuits in the hardware or by instructions in software form within processor 910. The processor 910 can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0121] The electronic device can also execute the methods described in the preceding method embodiments and achieve the functions and beneficial effects of the methods described in the preceding method embodiments, which will not be repeated here.

[0122] Of course, in addition to software implementation, the electronic device of this application does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. In other words, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0123] This application also proposes a computer-readable storage medium that stores one or more programs, which, when executed by an electronic device including multiple applications, cause the electronic device to perform... Figure 2 or Figure 8 The methods disclosed in the embodiments shown achieve the functions and beneficial effects of the methods described in the preceding method embodiments, and will not be repeated here.

[0124] The computer-readable storage medium mentioned above includes read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, etc.

[0125] Furthermore, embodiments of this application also provide a computer program product, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions, which, when executed by a computer, implement... Figure 2 or Figure 8 The methods disclosed in the embodiments shown achieve the functions and beneficial effects of the methods described in the preceding method embodiments, and will not be repeated here.

[0126] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0127] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can store information accessible to a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0128] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0129] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

Claims

1. A method of wire checking, characterized by, The method comprises the following steps: generating a management interface of a target server according to server configuration information of the target server; sending link layer discovery protocol (LLDP) start information to the target server through the management interface of the target server; determining a connection check result between the target server and a network device according to port LLDP neighbor information of the network device.

2. The method of claim 1, wherein, The step of sending the LLDP start information to the target server through the management interface of the target server comprises the following steps: inquiring an LLDP service state of the target server through the management interface of the target server; in a case where the LLDP service state of the target server is determined to be a closed state, sending the LLDP start information to the target server.

3. The method of claim 1, wherein, The step of sending the LLDP start information to the target server through the management interface of the target server comprises the following steps: establishing a communication connection between the management interface of the target server and a baseboard management controller of the target server; sending the LLDP start information to the baseboard management controller of the target server, and communicating with a network card module of the target server through the baseboard management controller, so that the network card module sends device state information of the target server to an adjacent device.

4. The method of claim 1, wherein, The step of determining the connection check result between the target server and the network device according to the port LLDP neighbor information of the network device comprises the following steps: obtaining the port LLDP neighbor information of the network device according to network device configuration information of the network device; obtaining a MAC address of the target server by analyzing the port LLDP neighbor information of the network device; determining the connection check result between the target server and the network device according to consistency between the MAC address of the target server and an actual MAC address of the target server.

5. The method of claim 4, wherein, The step of determining the connection check result between the target server and the network device according to consistency between the MAC address of the target server and the actual MAC address of the target server comprises the following steps: in a case where the MAC address of the target server is consistent with the actual MAC address of the target server, determining that the connection check result between the target server and the network device is correct; in a case where the MAC address of the target server is inconsistent with the actual MAC address of the target server, determining that the connection check result between the target server and the network device is incorrect.

6. The method of claim 5, wherein, After determining that the connection check result between the target server and the network device is incorrect, the method further comprises the following steps: determining a connection check failure type matched with the incorrect connection according to the server configuration information and the network device configuration information; generating at least one abnormal connection rectification suggestion according to the connection check failure type.

7. The method of claim 1, wherein, After determining the connection check result of the target server, the method further comprises the following steps: According to the connection checking result of the target server, a checking report is generated, and the checking report at least includes one of the following: a device pass rate of the target server and a connection entry pass rate of the target server.

8. The method according to any one of claims 1 to 7, characterized in that, Before the server configuration information of the target server is used to generate the management interface of the target server, the method further includes: Obtaining pre-configured planning connection information; The server configuration information of the target server is obtained by analyzing the planning connection information.

9. An electronic device, comprising: The electronic device includes a processor and a memory, the memory stores programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement the steps of the method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores programs or instructions, and the programs or instructions are executed by the processor to implement the steps of the method according to any one of claims 1 to 8.

Images