A BMC firmware upgrade method and system in offline state

Abstract

The present invention belongs to the technical field of server management and firmware upgrades, and specifically relates to a method and system for upgrading BMC firmware in an offline state. First, an intelligent BMC firmware storage device is deployed in a server. Then, upon detecting the need for a BMC firmware upgrade or repair, the server sends a specified exception request signal to the intelligent BMC firmware storage device, which then parses the exception request signal. The intelligent BMC firmware storage device generates a response and, based on the server's specified BMC firmware version, sends corresponding BMC firmware version data to the BMC firmware. The BMC firmware receives and verifies the firmware version data. The BMC firmware then automatically upgrades based on the firmware version data, writing the new and verified BMC firmware version data to the BMC chip. This method enables automated upgrades and maintenance of the BMC firmware in an offline state, improving the reliability, stability, and efficiency of the server.

Description

Technical Field

[0001] The present invention belongs to the technical field of server management and firmware upgrade, and in particular relates to a method and system for upgrading BMC firmware in an offline state. Background Art

[0002] The Baseboard Management Controller (BMC) plays an increasingly important role in modern data center and server management. A BMC is an embedded management controller that allows administrators to remotely monitor, manage, and maintain server hardware and firmware, including power, temperature, fan speed, logging, and, most critically, firmware updates.

[0003] BMC firmware upgrades are a critical part of server maintenance, ensuring servers have the latest security, performance, and stability updates. Existing BMC firmware upgrade technologies rely heavily on a stable network connection. This means BMC firmware upgrades can only be performed when the network connection is functioning properly. In practice, server networks can face a variety of issues, such as network failures, misconfigurations, or network attacks, all leading to network outages. In these situations, existing technologies cannot perform BMC firmware upgrades, leaving potential security vulnerabilities and performance issues.

[0004] Performing BMC firmware upgrades during a network outage typically requires physical access to the server. This means administrators must physically visit the server room or data center to perform operations through serial ports or other physical interfaces. This physical access requirement increases maintenance complexity and costs, especially in large-scale server deployments, where significant human resources are required to manage the server's BMC firmware. Because existing technologies require manual intervention during a network outage, servers may be left unsecured. Administrators may not be able to promptly perform BMC firmware updates to address known security vulnerabilities, increasing potential risks, especially in security-critical environments. The need for physical access to servers and manual operations also leads to inefficient maintenance. Especially in large-scale server maintenance or upgrades, significant time and human resources are required, which can delay maintenance work and increase management costs. Furthermore, to prevent unexpected issues during the upgrade process, redundant backup areas are required. However, these redundant backup areas increase server storage resources and reduce server space utilization.

[0005] Therefore, it is urgent to solve the technical problems existing in the existing technology, such as the inability to upgrade the BMC firmware when a network failure occurs, resulting in security vulnerabilities, the need for a large amount of human resources to manage the server's BMC firmware, low maintenance efficiency, and the increase in the use of server device storage resources and reduced server space utilization caused by the redundant backup area of the equipment. Summary of the Invention

[0006] The present invention aims to provide a method and system for upgrading BMC firmware in an offline state, so as to solve the technical problems existing in the prior art, such as the inability to upgrade BMC firmware when a network failure occurs, resulting in security vulnerabilities, the need for a large amount of human resources to manage the server's BMC firmware, low maintenance efficiency, and the increased usage of server device storage resources and reduced server space utilization caused by setting up a redundant backup area for the device.

[0007] In order to solve the above technical problems, the technical solutions adopted by the present invention are as follows:

[0008] In a first aspect, a method for upgrading BMC firmware in an offline state is provided, comprising the following steps:

[0009] S1: deploying an intelligent BMC firmware storage device and a BMC upgrade and repair module in the server, wherein the intelligent BMC firmware storage device stores multiple BMC firmware versions, and starting the server;

[0010] S2: When the server detects that a BMC firmware upgrade is required, it sends a specified exception request signal to the intelligent BMC firmware storage device. The intelligent BMC firmware storage device parses the exception request signal and obtains server identification information and a specified BMC firmware version.

[0011] S3: The intelligent BMC firmware storage device generates a response and sends the corresponding BMC firmware version data to the BMC firmware according to the BMC firmware version specified by the server;

[0012] S4: The BMC firmware receives the firmware version data and verifies it, including the data signature and ensuring that the data has not been tampered with.

[0013] S5: The BMC firmware automatically upgrades according to the firmware version data, writing the new and verified BMC firmware version data into the BMC chip. Meanwhile, the upgrade process is monitored to determine whether there is an upgrade anomaly, such as a power failure. If so, step S6 is executed; otherwise, the automatic upgrade process continues.

[0014] S6: Start the BMC upgrade and repair module to process abnormal situations during the upgrade process through the BMC upgrade and repair module. After the abnormal situations are processed, repeat step S5 until the upgrade is successful.

[0015] Preferably, the multiple BMC firmware versions in step S1 are customized according to the manufacturers and models of the corresponding servers, and have adaptability and compatibility.

[0016] Preferably, after step S1, a secure local communication protocol needs to be established between the intelligent BMC firmware storage device and the BMC firmware to enable communication between the intelligent BMC firmware storage device and the BMC firmware without an external network.

[0017] Preferably, at the same time as step S3, the intelligent BMC firmware storage device also performs BMC firmware version management, tracking the history of each BMC firmware version, including verification, authentication and release date, and the BMC firmware version data is encrypted to ensure data confidentiality and integrity.

[0018] Preferably, at the same time as step S2, a server disconnection status detection is also performed, including the following specific steps:

[0019] S21: Start hardware-level heartbeat detection and set the heartbeat time interval in the underlying hardware configuration of the server;

[0020] S22: Within the set time interval, the underlying hardware of the server generates a hardware-level heartbeat signal;

[0021] S23: The BMC firmware checks the continuity of the heartbeat signal. If it does not receive a specified number of consecutive heartbeat signals, the server will be marked as disconnected.

[0022] S24: The BMC firmware triggers an automatic processing procedure, including communicating with the intelligent BMC firmware storage device to request a BMC firmware upgrade;

[0023] S25: When the server is disconnected from the network, the system records the relevant events and sends an alarm to notify the administrator;

[0024] S26: When the network is disconnected, the server will continue to try to send hardware-level heartbeat signals to restore the connection in time when the network is restored.

[0025] Preferably, the underlying hardware of the server in step S22 is part of a mainboard.

[0026] Preferably, during the automatic upgrade process in step S5, the intelligent BMC firmware storage device and the BMC firmware continuously record detailed upgrade process information, including the upgrade date, time, version number, and verification status.

[0027] Preferably, the specific process of the BMC upgrade and repair module in step S6 processing abnormal situations during the upgrade process is as follows:

[0028] S61: Reading upgrade data of a parameter configuration module in a BMC firmware version to be upgraded from a BMC firmware storage device, and obtaining an upgrade path for the upgrade data;

[0029] S62: Reading partition information of upgrade data in the BMC firmware version to be upgraded;

[0030] S63: Checking the legitimacy of partition information of the upgrade data in the BMC firmware version to be upgraded;

[0031] S64: performing an image upgrade of the corresponding partition according to the partition information of the upgrade data in the BMC firmware version to be upgraded, and not upgrading the partition of the loader and the repair program of the BMC upgrade and repair module during the image upgrade process;

[0032] S65: Clearing the upgrade data of the parameter configuration module in the BMC firmware version to be upgraded;

[0033] S66: The BMC upgrade and repair module completes the repair of the abnormal power failure and restarts the server.

[0034] In a second aspect, a BMC firmware upgrade system in an offline state is provided, comprising an intelligent BMC firmware storage device, a BMC firmware upgrade module, a BMC firmware upgrade detection module, a BMC upgrade repair module, and a parameter configuration module; the intelligent BMC firmware storage device is connected to the BMC upgrade repair module, the BMC firmware upgrade module is stored in the intelligent BMC firmware storage device, the BMC firmware upgrade detection module is connected to the BMC upgrade repair module and the BMC firmware upgrade detection module, and the parameter configuration module is connected to the BMC firmware upgrade module and the BMC firmware upgrade detection module;

[0035] The intelligent BMC firmware storage device is used to store the BMC firmware version;

[0036] The BMC firmware upgrade module is used to upgrade the BMC firmware;

[0037] The parameter configuration module is used to configure the parameters during the BMC firmware upgrade process;

[0038] The BMC firmware upgrade detection module is used to detect abnormal conditions during the BMC firmware upgrade process, including power failure;

[0039] The BMC upgrade and repair module is used to handle abnormal situations that occur during the upgrade process.

[0040] The beneficial effects of the present invention include:

[0041] The present invention provides a method and system for upgrading BMC firmware in an offline state. First, an intelligent BMC firmware storage device is deployed in a server. Then, the server detects that a BMC firmware upgrade or repair is required and sends a specified exception request signal to the intelligent BMC firmware storage device. The intelligent BMC firmware storage device parses the exception request signal. The intelligent BMC firmware storage device generates a response and sends corresponding BMC firmware version data to the BMC firmware according to the BMC firmware version specified by the server. The BMC firmware receives the firmware version data and verifies it. The BMC firmware performs an automatic upgrade based on the firmware version data and writes the new and verified BMC firmware version data into the BMC chip.

[0042] First, through the local area communication protocol between the intelligent BMC firmware storage device and the server, the server BMC firmware is automatically upgraded and maintained, ensuring that the server can still communicate with the intelligent storage device when the network connection is unavailable.

[0043] Secondly, the heartbeat detection mechanism in the server's underlying hardware is used to monitor the normal operation of the server in the event of a network disconnection, to detect whether the server is in a network disconnected state, and to identify the server's working status to ensure that appropriate measures are taken when upgrades or repairs are needed, thereby improving the reliability and stability of the server.

[0044] Thirdly, it can automatically detect the BMC firmware version required by the server, request it and upgrade it to the server, and realize automatic upgrade of BMC firmware in the disconnected state without manual intervention, which improves the automation and efficiency of server management and ensures timely update and stability of the system.

[0045] Finally, by setting up the BMC upgrade and repair module, we can avoid setting up redundant backup areas for devices, effectively reduce the storage resource usage of server devices, and improve server space utilization. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 The figure is a flow chart of the offline BMC firmware upgrade method of the present invention.

[0047] Figure 2 This is a flow chart of detecting the server disconnection status according to the present invention.

[0048] Figure 3 This is a schematic diagram of the architecture of the offline BMC firmware upgrade system of the present invention. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of this application.

[0050] The following is combined with Figure 1-Figure 3 The present invention is described in further detail:

[0051] Example 1

[0052] See attached Figure 1 As shown, a method for upgrading BMC firmware in an offline state includes the following steps:

[0053] S1: deploying an intelligent BMC firmware storage device and a BMC upgrade and repair module in the server, wherein the intelligent BMC firmware storage device stores multiple BMC firmware versions, and starting the server;

[0054] S2: When the server detects that a BMC firmware upgrade is required, it sends a specified exception request signal to the intelligent BMC firmware storage device. The intelligent BMC firmware storage device parses the exception request signal and obtains server identification information and a specified BMC firmware version.

[0055] S3: The intelligent BMC firmware storage device generates a response and sends the corresponding BMC firmware version data to the BMC firmware according to the BMC firmware version specified by the server;

[0056] S4: The BMC firmware receives the firmware version data and verifies it, including the data signature and ensuring that the data has not been tampered with.

[0057] S5: The BMC firmware automatically upgrades based on the firmware version data, writing the new and verified BMC firmware version data to the BMC chip. During the automatic upgrade process, the intelligent BMC firmware storage device and the BMC firmware continuously record detailed upgrade process information, including the upgrade date, time, version number, and verification status.

[0058] At the same time, the upgrade process is monitored to determine whether there is an upgrade anomaly, such as a power failure. If so, step S6 is executed; if not, the automatic upgrade process continues;

[0059] S6: Start the BMC upgrade and repair module to process abnormal situations during the upgrade process through the BMC upgrade and repair module. After the abnormal situations are processed, repeat step S5 until the upgrade is successful.

[0060] In this solution, the intelligent BMC firmware storage device is a core component. Its highly intelligent functionality and security address BMC firmware upgrade issues during network outages, improving server maintenance efficiency and security. Furthermore, the intelligent BMC firmware storage device can adapt to the needs of different server models and manufacturers, offering high flexibility and scalability.

[0061] After step S1, a secure local communication protocol is established between the intelligent BMC firmware storage device and the BMC firmware, enabling communication between the two devices without an external network. Simultaneously with step S3, the intelligent BMC firmware storage device also manages BMC firmware versions, tracking the history of each BMC firmware version, including verification, authentication, and release dates. This BMC firmware version data is encrypted to ensure confidentiality and integrity.

[0062] In another implementation of this embodiment, the BMC firmware upgrade is achieved through the following process. Downloading the BMC firmware: First, download the latest BMC firmware version that matches the server model from the server manufacturer's official website. Ensure that the downloaded firmware fully matches the server model to avoid incompatibility issues. Prepare the upgrade tools and environment: Before upgrading the BMC, you need a computer that can remotely connect to the server and install tools that support BMC firmware upgrades. Typically, the manufacturer provides the corresponding tools and documentation, which can be obtained from the official website. Connect to the server: Use a serial cable to connect the server's serial port to a management terminal device, such as a computer's serial port or a USB-to-serial cable. Then, use serial terminal software (such as Putty or SecureCRT) to open the serial port connection and set the serial port's baud rate, data bits, stop bits, and parity to match those of the server. Enter the BMC command line: In the serial terminal, find the BMC prompt and follow it to enter the BMC command line interface. ‌Back up existing BMC data‌: In the BMC command line interface, use commands to back up existing BMC data to prevent data loss or system crashes caused by problems during the upgrade.‌ ‌Flash the BMC firmware‌: Upload the latest downloaded BMC firmware file to the server and use the corresponding commands in the BMC command line interface to flash the firmware. A series of prompts and progress bars will appear during the flashing process. Wait patiently until it is complete.‌ ‌Verify the BMC firmware‌: After the flashing is complete, restart the server and connect to the BMC command line interface via a serial terminal. Use commands to check the version and status of the BMC firmware to ensure that the upgrade was successful.‌

[0063] Example 2

[0064] Based on Example 1, see Figure 2 At the same time as step S2, the server disconnection status detection is also performed, including the following specific steps:

[0065] S21: Start hardware-level heartbeat detection and set the heartbeat time interval in the underlying hardware configuration of the server;

[0066] S22: within a set time interval, the underlying hardware of the server generates a hardware-level heartbeat signal, where the underlying hardware of the server is part of the motherboard;

[0067] S23: The BMC firmware checks the continuity of the heartbeat signal. If it does not receive a specified number of consecutive heartbeat signals, the server will be marked as disconnected.

[0068] S24: The BMC firmware triggers an automatic processing procedure, including communicating with the intelligent BMC firmware storage device to request a BMC firmware upgrade;

[0069] S25: When the server is disconnected from the network, the system can record relevant events and send an alarm to notify the administrator;

[0070] S26: When disconnected from the network, the server will continue to try to send hardware-level heartbeat signals so that the connection can be restored in time when the network is restored.

[0071] The heartbeat detection mechanism ensures that the server can monitor its own status before the BMC firmware is properly loaded and take automatic measures when necessary, such as requesting a BMC firmware upgrade to restore network connectivity. This mechanism is critical during the server startup process because it protects the server's network connectivity before the BMC firmware is properly loaded.

[0072] The specific process for automatically upgrading the BMC firmware based on the firmware version data in step S5 is as follows: First, the packaged configuration file u_fw_layout.ini is parsed. The values of each field in each upgrade partition item (UserPartX (X = 1, 2, 3, ...)) in the configuration file are extracted and stored in the partition table information. The number of partitions to be upgraded in the upgrade package is then calculated, and the partition table and header information in the upgrade package partition information structure are populated to create the output upgrade package file u_firmware.img. The upgrade package header and partition table information are then written to the upgrade package binary file u_firmware.img. The image files corresponding to each partition are then written to the upgrade package binary file u_firmware.img. If the image file size is larger than the partition size, an error is returned. If the image file size is smaller than the partition size, u_firmware.img is padded with null characters after the image file is written to ensure that the image in the upgrade package is equal to the partition size. This eliminates the need for an erase process during subsequent upgrades, allowing the corresponding image in the upgrade package to be directly written to the corresponding physical partition, improving upgrade efficiency and ultimately completing the upgrade.

[0073] Example 3

[0074] Based on Example 1 or Example 2, the specific process of the BMC upgrade and repair module in step S6 processing abnormal situations during the upgrade process is as follows:

[0075] S61: Reading upgrade data of a parameter configuration module in a BMC firmware version to be upgraded from a BMC firmware storage device, and obtaining an upgrade path for the upgrade data;

[0076] S62: Reading partition information of upgrade data in the BMC firmware version to be upgraded;

[0077] S63: Checking the legitimacy of partition information of the upgrade data in the BMC firmware version to be upgraded;

[0078] S64: performing an image upgrade of the corresponding partition according to the partition information of the upgrade data in the BMC firmware version to be upgraded, and not upgrading the partition of the loader and the repair program of the BMC upgrade and repair module during the image upgrade process;

[0079] S65: Clearing the upgrade data of the parameter configuration module in the BMC firmware version to be upgraded;

[0080] S66: The BMC upgrade and repair module completes the repair of the abnormal power failure and restarts the server.

[0081] In step S63, the partition information of the upgrade data in the BMC firmware version to be upgraded is checked for legitimacy by checking the magic number (uiFwMagic) in the header information of the partition information to determine whether the magic number in the header information is equal to 0x5559444a. If not, it is an illegal firmware. If equal to 0x5559444a, it is determined to be a legal firmware.

[0082] The purpose of not upgrading the partitions containing the loader and the repair program for the BMC upgrade and repair module during the image upgrade in step S64 is to prevent the BMC upgrade and repair module's repair program from failing to recover due to unexpected events during its recovery. Clearing the upgrade data for the parameter configuration module in the BMC firmware version to be upgraded in step S65 is the process of erasing the upgrade mode flag, preventing the loader from being booted into repair mode after a successful upgrade.

[0083] See also Figure 3A BMC firmware upgrade system in an offline state includes an intelligent BMC firmware storage device, a BMC firmware upgrade module, a BMC firmware upgrade detection module, a BMC upgrade repair module, and a parameter configuration module; the intelligent BMC firmware storage device is connected to the BMC upgrade repair module, the BMC firmware upgrade module is stored in the intelligent BMC firmware storage device, the BMC firmware upgrade detection module is connected to the BMC upgrade repair module and the BMC firmware upgrade detection module, and the parameter configuration module is connected to the BMC firmware upgrade module and the BMC firmware upgrade detection module. The intelligent BMC firmware storage device is used to store the BMC firmware version; the BMC firmware upgrade module is used to upgrade the BMC firmware; the parameter configuration module is used to configure parameters during the BMC firmware upgrade process; the BMC firmware upgrade detection module is used to detect abnormal conditions during the BMC firmware upgrade process, including power failure; the BMC upgrade repair module is used to handle abnormal conditions that occur during the upgrade process.

[0084] The offline BMC firmware upgrade method and system provided by the present invention, on the one hand, enables automatic upgrades of BMC firmware even when the network is offline, without requiring physical access to the server. This is crucial for data center and remote server management. Regardless of server location, even without remote connectivity, administrators can maintain control and upgrades of the BMC firmware, ensuring server up-to-dateness and stability. Furthermore, the automatic upgrade and offline communication mechanisms simplify management processes, reducing operational risks and management complexity. Administrators can more easily manage the entire server cluster without relying on physical contact.

[0085] On the other hand, it provides real-time BMC firmware upgrades and maintenance, independent of network connectivity, ensuring that server firmware remains up-to-date at all times, increasing system reliability and stability. Even when disconnected from the network, the server can still automatically respond to upgrade requests and provide reliable service. Finally, a secure local area communication protocol has been introduced to ensure the confidentiality and integrity of communications. Compared to traditional physical access, this communication method is more secure and reduces potential security risks. Administrators can trust the communication protocol, ensuring that data will not be tampered with or leaked during the firmware upgrade process. At the same time, by setting up a BMC upgrade and repair module, the need for redundant backup areas for devices can be avoided, effectively reducing the storage resource usage of server devices and improving server space utilization.

[0086] The above-described embodiments merely illustrate specific implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of protection of the present application. It should be noted that a person skilled in the art would be able to make numerous variations and improvements without departing from the technical concept of the present application, all of which fall within the scope of protection of the present application.

Claims

1. A BMC firmware upgrade method in offline state, characterized in that: The following steps are involved: S1: deploying an intelligent BMC firmware storage device and a BMC upgrade and repair module in the server, wherein the intelligent BMC firmware storage device stores multiple BMC firmware versions, and starting the server; S2: When the server detects that a BMC firmware upgrade is required, it sends a specified exception request signal to the intelligent BMC firmware storage device. The intelligent BMC firmware storage device parses the exception request signal and obtains server identification information and a specified BMC firmware version. S3: The intelligent BMC firmware storage device generates a response and sends the corresponding BMC firmware version data to the BMC firmware according to the BMC firmware version specified by the server; S4: The BMC firmware receives and verifies the firmware version data. The verification includes a data signature to ensure that the data has not been tampered with. S5: The BMC firmware automatically upgrades according to the firmware version data, writing the new and verified BMC firmware version data into the BMC chip. Meanwhile, the upgrade process is monitored to determine whether there is an upgrade anomaly, such as a power failure. If so, step S6 is executed; otherwise, the automatic upgrade process continues. S6: Starting the BMC upgrade and repair module to handle abnormalities during the upgrade process. After the abnormalities are handled, step S5 is repeated until the upgrade is successful. After step S1, a secure local communication protocol is established between the intelligent BMC firmware storage device and the BMC firmware, so as to enable communication between the intelligent BMC firmware storage device and the BMC firmware without an external network. At the same time as step S2, the server disconnection status detection is also performed, including the following specific steps: S21: Start hardware-level heartbeat detection and set the heartbeat time interval in the underlying hardware configuration of the server; S22: Within the set time interval, the underlying hardware of the server generates a hardware-level heartbeat signal; S23: The BMC firmware checks the continuity of the heartbeat signal. If it does not receive a specified number of consecutive heartbeat signals, the server will be marked as disconnected. S24: The BMC firmware triggers an automatic processing procedure, including communicating with the intelligent BMC firmware storage device to request a BMC firmware upgrade; S25: When the server is disconnected from the network, the system records the relevant events and sends an alarm to notify the administrator; S26: When the network is disconnected, the server will continue to try to send hardware-level heartbeat signals to restore the connection in time when the network is restored.

2. The offline BMC firmware upgrade method according to claim 1, characterized in that: The multiple BMC firmware versions in step S1 are customized according to the manufacturers and models of the corresponding servers, and have adaptability and compatibility.

3. The offline BMC firmware upgrade method according to claim 1, wherein: Simultaneously with step S3 , the intelligent BMC firmware storage device also manages BMC firmware versions, tracking the history of each BMC firmware version, including verification, authentication, and release date. The BMC firmware version data is encrypted to ensure data confidentiality and integrity.

4. The offline BMC firmware upgrade method according to claim 1, characterized in that: The underlying hardware of the server in step S22 is part of the mainboard.

5. The offline BMC firmware upgrade method according to claim 1, characterized in that: During the automatic upgrade process in step S5, the intelligent BMC firmware storage device and the BMC firmware continuously record detailed upgrade process information, including the upgrade date, time, version number, and verification status.

6. The offline BMC firmware upgrade method according to claim 1, wherein: The specific process of the BMC upgrade and repair module in step S6 processing abnormal situations during the upgrade process is as follows: S61: Reading upgrade data of a parameter configuration module in a BMC firmware version to be upgraded from a BMC firmware storage device, and obtaining an upgrade path for the upgrade data; S62: Reading partition information of upgrade data in the BMC firmware version to be upgraded; S63: Checking the legitimacy of partition information of the upgrade data in the BMC firmware version to be upgraded; S64: performing an image upgrade of the corresponding partition according to the partition information of the upgrade data in the BMC firmware version to be upgraded, and not upgrading the partition of the loader and the repair program of the BMC upgrade and repair module during the image upgrade process; S65: Clearing the upgrade data of the parameter configuration module in the BMC firmware version to be upgraded; S66: The BMC upgrade and repair module completes the repair of the abnormal power failure and restarts the server.

7. A BMC firmware upgrade system in an offline state, used to implement the BMC firmware upgrade method in an offline state according to any one of claims 1 to 6, characterized in that: It includes an intelligent BMC firmware storage device, a BMC firmware upgrade module, a BMC firmware upgrade detection module, a BMC upgrade repair module and a parameter configuration module; the intelligent BMC firmware storage device is connected to the BMC firmware upgrade module, the BMC firmware upgrade module is stored in the intelligent BMC firmware storage device, the BMC firmware upgrade module is connected to the BMC upgrade repair module and the BMC firmware upgrade detection module, and the parameter configuration module is connected to the BMC firmware upgrade module and the BMC firmware upgrade detection module; The intelligent BMC firmware storage device is used to store the BMC firmware version; The BMC firmware upgrade module is used to upgrade the BMC firmware; The parameter configuration module is used to configure the parameters during the BMC firmware upgrade process; The BMC firmware upgrade detection module is used to detect abnormal conditions during the BMC firmware upgrade process, including power failure; The BMC upgrade and repair module is used to handle abnormal situations that occur during the upgrade process 2.

Images