WO2022100307A1 - 一种服务器bios与bmc之间的数据交互方法、装置及设备 - Google Patents

一种服务器bios与bmc之间的数据交互方法、装置及设备 Download PDF

Info

Publication number
WO2022100307A1
WO2022100307A1 PCT/CN2021/121222 CN2021121222W WO2022100307A1 WO 2022100307 A1 WO2022100307 A1 WO 2022100307A1 CN 2021121222 W CN2021121222 W CN 2021121222W WO 2022100307 A1 WO2022100307 A1 WO 2022100307A1
Authority
WO
WIPO (PCT)
Prior art keywords
bmc
server
bios
ipmi
link
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2021/121222
Other languages
English (en)
French (fr)
Inventor
孙秀强
黄家明
李勋堂
乔英良
班华堂
李道童
艾山彬
姚藩益
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Wave Intelligent Technology Co Ltd
Original Assignee
Suzhou Wave Intelligent Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Suzhou Wave Intelligent Technology Co Ltd filed Critical Suzhou Wave Intelligent Technology Co Ltd
Priority to US18/034,057 priority Critical patent/US11907073B2/en
Publication of WO2022100307A1 publication Critical patent/WO2022100307A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operations
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G06F11/142—Reconfiguring to eliminate the error
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0751—Error or fault detection not based on redundancy
    • G06F11/0754—Error or fault detection not based on redundancy by exceeding limits
    • G06F11/076—Error or fault detection not based on redundancy by exceeding limits by exceeding a count or rate limit, e.g. word- or bit count limit
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operations
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G06F11/1417—Boot up procedures
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operations
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G06F11/1441—Resetting or repowering
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/81—Threshold

Definitions

  • the present application relates to the field of computer technologies, and in particular, to a data interaction method, apparatus, device, and readable storage medium between a server BIOS and a BMC.
  • BIOS Basic Input Output System
  • BMC Baseboard Management Controller
  • the BIOS is mainly responsible for the initialization of the server hardware devices and the booting of the operating system
  • the BMC is mainly responsible for the temperature monitoring and energy consumption management of each component of the server, as well as the display of asset information.
  • the server initialization action can only be handled by the BIOS firmware and can obtain valid data in time, but the BIOS cannot display the hardware information of the server.
  • the BMC can log in to view the basic hardware device information of the server at any time through remote management, but this asset information is handed by the BIOS to the server. At the same time, some functions of the BIOS also need to exchange data with the BMC.
  • the BIOS and the BMC exchange data through the IPMI (Intelligent Platform Management Interface) protocol physical link (hereinafter referred to as the IPMI link).
  • IPMI Intelligent Platform Management Interface
  • the BIOS will not be able to perform normal data interaction with the BMC, resulting in the inability to view the basic hardware device information of the server, and even affect some functions of the BIOS.
  • the purpose of this application is to provide a data interaction method, device, device and readable storage medium between server BIOS and BMC, to solve the problem that BIOS and BMC cannot perform data interaction due to abnormal IPMI link status or BMC abnormality. question. Its specific plan is as follows:
  • the present application provides a data interaction method between a server BIOS and a BMC, applied to the BIOS, including:
  • S3 initialize the device and boot to the BDS stage, obtain the state of the IPMI link between the BIOS and the BMC again, and obtain a second state value; if the second state value is normal, enter S2, if the first The second state value is abnormal, then enter S4;
  • the method further includes:
  • the executing the restart command controls the server to restart, and enters S1, including:
  • the data interaction with the BMC through the IPMI link includes:
  • the data interaction with the BMC through the IPMI link includes:
  • the latest configuration information of the target function is obtained from the BMC through the IPMI link.
  • the self-recovery according to the target data in the local preset memory address space includes:
  • the present application provides a data exchange device between a server BIOS and a BMC, which is applied to the BIOS and includes:
  • the first state obtaining module used to obtain the state of the IPMI link between the BIOS and the BMC when the server is powered on, and obtain the first state value; if the first state value is normal, enter the booting module, if If the first state value is abnormal, enter the second state acquisition module;
  • the booting module used for data interaction with the BMC through the IPMI link, and booting to the system;
  • the second state acquisition module used to initialize the device and boot to the BDS stage, obtain the state of the IPMI link between the BIOS and the BMC again, and obtain the second state value; if the second state value is normal , enter the boot and start module, if the second state value is abnormal, enter the restart judgment module;
  • the restart judgment module for judging whether the number of restarts of the server exceeds a preset threshold; if the number of restarts of the server exceeds the preset threshold, the abnormality processing module is entered, and if the number of restarts of the server does not exceed the preset threshold threshold, enter the restart module;
  • the exception handling module is used to determine that the BMC is abnormal, perform self-recovery according to the target data on the local preset memory address space, and boot into the system;
  • the restarting module is used to execute a restarting command to control the server to restart, and enter the first state acquiring module.
  • the exception handling module is further used for:
  • the present application provides a data exchange device between a server BIOS and a BMC, including:
  • Processor used to store computer programs
  • Processor used to execute the computer program to implement the above-mentioned data interaction method between the server BIOS and the BMC.
  • the present application provides a readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, is used to implement the above-mentioned communication between the server BIOS and the BMC. Data Interaction Methods.
  • a method for data interaction between a server BIOS and a BMC provided by the present application, applied to the BIOS, includes: when the server is powered on, acquiring the state of the IPMI link between the BIOS and the BMC, and obtaining a first state value; If the first state value is normal, data exchange with the BMC is performed through the IPMI link, and the system is booted. If the first state value is abnormal, the device is initialized and booted to the BDS stage, and the data between the BIOS and the BMC is obtained again. The state of the IPMI link is obtained, and the second state value is obtained; if the second state value is normal, data exchange is performed with the BMC through the IPMI link, and the system is booted to boot.
  • the number of restarts of the server is determined. Whether the preset threshold is exceeded; if the number of restarts of the server exceeds the preset threshold, it is determined that the BMC is abnormal, self-recovery is performed according to the target data in the local preset memory address space, and the system is booted to boot. If the number of restarts of the server does not exceed the preset threshold If the threshold is exceeded, the restart command is executed to control the server to restart, and the above steps are repeated.
  • this method determines whether to perform data interaction according to the state of the IPMI link between the BIOS and the BMC. At the same time, the method determines whether the BMC is caused by an abnormality by confirming whether the number of restarts of the server reaches a preset threshold in the BDS stage of the BIOS. It cannot be activated. When the number of server restarts has reached the preset threshold and the BMC has not been activated, it is determined that the BMC is abnormal. If the number of server restarts has not reached the preset threshold, the BIOS will execute the system restart action, where the preset threshold is internally customized by the BIOS. Variable confirmation, can be set freely. This design can achieve safe and effective data exchange between the server BIOS and BMC, avoid the problem of data exchange failure due to abnormal IPMI link, detect abnormal BMC status in time, and improve the security and reliability of the server. It is suitable for server products of all architectures.
  • the present application also provides a data exchange apparatus, device and readable storage medium between the server BIOS and the BMC, the technical effects of which correspond to the technical effects of the above method, and are not repeated here.
  • Embodiment 1 is a flowchart of Embodiment 1 of a data interaction method between a server BIOS and a BMC provided by the application;
  • Embodiment 2 is a flowchart of Embodiment 2 of a data interaction method between a server BIOS and a BMC provided by the present application;
  • FIG. 3 is a functional block diagram of an embodiment of a data exchange device between a server BIOS and a BMC provided by the present application;
  • FIG. 4 is a schematic structural diagram of an embodiment of a data exchange device between a server BIOS and a BMC provided by the present application.
  • the core of the present application is to provide a data interaction method, device, device and readable storage medium between the server BIOS and the BMC, which can ensure the safe and effective data interaction between the server BIOS and the BMC, and avoid the failure of data interaction due to an abnormal IPMI link. It can detect the abnormal state of the BMC in time, and improve the security and reliability of the server.
  • Embodiment 1 of a data interaction method between a server BIOS and a BMC provided by the present application will be introduced below. Referring to FIG. 1 , Embodiment 1 is applied to BIOS, including:
  • the BIOS is mainly responsible for the initialization of the server hardware devices and the booting of the operating system
  • the BMC is mainly responsible for the temperature monitoring, energy consumption management and asset information display of each component of the server.
  • the BIOS can obtain the hardware device information of the server, but the BIOS cannot display the hardware device information of the server.
  • the BMC can view the hardware device information of the server through the remote management login at any time.
  • the hardware device information is obtained by the BIOS through the IPMI link. It is passed to the BMC for display, so the data interaction process between the BIOS and the BMC during the server initialization process is essential.
  • some functions of the BIOS also require data interaction with the BMC, such as boot item setting, watchdog time setting, vlan and other functions through IPMI commands.
  • this embodiment provides a safe and effective data exchange solution between the BIOS and the BMC of a general server.
  • the BIOS obtains the status of the IPMI link between the local and the BMC through the IPMI protocol, and judges whether the IPMI link is normal at this time according to the status value fed back by the IPMI protocol. , then enter S102, interactively set and display the data to be transmitted between the BIOS and BMC according to the default transmission mode, and boot to the system normally; if the feedback status value is abnormal, enter S103, and abandon all data interaction at this time content, the BIOS continues to initialize other devices to the BDS (Boot Device Select, boot device selection) stage.
  • BDS Boot Device Select, boot device selection
  • the content of data interaction between the BIOS and the BMC includes, but is not limited to, hardware device information transmitted by the BIOS to the BMC, and data related to some functions of the BIOS transmitted by the BMC to the BIOS, such as function configuration data. Therefore, S102 includes: sending hardware device information to the BMC through the IPMI link to display the hardware device information; and acquiring the latest configuration information of the target function from the BMC through the IPMI link.
  • S103 initialize the device and boot to the BDS stage, obtain the state of the IPMI link between the BIOS and the BMC again, and obtain a second state value; if the second state value is normal, go to S102, if the first If the second state value is abnormal, enter S104;
  • S104 Determine whether the number of restarts of the server exceeds the preset threshold; if the number of restarts of the server exceeds the preset threshold, enter S105, and if the number of restarts of the server does not exceed the preset threshold, enter S106;
  • the causes of the abnormal IPMI link may include the following: the IPMI link between the BIOS and the BMC is not initialized normally when the server is turned on, or the physical link is damaged, or the IPMI protocol is not initialized normally, or the BMC is abnormal.
  • the BMC exception includes: the BMC is not initialized normally, or the BMC is damaged.
  • the default time for BMC to activate from the first power-on or power-off restart of the motherboard is 60 seconds, while the startup time of the BIOS is 40 seconds, so after the restart, the BIOS can wait for a period of time.
  • the waiting time here is not less than 20 seconds.
  • S105 determine that the BMC is abnormal, perform self-recovery according to the target data on the local preset memory address space, and boot into the system;
  • BIOS some functions of the BIOS also need to exchange data with the BMC.
  • the BIOS cannot obtain the relevant data of these functions from the BMC, which affects the smooth progress of the boot process.
  • the BIOS performs a self-recovery mechanism through the data (ie, NVRAM variables) stored in the preset memory address space in the early stage, obtains the original data of these functions, and no longer obtains the latest data of these functions from the BMC. Therefore, it can continue to boot to the system without being restricted by the parameters passed by the BMC.
  • the status information that the BMC is damaged or not activated can also be printed out through the serial port of the BIOS.
  • This embodiment provides a data exchange method between a server BIOS and a BMC. Whether to perform data exchange is determined according to the state of the IPMI link between the BIOS and the BMC, and the link state is confirmed once when the server is powered on. Then execute the data exchange between the BIOS and the BMC. If the link status is abnormal, the BIOS abandons the data exchange and continues to boot to the BDS stage to confirm the link status again. If the link status is confirmed to be normal again, execute the data exchange between the BIOS and the BMC. If it is confirmed that the link status is abnormal again, it is judged whether the number of restarts of the server has reached the preset threshold. If the threshold is set, it is determined that the BMC is abnormal, and the BIOS performs self-recovery according to the target data in the preset memory address space, and boots to the system.
  • This embodiment has strong reproducibility and scalability.
  • the IPMI protocol an interactive protocol between the BIOS and the BMC, is used to confirm the link status, and then the BIOS confirms the subsequent execution actions according to the status value returned by the IPMI protocol, which greatly improves the performance of the server.
  • Reliability and security can also meet the time limit requirement of BMC activation through the time consumption of system restart, which provides reliability for batch deployment and application of data center servers.
  • This embodiment is not limited by the server chip architecture, and is applicable to a variety of Server products with different architectures conform to the future development trend of server technology.
  • the second embodiment specifically includes:
  • the first step after the motherboard of any architecture server is powered on, the BIOS first checks whether the link with the BMC is normal through the IPMI protocol. If the link between the BIOS link and the BMC is normal, the BIOS communicates with the BMC through the IPMI protocol. Perform data interaction and transfer, and boot to the system normally.
  • the BIOS will not perform IPMI protocol data transmission at this time, and then the BIOS will initialize and start the device.
  • the BIOS will pass IPMI again
  • the protocol checks whether the link between the communication and the BMC is normal. If the link between the BIOS link and the BMC is normal, the BIOS exchanges and transmits data with the BMC through the IPMI protocol, and boots to the system normally.
  • Step 3 If the link between the BIOS link and the BMC is still abnormal, determine whether the number of restarts reaches the preset threshold. If the number of restarts does not reach the preset threshold, the BIOS executes the system restart command, waits for the time to allow the BMC to activate, and continues Perform the first and second steps.
  • the fourth step if the number of restarts has reached the preset threshold, the BMC is still not activated or the BMC is damaged and the IPMI link cannot be used, then the BIOS restores the information that needs to obtain data from the BMC through the NVRAM variable inside the BIOS, and the BIOS outputs the BMC through the serial port. Inactive or corrupt alert messages.
  • a data interaction device between a server BIOS and a BMC provided by an embodiment of the present application is introduced below.
  • a data interaction device between a server BIOS and a BMC described below and a data interaction device between the server BIOS and the BMC described above The data interaction methods can be referenced to each other.
  • the data exchange device between the server BIOS and the BMC of the present embodiment, applied to the BIOS includes:
  • the first state obtaining module 301 used to obtain the state of the IPMI link between the BIOS and the BMC when the server is powered on, and obtain a first state value; if the first state value is normal, enter the booting module 302 , if the first state value is abnormal, enter the second state acquisition module 303;
  • the booting module 302 used for performing data interaction with the BMC through the IPMI link, and booting to the system;
  • the second state obtaining module 303 used to initialize the device and boot to the BDS stage, obtain the state of the IPMI link between the BIOS and the BMC again, and obtain a second state value; if the second state value is If it is normal, enter the boot start module 302, if the second state value is abnormal, enter the restart judgment module 304;
  • the restart judgment module 304 for judging whether the number of restarts of the server exceeds a preset threshold; if the number of restarts of the server exceeds the preset threshold, enter the abnormality processing module 305, if the number of restarts of the server does not exceed If the preset threshold is set, enter the restart module 306;
  • the abnormality processing module 305 is used to determine that the BMC is abnormal, perform self-recovery according to the target data in the local preset memory address space, and boot into the system;
  • the restarting module 306 is configured to execute a restarting command to control the server to restart, and enter the first state obtaining module 301 .
  • the exception handling module is further configured to:
  • the apparatus for exchanging data between the server BIOS and the BMC in this embodiment is used to implement the aforementioned method for exchanging data between the server BIOS and the BMC. Therefore, the specific implementation of the apparatus can be found in the data between the server BIOS and the BMC mentioned above.
  • the embodiment part of the interaction method for example, the first state acquisition module 301, the boot start module 302, the second state acquisition module 303, the restart judgment module 304, the exception handling module 305, and the restart module 306 are respectively used to realize the above-mentioned server BIOS and Steps S101, S102, S103, S104, S105, and S106 in the data exchange method between BMCs. Therefore, reference may be made to the descriptions of the corresponding partial embodiments for specific implementations thereof, which will not be described herein again.
  • the apparatus for exchanging data between the server BIOS and the BMC in this embodiment is used to implement the foregoing method for exchanging data between the server BIOS and the BMC, its function corresponds to that of the foregoing method, and will not be repeated here.
  • the present application also provides a data exchange device between the server BIOS and the BMC, as shown in FIG. 4 , including:
  • Processor 100 used to store computer programs
  • Processor 200 used to execute the computer program to implement the data interaction method between the server BIOS and the BMC as described above.
  • the present application provides a readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, is used to realize the data between the server BIOS and the BMC as described above interactive method.
  • a software module can be placed in random access memory (RAM), internal memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other in the technical field. in any other known form of storage medium.
  • RAM random access memory
  • ROM read only memory
  • electrically programmable ROM electrically erasable programmable ROM
  • registers hard disk, removable disk, CD-ROM, or any other in the technical field. in any other known form of storage medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

一种服务器BIOS与BMC之间的数据交互方法、装置、设备及可读存储介质。根据BIOS和BMC之间IPMI链路的状态来决定是否进行数据交互，同时，通过在BIOS的BDS阶段确认服务器的重启次数是否达到预设阈值，判断BMC是否因存在异常导致无法激活，当服务器重启次数已经达到预设阈值且BMC仍未激活，则判定BMC异常，若服务器重启次数尚未达到预设阈值，则BIOS执行系统重启动作，其中预设阈值由BIOS内部自定义的变量确认，可以自由设置。如此设计可以达到服务器BIOS和BMC安全有效的数据交互，避免因IPMI链路异常导致数据交互失败的问题，及时发现BMC异常状态，提升服务器的安全性和可靠性，适用于所有架构的服务器产品。

Description

一种服务器BIOS与BMC之间的数据交互方法、装置及设备
本申请要求在2020年11月11日提交中国专利局、申请号为202011254073.5、发明名称为“一种服务器BIOS与BMC之间的数据交互方法、装置及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，特别涉及一种服务器BIOS与BMC之间的数据交互方法、装置、设备及可读存储介质。
背景技术
随着芯片行业和互联网行业的快速发展，国内外各个互联网公司开始对数据中心的建设也越加重视，同时对服务器的采购及批量部署也要求越来越高。无论是MIPS架构、Power架构、ARM架构、还是传统的X86架构包括英特尔和AMD等类型的服务器需求也在增加，所有架构的服务器产品都必不可少的使用到BIOS(Basic Input Output System，基本输入输出系统)和BMC(Baseboard Management Controller，基板管理控制器)这两大类管理软件。
BIOS主要负责服务器硬件设备的初始化及操作系统的引导，BMC则主要负责服务器各个部件的温度监控和能耗管理以及资产信息显示。服务器初始化动作只能由BIOS固件负责且能及时获取有效数据，但是BIOS无法将服务器的硬件信息进行显示，BMC可以随时通过远程管理登陆查看服务器的基本硬件设备信息，但是这个资产信息是BIOS递给BMC进行显示的，同时，BIOS的部分功能也需要与BMC进行数据交互。
一般的，BIOS和BMC通过IPMI(Intelligent Platform Management Interface，智能平台管理接口)协议物理链路(以下简称为IPMI链路)进行数据交互，如果BIOS和BMC之间的IPMI链路状态异常，或者 BMC异常，BIOS将无法与BMC进行正常的数据交互，导致无法查看服务器的基本硬件设备信息，甚至影响BIOS的部分功能。
发明内容
本申请的目的是提供一种服务器BIOS与BMC之间的数据交互方法、装置、设备及可读存储介质，用以解决因IPMI链路状态异常或BMC异常，导致BIOS与BMC无法进行数据交互的问题。其具体方案如下：
第一方面，本申请提供了一种服务器BIOS与BMC之间的数据交互方法，应用于BIOS，包括：
S1、在服务器上电开机时，获取BIOS与BMC之间的IPMI链路的状态，得到第一状态值；若所述第一状态值为正常，进入S2，若所述第一状态值为异常，则进入S3；
S2、通过所述IPMI链路与所述BMC进行数据交互，引导启动到系统；
S3、初始化设备并引导启动至BDS阶段，再次获取所述BIOS与BMC之间的IPMI链路的状态，得到第二状态值；若所述第二状态值为正常，进入S2，若所述第二状态值为异常，则进入S4；
S4、判断所述服务器的重启次数是否超过预设阈值；若所述服务器的重启次数超过预设阈值，则进入S5，若所述服务器的重启次数未超过预设阈值，则进入S6；
S5、判定所述BMC异常，根据本地的预设内存地址空间上的目标数据进行自我恢复，引导启动到系统；
S6、执行重启命令控制所述服务器进行重启，进入S1。
优选的，在所述判定所述BMC异常之后，还包括：
通过串口输出BMC异常的提示信息。
优选的，所述执行重启命令控制所述服务器进行重启，进入S1，包括：
执行重启命令控制所述服务器进行重启，等待预设时间，进入S1。
优选的，所述通过所述IPMI链路与所述BMC进行数据交互，包括：
通过所述IPMI链路向所述BMC发送硬件设备信息，以显示所述硬件设备信息。
优选的，所述通过所述IPMI链路与所述BMC进行数据交互，包括：
通过所述IPMI链路从所述BMC获取目标功能的最新配置信息。
优选的，所述根据本地的预设内存地址空间上的目标数据进行自我恢复，包括：
从本地的预设内存地址空间读取NVRAM数据，得到目标功能的原有配置信息。
第二方面，本申请提供了一种服务器BIOS与BMC之间的数据交互装置，应用于BIOS，包括：
第一状态获取模块：用于在服务器上电开机时，获取BIOS与BMC之间的IPMI链路的状态，得到第一状态值；若所述第一状态值为正常，进入引导启动模块，若所述第一状态值为异常，则进入第二状态获取模块；
所述引导启动模块：用于通过所述IPMI链路与所述BMC进行数据交互，引导启动到系统；
所述第二状态获取模块：用于初始化设备并引导启动至BDS阶段，再次获取所述BIOS与BMC之间的IPMI链路的状态，得到第二状态值；若所述第二状态值为正常，进入所述引导启动模块，若所述第二状态值为异常，则进入重启判断模块；
所述重启判断模块：用于判断所述服务器的重启次数是否超过预设阈值；若所述服务器的重启次数超过预设阈值，则进入异常处理模块，若所述服务器的重启次数未超过预设阈值，则进入重启模块；
所述异常处理模块：用于判定所述BMC异常，根据本地的预设内存地址空间上的目标数据进行自我恢复，引导启动到系统；
所述重启模块：用于执行重启命令控制所述服务器进行重启，进 入所述第一状态获取模块。
优选的，所述异常处理模块还用于：
通过串口输出BMC异常的提示信息。
第三方面，本申请提供了一种服务器BIOS与BMC之间的数据交互设备，包括：
处理器：用于存储计算机程序；
处理器：用于执行所述计算机程序，以实现如上所述的服务器BIOS与BMC之间的数据交互方法。
第四方面，本申请提供了一种可读存储介质，所述可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时用于实现如上所述的服务器BIOS与BMC之间的数据交互方法。
本申请所提供的一种服务器BIOS与BMC之间的数据交互方法，应用于BIOS，包括：在服务器上电开机时，获取BIOS与BMC之间的IPMI链路的状态，得到第一状态值；若第一状态值为正常，则通过IPMI链路与BMC进行数据交互，引导启动到系统，若第一状态值为异常，则初始化设备并引导启动至BDS阶段，再次获取BIOS与BMC之间的IPMI链路的状态，得到第二状态值；若第二状态值为正常，则通过IPMI链路与BMC进行数据交互，引导启动到系统，若第二状态值为异常，则判断服务器的重启次数是否超过预设阈值；若服务器的重启次数超过预设阈值，判定BMC异常，根据本地的预设内存地址空间上的目标数据进行自我恢复，引导启动到系统，若服务器的重启次数未超过预设阈值，则执行重启命令控制所述服务器进行重启，重复上述步骤。
可见，该方法根据BIOS和BMC之间IPMI链路的状态来决定是否进行数据交互，同时，该方法通过在BIOS的BDS阶段确认服务器的重启次数是否达到预设阈值，判断BMC是否因存在异常导致无法激活，当服务器重启次数已经达到预设阈值且BMC仍未激活，则判定BMC异常，若服务器重启次数尚未达到预设阈值，则BIOS执行系统重启动作，其中预设阈值由BIOS内部自定义的变量确认，可以自 由设置。如此设计可以达到服务器BIOS和BMC安全有效的数据交互，避免因IPMI链路异常导致数据交互失败的问题，及时发现BMC异常状态，提升服务器的安全性和可靠性，适用于所有架构的服务器产品。
此外，本申请还提供了一种服务器BIOS与BMC之间的数据交互装置、设备及可读存储介质，其技术效果与上述方法的技术效果相对应，这里不再赘述。
附图说明
为了更清楚的说明本申请实施例或现有技术的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单的介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请所提供的一种服务器BIOS与BMC之间的数据交互方法实施例一的流程图；
图2为本申请所提供的一种服务器BIOS与BMC之间的数据交互方法实施例二的流程图；
图3为本申请所提供的一种服务器BIOS与BMC之间的数据交互装置实施例的功能框图；
图4为本申请所提供的一种服务器BIOS与BMC之间的数据交互设备实施例的结构示意图。
具体实施方式
本申请的核心是提供一种服务器BIOS与BMC之间的数据交互方法、装置、设备及可读存储介质，能够保证服务器BIOS和BMC安全有效的数据交互，避免因IPMI链路异常导致数据交互失败的问题，及时发现BMC异常状态，提升服务器的安全性和可靠性。
为了使本技术领域的人员更好地理解本申请方案，下面结合附图和具体实施方式对本申请作进一步的详细说明。显然，所描述的实施 例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
下面对本申请提供的一种服务器BIOS与BMC之间的数据交互方法实施例一进行介绍，参见图1，实施例一应用于BIOS，包括：
S101、在服务器上电开机时，获取BIOS与BMC之间的IPMI链路的状态，得到第一状态值；若第一状态值为正常，进入S102，若第一状态值为异常，则进入S103；
在服务器中，BIOS主要负责服务器硬件设备的初始化及操作系统的引导，BMC主要负责服务器各个部件的温度监控和能耗管理以及资产信息显示。在服务器初始化过程中，BIOS能够获取到服务器的硬件设备信息，但是BIOS无法显示服务器的硬件设备信息，BMC可以随时通过远程管理登陆查看服务器的硬件设备信息，这些硬件设备信息是BIOS通过IPMI链路传递给BMC进行显示的，因此服务器初始化过程中BIOS和BMC的数据交互过程必不可少。此外，BIOS的部分功能也需要与BMC进行数据交互，如通过IPMI命令进行启动项设置、看门狗时间设置、vlan等功能。
为了避免因IPMI链路异常导致BIOS和BMC无法进行数据交互，本实施例提供一种通用服务器BIOS和BMC安全有效交互数据方案。
首先，在服务器首次上电开机时，BIOS通过IPMI协议获取本地与BMC之间的IPMI链路的状态，根据IPMI协议反馈的状态值判断此时IPMI链路是否正常，若反馈的状态值为正常，则进入S102，按照默认的传输方式将BIOS和BMC间需要传输的数据进行交互设置及显示，正常引导启动至系统；若反馈的状态值为异常，则进入S103，放弃此时所有的数据交互内容，BIOS继续初始化其他设备至BDS(Boot Device Select，启动设备选择)阶段。
S102、通过所述IPMI链路与所述BMC进行数据交互，引导启动到系统；
如前文所述，BIOS和BMC之间的数据交互内容包括但不限于BIOS向BMC传递的硬件设备信息，BMC向BIOS传递的BIOS的部分功能的相关数据，例如功能的配置数据。因此，S102包括：通过所述IPMI链路向所述BMC发送硬件设备信息，以显示所述硬件设备信息；通过所述IPMI链路从所述BMC获取目标功能的最新配置信息。
S103、初始化设备并引导启动至BDS阶段，再次获取所述BIOS与BMC之间的IPMI链路的状态，得到第二状态值；若所述第二状态值为正常，进入S102，若所述第二状态值为异常，则进入S104；
在BIOS的BDS阶段再次检查BIOS和BMC之间的IPMI链路是否正常，若此时的状态值为正常，则进入S102，按照默认的传输方式将BIOS和BMC间需要传输的数据进行交互设置及显示，正常引导启动至系统；若此时的状态值为异常，放弃此时所有的数据交互内容，进入S104。
S104、判断所述服务器的重启次数是否超过预设阈值；若所述服务器的重启次数超过预设阈值，则进入S105，若所述服务器的重启次数未超过预设阈值，则进入S106；
一般的，导致IPMI链路异常的原因可能有以下几种：BIOS和BMC之间的IPMI链路在服务器开启时未正常初始化，或者物理链路损坏，或者IPMI协议未正常初始化，或者BMC异常。其中，BMC异常包括：BMC未正常初始化，或者BMC损坏。
具体的，当BDS阶段IPMI链路的状态仍为异常时，判断服务器/BIOS的重启次数是否达到预设阈值，如果服务器/BIOS的重启次数已经达到预设阈值，则认为已经排除其他可能导致IPMI链路异常的原因，判定BMC异常，进入S105；如果服务器/BIOS的重启次数尚未达到预设阈值，则进入S106，BIOS通过执行系统重启命令让服务器进行重新启动，然后回到S101，重复前述步骤。
值得一提的是，BMC从主板第一次上电或者断电重启到激活的时间默认是60秒，而BIOS的启动时间则是40秒，所以在执行重启之后，BIOS可以等待一段时间，等到BMC已经处于激活状态时，再进 入S101。可以理解的是，此处的等待时间不小于20秒。
S105、判定所述BMC异常，根据本地的预设内存地址空间上的目标数据进行自我恢复，引导启动到系统；
如前文所述，BIOS的部分功能也需要与BMC进行数据交互，当判定BMC异常时，BIOS无法从BMC获取这些功能的相关数据，影响启动过程的顺利进行。为避免这种情况，本实施例中BIOS通过前期存储在预设内存地址空间的数据(即NVRAM变量)进行自我恢复机制，获取到这些功能的原有数据，不再从BMC获取这些功能的最新数据，因此可不受BMC传递参数的限制，继续引导启动到系统。
此外，此时还可以通过BIOS的串口打印出BMC已损坏或未激活的状态信息。
S106、执行重启命令控制所述服务器进行重启，进入S101。
本实施例提供一种服务器BIOS与BMC之间的数据交互方法，根据BIOS和BMC之间IPMI链路的状态来决定是否进行数据交互，在开机时确认一次链路状态，若链路状态正常，则执行BIOS和BMC的数据交互，若链路状态异常，则BIOS放弃数据交互，继续引导启动至BDS阶段再次确认链路状态，若再次确认链路状态正常，则执行BIOS和BMC的数据交互，若再次确认链路状态异常，则判断服务器的重启次数是否达到预设阈值，若服务器的重启次数未达到预设阈值，则进行重启动作，然后依次重复前述动作，若服务器的重启次数已经达到预设阈值，则判定BMC异常，BIOS根据预设内存地址空间上的目标数据进行自我恢复，引导启动到系统。
本实施例具有很强的可复制性和拓展性，利用BIOS和BMC的交互协议IPMI协议确认链路状态，然后BIOS根据IPMI协议返回的状态值来确认后续的执行动作，极大提高了服务器的可靠性和安全性，还可以通过系统重启的时间消耗满足BMC激活的时间限制要求，对于数据中心服务器的批量部署和应用提供了可靠性，本实施例不受服务器芯片架构的限制，适用多种不同架构的服务器产品，符合服务器技术未来发展趋势。
下面开始详细介绍本申请提供的一种服务器BIOS与BMC之间的数据交互方法实施例二，参见图2，实施例二具体包括：
第一步，任意架构服务器主板上电后，BIOS启动先去通过IPMI协议检查与BMC之间的链路是否正常，若BIOS链路与BMC之间的链路正常，则BIOS通过IPMI协议与BMC进行数据交互及传递，正常引导启动到系统。
第二步，若BIOS链路与BMC之间的链路异常，则此时BIOS不会进行IPMI协议数据传输，然后BIOS进行设备初始化及启动，待启动到BIOS的BDS阶段时，BIOS再通过IPMI协议检查与BMC通信之间的链路是否正常，若BIOS链路与BMC之间的链路正常，则BIOS通过IPMI协议与BMC进行数据交互及传递，正常引导启动到系统。
第三步，若BIOS链路与BMC之间的链路仍异常，判断重启次数是否达到预设阈值，若重启次数没有达到预设阈值，则BIOS执行系统重启命令，等待时间让BMC激活，继续执行第一步和第二步。
第四步，若重启次数已经达到预设阈值，BMC仍未激活或BMC损坏导致IPMI链路无法使用，则BIOS通过BIOS内部的NVRAM变量恢复需要从BMC获取数据的信息，同时BIOS通过串口输出BMC未激活或损坏的告警信息。
下面对本申请实施例提供的一种服务器BIOS与BMC之间的数据交互装置进行介绍，下文描述的一种服务器BIOS与BMC之间的数据交互装置与上文描述的一种服务器BIOS与BMC之间的数据交互方法可相互对应参照。
如图3所示，本实施例的服务器BIOS与BMC之间的数据交互装置，应用于BIOS，包括：
第一状态获取模块301：用于在服务器上电开机时，获取BIOS与BMC之间的IPMI链路的状态，得到第一状态值；若所述第一状态值为正常，进入引导启动模块302，若所述第一状态值为异常，则进 入第二状态获取模块303；
所述引导启动模块302：用于通过所述IPMI链路与所述BMC进行数据交互，引导启动到系统；
所述第二状态获取模块303：用于初始化设备并引导启动至BDS阶段，再次获取所述BIOS与BMC之间的IPMI链路的状态，得到第二状态值；若所述第二状态值为正常，进入所述引导启动模块302，若所述第二状态值为异常，则进入重启判断模块304；
所述重启判断模块304：用于判断所述服务器的重启次数是否超过预设阈值；若所述服务器的重启次数超过预设阈值，则进入异常处理模块305，若所述服务器的重启次数未超过预设阈值，则进入重启模块306；
所述异常处理模块305：用于判定所述BMC异常，根据本地的预设内存地址空间上的目标数据进行自我恢复，引导启动到系统；
所述重启模块306：用于执行重启命令控制所述服务器进行重启，进入所述第一状态获取模块301。
在一些具体的实施例中，所述异常处理模块还用于：
通过串口输出BMC异常的提示信息。
本实施例的服务器BIOS与BMC之间的数据交互装置用于实现前述的服务器BIOS与BMC之间的数据交互方法，因此该装置中的具体实施方式可见前文中的服务器BIOS与BMC之间的数据交互方法的实施例部分，例如，第一状态获取模块301、引导启动模块302、第二状态获取模块303、重启判断模块304、异常处理模块305、重启模块306，分别用于实现上述服务器BIOS与BMC之间的数据交互方法中步骤S101，S102，S103，S104，S105，S106。所以，其具体实施方式可以参照相应的各个部分实施例的描述，在此不再展开介绍。
另外，由于本实施例的服务器BIOS与BMC之间的数据交互装置用于实现前述的服务器BIOS与BMC之间的数据交互方法，因此其作用与上述方法的作用相对应，这里不再赘述。
此外，本申请还提供了一种服务器BIOS与BMC之间的数据交互设备，如图4所示，包括：
处理器100：用于存储计算机程序；
处理器200：用于执行所述计算机程序，以实现如上文所述的服务器BIOS与BMC之间的数据交互方法。
最后，本申请提供了一种可读存储介质，所述可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时用于实现如上文所述的服务器BIOS与BMC之间的数据交互方法。
本说明书中各个实施例采用递进的方式描述，每个实施例重点说明的都是与其它实施例的不同之处，各个实施例之间相同或相似部分互相参见即可。对于实施例公开的装置而言，由于其与实施例公开的方法相对应，所以描述的比较简单，相关之处参见方法部分说明即可。
结合本文中所公开的实施例描述的方法或算法的步骤可以直接用硬件、处理器执行的软件模块，或者二者的结合来实施。软件模块可以置于随机存储器(RAM)、内存、只读存储器(ROM)、电可编程ROM、电可擦除可编程ROM、寄存器、硬盘、可移动磁盘、CD-ROM、或技术领域内所公知的任意其它形式的存储介质中。
以上对本申请所提供的方案进行了详细介绍，本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的一般技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (10)

  1. 一种服务器BIOS与BMC之间的数据交互方法，其特征在于，应用于BIOS，包括：
    S1、在服务器上电开机时，获取BIOS与BMC之间的IPMI链路的状态，得到第一状态值；若所述第一状态值为正常，进入S2，若所述第一状态值为异常，则进入S3；
    S2、通过所述IPMI链路与所述BMC进行数据交互，引导启动到系统；
    S3、初始化设备并引导启动至BDS阶段，再次获取所述BIOS与BMC之间的IPMI链路的状态，得到第二状态值；若所述第二状态值为正常，进入S2，若所述第二状态值为异常，则进入S4；
    S4、判断所述服务器的重启次数是否超过预设阈值；若所述服务器的重启次数超过预设阈值，则进入S5，若所述服务器的重启次数未超过预设阈值，则进入S6；
    S5、判定所述BMC异常，根据本地的预设内存地址空间上的目标数据进行自我恢复，引导启动到系统；
    S6、执行重启命令控制所述服务器进行重启，进入S1。
  2. 如权利要求1所述的方法，其特征在于，在所述判定所述BMC异常之后，还包括：
    通过串口输出BMC异常的提示信息。
  3. 如权利要求1所述的方法，其特征在于，所述执行重启命令控制所述服务器进行重启，进入S1，包括：
    执行重启命令控制所述服务器进行重启，等待预设时间，进入S1。
  4. 如权利要求1所述的方法，其特征在于，所述通过所述IPMI链路与所述BMC进行数据交互，包括：
    通过所述IPMI链路向所述BMC发送硬件设备信息，以显示所述硬件设备信息。
  5. 如权利要求1所述的方法，其特征在于，所述通过所述IPMI链路与所述BMC进行数据交互，包括：
    通过所述IPMI链路从所述BMC获取目标功能的最新配置信息。
  6. 如权利要求5所述的方法，其特征在于，所述根据本地的预设内存地址空间上的目标数据进行自我恢复，包括：
    从本地的预设内存地址空间读取NVRAM数据，得到目标功能的原有配置信息。
  7. 一种服务器BIOS与BMC之间的数据交互装置，其特征在于，应用于BIOS，包括：
    第一状态获取模块：用于在服务器上电开机时，获取BIOS与BMC之间的IPMI链路的状态，得到第一状态值；若所述第一状态值为正常，进入引导启动模块，若所述第一状态值为异常，则进入第二状态获取模块；
    所述引导启动模块：用于通过所述IPMI链路与所述BMC进行数据交互，引导启动到系统；
    所述第二状态获取模块：用于初始化设备并引导启动至BDS阶段，再次获取所述BIOS与BMC之间的IPMI链路的状态，得到第二状态值；若所述第二状态值为正常，进入所述引导启动模块，若所述第二状态值为异常，则进入重启判断模块；
    所述重启判断模块：用于判断所述服务器的重启次数是否超过预设阈值；若所述服务器的重启次数超过预设阈值，则进入异常处理模块，若所述服务器的重启次数未超过预设阈值，则进入重启模块；
    所述异常处理模块：用于判定所述BMC异常，根据本地的预设内存地址空间上的目标数据进行自我恢复，引导启动到系统；
    所述重启模块：用于执行重启命令控制所述服务器进行重启，进入所述第一状态获取模块。
  8. 如权利要求7所述的装置，其特征在于，所述异常处理模块还用于：
    通过串口输出BMC异常的提示信息。
  9. 一种服务器BIOS与BMC之间的数据交互设备，其特征在于，包括：
    处理器：用于存储计算机程序；
    处理器：用于执行所述计算机程序，以实现如权利要求1至6任意一项所述的服务器BIOS与BMC之间的数据交互方法。
  10. 一种可读存储介质，其特征在于，所述可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时用于实现如权利要求1至6任意一项所述的服务器BIOS与BMC之间的数据交互方法。
PCT/CN2021/121222 2020-11-11 2021-09-28 一种服务器bios与bmc之间的数据交互方法、装置及设备 Ceased WO2022100307A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/034,057 US11907073B2 (en) 2020-11-11 2021-09-28 Method and apparatus for data interaction between BIOS and BMC of server, and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011254073.5A CN112463222A (zh) 2020-11-11 2020-11-11 一种服务器bios与bmc之间的数据交互方法、装置及设备
CN202011254073.5 2020-11-11

Publications (1)

Publication Number Publication Date
WO2022100307A1 true WO2022100307A1 (zh) 2022-05-19

Family

ID=74826784

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/121222 Ceased WO2022100307A1 (zh) 2020-11-11 2021-09-28 一种服务器bios与bmc之间的数据交互方法、装置及设备

Country Status (3)

Country Link
US (1) US11907073B2 (zh)
CN (1) CN112463222A (zh)
WO (1) WO2022100307A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115952065A (zh) * 2022-12-16 2023-04-11 西安超越申泰信息科技有限公司 一种bmc传感器信息展示的方法、系统、设备和存储介质

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112463222A (zh) 2020-11-11 2021-03-09 苏州浪潮智能科技有限公司 一种服务器bios与bmc之间的数据交互方法、装置及设备
CN113010217B (zh) * 2021-03-18 2023-04-07 山东英信计算机技术有限公司 一种bios参数设置方法、装置、电子设备及存储介质
CN113867812B (zh) * 2021-08-30 2023-08-04 苏州浪潮智能科技有限公司 一种bmc获取链路信息的方法、系统、设备以及介质
CN113986357B (zh) * 2021-09-23 2023-08-11 苏州浪潮智能科技有限公司 建立通信链路的方法、装置和存储介质
CN114048101A (zh) * 2021-11-17 2022-02-15 珠海格力电器股份有限公司 服务器的监测方法、监测装置以及监测系统
CN114489818A (zh) * 2021-12-30 2022-05-13 中电科技(北京)股份有限公司 一种基于bios的bmc配置方法和装置
CN114428963B (zh) * 2022-04-06 2022-07-08 浪潮(山东)计算机科技有限公司 一种服务器启动方法、装置、设备及存储介质
CN115576747B (zh) * 2022-11-21 2023-06-16 苏州浪潮智能科技有限公司 基板管理控制器固件故障恢复方法、系统、设备及介质
CN116723084B (zh) * 2023-06-14 2025-12-19 苏州元脑智能科技有限公司 Pcie链路故障修复方法、装置、电子设备及存储介质
CN117632569B (zh) * 2024-01-12 2024-04-12 宝德计算机系统股份有限公司 一种bmc网页端pci设备信息缺失的补救方法及其装置
CN117873853B (zh) * 2024-03-13 2024-05-28 苏州元脑智能科技有限公司 数据记录方法、装置、电子设备及介质
CN118245292B (zh) * 2024-05-28 2024-08-09 苏州元脑智能科技有限公司 服务器的重启方法、装置、存储介质及服务器
CN118426850A (zh) * 2024-07-05 2024-08-02 济南浪潮数据技术有限公司 信息交互方法、计算机装置、存储介质和程序
CN119218031B (zh) * 2024-08-15 2025-09-19 国网智慧车联网技术有限公司 一种充电系统和方法
CN119621157B (zh) * 2024-11-06 2025-09-26 武汉长江计算科技有限公司 一种ai服务器操作系统故障检测和恢复的方法和装置
CN120994454B (zh) * 2025-10-23 2026-03-03 苏州元脑智能科技有限公司 信息交互优化方法和电子设备

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130132700A1 (en) * 2011-07-21 2013-05-23 Huawei Technologies Co., Ltd. Method and system for dynamically upgrading a chip and baseboard management controller
CN104615506A (zh) * 2015-02-13 2015-05-13 浪潮电子信息产业股份有限公司 一种基于逻辑控制的bios和bmc备份方法
CN106201799A (zh) * 2016-07-14 2016-12-07 浪潮电子信息产业股份有限公司 一种基于ipmi服务对服务器进行DC重启的测试方法
CN106681878A (zh) * 2017-01-05 2017-05-17 郑州云海信息技术有限公司 一种pcie通道带宽的测试方法
CN106933710A (zh) * 2017-02-19 2017-07-07 郑州云海信息技术有限公司 基于wol功能对服务器进行dc重启的测试方法
CN109240851A (zh) * 2018-08-24 2019-01-18 郑州云海信息技术有限公司 一种自主式实现批量bmc自恢复的方法及系统
CN110908847A (zh) * 2019-11-22 2020-03-24 苏州浪潮智能科技有限公司 一种异常恢复方法、系统、电子设备及存储介质
CN112463222A (zh) * 2020-11-11 2021-03-09 苏州浪潮智能科技有限公司 一种服务器bios与bmc之间的数据交互方法、装置及设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9569324B2 (en) * 2014-11-20 2017-02-14 Dell Products, Lp System and method for reducing boot time of a workload configuration on a target server
US9921915B2 (en) * 2015-10-16 2018-03-20 Quanta Computer Inc. Baseboard management controller recovery
JP6946867B2 (ja) * 2017-09-01 2021-10-13 富士通株式会社 情報処理装置、管理装置およびプログラム
US10846160B2 (en) * 2018-01-12 2020-11-24 Quanta Computer Inc. System and method for remote system recovery
US11126517B2 (en) * 2019-05-14 2021-09-21 Quanta Computer Inc. Method and system for communication channels to management controller
US11226919B1 (en) * 2020-06-23 2022-01-18 Amazon Technologies, Inc. Communication link recovery

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130132700A1 (en) * 2011-07-21 2013-05-23 Huawei Technologies Co., Ltd. Method and system for dynamically upgrading a chip and baseboard management controller
CN104615506A (zh) * 2015-02-13 2015-05-13 浪潮电子信息产业股份有限公司 一种基于逻辑控制的bios和bmc备份方法
CN106201799A (zh) * 2016-07-14 2016-12-07 浪潮电子信息产业股份有限公司 一种基于ipmi服务对服务器进行DC重启的测试方法
CN106681878A (zh) * 2017-01-05 2017-05-17 郑州云海信息技术有限公司 一种pcie通道带宽的测试方法
CN106933710A (zh) * 2017-02-19 2017-07-07 郑州云海信息技术有限公司 基于wol功能对服务器进行dc重启的测试方法
CN109240851A (zh) * 2018-08-24 2019-01-18 郑州云海信息技术有限公司 一种自主式实现批量bmc自恢复的方法及系统
CN110908847A (zh) * 2019-11-22 2020-03-24 苏州浪潮智能科技有限公司 一种异常恢复方法、系统、电子设备及存储介质
CN112463222A (zh) * 2020-11-11 2021-03-09 苏州浪潮智能科技有限公司 一种服务器bios与bmc之间的数据交互方法、装置及设备

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115952065A (zh) * 2022-12-16 2023-04-11 西安超越申泰信息科技有限公司 一种bmc传感器信息展示的方法、系统、设备和存储介质

Also Published As

Publication number Publication date
US11907073B2 (en) 2024-02-20
CN112463222A (zh) 2021-03-09
US20230393944A1 (en) 2023-12-07

Similar Documents

Publication Publication Date Title
WO2022100307A1 (zh) 一种服务器bios与bmc之间的数据交互方法、装置及设备
JP6383839B2 (ja) リモートｋｖｍセッションに使用する方法、記憶装置及びシステム
US20090217072A1 (en) Automated electrical power savings in virtualization environments
US6763456B1 (en) Self correcting server with automatic error handling
TWI436588B (zh) 電源鎖定的設定方法及其電子裝置
US9152492B2 (en) Performing recovery of a headless computer
TWI668567B (zh) 伺服器及自動檢修基板管理控制器的方法
KR100831117B1 (ko) 컴퓨터에 대한 자동기술지원 방법 및 시스템
CN109766110B (zh) 一种控制方法、基板管理控制器及控制系统
CN110764829B (zh) 一种多路服务器cpu隔离方法及系统
WO2026066507A1 (zh) 服务器设备的启动方法及装置
CN117436090B (zh) 一种启动校验系统、方法、电子设备及存储介质
CN111352662B (zh) 一种服务器启动顺序控制方法、系统、终端及存储介质
CN116627702A (zh) 虚拟机的宕机重启方法及装置
CN1074148C (zh) 具有检错处理功能的数据处理系统
JP7830584B2 (ja) クロスドメインアクセス方法、装置、機器及び媒体
WO2025246557A1 (zh) 服务器的重启方法、装置、存储介质及服务器
WO2025113286A1 (zh) 故障处理方法、装置和可读存储介质
CN117331723B (zh) 应用于arm服务器的arm安全固件配置方法及装置
JP7389877B2 (ja) ネットワークの最適なブートパスの方法及びシステム
CN108073481B (zh) 可提供硬件运作信息的服务器系统及其处理方法
TW201324115A (zh) 電腦系統及電腦系統的開機管理方法
CN110795293B (zh) 一种服务器软关机的测试方法、系统及装置
CN115756648A (zh) 一种双基板管理控制器芯片的主动恢复方法及终端
CN116361114A (zh) 一种ai板卡监控保活方法、装置、设备及介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21890835

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18034057

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21890835

Country of ref document: EP

Kind code of ref document: A1