American Megatrends, Inc.

American Megatrends International, LLC

Purandhar Nallagatla

Harikrishna Doppalapudi

Satheesh Thomas

Ramakoti Reddy Bhimanadhuni

Sanjoy Maity

Chandrasekar Rathineswaran

Igor Kulchytskyy

Baskar Parthiban

Madhan B Santharam

Manickavasakam Karpagavinayagam

Manish Jha

Altaf Hussain

Joseprabu Inbaraj

Mark Eric Wilson

Naresh Kollu

Hari Krishna Doppalapudi

Anurag Bhatia

Winston Thangapandian

Valantina Arumugam

Muthuchamy Kumar

Abhitesh Kumar

Technologies are described herein for a representational state transfer ('REST' or 'RESTful') over Intelligent Platform Management Interface (&#x201c;IPMI&#x201d;) interface for firmware to baseboard management controller (&#x201c;BMC&#x201d;) communication and applications thereof. These applications include, but are not limited to, remote firmware configuration, firmware updates, peripheral device firmware updates, provision of management information such as system inventory data, cloning and batch migration of firmware configuration settings, and firmware integrity monitoring.

Cloning of firmware configuration settings using rest over IPMI interface

Technologies are disclosed for identifying firmware functions that were executed in a call chain prior to the occurrence of an error condition, such as an assert or an exception. In particular, a search is made from an instruction pointer ('IP') for a memory address containing a signature identifying a firmware module. The firmware module that includes a function that generated the error condition can be identified based on the memory address. The name of the function that generated the error condition can be identified using a function mapping file. Previous functions in the same call chain are identified and their names determined using the function mapping file. Output can then be generated that includes the name of the firmware module that includes the function that generated the error condition, the name of the function that generated the error condition, and the names of other functions in the same call chain.

Identifying firmware functions executed in a call chain prior to the occurrence of an error condition

In an aspect of the disclosure, a method, a computer-readable medium, and a computer system are provided. The computer system includes an initialization component of a host. The initialization component obtains health data indicating that at least one hardware component of the host is in one of one or more predetermined health conditions when executed in a system management mode of the host. The initialization component then sends, to a service processor of the host, a message in accordance with a management protocol. The message includes the health data.

Techniques of monitoring and updating system component health status

Technologies are described herein for a representational state transfer ('REST' or 'RESTful') over IPMI interface for firmware to BMC communication and applications thereof. These applications include, but are not limited to, remote firmware configuration, firmware updates, peripheral device firmware updates, provision of management information such as system inventory data, cloning and batch migration of firmware configuration settings, and firmware integrity monitoring. This functionality can be provided in a way that enables communication between BMCs and firmware to utilize modern manageability interfaces while maintaining backward compatibility with previous IPMI implementations.

Peripheral device firmware update using rest over IPMI interface firmware update module

Peripheral device firmware update using rest over IPMI interface firmware shell utility

A firmware attempts to allocate memory address resources, such as memory addresses in a PCI I/O and a PCI memory address space, to bus devices in a multi-processor computing system. If an out-of-resource (OOR) condition occurs during allocation of the memory address resources, memory address resources can be re-allocated from stacks that were successfully allocated requested resources to stacks that were not successfully allocated requested resources. Memory address resources can also, or alternately, be re-allocated from sockets that were successfully allocated requested resources to sockets that were not successfully allocated requested resources. If stack-level or socket-level readjustment of the memory address resource allocation fails, a base memory address of a configuration memory address space can be lowered, and the allocation can be retried. A pre-defined memory address resource allocation table can also be utilized to allocate the memory address resources following failure of the stack-level and socket-level allocation readjustment.

Distribution of memory address resources to bus devices in a multi-processor computing system

In an aspect of the disclosure, a method, a computer-readable medium, and a computer system are provided. The computer system includes an initialization component of a host. The initialization component requests from a service processor of the host a first replacement firmware image of a first device of the host. The initialization component then receives the first replacement firmware image from the service processor. The initialization component further provides the first replacement firmware image to a first updating program. The initialization component uses the first updating program to replace the first existing firmware image on the first device with the first replacement firmware image.

Techniques of updating host device firmware via service processor

Technologies are disclosed for identifying and remediating correctable hardware errors. A firmware can detect a system management interrupt ('SMI') generated by a hardware device responsive to the occurrence of a correctable error. Once the firmware has identified the device that generated the SMI, the firmware can determine whether an earliest recorded error generated by the identified device is longer ago than a threshold amount of time. If the earliest recorded error generated by the device is not longer ago than the threshold amount of time, the firmware can increment an error count for the device. The firmware can also determine whether the error count for the device exceeds a threshold. If the error count for the device exceeds the threshold, the firmware can generate an error notification for the device. The firmware can also implement a remedial action policy for the device.

Identifying an remediating correctable hardware errors

Technologies are described herein for a representational state transfer ('REST' or 'RESTful') over an Intelligent Platform Management Interface (&#x201c;IPMI&#x201d;) interface for firmware to a baseboard management controller (&#x201c;BMC&#x201d;) communication and applications thereof. These applications include, but are not limited to, remote firmware configuration, firmware updates, peripheral device firmware updates, provision of management information such as system inventory data, cloning and batch migration of firmware configuration settings, and firmware integrity monitoring. This functionality can be provided in a way that enables communication between BMCs and firmware to utilize modern manageability interfaces while maintaining backward compatibility with previous IPMI implementations.

Rest over IPMI interface for firmware to BMC communication

Technologies are described herein for a representational state transfer ('REST' or 'RESTful') over Intelligent Platform Management Interface (&#x201c;IPMI&#x201d;) interface for firmware to baseboard management controller (&#x201c;BMC&#x201d;) communication and applications thereof. These applications include, but are not limited to, remote firmware configuration, firmware updates, peripheral device firmware updates, provision of management information such as system inventory data, cloning and batch migration of firmware configuration settings, and firmware integrity monitoring. This functionality can be provided in a way that enables communication between BMCs and firmware to utilize modern manageability interfaces while maintaining backward compatibility with previous IPMI implementations.

Configuration of availability of debugging messages during the execution of a firmware in a debugging mode of operation is provided. The configuration can be updated without rebuilding the firmware. Thus, a selection of a group of available types of debugging messages can be updated dynamically, at various runtime instances of the firmware. The selection can be accomplished by configuring, at a runtime of the firmware, a level of recordation of debugging messages and one or more data structures associated with the level or recordation. Each of the one or more data structures includes elements indicative of respective types of debugging messages being enabled or disabled for presentation during the execution of the firmware in the debugging mode of operation. A debugging message can be provided based at least partially on at least one of the data structure(s) during the execution of the firmware in the debugging mode of operation.

Dynamic configuration of availability of debugging messages

Firmware configuration using REST over IPMI interface

Firmware update using rest over IPMI interface

In an aspect of the disclosure, a method, a computer-readable medium, and a computer system are provided. The computer system includes an initialization component of a host. The initialization component determines presence or absence of a plurality of hardware components of the host. The initialization component further generates a first series of indicators indicating the determined presence or absence of the plurality of hardware components. The initialization component sends, to a service processor of the host, a message in accordance with a management protocol, the message including the first series of indicators.

Techniques of providing policy options to enable and disable system components

Technologies are described herein for a representational state transfer ('REST' or 'RESTful') over Intelligent Platform Management Interface (&#x201c;IPMI&#x201d;) interface for firmware to BMC communication and applications thereof. These applications include, but are not limited to, remote firmware configuration, firmware updates, peripheral device firmware updates, provision of management information such as system inventory data, cloning and batch migration of firmware configuration settings, and firmware integrity monitoring. This functionality can be provided in a way that enables communication between BMCs and firmware to utilize modern manageability interfaces while maintaining backward compatibility with previous IPMI implementations.

Growing community of inventors

Johns Creek, GA, United States of America

Purandhar Nallagatla