Patent Application
20230244564
The present disclosure relates in general to information handling systems, and more particularly to systems and method for proactively staging preboot firmware components for offline update and remediation.
As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
A critical component of modern information handling systems is the BIOS. A BIOS may comprise boot firmware configured to be the first code executed by a processor of an information handling system when the information handling system is booted and/or powered on, and serves to initialize information handling resources of the information handling system and/or initialize interoperation of the information handling system with other information handling systems. In addition to BIOS, an information handling system may include critical firmware for one or more other components of the information handling system.
Existing approaches for updating firmware, whether for BIOS or another component, are often complicated for end users, as such approaches may require a system reboot, network connection, and operating system environment transition (e.g., a payload transfer from an operating system environment to a preboot environment). As of the date of filing of this application, all firmware updates are typically initiated or promoted from an operating system environment. Thus, if an information handling system is unable to boot to an operating system, then either a network connection may be required or the end user may need to download the firmware update image from another computer in order to make the update.
Applicant has found that new firmware adoption rates within the industry is very low, as end users often postpone firmware updates due to the complexity. In fact, the new firmware adoption rate six months after a firmware update is often less than one-half. Due to this low adoption rate, information handling systems may miss out on important bug fixes, features updates, and security updates, which may lead to increased support costs and quality control issues. Further, when an information handling system experiences a boot problem (which may be related to a firmware issue), it may already be too late to update firmware from an operating system environment or backend server, and may require a costly repair at a repair center.
In accordance with the teachings of the present disclosure, the disadvantages and problems associated with existing approaches to firmware updating may be reduced or eliminated.
In accordance with embodiments of the present disclosure, an information handling system may include a processor, a memory communicatively coupled to the processor, and a basic input/output system (BIOS) communicatively coupled to the processor and comprising a program of executable instructions configured to, when read and executed by the processor: monitor diagnostics information associated with one or more information handling resources of the information handling system, from the diagnostics information, determine whether a trigger point associated with a prescription for initiating a firmware update has been reached, and responsive to the trigger point being reached, perform a remedial action as defined by the prescription.
In accordance with these and other embodiments of the present disclosure, a method may include, in a basic input/output system (BIOS) of an information handling system: monitoring diagnostics information associated with one or more information handling resources of the information handling system, from the diagnostics information, determining whether a trigger point associated with a prescription for initiating a firmware update has been reached, and responsive to the trigger point being reached, performing a remedial action as defined by the prescription.
In accordance with these and other embodiments of the present disclosure, an article of manufacture may include a non-transitory computer-readable medium and computer-executable instructions carried on the computer-readable medium, the instructions readable by a processor, the instructions, when read and executed, for causing the processor to: monitor diagnostics information associated with one or more information handling resources of an information handling system, from the diagnostics information, determine whether a trigger point associated with a prescription for initiating a firmware update has been reached, and responsive to the trigger point being reached, perform a remedial action as defined by the prescription.
Technical advantages of the present disclosure may be readily apparent to one skilled in the art from the figures, description and claims included herein. The objects and advantages of the embodiments will be realized and achieved at least by the elements, features, and combinations particularly pointed out in the claims.
It is to be understood that both the foregoing general description and the following detailed description are examples and explanatory and are not restrictive of the claims set forth in this disclosure.
A more complete understanding of the present embodiments and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features, and wherein:
Preferred embodiments and their advantages are best understood by reference to
For the purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an information handling system may be a personal computer, a personal digital assistant (PDA), a consumer electronic device, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include memory, one or more processing resources such as a central processing unit (“CPU”) or hardware or software control logic. Additional components of the information handling system may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input/output (“I/O”) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communication between the various hardware components.
For the purposes of this disclosure, computer-readable media may include any instrumentality or aggregation of instrumentalities that may retain data and/or instructions for a period of time. Computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive or floppy disk), a sequential access storage device (e.g., a tape disk drive), compact disk, CD-ROM, DVD, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and/or flash memory; as well as communications media such as wires, optical fibers, microwaves, radio waves, and other electromagnetic and/or optical carriers; and/or any combination of the foregoing.
For the purposes of this disclosure, information handling resources may broadly refer to any component system, device or apparatus of an information handling system, including without limitation processors, service processors, basic input/output systems, buses, memories, I/O devices and/or interfaces, storage resources, network interfaces, motherboards, and/or any other components and/or elements of an information handling system.
In some embodiments, an information handling system 102 may comprise a personal computer. In some embodiments, an information handling system 102 may comprise or be an integral part of a server. In other embodiments, an information handling system 102 may comprise a portable information handling system (e.g., a laptop or notebook, etc.). As depicted in
Processor 103 may include any system, device, or apparatus configured to interpret and/or execute program instructions and/or process data, and may include, without limitation, a microprocessor, microcontroller, digital signal processor (DSP), application specific integrated circuit (ASIC), or any other digital or analog circuitry configured to interpret and/or execute program instructions and/or process data. In some embodiments, processor 103 may interpret and/or execute program instructions and/or process data stored in memory 104 and/or another component of information handling system 102.
Memory 104 may be communicatively coupled to processor 103 and may include any system, device, or apparatus configured to retain program instructions and/or data for a period of time (e.g., computer-readable media). Memory 104 may include RAM, EEPROM, a PCMCIA card, flash memory, magnetic storage, opto-magnetic storage, or any suitable selection and/or array of volatile or non-volatile memory that retains data after power to information handling system 102 is turned off.
As shown in
As shown in
Image staging area 112 may comprise any suitable non-volatile, preboot-accessible portion of memory 104. For example, image staging area 112 may include or may be a part of a Non-Volatile Memory Enhanced (NVMe) boot partition, Extensible Firmware Interface (EFI) system partition (ESP), or designated Serial Peripheral Interface (SPI) storage.
Prescription payload 114 may be stored in any suitable non-volatile, preboot-accessible portion of memory 104. For example, prescription payload 114 may be stored in an NVMe boot partition, ESP, or designated SPI storage. Prescription payload 114 may comprise a table, list, map, or other suitable data structure that sets forth one or more prescriptions for initiating a firmware update, wherein each prescription may include a prescription identifier (ID), an associated error/error code, an associated remedial action, associated metadata, a trigger point for a smart notification associated with the prescription, preboot notification text associated with the prescription, dependencies on one or more other prescriptions, a completion status, and/or a firmware type (e.g., BIOS firmware, management engine (ME) firmware, NVMe firmware, etc.).
Turning back to
Smart notification manager 116 may comprise a program of instructions configured to, when read and executed by processor 103, monitor telemetry information associated with firmware executing on various components of information handling system 102 (e.g., via BIOS IQ) and in response to detecting a trigger within such telemetry information that is set forth in a prescription 202 of prescription payload 114, communicate a smart notification as set forth in the prescription 202, and in response to user action and/or an administrative policy for information handling system 102, cause prescription execution manager 118 to perform an offline update and/or remediation of firmware, as described in greater detail below.
Prescription execution manager 118 may comprise a program of instructions configured to, when read and executed by processor 103, perform an offline update and/or remediation of firmware, as described in greater detail below.
Network interface 108 may comprise any suitable system, apparatus, or device operable to serve as an interface between information handling system 102 and one or more other information handling systems via an in-band management network. Network interface 108 may enable information handling system 102 to communicate using any suitable transmission protocol and/or standard. In these and other embodiments, network interface 108 may comprise a network interface card, or “NIC.” In some embodiments, network interface 108 may comprise a 10 gigabit Ethernet network interface. In these and other embodiments, network interface 108 may be enabled as a local area network (LAN)-on-motherboard (LOM) card. Network interface 108 may be configured to communicate via wire-line transmissions, wireless transmission, or both.
In addition to processor 103, memory 104, BIOS 105, and network interface 108, information handling system 102 may include one or more other information handling resources.
Network 120 may be a network and/or fabric configured to couple information handling system 102, management server 122, and/or one or more other information handling systems to one another. In these and other embodiments, network 120 may include a communication infrastructure, which provides physical connections, and a management layer, which organizes the physical connections and information handling systems communicatively coupled to network 120. Network 120 may be implemented as, or may be a part of, a storage area network (SAN), personal area network (PAN), local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a wireless local area network (WLAN), a virtual private network (VPN), an intranet, the Internet or any other appropriate architecture or system that facilitates the communication of signals, data and/or messages (generally referred to as data). Network 120 may transmit data via wireless transmissions and/or wire-line transmissions using any storage and/or communication protocol, including without limitation, Fibre Channel, Frame Relay, Asynchronous Transfer Mode (ATM), Internet protocol (IP), other packet-based protocol, small computer system interface (SCSI), Internet SCSI (iSCSI), Serial Attached SCSI (SAS) or any other transport that operates with the SCSI protocol, advanced technology attachment (ATA), serial ATA (SATA), advanced technology attachment packet interface (ATAPI), serial storage architecture (SSA), integrated drive electronics (IDE), and/or any combination thereof. Network 120 and its various components may be implemented using hardware, software, or any combination thereof.
Management server 122 may comprise any information handling system including requisite hardware, software, and/or firmware for interfacing information handling system 102 via network 120 in order to perform end-to-end workload modeling, as described in greater detail below.
As depicted in
Memory 124 may be communicatively coupled to processor 123 and may include any system, device, or apparatus configured to retain program instructions and/or data for a period of time (e.g., computer-readable media). Memory 124 may include RAM, EEPROM, a PCMCIA card, flash memory, magnetic storage, opto-magnetic storage, or any suitable selection and/or array of volatile or non-volatile memory that retains data after power to management server 122 is turned off.
As shown in
Network interface 128 may comprise any suitable system, apparatus, or device operable to serve as an interface between management server 122 and network 120. Network interface 128 may enable management server 122 to communicate using any suitable transmission protocol and/or standard, including any of the protocols and/or standards described above with respect to network 120. In these and other embodiments, network interface 128 may comprise a NIC.
In addition to information handling system 102, network 120, and management server 122, system 100 may include one or more other information handling resources.
At step 302, during preboot execution of BIOS 105, smart notification manager 116 may determine if there is a new prescription payload 114 (e.g., an update of prescription payload 114 with new prescriptions 202). If there is a new prescription payload 114, method 200 may proceed to step 304. Otherwise, method 300 may proceed to step 308.
At step 304, smart notification manager 116 may verify authentication of the new prescription payload 114. If the new prescription payload 114 is authenticated, method 300 may proceed to step 306. Such authentication may be performed in any suitable manner. For example, in some embodiments, management server 122 may sign prescription payload 114 with a private key of a public-private key pair, and smart notification manager 116 may verify by applying a public key of the public-private key pair. Otherwise, method 300 may proceed to step 308 with use of an existing, authenticated prescription payload 114.
At step 306, smart notification manager 116 may apply the new, authenticated prescription payload 114.
At step 308, smart notification manager 116 may monitor diagnostics (e.g., from BIOS IQ) to determine if a trigger point for a smart notification associated with a prescription 202 has been reached. If a trigger point has been reached, method 300 may proceed to step 310. Otherwise, method 300 may proceed to step 320.
At step 310, in response to the trigger point being reached for a prescription 202, smart notification manager 116 may communicate a smart notification, as set forth in the prescription 202, to a user or administrator of information handling system 102.
At step 312, smart notification manager 116 may determine if the user or administrator chose to execute the remedial action set forth in the prescription 202 or if a policy associated with the information handling system 102 dictates execution of the remedial action. If remedial action has been chosen or dictated by policy, method 300 may proceed to step 314. Otherwise, method 300 may proceed to step 320.
At step 314, prescription execution manager 118 may read a firmware image associated with the remedial action from firmware image staging area 112. At step 316, prescription execution manager 118 may update firmware in accordance with the firmware image. In the case that a particular remedial action is indicated by prescription 202 to be dependent upon another prescription, prescription execution manager 118 may also update firmware in accordance with such dependency. At step 318, after completion of the firmware update, prescription execution manager 118 may update a status of prescription 202 in prescription payload 114 to indicate completion of the firmware update defined by the prescription 202.
At step 320 prescription execution manager 118 may boot to operating system 106. After completion of step 320, method 300 may end.
Although
Method 300 may be implemented using information handling system 102, components thereof or any other system operable to implement method 300. In certain embodiments, method 300 may be implemented partially or fully in software and/or firmware embodied in computer-readable media.
As used herein, when two or more elements are referred to as “coupled” to one another, such term indicates that such two or more elements are in electronic communication or mechanical communication, as applicable, whether connected indirectly or directly, with or without intervening elements.
This disclosure encompasses all changes, substitutions, variations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend. Similarly, where appropriate, the appended claims encompass all changes, substitutions, variations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend. Moreover, reference in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, or component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative. Accordingly, modifications, additions, or omissions may be made to the systems, apparatuses, and methods described herein without departing from the scope of the disclosure. For example, the components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses disclosed herein may be performed by more, fewer, or other components and the methods described may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order. As used in this document, “each” refers to each member of a set or each member of a subset of a set.
Although exemplary embodiments are illustrated in the figures and described below, the principles of the present disclosure may be implemented using any number of techniques, whether currently known or not. The present disclosure should in no way be limited to the exemplary implementations and techniques illustrated in the drawings and described above.
Unless otherwise specifically noted, articles depicted in the drawings are not necessarily drawn to scale.
All examples and conditional language recited herein are intended for pedagogical objects to aid the reader in understanding the disclosure and the concepts contributed by the inventor to furthering the art, and are construed as being without limitation to such specifically recited examples and conditions. Although embodiments of the present disclosure have been described in detail, it should be understood that various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the disclosure.
Although specific advantages have been enumerated above, various embodiments may include some, none, or all of the enumerated advantages. Additionally, other technical advantages may become readily apparent to one of ordinary skill in the art after review of the foregoing figures and description.
To aid the Patent Office and any readers of any patent issued on this application in interpreting the claims appended hereto, applicants wish to note that they do not intend any of the appended claims or claim elements to invoke 35 U.S.C. § 112(f) unless the words “means for” or “step for” are explicitly used in the particular claim.
