Abstract: Technologies are described for verifying the integrity of data transmitted between a firmware and a baseboard management controller (“BMC”). During a first verification phase, a data integrity tool compares system inventory data provided by firmware protocols to a system inventory module to system inventory data in a device instance format. During a second verification phase, the data integrity tool verifies operation of a firmware conversion module by comparing the system inventory data in the device instance format to the system inventory data in a JavaScript Object Notation (“JSON”) format. During a third verification phase, the data integrity tool retrieves the system inventory data from a management server and compares the system inventory data retrieved from the management server to the system inventory data previously transmitted to the management server. Identified discrepancies can be utilized to modify the system inventory module, the firmware conversion module, or the management server.

Abstract: Technologies are described herein for remotely configuring multi-mode dual in-line memory modules (“multi-mode DIMMs”) using a firmware or a baseboard management controller (“BMC”). Technologies are also described for simultaneously initiating multiple commands for configuring multi-mode DIMMs using a BMC and for updating inventory data regarding multi-mode DIMMs stored by a BMC.

Abstract: Technologies are described herein for a representational state transfer (“REST” or “RESTful”) over Intelligent Platform Management Interface (“IPMI”) interface for firmware to baseboard management controller (“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.

Abstract: A firmware enumerates the buses of root bridges in the computing system. If an OOR condition occurs during enumeration of the buses, the firmware determines the number of required buses for each root bridge causing an OOR condition. The number of required buses for bridge devices connected to each root bridge causing an OOR condition can be identified using the same set of bus numbers. Once the firmware has determined the number of buses required by each root bridge, including those not causing an OOR condition, the firmware reallocates the number of available buses between the root bridges such that each root bridge is allocated a number of the available buses greater than or equal to the number of required buses. The firmware stores data identifying the allocation and restarts the computing device. Upon rebooting, the computing system utilizes the new allocation of bus numbers to eliminate the OOR condition.

Abstract: Technologies are described herein for remotely configuring multi-mode dual in-line memory modules (“multi-mode DIMMs”) using a firmware or a baseboard management controller (“BMC”). Technologies are also described for simultaneously initiating multiple commands for configuring multi-mode DIMMs using a BMC and for updating inventory data regarding multi-mode DIMMs stored by a BMC.

Abstract: Technologies are described herein for remotely configuring multi-mode dual in-line memory modules (“multi-mode DIMMs”) using a firmware or a baseboard management controller (“BMC”). Technologies are also described for simultaneously initiating multiple commands for configuring multi-mode DIMMs using a BMC and for updating inventory data regarding multi-mode DIMMs stored by a BMC.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Technologies are described herein for a representational state transfer (“REST” or “RESTful”) over an Intelligent Platform Management Interface (“IPMI”) interface for firmware to a baseboard management controller (“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.

Abstract: 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.

Abstract: A firmware enumerates the buses of root bridges in the computing system. If an OOR condition occurs during enumeration of the buses, the firmware determines the number of required buses for each root bridge causing an OOR condition. The number of required buses for bridge devices connected to each root bridge causing an OOR condition can be identified using the same set of bus numbers. Once the firmware has determined the number of buses required by each root bridge, including those not causing an OOR condition, the firmware reallocates the number of available buses between the root bridges such that each root bridge is allocated a number of the available buses greater than or equal to the number of required buses. The firmware stores data identifying the allocation and restarts the computing device. Upon rebooting, the computing system utilizes the new allocation of bus numbers to eliminate the OOR condition.

Abstract: Technologies are described herein for a representational state transfer (“REST” or “RESTful”) over Intelligent Platform Management Interface (“IPMI”) interface for firmware to baseboard management controller (“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.

Abstract: 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.

Abstract: 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.

Abstract: Technologies are described herein for a representational state transfer (“REST” or “RESTful”) over Intelligent Platform Management Interface (“IPMI”) interface for firmware to baseboard management controller (“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.

Abstract: Technologies are described herein for a representational state transfer (“REST” or “RESTful”) over an Intelligent Platform Management Interface (“IPMI”) interface for firmware to a baseboard management controller (“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.