Search

CN-122001758-A - Server firmware configuration issuing system

CN122001758ACN 122001758 ACN122001758 ACN 122001758ACN-122001758-A

Abstract

The embodiment of the application provides a server firmware configuration issuing system which comprises a management end and at least one managed end, wherein the management end is used for managing the incidence relation between server identification information and firmware configuration data, determining a server to be configured and corresponding firmware configuration data according to the incidence relation, issuing the firmware configuration data to the server to be configured, and the managed end is deployed in the server and used for receiving the firmware configuration data issued by the management end, executing firmware configuration operation and executing configuration effective operation according to a control instruction of the management end. The centralized management and the automatic issuing of the firmware configuration are realized, the operation and maintenance personnel are not required to log in the server one by one to perform manual configuration, the manual intervention is reduced, the efficiency and the accuracy of batch configuration are improved, and meanwhile, the consistency of the issuing process is ensured through the unified control of the management end to the managed end.

Inventors

  • LU DAXIN

Assignees

  • 紫光恒越技术有限公司

Dates

Publication Date
20260508
Application Date
20260319

Claims (12)

  1. 1. A server firmware configuration delivery system, the system comprising: The management terminal and at least one managed terminal; the management terminal is used for managing the association relation between the server identification information and the firmware configuration data, determining a server to be configured and the corresponding firmware configuration data according to the association relation, and issuing the firmware configuration data to the server to be configured; The managed end is deployed in the server and is used for receiving the firmware configuration data issued by the management end, executing the firmware configuration operation and executing the configuration effective operation according to the control instruction of the management end.
  2. 2. The system of claim 1, wherein the managed side is further configured to perform the step of receiving firmware configuration data issued by the managed side if it is determined that a configuration flag bit is in a target state, where the target state is used to characterize that the managed side is not loaded with firmware configuration.
  3. 3. The system of claim 1, wherein the managed side is further configured to obtain the firmware configuration data through a file transfer service, and perform the firmware configuration operation if the firmware configuration data is determined to pass a consistency check.
  4. 4. The system of claim 1, wherein the management side establishes an association between server identification information and firmware configuration data through a mapping file, and the server identification information includes a serial number of a server.
  5. 5. The system of claim 4, wherein the mapping file includes a correspondence between a sequence number range and firmware configuration data for determining firmware configuration data corresponding to servers belonging to the same sequence number range.
  6. 6. The system of claim 1, wherein the management side is further configured to issue configuration validation policy information to the managed side; the managed terminal is also used for executing configuration validation operation according to the configuration validation strategy information.
  7. 7. The system of claim 6, wherein the configuration validation policy information includes a restart sequence and checkpoint information; The managed end is further configured to sequentially execute a restarting operation according to the restarting sequence, verify a configuration state according to the checkpoint information after each restarting step, and continuously execute a next restarting step if it is determined that the configuration state of the current restarting step meets a preset requirement.
  8. 8. The system of claim 1, wherein the management side is further configured to record a configuration issuing status of the managed side, where the configuration issuing status includes an operation result of an activation phase, a registration phase, a configuration download phase, a configuration import phase, and a configuration validation phase.
  9. 9. The system of claim 1, wherein the management side and the managed side communicate via a preset protocol message, the preset protocol message including a message type field and a load field, the information included in the message type field and the load field being used to indicate an operation instruction and status information.
  10. 10. The system of claim 1, wherein the management side is further configured to send the activation information by broadcasting; The managed terminal is further configured to send registration information to the management terminal after receiving the activation information, where the registration information includes identification information of a server where the managed terminal is located.
  11. 11. The system of claim 1, wherein the managed side is further configured to feed back operational status information to the managed side; the management end is further configured to trigger a retry operation according to a preset policy when determining that the operation state information indicates failure, where the retry operation includes resending the firmware configuration data or resending the control instruction.
  12. 12. The system of claim 1, wherein the managed side is further configured to backup the current firmware configuration prior to performing the firmware configuration operation, and to restore to the pre-configuration firmware configuration state based on the backup if the configuration validation operation is determined to fail or a rollback instruction is received.

Description

Server firmware configuration issuing system Technical Field The application relates to the technical field of server management, in particular to a server firmware configuration issuing system. Background In a large data center with a mass server, there are two general scenarios that a large-scale firmware of the server is required (the firmware refers to a program directly written in a ROM of a hardware device and is responsible for the basic bottom operation of the hardware device, the firmware is a soul of the hardware device and serves as the most basic bottom work, the firmware not only controls the hardware, but also allows the software to interact with the hardware effectively, the server firmware includes a BMC firmware, a BIOS firmware, a CPLD firmware, etc., where the BMC, baseboard Management Controller refers to a baseboard management controller, is a core component of the server management system and is responsible for monitoring and managing the whole server, and is a small system independent of other hardware on the server, independent of an operating system and having an IP address, the BMC is composed of two parts, namely, a BMC chip and a BMC firmware, the BMC chip provides computing capability, and supports the operation of the BMC firmware, and the firmware is a core control program for implementing various out-of-band management functions: And initializing and configuring firmware when the first scene is put on shelf. The data center usually subdivides the cloud service, the running basic software type, the function roles born and other dimensions carried by the server on the basis of the same model of the server, namely subdivides subdivision models such as a computing model, a database model, a network model, a storage model and the like according to the difference between the service and the hardware configuration. Thus, servers of different subdivision models have differentiated requirements for firmware configuration. For example, a compute-based server may need to turn off NUMA in BIOS configuration, turn off CPU dynamic frequency modulation, set a fan control strategy to high performance mode in BMC or manually specify fan speed, while a web-based server may maintain default settings in BIOS configuration, turn on power saving or balancing mode in BMC. And (3) temporary configuration adjustment in the installation process of the second scene. In order to improve the installation efficiency, a data center generally adopts a PXE mode (PXE, preboot eXecution Environment refers to a standard method for enabling a server without a system to be "bare machine" and automatically download and install an operating system through a network, and the method is a basic stone technology for large-scale server deployment and system maintenance of the data center and a cloud computing platform) to install the operating system for the server in batches. Therefore, the "start-up sequence" in the BIOS of the server needs to be set to be started up from the network before the system is installed, and then restored to the original start-up sequence setting after the system is installed. It follows that in the server provisioning (provisioning refers to a series of preparation and steps that need to be performed during the new server unsealing, installing, provisioning and configuration process, these steps include a series of hardware preparation, firmware setting, operating system installation, network configuration, system setting, etc.), and later maintenance processes, it is necessary to frequently perform differential configuration and change operations on the firmware of a large number of servers. However, in the related art, the above firmware configuration operation is mainly performed manually on a station-by-station basis. The operation and maintenance personnel need to log in the remote management page of each server one by one according to the planned server role classification, manually modify each configuration parameter in the BMC and the BIOS, or import configuration files prepared in advance one by one, and manually restart the server to enable configuration to be effective after configuration is completed. When the manual operation mode is faced with the batch configuration requirement of hundreds or thousands of servers, the manual operation mode is low in efficiency and long in time consumption, and omission or configuration errors are easy to occur. Moreover, the errors are often detected in the formal online operation stage of the server, so that the troubleshooting is difficult and the service stability is affected. Therefore, it is needed to solve the problem of how to implement batch, automation and differentiated distribution of server firmware configuration, and to effectively monitor and manage the configuration process. Disclosure of Invention The embodiment of the application aims to provide a server firmware configuration issuing system which is used for realizing the t