Asset information acquisition method and device, server, electronic device, and medium

Abstract

The present disclosure provides a kind of asset information acquisition method and device, server, electronic equipment and medium, the detection of each slot in server, it is judged whether each slot exists expansion connection;When determining that there is expansion connection, in situ detection is carried out to the physical equipment in target slot, and the in situ information table of target slot is generated;The asset information of physical equipment is acquired, and the in situ information table is compared with asset information, and the acquisition mode of the target asset information of physical equipment is determined based on the comparison result;According to the acquisition mode of target asset information, the target asset information of physical equipment is acquired.Compared with the related art, the present disclosure can dynamically identify and adapt to different hardware configurations, including direct connection devices and devices under expansion card / acceleration card. Through accurate in situ detection, the system can accurately determine the presence state of the physical device on each slot. The most suitable asset information acquisition mode can be selected according to the actual connection condition of the device.

Description

Technical Field

[0001] This disclosure relates to the field of server technology, and in particular to a method and apparatus for acquiring asset information, a server, electronic equipment, and a medium. Background Technology

[0002] In the field of server hardware management, Peripheral Component Interconnect Express (PCIe) devices and their associated expansion cards have become core components of data centers and cloud computing due to their high performance and scalability. In traditional direct-connect mode, the Basic Input / Output System (BIOS) can obtain asset information such as the physical location, firmware version, part number (PN), serial number (SN), and bandwidth of the device through the standard PCIe scanning mechanism. However, when a device is connected through an expansion card, its virtualization layer or proprietary driver blocks direct access to the underlying physical device, preventing the BIOS from penetrating the abstraction layer to identify the device connected to the expansion card. Therefore, how to obtain the asset information of the device connected to the expansion card has become a pressing issue. Summary of the Invention

[0003] This disclosure provides a method, apparatus, electronic device, and storage medium for acquiring asset information. Its main purpose is to solve the problem of being unable to acquire asset information of physical devices connected to an expansion card.

[0004] According to a first aspect of this disclosure, a method for obtaining asset information is provided, comprising:

[0005] The baseboard management controller obtains the in-situ status information of the physical devices connected to each slot in the server, and generates an in-situ information table of the physical devices based on the obtained in-situ status information.

[0006] The baseboard management controller obtains asset information sent by the basic input / output system and compares the information in the in-situ information table with the asset information to determine whether the physical device is the target device on the accelerator card.

[0007] When a target device on an accelerator card is identified, the baseboard management controller determines the target asset information acquisition method based on the information comparison results, and acquires the target asset information of the target device according to the target asset information acquisition method.

[0008] Optional physical devices include: hard disk devices and slot devices;

[0009] The baseboard management controller acquires the presence status information of the physical devices connected to each slot in the server, including:

[0010] The baseboard management controller acquires the in-situ status information of the slot devices stored in the expander;

[0011] The baseboard management controller acquires the on-site status information of the hard disk devices in the hard disk backplane.

[0012] Optionally, before the substrate management controller obtains the presence information of the acceleration slot device stored in the expander, the method further includes:

[0013] The motherboard controller detects the presence of each slot in the server and stores the detected presence status information in the expander.

[0014] Optionally, the expanders include: a first motherboard expander, a second motherboard expander, and an accelerator card expander; the slot devices include motherboard devices and accelerator slot devices;

[0015] The motherboard controller performs presence detection on each slot in the server and stores the detected presence status information to the expander, including:

[0016] The motherboard controller scans the server's motherboard slots and stores the detected accelerator card presence status and accelerator card type in the first motherboard expander;

[0017] The motherboard controller scans the motherboard devices in the motherboard slots of the server and writes the presence status information of the detected motherboard devices into the second motherboard expander;

[0018] The motherboard controller scans the acceleration slot devices on the accelerator card, and stores the presence status information of the detected acceleration slot devices in the accelerator card expander.

[0019] Optionally, the baseboard management controller acquires the in-situ status information of the slot devices stored in the expander, including:

[0020] The baseboard management controller obtains the presence status information of the motherboard devices on the motherboard slots in the server from the second motherboard expander;

[0021] The baseboard management controller obtains the accelerator card's presence status information and accelerator card type from the first motherboard expander;

[0022] The baseboard management controller traverses a preset relationship table based on the accelerator card type to determine the presence status information of the accelerator slot device in the accelerator card.

[0023] Optionally, the baseboard management controller acquires the presence status information of the hard disk device in the hard disk backplane, including:

[0024] The basic management controller reads the topology information of the hard drive backplane;

[0025] The basic management controller accesses the hard drive backplane based on topology information to obtain the on-site status information of the hard drive devices.

[0026] Optionally, based on the acquired in-situ status information, an in-situ information table for physical devices is generated, including:

[0027] The baseboard management controller integrates the acquired on-site status information of the motherboard devices and acceleration slot devices.

[0028] The baseboard management controller constructs a table based on the identity identifiers of the motherboard devices and acceleration slot devices, and generates an in-situ information table.

[0029] Optionally, the baseboard management controller acquires asset information sent by the basic input / output system, including:

[0030] The baseboard management controller listens to the preset transmission interface to obtain asset information in a preset format sent by the basic input / output system;

[0031] The baseboard management controller parses the asset information in a preset format and extracts the asset information.

[0032] Optionally, before comparing the location information table with the asset information, the method may also include:

[0033] The baseboard management controller converts the received asset information into a system-side presence information table.

[0034] Optionally, the location information table will be compared with the asset information to determine whether the physical device is the target device on the accelerator card, including:

[0035] Compare the system-side presence information table with the presence information table;

[0036] If the physical device exists in the in-situ information table but does not exist in the system-side in-situ information table, then the physical device is determined to be the target device on the accelerator card.

[0037] Optionally, the baseboard management controller determines the method for obtaining the target asset information of the target device based on the information comparison results, including:

[0038] If the target device is a slot device, verify whether the slot device is the target physical device, and determine the method for obtaining the target asset information of the slot device based on the verification result;

[0039] If the target device is a hard disk device, the method for obtaining the target asset information of the hard disk device is determined based on whether the basic input / output system has sent asset information.

[0040] Optionally, verify whether the slot device is the target physical device, and determine the method for obtaining the target asset information of the slot device based on the verification result, including:

[0041] If it is determined that the slot device is in place and the basic input / output system has sent asset information, verify whether the slot device is the target physical device.

[0042] If it is a target physical device, then the target asset information is obtained through the baseboard management controller;

[0043] If it is not the target physical device, then the target asset information is obtained through the basic input / output system.

[0044] Optionally, depending on whether the basic input / output system has sent asset information, the method for obtaining the target asset information of the hard disk device is determined, including:

[0045] If the hard disk device is confirmed to be in place and the basic input / output system has sent asset information, the target asset information is obtained through the basic input / output system.

[0046] If the hard disk device is confirmed to be in place and the basic input / output system has not sent asset information, the target asset information is obtained through the baseboard management controller.

[0047] Optionally, according to the target asset information acquisition method, the target asset information of the target equipment is acquired, including:

[0048] If the target device is a target physical device, the baseboard management controller obtains the target module information of the target physical device;

[0049] The baseboard management controller obtains basic information about the target module stored in the basic input / output system, and generates target asset information based on the basic information and the target module information.

[0050] Optionally, obtaining the target asset information of the target equipment according to the target asset information acquisition method also includes:

[0051] If the target device is a hard disk device, then based on the source identifier of the hard disk device, look up the offset source mapping table to obtain the asset identifier data;

[0052] The asset identification data is parsed to generate target asset information.

[0053] According to a second aspect of this disclosure, a server for acquiring asset information is provided, comprising: a baseboard management controller, a controller unit, an extender unit, and an interface connection unit;

[0054] The controller unit includes a first controller, which is connected to the expander unit and the baseboard management controller. The first controller performs presence detection on each slot in the server motherboard and stores the detected presence status information in the expander unit. In response to the acquisition command of the baseboard management controller, the first controller sends the presence status information to the baseboard management controller.

[0055] The baseboard management controller is connected to the interface connection unit, which in turn is connected to the hard disk device on the hard disk backplane to obtain the on-site status information of the hard disk device.

[0056] Optionally, the controller unit may further include: a second controller;

[0057] The second controller is connected to the interface connection unit.

[0058] Optionally, the server may also include: multiple multiplexers;

[0059] Multiple multiplexers are installed on the link connecting the baseboard management controller and the interface connection unit, and on the link connecting the interface connection unit and the second controller and the hard disk device.

[0060] Optionally, the expander unit includes: a first motherboard expander, a second motherboard expander, and an accelerator card expander;

[0061] The first motherboard expander and the second motherboard expander are mounted on the server motherboard and are connected to the first controller, respectively; the accelerator card expander is mounted on the accelerator card and is connected to the first controller.

[0062] According to a third aspect of this disclosure, an apparatus for acquiring asset information is provided, comprising:

[0063] The generation unit is used by the baseboard management controller to obtain the on-site status information of the physical devices connected to each slot in the server, and to generate an on-site information table of the physical devices based on the obtained on-site status information.

[0064] The comparison unit is used by the baseboard management controller to obtain asset information sent by the basic input / output system, compare the in-situ information table with the asset information, and determine whether the physical device is the target device on the accelerator card.

[0065] The acquisition unit is used to determine the target asset information acquisition method of the target device based on the information comparison result when the target device is identified as a target device on the accelerator card, and to acquire the target asset information of the target device according to the target asset information acquisition method.

[0066] Optional physical devices include: hard disk devices and slot devices;

[0067] The generation unit includes:

[0068] The first acquisition module is used by the baseboard management controller to acquire the in-situ status information of the slot devices stored in the expander;

[0069] The second acquisition module is used by the baseboard management controller to acquire the on-site status information of the hard disk device in the hard disk backplane.

[0070] Optionally, the asset information acquisition device also includes:

[0071] The detection unit is used to detect the presence of each slot in the server before the motherboard controller obtains the presence information of the acceleration slot devices stored in the expander, and stores the detected presence status information in the expander.

[0072] Optionally, the expanders include: a first motherboard expander, a second motherboard expander, and an accelerator card expander; the slot devices include motherboard devices and accelerator slot devices;

[0073] The detection unit includes:

[0074] The first detection module is used by the motherboard controller to scan the motherboard slots of the server and store the detected accelerator card presence status and accelerator card type in the first motherboard expander.

[0075] The second detection module is used by the motherboard controller to scan the motherboard devices on the motherboard slots in the server and write the presence status information of the detected motherboard devices into the second motherboard expander.

[0076] The third detection module is used by the motherboard controller to scan the acceleration slot devices on the accelerator card, and store the on-site status information of the detected acceleration slot devices in the accelerator card expander.

[0077] Optionally, the first acquisition module is also used for:

[0078] The baseboard management controller obtains the presence status information of the motherboard devices on the motherboard slots in the server from the second motherboard expander;

[0079] The baseboard management controller obtains the accelerator card's presence status information and accelerator card type from the first motherboard expander;

[0080] The baseboard management controller traverses a preset relationship table based on the accelerator card type to determine the presence status information of the accelerator slot device in the accelerator card.

[0081] Optionally, the second acquisition module is also used for:

[0082] The basic management controller reads the topology information of the hard drive backplane;

[0083] The basic management controller accesses the hard drive backplane based on topology information to obtain the on-site status information of the hard drive devices.

[0084] Optionally, the generation unit may also include:

[0085] The integration module is used by the baseboard management controller to integrate the acquired on-site status information of the motherboard devices and the acceleration slot devices.

[0086] The generation module is used by the baseboard management controller to construct a table based on the identity identifiers of the motherboard devices and acceleration slot devices, and generate an in-situ information table.

[0087] Optionally, the comparison unit includes:

[0088] The acquisition module is used by the baseboard management controller to listen to the preset transmission interface and acquire asset information in a preset format sent by the basic input / output system;

[0089] The extraction module is used by the baseboard management controller to parse asset information in a preset format and extract the asset information.

[0090] Optionally, the asset information acquisition device also includes:

[0091] The conversion unit is used to convert the received asset information into a system-side presence information table before comparing the presence information table with the asset information.

[0092] Optionally, the comparison unit may also include:

[0093] The comparison module is used to compare the system-side presence information table with the presence information table.

[0094] The first determining module is used to determine that if the physical device exists in the in-situ information table but does not exist in the in-situ information table on the system side, then the physical device is the target device on the accelerator card.

[0095] Optionally, the acquisition unit includes:

[0096] The second determining module is used to verify whether the slot device is the target physical device if the target device is a slot device, and to determine the method of obtaining the target asset information of the slot device based on the verification result.

[0097] The third determination module is used to determine the method of obtaining the target asset information of the hard disk device based on whether the basic input / output system has sent asset information if the target device is a hard disk device.

[0098] Optionally, the second determining module is also used for:

[0099] If it is determined that the slot device is in place and the basic input / output system has sent asset information, verify whether the slot device is the target physical device.

[0100] If it is a target physical device, then the target asset information is obtained through the baseboard management controller;

[0101] If it is not the target physical device, then the target asset information is obtained through the basic input / output system.

[0102] Optionally, the third determining module is also used for:

[0103] If the hard disk device is confirmed to be in place and the basic input / output system has sent asset information, the target asset information is obtained through the basic input / output system.

[0104] If the hard disk device is confirmed to be in place and the basic input / output system has not sent asset information, the target asset information is obtained through the baseboard management controller.

[0105] Optionally, the acquisition unit includes:

[0106] The first acquisition module is used to acquire the target module information of the target physical device if the target device is a target physical device;

[0107] The baseboard management controller obtains basic information about the target module stored in the basic input / output system, and generates target asset information based on the basic information and the target module information.

[0108] Optionally, the acquisition unit may also include:

[0109] The second acquisition module is used to look up the offset source mapping table and obtain asset identification data based on the source identifier of the hard disk device if the target device is a hard disk device.

[0110] The asset identification data is parsed to generate target asset information.

[0111] According to a fourth aspect of this disclosure, an electronic device is provided, comprising:

[0112] At least one processor; and

[0113] A memory communicatively connected to the at least one processor; wherein,

[0114] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the asset information acquisition method described in the first aspect above.

[0115] According to a fifth aspect of this disclosure, a non-transitory computer-readable storage medium is provided storing computer instructions, wherein the computer instructions are used to cause the computer to perform the asset information acquisition method described in the first aspect above.

[0116] According to a sixth aspect of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the method for acquiring asset information as described in the first aspect above.

[0117] This disclosure provides a method, apparatus, server, electronic device, and medium for acquiring asset information, relating to the field of server technology. By comprehensively detecting the expansion connections of slots, the system can dynamically identify and adapt to different hardware configurations, including directly connected devices and devices connected to expansion cards / accelerator cards. Through precise presence detection, the system can accurately determine the presence status of physical devices in each slot. The generation of the presence information table provides reliable basic data for subsequent asset information acquisition and management, ensuring stable system operation. It can select the most suitable asset information acquisition method based on the actual connection status of the devices and the asset information sent by the BIOS. This dynamic allocation mechanism not only improves the accuracy and efficiency of asset information acquisition but also reduces unnecessary system overhead and improves overall management efficiency.

[0118] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0119] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein:

[0120] Figure 1 A flowchart illustrating a method for obtaining asset information provided in an embodiment of this disclosure;

[0121] Figure 2 A flowchart illustrating another method for obtaining asset information provided in this embodiment of the disclosure;

[0122] Figure 3 A schematic diagram of the structure of a server for acquiring asset information provided in an embodiment of this disclosure;

[0123] Figure 4 This is a schematic diagram of the structure of an asset information acquisition device provided in an embodiment of the present disclosure. Detailed Implementation

[0124] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0125] The following description, with reference to the accompanying drawings, outlines a method, apparatus, server, electronic device, and medium for acquiring asset information according to embodiments of this disclosure.

[0126] Figure 1This is a flowchart illustrating a method for obtaining asset information provided in an embodiment of this disclosure.

[0127] like Figure 1 As shown, the method includes the following steps:

[0128] Step 101: The baseboard management controller obtains the in-situ status information of the physical devices connected to each slot in the server, and generates an in-situ information table of the physical devices based on the obtained in-situ status information.

[0129] In the embodiments of this disclosure, the Baseboard Management Controller (BMC), as the core management component, is responsible for monitoring and managing various hardware resources within the server. The BMC communicates with various slots on the server motherboard through its built-in hardware monitoring interface. These slots may be directly connected to various physical devices, such as, but not limited to, PCIe devices (including NVMe SSDs, GPUs, FPGAs, etc.), network interface cards (NICs), and other expansion cards or accelerator cards. The BMC uses standard communication protocols (such as I2C, SMBus, etc.) or proprietary management interfaces to scan these slots one by one to obtain the presence status information of the physical devices currently connected to each slot.

[0130] In acquiring presence status information, the BMC may employ various detection mechanisms, including but not limited to electrical characteristic detection (such as monitoring slot level changes and current consumption), device identifier reading (such as confirming device presence by reading the device's unique identifier or serial number), and response signal detection (such as presence signals sent by the device through specific pins). These mechanisms ensure that the BMC can accurately and reliably determine whether a physical device is connected to each slot and identify the device's type or basic attributes.

[0131] Based on the availability information obtained from each slot, the BMC further processes this information to generate a detailed physical device availability table. This availability table not only records whether a device is connected to each slot, but may also include the device type, model, serial number, and other key information that helps with system management and maintenance. Through this availability table, the baseboard management controller can intuitively "understand" the configuration of the server's internal hardware resources, including which slots are occupied and what types of devices are connected.

[0132] By automating on-premises status detection and information aggregation, BMC simplifies the management process of server hardware resources, reduces the need for manual intervention, and improves management efficiency.

[0133] Step 102: The baseboard management controller obtains the asset information sent by the basic input / output system, compares the information in the in-situ information table with the asset information, and determines whether the physical device is the target device on the accelerator card.

[0134] In embodiments of this disclosure, the Baseboard Management Controller (BMC) works in conjunction with the Basic Input / Output System (BIOS) to enable comprehensive monitoring and management of the server's internal hardware resources.

[0135] After collecting the presence status information of the physical devices connected to each slot in the server and generating a physical device presence information table, the Baseboard Management Controller (BMC) further interacts with the Basic Input / Output System (BIOS). The BIOS, as the initialization software during server startup, is responsible for the initial hardware configuration and detection, and can collect detailed asset information about the connected hardware devices, including but not limited to device model, firmware version, serial number, and manufacturer.

[0136] The BMC establishes a connection with the BIOS through a pre-defined communication interface (such as the Redfish interface, a RESTful hardware management interface standard) and requests the asset information collected by the BIOS. Upon receiving the request, the BIOS sends the collected asset information to the BMC in a structured data format (such as JSON). After receiving the asset information from the BIOS, the BMC compares this information with the previously generated physical device availability table. The comparison process mainly includes: first, matching the slot identifier in the availability table with the device location information in the asset information to confirm whether each available device corresponds to asset information; second, for successfully matched devices, further comparing key information such as device model and serial number to verify the device's authenticity and consistency; finally, for specific application scenarios (such as server architectures supporting accelerator cards), the BMC also needs to specifically determine whether the physical device is the target device connected to the accelerator card, which typically involves a comprehensive judgment of information such as device type, functional characteristics, and connection location on the accelerator card.

[0137] Step 103: When the target device is determined to be on the accelerator card, the baseboard management controller determines the target asset information acquisition method of the target device based on the information comparison result, and acquires the target asset information of the target device according to the target asset information acquisition method.

[0138] In the embodiments of this disclosure, after the Baseboard Management Controller (BMC) confirms through information comparison that a certain physical device is a target device connected to the accelerator card, it needs to further determine the asset information acquisition method of the target device and obtain the corresponding target asset information accordingly.

[0139] After comparing the asset information sent by the BIOS with that of the physical device and confirming that the device is the target device on the accelerator card, the Baseboard Management Controller (BMC) dynamically determines the optimal method for acquiring asset information for the target device based on the comparison results and preset policies or rule bases. This decision-making process may consider multiple factors, including but not limited to the type of device (such as NVMe SSD, GPU, FPGA, etc.), the specific design of the accelerator card (such as whether it supports hot-swapping, whether it has a proprietary management interface, etc.), and the current system environment (such as operating system type, management software version, etc.).

[0140] The asset information acquisition methods determined by the BMC may include, but are not limited to, the following: Direct communication acquisition: For devices that support standard management interfaces (such as IPMI, REDFISH, etc.), the BMC can directly communicate with the device through these interfaces to obtain detailed asset information. Acquisition through the BIOS interface: For devices connected to the accelerator card, if the BIOS provides asset information for these devices, the asset information stored in the BIOS can also be used. This method can comprehensively and accurately obtain all necessary information about the device.

[0141] Once the method for acquiring the target asset information is determined, BMC will execute the asset information acquisition operation accordingly. This may involve sending specific management commands, parsing the returned data packets, and integrating the acquired information into the server's overall asset information database.

[0142] This disclosure provides a method for acquiring asset information. By comprehensively detecting the expansion connections of slots, the system can dynamically identify and adapt to different hardware configurations, including directly connected devices and devices connected to expansion cards / accelerator cards. Through precise presence detection, the system can accurately determine the presence status of physical devices in each slot. The generation of the presence information table provides reliable basic data for subsequent asset information acquisition and management, ensuring stable system operation. The system can select the most appropriate asset information acquisition method based on the actual connection status of the devices and the asset information sent by the BIOS. This dynamic allocation mechanism not only improves the accuracy and efficiency of asset information acquisition but also reduces unnecessary system overhead and improves overall management efficiency.

[0143] To clearly illustrate the embodiments of this disclosure, this embodiment provides a flowchart of another method for obtaining asset information.

[0144] like Figure 2 As shown, the method includes the following steps:

[0145] Step 201: The motherboard controller performs an on-premises detection on each slot in the server and stores the detected on-premises status information in the expander.

[0146] As a specific implementation method, "the motherboard controller performs presence detection on each slot in the server and stores the detected presence status information to the expander" includes, but is not limited to: the motherboard controller scanning the motherboard slots of the server and storing the detected accelerator card presence status and accelerator card type to the first motherboard expander; the motherboard controller scanning the motherboard devices on the motherboard slots in the server and writing the detected presence status information of the motherboard devices to the second motherboard expander; and the motherboard controller scanning the accelerator slot devices on the accelerator cards and storing the detected presence status information of the accelerator slot devices to the accelerator card expander.

[0147] Specifically, in step 201, within the server hardware management system, the motherboard controller undertakes crucial in-situ detection and information storage tasks to achieve comprehensive monitoring and efficient management of the server's internal hardware resources. The motherboard controller can be a CPLD on the motherboard, but this embodiment does not limit it to this type.

[0148] The motherboard controller first performs a systematic scan of all slots on the server motherboard, paying particular attention to slots that may house accelerator cards (such as NVMe accelerator cards, GPU accelerator cards, etc.). Through specific electrical signal detection mechanisms (such as differential line response level change rate monitoring), the motherboard controller can accurately determine the presence of an accelerator card and identify its type (e.g., based on vendor ID, device ID, or specific electrical characteristics). The detected accelerator card presence status and type information are then encoded and stored in the first motherboard expander, which acts as an information relay station for subsequent reading and processing by the BMC (Baseboard Management Controller) or other management components.

[0149] After completing the presence detection of the accelerator card, the motherboard controller continues to scan other motherboard devices directly connected to the motherboard slot (such as the CPU, memory modules, basic PCIe devices, etc.). Through similar or different detection mechanisms (such as GPIO status reading, device response signal analysis, etc.), the motherboard controller obtains the presence status information of these motherboard devices, encodes it, and writes it to the second motherboard expander. The second motherboard expander also serves as a medium for information storage and transmission, ensuring that the presence status information of the motherboard devices can be transmitted to the BMC or other management systems in a timely and accurate manner.

[0150] For accelerator cards already detected, the motherboard controller performs a further deep scan of the accelerator slot devices on the card. These devices may include additional NVMe SSDs, FPGA modules, or other dedicated hardware. The motherboard controller employs a detection mechanism similar to, but potentially more refined than, motherboard slot detection to accurately identify the presence status of the accelerator slot devices and stores the relevant information in the accelerator card expander. As a dedicated information storage unit for the accelerator card, the expander not only records the presence status of the accelerator slot devices but may also contain device configuration information, performance parameters, etc., providing data support for comprehensive management and optimization of the accelerator cards.

[0151] Step 202: The baseboard management controller obtains the in-situ status information of the slot devices stored in the expander.

[0152] As a specific implementation, "the baseboard management controller obtains the on-site status information of the slot devices stored in the expander" includes, but is not limited to: the baseboard management controller obtains the on-site status information of the motherboard devices on the motherboard slots in the server from the second motherboard expander; the baseboard management controller obtains the on-site status information and accelerator card type from the first motherboard expander; the baseboard management controller traverses a preset relationship table based on the accelerator card type to determine the on-site status information of the accelerator slot devices in the accelerator card.

[0153] Specifically, in step 202, the Baseboard Management Controller (BMC), as the core management unit, is responsible for monitoring and managing the status and configuration of various hardware resources within the server. The BMC first establishes a connection with the second motherboard expander via a pre-defined communication interface (such as the I2C bus). The second motherboard expander serves as a storage unit for motherboard device presence status information, internally recording the presence status of motherboard devices (such as the CPU, memory modules, and basic PCIe devices) connected to each slot on the server motherboard. The BMC retrieves this presence status information from the second motherboard expander by sending specific read commands. This process ensures that the BMC can monitor the configuration of critical hardware resources on the motherboard in real time, providing fundamental data support for subsequent system management and maintenance.

[0154] Next, BMC interacts with the first motherboard expander through the same communication interface. The first motherboard expander is specifically used to store the presence status information and type of accelerator cards (such as NVMe accelerator cards, GPU accelerator cards, etc.). BMC sends corresponding read commands to obtain the presence status (existence) of the accelerator card and its specific type (e.g., identified based on vendor ID, device ID, or specific electrical characteristics) from the first motherboard expander. This information is crucial for BMC to identify the accelerator card and take appropriate management measures.

[0155] After obtaining the accelerator card's presence status and type, the BMC further utilizes this information to traverse its internally maintained preset relationship table. This table records in detail the correspondence between different types of accelerator cards and their corresponding accelerator slot devices, including the number, location, and possible device types of accelerator slots. Based on the accelerator card's type, the BMC searches the relationship table for the corresponding accelerator slot device configuration and, combined with the basic presence status information obtained from the expander (such as whether the accelerator card as a whole is present), infers the specific presence status of each accelerator slot device on the accelerator card. This process allows the BMC to indirectly grasp the hardware resource configuration of each accelerator slot device without directly detecting each accelerator slot device, greatly improving the efficiency and flexibility of system management.

[0156] Step 203: The baseboard management controller obtains the on-site status information of the hard disk device in the hard disk backplane.

[0157] As a specific implementation method, "the baseboard management controller obtains the on-site status information of the hard disk device in the hard disk backplane" includes, but is not limited to: the basic management controller reads the topology information of the hard disk backplane; the basic management controller accesses the hard disk backplane based on the topology information to obtain the on-site status information of the hard disk device.

[0158] Specifically in step 203, in the server hardware resource management system, the Baseboard Management Controller (BMC) is not only responsible for monitoring the motherboard and its various devices, but also for monitoring the status of the hard disk backplane and its hard disk devices to ensure the reliability and efficiency of the entire storage system.

[0159] The Baseboard Management Controller (BMC) first establishes a connection with the hard drive backplane management controller (such as a CPLD or a dedicated backplane management chip) through its built-in communication interface (such as I2C, SMBus, etc.). The BMC sends a specific read command, requesting the hard drive backplane management controller to provide its topology information. This topology information includes, but is not limited to, the physical layout of the hard drive backplane, the number and location of hard drive slots, and the type of hard drive device that may be connected to each slot (such as SATA, SAS, NVMe, etc.). By obtaining this information, the BMC can construct a logical model of the hard drive backplane, providing a foundation for subsequent status monitoring.

[0160] After obtaining the topology information of the hard drive backplane, the BMC formulates an access strategy based on this information and interacts with each hard drive slot on the backplane through a preset communication protocol. Specifically, the BMC may obtain the presence status information of the hard drive devices through the following steps: Selecting a communication channel: Based on the topology information, the BMC determines the I2C channel or other dedicated communication channel required to communicate with a specific hard drive slot. Sending a detection command: The BMC sends a presence detection command to the hard drive slot through the selected communication channel. These commands may include reading the level status of specific pins, sending specific query instructions, etc., to determine whether the hard drive device is connected to the slot. Receiving and parsing the response: After receiving the detection command, the hard drive slot (or the connected hard drive device) will return a corresponding response signal. The BMC receives these response signals and parses the presence status information of the hard drive device according to the preset protocol. Updating the status record: The BMC updates the parsed presence status information of the hard drive device to its internal status record table for subsequent management and monitoring.

[0161] Step 204: The baseboard management controller integrates the acquired on-site status information of the motherboard device and the acceleration slot device.

[0162] Specifically in step 204, in the server hardware resource management process, the Baseboard Management Controller (BMC) serves as the core monitoring and management unit, responsible for collecting and integrating on-site status information from different hardware components to achieve a comprehensive understanding of the overall hardware configuration of the server.

[0163] The Baseboard Management Controller (BMC) first obtains the presence status information of motherboard devices (such as CPU, memory, basic PCIe devices, etc.) from the second motherboard expander through the communication interface established in the previous steps, and obtains the presence status information of accelerator cards and their accelerator slot devices from the first motherboard expander and accelerator card expander. After collecting this information, the BMC performs preliminary data cleaning and formatting to ensure that all data conforms to a unified format standard, facilitating subsequent integration and analysis.

[0164] BMC employs the following strategies to integrate the presence status information of motherboard devices and acceleration slot devices: **Unified Identifiers:** All devices are assigned unique identifiers (such as slot numbers, device serial numbers, etc.) to ensure accurate differentiation of different devices and their statuses during integration. **Status Field Mapping:** A standard set of status field mapping rules is defined to map status information from different sources (such as "present," "absent," "faulty," etc.) to a unified status representation, facilitating subsequent data analysis and processing. **Topology Establishment:** Based on the hard drive backplane topology information and motherboard slot layout, topological relationships between devices are established, clarifying the physical location and logical connections of each device within the server.

[0165] BMC categorizes and organizes the collected motherboard device availability information according to device type, slot location, and other dimensions, forming a motherboard device availability table. This table records the availability status and related attributes of each motherboard device in detail. For accelerator cards and their accelerator slot devices, BMC first traverses a preset relationship table based on the accelerator card type to determine the expected configuration of each accelerator slot device on the accelerator card. Then, it compares the actual detected accelerator slot device availability information with the expected configuration to form an accelerator slot device availability table. This table not only records the device availability status but also includes information on the differences between the actual and expected configurations. Finally, BMC merges the motherboard device availability table and the accelerator slot device availability table to generate a comprehensive availability table. This table comprehensively reflects the availability status and configuration of all critical hardware resources within the server, providing an important basis for subsequent system management and maintenance.

[0166] Step 205: The baseboard management controller constructs a table based on the identity identifiers of the motherboard device and the acceleration slot device, and generates an in-situ information table.

[0167] Specifically in step 205, in server hardware resource management, the Baseboard Management Controller (BMC) is responsible for integrating the in-situ status information from different hardware components and building a comprehensive and accurate in-situ information table based on this information, so that system administrators or automation tools can intuitively understand the configuration of the server's internal hardware resources.

[0168] The Baseboard Management Controller (BMC) has already collected the presence status information of the motherboard devices and acceleration slot devices in previous steps, and obtained the identification information for these devices. Identification information typically includes, but is not limited to, the device's unique serial number (SN), part number (PN), and slot location identifier. The BMC standardizes these identification information to ensure accurate identification and referencing of each device during subsequent table construction.

[0169] To construct a clear and easy-to-read presence information table, BMC employs the following strategies: Unified Table Format: A standard table format is defined, including headers, rows, and columns, ensuring all presence status information is displayed in a consistent format. Device Categorization: Devices are categorized and displayed according to type (e.g., motherboard devices, accelerator slot devices, etc.) to facilitate quick location of specific device types by administrators. Status Information Encoding: A unified encoding method is used for device presence status information (e.g., "1" for presence, "0" for absence, "F" for malfunction, etc.) to ensure accuracy and consistency. Table Initialization: BMC first creates an empty table and sets the header, including key fields such as device type, identifier, slot location, and presence status. Motherboard Device Information Population: Based on the previously collected motherboard device presence status information, BMC populates this information into the corresponding positions in the table. For each motherboard device, BMC records its device type, identifier, slot location, and presence status. Accelerator Slot Device Information Population: Similarly, BMC populates the table with the presence status information of accelerator slot devices. For each accelerator slot device, in addition to recording the device type, identification, slot location, and availability status, the BMC may also record the type of accelerator card it belongs to and related information. Data verification and correction: After filling in all device information, the BMC verifies the data in the table to ensure its accuracy and completeness. For any data errors or inconsistencies found, the BMC corrects or marks them for subsequent processing.

[0170] After the above steps, BMC generates a detailed and accurate on-premises information table. This table not only records the on-premises status information of motherboard devices and acceleration slot devices, but also includes key information such as device identification and slot location, providing system administrators or automation tools with a comprehensive view of hardware resources.

[0171] Step 206: The baseboard management controller listens to the preset transmission interface to obtain asset information in a preset format sent by the basic input / output system; the baseboard management controller parses the asset information in the preset format and extracts the asset information.

[0172] Specifically, in step 206, the Baseboard Management Controller (BMC) plays a core monitoring and management role in the server hardware management system. To comprehensively obtain detailed information about the server's internal hardware resources, the BMC is configured to listen to a preset transmission interface. This interface is typically based on an industry-standard protocol, such as the Redfish interface, used to communicate with the Basic Input / Output System (BIOS). Interface Selection: The Redfish interface was chosen as the transmission interface because it provides a standardized RESTful API, supports cross-platform and cross-vendor hardware management, and facilitates interaction between the BMC and BIOSes from different vendors. Listening Mechanism: The BMC continuously listens for data transmission on this preset interface through a built-in network service or a dedicated communication module. Once a data packet from the BIOS is detected, the BMC immediately initiates the receiving process.

[0173] During server startup, the BIOS collects and organizes detailed information on all hardware components on the motherboard, including but not limited to device model, serial number, firmware version, and hardware configuration, and encapsulates this information according to a preset format (such as JSON). Data Encapsulation: The BIOS encapsulates the collected asset information into a data packet conforming to the Redfish interface specification. This data packet contains rich hardware resource description information. Data Transmission: The encapsulated data packet is sent to the BMC through a preset transmission interface (such as the Redfish interface). Upon receiving the data packet, the BMC immediately receives it and temporarily stores it in memory for subsequent processing.

[0174] After receiving the asset information data packet from the BIOS, the BMC needs to parse it to extract useful hardware resource information. Data Decoding: The BMC first decodes the received data packet, converting it from binary format to a readable text format (such as a JSON string). Structure Analysis: Based on a preset JSON structure, the BMC analyzes each field in the data packet, identifying key data such as device type, identification, and status information. Information Extraction: The BMC extracts specific asset information from the parsed data, such as device model, serial number, and firmware version, and stores this information in an internal database or cache for later querying and use. Error Handling: During the parsing process, the BMC also has error detection and handling capabilities. If it finds errors such as incorrect data packet format, missing fields, or inconsistent data, the BMC will log the error and attempt to re-receive or request the BIOS to resend the data packet.

[0175] Step 207: The baseboard management controller converts the received asset information into a system-side presence information table.

[0176] Specifically, in step 207, within the server hardware resource management system, the Baseboard Management Controller (BMC) is responsible for collecting asset information from the BIOS. This information is typically stored in a structured data format (such as JSON) and contains detailed attributes of each hardware component within the server. However, to facilitate intuitive hardware resource monitoring and management by system administrators or automated operation and maintenance tools, this asset information needs to be converted into a more easily understood and manipulated format, namely, a system-side presence information table.

[0177] The BMC performs the following steps to convert the received asset information into a system-side presence information table: Data Reception and Preliminary Verification: The BMC first receives the asset information data packet from the BIOS through a preset transmission interface (such as the Redfish interface). The received data packet undergoes integrity verification to ensure that the data has not been damaged or lost during transmission.

[0178] Data Parsing and Field Mapping: The BMC parses the received asset information data packets, extracting key attribute fields for each hardware component, such as device type, identification, serial number, firmware version, and presence status. Based on the design requirements of the system-side presence information table, a mapping relationship is established between asset information fields and presence information table fields. For example, "device type" in the asset information is mapped to the "device category" field in the presence information table, and "serial number" is mapped to the "device number" field, etc.

[0179] Information Integration and Formatting: Based on field mapping relationships, BMC integrates the parsed asset information into the corresponding fields of the system-side location information table. The integrated information is then formatted to ensure that the data type, length, and format of all fields conform to the design specifications of the system-side location information table. For example, date and time fields are uniformly converted to a specific date and time format, and numeric fields are rounded or truncated.

[0180] Table Generation and Storage: Based on the formatted information, BMC dynamically generates a system-side presence information table. This table typically exists in the form of a two-dimensional array or a database table, containing the presence status and related attribute information of all hardware components. The generated system-side presence information table is stored in BMC's internal database or cache for subsequent querying and use. Alternatively, the table data can be synchronized to a remote management server or cloud platform for remote monitoring and management.

[0181] Step 208: Compare the system-side presence information table with the presence information table; if the physical device exists in the presence information table but does not exist in the system-side presence information table, then the physical device is determined to be the target device on the accelerator card.

[0182] If the target device is a slot device, proceed to step 209; if the target device is a hard disk device, proceed to step 210.

[0183] Specifically, in step 208, in server hardware resource management, to ensure accurate monitoring and effective management of hardware resources, the Baseboard Management Controller (BMC) needs to compare the system-side presence information table with the existing presence information table. The specific comparison process is as follows:

[0184] Data Preparation: System-side In-Situ Information Table: Contains hardware resource information parsed and converted from the BIOS, reflecting the theoretically existing hardware configuration of the system. In-Situ Information Table: Generated by the BMC through direct hardware detection methods (such as those constructed in step 204), reflecting the actual hardware resource status within the server.

[0185] Comparison Implementation: The BMC initiates the comparison procedure, checking each physical device record in the location information table one by one. For each record in the location information table, the BMC searches for a corresponding device identifier (such as device serial number, slot location, etc.) in the system-side location information table. If no corresponding record is found in the system-side location information table, the physical device is marked as "suspected missing".

[0186] Based on the comparison results, BMC further determined whether the suspected missing physical device was the target device on the accelerator card, and distinguished its type (slot device or hard drive device):

[0187] Accelerator Card Target Device Determination: If a suspected missing physical device is located in the accelerator card slot, and according to the accelerator card preset relationship table (as mentioned in step 202) or hardware topology information, the device should belong to the accelerator card, then the physical device is determined to be the target device on the accelerator card.

[0188] Device type distinction: Slot device: If the target device is connected to a standard slot such as a PCIe slot or memory slot on the motherboard or accelerator card, and does not belong to the category of hard drive devices, it is determined to be a slot device.

[0189] Hard drive device: If the target device is a hard drive (such as SATA hard drive, SAS hard drive, NVMe hard drive, etc.) and is connected to the hard drive back panel or directly connected to the hard drive interface on the motherboard, it is determined to be a hard drive device.

[0190] Depending on the type of target device, BMC executes different follow-up processing procedures:

[0191] If the target device is a slot device: Step 209 may involve further testing, configuration adjustment, or troubleshooting of the slot device to ensure its normal operation or restore it to its proper state in the system-side in-place information table. If the target device is a hard disk device: Step 210 may involve health checks, data backup, fault recovery, or reconfiguration of the hard disk device to ensure the reliability and data integrity of the storage system.

[0192] Step 209: Verify whether the slot device is the target physical device, and determine the method for obtaining the target asset information of the slot device based on the verification result.

[0193] As a specific implementation method, "verifying whether the slot device is the target physical device and determining the method of obtaining the target asset information of the slot device based on the verification result" includes, but is not limited to: verifying whether the slot device is the target physical device when it is determined that the slot device is in place and the basic input / output system has sent asset information; if it is the target physical device, determining to obtain the target asset information through the board management controller; if it is not the target physical device, obtaining the target asset information through the basic input / output system.

[0194] If the target device is a target physical device, then proceed to step 211.

[0195] Specifically, in step 209, within the server hardware resource management process, for the slot devices (i.e., candidate target physical devices) identified as potentially missing but actually present in step 208, further verification is needed to confirm whether they are truly the target physical devices requiring attention. The specific verification process is as follows:

[0196] In-situ Status Confirmation: Based on the in-situ information table, confirm that the slot device is indeed in-situ. This step ensures that subsequent verification targets devices that actually exist in the server hardware environment. BIOS Asset Information Matching: Check whether the Basic Input / Output System (BIOS) has sent an asset information data packet containing information about the slot device. By comparing the device identifier (such as device serial number, slot location, etc.) in the in-situ information table with the corresponding fields in the BIOS asset information, confirm whether the BIOS has recognized and recorded the device.

[0197] Target physical device determination: If the slot device is both present and recorded in the BIOS asset information, then the system further determines whether the device is the target physical device in the current management scenario based on preset rules (such as device model, functional requirements, etc.). For example, if the management requirement is to monitor a specific model of accelerator card or a PCIe device with a specific function, then it is necessary to verify whether the slot device meets these conditions.

[0198] Based on the above verification results, the BMC (Baseboard Management Controller) will determine the specific method for obtaining the target slot device asset information: If it is a target physical device: Obtained through the BMC: Since the slot device is a target physical device, and the BMC already has the ability to directly monitor and manage the device (e.g., through I2C, SMBus interfaces), it is determined that the target asset information of the device will be obtained directly through the BMC. This method ensures the real-time nature and accuracy of the information while reducing reliance on the BIOS. If it is not a target physical device: Obtained through the BIOS: If the slot device is present but not a target physical device, or for some reason (e.g., interface limitations, management requirements) is not suitable for direct management by the BMC, then it is determined that the asset information of the device will be obtained through the BIOS. The BIOS collects and organizes detailed information of all hardware components during server startup, thus serving as a reliable source for obtaining asset information of non-target physical devices.

[0199] If the target device is a target physical device: After determining that the target asset information is obtained through BMC, proceed to step 211, which is to further process this information to support tasks such as server hardware monitoring, configuration management, or troubleshooting.

[0200] Step 210: Determine the method for obtaining the target asset information of the hard disk device based on whether the basic input / output system has sent asset information.

[0201] As a specific implementation method, "determining the method for obtaining the target asset information of the hard disk device based on whether the basic input / output system has sent asset information" includes, but is not limited to:

[0202] If the hard disk device is confirmed to be in place and the basic input / output system has sent asset information, the target asset information is obtained through the basic input / output system.

[0203] If the hard disk device is confirmed to be in place and the basic input / output system has not sent asset information, the target asset information is obtained through the baseboard management controller.

[0204] If the target device is a hard disk device, then proceed to step 212.

[0205] Specifically, in step 210, within the server hardware resource management process, for the target device identified as a hard disk device in step 208, it is necessary to further determine the specific method for obtaining the target asset information of the hard disk device based on whether the Basic Input / Output System (BIOS) has sent asset information. Before this, the following prerequisites must be confirmed:

[0206] Hard drive device presence confirmation: Based on the presence information table, confirm that the hard drive device is indeed in a present state, that is, it has been physically and correctly connected to the server.

[0207] When BIOS has sent asset information: Information Verification: The BMC first checks whether it has received the asset information data packet from the BIOS and verifies whether the packet contains detailed information about the target hard drive device. Information Acquisition: If the BIOS has sent the packet and it contains the target hard drive device information, the BMC will directly obtain the target asset information by parsing the packet. This method leverages the BIOS's automatic collection of hardware information during server startup, reducing the BMC's additional operational burden.

[0208] If the BIOS fails to send asset information: Backup plan activated: If the BMC does not receive an asset information data packet from the BIOS, or the data packet does not contain target hard drive device information, the BMC will activate the backup plan. Direct acquisition: The BMC communicates directly with the target hard drive device through its built-in hard drive management interface (such as SATA, SAS, or NVMe interface) to obtain its target asset information. This method ensures that even if the BIOS does not provide relevant information, the BMC can still obtain the necessary information about the hard drive device.

[0209] Information Integration: Regardless of the method used to acquire target asset information, BMC will integrate and standardize this information for subsequent management and monitoring. Step 212: After acquiring the target asset information for the target hard drive device, BMC will execute step 212, which may involve operations such as checking the hard drive device's health status, monitoring performance, adjusting configurations, or troubleshooting to ensure the stable operation and efficient utilization of the hard drive device.

[0210] Step 211: The baseboard management controller obtains the target module information of the target physical device; the baseboard management controller obtains the basic information of the target module stored in the basic input / output system, and generates target asset information based on the basic information and the target module information.

[0211] Specifically, in step 211, the Baseboard Management Controller (BMC) first locates the target physical device in the system's internal database or hardware topology diagram based on the target physical device identifier (such as device serial number, slot location, etc.) confirmed in step 209. It further identifies key modules on the target physical device, such as the GPU module, FPGA module on the accelerator card, or other hardware components with independent functions and identifiers.

[0212] Target module information collection:

[0213] BMC establishes a connection with the target module through a pre-defined communication interface (such as I2C, PCIe configuration space access, dedicated management interface, etc.). It sends an information query command to the target module, requesting detailed information, including but not limited to module model, firmware version, hardware configuration, and operating status. It receives and parses the information returned by the target module, storing it as "target module information" for subsequent processing.

[0214] BIOS Information Storage Location Confirmation: The BMC understands that the BIOS stores hardware information in specific non-volatile memory areas (such as CMOS, NVRAM, or specific memory areas) during server startup for subsequent lookup. The BMC confirms the specific location and format of the target module's basic information within the BIOS storage area. Basic Information Extraction: The BMC accesses the BIOS storage area through an appropriate interface (such as LPC bus, SMBus, or memory-mapped I / O). Based on the predefined format and location, the BMC extracts the target module's basic information, such as the module's basic model number, manufacturer information, and compatibility identifiers. This extracted information is stored as "basic information" for comparison and integration with the target module's information.

[0215] Information Comparison and Integration: BMC compares the acquired "target module information" with the "basic information" to identify differences and gaps. Based on the comparison results, the two sets of information are integrated to generate a complete "target asset information". This information should include all key attributes of the target module, such as detailed model number, firmware version, hardware configuration, operating status, manufacturer information, and compatibility identifiers. Information Standardization and Storage: The generated "target asset information" is standardized to ensure its format is compatible with BMC's internal database or other management systems. The standardized "target asset information" is stored in BMC's internal database or cache for subsequent querying, monitoring, and management.

[0216] Step 212: Based on the source identifier of the hard disk device, look up the offset source mapping table to obtain the asset identifier data; parse the asset identifier data to generate target asset information.

[0217] Specifically, in step 212, the Baseboard Management Controller (BMC), having confirmed the presence of the hard disk device in step 210, may have obtained basic information about the hard disk device, including its source identifier, through the BIOS or direct communication. The source identifier can be a manufacturer-specific identifier, a specific field in the serial number, a hard disk interface type code, or a unique path identifier for the hard disk device within the system, used to uniquely determine the source or type of the hard disk device. Identifier validity verification: The BMC verifies the validity of the obtained source identifier to ensure it conforms to preset formats and rules, preventing subsequent processing failures due to incorrect identifiers.

[0218] The offset source mapping table is a predefined data structure stored in the BMC's non-volatile memory, used to establish a mapping relationship between the source identifier of a hard disk device and asset identifier data. This mapping table may contain multiple entries, each consisting of a source identifier field and the corresponding asset identifier data offset or direct asset identifier data. The BMC searches the offset source mapping table based on the hard disk device's source identifier. The search process may involve algorithms such as string matching, hash calculation, or index lookup to quickly locate the mapping table entry corresponding to the source identifier. If a matching entry is found, the BMC records the asset identifier data offset stored in that entry (if applicable) or directly retrieves the asset identifier data.

[0219] If the mapping table entry provides an offset for asset identification data, BMC reads the complete asset identification data from a preset storage area (such as a specific memory area or a specific sector in non-volatile memory) based on that offset. The read asset identification data is then parsed to identify key information fields, such as hard drive model, capacity, firmware version, production date, and serial number. The parsing process may involve data format conversion, field extraction, and verification.

[0220] Based on the parsed asset identification data, BMC generates target asset information. This target asset information should include all key attributes of the hard drive device, and the format should conform to the requirements of BMC's internal database or other management systems. The generated target asset information may include, but is not limited to: hard drive model, capacity, firmware version, production date, serial number, health status, interface type, SMART attribute, etc.

[0221] It should be noted that the embodiments of this disclosure may include multiple steps. For ease of description, these steps are numbered, but these numbers are not a limitation on the execution time slots or execution order between the steps; these steps can be implemented in any order, and the embodiments of this disclosure do not limit this.

[0222] Figure 3 A server for acquiring asset information includes: a baseboard management controller 31, a controller unit 32, an extender unit 33, and an interface connection unit 34;

[0223] The controller unit 32 includes a first controller 321, which is connected to the expander unit 33 and the baseboard management controller 31. The first controller 321 performs presence detection on each slot in the server motherboard and stores the detected presence status information in the expander unit 33. In response to the acquisition command of the baseboard management controller 31, the first controller 321 sends the presence status information to the baseboard management controller 31.

[0224] The baseboard management controller 31 is connected to the interface connection unit 34, and the interface connection unit 34 is connected to the hard disk device on the hard disk backplane to obtain the on-site status information of the hard disk device.

[0225] Furthermore, as one implementation of this disclosure, the controller unit 32 further includes: a second controller 322;

[0226] The second controller 322 is connected to the interface connection unit 34.

[0227] Furthermore, as one implementation of this disclosure, the server further includes: a plurality of multiplexers 35;

[0228] Multiple multiplexers 35 are disposed on the link connecting the baseboard management controller 31 and the interface connection unit 34, and on the link connecting the interface connection unit 34 and the second controller 322 and the hard disk device.

[0229] Furthermore, as one implementation of this disclosure, the expander unit 33 includes: a first motherboard expander 331, a second motherboard expander 332, and an accelerator card expander 333;

[0230] The first motherboard expander 331 and the second motherboard expander 332 are mounted on the server motherboard and are connected to the first controller 321 respectively; the accelerator card expander 333 is mounted on the accelerator card and is connected to the first controller 321.

[0231] Corresponding to the aforementioned method for obtaining asset information, this disclosure also proposes an apparatus for obtaining asset information. Since the apparatus embodiments of this disclosure correspond to the aforementioned method embodiments, details not disclosed in the apparatus embodiments can be referred to the aforementioned method embodiments, and will not be repeated here.

[0232] Figure 4 This is a schematic diagram of the structure of an asset information acquisition device provided in an embodiment of the present disclosure, as shown below. Figure 3 As shown, it includes:

[0233] The generation unit 41 is used for the baseboard management controller to obtain the on-site status information of the physical devices connected to each slot in the server, and to generate an on-site information table of the physical devices based on the obtained on-site status information.

[0234] The comparison unit 42 is used for the baseboard management controller to obtain asset information sent by the basic input / output system, and compare the in-situ information table with the asset information to determine whether the physical device is the target device on the accelerator card.

[0235] The acquisition unit 43 is used to determine the target asset information acquisition method of the target device based on the information comparison result when the target device is determined to be on the accelerator card, and to acquire the target asset information of the target device according to the target asset information acquisition method.

[0236] This disclosure provides an asset information acquisition device. By comprehensively detecting the expansion connections of slots, the system can dynamically identify and adapt to different hardware configurations, including directly connected devices and devices connected to expansion cards / accelerator cards. Through precise presence detection, the system can accurately determine the presence status of physical devices in each slot. The generation of the presence information table provides reliable basic data for subsequent asset information acquisition and management, ensuring stable system operation. It can select the most suitable asset information acquisition method based on the actual connection status of the devices and the asset information sent by the BIOS. This dynamic allocation mechanism not only improves the accuracy and efficiency of asset information acquisition but also reduces unnecessary system overhead and improves overall management efficiency.

[0237] It should be noted that the foregoing explanation of the method embodiments also applies to the apparatus of this embodiment, and the principle is the same, so it is not limited in this embodiment.

[0238] For a description of the features in the embodiment corresponding to the asset information acquisition device, please refer to the relevant description in the embodiment corresponding to the asset information acquisition method, which will not be repeated here.

[0239] Embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any of the above-described asset information acquisition method embodiments.

[0240] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above-described asset information acquisition method embodiments when it is run.

[0241] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0242] Embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above-described asset information acquisition method embodiments.

[0243] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in any of the above-described asset information acquisition method embodiments.

[0244] Those skilled in the art will further 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 implementation should not be considered beyond the scope of this application.

[0245] The foregoing has provided a detailed description of the method, apparatus, server, electronic device, and medium for acquiring asset information provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and its core ideas. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A method for obtaining asset information, characterized in that, include: The baseboard management controller acquires the in-situ status information of the physical devices connected to each slot in the server, and generates an in-situ information table of the physical devices based on the acquired in-situ status information. The baseboard management controller acquires asset information sent by the basic input / output system. The baseboard management controller converts the received asset information into a system-side presence information table and compares the presence information table with the asset information to determine whether the physical device is the target device on the accelerator card. The step of comparing the location information table with the asset information to determine whether the physical device is the target device on the accelerator card includes: comparing the system-side location information table with the location information table; if the physical device exists in the location information table but does not exist in the system-side location information table, then the physical device is determined to be the target device on the accelerator card. When a target device on an accelerator card is identified, the baseboard management controller determines the target asset information acquisition method for the target device based on the information comparison result, and acquires the target asset information of the target device according to the target asset information acquisition method. If the target device is a slot device, it verifies whether the slot device is the target physical device, and determines the target asset information acquisition method for the slot device based on the verification result. If the target device is a hard disk device, it determines the target asset information acquisition method for the hard disk device based on whether the basic input / output system has sent the asset information.

2. The method for obtaining asset information according to claim 1, characterized in that, The physical devices include: hard disk devices and slot devices; The baseboard management controller acquires the presence status information of the physical devices connected to each slot in the server, including: The baseboard management controller acquires the in-situ status information of the slot devices stored in the expander; The baseboard management controller acquires the in-situ status information of the hard disk device in the hard disk backplane.

3. The method for obtaining asset information according to claim 2, characterized in that, Before the substrate management controller acquires the presence information of the acceleration slot device stored in the expander, the method further includes: The motherboard controller detects the presence of each slot in the server and stores the detected presence status information in the expander.

4. The method for obtaining asset information according to claim 3, characterized in that, The expander includes: a first motherboard expander, a second motherboard expander, and an accelerator card expander; the slot device includes a motherboard device and an accelerator slot device. The motherboard controller performs presence detection on each slot in the server and stores the detected presence status information to the expander, including: The motherboard controller scans the motherboard slots of the server and stores the detected accelerator card presence status and accelerator card type in the first motherboard expander. The motherboard controller scans the motherboard devices on the motherboard slots in the server and writes the detected presence status information of the motherboard devices into the second motherboard expander; The motherboard controller scans the acceleration slot devices on the accelerator card, and stores the detected presence status information of the acceleration slot devices in the accelerator card expander.

5. The method for obtaining asset information according to claim 4, characterized in that, The baseboard management controller acquires the in-situ status information of the slot devices stored in the expander, including: The baseboard management controller obtains the in-situ status information of the motherboard device on the motherboard slot in the server from the second motherboard expander; The baseboard management controller obtains the accelerator card's presence status information and accelerator card type from the first motherboard expander; The baseboard management controller traverses a preset relationship table based on the accelerator card type to determine the in-situ status information of the accelerator slot device in the accelerator card.

6. The method for obtaining asset information according to claim 2, characterized in that, The baseboard management controller acquires the presence status information of the hard disk device in the hard disk backplane, including: The basic management controller reads the topology information of the hard disk backplane; The basic management controller accesses the hard disk backplane based on the topology information to obtain the on-site status information of the hard disk device.

7. The method for obtaining asset information according to claim 5, characterized in that, The step of generating a physical device presence information table based on the acquired presence status information includes: The baseboard management controller integrates the acquired in-situ status information of the motherboard device and the acceleration slot device. The baseboard management controller constructs a table based on the identity identifiers of the motherboard device and the acceleration slot device, and generates the in-situ information table.

8. The method for obtaining asset information according to claim 1, characterized in that, The baseboard management controller acquires asset information sent by the basic input / output system, including: The baseboard management controller listens to a preset transmission interface to obtain asset information in a preset format sent by the basic input / output system; The baseboard management controller parses the asset information in the preset format and extracts the asset information.

9. The method for obtaining asset information according to claim 1, characterized in that, The method for verifying whether the slot device is the target physical device and determining the method for obtaining the target asset information of the slot device based on the verification result includes: If it is determined that the slot device is in place and the basic input / output system has sent the asset information, verify whether the slot device is the target physical device; If it is a target physical device, then the target asset information is obtained through the baseboard management controller; If it is not the target physical device, the target asset information is obtained through the basic input / output system.

10. The method for obtaining asset information according to claim 9, characterized in that, The method for determining the acquisition method of the target asset information of the hard disk device based on whether the basic input / output system has sent the asset information includes: If the hard disk device is confirmed to be in place and the basic input / output system has sent the asset information, the target asset information is obtained through the basic input / output system. If the hard disk device is confirmed to be in place and the basic input / output system does not send the asset information, the target asset information is obtained through the baseboard management controller.

11. The method for obtaining asset information according to claim 10, characterized in that, The step of obtaining the target asset information of the target device according to the target asset information acquisition method includes: If the target device is the target physical device, then the baseboard management controller obtains the target module information of the target physical device; The baseboard management controller obtains the basic information of the target module stored in the basic input / output system, and generates the target asset information based on the basic information and the target module information.

12. The method for obtaining asset information according to claim 10, characterized in that, The step of obtaining the target asset information of the target device according to the target asset information acquisition method further includes: If the target device is the hard disk device, then based on the source identifier of the hard disk device, the offset source mapping table is searched to obtain the asset identifier data; The asset identification data is parsed to generate the target asset information.

13. A server for acquiring asset information, characterized in that, The server is configured to perform the asset information acquisition method according to any one of claims 1-12, the server comprising: a baseboard management controller, a controller unit, an extender unit, and an interface connection unit; The controller unit includes a first controller, which is connected to the expander unit and the baseboard management controller. The first controller performs presence detection on each slot in the server motherboard and stores the detected presence status information in the expander unit. In response to the acquisition command of the baseboard management controller, the first controller sends the presence status information to the baseboard management controller. The baseboard management controller is connected to the interface connection unit, and the interface connection unit is connected to the hard disk device on the hard disk backplane to obtain the on-site status information of the hard disk device.

14. The server for acquiring asset information according to claim 13, characterized in that, The controller unit further includes: a second controller; The second controller is connected to the interface connection unit.

15. The server for acquiring asset information according to claim 14, characterized in that, The server also includes: multiple multiplexers; The plurality of multiplexers are disposed on the link connecting the baseboard management controller and the interface connection unit, and on the link connecting the interface connection unit and the second controller and the hard disk device.

16. The server for acquiring asset information according to claim 13, characterized in that, The expander unit includes: a first motherboard expander, a second motherboard expander, and an accelerator card expander; The first motherboard expander and the second motherboard expander are mounted on the server motherboard and are respectively connected to the first controller; the accelerator card expander is mounted on the accelerator card and is connected to the first controller.

17. An apparatus for acquiring asset information, characterized in that, include: The generation unit is used for the baseboard management controller to obtain the in-situ status information of the physical devices connected to each slot in the server, and to generate an in-situ information table of the physical devices based on the obtained in-situ status information. The comparison unit is used for the baseboard management controller to obtain asset information sent by the basic input / output system. The baseboard management controller converts the received asset information into a system-side presence information table and compares the presence information table with the asset information to determine whether the physical device is the target device on the accelerator card. The step of comparing the location information table with the asset information to determine whether the physical device is the target device on the accelerator card includes: comparing the system-side location information table with the location information table; if the physical device exists in the location information table but does not exist in the system-side location information table, then the physical device is determined to be the target device on the accelerator card. The acquisition unit is configured to, when a target device is determined to be on an accelerator card, determine the target asset information acquisition method of the target device based on the information comparison result, and acquire the target asset information of the target device according to the target asset information acquisition method. Specifically, if the target device is a slot device, the unit verifies whether the slot device is a target physical device and determines the target asset information acquisition method of the slot device based on the verification result; if the target device is a hard disk device, the unit determines the target asset information acquisition method of the hard disk device based on whether the basic input / output system has sent the asset information.

18. An electronic device, characterized in that, include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the asset information acquisition method according to any one of claims 1-12.

19. A non-transitory computer-readable storage medium storing computer instructions, characterized in that, The computer instructions are used to cause the computer to perform the method for acquiring asset information according to any one of claims 1-12.

20. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method for acquiring asset information according to any one of claims 1-12.

Images