CN116610349A - Method, device, equipment and medium for starting firmware update - Google Patents

Abstract

The embodiment of the present application discloses a boot firmware update method, device, device and medium, which relate to the technical field of servers and can realize automatic retention configuration update of boot firmware. The method for updating the startup firmware includes: updating the first startup firmware in the server according to the startup firmware update file, the first startup firmware is the startup firmware started in the server; update, and the server enters the startup process, obtain the first parameter setting before the update of the first startup firmware from the baseboard management controller associated with the server through the first startup firmware, the The first parameter setting is sent by the first boot firmware to the baseboard management controller before updating; according to the first parameter setting, the parameter setting of the first boot firmware is adjusted.

Description

Start firmware update method, device and equipment and medium

technical field

The present application relates to the technical field of servers, in particular to a method, device, device and medium for starting firmware update.

Background technique

In order to maintain the stable operation of servers with various architectures in the data center, it is often necessary to update the boot firmware in the server to solve known problems of the boot firmware.

However, for some machines whose startup firmware setting parameters have been modified, after starting the firmware update, these machines cannot support the business before starting the firmware update, and manual intervention is required to readjust the startup firmware setting parameters.

Contents of the invention

The purpose of the embodiments of the present application is to provide a boot firmware update method, device, device and medium, which can realize automatic retention configuration update of boot firmware.

In order to solve the above technical problems, in the first aspect, the embodiment of the present application provides a startup firmware update, which is applied to a server, and the method includes:

According to the startup firmware update file, update the first startup firmware in the server, where the first startup firmware is the startup firmware started in the server;

When the update of the first startup firmware is completed and the server enters a startup process, acquire an update of the first startup firmware from a baseboard management controller associated with the server through the first startup firmware The first parameter setting before the update, the first parameter setting is sent to the baseboard management controller by the first boot firmware before updating;

According to the first parameter setting, adjust the parameter setting of the first boot firmware.

In the second aspect, the embodiment of the present application also provides a method for starting a firmware update, which is applied to a baseboard management controller, and the method includes:

In response to receiving a first acquisition request from the server for the first parameter setting before the update of the first boot firmware, sending the first parameter setting to the first boot firmware, so that the server according to the first parameter Setting, adjusting parameter settings of the first boot firmware;

Wherein, the first startup firmware is the startup firmware started in the server, the first parameter setting is sent to the baseboard management controller by the first startup firmware before updating, and the first acquisition request It is sent by the server when the update of the first boot firmware is completed and the server enters the boot process.

In the third aspect, the embodiment of the present application also provides a device for starting a firmware update, which is applied to a server, and the device includes:

The first update module is configured to update the first startup firmware in the server according to the startup firmware update file, where the first startup firmware is the startup firmware started in the server;

A first acquiring module, configured to acquire, through the first boot firmware, from a baseboard management controller associated with the server when the update of the first boot firmware is completed and the server enters a boot process. The first parameter setting before the first boot firmware is updated, the first parameter setting is sent to the baseboard management controller by the first boot firmware before the update;

A first setting module, configured to adjust parameter settings of the first boot firmware according to the first parameter settings.

In a fourth aspect, the embodiment of the present application also provides a device for starting firmware update, which is applied to a baseboard management controller, and the device includes:

The first sending module is configured to send the first parameter setting to the first startup firmware in response to receiving a first acquisition request from the server for the first parameter setting before the first startup firmware is updated, so that the The server adjusts the parameter setting of the first startup firmware according to the first parameter setting;

Wherein, the first startup firmware is the startup firmware started in the server, the first parameter setting is sent to the baseboard management controller by the first startup firmware before updating, and the first acquisition request It is sent by the server when the update of the first boot firmware is completed and the server enters the boot process.

In the fifth aspect, the embodiment of the present application also provides an electronic device, including a memory, a processor, and a computer program stored on the memory, and the processor executes the computer program to implement the first aspect or the second The method for initiating a firmware update described in the aspect.

In the sixth aspect, the embodiment of the present application also provides a computer-readable storage medium, on which a computer program/instruction is stored, and when the computer program/instruction is executed by a processor, the computer program/instruction as described in the first aspect or the second aspect is implemented. Start the firmware update method.

In a seventh aspect, the embodiment of the present application further provides a computer program product, including a computer program/instruction, and when the computer program/instruction is executed by a processor, implements the method for starting a firmware update as described in the first aspect or the second aspect.

It can be seen from the above technical solution that after the boot firmware of the server is updated, through the data interaction between the boot firmware and the baseboard management controller, the parameter settings before the boot firmware update can be transferred to the updated boot firmware, The updated boot firmware is used to complete the parameter setting restoration, thereby realizing the automatic retention configuration update of the boot firmware, which can reduce the manual intervention in the boot firmware update process, so that the updated boot firmware can support the business before the boot firmware update, and then Improved server stability and reliability.

Description of drawings

In order to illustrate the embodiments of the present application more clearly, the following will briefly introduce the accompanying drawings used in the embodiments. Obviously, the accompanying drawings in the following description are only some embodiments of the present application. As far as people are concerned, other drawings can also be obtained based on these drawings on the premise of not paying creative work.

FIG. 1 is an implementation flowchart of a method for starting a firmware update provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of an implementation process for starting firmware automatic update provided by an embodiment of the present application;

FIG. 3 is an implementation flowchart of another method for starting a firmware update provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a device for starting a firmware update provided by an embodiment of the present application;

FIG. 5 is a schematic structural diagram of another device for starting a firmware update provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of an electronic device provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of a computer-readable storage medium provided by an embodiment of the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of this application.

The terms "comprising" and "having" in the specification and claims of the present application and the above drawings and any variations thereof are intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or device comprising a series of steps or units is not limited to the listed steps or units, but may include unlisted steps or units.

With the development of Internet technology, the number of servers in the data center has reached millions. How to maintain the stable operation of servers with various architectures in the data center has become a problem that every server manufacturer must consider.

In order to ensure the stable operation of the server, the mainboard of the server is usually designed based on the primary and secondary settings of the Basic Input Output System (BIOS, also known as BIOS firmware, BIOS image, boot firmware, or boot management firmware). When any one of the main BIOS and the backup BIOS fails, the boot firmware can be controlled by a complex programmable logic device (CPLD, Complex Programmable Logic Device) to automatically switch, thereby ensuring the safety and reliability of the server and improving the use of the server. life.

In the research and development process of various server manufacturers, the boot firmware is often updated to solve the problems of the boot firmware found in the data center or to solve the known problems found by the server chip manufacturers. However, when the startup firmware is upgraded in batches through tools, the standby BIOS of the server that is not currently started cannot be updated, and the server cannot be started in time after the startup firmware is updated, so that users cannot know whether the startup firmware has been updated in time, and confirm the updated version in time. At the same time, some customers have modified the key BIOS setting parameters for some machines, but after the firmware update is completed, the parameter settings before the update cannot be automatically maintained, so that it is difficult for the server to meet the business needs before the firmware update.

In view of the problems existing in the above-mentioned related technologies, the application proposes a method for automatically retaining the configuration update of the startup firmware. The update of the main and standby BIOS is controlled by the BMC. After the update of the main and standby BIOS is completed, the server will be triggered to start, so that the BMC can update the The reserved parameter settings before the update of the active and standby BIOS are correspondingly transmitted to the updated active and standby BIOS, and at the same time, the BMC can obtain the BIOS version information transmitted by the active and standby BIOS updates, thereby confirming that the active and standby BIOS updates have been completed.

A method for starting a firmware update provided by an embodiment of the present application will be described in detail below through some embodiments and application scenarios with reference to the accompanying drawings.

In the first aspect, see FIG. 1 , which is an implementation flowchart of a method for starting a firmware update provided in an embodiment of the present application. The method for starting a firmware update is applied to a server, and the method may include the following steps:

Step S101: Update the first boot firmware in the server according to the boot firmware update file.

It can be understood that the first boot firmware is the boot firmware that has been started when the server triggers the boot firmware update. For example, the first boot firmware can be the main BIOS of the server. In the case of active/standby BIOS switching, the first boot firmware is the standby BIOS switched by the server.

Among them, the startup firmware is a group of system programs solidified into a memory chip on the mainboard of the server, which plays an indispensable role in the normal initialization, startup and operating system guidance of the computer system, and is the key to realizing the security and reliability of the computer system. A key link in key functions such as sex.

In a specific implementation, when the server needs to update the boot firmware, it can obtain (eg, obtain in advance through the BMC) the relevant boot firmware update file in advance. After obtaining the startup firmware update file, the server can continue to perform business processing until the current state of the server meets the startup firmware update conditions (such as the server is shut down or the server is not running business), and then according to the startup firmware update file, through the in-band management method Or out-of-band management to update the version of the startup firmware that has been started by itself.

As a possible implementation manner, after the server receives the startup firmware update file, it can notify the BMC to perform a power-off operation on the server, so that the server can update the startup firmware in time.

Step S102: When the update of the first boot firmware is completed and the server enters the boot process, obtain the first boot firmware from the baseboard management controller associated with the server through the first boot firmware. First parameter setting before starting the firmware update.

Wherein, the first parameter setting is sent to the baseboard management controller by the first boot firmware before updating.

In specific implementation, the first boot firmware can send the artificially modified parameter settings to the baseboard management controller for storage every time its own parameter settings are artificially modified, so that when the firmware is updated in the future, based on the baseboard management The parameter settings reserved by the controller are restored to the parameter settings. Considering that after the boot firmware is updated, the update of the boot firmware will take effect when the server is powered on, so when the server enters the boot process for the first time after the boot firmware is updated, the updated boot firmware can interact with the BMC for data , it can avoid the failure to obtain the parameter settings before the update due to the use of the boot firmware before the update takes effect (such as the abnormal boot firmware before the update), thereby improving the reliability of the boot firmware update process.

Step S103: Adjust parameter settings of the first startup firmware according to the first parameter settings.

In specific implementation, after the startup firmware obtains the parameter settings before the update, it can configure the obtained parameter settings to the corresponding model selection, so that the parameter settings of the updated startup firmware are automatically restored to those before the update, realizing the Business support before starting the firmware update.

It can be understood that if the server deploys at least two boot firmwares in active and standby mode, the server can automatically switch to use other boot firmware deployed on the server after completing the automatic retention configuration update of the first boot firmware through the above steps (i.e. the second boot firmware), after completing the firmware switch, you can repeat the above-mentioned steps of automatically retaining the configuration update for the first boot firmware, so as to implement other boot firmware deployed on the server (if the server does not start when the server triggers the boot firmware update). Automatic update of the standby BIOS).

It can be seen from the above technical solution that after the boot firmware of the server is updated, through the data interaction between the boot firmware and the baseboard management controller, the parameter settings before the boot firmware update can be transferred to the updated boot firmware, The updated boot firmware is used to complete the parameter setting restoration, thereby realizing the automatic retention configuration update of the boot firmware, which can reduce the manual intervention in the boot firmware update process, so that the updated boot firmware can support the business before the boot firmware update, and then Improved server stability and reliability.

Implementation Mode 1

This embodiment describes an example of data interaction between the updated boot firmware and the BMC. According to the type of data exchanged between the boot firmware and the BMC, it can be divided into the following two cases.

Case 1: During the startup process, the BIOS will exchange data with the BMC through the interactive interface, and the BMC will transfer the pre-updated BIOS parameter settings retained in the BMC image to the updated BIOS image.

In this embodiment, when the server completes the update of the boot firmware (such as the first boot firmware or the second boot firmware) and the server enters the boot process, the boot firmware is used to download the boot firmware from the BMC associated with the server (that is, store the In the BMC of the parameter setting before the startup firmware update), the parameter setting (such as the first parameter setting or the second parameter setting) before the startup firmware update is obtained, wherein, the parameter setting before the update is that the startup firmware sends before the update to the BMC.

When the server enters the boot process for the first time after the boot firmware is updated, the updated boot firmware sends an acquisition request to the BMC. The BMC responds to receiving an acquisition request (such as the first acquisition request or the second acquisition request) from the server for the parameter settings (such as the first parameter settings or the second parameter settings) before the startup firmware (such as the first startup firmware or the second startup) is updated. request), send the parameter setting to the boot firmware.

Situation 2: While the BMC transmits the pre-update BIOS parameter settings retained by itself to the updated BIOS image, the BIOS transmits its own version information (ie, the updated version information) to the BMC firmware.

In this embodiment, when the server completes the update of the boot firmware (such as the first boot firmware or the second boot firmware), and the server enters the boot process, it will automatically use the boot firmware to represent the boot firmware update. The completed information (such as the first information or the second information) is sent to the BMC, so as to inform the BMC server that the boot firmware has been updated in time.

After receiving the first information or the second information, the BMC can display the first information or the second information to the user through its own service page (such as BMC web).

As a possible implementation manner, the first information may at least include the version information of the first boot firmware (that is, the updated BIOS version), and the second information may at least include the version information of the second boot firmware, and the BMC displays the The updated BIOS version, so as to inform the user in time that the relevant startup firmware has been updated, and at the same time facilitate the user to confirm whether the BIOS version is wrong.

Implementation mode two

This embodiment describes an example of starting firmware automatic switching during an update process.

In this embodiment, in order to realize the automatic update of the active and standby BIOS of the server, after the server completes the data interaction as described in Embodiment 1 (such as the parameter setting transmission before the firmware update) through the updated startup firmware and the BMC, the Automatically send notification information to inform the BMC that the data interaction is complete, so that the BMC can control the server to automatically switch the startup firmware in time, such as the BMC can control the server to shut down, and send the server's BIOS Serial Peripheral Interface (SPI, Serial Peripheral Interface) signal (also known as chip select signal) to switch from the main BIOS to the standby BIOS. Wherein, after completing the automatic updating of the active and standby BIOS of the server, the BMC can control the server to switch the boot firmware back to the first boot firmware, thereby completing the automatic update operation of the active and standby BIOS in the server.

During specific implementation, the server can send to the BMC through the first boot firmware the first notification information that is used to represent the completion of data interaction between the first boot firmware and the BMC, so that the BMC can control the shutdown of the server and switch the server to be started The boot firmware is switched from the first boot firmware to the second boot firmware, so as to update the second boot firmware automatically with a reserved configuration.

After the data interaction between the second boot firmware and the BMC is completed, the server can send the second notification information used to represent the completion of the data interaction between the second boot firmware and the BMC to the BMC through the second boot firmware, so that The BMC controls the shutdown of the server, and switches the boot firmware to be started in the server from the second boot firmware back to the first boot firmware, thereby completing the automatic update operation of the active and standby BIOS.

Implementation Mode Three

This embodiment describes an example of starting firmware version update. In this embodiment, the boot firmware (such as the first boot firmware or the second boot firmware) can be managed through out-of-band or in-band management.

Taking the in-band management method as an example, when the server is in a non-running business state (that is, there is no business to be processed), the server can update the file according to the startup firmware, and perform in-band management on itself through the startup firmware. After updating the version, restart the server for the update to take effect.

Considering that when the boot firmware is abnormal, it is difficult to update the version of the boot firmware through in-band management. Therefore, when the server is powered off, the boot firmware can be updated through the BMC through out-of-band management according to the boot firmware update file. Perform a version update, and after completing the version update of the boot firmware, start the server through the BMC to make the update take effect.

Based on the foregoing embodiments, the present application automatically performs an update operation through the active and standby BIOS in the BMC control server, and the BIOS and the BMC pass each other's parameter settings through interactive protocols such as Intelligent Platform Management Interface (IPMI, Intelligent Platform Management Interface) to realize the update. The parameter setting of the BIOS after the update is consistent with the BIOS parameter setting before the update, which improves the stability and reliability of the server in the data center, minimizes the impact of starting the firmware update on the server business before the update, and realizes the independent update and maintenance of the server functions to meet the actual business needs of the customer's data center.

The above implementation manner will be described below with reference to the schematic diagram of the implementation process of starting firmware automatic update shown in FIG. 2 .

In this embodiment, no matter the server is currently in the power-on state or in the power-off state, the user can upload the BIOS mirror image (that is, start the firmware update file) that needs to be updated through the BMC;

When the working status of the server is off, the BMC is updated in a way that does not retain the configuration;

After the BMC finishes updating the main BIOS image, the BMC controls the server’s working state to power on and start. During the startup process, the BMC and the BIOS pass the original BIOS parameter settings retained in the BMC to the BIOS through an interactive protocol. Restore the updated BIOS parameter settings. After the BIOS restores the parameter settings, it will pass the BIOS version information to the BMC, and the BMC will then record the BIOS image version of this startup and display it on the relevant interface, so that the user can confirm the main BIOS of this time. The mirror has been updated.

After transferring the BIOS version information (that is, the BMC completes the main BIOS image update), the BIOS notifies the BMC to control the server to automatically shut down, and then the BMC switches the main BIOS to the backup BIOS image (at this time, the main BIOS refers to the BIOS that the server is currently waiting to start). And use the update process of the above-mentioned main BIOS to update the version of the backup BIOS image and configure the BIOS parameters. When the main and standby BIOS images are updated and started once (that is, the update takes effect), the BMC controls the server to shut down and switches the server to the main BIOS image. and wait for it to start. It can be understood that startup and to-be-started are two operating states of the boot firmware (ie, the boot firmware used by the server) selected by the chip select signal of the server, and the boot firmware (ie, the server boot firmware) not selected by the chip select signal of the server Unused boot firmware) does not have the above two operating states.

Based on the foregoing embodiments, the application controls the automatic update of the main and backup BIOS images through the BMC, passes the BIOS parameter settings retained by the BMC to the updated BIOS, and obtains the BIOS version information passed by the BIOS to confirm that the update has been completed in time, so that it can The BIOS parameter settings before the update are restored one by one after the update, which ensures the security and stability of the server, and the entire firmware update process does not require human intervention. It can be understood that the above-mentioned master-standby BIOS update process based on the data interaction between the BMC and the master-standby BIOS can also be migrated to the update of the master-standby BMC. At this time, the parameter settings before the master-standby BMC update can be retained by the BIOS, thereby Through data interaction between the updated active and standby BMCs and the BIOS, the parameter settings of the active and standby BMCs can be automatically restored to the parameter settings before the update.

The startup firmware update method provided by this application is not limited by architecture and platform, and can be widely applied to server products of various architectures, and can effectively reduce the workload and operation and maintenance costs of operation and maintenance personnel of data center servers.

In the second aspect, see FIG. 3 , which is an implementation flowchart of another method for starting a firmware update provided by an embodiment of the present application. The method for starting a firmware update is applied to a baseboard management controller, and the method may include the following steps:

Step S201: In response to receiving the first acquisition request from the server for the first parameter setting before the update of the first boot firmware, send the first parameter setting to the first boot firmware, so that the server according to the First parameter setting, adjusting the parameter setting of the first boot firmware;

Wherein, the first startup firmware is the startup firmware started in the server, the first parameter setting is sent to the baseboard management controller by the first startup firmware before updating, and the first acquisition request It is sent by the server when the update of the first boot firmware is completed and the server enters the boot process.

As a possible implementation, the method also includes:

receiving first information from the first boot firmware, the first information is sent by the server when the update of the first boot firmware is completed and the server enters a boot process, the The first information is used to represent the completion of the first startup firmware update;

The first information is displayed.

As a possible implementation, the method also includes:

In response to receiving the first notification information from the first boot firmware, controlling the server to shut down, and switching the boot firmware to be started in the server from the first boot firmware to the second boot firmware, the The first notification information is used to represent the completion of data interaction between the first boot firmware and the baseboard management controller;

In response to receiving a second acquisition request from the server for a second parameter setting before the second boot firmware is updated, sending the second parameter setting to the second boot firmware, so that the server according to the The second parameter setting, adjusting the parameter setting of the second startup firmware;

Wherein, the second parameter setting is sent by the second boot firmware to the baseboard management controller before updating, and the second acquisition request is that the server completes the update of the second boot firmware, and the server enters the startup process.

As a possible implementation, the method also includes:

receiving second information from the second boot firmware, the second information is sent by the server when the update of the second boot firmware is completed and the server enters a boot process, the The second information is used to represent the completion of the second startup firmware update;

The second information is displayed.

As a possible implementation, the method also includes:

In response to receiving the second notification information from the second boot firmware, controlling the server to shut down, and switching the boot firmware to be started in the server from the second boot firmware to the first boot firmware , the second notification information is used to indicate that the data interaction between the second boot firmware and the baseboard management controller is completed.

As a possible implementation manner, the first boot firmware in the server is updated through the following steps:

sending the boot firmware update file to the server;

When the server is in a shutdown state, update the first boot firmware in an out-of-band management manner according to the boot firmware update file;

After the updating of the first boot firmware is completed, the server is started.

It can be seen from the above technical solution that after the boot firmware of the server is updated, through the data interaction between the boot firmware and the baseboard management controller, the parameter settings before the boot firmware update can be transferred to the updated boot firmware, The updated boot firmware is used to complete the parameter setting restoration, thereby realizing the automatic retention configuration update of the boot firmware, which can reduce the manual intervention in the boot firmware update process, so that the updated boot firmware can support the business before the boot firmware update, and then Improved server stability and reliability.

In a third aspect, the embodiment of the present application provides a device for starting a firmware update, which is applied to a server. As shown in FIG. 4 , the device includes:

The first update module 11 is configured to update the first startup firmware in the server according to the startup firmware update file, the first startup firmware is the startup firmware started in the server;

The first obtaining module 12 is configured to, when the update of the first startup firmware is completed and the server enters the startup process, obtain from the baseboard management controller associated with the server through the first startup firmware, Acquiring a first parameter setting before the update of the first boot firmware, where the first parameter setting is sent to the baseboard management controller by the first boot firmware before the update;

The first setting module 13 is configured to adjust the parameter setting of the first startup firmware according to the first parameter setting.

Optionally, the device also includes:

A first information sending module, configured to send first information to the baseboard management controller through the first startup firmware when the update of the first startup firmware is completed and the server enters a startup process. , so that the baseboard management controller displays the first information, where the first information is used to indicate that the update of the first startup firmware is completed.

Optionally, the first information includes at least: version information of the first boot firmware.

Optionally, the device also includes:

The first notification information sending module is configured to send the first notification information to the baseboard management controller through the first startup firmware, so that the baseboard management controller controls the shutdown of the server, and shuts down the standby server in the server. The started boot firmware is switched from the first boot firmware to the second boot firmware, and the first notification information is used to indicate that the data interaction between the first boot firmware and the baseboard management controller is completed;

A second update module, configured to update the second boot firmware according to the boot firmware update file;

The second acquiring module is configured to acquire the second boot firmware from the baseboard management controller through the second boot firmware when the update of the second boot firmware is completed and the server enters a boot process. 2. The second parameter setting before the boot firmware is updated, the second parameter setting is sent to the baseboard management controller by the second boot firmware before the update;

The second setting module is configured to adjust the parameter setting of the second startup firmware according to the second parameter setting.

Optionally, the device also includes:

A second information sending module, configured to send second information to the baseboard management controller through the second startup firmware when the update of the second startup firmware is completed and the server enters a startup process , so that the baseboard management controller displays the second information, where the second information is used to indicate that the update of the second startup firmware is completed.

Optionally, the second information includes at least: version information of the second boot firmware.

Optionally, the device also includes:

The second notification information sending module is configured to send second notification information to the baseboard management controller through the second startup firmware, so that the baseboard management controller controls the shutdown of the server and shuts down the server in the server. The started boot firmware is switched from the second boot firmware to the first boot firmware, and the second notification information is used to represent the completion of data interaction between the second boot firmware and the BMC.

Optionally, the first update module 11 includes:

The first update submodule is configured to update the first boot firmware in an out-of-band management manner through the baseboard management controller according to the boot firmware update file when the server is in a shutdown state;

A startup module, configured to start the server through the baseboard management controller after the update of the first startup firmware is completed.

Optionally, the first update module 11 includes:

The second update submodule is configured to update the first boot firmware through the first boot firmware in an in-band management manner according to the boot firmware update file when the server is in a non-running service state;

A restart module, configured to restart the server after the update of the first boot firmware is completed.

It can be seen from the above technical solution that after the boot firmware of the server is updated, the parameter settings before the boot firmware update can be transferred to the updated boot firmware through data interaction between the boot firmware and the baseboard management controller, The updated boot firmware is used to complete the parameter setting restoration, thereby realizing the automatic retention configuration update of the boot firmware, which can reduce the manual intervention in the boot firmware update process, so that the updated boot firmware can support the business before the boot firmware update, and then Improved server stability and reliability.

In the fourth aspect, the embodiment of the present application provides another device for starting a firmware update, which is applied to a baseboard management controller. As shown in FIG. 5 , the device includes:

The first sending module 21 is configured to send the first parameter setting to the first startup firmware in response to receiving a first acquisition request from the server for the first parameter setting before the update of the first startup firmware, so that all The server adjusts the parameter setting of the first startup firmware according to the first parameter setting;

Wherein, the first startup firmware is the startup firmware started in the server, the first parameter setting is sent to the baseboard management controller by the first startup firmware before updating, and the first acquisition request It is sent by the server when the update of the first boot firmware is completed and the server enters the boot process.

Optionally, the device also includes:

The first receiving module is configured to receive first information from the first boot firmware, the first information is that the server is completing the update of the first boot firmware and the server enters the boot process issued under the above circumstances, the first information is used to represent the completion of the first startup firmware update;

A first display module, configured to display the first information.

Optionally, the device also includes:

A first control module, configured to, in response to receiving first notification information from the first boot firmware, control the server to shut down, and switch the boot firmware to be started in the server from the first boot firmware. To the second boot firmware, the first notification information is used to represent the completion of data interaction between the first boot firmware and the baseboard management controller;

The second sending module is configured to send the second parameter setting to the second startup firmware in response to receiving a second acquisition request from the server for the second parameter setting before the second startup firmware is updated, making the server adjust the parameter setting of the second boot firmware according to the second parameter setting;

Wherein, the second parameter setting is sent by the second boot firmware to the baseboard management controller before updating, and the second acquisition request is that the server completes the update of the second boot firmware, and the server enters the startup process.

Optionally, the device also includes:

The second receiving module is configured to receive second information from the second boot firmware, the second information is that the server is completing the update of the second boot firmware, and the server enters the boot process issued under the circumstances, the second information is used to represent the completion of the second startup firmware update;

The second display module is used to display the second information.

Optionally, the device also includes:

The second control module is configured to control the server to shut down in response to receiving the second notification information from the second boot firmware, and switch the boot firmware to be started in the server to the second boot firmware. For the first boot firmware, the second notification information is used to represent the completion of data interaction between the second boot firmware and the baseboard management controller.

Optionally, the device also includes:

A third sending module, configured to send the startup firmware update file to the server;

A firmware update module, configured to update the first boot firmware in an out-of-band management manner according to the boot firmware update file when the server is powered off;

The third control module is configured to start the server after updating the first startup firmware.

It can be seen from the above technical solution that after the boot firmware of the server is updated, through the data interaction between the boot firmware and the baseboard management controller, the parameter settings before the boot firmware update can be transferred to the updated boot firmware, The updated boot firmware is used to complete the parameter setting restoration, thereby realizing the automatic retention configuration update of the boot firmware, which can reduce the manual intervention in the boot firmware update process, so that the updated boot firmware can support the business before the boot firmware update, and then Improved server stability and reliability.

It should be noted that the device embodiment is similar to the method embodiment, so the description is relatively simple, and the relevant parts can be referred to the method embodiment.

The embodiment of the present application also provides an electronic device. Referring to FIG. 6 , FIG. 6 is a schematic diagram of the electronic device proposed in the embodiment of the present application. As shown in FIG. 6 , the electronic device 100 includes: a memory 110 and a processor 120, the memory 110 and the processor 120 are connected through a bus communication, and a computer program is stored in the memory 110, and the computer program can run on the processor 120, Further, the steps in the method for starting firmware update disclosed in the embodiment of the present application are implemented.

An embodiment of the present application further provides a computer-readable storage medium, see FIG. 7 , which is a schematic diagram of a computer-readable storage medium proposed in an embodiment of the present application. As shown in FIG. 7 , a computer readable storage medium 200 stores a computer program/instruction 210 , and when the computer program/instruction 210 is executed by a processor, the steps in the method for starting a firmware update as disclosed in the embodiment of the present application are implemented.

The embodiment of the present application also provides a computer program product, including a computer program/instruction, and when the computer program/instruction is executed by a processor, the steps in the method for starting a firmware update as disclosed in the embodiment of the present application are implemented.

Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same and similar parts of each embodiment can be referred to each other.

Those skilled in the art should understand that the embodiments of the embodiments of the present application may be provided as methods, devices or computer program products. Therefore, the embodiment of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

Embodiments of the present application are described with reference to flowcharts and/or block diagrams of methods, systems, devices, storage media, and program products according to the embodiments of the present application. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor or processor of other programmable data processing terminal equipment to produce a machine such that instructions executed by the computer or processor of other programmable data processing terminal equipment Produce means for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the The instruction means implements the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded into a computer or other programmable data processing terminal equipment, so that a series of operational steps are performed on the computer or other programmable terminal equipment to produce computer-implemented processing, thereby The instructions executed above provide steps for implementing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

While the preferred embodiments of the embodiments of the present application have been described, additional changes and modifications can be made to these embodiments by those skilled in the art once the basic inventive concept is understood. Therefore, the appended claims are intended to be interpreted to cover the preferred embodiment and all changes and modifications that fall within the scope of the embodiments of the application.

Finally, it should also be noted that in this text, relational terms such as first and second etc. are only used to distinguish one entity or operation from another, and do not necessarily require or imply that these entities or operations, any such actual relationship or order exists. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or terminal equipment comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements identified, or also include elements inherent in such a process, method, article, or terminal equipment. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or terminal device comprising said element.

Above, a method, device, device and medium for starting firmware update provided by this application have been introduced in detail. In this paper, specific examples are used to illustrate the principle and implementation of this application. The description of the above embodiments is only for To help understand the method and its core idea of this application; at the same time, for those of ordinary skill in the art, according to the idea of this application, there will be changes in the specific implementation and application scope. In summary, the content of this specification It should not be construed as a limitation of the application.

Claims (19)

1. A method for starting a firmware update, characterized in that it is applied to a server, and the method comprises: According to the startup firmware update file, update the first startup firmware in the server, where the first startup firmware is the startup firmware started in the server; When the update of the first startup firmware is completed and the server enters a startup process, acquire an update of the first startup firmware from a baseboard management controller associated with the server through the first startup firmware The first parameter setting before the update, the first parameter setting is sent to the baseboard management controller by the first boot firmware before updating; According to the first parameter setting, adjust the parameter setting of the first boot firmware. 2. The method according to claim 1, characterized in that the method further comprises: When the update of the first startup firmware is completed and the server enters the startup process, the first information is sent to the baseboard management controller through the first startup firmware, so that the baseboard management controller The monitor displays the first information, and the first information is used to indicate that the first startup firmware update is completed. 3. The method according to claim 2, wherein the first information at least includes: version information of the first boot firmware. 4. The method according to claim 1, wherein the method further comprises: Sending first notification information to the baseboard management controller through the first startup firmware, so that the baseboard management controller controls the shutdown of the server, and sends the startup firmware to be started in the server by the first The boot firmware is switched to the second boot firmware, and the first notification information is used to indicate that the data interaction between the first boot firmware and the baseboard management controller is completed; updating the second boot firmware according to the boot firmware update file; When the update of the second boot firmware is completed and the server enters the boot process, obtain the second boot firmware before the update of the second boot firmware from the baseboard management controller through the second boot firmware. Two parameter settings, the second parameter setting is sent to the baseboard management controller by the second boot firmware before updating; Adjusting parameter settings of the second boot firmware according to the second parameter settings. 5. method according to claim 4, is characterized in that, described method also comprises: When the update of the second startup firmware is completed and the server enters the startup process, the second information is sent to the baseboard management controller through the second startup firmware, so that the baseboard management controller The monitor displays the second information, and the second information is used to indicate that the second startup firmware update is completed. 6. The method according to claim 5, wherein the second information at least includes: version information of the second boot firmware. 7. The method according to claim 4, characterized in that the method further comprises: The second notification information is sent to the baseboard management controller through the second startup firmware, so that the baseboard management controller controls the shutdown of the server, and sends the startup firmware to be started in the server by the second The boot firmware is switched to the first boot firmware, and the second notification information is used to represent the completion of data interaction between the second boot firmware and the BMC. 8. The method according to any one of claims 1-7, wherein the first boot firmware in the server is updated through the following steps: When the server is in the shutdown state, according to the boot firmware update file, update the first boot firmware in an out-of-band management manner through the baseboard management controller; After the updating of the first boot firmware is completed, the server is booted by the baseboard management controller. 9. The method according to any one of claims 1-7, wherein the first boot firmware in the server is updated through the following steps, including: When the server is in a state of no running business, according to the boot firmware update file, the first boot firmware is updated in an in-band management manner through the first boot firmware; After the updating of the first boot firmware is completed, the server is restarted. 10. A method for starting a firmware update, characterized in that it is applied to a baseboard management controller, the method comprising: In response to receiving a first acquisition request from the server for the first parameter setting before the update of the first boot firmware, sending the first parameter setting to the first boot firmware, so that the server according to the first parameter Setting, adjusting parameter settings of the first boot firmware; Wherein, the first startup firmware is the startup firmware started in the server, the first parameter setting is sent to the baseboard management controller by the first startup firmware before updating, and the first acquisition request It is sent by the server when the update of the first boot firmware is completed and the server enters the boot process. 11. The method of claim 10, further comprising: receiving first information from the first boot firmware, the first information is sent by the server when the update of the first boot firmware is completed and the server enters a boot process, the The first information is used to represent the completion of the first startup firmware update; The first information is displayed. 12. The method according to claim 10, further comprising: In response to receiving the first notification information from the first boot firmware, controlling the server to shut down, and switching the boot firmware to be started in the server from the first boot firmware to the second boot firmware, the The first notification information is used to represent the completion of data interaction between the first boot firmware and the baseboard management controller; In response to receiving a second acquisition request from the server for a second parameter setting before the second boot firmware is updated, sending the second parameter setting to the second boot firmware, so that the server according to the The second parameter setting, adjusting the parameter setting of the second startup firmware; Wherein, the second parameter setting is sent by the second boot firmware to the baseboard management controller before updating, and the second acquisition request is that the server completes the update of the second boot firmware, and the server enters the startup process. 13. The method of claim 12, further comprising: receiving second information from the second boot firmware, the second information is sent by the server when the update of the second boot firmware is completed and the server enters a boot process, the The second information is used to represent the completion of the second startup firmware update; The second information is displayed. 14. The method of claim 12, further comprising: In response to receiving the second notification information from the second boot firmware, controlling the server to shut down, and switching the boot firmware to be started in the server from the second boot firmware to the first boot firmware , the second notification information is used to indicate that the data interaction between the second boot firmware and the baseboard management controller is completed. 15. The method according to any one of claims 10-14, wherein the first boot firmware in the server is updated through the following steps: sending the boot firmware update file to the server; When the server is in a shutdown state, update the first boot firmware in an out-of-band management manner according to the boot firmware update file; After the updating of the first boot firmware is completed, the server is started. 16. A device for starting a firmware update, characterized in that it is applied to a server, and the device comprises: The first update module is configured to update the first startup firmware in the server according to the startup firmware update file, where the first startup firmware is the startup firmware started in the server; A first acquiring module, configured to acquire, through the first boot firmware, from a baseboard management controller associated with the server when the update of the first boot firmware is completed and the server enters a boot process. The first parameter setting before the first boot firmware is updated, the first parameter setting is sent to the baseboard management controller by the first boot firmware before the update; A first setting module, configured to adjust parameter settings of the first boot firmware according to the first parameter settings. 17. A device for starting firmware update, characterized in that it is applied to a baseboard management controller, and the device comprises: The first sending module is configured to send the first parameter setting to the first startup firmware in response to receiving a first acquisition request from the server for the first parameter setting before the first startup firmware is updated, so that the The server adjusts the parameter setting of the first startup firmware according to the first parameter setting; Wherein, the first startup firmware is the startup firmware started in the server, the first parameter setting is sent to the baseboard management controller by the first startup firmware before updating, and the first acquisition request It is sent by the server when the update of the first boot firmware is completed and the server enters the boot process. 18. An electronic device, comprising a memory, a processor, and a computer program stored on the memory, wherein the processor executes the computer program to realize any one of claims 1 to 9 The method for starting firmware update or implementing the method for starting firmware update according to any one of claims 10 to 15. 19. A computer-readable storage medium, on which computer programs/instructions are stored, characterized in that, when the computer program/instructions are executed by a processor, the startup firmware update according to any one of claims 1 to 9 is implemented method or implement the method for initiating a firmware update as claimed in any one of claims 10 to 15.