Intelligent detection method, device and equipment for server cable configuration and medium

Abstract

The invention discloses an intelligent detection method, device and equipment for server cable configuration and a medium, and relates to the technical field of server configuration.The method comprises the steps that identifier values preset for connectors of a backboard in a CPLD of the backboard are correspondingly read through I 2C interfaces of the connectors on a mainboard; according to the read identifier value, constructing an actual connection table containing a corresponding relation between the connector of the mainboard and the connector of the backboard; judging whether the actual connection table is consistent with a pre-stored expected connection table or not; and if the actual connection table is not consistent with a pre-stored expected connection table, sending connection error alarm information. The method has the capability of automatically detecting the physical connection relation of the cables between the backboard and the mainboard and sensing errors, wrong connection configuration is found in time, and then it is ensured that the system operates in an expected state.

Description

Technical Field

[0001] This invention relates to the field of server configuration technology, and in particular to an intelligent detection method, device, equipment and medium for server cable configuration. Background Technology

[0002] With the rapid development of the information technology industry, servers, as core infrastructure, have seen their application areas continuously expand, and market shipments have shown a significant growth trend. To meet increasingly complex computing and storage demands, modern servers are generally equipped with powerful central processing units (CPUs), which typically integrate abundant PCIe (Peripheral Component Interconnect Express) channel resources. This feature gives server system configurations extremely high flexibility, especially in storage subsystem design. However, due to the limited physical space within servers, hard drive backplanes usually cannot be directly inserted into the PCIe slots on the motherboard for connection. Therefore, bridging the hard drive backplane and the PCIe connector on the motherboard with a cable has become a common and necessary solution.

[0003] While this cable connection method offers significant flexibility, it also introduces considerable complexity. Specifically, a particular connector on a single hard drive backplane (e.g., the JA1 connector on hard drive backplane 1) can theoretically be connected to any one of the many similar PCIe connectors on the motherboard (e.g., J01, J02, ..., J0n) via different cables. Similarly, any PCIe connector on the motherboard can be selectively connected to different connectors on different hard drive backplanes. This "many-to-many" connectivity possibility stems from a key factor: both the PCIe connectors on the motherboard and the corresponding connectors on the hard drive backplanes are typically standardized and consistent in their physical interface definitions (e.g., pin arrangement, electrical characteristics) and mechanical dimensions. While this consistency ensures physical connection compatibility, giving engineers considerable freedom in designing cabling schemes to adapt to different performance or topology requirements, it is precisely this high degree of flexibility and the high similarity in connector appearance that presents significant challenges to actual production assembly and field deployment.

[0004] Currently, the industry's commonly used solutions rely on manual operation and blueprint guidance. System engineers, based on pre-designed intent, create detailed cable connection diagrams or lists, clearly specifying which motherboard and backplane connectors each cable should connect to (e.g., specifying "Cable 5" to connect motherboard "J05" to backplane "JB1"). Assembly personnel or end users must then strictly follow these diagrams for physical connections. The success of this approach heavily depends on the operator's conscientiousness, understanding of the blueprints, meticulousness in identifying connectors, and operational proficiency. In real-world environments, with numerous similarly shaped connectors densely packed within servers, even the most cautious operator cannot completely avoid connection errors. For example, a cable intended for J01 might be mistakenly inserted into an adjacent, identical-looking J02 connector.

[0005] More critically, the existing solution suffers from a fundamental flaw: the system itself lacks the ability to perceive and verify the actual physical connections. After the server powers on, the system firmware or management controller cannot automatically detect and confirm whether the cables are correctly connected as required by the design drawings. Even if a connection error occurs (such as the hard drive backplane being connected to an unexpected PCIe lane), the system can usually still boot and run, but it may operate in an suboptimal configuration (e.g., some high-speed devices are incorrectly connected to a low-bandwidth lane, or the intended redundant path is not correctly established), leading to potential performance degradation, functional deficiencies, or reliability risks. Furthermore, because the system cannot perceive errors, it naturally cannot provide any form of error indication or alarm. When the system experiences performance anomalies or other problems, the troubleshooting process becomes extremely difficult. Technicians need to spend a significant amount of time performing tedious manual checks to locate possible cable connection errors, greatly reducing deployment efficiency and operational experience, and increasing the total cost of ownership.

[0006] In summary, the core technical problem with the existing technology is that the server system lacks the ability to automatically detect and identify errors in the physical connection between the hard drive backplane and the motherboard. This makes it difficult to detect incorrect connection configurations, which in turn may cause the system to operate in an unexpected state and result in low efficiency in troubleshooting. Summary of the Invention

[0007] This invention provides an intelligent detection method, device, equipment, and medium for server cable configuration, aiming to solve the problem that existing server systems lack the ability to automatically detect and perceive errors in the physical connection relationship of cables between the hard drive backplane and the motherboard, making it difficult to detect incorrect connection configurations, which in turn may cause the system to operate in an unexpected state and result in low troubleshooting efficiency.

[0008] In a first aspect, embodiments of the present invention provide an intelligent detection method for server cable configuration, comprising:

[0009] By using the I2C interfaces of each connector on the motherboard, the preset identifier values ​​for each connector on the backplane are read from the CPLD of the backplane.

[0010] Based on the read identifier value, construct an actual connection table containing the correspondence between the connectors of the motherboard and the connectors of the backplane;

[0011] Determine whether the actual join table is consistent with the pre-stored expected join table;

[0012] If the actual join table is inconsistent with the pre-stored expected join table, a join error alarm message will be issued.

[0013] A further technical solution is to set registers for the I2C interfaces corresponding to the connectors connecting to the motherboard in the CPLD of the backplane, and configure the values ​​of each register to the corresponding identifier values.

[0014] A further technical solution is that, by reading the preset identifier values ​​for each connector on the backplane from the CPLD of the backplane via the I2C interfaces of each connector on the motherboard, the following steps are taken:

[0015] The identifier values ​​in the corresponding registers of the CPLD on the backplane are read through the I2C interfaces of each connector on the motherboard.

[0016] A further technical solution is that the identifier values ​​corresponding to the connectors in the backplate are all different.

[0017] A further technical solution is that the expected connection table is pre-stored in the BMC of the motherboard in the form of a data structure, including the connector numbers of the motherboard, the connector numbers of the backplane, and the corresponding identifier values.

[0018] A further technical solution is that determining whether the actual join table is consistent with the pre-stored expected join table includes:

[0019] Verify item by item whether the mapping relationship between the motherboard connectors and the backplane connectors in the actual connection table matches the expected connection table.

[0020] A further technical solution is that the connection error alarm information includes error location information, which is used to indicate the numbers of the mismatched motherboard connector and the backplane connector.

[0021] Secondly, embodiments of the present invention also provide an intelligent detection device for server cable configuration, which includes a unit for performing the above-described method.

[0022] Thirdly, embodiments of the present invention also provide a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the above-described method.

[0023] Fourthly, embodiments of the present invention also provide a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the above-described method.

[0024] This invention provides an intelligent detection method, apparatus, device, and medium for server cable configuration. The method includes: reading preset identifier values ​​for each connector on the backplane from the CPLD of the backplane via the I2C interfaces of each connector on the motherboard; constructing an actual connection table containing the correspondence between the motherboard connectors and the backplane connectors based on the read identifier values; determining whether the actual connection table matches a pre-stored expected connection table; and issuing a connection error alarm if the actual connection table does not match the pre-stored expected connection table. This invention has the ability to automatically detect and perceive errors in the physical connection relationship of cables between the backplane and the motherboard, promptly identifying incorrect connection configurations, thereby ensuring that the system operates in the expected state. Attached Figure Description

[0025] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0026] Figure 1 A flowchart illustrating an intelligent detection method for server cable configuration provided in an embodiment of the present invention;

[0027] Figure 2 A schematic diagram of the server cable configuration provided in an embodiment of the present invention;

[0028] Figure 3 This is a schematic block diagram of a computer device provided in an embodiment of the present invention. Detailed Implementation

[0029] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0030] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0031] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0032] It should also be further understood that the term "and / or" as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0033] As used in this specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrases "if determined" or "if [described condition or event] is detected" may be interpreted, depending on the context, as "once determined," "in response to determination," "once [described condition or event] is detected," or "in response to detection of [described condition or event]."

[0034] Please see Figure 1 This invention provides an intelligent detection method for server cable configuration, the method comprising the following steps:

[0035] S1, via the I2C interfaces of each connector on the motherboard, read the preset identifier values ​​for each connector on the backplane from the CPLD. The connector may specifically be a PCIe connector; however, this invention does not specifically limit its application to this.

[0036] S2, Based on the read identifier value, construct an actual connection table containing the correspondence between the connectors of the motherboard and the connectors of the backplane.

[0037] S3, determine whether the actual join table is consistent with the pre-stored expected join table.

[0038] S4. If the actual connection table is inconsistent with the pre-stored expected connection table, a connection error alarm message is issued.

[0039] The intelligent detection method for server cable configuration provided by this invention reads preset identifier values ​​from the backplane CPLD through the I2C interfaces of each connector on the motherboard. Based on these values, it constructs an actual connection table corresponding to the motherboard and backplane connectors, and then performs a consistency check with a pre-stored expected connection table. If there is a discrepancy, it triggers a connection error alarm. Specifically:

[0040] First, a unique electronic identification and automated verification mechanism for connectors was established. Using a pre-defined identifier value for each connector via the backplane CPLD, a digital identity that can be recognized by the system is assigned to the physical connector (e.g., JA1 corresponds to a specific coded value), and the identity information is transmitted unambiguously through the existing I2C interface bus resource. Upon system power-up, the identifier value is automatically read and an actual connection table is generated, completely replacing the traditional passive mode that relies on manual verification of drawings. When the comparison result between the actual connection table and the expected connection table deviates (e.g., the motherboard J01 interface reads the identifier value 0xA2, while the expected value should be 0xA1), the system immediately detects the deviation between the physical connection and the design intent, thus proactively intercepting incorrect configurations during startup and avoiding performance degradation, functional abnormalities, or stability risks that may be caused by the system operating in an unexpected state.

[0041] Secondly, it establishes a closed-loop error location and response capability. The actual connection table construction process transforms physical connection relationships into structured data (such as a mapping table), enabling the system to accurately locate specific conflict items. When an inconsistency is detected, the issued connection error alarm not only includes abstract anomaly messages but can also be associated with specific motherboard connector numbers (such as J01) and backplane identifier values ​​(such as 0xA2). Furthermore, the physical location of the faulty connection (such as the JA2 interface) can be deduced through the preset identifier-connector mapping relationship. This reverse tracing mechanism from digital signals to physical entities allows maintenance personnel to directly pinpoint problematic cables without unpacking and inspecting them, reducing the time-consuming manual fault location process of traditional solutions (which takes hours) to minutes, significantly improving maintenance efficiency and reducing downtime losses.

[0042] Finally, the adaptability and deployment reliability of the server system are enhanced. The structured storage design of the expected connection table (such as a two-dimensional table containing connector numbers and identifier values) supports flexible configuration in multiple scenarios. Engineers can preset multiple connection schemes (such as redundant mode or high-speed mode) according to different performance requirements, and the system automatically calls the matching scheme to perform detection. This method transforms human experience into intelligent verification logic built into the system without hardware cost (reusing I2C sideband signals and CPLD resources), significantly reducing the dependence on the skill level of operators. Especially in high-density server cluster deployments, it can effectively avoid the risk of mis-insertion caused by similar connector appearances, ensure the consistency of large-scale assembly, and provide a traceable configuration baseline for later expansion or adjustment.

[0043] Furthermore, in some preferred embodiments, in the CPLD of the backplane, registers are set for the I2C interfaces corresponding to the connectors in the backplane that connect to the motherboard, and the values ​​of each register are configured to the corresponding identifier values.

[0044] In this invention, a register is set in the CPLD on the backplane for the I2C interface corresponding to each connector, and the register value is configured as an identifier value. Specifically, the register can be a read-only register. The technical objective is to provide underlying hardware support for connector identification and ensure the stable execution of the detection process. Since the CPLD is an inherently programmable device on the backplane, storing identifier values ​​in registers gives each backplane connector a unique software-readable identifier (e.g., JA1 corresponds to 0xA1), and this identifier is transmitted to the motherboard via I2C signals after the physical connection is established. This design solves the identification confusion problem caused by the uniform physical appearance of connectors: the identifier value in the register acts as an "electronic tag" and forms a fixed binding relationship with the connector, ensuring that the identifier value read by the BMC can be unambiguously mapped to a specific backplane connector; at the same time, the read-only attribute of the register prevents accidental modification, ensuring the persistent reliability of the identifier.

[0045] Furthermore, in some preferred embodiments, the above step "reading the preset identifier values ​​for each connector on the backplane from the CPLD of the backplane via the I2C interface of each connector on the motherboard" specifically includes the following steps: reading the identifier values ​​in the corresponding registers in the CPLD of the backplane via the I2C interface of each connector on the motherboard.

[0046] This invention explicitly uses the I2C interface to read the identifier value from the CPLD register. The technical objective is to reliably acquire and parse connection information using a standardized interface protocol. I2C, as a mature two-wire serial communication protocol, has electrical characteristics and addressing mechanisms widely supported by server hardware. By directly accessing the backplane CPLD registers through the motherboard's I2C interface, the BMC can efficiently traverse all connector channels (e.g., I2C01 reads the JA1 register, I2C02 reads the JA2 register); the mapping relationship between registers and identifier values ​​(e.g., address 0x01 stores value 0xA1) transforms the read operation into direct decoding of the connector identity.

[0047] Furthermore, in some preferred embodiments, the identifier values ​​corresponding to the connectors in the backplane are all different.

[0048] In this invention, the identifier values ​​corresponding to the backplane connectors must be distinct. The technical objective is to eliminate ambiguity in identification and ensure the accuracy of connection verification. When each backplane connector is assigned a globally unique identifier (e.g., JA1 = 0xA1, JA2 = 0xA2, JB1 = 0xB1), each record in the actual connection table (e.g., J01 → 0xA1) uniquely identifies the backplane connector. During the comparison process, this uniqueness allows the system to accurately locate conflicts: if the expected table requires J01 to connect to JA1 (identifier 0xA1), but the actual table shows J01's read value as 0xA2, then it can be immediately determined that J01 is mistakenly connected to JA2. If the identifiers are duplicated (e.g., JA1 and JA2 are both 0xA1), the actual table will be unable to distinguish the connection target, leading to misjudgment or missed detection.

[0049] Furthermore, in some preferred embodiments, the expected connection table is pre-stored in the motherboard's BMC in the form of a data structure, including the connector numbers of the motherboard, the connector numbers of the backplane, and the corresponding identifier values.

[0050] In this invention, the expected connection table is pre-stored in the BMC in the form of a data structure, containing motherboard / backplane connector numbers and identifier values. The technical objective is to provide a scalable benchmark reference for automated verification, supporting flexible configuration across multiple scenarios. By storing the expected connection table in a structured manner locally on the BMC (such as in firmware or non-volatile memory), the system becomes independent of manual intervention: engineers can configure connection schemes in advance according to design intent, and the BMC directly calls the matching expected table for comparison. The structured data design (such as two-dimensional tables or key-value pairs) facilitates efficient querying and traversal, where the associated fields (such as J01-JA1-A1) of "motherboard connector number - backplane connector number - identifier value" completely cover the mapping relationship between physical connections and logical identifiers.

[0051] Furthermore, in some preferred embodiments, the step "determining whether the actual connection table is consistent with the pre-stored expected connection table" includes: verifying item by item whether the mapping relationship between the motherboard connectors and the backplane connectors in the actual connection table conforms to the expected connection table. If any mapping relationship does not conform, it is determined that the actual connection table is inconsistent with the pre-stored expected connection table; if all mapping relationships conform, it is determined that the actual connection table is consistent with the pre-stored expected connection table.

[0052] This invention determines consistency by verifying the motherboard-backplane connector mapping relationship between the actual and expected tables item by item. The technical objective is to achieve fine-grained error detection and avoid missed detections caused by overall misjudgments. Item-by-item verification (e.g., traversing each record in the expected table and checking whether the same motherboard connector in the actual table is associated with the expected backplane identifier) ​​can accurately identify partial connection errors (e.g., only J01 is incorrectly connected while others are correct). When a verification fails (e.g., the actual value of J01 0xA2 ≠ the expected value 0xA1), the system immediately records the conflict, providing input for generating accurate alarms. Item-by-item verification ensures detection completeness in complex configuration scenarios (e.g., dozens of connectors) and significantly reduces the difficulty of troubleshooting multiple overlapping connection errors.

[0053] Furthermore, in some preferred embodiments, the connection error alarm information includes error location information, which is used to indicate the numbers of the mismatched motherboard connector and the backplane connector.

[0054] In this invention, the connection error alarm includes error location information specifying the mismatched motherboard / backplane connector number. The technical objective is to transform abstract alarms into actionable repair instructions, significantly improving fault repair efficiency. Traditional solutions only indicate "connection abnormality," requiring maintenance personnel to open the package and check each cable individually, which can easily take several hours. This invention, however, requires alarms to include specific conflict items (e.g., "J01 should be connected to JA1, but is actually connected to JA2"), allowing users to directly locate and adjust the problematic cable, reducing repair time to minutes. The error location information is precisely mapped to the physical connector location (e.g., motherboard J01 is located in the third slot, backplane JA2 is marked as a red interface), avoiding secondary manual diagnosis.

[0055] For example, see Figure 2 The server has a total of n PCIe interfaces, corresponding to n connectors. Each connector defines a corresponding I2C interface. For PCIe1, it connects to connector J01 on the motherboard via PCB traces. J01 also has a sideband signal I2C1. The other PCIe, connectors, and I2C interfaces follow the same pattern. Similarly, the connector on the hard drive backplane corresponds to connector JA1, which defines both PCIe and I2C interfaces. I2C is defined as I2CA1, connector JA2 corresponds to I2CA2, and so on.

[0056] There is already a CPLD on the hard drive backplane, and each I2C is processed by the CPLD. A read-only register can be designed for each I2C in the CPLD. The address and value of this register are set to fixed values. For example, the address is uniformly designed as 0x01, the register value corresponding to I2CA1 is set to 0xA1, the register value of I2CA2 is designed to be 0xA2, and so on.

[0057] Similarly, for the hard disk backplane B, a series of read-only registers with address 0x01 are designed, and their values ​​are fixed as 0xB1, 0xB2, and so on.

[0058] When the system is powered on, the BMC reads the CPLD's register at address 0x01 through each I2C bus to obtain the corresponding connection relationship. Then, it compares the obtained connection relationship with the pre-saved connection relationship table. If they match perfectly, it means the connection is correct, and the system enters normal working state. Otherwise, an alarm is generated, indicating that the cable connection relationship is not optimal, and providing specific information about the connection abnormality. The customer is reminded to readjust the cable connection after powering off to avoid abnormal phenomena from occurring again during operation.

[0059] For example, the expected join tables stored in advance are shown in Table 1 below:

[0060]

[0061] Table 1. Expected Join Table

[0062] Upon power-up, the BMC reads data via the I2C interface and constructs the actual connection table as shown in Table 2 below:

[0063]

[0064] Table 2. Actual Connection Table

[0065] By comparing the contents of Table 1 and Table 2, it was found that J01 was connected to JA2 but not to JA1. The connection relationship was not as expected, and the system generated an alarm, prompting the user to power off and make adjustments. This made the assembly of downstream processes more intelligent, reduced the possibility of errors, and made deployment and operation and maintenance more intelligent.

[0066] This invention proposes an intelligent detection method for server cable configuration, comprising: reading preset identifier values ​​for each connector on the backplane from the CPLD of the backplane via the I2C interfaces of each connector on the motherboard; constructing an actual connection table containing the correspondence between the motherboard connectors and the backplane connectors based on the read identifier values; determining whether the actual connection table is consistent with a pre-stored expected connection table; and issuing a connection error alarm message if the actual connection table is inconsistent with the pre-stored expected connection table. This invention has the ability to automatically detect and perceive errors in the physical connection relationship of cables between the backplane and the motherboard, promptly identifying incorrect connection configurations, thereby ensuring that the system operates in the expected state.

[0067] Corresponding to the above-described intelligent detection method for server cable configuration, the present invention also provides an intelligent detection device for server cable configuration. This intelligent detection device for server cable configuration includes a unit for executing the above-described intelligent detection method for server cable configuration, and can be configured in terminals such as desktop computers, tablet computers, and laptops. Specifically, the intelligent detection device for server cable configuration includes:

[0068] The reading unit is used to read the preset identifier values ​​of each connector on the backplane from the CPLD of the backplane through the I2C interface of each connector on the motherboard.

[0069] The construction unit is used to construct an actual connection table containing the correspondence between the connectors of the motherboard and the connectors of the backplane based on the read identifier value;

[0070] The judgment unit is used to determine whether the actual join table is consistent with the pre-stored expected join table;

[0071] The prompting unit is used to issue a connection error alarm message if the actual connection table is inconsistent with the pre-stored expected connection table.

[0072] In some preferred embodiments, in the CPLD of the backplane, registers are set for the I2C interfaces corresponding to the connectors in the backplane that connect to the motherboard, and the values ​​of each register are configured to the corresponding identifier values.

[0073] In some preferred embodiments, the step of reading the preset identifier values ​​for each connector on the backplane from the CPLD via the I2C interface of each connector on the motherboard includes:

[0074] The identifier values ​​in the corresponding registers of the CPLD on the backplane are read through the I2C interfaces of each connector on the motherboard.

[0075] In some preferred embodiments, the identifier values ​​corresponding to the connectors in the backplane are all different.

[0076] In some preferred embodiments, the expected connection table is pre-stored in the motherboard's BMC in the form of a data structure, including the connector numbers of the motherboard, the connector numbers of the backplane, and the corresponding identifier values.

[0077] In some preferred embodiments, determining whether the actual join table matches the pre-stored expected join table includes:

[0078] Verify item by item whether the mapping relationship between the motherboard connectors and the backplane connectors in the actual connection table matches the expected connection table.

[0079] In some preferred embodiments, the connection error alarm information includes error location information, which is used to indicate the numbers of the mismatched motherboard connector and the backplane connector.

[0080] It should be noted that those skilled in the art can clearly understand that the specific implementation process of the intelligent detection device and each unit of the above-mentioned server cable configuration can be referred to the corresponding description in the foregoing method embodiments. For the sake of convenience and brevity, it will not be repeated here.

[0081] The intelligent detection device configured in the aforementioned server cable can be implemented as a computer program, which can, for example... Figure 3 It runs on the computer device shown.

[0082] Please see Figure 3 , Figure 3 This is a schematic block diagram of a computer device provided in an embodiment of this application. The computer device 500 can be a terminal or a server. The terminal can be an electronic device with communication functions, such as a smartphone, tablet, laptop, desktop computer, personal digital assistant, or wearable device. The server can be a standalone server or a server cluster composed of multiple servers.

[0083] The computer device 500 includes a processor 502, a memory, and a network interface 505 connected via a system bus 501. The memory may include a non-volatile storage medium 503 and internal memory 504.

[0084] The non-volatile storage medium 503 may store an operating system 5031 and a computer program 5032. When the computer program 5032 is executed, it causes the processor 502 to perform an intelligent detection method for server cable configuration.

[0085] The processor 502 provides computing and control capabilities to support the operation of the entire computer device 500.

[0086] The internal memory 504 provides an environment for the operation of the computer program 5032 in the non-volatile storage medium 503. When the computer program 5032 is executed by the processor 502, the processor 502 can execute an intelligent detection method for server cable configuration.

[0087] The network interface 505 is used for network communication with other devices. Those skilled in the art will understand that the above structure 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 500 to which the present application is applied. A specific computer device 500 may include more or fewer components than shown in the figures, or combine certain components, or have different component arrangements.

[0088] The processor 502 is used to run a computer program 5032 stored in the memory to perform the following steps:

[0089] By using the I2C interfaces of each connector on the motherboard, the preset identifier values ​​for each connector on the backplane are read from the CPLD of the backplane.

[0090] Based on the read identifier value, construct an actual connection table containing the correspondence between the connectors of the motherboard and the connectors of the backplane;

[0091] Determine whether the actual join table is consistent with the pre-stored expected join table;

[0092] If the actual join table is inconsistent with the pre-stored expected join table, a join error alarm message will be issued.

[0093] In some preferred embodiments, in the CPLD of the backplane, registers are set for the I2C interfaces corresponding to the connectors in the backplane that connect to the motherboard, and the values ​​of each register are configured to the corresponding identifier values.

[0094] In some preferred embodiments, the step of reading the preset identifier values ​​for each connector on the backplane from the CPLD via the I2C interface of each connector on the motherboard includes:

[0095] The identifier values ​​in the corresponding registers of the CPLD on the backplane are read through the I2C interfaces of each connector on the motherboard.

[0096] In some preferred embodiments, the identifier values ​​corresponding to the connectors in the backplane are all different.

[0097] In some preferred embodiments, the expected connection table is pre-stored in the motherboard's BMC in the form of a data structure, including the connector numbers of the motherboard, the connector numbers of the backplane, and the corresponding identifier values.

[0098] In some preferred embodiments, determining whether the actual join table matches the pre-stored expected join table includes:

[0099] Verify item by item whether the mapping relationship between the motherboard connectors and the backplane connectors in the actual connection table matches the expected connection table.

[0100] In some preferred embodiments, the connection error alarm information includes error location information, which is used to indicate the numbers of the mismatched motherboard connector and the backplane connector.

[0101] It should be understood that in the embodiments of this application, the processor 502 may be a central processing unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0102] It will be understood by those skilled in the art 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 may be stored in a storage medium, which is a computer-readable storage medium. The computer program is executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.

[0103] Therefore, the present invention also provides a storage medium. This storage medium can be a computer-readable storage medium. The storage medium stores a computer program. When executed by a processor, the computer program causes the processor to perform the following steps:

[0104] By using the I2C interfaces of each connector on the motherboard, the preset identifier values ​​for each connector on the backplane are read from the CPLD of the backplane.

[0105] Based on the read identifier value, construct an actual connection table containing the correspondence between the connectors of the motherboard and the connectors of the backplane;

[0106] Determine whether the actual join table is consistent with the pre-stored expected join table;

[0107] If the actual join table is inconsistent with the pre-stored expected join table, a join error alarm message will be issued.

[0108] In some preferred embodiments, in the CPLD of the backplane, registers are set for the I2C interfaces corresponding to the connectors in the backplane that connect to the motherboard, and the values ​​of each register are configured to the corresponding identifier values.

[0109] In some preferred embodiments, the step of reading the preset identifier values ​​for each connector on the backplane from the CPLD via the I2C interface of each connector on the motherboard includes:

[0110] The identifier values ​​in the corresponding registers of the CPLD on the backplane are read through the I2C interfaces of each connector on the motherboard.

[0111] In some preferred embodiments, the identifier values ​​corresponding to the connectors in the backplane are all different.

[0112] In some preferred embodiments, the expected connection table is pre-stored in the motherboard's BMC in the form of a data structure, including the connector numbers of the motherboard, the connector numbers of the backplane, and the corresponding identifier values.

[0113] In some preferred embodiments, determining whether the actual join table matches the pre-stored expected join table includes:

[0114] Verify item by item whether the mapping relationship between the motherboard connectors and the backplane connectors in the actual connection table matches the expected connection table.

[0115] In some preferred embodiments, the connection error alarm information includes error location information, which is used to indicate the numbers of the mismatched motherboard connector and the backplane connector.

[0116] The storage medium is a physical, non-transient storage medium, such as a USB flash drive, external hard drive, read-only memory (ROM), magnetic disk, or optical disk, or any other physical storage medium capable of storing program code. The computer-readable storage medium can be non-volatile or volatile.

[0117] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0118] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0119] The steps in the method of this invention can be adjusted, merged, or reduced in order according to actual needs. The units in the device of this invention can be merged, divided, or reduced according to actual needs. Furthermore, the functional units in the various embodiments of this invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0120] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0121] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0122] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Since these modifications and variations fall within the scope of the claims and their equivalents, this invention also intends to include these modifications and variations.

[0123] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for intelligent detection of server cable configuration, characterized in that, include: By using the I2C interfaces of each connector on the motherboard, the preset identifier values ​​for each connector on the backplane are read from the CPLD of the backplane. Based on the read identifier value, construct an actual connection table containing the correspondence between the connectors of the motherboard and the connectors of the backplane; Determine whether the actual join table is consistent with the pre-stored expected join table; If the actual join table is inconsistent with the pre-stored expected join table, a join error alarm message will be issued.

2. The intelligent detection method for server cable configuration according to claim 1, characterized in that, In the CPLD of the backplane, registers are set for the I2C interfaces corresponding to the connectors in the backplane that connect to the motherboard, and the values ​​of each register are configured to the corresponding identifier values.

3. The intelligent detection method for server cable configuration according to claim 2, characterized in that, The step of reading the preset identifier values ​​for each connector on the backplane from the CPLD via the I2C interfaces of each connector on the motherboard includes: The identifier values ​​in the corresponding registers of the CPLD on the backplane are read through the I2C interfaces of each connector on the motherboard.

4. The intelligent detection method for server cable configuration according to claim 3, characterized in that, The identifier values ​​corresponding to the connectors in the backplate are all different.

5. The intelligent detection method for server cable configuration according to claim 1, characterized in that, The expected connection table is pre-stored in the motherboard's BMC in the form of a data structure, which includes the connector numbers of the motherboard, the connector numbers of the backplane, and the corresponding identifier values.

6. The intelligent detection method for server cable configuration according to claim 4, characterized in that, The step of determining whether the actual join table is consistent with the pre-stored expected join table includes: Verify item by item whether the mapping relationship between the motherboard connectors and the backplane connectors in the actual connection table matches the expected connection table.

7. The intelligent detection method for server cable configuration according to claim 1, characterized in that, The connection error alarm information includes error location information, which is used to indicate the numbers of the mismatched motherboard connector and backplane connector.

8. An intelligent detection device for server cable configuration, characterized in that, Includes a unit for performing the method as described in any one of claims 1-7.

9. A computer device, characterized in that, The computer device includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, can implement the method as described in any one of claims 1-7.

Images