Method for enabling volume device management function, mainboard management controller, and electronic device

Abstract

The present application discloses a method for enabling a volume device management function, a motherboard management controller, and an electronic device, which are applied to the motherboard management controller end. The method includes: receiving an indication for enabling the hard disk volume device management function, obtaining hard disk information sent by the host end; responding to the indication for enabling the hard disk volume device management function, and determining the root port number corresponding to the target hard disk in the hard disk in place based on the hard disk information; determining a basic input / output system out-of-band option command based on the root port number; sending the basic input / output system out-of-band option command to the basic input / output system of the host end, and sending a restart command to the host end, so that the host end sets the corresponding root port register based on the basic input / output system out-of-band option command to enable the volume device management function. The method of the present application can facilitate customer function customization and deployment of the volume device management function at the customer site, thereby improving product competitiveness, saving labor costs, and improving efficiency.

Description

Technical Field

[0001] The present application relates to the field of server storage technology, and in particular to a method for enabling volume device management functions, a motherboard management controller, and an electronic device. Background Art

[0002] In a server system, setting the Volume Management Device (VMD) function is a common operation.

[0003] Currently, a common way to configure the VMD function is to manually modify the relevant options after entering the Basic Input Output System (BIOS) configuration interface, which is time-consuming and labor-intensive. Another method is for the BIOS to identify NVMe (Non Volatile Memory Express) solid-state drives by scanning the high-speed serial computer expansion bus standard (Peripheral Component Interconnect Express, PCIe) bus or bandwidth configuration information. This solution requires a second reboot or the implementation of complex logic to complete VMD configuration. Another method uses a multiplexer to form a hardware device to automatically configure VMD. This method requires additional hardware, adds additional costs, and increases the complexity of hardware design, lengthening the hardware design process and relatively extending the product's design-to-market time. Due to the different layout and wiring of each motherboard, this method has a low design reuse rate. Summary of the Invention

[0004] The present application provides a method for enabling volume device management functions, a motherboard management controller, and an electronic device to at least solve the problems of manual configuration of VMD functions and high cost and complex hardware design when configuring VMD functions in related technologies. It can facilitate customer function customization and deployment of VMD functions on-site, enhance product competitiveness, save labor costs, and improve efficiency.

[0005] The present application provides a method for enabling volume device management, characterized in that it is applied to a mainboard management controller, and the method includes:

[0006] Receive the instruction to start the hard disk volume device management function and obtain the hard disk information sent by the host;

[0007] In response to the opening instruction, and based on the hard disk information, determining a root port number corresponding to a target hard disk in the hard disk in place;

[0008] determining a basic input / output system out-of-band option command based on the root port number;

[0009] The BIOS out-of-band option command is sent to the BIOS of the host side, and a restart command is sent to the host side, so that the host side sets a corresponding root port register based on the BIOS out-of-band option command to enable a volume device management function.

[0010] The present application also provides a method for enabling volume device management function, which is characterized in that, when applied to a host side, the method includes: sending hard disk information to a motherboard management controller side after a basic input / output system on the host side performs a power-on self-test; after receiving a restart command sent by the motherboard management controller side, executing a restart operation, and parsing a basic input / output system out-of-band option command sent by the motherboard management controller during the restart process; and setting a corresponding root port register based on the basic input / output system out-of-band option command to enable the volume device management function.

[0011] The present application also provides a computer-readable storage medium having a program stored thereon, which, when executed by a processor, implements the method for enabling volume device management function of the server described above.

[0012] The present application also provides a motherboard management controller, comprising a memory, a processor, and a program stored in the memory and executable on the processor. When the processor executes the program, the method for enabling volume device management function is implemented.

[0013] The present application also provides an electronic device, including a memory, a processor, and a program stored in the memory and executable on the processor. When the processor executes the program, the method for enabling volume device management function is implemented.

[0014] The present application also provides a computer program product, including a computer program / instruction, which implements the above-mentioned method for enabling volume device management function when executed by a processor.

[0015] Through this application, an instruction to enable the hard disk volume device management function is received, hard disk information sent by the host is obtained, and in response to the enable instruction, the root port number corresponding to the target hard disk in the hard disk in place is determined based on the hard disk information. Based on the root port number, a BIOS out-of-band option command is determined, the BIOS out-of-band option command is sent to the host's BIOS, and a restart command is sent to the host, so that the host sets the corresponding root port register based on the BIOS out-of-band option command to enable the volume device management function. Therefore, this method can facilitate customer function customization and on-site deployment of VMD functions, enhance product competitiveness, save labor costs, and improve efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0017] Figure 1 A flowchart of a method for enabling volume device management functions according to one embodiment of the present application;

[0018] Figure 2 This is a structural diagram of the interaction between the motherboard management controller and the host according to one embodiment of the present application;

[0019] Figure 3 A flowchart of a method for enabling volume device management functions according to a specific example of the present application;

[0020] Figure 4 is a flowchart of a method for enabling volume device management function according to another embodiment of the present application;

[0021] Figure 5 This is a schematic diagram of the interaction between the motherboard management controller and the host according to a specific example of the present application;

[0022] Figure 6 is a block diagram of a motherboard management controller according to an embodiment of the present application;

[0023] Figure 7 Schematic diagram of a block diagram of an electronic device according to an embodiment of the present application.

[0024] Reference numerals: 200 - motherboard management controller, 210 - first memory, 220 - first processor, 300 - electronic device, 310 - second memory, 320 - second processor. DETAILED DESCRIPTION

[0025] The following describes in detail embodiments of the present application, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0026] The following describes, with reference to the accompanying drawings, a method for enabling volume device management functions, a computer-readable storage medium, a motherboard management controller, an electronic device, and a computer program product proposed in embodiments of the present application.

[0027] Figure 1 The present invention is a flowchart of a method for enabling volume device management functions according to an embodiment of the present application.

[0028] like Figure 1 As shown, the method for enabling the volume device management function in an embodiment of the present application may include the following steps:

[0029] S1, receiving an instruction to start the hard disk volume device management function, and obtaining hard disk information sent by the host.

[0030] S2, responding to the start instruction and determining the root port number corresponding to the target hard disk in the hard disk in place based on the hard disk information.

[0031] S3, determining a basic input / output system out-of-band option command based on the root port number.

[0032] S4, sending a BIOS out-of-band option command to the BIOS of the host side, and sending a restart command to the host side, so that the host side sets a corresponding root port register based on the BIOS out-of-band option command to enable the volume device management function.

[0033] Specifically, the motherboard management controller can receive an instruction to enable the hard disk volume device management function and obtain the hard disk information sent by the host. For example, the motherboard management controller receives an external instruction to enable the hard disk volume device management function. This instruction can come from the management platform, the administrator's operating interface, or an automated script. The hard disk information sent by the host may include the location number, model, capacity, serial number, etc. of the hard disk. That is, by receiving external instructions, the enabling process of the hard disk volume device management function can be automatically started, reducing manual intervention, and obtaining the latest hard disk information from the host in real time to ensure that subsequent operations are based on accurate hardware status.

[0034] After receiving the power-on instruction, the system responds to the power-on instruction and determines the root port number corresponding to the target hard disk in the hard disk in place based on the hard disk information. In other words, the received power-on instruction is confirmed and processing begins. If the instruction is invalid or the format is incorrect, an error message may be returned. The hard disk information obtained from the host is parsed to identify which hard disks are target hard disks (i.e., hard disks that need to enable the VMD function and the hard disks have been normally installed in the corresponding positions), and further parse the PCIe (Peripheral Component Interconnect Express) root port number of the target hard disk. This port number is the interface identifier for the hard disk to be connected to the host. For example, the root port number can be determined through a pre-set correspondence. For example, the relationship between the position number of the hard disk information and the root port number can be pre-determined. After the position number is determined, the root port number can be obtained by directly calling the correspondence.

[0035] After determining the root port number, the basic input / output system out-of-band option command can be determined based on the root port number. Based on the root port number of the target hard drive, an out-of-band option command (such as a Redfish command) is generated. This command is used to configure the basic input / output system (BIOS) settings and enable the VMD function of the target hard drive. Among them, the out-of-band option command is a command sent through an out-of-band management interface (such as IPMI (Intelligent Platform Management Interface) or Redfish) and is used to configure the basic input / output system settings. BIOS is the firmware on the server motherboard, responsible for hardware initialization and self-test, and guiding the operating system startup. Therefore, by generating out-of-band option commands, the BIOS settings can be automatically configured without manual intervention, avoiding errors caused by manually configuring BIOS settings and improving system stability and reliability.

[0036] After determining the basic input and output system out-of-band option command, the basic input and output system out-of-band option command can be sent to the basic input and output system on the host side, and a restart command can be sent to the host side, so that the host side sets the corresponding root port register based on the basic input and output system out-of-band option command to enable the volume device management function. Among them, the root port register is a hardware register in the PCIe bus architecture, which is used to control and manage PCIe devices. In addition, the BIOS settings are usually loaded when the system starts. Restarting the host is to make the BIOS settings take effect, so it is necessary to restart the host to apply the new settings. Therefore, when the host restarts, the BIOS modifies the configuration of the root port register according to the received out-of-band option command to enable the volume device management function and ensure that the hardware device can work normally.

[0037] This can solve the problems in the related technology of using BIOS configuration script methods that are not suitable for customer production environments and that writing or generating scripts is cumbersome, the problem of using BIOS code processing methods that increase boot time and code maintenance costs, as well as version compatibility issues, and the problem of using hardware methods that increase costs and design time. Customers can choose to partially or fully enable hard disk information, and automatically find the root port where the hard disk where the VMD function is to be enabled is located, which is convenient for customer function customization and deployment of VMD functions at customer sites, thereby improving product competitiveness, reducing the manpower hours of manually enabling or customizing BIOS versions or writing and setting BIOS scripts in the BIOS interface, saving labor costs and improving efficiency.

[0038] According to one embodiment of the present application, the motherboard management controller is communicatively connected to the hard disk backplane controller, and the method for enabling the volume device management function also includes: obtaining the hard disk presence information provided by the hard disk backplane controller; and determining whether the hard disk is in place based on the hard disk information and presence information of each hard disk.

[0039] Specifically, the hard drive backplane controller is a dedicated chip on the hard drive backplane that manages the physical connection and status detection of the hard drive. It can detect whether the hard drive is in place (that is, whether the hard drive is inserted into the backplane slot) and provide hard drive presence information, including the hard drive's physical location and connection status, as well as manage the hard drive's power and data connections. The motherboard management controller communicates with the hard drive backplane controller. For example, the motherboard management controller communicates with the hard drive backplane controller via I2C (Inter-Integrated Circuit, a communication bus between integrated circuits). I2C is a simple bidirectional two-wire synchronous serial bus suitable for short-distance, low-speed communication. That is, the motherboard management controller sends a request to the hard drive backplane controller to obtain the hard drive's presence information. After receiving the request, the hard drive backplane controller reads the hard drive's presence status and sends the status information back to the motherboard management controller via the I2C bus.

[0040] This allows you to obtain the hard drive presence information provided by the hard drive backplane controller, such as the physical location: the hard drive's physical location number on the backplane. Connection status: whether the hard drive is inserted into the backplane slot (in place or not). Power status: whether the hard drive is powered on. Communication status: whether the hard drive can communicate normally (for example, the connection status of the Serial Advanced Technology Attachment interface). After obtaining the presence information, you can determine whether the hard drive is in place based on the hard drive information and the presence information for each hard drive. If the hard drive information and the presence information are consistent (that is, the hard drive is in place and recognized by the BIOS or operating system), the hard drive is confirmed to be in place. If the hard drive information and the presence information are inconsistent (for example, the BIOS or operating system detects the hard drive, but the hard drive backplane controller reports that the hard drive is not in place), the hard drive is confirmed to be not in place.

[0041] Therefore, the BIOS and BMC's recognition of the hard disk's presence confirm each other. The VMD function is enabled only after the hard disk is confirmed to be in place, preventing crashes and other abnormal problems caused by the mistaken activation of VMD on the root port of other devices, thereby improving system stability.

[0042] Further, according to one embodiment of the present application, the hard disk information includes a position number of the hard disk, and determining whether the hard disk is in place is based on the hard disk information and the in-place information of each hard disk, including: for the position number of each hard disk, judging whether the position number and the in-place information match; if the position number corresponds to a corresponding hard disk and the in-place information corresponds to a corresponding hard disk, determining that the hard disk is in place; if the position number corresponds to a corresponding hard disk but the in-place information corresponds to no corresponding hard disk, determining that the hard disk is not in place.

[0043] Specifically, the hard disk information includes the hard disk location number. When determining whether a hard disk is in place based on the hard disk information and the presence information of each hard disk, for each hard disk location number, a determination is made as to whether the location number matches the presence information. That is, the location number of each hard disk is extracted from the hard disk information, and the location number and presence status of each hard disk are extracted from the presence information provided by the hard disk backplane controller. For each hard disk location number, a check is made to see whether the location number exists in both the hard disk information and the presence information. The location number in the hard disk information is compared with the location number in the presence information to see whether it matches, and the hard disk corresponding to the location number in the presence information is checked. If the location number in the hard disk information matches the location number in the presence information, and the presence information indicates that the hard disk corresponding to the location number is in place, then the hard disk is determined to be in place. If the location number in the hard disk information matches the location number in the presence information, but the presence information indicates that the hard disk corresponding to the location number is not in place, then the hard disk is determined to be out of place. If the location number in the hard disk information does not exist in the presence information, then the hard disk is determined to be out of place.

[0044] Suppose the following hard drive information and presence information are available: Hard drive 1: Position number 1, model SSD123, capacity 1TB; Hard drive 2: Position number 2, model SSD456, capacity 2TB; Hard drive 3: Position number 3, model SSD789, capacity 500GB. The presence information includes Position number 1: hard drive present, Position number 2: hard drive absent, and Position number 3: hard drive present. During the comparison process, for Hard drive 1, the position number in the hard drive information is 1, and the hard drive corresponding to position number 1 in the presence information is present. Therefore, it can be concluded that Hard drive 1 is present. For Hard drive 2, the position number in the hard drive information is 2, and the hard drive corresponding to position number 2 in the presence information is absent. Therefore, it can be concluded that Hard drive 2 is absent. For Hard drive 3, the position number in the hard drive information is 3, and the hard drive corresponding to position number 3 in the presence information is present. Therefore, it can be concluded that Hard drive 3 is present.

[0045] By comparing hard drive information and presence information, the presence status of each hard drive can be accurately monitored. If a hard drive is not in place or has an abnormal connection, an alarm can be promptly detected and issued, reducing the risk of data loss due to hardware failure. Double verification allows for more reliable determination of hard drive status and reduces false alarms. The root port number corresponding to the desired hard drive can then be determined among the available hard drives, enabling the corresponding volume device management functions.

[0046] According to an embodiment of the present application, the method for enabling volume device management function further includes: determining a target fault type when the hard disk is not in place; and determining corresponding alarms and processing measures based on the target fault type.

[0047] Specifically, when a hard drive is not present, the target fault type can be determined in a variety of ways. For example, the target fault type may include a hardware fault, which can be determined by monitoring the hardware status of the hard drive backplane (e.g., indicators, hardware interfaces). If the backplane hardware interfaces have a short circuit, open circuit, or poor contact, the hard drive may not be correctly identified. A fault in the hard drive itself (e.g., damage, aging, etc.) may also prevent the drive from being detected. This can be determined, for example, by monitoring the hard drive's hardware status (e.g., temperature, voltage, etc.). The cable connecting the hard drive to the backplane can also be checked for looseness, damage, or poor contact. A faulty cable can prevent the hard drive from being correctly identified. The target fault type may also include a software fault, which can be determined by checking whether the hard drive identification and management options are correctly configured in the BIOS. Incorrect BIOS settings may prevent the hard drive from being correctly identified. The target fault type also includes checking whether communication between the BMC and the hard drive backplane controller is normal. A communication failure may prevent the hard drive's presence information from being correctly transmitted to the BMC.

[0048] After determining the target fault type, corresponding alarms and handling measures can be determined based on the target fault type. For example, in the case of a hard drive failure, the BMC can send an alarm message to notify the administrator of a possible hard drive failure and recommend that the administrator check the hard drive's hardware status and replace the hard drive if necessary. In the case of a BIOS setting error, the BMC can send an alarm message to notify the administrator of a possible BIOS setting error and recommend that the administrator enter the BIOS setup interface to check and correct the hard drive identification and management options. This allows the fault type to be quickly determined and appropriate alarm and handling measures to be taken, even when the hard drive is not in place, ensuring stable system operation.

[0049] According to one embodiment of the present application, corresponding alarms and processing measures are determined based on the target fault type, including: when the target fault type is a hard disk hardware failure, a first-level alarm signal is issued, and the processing measure of replacing the hard disk is determined; when the target fault type is a mismatch between the hard disk and the basic input / output system configuration, a second-level alarm signal is issued, and the processing measure of reconfiguring the basic input / output system is determined; when the target fault type is a connection failure between the hard disk and the hard disk backplane, a third-level alarm signal is issued, and the processing measure of re-inserting the hard disk is determined, wherein the priority of the first-level alarm signal is greater than the priority of the second-level alarm signal, and the priority of the second-level alarm signal is greater than the priority of the third-level alarm signal.

[0050] Specifically, when determining the corresponding alarm and handling measures based on the target fault type, the target fault type is determined. If the target fault type is a hard drive hardware failure, a Level 1 alarm signal is issued and the handling measure of replacing the hard drive is determined. In other words, if the hard drive itself is faulty, such as damaged, aged, or malfunctioning, the alarm signal is a Level 1 alarm signal with the highest priority (the highest priority indicates a serious problem requiring immediate attention). An emergency alert can be sent through the BMC, such as an audible and visual alarm, email notification, or SMS notification. The alert clearly indicates "hard drive hardware failure" and specifies the specific hard drive location (such as the drive number and slot). A recommendation is also given to immediately replace the faulty hard drive. For example, the server can be shut down to ensure safety, the faulty hard drive removed, and replaced with a new one. The server can then be restarted to check whether the new drive is correctly recognized. Furthermore, if the hard drive contains important data, a backup of the data can be performed in advance.

[0051] If the target fault type is a mismatch between the hard drive and the Basic Input / Output System (BIOS) configuration, a Level 2 alarm signal can be issued, and action to reconfigure the BIOS can be determined. This means that the hard drive is not functioning properly because the BIOS settings do not match the actual hard drive configuration, such as an incorrect hard drive interface type or mode setting. This alarm signal is a Level 2 alarm signal with a medium priority (lower priority than a hard drive hardware failure, but still requiring prompt attention). A medium-priority alert can be sent through the BMC, such as an email notification or system log entry, with a clear message stating "The hard drive does not match the BIOS configuration" and identifying the specific issue (e.g., incorrect interface type or mode setting). Suggestions for reconfiguring the hard drive settings in the BIOS are also provided. For example, entering the BIOS setup interface, check whether the hard drive interface type is set correctly and whether the hard drive mode setting is consistent with the actual hard drive requirements. Finally, save the settings and restart the server to verify that the hard drive is correctly recognized.

[0052] If the target fault type is a connection failure between the hard drive and the drive backplane, a Level 3 alarm signal will be issued, and the action of reseating the drive will be determined. This means that the hard drive is not functioning properly due to a problem with the connection between the hard drive and the drive backplane, such as a loose, damaged, or poorly connected cable. A Level 3 alarm signal, with the lowest priority (lowest priority, but still requiring action), will be issued. A low-priority alert will be sent through the BMC, such as a system log entry or console prompt, clearly indicating "hard drive connection failure to backplane" and the specific drive location (such as drive number and slot). Recommendations for reseating the drive will also be provided to ensure a secure connection. For example, the server can be shut down for safety, and the cable connecting the hard drive to the backplane can be checked for looseness or damage. The hard drive can then be reseated to ensure a secure connection. Finally, the server can be restarted to verify that the drive is correctly recognized.

[0053] In this way, the reason why the hard disk is not in place can be quickly located, and corresponding alarms and processing measures can be taken to ensure the stable operation of the system.

[0054] According to an embodiment of the present application, sending a BIOS out-of-band option command to a host BIOS includes sending the BIOS out-of-band option command to the host BIOS based on a shared memory.

[0055] Specifically, when sending a BIOS out-of-band option command to the host-side BIOS, the BIOS out-of-band option command can be sent to the host-side BIOS via shared memory or a network interface. Shared memory is an efficient inter-process communication mechanism that allows different processes to directly access the same memory area. When sending via shared memory, the BMC first generates a BIOS out-of-band option command based on user input. The BMC writes the generated command to a predefined shared memory area. The host-side BIOS periodically checks the shared memory area during the startup process or runtime, reads and parses the command, and finally, the host-side BIOS performs the corresponding operation (such as enabling the VMD function) based on the parsed command content.

[0056] For example, reference Figure 2The figure shows a simplified internal architecture of a server, including the host CPU (Central Processing Unit), BMC, shared memory, and multiple NVMe drives (16 interfaces corresponding to 16 NVMe drives are shown in the figure). The host CPU is the server's main processor, responsible for performing computing tasks. The root port is the PCIe interface provided by the CPU for connecting high-speed devices, in this case NVMe drives. NVMe drives are non-volatile storage devices that use PCIe interfaces and provide high-speed data access. The DMI (Direct Media Interface) / ESPI (Enhanced Serial Presence Interface) bus is used for communication between the host and the BMC. The BMC is responsible for out-of-band management of the server, including hardware monitoring and remote management. Shared memory is a memory area accessible to the CPU and BMC, used to transfer data between them. Therefore, the BIOS collects drive information during system startup and sends this information to the BMC via shared memory. The user can send commands (such as IPMI and Redfish commands) through the BMC. The BMC parses the commands and generates corresponding operations. Based on the parsed commands, the BMC sends an out-of-band option command to the CPU through the DMI / ESPI bus to enable the VMD function of the specified NVMe drive. After receiving the command, the CPU performs a reboot and parses the out-of-band option command sent by the BMC during the reboot process to set the corresponding root port registers to enable the VMD function.

[0057] Therefore, using shared memory can reduce communication latency and improve command transmission efficiency. Communication between the BMC and the host BIOS does not require a network, resulting in faster communication. This approach enables efficient and flexible transmission and execution of BIOS out-of-band option commands, improving system stability and user experience.

[0058] According to one embodiment of the present application, in response to the turn-on indication, and based on the hard disk information, determining the root port number corresponding to the target hard disk in the in-place hard disk includes: determining the position number of the hard disk for which the volume device management function needs to be enabled based on the turn-on indication; determining the root port number based on the position number and a preset mapping relationship, wherein the preset mapping relationship is used to indicate the relationship between the position number and the root port number.

[0059] Specifically, when determining the root port number of the target hard drive among the currently installed hard drives based on the enable instruction and hard drive information, the location number of the hard drive for which the volume device management function needs to be enabled can be determined based on the enable instruction. Specifically, an enable instruction is a command issued to the system by a user through some method (e.g., a user can select the hard drive for which the VMD function needs to be enabled through a management interface provided by the BMC (e.g., a web interface)) to specify the hard drive for which the volume device management function (VMD) needs to be enabled. These enable instructions typically include the location number of the hard drive or other identification information. After receiving the enable instruction, the BMC parses its content and extracts the location number of the hard drive for which the VMD function needs to be enabled.

[0060] After determining the location number, the root port number can be determined based on the location number and a preset mapping relationship. The preset mapping relationship is the mapping between the hard drive location number and the root port number, which is used to quickly locate the corresponding root port number of the hard drive. For example, the root port number corresponding to hard drive location number 1 is 0x01, the root port number corresponding to hard drive location number 2 is 0x02, and the root port number corresponding to hard drive location number 3 is 0x03. Alternatively, the mapping table can be stored in the BMC's memory or in a persistent storage medium (such as EEPROM).

[0061] For example, after receiving a power-on instruction, the BMC parses its content and extracts the location number of the hard drive for which VMD needs to be enabled. For example, the power-on instruction includes "location number 1." The BMC obtains hard drive presence information from the hard drive backplane controller via the I2C bus or other communication methods. This information includes whether a hard drive is present in each slot and the drive's unique identifier (such as its serial number). The BMC compares the location number specified in the power-on instruction with the hard drive presence information to confirm the presence of the hard drive corresponding to that location number. If the hard drive is not present, an alarm is issued, notifying the user that the hard drive is missing. If the hard drive is present, the BMC searches for the root port number corresponding to that location number based on a preset mapping. For example, if the location number is 1, the preset mapping table determines that the root port number is 0x01. Finally, based on the found root port number, the BMC generates a BIOS out-of-band option command to enable VMD for the specified root port.

[0062] Therefore, by turning on the indication and pre-setting the mapping relationship, the root port number of the target hard disk can be automatically determined without manual intervention, which improves the convenience and efficiency of operation, reduces the risks caused by manual configuration errors, and improves the stability of the system.

[0063] According to an embodiment of the present application, receiving an instruction to enable the hard disk volume device management function includes: receiving an instruction to enable the hard disk volume device management function based on one of an IPMI command, a Redfish command, or a web button command.

[0064] Specifically, when receiving an instruction to enable the hard disk volume device management function, the instruction to enable the hard disk volume device management function can be received using one of the following: an IPMI command, a Redfish command, or a web page button command. For example, a user can send a specific IPMI command through an IPMI (Intelligent Platform Management Interface) client tool, which contains an instruction to enable the VMD function. After receiving the command from the IPMI client, the BMC parses the command content and recognizes that it is an instruction to enable the VMD function. The BMC then determines the specific hard disk for which the VMD function needs to be enabled based on the parameters in the command (such as the hard disk location number).

[0065] Users can also send a Redfish command through an HTTP (HyperText Transfer Protocol) client tool or management software. This command, sent as an HTTP request, contains JSON data for enabling the VMD function. The BMC, acting as a Redfish server, receives the HTTP request from the client, parses the JSON data, recognizes it as an instruction to enable VMD, and then determines the specific hard disks for which VMD should be enabled based on the parameters in the JSON. After enabling VMD, the BMC provides feedback to the user via an HTTP response message. If the operation succeeds, a status code and a success message are returned; if it fails, an error status code and error message are returned.

[0066] Users can also trigger the VMD feature by clicking a button or selecting a menu option through a server management interface (such as a web interface). The web interface converts the user's action into an HTTP request using JavaScript or other front-end technologies and sends it to the server's management interface. As the back-end implementer of the web management interface, the BMC receives the HTTP request from the web interface, parses the request content, and recognizes it as an instruction to enable the VMD feature. Based on the parameters in the request (such as the hard drive location number), the BMC determines the specific hard drive for which VMD should be enabled. After the BMC performs the VMD feature enablement operation, it returns the results to the web interface, where the user can view them. If the operation is successful, a success message is displayed; if it fails, an error message is displayed.

[0067] Therefore, by supporting three methods: IPMI commands, Redfish commands, and web button commands, it is possible to flexibly receive instructions to enable the hard disk volume device management function. These three methods each have their own characteristics and are suitable for different usage scenarios and user needs. For example, IPMI commands are suitable for out-of-band management scenarios that require high compatibility and powerful functions, and are suitable for use by professional operation and maintenance personnel. Redfish commands are suitable for modern data center management, easy to integrate with automation tools, and suitable for scenarios that require efficient management and large-scale deployment. Web button commands are suitable for user-friendly local and remote management, providing an intuitive operating experience through a graphical interface, and are suitable for daily operation and maintenance and non-professional users. In this way, the needs of different users can be met, providing a flexible, efficient, and secure management method.

[0068] The following combination Figure 3 To describe the method of this application.

[0069] As a specific example, the method for enabling the volume device management function of the present application may include the following steps:

[0070] S101, receiving an instruction to enable a hard disk volume device management function based on one of an IPMI command, a Redfish command, or a web button command, and obtaining a location number sent by a host and hard disk presence information provided by a hard disk backplane controller.

[0071] S102: Determine the location number of the hard disk for which the volume device management function needs to be enabled based on the enable instruction.

[0072] S103: Determine whether the location number of each hard disk matches the in-place information. If yes, go to step S104; if not, go to step S108.

[0073] S104: Determine a root port number based on the position number and a preset mapping relationship, wherein the preset mapping relationship is used to indicate a relationship between the position number and the root port number.

[0074] S105 : Determine a basic input / output system out-of-band option command based on the root port number.

[0075] S106 : Sending the BIOS out-of-band option command to the BIOS on the host side based on the shared memory.

[0076] S107, sending a BIOS out-of-band option command to the BIOS of the host side based on the shared memory, and sending a restart command to the host side, so that the host side sets a corresponding root port register based on the BIOS out-of-band option command to enable the volume device management function.

[0077] S108: Determine a target fault type, and determine corresponding alarms and processing measures based on the target fault type.

[0078] In summary, according to the method for enabling the volume device management function of the embodiment of the present application, an instruction to enable the hard disk volume device management function is received, the hard disk information sent by the host side is obtained, and in response to the enable instruction, the root port number corresponding to the target hard disk in the hard disk in place is determined based on the hard disk information, a basic input and output system out-of-band option command is determined based on the root port number, the basic input and output system out-of-band option command is sent to the basic input and output system of the host side, and a restart command is sent to the host side so that the host side sets the corresponding root port register based on the basic input and output system out-of-band option command to enable the volume device management function. Therefore, this method can facilitate customer function customization and deployment of VMD functions on-site, enhance product competitiveness, save labor costs and improve efficiency.

[0079] Figure 4 The figure is a flowchart of a method for enabling volume device management function according to an embodiment of the present invention.

[0080] like Figure 4 As shown, the method for enabling the volume device management function according to an embodiment of the present invention may include the following steps:

[0081] S10, after the basic input and output system of the host side performs a power-on self-test, hard disk information is sent to the mainboard management controller side.

[0082] S11, after receiving the restart command sent by the motherboard management controller, executing the restart operation, and parsing the basic input and output system out-of-band option command sent by the motherboard management controller during the restart process.

[0083] S12: Setting a corresponding root port register based on a basic input / output system out-of-band option command to enable a volume device management function.

[0084] Specifically, when the host is powered on, the BIOS performs a power-on self-test (POST). During the POST, the BIOS detects the status of hardware devices (including hard drives) and initializes them. Specifically, the POST identifies all NVMe hard drives connected to the host and obtains relevant information, such as the drive's unique identifier (e.g., serial number) and location number. The drive information collected by the BIOS during the POST is organized into an asset information table, which contains detailed information about all identified drives, such as model, capacity, and location number. After the POST completes, the BIOS sends this drive asset information to the BMC via a predefined communication mechanism. For example, the BIOS can write the drive information to a specific area in shared memory or send it to the BMC via the IPMI protocol. This ensures that all hardware devices (including hard drives) are correctly identified and initialized, and that the BIOS promptly transmits drive information to the BMC, providing accurate hardware information for enabling the VMD function.

[0085] After receiving a reboot command from the BMC, the system executes a reboot and parses the Basic Input / Out-of-Band Option Commands sent by the BMC during the reboot process. Specifically, after processing the hard drive information (for example, determining the hard drives and their root port numbers for which VMD needs to be enabled), the BMC generates a reboot command and sends it to the host BIOS. Upon receiving the reboot command, the BIOS triggers a host reboot and re-enters the POST phase during the reboot process. During the reboot process, the BIOS checks for an out-of-band option command from the BMC. If so, it parses the command content. For example, the command may include the root port number for enabling VMD. Based on the parsed command content, the BIOS determines the specific action to be performed (such as enabling VMD). This allows the BIOS to promptly receive and respond to reboot commands sent by the BMC, ensuring that the system operates according to the intended process. Automatically parsing out-of-band option commands during the reboot process reduces manual intervention and improves operational automation. Through the reboot process, the BIOS can dynamically update the system configuration based on the out-of-band option command, such as enabling VMD.

[0086] Finally, the corresponding root port registers are set based on the out-of-band option commands sent by the input and output systems to enable volume device management. Specifically, during the reboot process, the BIOS parses the out-of-band option commands sent from the BMC and extracts key information, such as the root port number for enabling VMD. The out-of-band option command is a command containing specific operation parameters. Based on the extracted root port number, the BIOS locates the corresponding PCIe root port registers. These PCIe root port registers are hardware registers that control PCIe devices (such as NVMe drives). VMD can be enabled or disabled by setting these registers.

[0087] The BIOS sets the corresponding root port registers based on the out-of-band option command. For example, by setting a specific bit in the root port register to "1" to enable the VMD function, the VMD function is enabled and the system can begin managing NVMe drives. Furthermore, after the BIOS completes the register setting, it reports the operation results to the BMC. If the operation is successful, the BIOS sends a success signal; if the operation fails, the BIOS sends an error signal with specific error information. Thus, by setting the root port registers, the BIOS can dynamically enable the VMD function without the user having to manually enter the BIOS setup interface.

[0088] As a result, the host side can efficiently enable the volume device management function. This process not only improves the system's automation level and user experience, but also enhances the system's performance and stability.

[0089] According to one embodiment of the present application, parsing a basic input / output system out-of-band option command sent by a motherboard management controller includes: parsing the basic input / output system out-of-band option command based on a data format of the basic input / output system out-of-band option command, and determining a root port for which a volume device management function needs to be enabled.

[0090] Specifically, the data format of the BIOS out-of-band option command is a standardized structure used to describe the specific operations that need to be performed. The key information contained in the command includes: Command type: Identifies that this is a BIOS out-of-band option command. Operation code: Specifies the specific operation, such as enabling the VMD function. Parameters: Contains the specific information required to perform the operation, such as the root port number, hard disk location number, etc. For example, taking the Redfish protocol as an example, the data format of the BIOS out-of-band option command is a JSON object, such as "Action":"EnableVMD" indicates that this is a command to enable the VMD function, "RootPort":"0x01" indicates that the root port number 0x01 of the VMD function needs to be enabled, and "DriveLocation":"1" indicates that the hard disk location number is 1.

[0091] When parsing BIOS out-of-band option commands sent by the baseboard management controller, the command can be parsed based on its data format. Specifically, during the reboot process, the host BIOS receives the out-of-band option command from the BMC via a predefined communication mechanism. Upon receiving the command, the BIOS first verifies whether the command's data format conforms to expectations, checks whether the command contains necessary fields (such as the Action and Parameters fields), and ensures that the field values ​​conform to specifications. If the command format is correct, the BIOS parses the command's specific information, extracts the Action field to confirm that it is a command to enable the VMD function, extracts the RootPor value in the Parameters field to determine the root port number for enabling VMD, and extracts the DriveLocation value in the Parameters field to determine the hard drive location number. The BIOS then verifies the validity of the extracted parameters. For example, it checks whether the root port number is within the system's supported range and whether the hard drive location number corresponds to an actual hard drive. If the parameters are invalid, the BIOS can log an error message and send error feedback to the BMC.

[0092] Therefore, after parsing the command and verifying the validity of the parameters, the BIOS determines the specific root port, such as the BIOS searches for the root port number corresponding to the hard disk location number based on a preset mapping relationship (such as a mapping table between location number and root port number). In addition, in one embodiment of the present application, the BIOS checks whether the determined root port is already in an enabled state. If the root port is already enabled, the BIOS can skip repeated enabling operations. If the root port is not enabled, the BIOS continues to perform the enabling operation. Based on the determined root port number, the BIOS sets the corresponding root port register to enable the VMD function. For example, a specific bit in the root port register is set to 1 to enable the VMD function. After the BIOS completes the root port enabling operation, it feeds back the operation results to the BMC. If the operation is successful, the BIOS sends a success signal; if the operation fails, the BIOS sends an error signal with specific error information.

[0093] Therefore, by parsing the out-of-band option command sent by the BMC, the BIOS can automatically determine the root port on which the VMD function needs to be enabled, eliminating the need for the user to manually enter the BIOS setup interface for operation. This improves the system's automation and user experience, and also enhances system performance and stability.

[0094] According to an embodiment of the present application, sending hard disk information to the motherboard management controller includes: sending the hard disk information to the motherboard management controller based on shared memory.

[0095] Specifically, sending hard drive information to the BMC is a critical step, ensuring the BMC receives accurate hard drive status and configuration information for subsequent management operations. This information can be sent to the BMC via shared memory. Shared memory is an efficient inter-process communication mechanism that allows multiple processes to access the same memory area. In this scenario, the host BIOS and BMC can share a memory area for transmitting hard drive information. Shared memory is typically located in the host's physical memory, and the BIOS and BMC exchange data using predefined memory addresses and formats. During the power-on self-test (POST) process, the BIOS collects information about all hard drives connected to the system, including the drive model, capacity, location number, and PCIe bus port number. This information is organized into a structured data format, such as a fixed-length structure or a JSON object. After the POST process completes, the BIOS writes the collected hard drive information to a predefined shared memory area. For example, the BIOS might write the hard drive information to a specific address range in the shared memory, such as 0x00010000 to 0x0001FFFF. To ensure the BMC can read the hard drive information in shared memory promptly, the BIOS can use some mechanism to notify the BMC that the data is ready. For example, the BIOS can set a flag or send an interrupt signal to the BMC. The BMC periodically checks a specific address in shared memory or reads the hard drive information from shared memory after receiving the notification. This allows the BMC to parse the hard drive information and extract the required data, such as the hard drive's location number and the PCIe bus port number to which it is connected.

[0096] This ensures that the BMC obtains accurate hard disk information, allowing subsequent management operations, such as enabling volume device management.

[0097] In summary, according to the method for enabling volume device management functions in an embodiment of the present application, after the host's BIOS performs a power-on self-test, it sends hard disk information to the motherboard management controller. After receiving a restart command from the motherboard management controller, the host executes a restart operation. During the restart process, the motherboard management controller parses the BIOS out-of-band option command sent by the motherboard management controller and sets the corresponding root port register based on the BIOS out-of-band option command to enable volume device management functions. This method thus facilitates customer function customization and on-site deployment of VMD functions, enhancing product competitiveness, saving labor costs, and improving efficiency.

[0098] For ease of understanding, the interaction between the host side and the motherboard management controller side of the present invention is described in a specific embodiment. Figure 5 As shown, the interaction method of the embodiment of the present invention may include the following steps:

[0099] S201, after the basic input and output system of the host side performs a power-on self-test, hard disk information is sent to the mainboard management controller side.

[0100] S202: Receive an instruction to enable the hard disk volume device management function, and obtain hard disk information sent by the host.

[0101] S203 : In response to the start instruction, the root port number corresponding to the target hard disk in the hard disk in place is determined based on the hard disk information.

[0102] S204: Determine a basic input / output system out-of-band option command based on the root port number.

[0103] S205 , sending a BIOS out-of-band option command to the BIOS of the host side and sending a restart command to the host side.

[0104] S206 , after receiving the restart command sent by the motherboard management controller, executing the restart operation, and parsing the basic input and output system out-of-band option command sent by the motherboard management controller during the restart process.

[0105] S207: Setting a corresponding root port register based on the basic input / output system out-of-band option command to enable the volume device management function.

[0106] Corresponding to the above embodiment, the present application also proposes a computer-readable storage medium.

[0107] The computer-readable storage medium of the embodiment of the present application stores a program thereon, and when the program is executed by a processor, the method for enabling the volume device management function is implemented.

[0108] According to the computer-readable storage medium of the embodiment of the present application, by executing the above-mentioned method of enabling volume device management function, it is possible to facilitate customer function customization and deployment of VMD functions at the customer site, enhance product competitiveness, save labor costs and improve efficiency.

[0109] Corresponding to the above embodiment, the present application also proposes a motherboard management controller.

[0110] like Figure 6 As shown, the motherboard management controller 200 of an embodiment of the present application may include: a first memory 210, a first processor 220, and a program stored in the first memory 210 and executable on the first processor 220. When the first processor 220 executes the program, the above-mentioned method of enabling the volume device management function is implemented.

[0111] According to the electronic device of the embodiment of the present application, by executing the above-mentioned method of enabling volume device management function, it is possible to facilitate customer function customization and deploy VMD functions at the customer site, thereby improving product competitiveness, saving labor costs and improving efficiency.

[0112] Corresponding to the above embodiment, the present application also proposes an electronic device.

[0113] like Figure 7 As shown, the electronic device 300 of an embodiment of the present application may include: a second memory 310, a second processor 320, and a program stored in the second memory 310 and executable on the second processor 320. When the second processor 320 executes the program, the above-mentioned server verification method is implemented.

[0114] According to the electronic device of the embodiment of the present application, by executing the above-mentioned method of enabling volume device management function, it is possible to facilitate customer function customization and deploy VMD functions at the customer site, thereby improving product competitiveness, saving labor costs and improving efficiency.

[0115] Corresponding to the above embodiments, the present application also proposes a computer program product.

[0116] A computer program product according to an embodiment of the present application includes a computer program / instruction, and when the computer program / instruction is executed by a processor, the computer program / instruction implements the above-mentioned method for enabling volume device management function.

[0117] According to the computer program product of the embodiment of the present application, by executing the above-mentioned method of enabling volume device management function, it is possible to facilitate customer function customization and deployment of VMD functions at the customer site, thereby improving product competitiveness, saving labor costs and improving efficiency.

[0118] It should be noted that the logic and / or steps represented in flowcharts or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (e.g., a computer-based system, a system including a processor, or other system that can fetch and execute instructions from an instruction execution system, apparatus, or device). For purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (non-exhaustive list) of computer-readable media include the following: an electrical connection with one or more wires (electronic device), a portable computer disk cartridge (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and programmable read-only memory (EPROM or flash memory), fiber optic devices, and a portable compact disc read-only memory (CDROM). Furthermore, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing it in another suitable manner if necessary, and then storing it in a computer memory.

[0119] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above-described embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used: a discrete logic circuit having logic gate circuits for implementing logic functions on data signals, an application-specific integrated circuit having suitable combinational logic gate circuits, a programmable gate array (PGA), a field-programmable gate array (FPGA), etc.

[0120] Throughout this specification, reference to terms such as "one embodiment," "some embodiments," "examples," "specific examples," or "some examples" means that a specific feature, structure, material, or characteristic described in conjunction with that embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

[0121] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of the technical features being referred to. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of such features. Throughout the description of this application, "plurality" means at least two, for example, two, three, etc., unless otherwise specifically defined.

[0122] In this application, unless otherwise specified or limited, the terms "installed," "connected," "connect," "fixed," etc. should be understood in a broad sense. For example, they can refer to fixed connection, detachable connection, or integration; mechanical connection or electrical connection; direct connection or indirect connection through an intermediate medium; internal communication between two elements or interaction between two elements, unless otherwise specified. Those skilled in the art will understand the specific meanings of the above terms in this application based on specific circumstances.

[0123] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A method for enabling volume device management function, characterized in that: Applied to the motherboard management controller, the method includes: Receive the instruction to start the hard disk volume device management function and obtain the hard disk information sent by the host; In response to the opening instruction, and based on the position number in the hard disk information and a preset mapping relationship, determining a root port number corresponding to the target hard disk in the in-place hard disk, wherein the preset mapping relationship is used to indicate a relationship between the position number and the root port number; determining a basic input / output system out-of-band option command based on the root port number; The BIOS out-of-band option command is sent to the BIOS of the host side, and a restart command is sent to the host side, so that the host side sets a corresponding root port register based on the BIOS out-of-band option command to enable a volume device management function.

2. The method for enabling volume device management function according to claim 1, wherein: The motherboard management controller is communicatively connected to the hard disk backplane controller, and the method further comprises: Obtaining hard disk presence information provided by the hard disk backplane controller; Whether the hard disk is in place is determined based on the hard disk information and the presence information of each hard disk.

3. The method for enabling volume device management function according to claim 2, characterized in that: The hard disk information includes a location number of the hard disk, and determining whether the hard disk is in place based on the hard disk information and the in-place information of each hard disk includes: For each hard disk's position number, determining whether the position number matches the in-place information; If the position number corresponds to a corresponding hard disk and the presence information corresponds to a corresponding hard disk, then it is determined that the hard disk is in place; If the position number corresponds to a corresponding hard disk but the presence information corresponds to no corresponding hard disk, it is determined that the hard disk is not in place.

4. The method for enabling volume device management function according to claim 3, characterized in that: The method further comprises: In the case where the hard disk is not in place, determining a target fault type; Determine corresponding alarms and handling measures based on the target fault type.

5. The method for enabling volume device management function according to claim 4, characterized in that: The determining of corresponding alarms and handling measures based on the target fault type includes: In the case where the target fault type is the hard disk hardware failure, a first-level alarm signal is issued and a treatment measure of replacing the hard disk is determined; In the case where the target fault type is a fault in which the hard disk and the basic input / output system configuration do not match, a second-level alarm signal is issued, and a treatment measure of reconfiguring the basic input / output system is determined; When the target fault type is a connection failure between the hard disk and the hard disk backplane, a third-level alarm signal is issued, and the processing measures for re-inserting the hard disk are determined, wherein the priority of the first-level alarm signal is greater than the priority of the second-level alarm signal, and the priority of the second-level alarm signal is greater than the priority of the third-level alarm signal.

6. The method for enabling volume device management function according to claim 1, characterized in that: The step of sending the basic input / output system out-of-band option command to the basic input / output system of the host side includes: The basic input and output system out-of-band option command is sent to the basic input and output system of the host side based on the shared memory.

7. The method for enabling volume device management function according to claim 1, characterized in that: The receiving of the instruction to start the hard disk volume device management function includes: An instruction to start the hard disk volume device management function is received based on one of an IPMI command, a Redfish command, or a webpage button command.

8. A method for enabling volume device management function, characterized in that: Applied to the host side, the method includes: After the basic input and output system of the host side performs a power-on self-test, sending hard disk information to the mainboard management controller side; After receiving the restart command sent by the motherboard management controller, executing a restart operation, and parsing a basic input and output system out-of-band option command sent by the motherboard management controller during the restart process, wherein the basic input and output system out-of-band option command includes a root port number for enabling a volume device management function; A corresponding root port register is set based on the root port number in the basic input / output system out-of-band option command to enable a volume device management function, wherein the basic input / output system determines the corresponding root port register based on the root port number, and the root port register is a hardware register for controlling the hard disk and is used to enable or disable the volume device management function.

9. The method for enabling volume device management function according to claim 8, characterized in that: The parsing of the basic input / output system out-of-band option command sent by the mainboard management controller includes: The basic input / output system out-of-band option command is parsed based on a data format of the basic input / output system out-of-band option command to determine a root port for which a volume device management function needs to be enabled.

10. The method for enabling volume device management function according to claim 8, characterized in that: The sending of hard disk information to the mainboard management controller includes: The hard disk information is sent to the mainboard management controller end based on the shared memory.

11. A computer-readable storage medium, characterized in that A program is stored thereon, and when the program is executed by a processor, the method for enabling volume device management function according to any one of claims 1-7 or 8-10 is implemented.

12. A motherboard management controller, characterized in that: include: A first memory, a first processor, and a program stored in the first memory and executable on the first processor, wherein when the first processor executes the program, the method for enabling volume device management function according to any one of claims 1 to 7 is implemented.

13. An electronic device, characterized in that: include: A second memory, a second processor, and a program stored in the second memory and executable on the second processor, wherein when the second processor executes the program, the method for enabling volume device management function according to any one of claims 8 to 10 is implemented.

14. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instruction is executed by a processor, the method for enabling volume device management function according to any one of claims 1 to 7 or claims 8 to 10 is implemented.

Images