CN106980493B

CN106980493B - Firmware management method and device

Info

Publication number: CN106980493B
Application number: CN201610031467.1A
Authority: CN
Inventors: 徐东; 熊先奎; 郑旭锋; 张景涛
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2016-01-18
Filing date: 2016-01-18
Publication date: 2021-06-18
Anticipated expiration: 2036-01-18
Also published as: WO2017124799A1; CN106980493A

Abstract

The invention discloses a firmware management method, which comprises the following steps: the baseboard management controller virtualizes a pre-configured firmware management image file into a virtual starting system, and the virtual starting system is hung on a host; modifying the starting mode configuration of the host, wherein the modified starting mode configuration of the host is associated with the virtual starting system; and controlling the host to start from the virtual starting system according to the modified starting mode configuration, and loading the firmware management image file to perform firmware management. The invention also discloses a firmware management device. The invention improves the management function of the server firmware, simplifies the management process, realizes the automatic management of the server firmware and improves the maintainability of the server firmware.

Description

Firmware management method and device

Technical Field

The present invention relates to the field of firmware management technologies, and in particular, to a firmware management method and apparatus.

Background

A server is a device for providing computing services, and mainly includes hardware devices such as a Central Processing Unit (CPU), a storage device, a memory, and an Input/Output (I/O) device. In a hardware device, firmware acts as the software that operates on the very bottom of the system's foundation. The CPU is the operation core and control core of a computer, and the memory is used for storing program operation data. The CPU and memory need not rely on specific firmware for normal use. Generally, the storage device, the network card, the display card and other input/output devices need to sinter specific firmware, such as display card firmware, network card firmware, SAS (Serial Attached SCSI) controller firmware, to normally operate.

For the management of firmware, there are mainly firmware sintering, firmware updating, backup of firmware configuration data, and recovery of accessory configuration data. At present, server firmware management mainly adopts two ways, one is software sintering based on an OS (operating System), and the other is special cable sintering.

The OS-based software sintering is to install an operating system and sintering software on a server, and to sinter or update firmware by uploading firmware files and inputting configuration data of the firmware and using the sintering software. When there are a plurality of pieces of firmware that need to be burned or updated, the above-described procedure needs to be repeated for each piece of firmware.

And the special cable sintering is to upload the firmware file to a debugging machine, connect the debugging machine with a sintered device and the debugging machine by using the special cable, run firmware sintering software on the debugging machine after powering on a sintered server, input configuration data of the firmware, and sinter or update the firmware on the single board. When there are a plurality of pieces of firmware that need to be burned or updated, the above-described procedure needs to be repeated for each piece of firmware.

Because the software sintering based on OS and the special cable sintering process are complex, and the number of manual operation parts is large, the accuracy of firmware sintering or updating cannot be guaranteed, and the batch production of server single boards is not facilitated. Particularly, when the server firmware is updated, the feasibility of field operation is not high, and if the server firmware is returned to a factory for maintenance, the cost is increased, which causes great maintenance difficulty and poor maintainability.

In addition, when the server is replaced but the firmware configuration data of the replaced device is not changed, backup and recovery of the backup firmware configuration data need to be realized through an in-band interface or an out-band interface of the server, and as most current devices do not support acquisition and rewriting of the out-band interface, software and hardware design is complicated, and firmware configuration data management of only part of devices can be realized.

Therefore, the existing server firmware management process is complex, incomplete in function, high in human participation degree and poor in maintainability.

Disclosure of Invention

The invention mainly aims to provide a firmware management method and a firmware management device, and aims to solve the technical problems of incomplete firmware management function and poor maintainability.

In order to achieve the above object, the present invention provides a firmware management method, including the steps of:

the baseboard management controller virtualizes a pre-configured firmware management image file into a virtual starting system, and the virtual starting system is hung on a host;

modifying the starting mode configuration of the host, wherein the modified starting mode configuration of the host is associated with the virtual starting system;

and controlling the host to start from the virtual starting system according to the modified starting mode configuration, and loading the firmware management image file to perform firmware management.

Preferably, the step of modifying the boot method configuration of the host, where the modified boot method configuration of the host is associated with the virtual boot system, includes:

and modifying the starting mode configuration of the host computer into a starting mode acquired from the baseboard management controller and starting according to the acquired starting mode, wherein the acquired starting mode is started from the virtual starting system.

Preferably, the step of controlling the host to boot from the virtual boot system according to the modified boot method configuration, and loading the firmware management image file to perform firmware management includes:

controlling the host to restart, and acquiring a starting mode from the baseboard management controller according to the modified starting mode configuration;

controlling the host to start from the virtual starting system according to the acquired starting mode, and loading the firmware management image file;

and guiding the host to perform firmware management.

Preferably, the firmware management image file includes a firmware configuration data collection image file, and the step of booting the host to perform firmware management includes:

scanning each firmware of the host through the firmware configuration data acquisition mirror image file, and acquiring configuration data of the firmware;

storing the firmware configuration data for the firmware state recovery.

Preferably, the firmware management image file includes a firmware configuration data recovery image file, and the step of booting the host to perform firmware management further includes:

recovering the image file through the firmware configuration data, and controlling the corresponding firmware to recover the configuration data;

and recording and storing the firmware configuration data recovery result.

Preferably, before the step of virtualizing the pre-configured firmware management image file into a virtual boot system and attaching to the host, the baseboard management controller further includes:

the baseboard management controller configures the firmware management image file in a local or remote debugging machine of the baseboard management controller, and the baseboard management controller is communicated with the remote debugging machine to call the firmware management image file on the remote debugging machine.

Preferably, the step of modifying the configuration of the boot method of the host further includes:

modifying the starting mode configuration of the host computer, and backing up the original starting configuration data of the host computer;

after the step of controlling the host to start from the virtual boot system and perform firmware management, the method further includes:

and controlling the host to reset according to the original starting configuration data.

Further, to achieve the above object, the present invention provides a firmware management apparatus including:

the virtual module is used for virtualizing a pre-configured firmware management image file into a virtual starting system and hanging the virtual starting system on a host;

a modification module, configured to modify a boot method configuration of the host, where the modified boot method configuration of the host is associated with the virtual boot system;

and the management module is used for controlling the host to start from the virtual starting system according to the modified starting mode configuration, and loading the firmware management image file to perform firmware management.

Preferably, the modification module is further configured to,

the starting mode configuration of the host is modified to be a starting mode obtained from the baseboard management controller and the host is started according to the obtained starting mode, wherein the obtained starting mode is started from the virtual starting system;

the management module comprises:

the restarting unit is used for controlling the host to restart and acquiring a starting mode from the substrate management controller according to the modified starting mode configuration;

the configuration unit is used for controlling the host to start from the virtual starting system according to the acquired starting mode and loading the firmware management image file;

and the management unit is used for guiding the host to carry out firmware management.

Preferably, the modification module is further configured to,

the firmware management apparatus further includes:

and the reset module is used for controlling the host to reset according to the original starting configuration data.

The firmware management method and the firmware management device provided by the embodiment of the invention virtualize a pre-configured firmware management image file into a virtual starting system through a baseboard management controller, and are hung on a host; modifying the starting mode configuration of the host, wherein the modified starting mode configuration of the host is associated with the virtual starting system; and controlling the host to start from the virtual starting system according to the modified starting mode configuration, and loading the firmware management image file to perform firmware management. The embodiment of the invention perfects the management function of the server firmware, simplifies the management process, realizes the automatic management of the server firmware and improves the maintainability of the server firmware.

Drawings

FIG. 1 is a flowchart illustrating a firmware management method according to a first embodiment of the present invention;

FIG. 2 is a flowchart illustrating a firmware management method according to a second embodiment of the present invention;

FIG. 3 is a flowchart illustrating a firmware management method according to a third embodiment of the present invention;

FIG. 4 is a flowchart illustrating a firmware management method according to a fourth embodiment of the present invention;

FIG. 5 is a flowchart illustrating a fifth embodiment of a firmware management method according to the present invention;

FIG. 6 is a flowchart illustrating a firmware management method according to a sixth embodiment of the present invention;

FIG. 7 is a diagram illustrating firmware management according to an embodiment of a firmware management method;

FIG. 8 is a diagram illustrating firmware management according to an embodiment of the firmware management method of the present invention;

FIG. 9 is a flowchart illustrating a firmware management method according to a seventh embodiment of the present invention;

FIG. 10 is a functional block diagram of a firmware management device according to a first embodiment and a second embodiment of the present invention;

FIG. 11 is a functional block diagram of a firmware management device according to a third embodiment of the present invention;

FIG. 12 is a functional block diagram of a firmware management device according to a fourth embodiment of the present invention;

FIG. 13 is a functional block diagram of a fifth embodiment of a firmware management device according to the present invention;

FIG. 14 is a functional block diagram of a firmware management device according to a sixth embodiment of the present invention;

FIG. 15 is a functional block diagram of a firmware management device according to a seventh embodiment of the present invention.

The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.

Detailed Description

It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The main solution of the embodiment of the invention is as follows: the baseboard management controller virtualizes a pre-configured firmware management image file into a virtual starting system, and the virtual starting system is hung on a host; modifying the starting mode configuration of the host, wherein the modified starting mode configuration of the host is associated with the virtual starting system; and controlling the host to start from the virtual starting system according to the modified starting mode configuration, and loading the firmware management image file to perform firmware management.

When the prior art is used for firmware management, the firmware sintering and updating processes are complex, the manual participation degree is high, the automation degree is low, the maintainability is poor, the backup and management of all firmware configuration data cannot be realized, and the management function is incomplete.

The invention provides a solution, which simplifies the sintering and updating processes of the firmware, reduces the manual participation, realizes the backup and management of all firmware configuration data and perfects the firmware management function.

Referring to fig. 1, a first embodiment of a firmware management method according to the present invention provides a firmware management method, including:

step S10, the baseboard management controller virtualizes the pre-configured firmware management image file into a virtual boot system, and attaches the virtual boot system to the host.

The embodiment of the invention is mainly applied to the firmware management of the server single board, but is not limited to the firmware management of the server single board, and can also be applied to the firmware management of other equipment.

In this embodiment, the server board uses a PCIE bus and an interface standard, and the server CPU connects components of the server, such as a PCIE bridge, a PCH (Platform Controller Hub), a network card, an FC (fiber Controller), an SAS (Serial Attached SCSI) Controller, a video card, and the like, through the PCIE bus. In this embodiment, the firmware such as the PCIE bridge, the PCH, the network card, the FC, the SAS controller, and the video card may be managed.

The firmware managed by the server board can be divided into two types, one type is firmware related to a hardware device of the server host, and such firmware is only related to the type of the hardware device and is usually fixed, for example, firmware of devices such as a network card, an SAS controller, and a video card, and such firmware is referred to as firmware in the embodiment of the present invention. Another type of firmware is not tied to the server host hardware device and may change, such as the MAC address (physical address) of the network card, the WWN (World Wide Name) address of the FC and SAS controller, and such firmware is referred to as firmware configuration data in the embodiments of the present invention.

The firmware management according to the embodiment of the present invention includes, but is not limited to, sintering of firmware, updating of firmware, and backup and recovery of firmware configuration data.

Specifically, as an embodiment, the present embodiment uses a Baseboard Management Controller (BMC) to manage the server firmware sintering.

The baseboard Management controller is installed on a server mainboard, and uses an Intelligent Platform Management Interface (IPMI) to support functions such as local and remote diagnosis, console support, configuration Management, hardware Management, and troubleshooting.

The baseboard management controller is connected to the server host through a USB interface as a USB device such as a USB CD-ROM or a USB block device. The server may send an IPMI command to the substrate Management controller via an SMI (System Management Interface) bus to perform transmission and interaction of messages and commands.

The pre-configured firmware management image file is an integrated OS (Operation System), such as a DOS (Disk Operating System), and meets the requirement of loading and running of a server host, thereby implementing firmware management.

The firmware management image file includes: operating system, firmware management control software, firmware tool software, server firmware, and the like. The operating system is the running environment of all software and tools in the firmware management image file; the firmware management control software is used for controlling a firmware sintering process, a firmware configuration data acquisition process and communication with the substrate management controller; the firmware tool software is used for accessing specific firmware equipment and comprises firmware sintering tool software, firmware configuration data acquisition tool software, firmware configuration data recovery tool software and the like; the server firmware, including the firmware software that needs to be sintered to a specific device, may include all the firmware of the server board, and may also configure part of the firmware according to actual needs. The firmware management image file can also comprise a firmware configuration data file which is used for recovering the firmware configuration data and can be flexibly set according to actual needs.

The firmware management image file can be flexibly configured according to the actual requirement of firmware management. For example, when firmware sintering management or firmware update management is performed, the firmware management image file may include firmware to be sintered or updated, firmware sintering tool software, firmware management control software, and an operating system; when backing up firmware configuration data, the firmware management image file can comprise firmware configuration data acquisition tool software, firmware management control software and an operating system; when recovering the firmware configuration data, the firmware management image file may include firmware configuration data recovery tool software, a firmware configuration data file, firmware management control software, and an operating system.

After the baseboard management controller is started, the baseboard management controller virtualizes the pre-configured firmware management image file into a virtual starting system, and the virtual starting system is hung on the server host, namely the firmware management image file is hung on the server host as the virtual starting system. The server host may access the virtual boot system.

And step S20, modifying the starting mode configuration of the host, wherein the modified starting mode configuration of the host is associated with the virtual starting system.

After the baseboard management controller hooks the firmware management image file as a virtual boot system to the server host, specifically, as an implementation manner, the baseboard management controller modifies the configuration of the boot manner of the server host, and changes the original boot manner of the server host into a boot manner obtained from the baseboard management controller.

The baseboard management controller configures the starting mode obtained by the server host to be started from the virtual starting system, so that the server host is started from the hooked virtual starting system to perform firmware management.

And step S30, controlling the host to start from the virtual starting system according to the modified starting mode configuration, and loading the firmware management image file for firmware management.

After the bmc modifies the configuration of the start-up mode of the server host, specifically, as an embodiment, first, the bmc controls the server host to restart.

And after the server host is restarted, acquiring the starting mode from the baseboard management controller according to the starting mode modified by the baseboard management controller.

Then, the server host accesses the virtual boot system, boots from the virtual boot system, and loads the firmware management image file.

After the server host loads the firmware management image file, the firmware management image file enables the firmware management control software and the firmware tool software to automatically run in an operating system environment in a script or batch processing mode, and firmware sintering and updating or firmware configuration data backup and recovery are carried out according to the actual requirement of current firmware management.

In this embodiment, the baseboard management controller is linked to the host by virtualizing a pre-configured firmware management image file into a virtual boot system; then, modifying the starting mode configuration of the host, wherein the modified host starting mode configuration is associated with the virtual starting system; and the control host is configured according to the modified starting mode, is started from the virtual starting system, and loads the firmware management image file to perform firmware management. The embodiment improves the management function of the server firmware, simplifies the management process, realizes the automatic management of the server firmware and improves the maintainability of the server firmware.

Further, referring to fig. 2, a second embodiment of the firmware management method according to the present invention provides a firmware management method, based on the above embodiment shown in fig. 1, where the step S20 includes:

and step S21, the starting mode configuration of the host is modified to obtain the starting mode from the baseboard management controller and the host is started according to the obtained starting mode, wherein the obtained starting mode is started from the virtual starting system.

Specifically, as an implementation mode, after the baseboard management controller hooks the firmware management image file as a virtual boot system to the server host, first, the baseboard management controller modifies the configuration of the boot mode of the server host, and changes the original boot mode of the server host into the boot mode obtained from the baseboard management controller.

Then, the baseboard management controller configures the starting mode of the server host to be starting from the virtual starting system, and returns the configured starting mode to the server host, so that the server host accesses the virtual starting system.

In this embodiment, the pre-configured firmware management image file may be located locally in the baseboard control manager, may also be located in the remote debugger, and may be flexibly set according to actual needs. The baseboard control manager can be communicated with the remote debugging machine through the Ethernet to read the firmware management image file configured on the remote debugging machine.

If the pre-configured firmware management image file is located locally in the baseboard management controller, and the server host accesses the virtual boot system, the baseboard management controller controls the server host to load the firmware management image file from the local so that the server host is booted from the virtual boot system.

If the pre-configured firmware management image file is located in the remote debugging machine and the server host accesses the virtual starting system, the baseboard management controller analyzes the access protocol of the server host into a firmware management image file reading message and transmits the firmware management image file reading message to the remote debugging machine through the Ethernet. And after receiving the message, the remote debugging machine returns the data of the firmware management image file to the substrate management controller. And then, the baseboard management controller sends the obtained data of the firmware management image file to the server host through an access protocol, and controls the server host to load the firmware management image file so as to enable the server host to be started from the virtual starting system.

In this embodiment, the baseboard management controller modifies the configuration of the boot mode of the host to a configuration in which the host acquires the boot mode from the baseboard management controller, and the host boot mode configured by the baseboard management controller is started from the virtual boot system, so that the server host can be started from the virtual boot system to perform firmware management when the pre-configured firmware management image file is located in the local or remote debug machine of the baseboard management controller.

Further, referring to fig. 3, a third embodiment of the firmware management method according to the present invention provides a firmware management method, based on the above embodiment shown in fig. 2, where the step S30 includes:

and step S31, controlling the host to restart, and acquiring the starting mode from the baseboard management controller according to the modified starting mode configuration.

When the server host is restarted, in a BIOS (Basic Input Output System) loading stage, the server BIOS may issue an IPMI command to the substrate management controller through the SMI bus to obtain a starting mode.

Then, the baseboard management controller returns the configured starting mode of the server host to the server host, so that the server host accesses the virtual starting system.

And step S32, controlling the host to start from the virtual starting system according to the acquired starting mode, and loading the firmware management image file.

And after the baseboard management controller returns the starting mode to the server host, the server BIOS accesses the virtual starting system to start.

And the baseboard management controller responds to the request of the server host according to the access protocol and returns the firmware management image file to the server host so that the server host acquires the firmware management image file.

And then, the server host acquires the pre-configured firmware management image file through the baseboard management controller and loads the pre-configured firmware management image file.

And step S33, booting the host computer to manage the firmware.

After the server host loads the firmware management image file, the baseboard management controller controls the firmware management image file to guide the server host to carry out firmware management.

The firmware management control software and the firmware tool software automatically run in an operating system environment in a script or batch processing mode, and the firmware sintering and updating or the backup and recovery of firmware configuration data are carried out according to the actual requirement of the current firmware management.

The application scenario of the present invention is used as a server firmware sintering or updating for example. In this embodiment, both firmware sintering and firmware update can be implemented by firmware sintering.

When sintering the server firmware, the firmware management image file may include: operating system, firmware management control software, firmware sintering tool software, server firmware, and the like. The server firmware is the server firmware which needs to be sintered or updated currently, and may be all the firmware of the current server host, or may be part of the firmware of the current server host.

And after the BIOS of the control server loads the firmware management image file and starts, the firmware management control software and the firmware sintering tool software automatically run in a script or batch processing mode.

The firmware management control software sends an IPMI command to the substrate management controller through an SMI bus to acquire a configuration file of the sintering of the firmware, wherein the configuration file comprises specific firmware targeted by the sintering and firmware configuration data of the sintering. And the firmware sintering tool software accesses the specific firmware to sinter according to the acquired configuration file of the firmware sintering at this time.

The configuration data of the firmware sintered at this time can be configured locally in the baseboard management controller in advance, can also be configured in a remote debugging machine, and can be flexibly set according to actual needs. The firmware configuration data, such as the MAC address, needs to be sintered together with the network card firmware.

And when the firmware is sintered, the firmware management control software sends an IPMI command to the substrate management controller through the SMI bus and feeds back the progress and the result of the sintering or updating of the firmware to the substrate management controller.

In order to ensure the safety of firmware sintering or updating, if the baseboard management controller does not receive any message fed back by the firmware management control software within a preset timeout period, it is determined that the current firmware sintering fails.

And recording the firmware which is successfully sintered and the firmware which is failed to be sintered by the substrate management controller, and recording the firmware which is failed to be sintered and the reason of the failure to be sintered if the firmware is failed to be sintered.

Therefore, the baseboard management controller obtains the result of the current firmware sintering, and stores the result in the local or remote debugging machine of the baseboard management controller to complete the firmware management.

In this embodiment, the baseboard management controller controls the server host to restart, and acquires a starting mode from the baseboard management controller according to the modified starting mode configuration; and then, the control host is started from the virtual starting system according to the obtained starting mode, loads a preset firmware management image file and guides the host to carry out firmware management. The implementation carries out batch and automatic processing of server firmware management, perfects the function of server firmware management, simplifies the management flow, realizes automatic management of server firmware and improves the maintainability of server firmware.

Further, referring to fig. 4, a fourth embodiment of the firmware management method according to the present invention provides a firmware management method, based on the above embodiment shown in fig. 3, where the firmware management image file includes a firmware configuration data collection image file, and the step S33 includes:

step S331, scanning each firmware of the host through the firmware configuration data acquisition image file, and acquiring configuration data of the firmware.

If the current firmware management is the collection of server firmware configuration data, the firmware management image file may include: operating system, firmware management control software, firmware configuration data acquisition tool software.

Specifically, as an implementation manner, after the baseboard management controller controls the server BIOS to load the firmware management image file and start the firmware management image file, the firmware management control software and the firmware configuration data acquisition tool software automatically run in a script or batch processing manner, and the server host is guided to perform firmware management.

The firmware configuration data acquisition tool software scans hardware equipment information of the server host and acquires configuration data of the firmware.

Then, the firmware management control software sends the acquired data file to the baseboard management controller through an SMI bus, a USB or other channels.

Step S332, storing the firmware configuration data for recovering the firmware state.

And the baseboard management controller acquires the data file sent by the firmware management control software to obtain the configuration data of the server firmware.

And then, the baseboard management controller stores the obtained server firmware configuration data for the subsequent recovery of the server firmware state.

The server firmware configuration data can be stored locally in the baseboard management controller or in a remote debugging machine, and can be flexibly set according to actual needs. The background manager can acquire the configuration data of the server firmware through the Ethernet and store the configuration data into the database for the state recovery of the server firmware.

In this embodiment, the baseboard management controller scans each firmware of the host through the firmware configuration data acquisition image file, and acquires configuration data of the firmware; firmware configuration data is stored for firmware state recovery. In the embodiment, the server firmware configuration data is collected in a batched and automatic manner, the management of server firmware configuration data collection is realized, the management flow is simplified, the automatic management of the server firmware is realized, and the maintainability of the server firmware is improved.

Further, referring to fig. 5, a fifth embodiment of the firmware management method according to the present invention provides a firmware management method, based on the above embodiment shown in fig. 3, where the firmware management image file includes a firmware configuration data recovery image file, and the step S33 further includes:

and step S333, restoring the image file through the firmware configuration data, and controlling the corresponding firmware to restore the configuration data.

If the current firmware management is the collection of server firmware configuration data, the firmware management image file may include: operating system, firmware management control software, firmware configuration data recovery tool software, and firmware configuration data files.

Specifically, as an implementation manner, after the baseboard management controller controls the server BIOS to load the firmware management image file and start the firmware management image file, the firmware management control software and the firmware configuration data recovery tool software automatically run in a script or batch processing manner, and the server host is guided to perform firmware management.

The firmware configuration data recovery tool software accesses the firmware which needs to be subjected to firmware configuration data recovery, and recovers the firmware configuration data into specific hardware equipment information.

The firmware management control software sends the result of the firmware configuration data recovery to the baseboard management controller through an SMI bus, a USB or other channels.

And step 334, recording and storing the firmware configuration data recovery result.

And the baseboard management controller acquires the firmware configuration data recovery result sent by the firmware management control software, and records and stores the result of the firmware configuration data recovery of the server.

The result of the server firmware configuration data recovery can be stored in the local baseboard management controller or in a remote debugging machine, and can be flexibly set according to actual needs.

In this embodiment, the baseboard management controller controls the corresponding firmware to restore the configuration data by restoring the image file through the firmware configuration data; and recording and storing the firmware configuration data recovery result. According to the embodiment, the firmware configuration data is recovered, the management of the recovery of the server configuration data is realized, the management flow is simplified, the automatic management of the server firmware is realized, and the maintainability of the server firmware is improved.

Further, referring to fig. 6, a sixth embodiment of the firmware management method according to the present invention provides a firmware management method, based on the embodiment shown in any one of fig. 1 to 5 (this embodiment takes fig. 2 as an example), before step S10, the method further includes:

and step S40, the baseboard management controller configures the firmware management image file in a local or remote debugging machine of the baseboard management controller, the baseboard management controller communicates with the remote debugging machine, and the firmware management image file on the remote debugging machine is called.

Referring to fig. 7, if the pre-configured firmware management image file is located locally in the baseboard control manager, first, the firmware management image file is uploaded locally in the baseboard control manager through a background remote debugger, that is, a background PC (personal computer), or a WEB of the baseboard control manager. The baseboard control manager virtualizes the firmware management image file as a starting system.

And then, the baseboard control manager modifies the starting mode configuration of the server host, restarts the server host and controls the server host to start from the virtual starting system.

The server BIOS sends an IPMI command to the substrate control manager through SMI to acquire a starting mode, the substrate control manager configures the server host to start from the virtual starting system, and the server host accesses the virtual starting system.

The baseboard control manager responds to the request of the server host according to the access protocol, and the server host acquires the firmware management image file and guides the server host to start up by the OS integrated with the file.

Then, the CPU of the server automatically executes the appointed program in the firmware management image file, accesses the equipment under the host computer of the server through the appointed program in the firmware management image file, realizes the sintering, updating and configuration data acquisition and recovery of each firmware of the server, and feeds back the execution result to the substrate control manager through SMI.

Referring to fig. 8, if the pre-configured firmware management image file is located in the remote debugger, first, the remote debugger, that is, the background PC, communicates with the baseboard control manager through the ethernet, and the baseboard control manager virtualizes the firmware management image file as a boot system.

The server BIOS sends an IPMI command to the substrate control manager through SMI to acquire a starting mode, the substrate control manager configures the server host to start the system from the virtual mode, and the server host accesses the virtual mode.

And then, the baseboard control manager analyzes the access protocol of the server host into a firmware management image file reading message, and transmits the firmware management image file reading message to the remote debugging machine through the Ethernet. And after receiving the message, the remote debugging machine returns the data of the firmware management image file to the substrate management controller.

And then, the baseboard management controller sends the obtained data of the firmware management image file to the server host through an access protocol, and the server host is controlled to start from the virtual starting system and load the firmware management image file.

After the server host acquires the firmware management image file, the server host is guided to start by the OS integrated with the file, the CPU of the server automatically executes the appointed program in the firmware management image file, accesses the equipment on the server host through the appointed program in the firmware management image file, realizes the sintering, updating and acquisition and recovery of configuration data of each firmware of the server, and feeds back the execution result to the substrate control manager through SMI. And the baseboard control manager returns the feedback result to the background PC through the Ethernet.

In this embodiment, the baseboard management controller configures the firmware management image file in a local or remote debugger of the baseboard management controller, and the baseboard management controller communicates with the remote debugger to call the firmware management image file on the remote debugger for managing the server firmware. According to the embodiment, when the pre-configured firmware management image file is located in the local or remote debugging machine of the baseboard management controller, the server host can be started from the virtual starting system to perform firmware management, and the server firmware management flow is simplified.

Further, referring to fig. 9, a seventh embodiment of the firmware management method according to the present invention provides a firmware management method, based on the above embodiment shown in fig. 6, the step S20 further includes:

step S22, modify the configuration of the boot mode of the host, and backup the original boot configuration data of the host.

After the baseboard management controller hooks the firmware management image file as a virtual boot system to the server host, specifically, as an implementation manner, the baseboard management controller modifies the configuration of the boot manner of the server host, and changes the original boot manner of the server host into the boot manner obtained from the baseboard management controller, so that the server host is booted from the hooked virtual boot system to perform firmware management.

Meanwhile, the baseboard management controller records the original starting mode of the server host and stores the original starting configuration data of the server host. The original starting configuration data of the server host can be stored in the local of the baseboard management controller.

After the step S30, the method further includes:

and step S50, controlling the host to reset according to the original starting configuration data.

And after the baseboard management controller controls the server host to be configured according to the modified starting mode, starting from the virtual starting system and managing the firmware, the baseboard management controller controls the server host to reset according to the original starting configuration data of the server host.

Specifically, as an implementation manner, the baseboard management controller modifies the configuration of the starting manner of the server host according to the original starting configuration data of the server host, and restores the original starting manner of the server host.

Then, the baseboard management controller removes the virtual starting system hooked on the server host, controls the server host to reset, and restores to the state before the server firmware management is carried out.

In this embodiment, the baseboard management controller backs up original startup configuration data of the server host; after the control server host carries out firmware management, the control server host resets according to the original starting configuration data of the server host and restores to the state before the firmware management. According to the embodiment, the server host is reset after the firmware management of the server host is completed, the automatic management of the server firmware is realized, and the maintainability of the server firmware is improved.

Referring to fig. 10, a first embodiment of a firmware management apparatus according to the present invention provides a firmware management apparatus, including:

the virtualization module 100 is configured to virtualize a pre-configured firmware management image file into a virtual boot system, and attach the virtual boot system to a host.

Specifically, as an embodiment, the present embodiment uses a firmware management device to manage the server firmware burning. The firmware Management device is located in a Baseboard Management Controller (BMC).

The firmware management image file includes: operating system, firmware management control software, firmware tool software, server firmware, and the like. The operating system is the running environment of all software and tools in the firmware management image file; the firmware management control software is used for controlling a firmware sintering process, a firmware configuration data acquisition process and communication with the firmware management device; the firmware tool software is used for accessing specific firmware equipment and comprises firmware sintering tool software, firmware configuration data acquisition tool software, firmware configuration data recovery tool software and the like; the server firmware, including the firmware software that needs to be sintered to a specific device, may include all the firmware of the server board, and may also configure part of the firmware according to actual needs. The firmware management image file can also comprise a firmware configuration data file which is used for recovering the firmware configuration data and can be flexibly set according to actual needs.

When performing server firmware management, the virtual module 100 virtualizes a pre-configured firmware management image file as a virtual boot system, and attaches the virtual boot system to the server host, that is, attaches the firmware management image file as a virtual boot system to the server host. The server host may access the virtual boot system.

A modification module 200, configured to modify the boot method configuration of the host, where the modified boot method configuration of the host is associated with the virtual boot system.

After the virtual module 100 hooks the firmware management image file as a virtual boot system to the server host, specifically, as an implementation manner, the modification module 200 modifies the configuration of the boot manner of the server host, and changes the original boot manner of the server host into a boot manner obtained from the baseboard management control.

The modification module 200 configures the server host to obtain a starting mode of starting from the virtual starting system, so that the server host is started from the hooked virtual starting system to perform firmware management.

A management module 300, configured to control the host to start from the virtual boot system according to the modified boot mode configuration, and load the firmware management image file to perform firmware management.

After the modification module 200 modifies the configuration of the server host startup method, specifically, as an embodiment, first, the management module 300 controls the server host to restart.

After the server host is restarted, the startup mode is acquired from the firmware management device according to the startup mode modified by the modification module 200.

In this embodiment, the virtualization module 100 virtualizes a pre-configured firmware management image file into a virtual boot system, and attaches the virtual boot system to a host; then, the modification module 200 modifies the boot method configuration of the host, and the modified boot method configuration of the host is associated with the virtual boot system; the management module 300 controls the host to start from the virtual boot system according to the modified boot mode configuration, and loads the firmware management image file for firmware management. The embodiment improves the management function of the server firmware, simplifies the management process, realizes the automatic management of the server firmware and improves the maintainability of the server firmware.

Further, referring to fig. 10, a second embodiment of the firmware management apparatus according to the present invention provides a firmware management apparatus, based on the first embodiment of the firmware management apparatus according to the present invention shown in fig. 10, the modifying module 200 is further configured to:

After the virtual module 100 hooks the firmware management image file as a virtual boot system to the server host, specifically, as an implementation manner, first, the modification module 200 modifies the configuration of the boot manner of the server host, and changes the original boot manner of the server host into the boot manner obtained from the firmware management device on the baseboard management controller.

Then, the modification module 200 configures the starting mode of the server host to be starting from the virtual starting system, and returns the configured starting mode to the server host, so that the server host accesses the virtual starting system.

If the pre-configured firmware management image file is local to the baseboard management controller, and the server host accesses the virtual boot system, the management module 300 controls the server host to load the firmware management image file locally from the baseboard management controller, so that the server host is booted from the virtual boot system.

If the pre-configured firmware management image file is located in the remote debugging machine and the server host accesses the virtual boot system, the management module 300 parses the access protocol of the server host into a firmware management image file reading message, and transmits the firmware management image file reading message to the remote debugging machine through the ethernet. And after receiving the message, the remote debugging machine returns the data of the firmware management image file to the firmware management device. Then, the management module 300 sends the obtained data of the firmware management image file to the server host through the access protocol, and controls the server host to load the firmware management image file, so that the server host is started from the virtual boot system.

In this embodiment, the modification module 200 modifies the configuration of the host start-up mode to a mode in which the host acquires the start-up mode from the bmc, and the host start-up mode configured by the modification module 200 is started from the virtual start-up system, so that when the pre-configured firmware management image file is located in the bmc local or remote debugger, the server host can be started from the virtual start-up system to perform firmware management.

Further, referring to fig. 11, a firmware management device according to a third embodiment of the present invention provides a firmware management device, based on the second embodiment of the firmware management device shown in fig. 10, the management module 300 includes:

and a restarting unit 310, configured to control the host to restart, and obtain a starting mode from the baseboard management controller according to the modified starting mode configuration.

After the modification module 200 modifies the configuration of the boot method of the server host, specifically, as an embodiment, first, the reboot unit 310 controls the server host to reboot.

When the server host is restarted, in a BIOS (Basic Input Output System) loading stage, the server BIOS may issue an IPMI command to the restart unit 310 through an SMI bus to obtain a starting mode.

Then, the restarting unit 310 returns the server host starting mode configured by the modification module 200 to the server host, so that the server host accesses the virtual starting system.

A configuration unit 320, configured to control the host to start from the virtual boot system according to the obtained boot manner, and load the firmware management image file.

After the reboot unit 310 returns the boot mode to the server host, the server BIOS accesses the virtual boot system to boot.

The configuration unit 320 responds to the request of the server host according to the access protocol, and returns the firmware management image file to the server host, so that the server host obtains the firmware management image file.

Then, the server host acquires the pre-configured firmware management image file through the firmware management device and loads the pre-configured firmware management image file.

A management unit 330, configured to direct the host to perform firmware management.

After the server host loads the firmware management image file, the management unit 330 controls the firmware management image file to guide the server host to perform firmware management.

After the configuration unit 320 controls the server BIOS to load the firmware management image file and start, the management unit 330 enables the firmware management control software and the firmware sintering tool software to automatically run in a script or batch processing manner.

The firmware management control software sends an IPMI command to the management unit 330 through the SMI bus, and obtains a configuration file of the current firmware sintering, including specific firmware targeted by the current sintering and configuration data of the current firmware sintering. And the firmware sintering tool software accesses the specific firmware to sinter according to the acquired configuration file of the firmware sintering at this time.

While firmware sintering is performed, the firmware management control software sends an IPMI command to the management unit 330 via the SMI bus, and feeds back the progress and result of firmware sintering to the management unit 330.

In order to ensure the safety of firmware sintering, if the management unit 330 does not receive any message fed back by the firmware management control software within a preset timeout period, it is determined that the current firmware sintering fails.

The management unit 330 records the firmware that is successfully sintered and the firmware that is failed to be sintered, and if the firmware fails to be sintered, records the firmware that is failed to be sintered and the reason for the failure of sintering.

Therefore, the basic management unit 330 obtains the result of the current firmware sintering, and stores the result in the local or remote debugging machine of the baseboard management controller, thereby completing the firmware management.

In this embodiment, the restart unit 310 controls the server host to restart, and acquires the start mode from the bmc according to the modified start mode configuration; then, the configuration unit 320 controls the host to start from the virtual boot system according to the obtained boot method, loads a preset firmware management image file, and the management unit 330 guides the host to perform firmware management. The implementation carries out batch and automatic processing of server firmware management, perfects the function of server firmware management, simplifies the management flow, realizes automatic management of server firmware and improves the maintainability of server firmware.

Further, referring to fig. 12, a fourth embodiment of the firmware management apparatus according to the present invention provides a firmware management apparatus, based on the embodiment shown in fig. 11, where the firmware management image file includes a firmware configuration data collection image file, and the management unit 330 includes:

the collecting subunit 331 is configured to scan each firmware of the host through the firmware configuration data collecting image file, and collect configuration data of the firmware.

Specifically, as an implementation manner, after the configuration unit 320 controls the server BIOS to load the firmware management image file and start the firmware management image file, the acquisition subunit 331 enables the firmware management control software and the firmware configuration data acquisition tool software to automatically run in a script or batch processing manner, and guides the server host to perform firmware management.

The firmware management control software then sends the retrieved data file to the first storage subunit 332 via an SMI bus, USB, or other channel.

A first storage subunit 332, configured to store the firmware configuration data for the firmware state recovery.

The first storage subunit 332 obtains the data file sent by the firmware management control software to obtain the configuration data of the server firmware.

Then, the first storage subunit 332 stores the obtained server firmware configuration data for subsequent recovery of the server firmware state.

In this embodiment, the collecting subunit 331 scans each firmware of the host through the firmware configuration data collecting image file, and collects configuration data of the firmware; the first storage subunit 332 stores firmware configuration data for firmware state recovery. In the embodiment, the server firmware configuration data is collected in a batched and automatic manner, the management of server firmware configuration data collection is realized, the management flow is simplified, the automatic management of the server firmware is realized, and the maintainability of the server firmware is improved.

Further, referring to fig. 13, a fifth embodiment of the firmware management apparatus according to the present invention provides a firmware management apparatus, based on the embodiment shown in fig. 11, where the firmware management image file includes a firmware configuration data recovery image file, and the management unit 330 further includes:

a recovery subunit 333, configured to recover the image file according to the firmware configuration data, and control the corresponding firmware to recover the configuration data.

Specifically, as an embodiment, after the configuration unit 320 controls the server BIOS to load the firmware management image file and start, the recovery subunit 333 automatically runs the firmware management control software and the firmware configuration data recovery tool software in a script or batch processing manner, and guides the server host to perform firmware management.

The firmware management control software sends the result of the firmware configuration data recovery to the second storage subunit 334 through an SMI bus, USB or other channel.

And a second storage subunit 334, configured to record and store the firmware configuration data recovery result.

The second storage subunit 334 obtains the result of recovering the firmware configuration data sent by the firmware management control software, and records and stores the result of recovering the firmware configuration data of the server this time.

In this embodiment, the recovery subunit 333 controls the corresponding firmware to recover the configuration data by recovering the image file with the firmware configuration data; the second storage subunit 334 records and stores the firmware configuration data recovery result. According to the embodiment, the firmware configuration data is recovered, the management of the recovery of the server configuration data is realized, the management flow is simplified, the automatic management of the server firmware is realized, and the maintainability of the server firmware is improved.

Further, referring to fig. 14, a sixth embodiment of the firmware management device according to the present invention provides a firmware management device, based on the embodiment shown in any one of fig. 10 to 13 (this embodiment takes the second embodiment of the firmware management device according to the present invention shown in fig. 10 as an example), the firmware management device further includes:

a configuration module 400, configured to configure the firmware management image file in a local or remote debugger of the baseboard management controller, where the baseboard management controller communicates with the remote debugger to retrieve the firmware management image file on the remote debugger.

In this embodiment, the firmware management image file pre-configured by the configuration module 400 may be located locally in the baseboard control manager, or may be located in a remote debugger, and may be flexibly set according to actual needs. The baseboard control manager can be communicated with the remote debugging machine through the Ethernet to read the firmware management image file configured on the remote debugging machine.

Referring to fig. 7, if the firmware management image file pre-configured by the configuration module 400 is located locally in the baseboard control manager, first, the firmware management image file is uploaded locally in the baseboard control manager through a background remote debugger, that is, a background PC (personal computer), or a WEB of the baseboard control manager. The virtualization module 100 virtualizes the firmware management image file as a boot system.

Then, the modification module 200 modifies the configuration of the boot method of the server host, and the management module 300 restarts the server host and controls the server host to boot from the virtual boot system.

The server BIOS sends an IPMI command to the substrate control manager through the SMI to obtain a start mode, the modification module 200 configures the server host to start from the virtual start system, and the server host accesses the virtual start system.

The management module 300 responds to the request of the server host according to the access protocol, and the server host acquires the firmware management image file and guides the server host to start up by the OS integrated with the file.

Referring to fig. 8, if the firmware management image file pre-configured by the configuration module 400 is located in the remote debugger, first, the remote debugger, that is, the background PC, communicates with the baseboard control manager through the ethernet, and the virtualization module 100 virtualizes the firmware management image file as a boot system.

Then, the management module 300 parses the access protocol of the server host into a firmware management image file read packet, and transmits the firmware management image file read packet to the remote debugger through the ethernet. After receiving the message, the remote debugger returns the data of the firmware management image file to the management module 300.

Then, the management module 300 sends the obtained data of the firmware management image file to the server host through the access protocol, and controls the server host to start from the virtual boot system and load the firmware management image file.

After the server host acquires the firmware management image file, the server host is guided to start by the OS integrated with the file, the server CPU automatically executes the program specified in the firmware management image file, accesses the device on the server host through the program specified in the firmware management image file, realizes sintering, updating, and acquisition and recovery of configuration data of each firmware of the server, and feeds back an execution result to the management module 300 through the SMI. The management module 300 returns the feedback result to the background PC through the ethernet.

In this embodiment, the configuration module 400 configures the firmware management image file in the local or remote debugger of the bmc, and the virtual module 100 and the management module 300 may communicate with the remote debugger to call the firmware management image file on the remote debugger for managing the server firmware. According to the embodiment, when the pre-configured firmware management image file is located in the local or remote debugging machine of the baseboard management controller, the server host can be started from the virtual starting system to perform firmware management, and the server firmware management flow is simplified.

Further, referring to fig. 15, a seventh embodiment of the firmware management device of the present invention provides a firmware management device, based on the above-mentioned embodiment shown in fig. 14, the modification module 200 is further configured to,

and modifying the starting mode configuration of the host computer, and backing up the original starting configuration data of the host computer.

After the virtual module 100 hooks the firmware management image file as a virtual boot system to the server host, specifically, as an implementation manner, the modification module 200 modifies the configuration of the boot manner of the server host, and changes the original boot manner of the server host into the boot manner obtained from the firmware management device on the baseboard management controller, so that the server host is booted from the hooked virtual boot system to perform firmware management.

Meanwhile, the modification module 200 records the original starting mode of the server host and stores the original starting configuration data of the server host. The original starting configuration data of the server host can be stored in the local of the baseboard management controller.

The firmware management apparatus further includes:

a reset module 500, configured to control the host to reset according to the original start configuration data.

After the management module 300 controls the server host to be configured according to the modified starting mode, start from the virtual starting system, and perform firmware management, the reset module 500 controls the server host to be reset according to the original starting configuration data of the server host.

Specifically, as an embodiment, the reset module 500 modifies the configuration of the boot mode of the server host according to the original boot configuration data of the server host, and restores the original boot mode of the server host.

Then, the reset module 500 removes the virtual boot system hooked on the server host, and controls the server host to reset to a state before performing the server firmware management.

In this embodiment, the modification module 200 backs up original startup configuration data of the server host; after the management module 300 controls the server host to perform firmware management, the reset module 500 controls the server host to reset according to the original start configuration data of the server host, and then the server host is restored to the state before performing firmware management. According to the embodiment, the server host is reset after the firmware management of the server host is completed, the automatic management of the server firmware is realized, and the maintainability of the server firmware is improved.

The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. A firmware management method, comprising the steps of:

the method comprises the following steps that a baseboard management controller virtualizes a pre-configured firmware management image file into a virtual starting system for host access, and the virtual starting system is connected to a host in a hanging mode, wherein the firmware management image file comprises an operating system, firmware management control software, firmware tool software, server firmware and a firmware configuration data file;

the baseboard management controller controls the starting mode of the host to be changed into the mode from the virtual starting system;

and the baseboard management controller controls the host to be restarted, so that the host is started from the virtual starting system according to the starting mode of the virtual starting system when being restarted, and the firmware management image file is loaded for firmware management.

2. A firmware management method as claimed in claim 1, wherein said step of modifying the boot-up mode configuration of the host, the step of associating the modified host boot-up mode configuration with the virtual boot-up system comprises:

3. The firmware management method according to claim 2, wherein the step of controlling the host to boot from the virtual boot system according to the modified boot configuration, and loading the firmware management image file for firmware management comprises:

and guiding the host to perform firmware management.

4. A firmware management method as claimed in claim 3, wherein the firmware management image file comprises a firmware configuration data collection image file, and the step of booting the host for firmware management comprises:

storing the firmware configuration data for the firmware state recovery.

5. A firmware management method as claimed in claim 3, wherein the firmware management image file comprises a firmware configuration data recovery image file, the step of booting the host for firmware management further comprising:

and recording and storing the firmware configuration data recovery result.

6. A firmware management method according to any one of claims 1 to 5, wherein the baseboard management controller virtualizes a pre-configured firmware management image file as a virtual boot system, and before the step of attaching to the host, the method further comprises:

7. The firmware management method of claim 6, wherein the step of modifying the boot-mode configuration of the host further comprises:

8. A firmware management apparatus, characterized in that the firmware management apparatus comprises:

the virtual module is used for virtualizing a pre-configured firmware management image file into a virtual starting system for host access and hanging the virtual starting system on a host, wherein the firmware management image file comprises an operating system, firmware management control software, firmware tool software, server firmware and a firmware configuration data file;

the modification module is used for controlling the starting mode of the host to be modified to be started from the virtual starting system;

and the management module is used for controlling the host to restart so that the host can be started from the virtual starting system according to the starting mode of the virtual starting system when being restarted, and the firmware management image file is loaded for firmware management.

9. The firmware management device of claim 8, wherein the modification module is further to,

the starting mode configuration of the host is modified to be that a starting mode is obtained from a baseboard management controller and is started according to the obtained starting mode, and the obtained starting mode is started from the virtual starting system;

the management module comprises:

10. The firmware management apparatus of claim 8 or 9, wherein the modification module is further to,

the firmware management apparatus further includes: