Cable detection method and device

Abstract

The invention provides a cable detection method and equipment. The method comprises the steps that cable data are obtained, the cable data are cable data corresponding to cable loop data sent by a mainboard complex programmable logic device CPLD of a server according to a preset data format, and the cable loop data are cable data generated by the mainboard CPLD according to a cable connection relation; and according to the cable data and the preset configuration data, judging whether the cable of the server has a connection fault or not. The method is used for improving the cable detection effect.

Description

Technical Field

[0001] The present application relates to the technical field of server hardware, and in particular to a cable detection method and device. Background Art

[0002] In modern data centers and cloud computing environments, servers are core devices for data processing and storage, and their stable operation is crucial. A complex cable network is used inside the server to achieve high-speed data transmission and command synchronization between various components. The correct connection and performance status of the cables directly affect the overall performance and stability of the server.

[0003] Testing server cables to ensure that all cables are correctly connected is a necessary measure to maintain normal server operation and efficient data processing. At present, server cable detection mainly relies on in-place signal level detection technology. This technology monitors the in-place signal level changes generated after the cable is inserted by setting detection circuits at both ends of the cable connector. When the cable is correctly inserted into the connector, a low-level signal is formed, indicating that the cable is in place; if the cable is not inserted or the connection is poor, the detected signal level is high, indicating that the cable is not in place.

[0004] However, the above detection method cannot identify whether the cables are connected incorrectly, and the detection effect is poor. Summary of the invention

[0005] The present application provides a cable detection method and device to solve the problem of poor cable detection effect in the prior art.

[0006] In a first aspect, the present application provides a cable detection method, comprising:

[0007] Acquire cable data, where the cable data is cable data corresponding to cable loop data sent by a mainboard complex programmable logic device (CPLD) of the server in a preset data format, and the cable loop data is cable data generated by the mainboard CPLD according to the cable connection relationship;

[0008] According to the cable data and the preset configuration data, determine whether there is a connection fault in the cable of the server.

[0009] In some embodiments, obtaining cable data includes:

[0010] The cable data is obtained from the backplane CPLD of the server, where the cable data is the cable loop data after the backplane CPLD performs protocol conversion on the cable loop data.

[0011] In some embodiments, obtaining cable data includes:

[0012] The cable data is obtained from the mainboard CPLD. The cable data is cable loop data sent by the mainboard CPLD and looped back to the mainboard CPLD via the expansion card.

[0013] In some embodiments, judging whether a cable of the server has a connection fault according to the cable data and the preset configuration data includes:

[0014] When the cable data is the first preset configuration data, it is determined that there is no connection fault in the server cable;

[0015] When the cable data is the second preset configuration data, determining that the server cable is not connected;

[0016] The cable data is not the second preset configuration data and is different from the first preset configuration data by at least one bit, and it is determined that the server cable connection is faulty.

[0017] In some embodiments, after determining that the server cable connection failure occurs, the method further includes:

[0018] The fault type is determined according to the cable data and the first preset configuration data, and the fault type includes a cable attribution error and a cable sequence number error.

[0019] In some embodiments, obtaining cable data includes:

[0020] Get cable data through I2C (Inter-Integrated Circuit) data transmission channel.

[0021] In some embodiments, obtaining cable data includes:

[0022] The cable data is obtained by polling the register of the receiving unit, which is the backplane CPLD or expansion card.

[0023] In a second aspect, the present application provides a cable detection device, comprising:

[0024] An acquisition module is used to acquire cable data, where the cable data is cable data corresponding to the cable loop data sent by the mainboard CPLD of the server in a preset data format, and the cable loop data is cable data generated by the mainboard CPLD according to the cable connection relationship;

[0025] The judgment module is used to judge whether there is a connection fault in the cable of the server according to the cable data and the preset configuration data.

[0026] In a third aspect, the present application provides an electronic device, including: a memory and a processor;

[0027] The memory is used to store computer programs; the processor is used to execute the computer programs stored in the memory to implement the cable detection method in the first aspect and any one of the embodiments of the first aspect.

[0028] In a fourth aspect, the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the cable detection method in the first aspect and any one of the embodiments of the first aspect is implemented.

[0029] In a fifth aspect, the present application provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the cable detection method in the first aspect and any one of the embodiments of the first aspect.

[0030] The cable detection method and device provided in the present application obtain the cable connection data sent by the server mainboard CPLD and compare the cable connection data with the preset configuration data to determine whether there is a connection fault in the cable, thereby improving the cable detection effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the technical solutions in the present application or the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0032] Figure 1 A flow chart of a cable detection method provided in one embodiment of the present application;

[0033] Figure 2 A schematic diagram of a cable detection scenario provided in an embodiment of the present application;

[0034] Figure 3 A schematic diagram of another cable detection scenario provided in an embodiment of the present application;

[0035] Figure 4 A schematic diagram of the structure of a cable detection device provided in one embodiment of the present application;

[0036] Figure 5 A schematic diagram of the hardware structure of an electronic device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0037] In order to make the purpose, technical solutions and advantages of this application clearer, the technical solutions in this application will be clearly and completely described below in conjunction with the drawings in this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0038] The terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances. For example, without departing from the scope of this document, first information can also be referred to as second information, and similarly, second information can also be referred to as first information.

[0039] As used herein, the word "if" may be interpreted as "when" or "when" or "in response to determining," depending on the context.

[0040] It should be understood that the terms “comprises” and “includes” indicate the existence of features, steps, operations, elements, components, items, types, and / or groups, but do not exclude the existence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, types, and / or groups.

[0041] The terms "or" and "and / or" used herein are interpreted as inclusive, or mean any one or any combination. Thus, "A, B and / or C" means "any of the following: A; B; C; A and B; A and C; B and C; A, B and C". An exception to this definition will only occur when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.

[0042] In modern data centers and cloud computing environments, servers are core devices for data processing and storage, and their stable operation is crucial. The correct connection and performance status of cables directly affect the overall performance and stability of the server. Therefore, ensuring that all cables are correctly connected is a necessary measure to maintain the normal operation of the server and efficient data processing. Timely detection and resolution of cable faults can effectively prevent serious consequences such as data loss and system crashes, and ensure the continuity and reliability of data center services.

[0043] At present, the detection of server cables mainly relies on the in-place signal level detection technology. This technology sets detection circuits at both ends of the cable connector to monitor the changes in the in-place signal level generated after the cable is inserted. When the cable is correctly inserted into the connector, a low-level signal is formed, indicating that the cable is in place; if the cable is not inserted or the connection is poor, the detected signal level is high, indicating that the cable is not in place. This detection method is simple and direct, and can reflect the physical connection status of the cable to a certain extent. It has a certain detection capability for basic cable plugging and unplugging failures.

[0044] However, the above cable detection method has significant limitations. First, it can only detect whether the cable is in place, but cannot further identify complex fault conditions such as whether the cable type matches, whether the cable is plugged into other connectors incorrectly, and whether the internal signal lines of the cable (such as the high and low 8 bits) are connected in reverse. These problems often need to be discovered after the server is turned on and the relevant high-speed serial computer expansion bus standard (Peripheral Component Interconnect Express, PCIE) equipment is running, which not only increases the complexity and time cost of system debugging, but may also cause system instability or data errors due to cable failures in the early stage of startup. Secondly, the existing detection technology lacks immediacy and intelligence, and cannot automatically warn of potential cable connection problems before system deployment or in the early stage of operation, which brings additional challenges to the operation and maintenance management of the data center.

[0045] In response to the above problems, the present application proposes a cable detection method and device. In this method, after the server is turned on, the server's mainboard CPLD generates cable data according to the cable connection status, and sends the data to the backplane CPLD or back to the mainboard CPLD via the expansion card. The server compares the cable data with the preset configuration data. Since the preset configuration data can reflect the correct connection relationship of the cable, it is possible to determine whether the cable has a connection fault based on the data comparison result. By setting a fixed data format for the data, the abnormal position of the cable data using this data format can reflect the specific fault type of the cable, thereby achieving the effect of improving the accuracy of cable detection.

[0046] The technical solution of the present application is described in detail with specific embodiments below. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

[0047] In the present application, the cable detection method of the following embodiments is executed with the server as the execution subject. Specifically, the execution subject may be a hardware device of the server, for example, a baseboard management controller (BMC) of the server, or a software application implementing the following embodiments in the server, or a computer-readable storage medium installed with the software application implementing the following embodiments, or a code of the software application implementing the following embodiments.

[0048] Figure 1 FIG. 1 is a flow chart of a cable detection method provided by an embodiment of the present application. Figure 1 As shown, with the server as the execution subject, the method of this embodiment may include the following steps:

[0049] S101. Obtain cable data.

[0050] In this embodiment, the cable may be a high-speed cable in the server, used to support high-speed data transmission. The cable data is cable data corresponding to the cable loop data sent by the server's mainboard CPLD in a preset data format, and the cable loop data is cable data generated by the mainboard CPLD according to the cable connection relationship.

[0051] The server's motherboard high-speed connector usually needs to define cable loop (Cable Loop) data, cable loop back (Cable Loop Back) data and board identification (Board ID) signals. Among them, the Cable Loop signal is defined in the high-speed connector corresponding to PCIE[7:0] (i.e., the lower 8 bits), and the Cable Loop Back signal is defined in the high-speed connector corresponding to PCIE[15:8] (i.e., the upper 8 bits). The number of Board ID signals is determined by the complexity of the server design. The Cable Loop, Cable Loop Back and Board ID signals are all connected to the motherboard CPLD pins. The motherboard CPLD controls the Cable Loop pin to send data and the Cable Loop Back pin to receive data.

[0052] The mainboard CPLD sends a Cable Loop signal, which carries cable loop data in a preset data format. The preset data format is shown in Table 1.

[0053] Table 1

[0054]

[0055] BOARD ID indicates the high-speed connector identifier recognized by the mainboard CPLD.

[0056] Cable ownership indicates which chips the PCIE to which the current cable is connected belongs to. For example, the chip corresponding to 0000 is the central processing unit (CPU) 0, the chip corresponding to 0001 is CPU1, and the chip corresponding to 0010 is the platform controller hub (Platform Controller Hub, PCH), etc.

[0057] The cable serial number indicates the serial number of the current cable under the corresponding chip. For example, 0000 indicates that the current cable is connected to the high-speed connector (Modular Connector Input Output, MCIO)-0 of the chip CPU0, and 0001 indicates that the current cable is connected to the MCIO-1 of the chip CPU0.

[0058] Reserved indicates bits reserved for other functions.

[0059] The parity bit is used to check the data bit. If the parity bit sent by the sender does not match the bit calculated by the receiver based on the received data, the receiver needs to discard the transmitted data.

[0060] In this embodiment, after the cable connection is completed, the high-speed connector PINs of the sender and the receiver are determined accordingly. Therefore, after the server is powered on, the mainboard CPLD can determine the cable loop data based on the connection relationship of the cable, that is, the high-speed connector PINs of the sender and the receiver.

[0061] The cable data corresponding to the cable loop data sent by the mainboard CPLD according to the above preset data format is the cable data after the receiving party processes the cable loop data. Here, the processing by the receiving party may be format parsing or other processing.

[0062] S102: Determine whether there is a connection fault in the cable of the server according to the cable data and the preset configuration data.

[0063] In this embodiment, the server stores preset configuration data, which is used to indicate the cable loop data corresponding to the correct cable connection, i.e., reference data. After the server obtains the cable data, it compares it with the preset configuration data, i.e., the reference data, to determine whether the server's cable has a connection error.

[0064] The cable detection method provided in this embodiment obtains cable data reflecting the actual connection status of the cable, compares the cable data with preset configuration data, and then determines whether there is an error in the cable connection, thereby achieving the effect of accurately detecting the cable connection relationship.

[0065] like Figure 2As shown, in some embodiments, the specific implementation of step S101 is to obtain cable data from the backplane CPLD of the server.

[0066] The cable data is the cable loop data obtained after the backplane CPLD performs protocol conversion on the cable loop data.

[0067] Specifically, the mainboard CPLD sends data through different Cable Loop signal pins according to the preset data format, and the backplane CPLD receives the Cable Loop signal from the mainboard CPLD. The server's BMC accesses the backplane CPLD, obtains the corresponding cable data, and compares the cable data with the preset configuration data. If the comparison result shows that the cable data is incorrect, it means that the cable is connected incorrectly. At this time, the specific error type can be determined based on the BOARD ID, cable ownership, cable serial number and other data, so as to quickly and accurately detect the problem of reverse or incorrect cable connection.

[0068] like Figure 3 As shown, in some embodiments, the specific implementation of step S101 is to obtain cable data from the mainboard CPLD.

[0069] The cable data is cable loop data sent by the mainboard CPLD and looped back to the mainboard CPLD via the expansion card.

[0070] Specifically, the mainboard CPLD sends data through different Cable Loop signal pins according to the preset data format, and Cable Loop Back is the signal that Cable Loop loops back to the mainboard CPLD via the expansion card (Riser card). Cable Loop and Cable Loop Back are signals under the same set of PCIE x16 high-speed connectors.

[0071] The BMC accesses the mainboard CPLD to obtain the cable loopback data carried by the Cable Loop Back signal, and compares the cable loopback data with the preset configuration data to determine whether there is a connection fault in the cable.

[0072] Optionally, the server obtains the cable data through an I2C data transmission channel, thereby improving the efficiency of obtaining data.

[0073] Optionally, the server obtains the cable data from a register of the receiving unit by polling.

[0074] The receiving unit is a backplane CPLD or an expansion card.

[0075] In this embodiment, after the server is powered on, the mainboard CPLD can send data, and the receiving unit parses the data and stores it in the register of the receiving unit, so that the BMC can poll the register to obtain data after startup, which is highly flexible. When the data changes frequently, the polling interval can be shortened to improve real-time performance; when the data changes infrequently, the polling interval can be extended to save resources. The server can adjust the polling interval according to actual needs.

[0076] In some embodiments, the specific implementation of step S102 includes:

[0077] S1021: When the cable data is the first preset configuration data, determine that there is no connection fault in the server cable.

[0078] Among them, the first preset configuration data is the cable data corresponding to when the server cable is correctly connected. When the cable data obtained by the server is consistent with the first preset configuration data, it can be determined that the current cable connection is correct, that is, there is no cable connection failure.

[0079] S1022: When the cable data is the second preset configuration data, determine that the server cable is not connected.

[0080] Among them, the second preset configuration data is the cable data corresponding to when the server cable is not connected or not fully connected. When the cable data obtained by the server is consistent with the second preset configuration data, it can be determined that the current cable is not connected or not fully connected. For example, the second preset configuration data is all 0s or all 1s in the preset data format. It can be understood that when the cable is not connected or not fully connected, the mainboard CPLD cannot send the cable loop data, and accordingly, the receiving unit does not receive the corresponding data. At this time, when the server obtains the cable data from the receiving unit, it can obtain a set of specific data, that is, data consistent with the second preset configuration data.

[0081] S1023: The cable data is not the second preset configuration data and is different from the first preset configuration data by at least one bit, and it is determined that the server cable connection is faulty.

[0082] Specifically, the cable data is not the second preset configuration data, indicating that the cable is connected.

[0083] The cable data and the first preset configuration data have at least one different bit, which means that the cable data and the first preset configuration data are both data in a preset data format, and the same bit can be compared according to the preset data format. When at least one bit of data is different, it can be determined that there is a fault in the current cable connection.

[0084] In some embodiments, after determining in step S1023 that the server cable connection is faulty, the server may also determine the fault type based on the cable data and the first preset configuration data.

[0085] Among them, the fault types include cable attribution error and cable serial number error.

[0086] For example, if the cable data and the first preset configuration data are inconsistent in the bit indicating the cable ownership, it may indicate that the cable ownership is wrong. If the cable data and the first preset configuration data are inconsistent in the bit indicating the cable serial number, it may indicate that the cable serial number is wrong.

[0087] It should be understood that the fault type may also include a board connection error, that is, a receiving unit connection error.

[0088] The cable detection method of the embodiment of the present application determines the board identification of the mainboard after the BMC is started, and compares it with the board identification in the preset configuration data to determine whether the cable is correctly connected to the board. Compared with the prior art, after a long wait to enter the server operating system, it detects whether the cable is connected incorrectly when the PCIE function is found to be faulty, the cable detection method of the embodiment of the present application can detect whether the cable is connected incorrectly more quickly, and by comparing the cable data in the preset data format with the preset configuration data, according to the comparison result of each bit, it can accurately identify which group of cables in the server has the problem of wrong connection or reverse connection, thereby improving the effect of cable detection.

[0089] Figure 4 FIG. 1 shows a schematic diagram of the structure of a cable detection device provided in an embodiment of the present application. Figure 4 As shown, the cable detection device 10 of this embodiment is used to implement the operation corresponding to the electronic device in any of the above method embodiments. The cable detection device 10 of this embodiment includes:

[0090] An acquisition module 11 is used to acquire cable data, where the cable data is cable data corresponding to cable loop data sent by the mainboard CPLD of the server in a preset data format, and the cable loop data is cable data generated by the mainboard CPLD according to the cable connection relationship;

[0091] The judgment module 12 is used to judge whether there is a connection fault in the cable of the server according to the cable data and the preset configuration data.

[0092] The cable detection device 10 provided in the embodiment of the present application can execute the above method embodiment. Its specific implementation principle and technical effects can be found in the above method embodiment, and this embodiment will not be repeated here.

[0093] Figure 5 FIG. 1 shows a hardware structure diagram of an electronic device provided in an embodiment of the present application. Figure 5As shown, the electronic device 20 is used to implement the operations corresponding to the electronic device in any of the above method embodiments. The electronic device 20 of this embodiment may include: a memory 21, a processor 22 and a communication interface 24.

[0094] The memory 21 is used to store computer programs. The memory 21 may include a high-speed random access memory (RAM), and may also include a non-volatile memory (NVM), such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a disk, or an optical disk.

[0095] The processor 22 is used to execute the computer program stored in the memory to implement the method in the above embodiment. For details, please refer to the relevant description in the above method embodiment. The processor 22 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the invention can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor.

[0096] Optionally, the memory 21 may be independent or integrated with the processor 22 .

[0097] When the memory 21 is a device independent of the processor 22, the electronic device 20 may further include a bus 23. The bus 23 is used to connect the memory 21 and the processor 22. The bus 23 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0098] The communication interface 24 may be connected to the processor 22 via the bus 23. The processor 22 may control the communication interface 24 to implement the functions of receiving and sending signals.

[0099] The electronic device 20 provided in this embodiment can be used to execute the above-mentioned cable detection method, and its implementation method and technical effect are similar, which will not be described in detail in this embodiment.

[0100] The present application also provides a computer-readable storage medium, in which a computer program / instruction is stored. When the computer program / instruction is executed by a processor, it is used to implement the methods provided in the various embodiments described above.

[0101] Among them, the computer-readable storage medium can be a computer storage medium or a communication medium. The communication medium includes any medium that is convenient for transmitting a computer program from one place to another. The computer storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, a computer-readable storage medium is coupled to a processor so that the processor can read information from the computer-readable storage medium and write information to the computer-readable storage medium. Of course, the computer-readable storage medium can also be a component of the processor. The processor and the computer-readable storage medium can be located in an application-specific integrated circuit (ASIC). In addition, the ASIC can be located in a user device. Of course, the processor and the computer-readable storage medium can also exist in a communication device as discrete components.

[0102] Specifically, the computer-readable storage medium may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The storage medium may be any available medium that can be accessed by a general or special-purpose computer.

[0103] The present application also provides a computer program product, which includes a computer program / instruction, and the computer program / instruction is stored in a computer-readable storage medium. At least one processor of the device can read the computer program / instruction from the computer-readable storage medium, and at least one processor executes the computer program / instruction so that the device implements the methods provided in the various embodiments described above.

[0104] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of modules is only a logical function division. There may be other division methods in actual implementation. For example, multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0105] Among them, each module can be physically separated, for example, installed in different locations of a device, or installed on different devices, or distributed on multiple network units, or distributed on multiple processors. Each module can also be integrated together, for example, installed in the same device, or integrated in a set of codes. Each module can exist in the form of hardware, or can also exist in the form of software, or can also be implemented in the form of software plus hardware. The present application can select some or all of the modules according to actual needs to achieve the purpose of the present embodiment.

[0106] It should be understood that, although the various steps in the flowcharts in the above-described embodiments are sequentially displayed according to the indications of the arrows, these steps are not necessarily executed sequentially in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and they can be executed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily to be carried out sequentially, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0107] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0108] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the above embodiments, a person of ordinary skill in the art should understand that the technical solutions described in the above embodiments can still be modified, or some or all of the technical features can be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A cable detection method, characterized in that: include: Acquire cable data, where the cable data is cable data corresponding to cable loop data sent by a mainboard complex programmable logic device (CPLD) of the server in a preset data format, where the cable loop data is cable data generated by the mainboard CPLD according to a cable connection relationship; It is determined whether there is a connection fault in the cable of the server according to the cable data and the preset configuration data.

2. The method according to claim 1, characterized in that Get cable data, including: The cable data is obtained from a backplane CPLD of a server, wherein the cable data is cable loop data after the backplane CPLD performs protocol conversion on the cable loop data.

3. The method according to claim 1, characterized in that Get cable data, including: The cable data is obtained from the mainboard CPLD, where the cable data is cable loop data sent by the mainboard CPLD and looped back to the mainboard CPLD via the expansion card.

4. The method according to any one of claims 1 to 3, characterized in that: Judging whether there is a connection fault in the cable of the server according to the cable data and the preset configuration data includes: When the cable data is the first preset configuration data, it is determined that there is no connection fault in the server cable; When the cable data is the second preset configuration data, determining that the server cable is not connected; The cable data is not the second preset configuration data and is different from the first preset configuration data by at least one bit, and a server cable connection fault is determined.

5. The method according to claim 4, characterized in that After confirming that the server cable connection is faulty, the following steps are also required: A fault type is determined according to the cable data and the first preset configuration data, where the fault type includes a cable attribution error and a cable sequence number error.

6. The method according to any one of claims 1 to 3, characterized in that: Get cable data, including: The cable data is obtained through the I2C data transmission channel.

7. The method according to any one of claims 1 to 3, characterized in that: Get cable data, including: The cable data is obtained by polling a register of a receiving unit, where the receiving unit is a backplane CPLD or an expansion card.

8. A cable detection device, characterized in that: include: An acquisition module is used to acquire cable data, wherein the cable data is cable data corresponding to cable loop data sent by a mainboard complex programmable logic device CPLD of the server in accordance with a preset data format, and the cable loop data is cable data generated by the mainboard CPLD according to a cable connection relationship; The judgment module is used to judge whether there is a connection fault in the cable of the server according to the cable data and the preset configuration data.

9. An electronic device, characterized in that: include: Memory and processor; The memory is used to store computer programs; The processor is used to execute the computer program stored in the memory to implement the cable detection method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it is used to implement the cable detection method according to any one of claims 1 to 7.

11. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the cable detection method according to any one of claims 1 to 7 is implemented.

Images