WO2023193351A1

WO2023193351A1 - Server starting method and apparatus, device, and storage medium

Info

Publication number: WO2023193351A1
Application number: PCT/CN2022/101148
Authority: WO
Inventors: 张旭; 李瑞东
Original assignee: 浪潮(山东)计算机科技有限公司
Priority date: 2022-04-06
Filing date: 2022-06-24
Publication date: 2023-10-12
Also published as: CN114428963A; CN114428963B

Abstract

The present application relates to the technical field of communications, and discloses a server starting method and apparatus, a device, and a storage medium. The method comprises: respectively packaging a target process in BMC firmware and BIOS firmware of a target server to trigger, when the BMC firmware and the BIOS firmware are running, the target process to perform firmware verification; in the firmware verification process, by means of data interaction between the BMC firmware and the BIOS firmware, respectively performing first verification on the BIOS firmware by using the BMC firmware and second verification on the BMC firmware by using the BIOS firmware; and determining whether the first verification and the second verification are passed, and if not, powering off the target server. According to the present application, the BMC firmware and the BIOS firmware are verified when no peripheral trusted verification device needs to be added, such that the credibility of the firmware of the server is improved to ensure secure starting of the server.

Description

A server startup method, device, equipment and storage medium

Cross-references to related applications

This application requests the priority of the Chinese patent application submitted to the China Patent Office on April 6, 2022, with the application number 202210352874.8, and the application name is "A server startup method, device, equipment and storage medium", the entire content of which is incorporated by reference incorporated in this application.

Technical field

The present application relates to the field of communication technology, and in particular to a server startup method, device, equipment and storage medium.

Background technique

BMC (Baseboard Management Controller) is a baseboard management controller, which can realize server-related control, information supervision and other functions. It is a platform for intuitively presenting server information. The server client can access the server BMC through web, ipmitool, snmp tools, etc. to obtain server information. BMC is essentially an embedded system. During use, it will face security risks such as program integrity being destroyed, operating system being attacked, and web applications being implanted with malicious code. In addition, domestic servers currently generally use foreign BMC chips (such as ASPEED series AST2400, AST2500 and other models), the security of which is unknown, and the core technology is controlled by others. The same is true for BIOS firmware.

Traditional security methods can generally only protect against problems at the network level or operating system level. For attacks on server BIOS firmware and attacks on server BMC firmware, traditional "containment and killing" methods are even more limited and cannot guarantee firmware security. Secure boot of the server and trusted verification of BMC firmware and BIOS firmware are the only way to go. Currently, it is necessary to add peripheral circuits (such as trusted cryptographic modules or firmware verification modules, etc.). This method greatly increases the cost of the server, and no peripheral devices can be added to the server that has been shipped to the customer's site.

Therefore, how to improve the reliability of the server firmware to ensure safe startup of the server is an urgent technical problem to be solved by those skilled in the art.

Contents of the invention

The first aspect of this application provides a server starting method, including:

Encapsulate the target process in the BMC firmware and BIOS firmware of the target server respectively, so as to trigger the target process to perform firmware verification when the BMC firmware and the BIOS firmware are running;

During the firmware verification process, through data interaction between the BMC firmware and the BIOS firmware, the BMC firmware is used to perform a first verification on the BIOS firmware and the BIOS firmware is used to perform a first verification on the BMC firmware. Second verification; and

Determine whether the first verification and the second verification pass, and in response to the failure of the first verification and the second verification, perform power-off processing on the target server.

Optionally, the server startup method also includes:

Pre-create custom protocols; and

Control the BMC firmware and the BIOS firmware to interact with the firmware verification information according to the structure defined in the custom protocol; wherein the firmware verification information includes BIOS firmware verification information and BMC firmware verification information.

Optionally, the firmware verification information includes any one or more of firmware self-test results, core process running status, firmware startup status, firmware size, firmware version number and preset encryption check code.

Optionally, the server startup method also includes:

When the BMC firmware and the BIOS firmware are running, the BMC firmware and the BIOS firmware are respectively controlled to perform self-tests on themselves.

Optionally, after controlling the BMC firmware and the BIOS firmware respectively to perform self-tests, the method further includes:

Control the BMC firmware and the BIOS firmware respectively to save their own firmware self-test results. When the firmware verification information contains the firmware self-test results, control the BMC firmware and the BIOS firmware to save the firmware self-test results. Interaction.

Optionally, using the BMC firmware to perform a first verification on the BIOS firmware and using the BIOS firmware to perform a second verification on the BMC firmware includes:

Utilize the BMC firmware to obtain the BIOS firmware verification information from the BIOS firmware through IPMI commands, so that the BMC firmware uses the BIOS firmware verification information to perform the first verification on the BIOS firmware; and

The BIOS firmware is used to obtain the BMC firmware verification information from the BMC firmware through an IPMI command, so that the BIOS firmware uses the BMC firmware verification information to perform a second verification on the BMC firmware.

Optionally, powering off the target server includes:

The BMC board equipped with the BMC firmware is powered off through the programmable logic device CPLD and stops powering on the processor of the target server.

Optionally, the method also includes:

In response to both the first verification and the second verification passing, the target server is started.

The second aspect of this application provides a server starting device, including:

The process encapsulation and triggering module is used to encapsulate the target process in the BMC firmware and BIOS firmware of the target server respectively, so as to trigger the target process to perform firmware verification when the BMC firmware and the BIOS firmware are running;

An interactive verification module, configured to perform first verification on the BIOS firmware using the BMC firmware and using the BIOS firmware through data interaction between the BMC firmware and the BIOS firmware during the firmware verification process. Perform a second verification of the BMC firmware; and

A judgment module, configured to judge whether both the first verification and the second verification pass, and in response to the failure of both the first verification and the second verification, perform power-off processing on the target server.

A third aspect of the present application provides an electronic device, including a memory and one or more processors. Computer-readable instructions are stored in the memory, and the computer-readable instructions are executed by the one or more processors. When, the one or more processors are caused to execute the steps of the foregoing server startup method.

A fourth aspect of the application provides one or more non-volatile computer-readable storage media storing computer-readable instructions that, when executed by one or more processors, cause the one or more Multiple processors execute the steps of the foregoing server startup method.

Description of the drawings

In order to explain the embodiments of the present application or the technical solutions in the prior art more clearly, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are only This is an embodiment of the present application. For those of ordinary skill in the art, other drawings can be obtained based on the provided drawings without exerting creative efforts.

Figure 1 is a flow chart of a server startup method provided by one or more embodiments of the present application;

Figure 2 is a schematic diagram of a specific server startup method provided by one or more embodiments of the present application;

Figure 3 is a schematic structural diagram of a server startup device provided by one or more embodiments of the present application;

Figure 4 is a structural diagram of a server-starting electronic device provided by one or more embodiments of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

In the existing technology, on the one hand, the traditional "containment and killing" means are more limited for attacks on server BIOS firmware and attacks on server BMC firmware. If the security of the firmware cannot be guaranteed, the server cannot be safely started, and the BMC firmware cannot be safely started. Trusted verification with BIOS firmware is the only way to go. On the other hand, it is currently necessary to add new peripheral circuits. This method greatly increases the cost of the server, and peripheral devices cannot be added to the server that has been shipped to the customer's site. In response to the above technical shortcomings, this application provides a server startup solution that verifies the BMC firmware and BIOS firmware without adding peripheral trusted verification devices, thereby improving the credibility of the server firmware to ensure safe startup of the server.

Figure 1 is a flow chart of a server startup method provided by an embodiment of the present application. As shown in Figure 1, the server startup method includes:

S11: Encapsulate the target process in the BMC firmware and BIOS firmware of the target server respectively, so as to trigger the target process to perform firmware verification when the BMC firmware and the BIOS firmware are running.

In this embodiment, the target process is first encapsulated in the BMC firmware and BIOS firmware of the target server, so that the target process is triggered to perform firmware verification when the BMC firmware and the BIOS firmware are running. The target process is also a piece of code, and the BMC firmware and the BIOS firmware are essentially program codes. The target process can be encapsulated in the BMC firmware and BIOS firmware. When the target server motherboard is powered on , the BMC firmware and the BIOS firmware start to run one after another. When both the BMC firmware and the BIOS firmware start to run, the target process encapsulated in the BMC firmware and the BIOS firmware starts to run. Interlock verification is performed between the BMC firmware and the BIOS firmware.

S12: During the firmware verification process, through data interaction between the BMC firmware and the BIOS firmware, use the BMC firmware to perform a first verification on the BIOS firmware and use the BIOS firmware to verify the BMC The firmware performs a second verification.

In this embodiment, during the firmware verification process, through data interaction between the BMC firmware and the BIOS firmware, the BMC firmware is used to perform the first verification on the BIOS firmware and the BIOS firmware is used to perform the first verification. The BMC firmware performs a second verification. Currently, the verification of the BMC firmware or the BIOS firmware requires the use of peripheral circuits, such as trusted cryptographic modules, firmware verification modules, etc., and the cost of peripheral hardware circuits is relatively high. The above-mentioned peripheral circuits are embedded in the server. It is difficult to add hardware trusted peripherals to the server that has been shipped to the customer's site.

This embodiment uses a software method to perform server firmware verification, that is, based on the target process encapsulated in the BMC firmware and the BIOS firmware, as well as the data interaction mode and existing between the BMC firmware and the BIOS firmware. The channel performs server firmware verification, which not only reduces the cost of firmware trustworthy verification by adding peripheral circuits, but also realizes firmware verification of client room equipment. Specifically, on the one hand, the BMC firmware is used to perform the first verification on the BIOS firmware through data exchange between the BMC firmware and the BIOS firmware; on the other hand, through the BMC firmware and the BIOS firmware The data exchange between them uses the BIOS firmware to perform a second verification on the BMC firmware.

S13: Determine whether the first verification and the second verification pass, and if not, perform power-off processing on the target server.

In this embodiment, after the verification, it is comprehensively determined whether the first verification and the second verification pass, and in response to the failure of the first verification and the second verification, the target server is Power outage processing. In response to both the first verification and the second verification passing, the target server is started. That is, if not, the target server is powered off. If both the first verification and the second verification pass, it means that the BMC firmware and the BIOS firmware of the target server have passed the trusted verification, and both the BMC firmware and the BIOS firmware are in Safe state, at which point the target server can be safely started. Similarly, as mentioned above, if any one of the BMC firmware and the BIOS firmware fails the trusted verification, that is, any one of the first verification and the second verification fails, then Power off the target server.

In particular, this embodiment performs power-off processing on the BMC board equipped with the BMC firmware and stops powering on the processor of the target server. Specifically, the programmable logic device CPLD is used to power off the BMC board equipped with the BMC firmware. Perform power-off processing and stop powering on the processor of the target server. That is to say, if the BMC firmware fails to verify the BIOS firmware information, the programmable logic device CPLD is notified to power off the BMC module and no longer powers the CPU. If the BIOS firmware verifies the BMC firmware If the information does not pass, the programmable logic device CPLD is notified to power off the BMC module and no longer power on the CPU, thereby achieving the purpose of interlocking verification of the BMC firmware and the BIOS firmware. Of course, the programmable logic device CPLD is essentially a control unit, which needs to be determined according to the specific configuration of the server. Other devices that can achieve the same effect can be used, and this embodiment is not limited to this.

It can be seen that the embodiment of the present application first encapsulates the target process in the BMC firmware and BIOS firmware of the target server respectively, so as to trigger the target process to perform firmware verification when the BMC firmware and the BIOS firmware are running; and then perform the firmware verification. During the process, through data interaction between the BMC firmware and the BIOS firmware, the BMC firmware is used to perform a first verification on the BIOS firmware and the BIOS firmware is used to perform a second verification on the BMC firmware; Finally, it is determined whether the first verification and the second verification pass, and if not, the target server is powered off. In the embodiment of this application, when the BMC firmware and BIOS firmware in the server are running, firmware verification is performed through the target process encapsulated in the firmware, that is, based on the data interaction between the BMC firmware and BIOS firmware in the server, the BMC firmware and BIOS firmware are implemented Interlock verification. The beneficial effect of this embodiment is to verify the BMC firmware and BIOS firmware without adding a peripheral trusted verification device, thereby improving the credibility of the server firmware to ensure safe startup of the server.

Figure 2 is a flow chart of a specific server startup method provided by an embodiment of the present application. As shown in Figure 2, the server startup method includes:

S21: Create custom protocols in advance.

S22: Control the BMC firmware and the BIOS firmware to interact with the firmware verification information according to the structure defined in the custom protocol; wherein the firmware verification information includes BIOS firmware verification information and BMC firmware verification information.

In this embodiment, further, a custom protocol is created in advance. The custom protocol is mainly an agreement on the underlying transmission protocol between the BMC firmware and the BIOS firmware, that is, an agreement on the interactive data between the BMC firmware and the BIOS firmware. On this basis, the BMC firmware and the BIOS firmware are controlled to interact with the firmware verification information according to the structure defined in the custom protocol. It is easy to understand that the custom protocol can be a part of the code in the target process, or can be separately packaged in the BMC firmware and the BIOS firmware, which is not limited in this embodiment.

In this embodiment, in order to make the verification results more accurate, when the BMC firmware and the BIOS firmware are running, the BMC firmware and the BIOS firmware are respectively controlled to perform self-tests on themselves. Control the BMC firmware and the BIOS firmware respectively to save their own firmware self-test results. When the firmware verification information contains the firmware self-test results, control the BMC firmware and the BIOS firmware to save the firmware self-test results. Interaction.

In this embodiment, the firmware verification information includes any one or more of firmware self-test results, core process running status, firmware startup status, firmware size, firmware version number, and preset encryption check code. It can be understood that the firmware verification information includes BIOS firmware verification information and BMC firmware verification information. The BIOS firmware verification information is the firmware self-test results of the BIOS firmware, core process running status, firmware startup status, firmware size, and firmware version. Any one or more of the number and preset encryption check code. The BMC firmware verification information is the firmware self-test result of the BMC firmware, core process operation status, firmware startup status, firmware size, firmware version number and Any one or more of the preset encryption check codes. Therefore, this embodiment adopts a custom protocol method for firmware verification. The protocol format, that is, the protocol structure is defined as:

It should be noted that SelfTest in the above-mentioned custom structure represents the self-test result of the BMC firmware or the BIOS firmware. When the BMC firmware or the BIOS firmware is running, it needs to self-test its own operating status and will perform the self-test. The result is saved; CoreProcessStatus indicates the running status of the core process of the BMC firmware or the BIOS firmware; InitCompletely indicates whether the BMC firmware or the BIOS firmware is fully started to prevent a certain firmware core process from not starting to power on the server, causing the server to Abnormal; FirmwareSize represents the firmware size, the BMC firmware is generally 64M in size, and the BIOS firmware is generally 32M in size. When the data is incorrect, it means the firmware is damaged; Version[4] represents the firmware version number, the BMC firmware or all The BIOS firmware will verify the version number of the other party; CheckCode represents the check code of the BMC firmware or the BIOS firmware. The check code is a string of encrypted characters to prevent the BMC firmware or BIOS of the server from The firmware has been tampered with or tampered with. The above information types can be customized according to different application scenarios, which is not limited in this embodiment.

S23: Use the BMC firmware to obtain the BIOS firmware verification information from the BIOS firmware through IPMI commands, so that the BMC firmware uses the BIOS firmware verification information to perform the first verification on the BIOS firmware.

S24: Use the BIOS firmware to obtain the BMC firmware verification information from the BMC firmware through IPMI commands, so that the BIOS firmware uses the BMC firmware verification information to perform a second verification on the BMC firmware.

S25: Determine whether the first verification and the second verification pass. If not, perform power-off processing on the target server.

In this embodiment, the BMC firmware and the BIOS firmware generally interact through IPMI (Intelligent Platform Management Interface, Intelligent Platform Management Interface) commands. IPMI is an open standard hardware management interface specification. After the target server motherboard is powered on, the BMC firmware and the BIOS firmware run respectively. The BMC firmware and the BIOS firmware first perform self-tests, and then interactively transmit the information in the above structure through IPMI commands. On the one hand, the BMC firmware is used to obtain the BIOS firmware verification information from the BIOS firmware through IPMI commands, so that the BMC firmware uses the BIOS firmware verification information to perform a first verification on the BIOS firmware; On the other hand, the BIOS firmware is used to obtain the BMC firmware verification information from the BMC firmware through IPMI commands, so that the BIOS firmware uses the BMC firmware verification information to perform a second verification on the BMC firmware. . Similarly, if the BMC firmware fails to verify the BIOS firmware information, that is, the first verification fails, the programmable logic device CPLD will power off the BMC module and no longer power on the CPU; the BIOS firmware will verify If the BMC firmware information fails to pass the verification, that is, the second verification fails, the CPLD is notified to power off the BMC module and no longer power on the CPU to achieve the purpose of interlock verification of the BMC and BIOS.

It can be seen that the embodiment of the present application controls the BMC firmware and the BIOS firmware to interact with the firmware verification information according to the structure defined in the custom protocol on the basis of pre-creating a custom protocol. Then the BMC firmware is used to obtain the BIOS firmware verification information from the BIOS firmware through IPMI commands to perform the first verification of the BIOS firmware, and at the same time, the BIOS firmware is used to obtain the verification information from the BMC through IPMI commands. The BMC firmware verification information is obtained in the firmware to perform a second verification on the BMC firmware. The beneficial effect of this embodiment is that the server firmware is verified using software and protocols. After the interlocking verification of the BMC firmware and the BIOS firmware is completed, the target server is turned on again, which can ensure the integrity of the server firmware and prevent the firmware from being Malicious strings to further protect server firmware security.

Referring to Figure 3, the embodiment of the present application also discloses a server starting device, which includes:

The process encapsulation and triggering module 11 is used to encapsulate the target process in the BMC firmware and BIOS firmware of the target server respectively, so as to trigger the target process to perform firmware verification when the BMC firmware and the BIOS firmware are running;

The interactive verification module 12 is configured to perform first verification on the BIOS firmware using the BMC firmware and using the BIOS firmware through data interaction between the BMC firmware and the BIOS firmware during the firmware verification process. The firmware performs a second verification on the BMC firmware;

The judgment module 13 is used to judge whether the first verification and the second verification pass, and if not, power off the target server.

It can be seen that the embodiment of the present application first encapsulates the target process in the BMC firmware and BIOS firmware of the target server respectively, so as to trigger the target process to perform firmware verification when the BMC firmware and the BIOS firmware are running; and then perform the firmware verification. During the process, through data interaction between the BMC firmware and the BIOS firmware, the BMC firmware is used to perform a first verification on the BIOS firmware and the BIOS firmware is used to perform a second verification on the BMC firmware; Finally, it is determined whether the first verification and the second verification pass, and if not, the target server is powered off. In the embodiment of this application, when the BMC firmware and BIOS firmware in the server are running, firmware verification is performed through the target process encapsulated in the firmware, that is, based on the data interaction between the BMC firmware and BIOS firmware in the server, the BMC firmware and BIOS firmware are implemented The interlocking verification verifies the BMC firmware and BIOS firmware without adding peripheral trusted verification equipment, improving the credibility of the server firmware to ensure safe startup of the server.

In some specific embodiments, the server startup device further includes:

Protocol creation module for pre-creating custom protocols;

A control module configured to control the BMC firmware and the BIOS firmware to interact with firmware verification information according to the structure defined in the custom protocol; wherein the firmware verification information includes BIOS firmware verification information and BMC firmware verification information. ;

A self-test module, configured to control the BMC firmware and the BIOS firmware respectively to perform self-tests on themselves when the BMC firmware and the BIOS firmware are running;

A storage module, configured to respectively control the BMC firmware and the BIOS firmware to save their own firmware self-test results. When the firmware verification information contains the firmware self-test results, control the BMC firmware and the BIOS firmware to store the firmware self-test results. Interact with firmware self-test results.

In some specific embodiments, the interactive verification module 12 specifically includes:

The first verification unit is configured to use the BMC firmware to obtain the BIOS firmware verification information from the BIOS firmware through IPMI commands, so that the BMC firmware uses the BIOS firmware verification information to perform verification on the BIOS firmware. First verification;

The second verification unit is configured to use the BIOS firmware to obtain the BMC firmware verification information from the BMC firmware through IPMI commands, so that the BIOS firmware uses the BMC firmware verification information to perform verification on the BMC firmware. Second verification.

In some specific embodiments, the judgment module 13 is specifically configured to power off the BMC board equipped with the BMC firmware through the programmable logic device CPLD and stop powering on the processor of the target server.

Further, the embodiment of the present application also provides an electronic device. FIG. 4 is a structural diagram of the electronic device 20 according to an exemplary embodiment. The content in the figure cannot be considered as any limitation on the scope of the present application.

FIG. 4 is a schematic structural diagram of an electronic device 20 provided by an embodiment of the present application. The electronic device 20 may specifically include: one or more processors 21, at least one memory 22, a power supply 23, a communication interface 24, an input-output interface 25 and a communication bus 26. The memory 22 is used to store computer-readable instructions, which are loaded and executed by the processor 21 to implement relevant steps in the server startup method disclosed in any of the foregoing embodiments.

In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be applicable Any communication protocol of the technical solution of this application is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the external world, and its specific interface type can be selected according to specific application needs. Here Not specifically limited.

In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, a random access memory, a magnetic disk or an optical disk, etc. The resources stored thereon can include an operating system 221, computer readable instructions 222, data 223, etc., and the storage method can be Short-term storage or permanent storage.

Among them, the operating system 221 is used to manage and control each hardware device and computer readable instructions 222 on the electronic device 20 to realize the calculation and processing of the massive data 223 in the memory 22 by the processor 21. It can be Windows Server, Netware, Unix, Linux, etc. In addition to computer-readable instructions that can be used to complete the server startup method executed by the electronic device 20 disclosed in any of the foregoing embodiments, the computer-readable instructions 222 may further include computer-readable instructions that can be used to complete other specific tasks. instruction. Data 223 may include interaction data collected by electronic device 20 .

Further, embodiments of the present application also disclose one or more non-volatile computer-readable storage media storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, one or more The processor executes the steps of the server startup method disclosed in any of the foregoing embodiments.

Each embodiment in this specification is described in a progressive manner. Each embodiment focuses on its differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other. As for the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple. For relevant details, please refer to the description in the method section.

Finally, it should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that these entities or any such actual relationship or sequence between operations. Furthermore, the terms "comprises," "comprises," or any other variations thereof are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus that includes a list of elements includes not only those elements, but also those not expressly listed other elements, or elements inherent to the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article, or apparatus that includes the stated element.

The server startup method, device, equipment and storage medium provided by this application have been introduced in detail above. This article uses specific examples to illustrate the principles and implementation methods of this application. The description of the above embodiments is only used to help understand this application. The application method and its core idea; at the same time, for those of ordinary skill in the field, there will be changes in the specific implementation and application scope based on the ideas of this application. In summary, the contents of this specification should not be understood as a limitation on this application.

Claims

A server startup method, characterized by including:

Encapsulate the target process in the BMC firmware and BIOS firmware of the target server respectively, so as to trigger the target process to perform firmware verification when the BMC firmware and the BIOS firmware are running;

During the firmware verification process, through data interaction between the BMC firmware and the BIOS firmware, the BMC firmware is used to perform a first verification on the BIOS firmware and the BIOS firmware is used to perform a first verification on the BMC firmware. Second verification; and

Determine whether the first verification and the second verification pass, and in response to the failure of the first verification and the second verification, perform power-off processing on the target server.
The server startup method according to claim 1, further comprising:

Pre-create custom protocols; and

Control the BMC firmware and the BIOS firmware to interact with the firmware verification information according to the structure defined in the custom protocol; wherein the firmware verification information includes BIOS firmware verification information and BMC firmware verification information.
The server startup method according to claim 2, wherein the firmware verification information includes firmware self-test results, core process operation status, firmware startup status, firmware size, firmware version number and preset encryption check code. any one or more.
The server startup method according to any one of claims 1-3, further comprising:

When the BMC firmware and the BIOS firmware are running, the BMC firmware and the BIOS firmware are respectively controlled to perform self-tests on themselves.
The server startup method according to claim 4, characterized in that after controlling the BMC firmware and the BIOS firmware respectively to perform self-tests, the method further includes:

Control the BMC firmware and the BIOS firmware respectively to save their own firmware self-test results. When the firmware verification information contains the firmware self-test results, control the BMC firmware and the BIOS firmware to save the firmware self-test results. Interaction.
The server startup method according to any one of claims 2 to 5, wherein the BMC firmware is used to perform a first verification on the BIOS firmware and the BIOS firmware is used to perform a third verification on the BMC firmware. Second verification, including:

Utilize the BMC firmware to obtain the BIOS firmware verification information from the BIOS firmware through IPMI commands, so that the BMC firmware uses the BIOS firmware verification information to perform the first verification on the BIOS firmware; and

The BIOS firmware is used to obtain the BMC firmware verification information from the BMC firmware through an IPMI command, so that the BIOS firmware uses the BMC firmware verification information to perform a second verification on the BMC firmware.
The server startup method according to any one of claims 1 to 6, characterized in that said powering off the target server includes:

The BMC board equipped with the BMC firmware is powered off through the programmable logic device CPLD and stops powering on the processor of the target server.
The server startup method according to any one of claims 1-7, characterized in that the method further includes:

In response to both the first verification and the second verification passing, the target server is started.
A server startup device, characterized by including:

The process encapsulation and triggering module is used to encapsulate the target process in the BMC firmware and BIOS firmware of the target server respectively, so as to trigger the target process to perform firmware verification when the BMC firmware and the BIOS firmware are running;

An interactive verification module, configured to perform first verification on the BIOS firmware using the BMC firmware and using the BIOS firmware through data interaction between the BMC firmware and the BIOS firmware during the firmware verification process. Perform a second verification of the BMC firmware; and

A judgment module, configured to judge whether both the first verification and the second verification pass, and in response to the failure of both the first verification and the second verification, perform power-off processing on the target server.
An electronic device, characterized in that it includes a memory and one or more processors. Computer-readable instructions are stored in the memory. When the computer-readable instructions are executed by the one or more processors, the computer-readable instructions cause the The one or more processors perform the steps of the method according to any one of claims 1-8.
One or more non-volatile computer-readable storage media storing computer-readable instructions, characterized in that, when executed by one or more processors, the computer-readable instructions cause the one or more processors to Carry out the steps of the method according to any one of claims 1-8.