CN113778756A - Fault recovery method, device, equipment and medium for BMC (baseboard management controller) firmware - Google Patents
Fault recovery method, device, equipment and medium for BMC (baseboard management controller) firmware Download PDFInfo
- Publication number
- CN113778756A CN113778756A CN202111088585.3A CN202111088585A CN113778756A CN 113778756 A CN113778756 A CN 113778756A CN 202111088585 A CN202111088585 A CN 202111088585A CN 113778756 A CN113778756 A CN 113778756A
- Authority
- CN
- China
- Prior art keywords
- bmc firmware
- target
- standby
- boot
- firmware
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 71
- 238000011084 recovery Methods 0.000 title claims abstract description 69
- 238000004891 communication Methods 0.000 claims abstract description 33
- 238000004590 computer program Methods 0.000 claims description 10
- 230000008569 process Effects 0.000 abstract description 13
- 238000012423 maintenance Methods 0.000 abstract description 9
- 238000010586 diagram Methods 0.000 description 6
- 230000009286 beneficial effect Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 239000011449 brick Substances 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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 operation
- 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; CALCULATING OR 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 operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a fault recovery method, a fault recovery device, equipment and a medium for BMC firmware, wherein the method comprises the following steps: when the target BMC firmware fails, establishing communication connection with the target BMC firmware, and judging whether a target U-boot in the target BMC firmware can be started normally; if so, starting the standby BMC firmware stored in the mobile storage equipment by using the target U-boot; if not, burning the standby U-boot stored in the mobile storage device to the target BMC firmware, and starting the standby BMC firmware by using the standby U-boot; and when the standby BMC firmware is started, refreshing the target BMC firmware by using the standby BMC firmware. Due to the fact that the method can avoid a complicated burning process when the BMC firmware is subjected to fault recovery by using a chip burner, the working efficiency of maintenance personnel can be remarkably improved when the BMC firmware is subjected to fault recovery by using the method.
Description
Technical Field
The invention relates to the technical field of servers, in particular to a fault recovery method, a fault recovery device, fault recovery equipment and a fault recovery medium for BMC firmware.
Background
With the continuous development of internet technology, the market of the server is prosperous. In this technical context, a large amount of data storage, computation and interaction all need to be supported by a server. In the using process of the server, a fault may occur in the BMC (Baseboard Management Controller) firmware inside the server, and in this case, the server cannot normally use the network to update the firmware due to a problem in the BMC firmware, which may cause the BMC firmware to fail to operate normally, commonly called BMC brick change.
In the prior art, in order to perform fault recovery on the BMC, a chip burner is usually used to burn related programs into the BMC firmware again, but this fault recovery method for the BMC firmware not only needs to disassemble the server, but also needs to manually weld the chip, which is huge and complicated in workload, and greatly reduces the work efficiency of maintenance personnel. At present, no effective solution exists for the technical problem.
Disclosure of Invention
In view of this, an object of the present invention is to provide a method, an apparatus, a device and a medium for fault recovery of BMC firmware, so as to improve the work efficiency of a maintenance worker when performing fault recovery of BMC firmware. The specific scheme is as follows:
a fault recovery method of BMC firmware is applied to a mobile storage device and comprises the following steps:
when the target BMC firmware fails, establishing communication connection with the target BMC firmware, and judging whether a target U-boot in the target BMC firmware can be started normally;
if the target U-boot can be started normally, starting the standby BMC firmware stored in the mobile storage device by using the target U-boot;
if the target U-boot cannot be started normally, burning the standby U-boot stored in the mobile storage device to the target BMC firmware, and starting the standby BMC firmware stored in the mobile storage device by using the standby U-boot;
and when the standby BMC firmware is started, refreshing the target BMC firmware by using the standby BMC firmware so as to recover the fault of the target BMC firmware.
Preferably, the method further comprises the following steps:
and when the target BMC firmware does not respond to the target control instruction and the reset instruction, judging that the target BMC firmware fails.
Preferably, the process of establishing a communication connection with the target BMC firmware when the target BMC firmware fails includes:
and when the target BMC firmware in the Power server fails, establishing communication connection with the target BMC firmware.
Preferably, the process of establishing a communication connection with the target BMC firmware when the target BMC firmware fails includes:
when the target BMC firmware in the X86 server fails, a communication connection is established with the target BMC firmware.
Preferably, the method further comprises the following steps:
and when the fault of the target BMC firmware is recovered, disconnecting the communication connection with the target BMC firmware.
Preferably, the mobile storage device is specifically a usb disk or a memory card.
Correspondingly, the invention also discloses a fault recovery device of the BMC firmware, which is applied to the mobile storage equipment and comprises the following components:
the starting judgment module is used for establishing communication connection with the target BMC firmware when the target BMC firmware fails and judging whether a target U-boot in the target BMC firmware can be started normally or not;
the first judgment module is used for starting the standby BMC firmware stored in the mobile storage device by using the target U-boot if the target U-boot can be started normally;
the second judgment module is used for burning the standby U-boot stored in the mobile storage device to the target BMC firmware and starting the standby BMC firmware stored in the mobile storage device by using the standby U-boot if the target U-boot cannot be started normally;
and the fault recovery module is used for refreshing the target BMC firmware by using the standby BMC firmware when the standby BMC firmware is started so as to recover the fault of the target BMC firmware.
Correspondingly, the invention also discloses a fault recovery device of the BMC firmware, which comprises:
a memory for storing a computer program;
a processor for implementing the steps of a method for fault recovery of BMC firmware as disclosed in the foregoing when executing the computer program.
Accordingly, the present invention also discloses a computer readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the fault recovery method for BMC firmware as disclosed in the foregoing.
In the invention, when the target BMC firmware has a fault, the mobile storage device firstly establishes communication connection with the target BMC firmware and judges whether a target U-boot in the target BMC firmware can be normally started or not, and if the target U-boot can be normally started, the target U-boot is utilized to start the standby BMC firmware stored in the mobile storage device; if the target U-boot cannot be started normally, burning the standby U-boot stored in the mobile storage device into the target BMC firmware, and starting the standby BMC firmware stored in the mobile storage device by using the standby U-boot; and when the standby BMC firmware is started, refreshing the target BMC by using the standby BMC firmware, and recovering the fault of the target BMC firmware. Compared with the prior art, the method can avoid a complicated burning process when the BMC firmware is subjected to fault recovery by using a chip burner, so that the working efficiency of maintenance personnel during the fault recovery of the BMC firmware can be obviously improved by the method. Correspondingly, the fault recovery device, equipment and medium of the BMC firmware have the beneficial effects.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a method for recovering a fault of BMC firmware according to an embodiment of the present invention;
fig. 2 is a schematic diagram illustrating information interaction between BMC firmware and a mobile storage device according to an embodiment of the present invention;
fig. 3 is a structural diagram of a fault recovery apparatus for BMC firmware according to an embodiment of the present invention;
fig. 4 is a structural diagram of a fault recovery device of BMC firmware according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, fig. 1 is a flowchart of a fault recovery method for BMC firmware according to an embodiment of the present invention, where the fault recovery method includes:
step S11: when the target BMC firmware fails, establishing communication connection with the target BMC firmware, and judging whether a target U-boot in the target BMC firmware can be started normally;
step S12: if the target U-boot can be started normally, starting the standby BMC firmware stored in the mobile storage device by using the target U-boot;
step S13: if the target U-boot cannot be started normally, burning the standby U-boot stored in the mobile storage device to the target BMC firmware, and starting the standby BMC firmware stored in the mobile storage device by using the standby U-boot;
step S14: and when the standby BMC firmware is started, refreshing the target BMC firmware by using the standby BMC firmware so as to recover the fault of the target BMC firmware.
In this embodiment, a fault recovery method for a BMC is provided, and when fault recovery is performed on BMC firmware by using the method, the work efficiency of a maintenance worker during fault recovery of the BMC firmware can be greatly improved. The failure recovery method is specifically described with a mobile storage device as an execution subject. It should be noted that, in the failure recovery method provided in this embodiment, a standby U-boot that matches the target U-boot stored in the target BMC firmware and a standby BMC firmware that matches the target BMC firmware need to be stored in the mobile storage device in advance.
Referring to fig. 2, fig. 2 is a schematic diagram illustrating information interaction between the BMC firmware and the mobile storage device according to an embodiment of the present invention. When the target BMC firmware fails, it indicates that the target BMC firmware cannot refresh itself by using a normal network, and in this case, a communication connection is first established between the mobile storage device and the target BMC firmware.
After the mobile storage device establishes communication connection with the target BMC firmware, judging whether a target U-boot stored in the target BMC firmware can be started normally by using the mobile storage device; because the target U-boot stored in the target BMC firmware is a boot loader, if the target U-boot can be started normally, the target U-boot can be used for booting the standby BMC firmware stored in the mobile storage device to start; if the target U-boot cannot be started normally, it indicates that the target U-boot stored in the target BMC firmware cannot guide the standby BMC firmware stored in the mobile storage device to start, at this time, the standby U-boot stored in the mobile storage device needs to be burned into the target BMC firmware, and the standby BMC firmware stored in the mobile storage device is started by using the standby U-boot.
When the standby BMC firmware is started, the target BMC firmware is indicated to restore network communication, and the standby BMC firmware is used for refreshing the target BMC firmware. It can be thought that when the target BMC firmware finishes refreshing itself, the target BMC firmware can normally operate, and the recovery process of the fault is completed.
Compared with the prior art, the fault recovery method for the BMC firmware can be realized only by rewriting the related program into the BMC firmware by using the programmer chip, and the complicated process that a maintenance worker removes the server and manually welds the chip can be avoided by using the fault recovery method provided by the embodiment, so that the working efficiency of the maintenance worker in fault recovery of the BMC firmware can be remarkably improved by using the method provided by the embodiment.
In this embodiment, when the target BMC firmware fails, the mobile storage device first establishes a communication connection with the target BMC firmware, and determines whether the target U-boot in the target BMC firmware can be normally started, and if the target U-boot can be normally started, the target U-boot is used to start the standby BMC firmware stored in the mobile storage device; if the target U-boot cannot be started normally, burning the standby U-boot stored in the mobile storage device into the target BMC firmware, and starting the standby BMC firmware stored in the mobile storage device by using the standby U-boot; and when the standby BMC firmware is started, refreshing the target BMC by using the standby BMC firmware, and recovering the fault of the target BMC firmware. Compared with the prior art, the method can avoid a complicated burning process when the BMC firmware is subjected to fault recovery by using a chip burner, so that the working efficiency of maintenance personnel during the fault recovery of the BMC firmware can be obviously improved by the method.
Based on the foregoing embodiment, this embodiment further describes and optimizes the technical solution, and as a preferred implementation, the fault recovery method further includes:
and when the target BMC firmware does not respond to the target control instruction and the reset instruction, judging that the target BMC firmware fails.
In this embodiment, a method for determining a fault of the target BMC firmware is provided, that is, if the target BMC firmware does not respond to both the target control instruction and the reset instruction sent by the server, it indicates that the target BMC firmware has a fault. The target control instruction refers to all control instructions sent by the server to the target BMC firmware, such as: program control instructions, interrupt instructions, start instructions, and run termination instructions, among others.
Obviously, the technical scheme provided by the embodiment can ensure the accuracy and reliability of the target BMC fault judgment result.
Based on the above embodiments, this embodiment further describes and optimizes the technical solution, and as a preferred implementation, the above steps: when the target BMC firmware fails, establishing communication connection with the target BMC firmware, wherein the process comprises the following steps:
and when the target BMC firmware in the Power server fails, establishing communication connection with the target BMC firmware.
It can be understood that, because the Power (Performance Optimization With Enhanced RISC, RISC architecture based instruction set architecture) server not only has good data processing Performance, but also has strong extensibility, the Power server is widely applied to many network workstations and supercomputers, and the BMC firmware is a core device for data processing of the Power server, so the fault recovery method of the BMC firmware provided by this embodiment can be applied to an application scenario including the Power server.
Obviously, by the technical scheme provided by the embodiment, the universality of the fault recovery method for the BMC firmware provided by the present application in practical application can be further improved.
Based on the above embodiments, this embodiment further describes and optimizes the technical solution, and as a preferred implementation, the above steps: when the target BMC firmware fails, establishing communication connection with the target BMC firmware, wherein the process comprises the following steps:
when the target BMC firmware in the X86 server fails, a communication connection is established with the target BMC firmware.
In practical applications, besides the fault recovery method for the BMC firmware provided by the present application may be applied to a Power server, the fault recovery method for the BMC firmware provided by the present application may also be applied to an X86 server. In the X86 server, the BMC firmware can not only monitor the operating conditions of the devices such as temperature, voltage, fan, power supply, etc. in the X86 server in real time, but also regulate and control various electronic devices in the X86 server, so that the X86 server is in a healthy operating state, and therefore, the BMC firmware plays an extremely important role in the X86 server. In this context, the fault recovery method for BMC firmware provided by the present application can be applied to an X86 server containing BMC firmware to further improve the operation performance of the X86 server.
Obviously, the flexibility of the fault recovery method for the BMC firmware provided by the present application in the actual use process can be further increased through the technical scheme provided by the present embodiment.
Based on the foregoing embodiment, this embodiment further describes and optimizes the technical solution, and as a preferred implementation, the fault recovery method further includes:
and when the fault of the target BMC firmware is recovered, disconnecting the communication connection with the target BMC firmware.
It is conceivable that, after the failure of the target BMC firmware is recovered, the target BMC firmware may execute a normal operation procedure in the server, in which case, the mobile storage device that establishes a communication connection with the target BMC firmware is disabled. At this time, if the mobile storage device continues to be in communication connection with the target BMC firmware, unnecessary waste of communication resources is caused. Therefore, in this embodiment, in order to avoid the above situation, after the failure of the target BMC firmware is recovered, the communication connection between the mobile storage device and the target BMC firmware is disconnected.
Obviously, by the technical scheme provided by the embodiment, the waste of the communication resources of the target BMC firmware can be reduced, and the utilization rate of the communication resources can be improved.
Based on the above embodiments, this embodiment further describes and optimizes the technical solution, and as a preferred implementation, the mobile storage device is specifically a usb disk or a memory card.
In practical application, the mobile storage device can be set as a USB flash disk, and the USB flash disk is small in size and convenient to carry, has the advantages of large storage capacity, low price, reliable performance and the like, so that when the mobile storage device is set as the USB flash disk, the convenience of maintenance personnel in fault recovery of the target BMC firmware can be further improved.
Alternatively, the removable storage device may be configured as a memory card, because the memory card not only has the advantages of small size and small power consumption, but also has a lower cost compared to other types of removable storage devices, when the removable storage device is configured as a memory card, the capital cost required to be invested in performing fault recovery on the target BMC firmware can be relatively reduced.
Referring to fig. 3, fig. 3 is a structural diagram of a failure recovery apparatus of BMC firmware according to an embodiment of the present invention, where the failure recovery apparatus includes:
the starting judgment module 21 is configured to establish a communication connection with the target BMC firmware when the target BMC firmware fails, and judge whether a target U-boot in the target BMC firmware can be started normally;
the first judging module 22 is configured to start the standby BMC firmware stored in the mobile storage device by using the target U-boot if the target U-boot can be started normally;
the second judging module 23 is configured to, if the target U-boot cannot be started normally, burn the standby U-boot stored in the mobile storage device to the target BMC firmware, and start the standby BMC firmware stored in the mobile storage device by using the standby U-boot;
and the fault recovery module 24 is configured to, when the standby BMC firmware is started, refresh the target BMC firmware by using the standby BMC firmware, so as to recover the fault of the target BMC firmware.
The fault recovery device for the BMC firmware provided by the embodiment of the invention has the beneficial effects of the fault recovery method for the BMC firmware disclosed by the embodiment of the invention.
Referring to fig. 4, fig. 4 is a structural diagram of a fault recovery device of BMC firmware according to an embodiment of the present invention, where the fault recovery device includes:
a memory 31 for storing a computer program;
a processor 32 for implementing the steps of a method for fault recovery of BMC firmware as disclosed above when executing a computer program.
The fault recovery device of the BMC firmware provided by the embodiment of the invention has the beneficial effects of the fault recovery method of the BMC firmware disclosed by the embodiment of the invention.
Accordingly, an embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method for recovering a fault of the BMC firmware disclosed in the foregoing are implemented.
The computer-readable storage medium provided by the embodiment of the invention has the beneficial effects of the fault recovery method for the BMC firmware disclosed in the foregoing.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The method, the apparatus, the device and the medium for fault recovery of BMC firmware provided by the present invention are described in detail above, and a specific example is applied in the description to explain the principle and the implementation of the present invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (9)
1. A fault recovery method of BMC firmware is applied to a mobile storage device and comprises the following steps:
when the target BMC firmware fails, establishing communication connection with the target BMC firmware, and judging whether a target U-boot in the target BMC firmware can be started normally;
if the target U-boot can be started normally, starting the standby BMC firmware stored in the mobile storage device by using the target U-boot;
if the target U-boot cannot be started normally, burning the standby U-boot stored in the mobile storage device to the target BMC firmware, and starting the standby BMC firmware stored in the mobile storage device by using the standby U-boot;
and when the standby BMC firmware is started, refreshing the target BMC firmware by using the standby BMC firmware so as to recover the fault of the target BMC firmware.
2. The fault recovery method of claim 1, further comprising:
and when the target BMC firmware does not respond to the target control instruction and the reset instruction, judging that the target BMC firmware fails.
3. The method of claim 1, wherein the step of establishing a communication connection with the target BMC firmware when the target BMC firmware fails comprises:
and when the target BMC firmware in the Power server fails, establishing communication connection with the target BMC firmware.
4. The method of claim 1, wherein the step of establishing a communication connection with the target BMC firmware when the target BMC firmware fails comprises:
when the target BMC firmware in the X86 server fails, a communication connection is established with the target BMC firmware.
5. The fault recovery method of claim 1, further comprising:
and when the fault of the target BMC firmware is recovered, disconnecting the communication connection with the target BMC firmware.
6. The failure recovery method according to any of claims 1 to 5, characterized in that the mobile storage device is in particular a U-disk or a memory card.
7. The fault recovery device for the BMC firmware is applied to a mobile storage device and comprises the following components:
the starting judgment module is used for establishing communication connection with the target BMC firmware when the target BMC firmware fails and judging whether a target U-boot in the target BMC firmware can be started normally or not;
the first judgment module is used for starting the standby BMC firmware stored in the mobile storage device by using the target U-boot if the target U-boot can be started normally;
the second judgment module is used for burning the standby U-boot stored in the mobile storage device to the target BMC firmware and starting the standby BMC firmware stored in the mobile storage device by using the standby U-boot if the target U-boot cannot be started normally;
and the fault recovery module is used for refreshing the target BMC firmware by using the standby BMC firmware when the standby BMC firmware is started so as to recover the fault of the target BMC firmware.
8. A fault recovery device for BMC firmware, comprising:
a memory for storing a computer program;
a processor for implementing the steps of a method of fault recovery for BMC firmware as claimed in any one of claims 1 to 6 when executing said computer program.
9. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, carries out the steps of a method of fault recovery for BMC firmware as claimed in any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111088585.3A CN113778756A (en) | 2021-09-16 | 2021-09-16 | Fault recovery method, device, equipment and medium for BMC (baseboard management controller) firmware |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111088585.3A CN113778756A (en) | 2021-09-16 | 2021-09-16 | Fault recovery method, device, equipment and medium for BMC (baseboard management controller) firmware |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113778756A true CN113778756A (en) | 2021-12-10 |
Family
ID=78851608
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111088585.3A Pending CN113778756A (en) | 2021-09-16 | 2021-09-16 | Fault recovery method, device, equipment and medium for BMC (baseboard management controller) firmware |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113778756A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115016822A (en) * | 2022-07-22 | 2022-09-06 | 浪潮商用机器有限公司 | BMC (baseboard management controller) firmware updating method, device, equipment and computer readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103186393A (en) * | 2011-12-30 | 2013-07-03 | 鸿富锦精密工业（深圳）有限公司 | Electronic device with substrate management controller firmware and firmware loading method |
| CN103246583A (en) * | 2012-02-09 | 2013-08-14 | 鸿富锦精密工业（深圳）有限公司 | Electronic device with bulk molding compound (BMC) firmware repairing function and repairing method |
| CN105653405A (en) * | 2015-12-31 | 2016-06-08 | 北京锐安科技有限公司 | Fault processing method and system of U-boot |
| CN107729038A (en) * | 2017-11-27 | 2018-02-23 | 英业达科技有限公司 | The baseboard management controller of firmware update and renewable firmware |
-
2021
- 2021-09-16 CN CN202111088585.3A patent/CN113778756A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103186393A (en) * | 2011-12-30 | 2013-07-03 | 鸿富锦精密工业（深圳）有限公司 | Electronic device with substrate management controller firmware and firmware loading method |
| CN103246583A (en) * | 2012-02-09 | 2013-08-14 | 鸿富锦精密工业（深圳）有限公司 | Electronic device with bulk molding compound (BMC) firmware repairing function and repairing method |
| CN105653405A (en) * | 2015-12-31 | 2016-06-08 | 北京锐安科技有限公司 | Fault processing method and system of U-boot |
| CN107729038A (en) * | 2017-11-27 | 2018-02-23 | 英业达科技有限公司 | The baseboard management controller of firmware update and renewable firmware |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115016822A (en) * | 2022-07-22 | 2022-09-06 | 浪潮商用机器有限公司 | BMC (baseboard management controller) firmware updating method, device, equipment and computer readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106257417B (en) | Boot program upgrading method, embedded equipment, control equipment and embedded system | |
| CN112433769A (en) | BMC starting method and device, computer equipment and storage medium | |
| CN111694710A (en) | Method, device and equipment for monitoring faults of substrate management controller and storage medium | |
| JP2013164842A (en) | Electronic device having restoration function of bmc firmware and restoration method of the same | |
| CN111800304A (en) | Process running monitoring method, storage medium and virtual device | |
| CN108737153B (en) | Block chain disaster recovery system, method, server and computer-readable storage medium | |
| CN111338698A (en) | Method and system for accurately booting server by BIOS (basic input output System) | |
| CN111124761B (en) | Equipment restarting method, device, equipment and medium | |
| CN113778756A (en) | Fault recovery method, device, equipment and medium for BMC (baseboard management controller) firmware | |
| CN112131043A (en) | Method and device for detecting and recovering abnormity of basic input and output system | |
| CN115756648A (en) | Active recovery method and terminal for double-substrate management controller chip | |
| CN116627702A (en) | Method and device for restarting virtual machine in downtime | |
| CN108829442A (en) | Program starts method and device | |
| JP2007200103A (en) | Client-server system and resource control method | |
| CN111078452A (en) | BMC firmware image recovery method and device | |
| CN115167883A (en) | Operating system installation method, device, equipment and storage medium | |
| CN115454515A (en) | System processing method and device and electronic equipment | |
| CN114995854A (en) | Application program online upgrading method and device, terminal and operation machine | |
| CN114860292A (en) | Terminal equipment firmware upgrading control method and device, computer equipment and medium | |
| CN111158783B (en) | Environment variable modification method, device and equipment and readable storage medium | |
| CN108170247A (en) | BMC power loss recovery method and apparatus | |
| CN115129517B (en) | BIOS (basic input output system) option fault recovery method, device, equipment and storage medium | |
| CN117472457B (en) | Dual BIOS (basic input output system), system switching method, device, equipment and storage medium | |
| CN104142870A (en) | Virtual BIOS (basic input /output system) booting system and virtual BIOS booting method | |
| CN109783150A (en) | A kind of anti-brick method and device of embedded system starting |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20211210 |
|
| RJ01 | Rejection of invention patent application after publication |