Method and system for communication between BMC and RAID card

By deploying an agent program in the operating system, communication between the BMC and the RAID card is realized through PCIe channels and USB interfaces, solving the communication silo problem caused by the lack of hardware support for MCTP over PCIe and MCTP over I2C, and improving the manageability and compatibility of the server.

CN121705054APending Publication Date: 2026-03-20RAMAXEL TECH SHENZHEN
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202511890086.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-12-15
Publication Date
2026-03-20

AI Technical Summary

Technical Problem

In environments lacking hardware support for MCTP over PCIe and MCTP over I2C, the BMC cannot communicate effectively with the RAID card, leading to server manageability and reliability issues.

Method used

An agent program is deployed in the operating system, using the operating system's PCIe channel as a communication relay station. Network communication between the BMC and the RAID card is established through the LPC or USB interface. Command and data transmission are performed using the Socket protocol and the PCIe channel, achieving bidirectional reliable transmission between the BMC and the RAID card.

Benefits of technology

Reliable communication between the BMC and the RAID card was achieved without relying on CPU support or motherboard I2C cabling, improving the flexibility of server design and hardware compatibility, and ensuring system manageability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121705054A_ABST
    Figure CN121705054A_ABST
Patent Text Reader

Abstract

The invention provides a BMC and RAID card communication method and system, and the method comprises the steps: deploying and operating an agent program in an operating system, and enabling the agent program to be automatically initialized when the system is started; the agent program configures and monitors a communication interface between the agent program and the BMC; the BMC sends a control command to the agent program; the agent program forwards the control command to RAID card firmware; and the agent program receives response data returned by the RAID card firmware, and returns the response data to the BMC. The method has the beneficial effects that the design flexibility of the server and the compatibility under different hardware combinations are remarkably improved, and the manageability of the system is completely realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a method and system for communication between a BMC and a RAID card. Background Technology

[0002] In server management, the Baseboard Management Controller (BMC) needs to communicate with various hardware components in the system to achieve remote monitoring, diagnostics, and control functions. Communication with the RAID card firmware (FW) is crucial, for operations such as creating, deleting, or querying RAID volumes. Currently, the Management Component Transport Protocol (MCTP) is widely used in the industry as the standard communication protocol between the BMC and the RAID card. This protocol has two main physical layer implementations: MCTP over PCIe based on the PCIe bus, and MCTP over I2C based on the I2C bus. MCTP over PCIe requires support from the BMC, CPU, and RAID card; while MCTP over I2C only requires support from the BMC and RAID card, with no special requirements for the CPU.

[0003] However, both of these mainstream technologies have limitations in specific application scenarios. Specifically, in some domestically developed servers, the CPU may not support the MCTP over PCIe protocol. Furthermore, due to motherboard design limitations, the PCIe slots reserved for RAID cards do not connect the necessary I2C signal lines to the BMC. This results in the inability to establish either MCTP over PCIe or MCTP over I2C communication paths, creating a communication island that prevents the BMC from performing necessary management and control of the RAID card, severely impacting the server's manageability and reliability.

[0004] Therefore, there is an urgent need for a new communication method that can reliably and effectively enable communication between the BMC and the RAID card in environments lacking MCTP over PCIe and MCTP over I2C hardware support, in order to fill the gap in existing technologies for such specific application scenarios. Summary of the Invention

[0005] The technical problem to be solved by this invention is to provide a method for BMC to communicate with RAID cards in an environment lacking hardware support for MCTP over PCIe and MCTP over I2C.

[0006] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is: a method for communication between a BMC and a RAID card, comprising the following steps: An agent program is deployed and run in the operating system, and the agent program is automatically initialized when the system starts; The agent program is configured to listen to the communication interface with the BMC; BMC sends control commands to the agent program; The agent program forwards the control commands to the RAID card firmware; The agent program receives the response data returned by the RAID card firmware and returns the response data to the BMC.

[0007] Furthermore, the step of automatically initializing the agent program when the system starts includes: The agent program is started via the system startup script; Automatically detects the device interface connected to the BMC; Obtain the network configuration information of the device interface; Configure the listening address of the proxy program according to the network configuration information.

[0008] Furthermore, obtaining the network configuration information of the device interface includes: Obtain the host IP address through system management BIOS type 42; Use server configuration commands to update system network settings.

[0009] Furthermore, the listening address of the configured proxy program includes: If the IP address of the device interface is successfully obtained, a TCP server bound to that IP address is created; If the IP address of the device interface is not successfully obtained, a TCP server listening on all local addresses will be created.

[0010] Furthermore, the communication between the BMC and the agent program adopts a Socket-based network communication protocol, and the communication link is a local area network over USB channel implemented through an LPC or USB interface.

[0011] Furthermore, the communication between the agent program and the RAID card firmware is conducted through the PCIe channel, using in-band communication to transmit commands and data.

[0012] Furthermore, the agent program parses and encapsulates the commands received from the BMC, converting them into an instruction format recognizable by the RAID card firmware.

[0013] Furthermore, the agent program packages the response data from the RAID card firmware according to a predetermined format and returns it to the BMC via a Socket.

[0014] The present invention also provides a system for BMC and RAID card communication, and a method for implementing BMC and RAID card communication as described above, comprising: The BMC module is used to generate and send control commands to the agent program. The agent module, deployed in the operating system, is used to forward commands and data between the BMC and the RAID card firmware; The RAID card firmware module is used to receive and execute commands from the agent program and return the execution results.

[0015] Furthermore, the agent module further includes: Communication interface configuration unit, used to configure the communication interface with BMC; Command forwarding unit, used for bidirectional data transmission between BMC and RAID card firmware; The data encapsulation unit is used to convert and encapsulate the transmitted data.

[0016] The beneficial effects of this invention are as follows: By introducing an agent program deployed in the operating system, a completely new communication path is established between the BMC and the RAID card, which does not rely on the CPU's support for MCTP over PCIe or the motherboard's I2C cabling connection; it cleverly utilizes the operating system's inherent support for the PCIe channel, using the agent program as a communication relay station to achieve bidirectional reliable transmission of BMC control commands and RAID card execution results; it effectively overcomes the industry problem that certain hardware platforms cannot implement BMC management of RAID functions due to the lack of underlying physical channels, significantly improves the flexibility of server design and compatibility under different hardware combinations, and ensures the complete realization of system manageability. Attached Figure Description

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

[0018] Figure 1 This is a flowchart illustrating the method for BMC and RAID card communication according to an embodiment of the present invention. Figure 2 This is a flowchart illustrating the agent program startup process according to an embodiment of the present invention. Figure 3 This is a flowchart of the command to create a TCP Server listening BMC according to an embodiment of the present invention; Figure 4This is a flowchart illustrating the process of the BMC sending control commands to the agent program according to an embodiment of the present invention. Figure 5 This is a system architecture diagram of BMC and RAID card communication according to an embodiment of the present invention. Detailed Implementation

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

[0020] It should be noted that the descriptions involving "first," "second," etc., in this invention are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of that feature. Furthermore, the technical solutions of the various embodiments can be combined with each other, but only on the basis of being achievable by those skilled in the art. When the combination of technical solutions is contradictory or impossible to implement, such a combination of technical solutions should be considered non-existent and not within the scope of protection claimed by this invention.

[0021] like Figure 1 As shown, an embodiment of the present invention is: a method for BMC to communicate with a RAID card, comprising the following steps: S1. Deploy and run the agent program in the operating system. The agent program is automatically initialized when the system starts.

[0022] In this embodiment, the agent (FW Agent) is a daemon that resides in the server operating system (such as Linux). Its core function is to act as a communication bridge between the BMC and the RAID card firmware when the traditional MCTP communication path is unavailable. To achieve seamless integration and automated management, the agent is configured as a system service and runs automatically upon operating system startup.

[0023] Furthermore, in step S1, such as Figure 2 As shown, the steps for the agent program to automatically initialize when the system starts include: S11. Start the agent program via the system startup script.

[0024] In this embodiment, the FW Agent is registered as a system startup service by creating a Systemd service unit file or an init.d script. When the OS starts, the system service manager automatically loads and runs the agent program, ensuring the continuous availability of management functions.

[0025] S12. Automatically detect the device interface connected to the BMC.

[0026] In this embodiment, after the agent program starts, it automatically scans and locates the physical device interface that communicates with the BMC. This interface is typically a network device simulated via LPC (Low Pin Count) or a USB bus, which appears as a standard network interface (such as usb0 or eth1) in the operating system. This simulated network channel is often referred to as LAN over USB. Automatic detection ensures that the agent program can accurately find the portal for communicating with the BMC.

[0027] S13. Obtain the network configuration information of the device interface.

[0028] In this embodiment, to establish a reliable Socket communication connection, the proxy program needs to obtain the IP address of the device interface found in step S12. Specifically, this includes: S131. Obtain the host IP address through System Management BIOS Type 42 (SMBIOS Type 42). For example... Figure 3 As shown.

[0029] SMBIOS (System Management BIOS) is a standard system management information interface. A Type 42 structure is dedicated to managing the host interface (MCHost Interface) information, which may contain a pre-configured IP address set by the BMC for the host. The agent program reads this structure by calling system tools such as dmidecode or directly parsing the / dev / mem memory device, thereby obtaining the pre-configured IP address used for communication with the BMC. This method enables static, firmware-level configuration of the IP address, avoiding the uncertainty of dynamic allocation.

[0030] S132. Use server configuration commands to update system network settings.

[0031] After successfully obtaining an IP address through SMBIOS, the agent program will call system network configuration commands (such as the lan set command of ipmitool or the Redfish interface) to set this IP address and subnet mask on the LPC / USB device interface found in step S12, thereby completing the network initialization of the communication port.

[0032] S14. Configure the listening address of the agent program according to the network configuration information.

[0033] In this embodiment, the proxy program will create a listening service based on the IP acquisition result, specifically including: If the device interface IP address is successfully obtained via SMBIOS type 42, a TCP server bound to that fixed IP address is created. This enhances security by ensuring that the agent only listens for BMC connections from that specific channel.

[0034] If the IP address of the device interface cannot be obtained due to platform differences or configuration reasons, as a fault tolerance mechanism, the proxy program will create a TCP server listening on all local addresses (INADDR_ANY) to ensure that the communication service can still be established in most cases.

[0035] S2. The agent program configures and listens to the communication interface with the BMC.

[0036] In this embodiment, after completing the above initialization, the FW Agent will start a TCP Socket server and begin listening for connection requests from the BMC on the configured IP address and specific port. Figure 5 As shown in the system architecture diagram, the communication link between the BMC and FWAgent is a socket-based network communication, with its physical layer implementing a LAN over USB channel via an LPC or USB interface. The BMC can send data to the FW Agent's listening address using ipmitool, redfish, or direct socket programming.

[0037] S3, BMC sends control commands to the agent program.

[0038] In this embodiment, as Figure 4 As shown, when the BMC needs to manage the RAID card (such as initiating operations like creating a RAID volume or querying RAID status), it will encapsulate the corresponding control commands into Socket data packets according to a predefined format and send them to the connected FW Agent through the LAN over USB channel established in step S2.

[0039] S4. The agent program forwards the control command to the RAID card firmware.

[0040] In this embodiment, after the FW Agent receives the Socket data from the BMC, it parses and processes it. For example... Figure 5 As shown, communication between the agent program and the RAID card firmware is conducted through the PCIe channel managed by the operating system kernel, which is an in-band communication method.

[0041] Furthermore, the agent program parses and encapsulates the commands received from the BMC, converting them into an instruction format recognizable by the RAID card firmware. For example, the FW Agent converts the request content in the Socket data packet into calling parameters for command-line tools (such as StorCLI) provided by the RAID card manufacturer, or delivers the commands to the RAID card firmware (Hamin RAID FW) of brands such as Haiming by directly reading and writing the PCIe configuration space or sending specific SCSI commands.

[0042] S5. The agent program receives the response data returned by the RAID card firmware and returns the response data to the BMC.

[0043] In this embodiment, after the RAID card firmware executes the command, it will return the result (such as successful creation, return of disk information, etc.) to the FW Agent through the PCIe in-band channel.

[0044] Furthermore, the agent program repackages the response data from the RAID card firmware according to a predetermined format (such as JSON, XML, or a custom binary structure) and then returns it to the BMC via the previously established Socket connection. After parsing this response, the BMC can complete the closed loop of the entire RAID card management operation, for example, displaying the operation results to the user on the BMC's web management interface.

[0045] like Figure 5 As shown, the present invention also provides a system for BMC and RAID card communication, for implementing the method of BMC and RAID card communication as described above, comprising: The BMC module, typically a standalone management chip (such as Aspeed 2400 / 2500), is used to generate and send control commands to the agent program and receive the returned response data.

[0046] The agent module (FW Agent) is deployed in the host operating system as a core relay station, used to forward commands and data between the BMC and the RAID card firmware.

[0047] The RAID card firmware module runs on the RAID card hardware and is used to receive and execute commands from the agent program and return the execution results.

[0048] Furthermore, the agent program module can be further divided in its software implementation as follows: The communication interface configuration unit is responsible for executing steps S12-S14, namely configuring the LPC / USB communication interface and network monitoring service with the BMC.

[0049] The command forwarding unit is responsible for executing the core forwarding logic of steps S3-S5, and transmitting data bidirectionally between the BMC and the RAID card firmware.

[0050] The data encapsulation unit is responsible for parsing, format conversion, and packaging the commands from the BMC and the response data from the RAID card, ensuring the correct conversion of the protocols between the two parties.

[0051] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent structural or procedural transformations made based on the content of the present invention's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A method for communication between a BMC and a RAID card, characterized in that, Includes the following steps: An agent program is deployed and run in the operating system, and the agent program is automatically initialized when the system starts; The agent program is configured to listen to the communication interface with the BMC; BMC sends control commands to the agent program; The agent program forwards the control commands to the RAID card firmware; The agent program receives the response data returned by the RAID card firmware and returns the response data to the BMC.

2. The method for BMC and RAID card communication according to claim 1, characterized in that, The steps for the agent program to automatically initialize when the system starts include: The agent program is started via the system startup script; Automatically detects the device interface connected to the BMC; Obtain the network configuration information of the device interface; Configure the listening address of the proxy program according to the network configuration information.

3. The method for BMC and RAID card communication according to claim 2, characterized in that, The method of obtaining the network configuration information of the device interface includes: Obtain the host IP address through system management BIOS type 42; Use server configuration commands to update system network settings.

4. The method for BMC and RAID card communication according to claim 2, characterized in that, The listening address of the configured agent program includes: If the IP address of the device interface is successfully obtained, a TCP server bound to that IP address is created; If the IP address of the device interface is not successfully obtained, a TCP server listening on all local addresses will be created.

5. The method for BMC and RAID card communication according to claim 1, characterized in that, The communication between the BMC and the agent program adopts a Socket-based network communication protocol, and the communication link is a local area network over USB channel implemented through an LPC or USB interface.

6. The method for BMC and RAID card communication according to claim 1, characterized in that, The communication between the agent program and the RAID card firmware is conducted through the PCIe channel, using in-band communication to transmit commands and data.

7. The method for BMC and RAID card communication according to claim 1, characterized in that, The agent program parses and encapsulates the commands received from the BMC, converting them into an instruction format recognizable by the RAID card firmware.

8. The method for BMC and RAID card communication according to claim 1, characterized in that, The agent program packages the response data from the RAID card firmware into a predetermined format and returns it to the BMC via a Socket.

9. A system for communication between a BMC and a RAID card, used to implement the method for communication between a BMC and a RAID card as described in any one of claims 1-8, characterized in that, include: The BMC module is used to generate and send control commands to the agent program. The agent module, deployed in the operating system, is used to forward commands and data between the BMC and the RAID card firmware; The RAID card firmware module is used to receive and execute commands from the agent program and return the execution results.

10. The system according to claim 9, characterized in that, The agent module further includes: Communication interface configuration unit, used to configure the communication interface with BMC; Command forwarding unit, used for bidirectional data transmission between BMC and RAID card firmware; The data encapsulation unit is used to convert and encapsulate the transmitted data.