Baseboard management controller recovery

US9921915B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9921915-B2
Application numberUS-201514885157-A
CountryUS
Kind codeB2
Filing dateOct 16, 2015
Priority dateOct 16, 2015
Publication dateMar 20, 2018
Grant dateMar 20, 2018

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A method for recovering a baseboard management controller (BMC) by determining, by a basic input/output system (BIOS), whether a BMC recovery mode is generated by a recovery mode jumper being triggered. The system performing the method can further install, if the recovery jumper is not triggered, a BMC firmware update driver and detect, if the recovery jumper is not triggered, a BMC image. The system that performs the method can further update, if the recovery jumper is not triggered, the BMC firmware and copy to a backup image, if the recovery jumper is not triggered, the BMC firmware update.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for recovering a baseboard management controller, the method comprising: determining, by a basic input/output system, whether a baseboard management controller recovery mode is triggered by a physical recovery mode jumper; in an event that the recovery mode is not triggered by the physical recovery mode jumper, installing a baseboard management controller firmware update driver configured to identify a revision level of a specific firmware image; searching for a baseboard management controller firmware that is the most recent backup version of a working firmware for the baseboard management controller; updating, the baseboard management controller with the baseboard management controller firmware; and storing a backup image of the baseboard management controller firmware. 2. The method of claim 1 , wherein when the recovery mode is not generated by the recovery mode jumper being triggered, the baseboard management controller firmware requires updating. 3. The method of claim 1 , wherein when the baseboard management controller recovery mode is generated by the recovery mode jumper, the baseboard management controller continues to a power on self-test. 4. The method of claim 1 , wherein installing the baseboard management controller firmware update driver comprises: acquiring information about a current firmware image; comparing the information about the current firmware image with a current saved firmware image; acquiring, when the current firmware image is newer than the current saved firmware image, a copy of the current firmware image for the basic input/output system to perform a baseboard management controller roll-back; programming a firmware image; and validating the firmware image, wherein a baseboard management controller roll-back programs the current firmware image as a new firmware image. 5. The method of claim 4 , wherein installing the baseboard management controller firmware update driver further comprises saving the new firmware image into non-volatile random access memory if a current firmware version is newer than the current firmware image. 6. The method of claim 4 , wherein installing the baseboard management controller firmware update driver further comprises saving the new firmware image into recovery storage if a current firmware version is newer than the current firmware image. 7. The method of claim 4 , wherein installing the baseboard management controller firmware update driver further comprises booting into an operating system. 8. The method of claim 1 , wherein when detecting a baseboard management controller image, the basic input/output system searches all recovery storages to detect whether there is any authorized baseboard management controller image present. 9. The method of claim 8 , wherein a detected authorized baseboard management controller image can reprogram/recover the baseboard management controller firmware. 10. The method of claim 8 , wherein when no authorized baseboard management controller image is detected the basic input/output system acquires a new image to reprogram the baseboard management controller firmware automatically. 11. The method of claim 10 , wherein the basic input/output system accesses an internet or official website to acquire the new image. 12. The method of claim 1 , wherein updating the baseboard management controller firmware further comprises acquiring a current baseboard management controller firmware update driver within an BIOS. 13. The method of claim 12 , wherein the basic input/output system accesses an internet or official website to acquire the current baseboard management controller firmware update driver. 14. A baseboard management controller storing instructions that, when executed by the baseboard management controller, cause the baseboard management controller to perform operations comprising: determining, by a basic input/output system, whether a baseboard management controller recovery mode is triggered by a physical recovery mode jumper; in an event that the recovery mode is not triggered by the physical recovery mode jumper, installing a baseboard management controller firmware update driver configured to identify a revision level of a specific firmware image; searching for a baseboard management controller firmware that is the most recent backup version of a working firmware for the baseboard management controller; updating the baseboard management controller with the baseboard management controller firmware; and storing a backup image of the baseboard management controller firmware. 15. The baseboard management controller of claim 14 , wherein when the recovery mode is not generated by the recovery mode jumper being triggered, the baseboard management controller firmware requires updating. 16. The baseboard management controller of claim 14 , wherein when the baseboard management controller recovery mode is generated by the recovery mode jumper, the baseboard management controller continues to a power on self-test. 17. The baseboard management controller of claim 14 , further comprising instructions, which, when installing the baseboard management controller firmware update driver, cause the baseboard management controller to perform further operations comprising: acquiring information about a current firmware image; comparing the information about the current firmware image with a current saved firmware image; acquiring, when the current firmware image is newer than the current saved firmware image, a copy of the current firmware image for the basic input/output system to perform a baseboard management controller roll-back; programming a firmware image; and validating the firmware image, wherein a baseboard management controller roll-back programs the current firmware image as a new firmware image. 18. The baseboard management controller of claim 17 , further including instructions, when installing the baseboard management controller firmware update driver, that cause the baseboard management controller to: save the new firmware image into non-volatile random access memory if a current firmware version is newer than the current firmware image. 19. The baseboard management controller of claim 17 , further including instructions, when installing the baseboard management controller firmware update driver, that cause the baseboard management controller to: save the new firmware image into recovery storage if a current firmware version is newer than the current firmware image. 20. The baseboard management controller of claim 17 , further including instructions, when installing the baseboard management controller firmware update driver, that cause the baseboard management controller to: boot into an operating system. 21. The baseboard management controller of claim 14 , wherein the basic input/output system searches all recovery storages to detect whether there is any authorized baseboard management controller image present. 22. The baseboard management controller of claim 21 , wherein a detected authorized baseboard management controller image can reprogram/recover the baseboard management controller firmware. 23. The baseboard management controller of claim 21 , wherein when no authorized baseboard management controller image is detected the basic input/output system acquires a new image to reprogram the baseboard management controller firmware automatically. 24. The baseboard management control

Assignees

Inventors

Classifications

  • Boot up procedures · CPC title

  • G06F21/575Primary

    Secure boot · CPC title

  • G06F8/65Primary

    Updates (security arrangements therefor G06F21/57) · CPC title

  • Monitoring arrangements for monitoring environmental properties or parameters of the computing system or of the computing system component, e.g. monitoring of power, currents, temperature, humidity, position, vibrations (thermal management in cooling arrangements of a computing system G06F1/206) · CPC title

  • using file system or storage system metadata · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9921915B2 cover?
A method for recovering a baseboard management controller (BMC) by determining, by a basic input/output system (BIOS), whether a BMC recovery mode is generated by a recovery mode jumper being triggered. The system performing the method can further install, if the recovery jumper is not triggered, a BMC firmware update driver and detect, if the recovery jumper is not triggered, a BMC image. The …
Who is the assignee on this patent?
Quanta Comp Inc
What technology area does this patent fall under?
Primary CPC classification G06F11/1417. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Mar 20 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).