Hard disk backboard monitoring method and device of server and electronic equipment

Abstract

The invention provides a hard disk backboard monitoring method for a server, and the method comprises the steps: determining an identifier of the server, the identifier being capable of representing configuration information of the server; based on the identifier of the server, obtaining a to-be-detected data physical link which possibly has a hard board and a back board under the corresponding server configuration information; determining whether the hard disk backboard is in place based on the to-be-detected data physical link; and if the hard disk backplane is in place, determining a hard disk backplane identifier. The invention further provides a hard disk backboard monitoring device of the server and electronic equipment.

Description

Technical Field

[0001] The present application relates to the technical field of hard disk backplanes, and in particular to a hard disk backplane monitoring method of a server, a hard disk backplane monitoring device of a server, and electronic equipment. Background Art

[0002] With the rise of the Internet at home and abroad, the demand for data centers and cloud services has surged, and more powerful computing power is also leading the development trend of the server market. The demand for hard disks on servers has also increased year-on-year, and the demand for the number of hard disk backplanes has also increased simultaneously. A server can be adapted to multiple hard disks, and correspondingly, multiple types of hard disk backplanes are also required. The current identification of hard disk backplanes depends on the FRU information stored in the EEPROM on the backplane. Under normal circumstances, there is an EEPROM on the backplane hardware, and the FRU data can be read normally. However, when the FRU content is not determined in the R&D stage, the FRU data cannot determine the fixed format and content, and the BMC cannot identify the backplane at this stage. Summary of the invention

[0003] The purpose of the embodiments of the present application is to provide a hard disk backplane monitoring method for a server, a hard disk backplane monitoring device for a server, and an electronic device.

[0004] A first aspect of the present application provides a method for monitoring a hard disk backplane of a server, the method comprising:

[0005] Determine an identifier of a server, where the identifier can represent configuration information of the server;

[0006] Based on the identification of the server, obtaining a physical link of data to be detected that may exist on a hardboard backplane corresponding to the server configuration information;

[0007] Determine whether the hard disk backplane is in place based on the physical link of the data to be detected;

[0008] If the hard disk backplane is in place, the hard disk backplane identifier is determined.

[0009] In some embodiments, the method of determining an identity of a server includes:

[0010] Determining a motherboard type of the server based on a first set of editable electrical signal combinations on the server motherboard;

[0011] Determining the host type of the server based on a second set of editable electrical signal combinations on the server motherboard;

[0012] An identification of the server is determined based on the motherboard type and the host type.

[0013] In some embodiments, determining the identification of the server based on the motherboard type and the host type includes:

[0014] Reading a first configuration table pre-stored in the memory, wherein the first configuration table stores a plurality of value pairs formed by a motherboard type, a host type, and a server identifier;

[0015] The mainboard type and the host type are compared with each value pair in the first configuration table, and the server identifier corresponding to the successfully matched value pair is determined as the identifier of the server.

[0016] In some embodiments, the obtaining of a physical link of data to be detected that may exist on a hardboard backplane corresponding to the server configuration information based on the identification of the server includes:

[0017] Determine physical link location information of the hard disk backplane based on the identifier of the server, wherein the physical link location information includes location information of all physical links on which the hard disk backplane may be installed in the correspondingly configured server;

[0018] Wherein, whether the hard disk backplane is in place can be determined based on the physical link position information.

[0019] In some embodiments, the method further comprises:

[0020] In the case where there are multiple pieces of physical link location information, sorting the multiple pieces of physical link location information according to a first rule;

[0021] The determining whether the hard disk backplane is in place based on the physical link position information includes:

[0022] The multiple physical link positions are sorted based on the first rule to determine whether the hard disk backplane is in place.

[0023] In some embodiments, if the hard disk backplane is in place, determining the hard disk backplane identifier includes:

[0024] Reading the model information of the hard disk backplane from the register of the mainboard of the server;

[0025] The model information of the backplane is transcoded to obtain the hard disk backplane model information represented by a character string and use it as the hard disk backplane identifier.

[0026] In some embodiments, the method further comprises:

[0027] The hard disk backplane model information represented by the character string and the hard disk backplane serial number are concatenated, and the concatenated information is used as the hard disk backplane identifier;

[0028] When there are multiple physical link positions determined based on the physical link of the data to be detected, the physical link positions are sorted based on the first rule, and the hard disk backplane serial number corresponds to the sorted serial number.

[0029] In some embodiments, the method further comprises:

[0030] According to the standard FRU format, FRU information including the hard disk backplane identification is constructed so that the hard disk backplane can be identified according to the FRU information.

[0031] A second aspect of the present application provides a hard disk backplane monitoring device for a server, the device comprising:

[0032] A server model determination module, used to determine an identifier of a server, where the identifier can represent configuration information of the server;

[0033] A physical link information acquisition module, based on the server identifier, acquires a physical link of data to be detected that may exist on a hardboard backplane corresponding to the server configuration information;

[0034] A hard disk backplane in-place detection module, which determines whether the hard disk backplane is in place based on the physical link of the data to be detected;

[0035] The hard disk backplane identification determination module determines the hard disk backplane identification if the hard disk backplane is in place.

[0036] A third aspect of the present application provides an electronic device, including:

[0037] A processor and a memory, wherein the memory stores executable instructions, and when the executable instructions are executed by the processor, the electronic device executes any of the methods described above.

[0038] The hard disk backplane monitoring method provided by the present application determines whether the hard disk backplane is in place by determining the server identification and the physical link of the data to be detected. When the hard disk backplane is in place, the hard disk backplane identification is determined. Then, the standard FRU format can be referred to, and the FRU information containing the hard disk backplane identification can be built based on the above backplane identification, and the required data can be displayed on the Dbus to virtualize the FRU information of the backplane. This solves the problem that when the FRU content is not determined in the research and development stage, the FRU data cannot determine the fixed format and content, and the BMC cannot identify the backplane at this stage. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 A flowchart of a method for monitoring a hard disk backplane of a server according to an embodiment of the present application;

[0040] Figure 2 This is a schematic diagram of the structure of a hard disk backplane monitoring device of a server according to an embodiment of the present application.

[0041] Reference numerals:

[0042] 1000, hard disk backplane monitoring device of server; 1001, server model determination module; 1002, physical link information acquisition module; 1003, hard disk backplane in-place detection module; 1004, hard disk backplane identification determination module; 1100, bus; 1200, processor; 1300, memory; 1400, other circuits. DETAILED DESCRIPTION

[0043] Various aspects and features of the present application are described herein with reference to the accompanying drawings.

[0044] It should be understood that various modifications may be made to the embodiments of the present application. Therefore, the above description should not be considered as limiting, but only as an example of an embodiment. Other modifications within the scope and spirit of the present application will occur to those skilled in the art.

[0045] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the present application and, together with the general description of the present application given above and the detailed description of the embodiments given below, serve to explain the principles of the present application.

[0046] These and other characteristics of the present application will become apparent from the following description of a preferred form of embodiment given as a non-limiting example with reference to the accompanying drawings.

[0047] It should also be understood that although the present application has been described with reference to some specific examples, those skilled in the art will be able to readily implement many other equivalent forms of the present application.

[0048] The following is a conceptual explanation of the relationship between the hard disk backplane and the server involved in this application.

[0049] The hard disk backplane is a fixing, plug-in and transmission component of the server hard disk. The server's hard disk is plugged into the hard disk backplane, which is connected to the array card through the SAS link. The array card is divided into HBA card and RAID card or onboard SAS controller. These array cards are plugged into the motherboard and exchange data with the CPU and memory on the motherboard through the PCIe link. The hard disk is plugged into the front end of the backplane. The number of hard disk interface slots on the front side is the number of hard disks that can be plugged in. The back of the backplane has a small number of ports for connecting to SAS or RAID array cards. The hard disk backplane serves as an interface for transferring signals and fixing hard disks. It avoids multi-line connections between the hard disk and the motherboard, making the wiring in the chassis simpler, reducing the degree of obstruction of heat emission in the chassis, and also simplifying the removal and maintenance of the hard disk. The hard disk backplane varies according to the brand model and function. It can be a whole piece or several pieces, and the shapes are also different.

[0050] The server models and backplane models to which the hard disk backplane monitoring method of the present application is applicable are not limited. The hard disk backplane monitoring method of the present application is described below in conjunction with an embodiment.

[0051] Figure 1 A flow chart of a method for monitoring a hard disk backplane of a server according to an embodiment of the present application is shown. Figure 1 As shown, the method includes:

[0052] S101, determining an identifier of a server, where the identifier can represent configuration information of the server;

[0053] S102, based on the identification of the server, obtaining a physical link of data to be detected that may exist on a hardboard backplane under the corresponding server configuration information;

[0054] S103, determining whether the hard disk backplane is in place based on the physical link of the data to be detected;

[0055] S104: If the hard disk backplane is in place, determine the hard disk backplane identifier.

[0056] For ease of understanding, each of the above steps is described separately.

[0057] In the above step S101, the server identifier is determined. The server identifier can represent the configuration information of the server. For example, the configuration information of the server may include a motherboard type and a host type. The motherboard type and the host type of the server can be uniquely determined through the server identifier.

[0058] In the above step S102, the server may be configured with multiple hard disks and correspondingly may have multiple hard disk backplanes. Based on the server identifier, the physical link of the data to be detected that may exist in the hard disk backplane under the corresponding server configuration information is obtained.

[0059] In the above step S103, the hard disk backplane is in place, which means that if the hard disk backplane has been correctly installed in the server, and all necessary connections (such as power lines and data lines) have been correctly connected, it is ensured that the hard disk can work normally. In the S103 step, it is determined whether the hard disk backplane is in place based on the physical link of the data to be detected. Wherein, the physical link of the data to be detected can be an SMBus (System Management Bus) link, or it can be an I2C physical link.

[0060] In the above step S104, when the hard disk backplane is in place, the hard disk backplane identifier can be further determined.

[0061] The hard disk backplane monitoring method provided by the present application determines whether the hard disk backplane is in place by determining the server identification and the physical link of the data to be detected. When the hard disk backplane is in place, the hard disk backplane identification is determined. Then, the standard FRU format can be referred to, and the FRU information containing the hard disk backplane identification can be built based on the above backplane identification, and the required data can be displayed on the Dbus to virtualize the FRU information of the backplane. This solves the problem that when the FRU content is not determined in the research and development stage, the FRU data cannot determine the fixed format and content, and the BMC cannot identify the backplane at this stage.

[0062] In some embodiments, a method of determining an identity of a server includes:

[0063] Determining a motherboard type of the server based on a first set of editable electrical signal combinations on the server motherboard;

[0064] determining a host type of the server based on a second set of editable electrical signal combinations on a server motherboard;

[0065] Determines the identity of the server based on the motherboard type and host type.

[0066] As an example, there are multiple GPIO pins on the server motherboard. In this embodiment, two groups of GPIO pins reserved in advance on the server motherboard can be used to generate editable electrical signals. The electrical signals generated by the first group of GPIO pins can be used to distinguish the type of motherboard, and the second group of GPIO pins can be used to distinguish different models built on the same type of motherboard.

[0067] For example, the first group of GPIOs may be composed of multiple GPIOs. If the number of the first group of GPIOs is 5, the 5 GPIOs are GPIO1, GPIO2, GPIO3, GPIO4, and GPIO5, respectively. The combination of different levels of the 5 GPIO pins will form a set of binary numbers, such as 00001, 00010, 00011, etc. The different values ​​of this group of numbers can be used to distinguish the types of server hardware, such as 00001 for a dual-CPU standard rack server, and 00010 for a 4-CPU standard rack server. Other values ​​can represent other different server types, which will not be repeated here.

[0068] For example, the second group of GPIOs may also be composed of multiple GPIOs. If the number of the second group of GPIOs is 3, the three GPIOs are GPIO6, GPIO7, and GPIO8, respectively. The combination of different levels of the three GPIO pins will also form a group of binary numbers, such as 000, 001, 010, 011, etc. The different values ​​of this group of numbers can be used to distinguish different models built on the same type of motherboard, for example, 000 is a standard rack server and 001 is a storage model.

[0069] The method for determining the identification of the server provided in the present application can determine the hardware configuration information of the server through multiple groups of different editable electrical signals. It should be noted that the present application is not limited to two groups of editable electrical signals, and the number of groups of editable electrical signals can also be increased or decreased accordingly according to other hardware information components of the server.

[0070] In some embodiments, determining the identity of the server based on the motherboard type and the host type includes:

[0071] Reading a first configuration table pre-stored in the memory, the first configuration table storing a plurality of value pairs formed by a motherboard type, a host type, and a server identifier;

[0072] The mainboard type and the host type are compared with each value pair in the first configuration table, and the server identifier corresponding to the successfully matched value pair is determined as the server identifier.

[0073] The baseboard management controller BMC (Baseboard Management Controller) plays an important role. It allows administrators to remotely manage and monitor servers through the network, including reading and updating FRU information. A piece of memory is reserved in advance inside the BMC to store the correspondence between hardware models and product models. As an example, the present application can store the motherboard type, host model and server identification (the server identification is determined by the motherboard type and the host model) through the first configuration table. Specifically, the first configuration table can be used to pre-store the value pairs formed by the motherboard type, host type and server identification, and there are multiple value pairs. Then, according to the currently obtained hardware model and model, traversal matching is performed to determine the configuration type of the current server, and a virtual software ID number is obtained, which can be used as the unique ID number of this product, that is: the motherboard type and host type are compared with each value pair in the first configuration table, and the server identification corresponding to the successfully matched value pair is determined as the server identification.

[0074] Furthermore, if there is no matching server in the first configuration table, that is, when the matching by motherboard type and host type fails, a default server type can be preset as the matching type, for example, the identifier corresponding to the first server in the first configuration table is determined as the matching server identifier.

[0075] In some embodiments, based on the identification of the server, obtaining the physical link of the data to be detected that may exist in the hard board backplane under the corresponding server configuration information includes:

[0076] Determine the physical link location information of the hard disk backplane based on the identification of the server, wherein the physical link location information includes location information of all physical links of the hard disk backplane that may be installed in the corresponding configured server;

[0077] Among them, whether the hard disk backplane is in place can be determined based on the physical link position information.

[0078] SMBus (System Management Bus) is usually used for low-speed communication in mobile PC and desktop PC systems. It controls devices on the motherboard and collects corresponding information through a cheap and powerful bus, which usually consists of two lines. As an example, the physical link can be an SMBus physical link. In addition, the physical link can also be an I2C link.

[0079] In some embodiments, the method further comprises:

[0080] In the case where there are multiple pieces of physical link location information, the multiple pieces of physical link location information are sorted according to a first rule;

[0081] Determine whether the hard disk backplane is in place based on the physical link location information, including:

[0082] Based on the first rule, multiple physical link positions are sorted one by one to determine whether the hard disk backplane is in place.

[0083] As an example, the physical link may be an SMBus physical link, and the backplane position determined by the physical link may be multiple. In the case of multiple physical link positions, they may be sorted by the first rule. After the sorting is completed, the link is scanned in order, that is, the sorted multiple physical link positions are compared with the CPLD address of the hard disk backplane one by one. If the match is successful, it is determined that the hard disk backplane is in place, and the address of the CPLD on the backplane can be scanned to the address. If it is not in place, the address of the CPLD on the backplane will not be scanned. Wherein, CPLD (Complex Programmable Logic Device) is a complex programmable logic device.

[0084] This application can save chip costs, reduce hardware bus usage and layout, and save labor costs and hardware design costs by replacing the eeprom of the FRU with the register of the CPLD.

[0085] In some embodiments, if the hard disk backplane is in place, determining the hard disk backplane identifier includes:

[0086] Read the model information of the hard disk backplane from the register of the server's mainboard;

[0087] The model information of the backplane is transcoded to obtain the hard disk backplane model information represented by a character string and use it as the hard disk backplane identifier.

[0088] As an example, determining the hard disk backplane identification when the backplane is in place may include: first, after scanning the CPLD address on the backplane, read the model information of the hard disk backplane from the register of the server's mainboard according to the register of the CPLD customized by each manufacturer. The model of the hard disk backplane can be represented in hexadecimal form, or in binary form. Then, the hard disk backplane model information represented in hexadecimal or binary is converted into ASCII code, and a group of characters can be obtained, and the content of this group of characters can be used as the unique identification code of the backplane model.

[0089] In some embodiments, the method further comprises:

[0090] The hard disk backplane model information represented by the character string and the hard disk backplane serial number are concatenated, and the concatenated information is used as the hard disk backplane identifier;

[0091] When there are multiple physical link positions determined based on the physical link of the data to be detected, the physical link positions are sorted based on the first rule, and the hard disk backplane serial number corresponds to the sorted serial number.

[0092] For ease of understanding, the embodiment is further described. Since a server can have multiple identical backplanes, it is impossible to distinguish multiple backplanes of the same model simply by the backplane model. Backplanes of the same model can be numbered, and the hard disk backplane serial number formed by the numbering and the backplane model are combined as a unique identifier for identifying the hard disk backplane.

[0093] Furthermore, if there are multiple physical link positions determined based on the physical link of the data to be detected, the physical link positions are sorted based on the first rule, and the hard disk backplane serial number corresponds to the serial number sorted by the first rule, that is, the hard disk backplane serial number can be the same as the sorting serial number of the physical link position performed by the first rule, or it can be different, but it needs to correspond one-to-one with the sorting serial number of the physical link position performed by the first rule. The physical link positions that all hard disk backplanes are allowed to access, that is, it is determined on which SMBUS links the CPLD of the backplane may appear, and the physical link information that may appear is sorted according to the bus order according to the first rule. The first rule can be, for example, a sorting rule from small to large.

[0094] In some embodiments, the method further comprises:

[0095] According to the standard FRU format, FRU information including the hard disk backplane identification is constructed so that the hard disk backplane can be identified according to the FRU information.

[0096] FRU information is usually stored in the electrically erasable programmable read-only memory (EEPROM) on the server motherboard. This data includes key information such as manufacturer, product model, product serial number, and asset serial number, providing manufacturers and customers with a convenient means of asset information management. However, since the FRU content is not determined during the research and development phase, the FRU data cannot determine a fixed format and content, and the BMC cannot identify the backplane at this stage. The present application can construct FRU information containing the hard disk backplane identification in accordance with the standard FRU format, so that the backplane identification information can be identified or read by other devices or services.

[0097] The hard disk backplane monitoring method provided by the present application can refer to the standard FRU format, build FRU information containing the hard disk backplane identification, display the required data on Dbus, and virtualize the FRU information of the backplane. The FRU content of the prior art needs to be manually flashed, and there will be situations where the FRU is missed or the wrong FRU is flashed. When an abnormal situation occurs, the content of the backplane FRU is incorrect, and there will be a risk of BMC recognition error or failure to recognize it. The FRU information constructed by the present application does not need to be manually flashed, reducing the risk of human error.

[0098] The FRU information constructed by the method provided in the present application is virtual FRU information and can be used to monitor the hard disk backplane. The following is an exemplary method for backplane monitoring based on the above FRU information.

[0099] When the virtual FRU information of the backplane is displayed on the Dbus, according to the communication mechanism of the Dbus, it will notify all related services on the Dbus, and the FRU monitoring instantiation service is also one of the related services. The FRU monitoring instance service usually refers to the monitoring of hardware resources, such as the hard disk, memory, power supply, temperature and other hardware status monitoring on the server.

[0100] This application can monitor the hard disk backplane through the FRU monitoring instantiation service, and preset some configuration files or information for the FRU monitoring instantiation service, which can include configuration files of various types of backplanes, and the configuration file content contains the string ASCII code of the backplane type. Among them, the configuration file can be organized in json format or in other formats.

[0101] When the information data content notified by Dbus is matched with the backplane data in the hard disk backplane configuration file, if the same data is found, it can be determined that the match is successful.

[0102] After the match is successful, on the one hand, the backplane serial number and I2C Bus information in the backplane virtual FRU information are read out, and on the other hand, the custom data in the backplane json configuration file is read out. The custom data can be, for example: the number of hard disks supported by the backplane, the backplane CPLD refresh address, the interface type supported by the backplane, the mux information on the backplane, etc. All the backplane information is displayed on the Dbus, and the backplane identification is completed.

[0103] Dbus has all the information of the identified backplane, and the serial number of the backplane is consistent or corresponds to the hardware I2C link sequence. At the same time, the FRU monitoring instantiation service on Dbus successfully receives the information that the backplane identification is completed, and the cyclic monitoring can be started.

[0104] Figure 2 A schematic diagram of the structure of a hard disk backplane monitoring device of a server according to an embodiment of the present application is shown. Figure 2 As shown, the hard disk backplane monitoring device 1000 may include:

[0105] A server model determination module 1001 is used to determine an identifier of a server, where the identifier can represent configuration information of the server;

[0106] The physical link information acquisition module 1002 acquires the physical link of the data to be detected that may exist in the hard board backplane under the corresponding server configuration information based on the server identifier;

[0107] A hard disk backplane in-place detection module 1003 determines whether the hard disk backplane is in place based on the physical link of the data to be detected;

[0108] The hard disk backplane identification determination module 1004 determines the hard disk backplane identification if the hard disk backplane is in place.

[0109] It should be noted that the implementation details of each module of the hard disk backplane monitoring device of the server provided in the present application correspond to the hard disk backplane monitoring method of the server provided in the present application, and will not be repeated here one by one.

[0110] An electronic device according to at least one embodiment of the present application includes:

[0111] A processor and a memory, wherein the memory stores executable instructions. When the executable instructions are executed by the processor, the electronic device executes any of the above-mentioned methods for monitoring the hard disk backplane of the server.

[0112] The memory storage medium stores executable instructions, and the above method is implemented when the executable instructions are executed by the processor. The method described in the above embodiments can be implemented in whole or in part by software, hardware, firmware or any combination thereof. If implemented in software, the function can be stored as one or more instructions or codes on a computer-readable medium or transmitted on a computer-readable medium. Computer-readable media can include computer storage media and communication media, and can also include any medium that can transfer a computer program from one place to another. The storage medium can be any target medium that can be accessed by a computer.

[0113] In one possible implementation, the memory may include RAM, ROM, compact disc read-only memory (CD-ROM) or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that is intended to carry or store the required program code in the form of instructions or data structures and can be accessed by the computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave), the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of the medium. Disks and optical disks as used herein include optical disks, laser disks, optical disks, digital versatile disks (DVD), floppy disks and Blu-ray disks, where disks usually reproduce data magnetically, while optical disks reproduce data optically using lasers. The combination of the above should also be included in the scope of computer-readable media.

[0114] Figure 2 An example diagram of an apparatus using a hardware implementation of a processing system is shown. The apparatus may include a corresponding module for performing each or several steps in the above flowchart. Therefore, each step or several steps in the above flowchart may be performed by a corresponding module, and the apparatus may include one or more modules in these modules. The module may be one or more hardware modules specifically configured to perform the corresponding steps, or implemented by a processor configured to perform the corresponding steps, or stored in a computer-readable medium for implementation by a processor, or implemented by some combination.

[0115] The hardware structure can be implemented using a bus architecture. The bus architecture can include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the hardware. The bus 1100 connects various circuits including one or more processors 1200, memory 1300, and / or hardware modules together. The bus 1100 can also connect various other circuits 1400 such as peripherals, voltage regulators, power management circuits, external antennas, etc.

[0116] The bus 1100 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Component (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the figure only uses one connecting line, but does not mean that there is only one bus or one type of bus.

[0117] The processor 1200 may be a general purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof. The general purpose processor may be a microprocessor or any conventional processor.

[0118] Any process or method description in the flowchart or otherwise described herein can be understood as a module, fragment or portion of a code representing one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present application includes other implementations, in which the functions may not be performed in the order shown or discussed, including performing the functions in a substantially simultaneous manner or in a reverse order according to the functions involved, which should be understood by a person skilled in the art of the technical field to which the embodiments of the present application belong. The processor performs the various methods and processes described above. For example, the method implementation in the present application can be implemented as a software program, which is tangibly contained in a machine-readable medium, such as a memory. In some embodiments, part or all of the software program can be loaded and / or installed via a memory and / or a communication interface. When the software program is loaded into the memory and executed by the processor, one or more steps in the method described above can be performed. Alternatively, in other embodiments, the processor can be configured to perform one of the above methods in any other appropriate manner (e.g., by means of firmware).

[0119] The logic and / or steps represented in the flowchart or otherwise described herein may be embodied in any readable storage medium for use by an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processor, or other system that can fetch instructions from and execute instructions on an instruction execution system, apparatus, or device), or in combination with such instruction execution systems, apparatuses, or devices.

[0120] For the purposes of this specification, a "readable storage medium" may be any device that can contain, store, communicate, propagate or transmit a program for use with or in conjunction with an instruction execution system, device or apparatus. More specific examples of readable storage media (a non-exhaustive list) include the following: an electrical connection with one or more wirings (electronic device), a portable computer disk case (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and editable read-only memory (EPROM or flash memory), a fiber optic device, and a portable read-only memory (CDROM). In addition, the readable storage medium may even be paper or other suitable medium on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, deciphering or, if necessary, processing in another suitable manner, and then stored in a memory.

[0121] It should be understood that the various parts of the present application can be implemented by hardware, software or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented by software stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0122] A person skilled in the art may understand that all or part of the steps of implementing the above-mentioned implementation method may be completed by instructing related hardware through a program, and the program may be stored in a readable storage medium, which, when executed, includes one or a combination of the steps of the implementation method.

[0123] In addition, each functional unit in each embodiment of the present application may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a readable storage medium. The storage medium may be a read-only memory, a disk or an optical disk, etc.

[0124] In the description of this specification, the description with reference to the terms "one embodiment / method", "some embodiments / methods", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment / method or example are included in at least one embodiment / method or example of the present application. In this specification, the schematic representations of the above terms are not necessarily the same embodiment / method or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments / methods or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments / methods or examples described in this specification and the features of the different embodiments / methods or examples, unless they are contradictory.

[0125] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0126] Those skilled in the art should understand that the above embodiments are only for the purpose of clearly illustrating the present application, and are not intended to limit the scope of the present application. For those skilled in the art, other changes or modifications may be made based on the above disclosure, and these changes or modifications are still within the scope of the present application.

Claims

1. A method for monitoring a hard disk backplane of a server, the method comprising: Determine an identifier of a server, where the identifier can represent configuration information of the server; Based on the identification of the server, obtaining a physical link of data to be detected that may exist on a hardboard backplane corresponding to the server configuration information; Determine whether the hard disk backplane is in place based on the physical link of the data to be detected; If the hard disk backplane is in place, the hard disk backplane identifier is determined.

2. The method according to claim 1, wherein the method for determining the identity of the server comprises: Determining a mainboard type of the server based on a first set of editable electrical signal combinations on the mainboard of the server; Determining the host type of the server based on a second set of editable electrical signal combinations on the server motherboard; An identification of the server is determined based on the motherboard type and the host type.

3. The method according to claim 2, wherein determining the identification of the server based on the motherboard type and the host type comprises: Reading a first configuration table pre-stored in the memory, wherein the first configuration table stores a plurality of value pairs formed by a motherboard type, a host type, and a server identifier; The mainboard type and the host type are compared with each value pair in the first configuration table, and the server identifier corresponding to the successfully matched value pair is determined as the identifier of the server.

4. The method according to claim 1, wherein the step of obtaining the physical link of the data to be detected that may have a hardboard backplane corresponding to the server configuration information based on the server identification comprises: Determine physical link location information of the hard disk backplane based on the identifier of the server, wherein the physical link location information includes location information of all physical links on which the hard disk backplane may be installed in the correspondingly configured server; Wherein, whether the hard disk backplane is in place can be determined based on the physical link position information.

5. The method according to claim 4, further comprising: In the case where there are multiple pieces of physical link location information, sorting the multiple pieces of physical link location information according to a first rule; The determining whether the hard disk backplane is in place based on the physical link position information includes: The multiple physical link positions are sorted based on the first rule to determine whether the hard disk backplane is in place.

6. The method according to claim 1, if the hard disk backplane is in place, determining the hard disk backplane identifier comprises: Reading the model information of the hard disk backplane from the register of the mainboard of the server; The model information of the backplane is transcoded to obtain the hard disk backplane model information represented by a character string and use it as the hard disk backplane identifier.

7. The method according to claim 6, further comprising: The hard disk backplane model information represented by the character string and the hard disk backplane serial number are concatenated, and the concatenated information is used as the hard disk backplane identifier; When there are multiple physical link positions determined based on the physical link of the data to be detected, the physical link positions are sorted based on the first rule, and the hard disk backplane serial number corresponds to the sorted serial number.

8. The method according to any one of claims 1 to 7, further comprising: According to the standard FRU format, FRU information including the hard disk backplane identification is constructed so that the hard disk backplane can be identified according to the FRU information.

9. A hard disk backplane monitoring device for a server, the device comprising: A server model determination module, used to determine an identifier of a server, where the identifier can represent configuration information of the server; A physical link information acquisition module, based on the server identifier, acquires a physical link of data to be detected that may exist on a hardboard backplane corresponding to the server configuration information; A hard disk backplane in-place detection module, which determines whether the hard disk backplane is in place based on the physical link of the data to be detected; The hard disk backplane identification determination module determines the hard disk backplane identification if the hard disk backplane is in place.

10. An electronic device, characterized in that: include: A processor and a memory, wherein the memory stores executable instructions, and when the executable instructions are executed by the processor, the electronic device executes the method according to any one of claims 1 to 8.

Images