Abstract: In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an embedded-system device. The embedded-system device determines a respective operational state of each of one or more threads of a process executing on the embedded-system device. The embedded-system device stores the respective operational state of each of the one or more threads in a thread state register in a memory of the embedded-system device. The embedded-system device stores information data associated with the respective operational state of each of the one or more threads in the thread state register. The embedded-system device determines that operation of at least one thread of the one or more threads is abnormal. The embedded-system device retrieves the stored operational states of the one or more threads from the thread state register in response to the determination. The embedded-system device outputs the retrieved operational states.

Abstract: In an aspect of the disclosure, a method, a computer-readable medium, and a computer system are provided. The computer system includes a service processor. The service processor monitors events of one or more ACPI compliant devices of a host of the service processor. The service processor maintains device data associated with the one or more ACPI compliant devices based on the events in a data store of the service processor. The service processor emulates an ACPI controller to monitor a communication channel for detecting one or more ACPI commands from the host. The service processor processes the device data in the data store in response to detecting the one or more ACPI commands on the communication channel.

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: 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: A computer-implemented method renders user interfaces for devices with multi-image option ROMs according to option ROM dispatch policies associated with the devices. The option ROM dispatch policies can specify whether the multi-image option ROM for the device is enabled or disabled. The option ROM dispatch policies can also specify the image of the multi-image option ROM to execute during boot. The multi-image ROM can include a UEFI compliant image and a legacy BIOS image. The computer-implemented method may receive user selections modifying the option ROM dispatch policies via the rendered user interfaces.

Abstract: In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an embedded-system device. The embedded-system device receives at least one IPMI message from a client device. The embedded-system device extracts message data from the at least one IPMI message. The embedded-system device determines, from the message data, a function call including at least one operation code and for processing a data collection. The embedded-system device processes the data collection based on the at least one operation code. The disclosure describes a common implementation of data transfer and usage that can serve different clients as well as future features with zero or minimum redesign or redevelopment.

Abstract: In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a service processor. The service processor sends to a DHCP server a request-to-acquire for acquiring an IP address. The service processor then receives a response from the DHCP server. The response includes a first user name. The service processor further configures a user account in association with the first user name on the service processor. The user account allows access to the service processor.

Abstract: Systems and methods for constructing extensible event log with JavaScript Object Notation (JSON) encoded payload data. The system includes a computing device. The computing device may be connected to a device, where an event has occurred. The device may send a message to the management software of the computing device based on the event, where the message includes information corresponding to an event occurred at the device and payload data of the event. When the management software receives the message, the management software may determine an event type of the event based on the information, and then convert the payload data of the event to encoded payload data in an extensible format, such as the JSON format. Thus, the management software may generate and store an event log comprising the event type and the encoded payload data.

Abstract: A firmware, such as a unified extensible firmware interface (UEFI)-compliant firmware, provides a network protocol stack in a pre-boot execution environment. A network layer in the network protocol stack receives network packets. A firmware driver executing in the network layer determines whether individual network packets received at the network layer meet one or more pre-defined criteria. If individual network packets meet the pre-defined criteria, the firmware driver provides the network packets to a transport layer in the network protocol stack. If, however, the network packets received at the network layer do not meet the pre-defined criteria, the firmware driver discards the individual network packets.

Abstract: Firmware interfaces scale a fixed-font utilized by the firmware interfaces to display glyphs of the fixed-font at a native resolution or a preferred resolution of a display. A conversion factor is generated for scaling the glyphs of the font using the native resolution or the preferred resolution. The glyphs may be scaled using the conversion factor. The scaled glyphs may be stored and utilized to display text of the firmware interface in the native resolution or the preferred resolution.

Abstract: In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a service processor. The service processor generates a user interface on the service processor. The user interface providing access to platform specific configurations of the service processor. The service processor receives, through the user interface, an input for modifying a first configuration data item of the platform specific configurations. The service processor accordingly modifies the first configuration data item in accordance with the input.

Abstract: Aspects of the disclosure relate to management node failover systems and methods. The system includes two management devices and a detection and reversal device. Each of the two management devices has a processor and a non-volatile memory storing computer executable code. The two management devices function respectively as an active node and a passive node. The detection and reversal device monitors status of the active node. When the active node fails, the detection and reversal device sends an activation signal to the passive node. The passive node, in response to receiving the active signal, switches from the passive node to the active node.

Abstract: In an aspect of the disclosure, a method, a computer-readable medium, and a computer system are provided. The computer system includes a BMC. The BMC receives, through a management platform on the BMC, a first part of initialization data from an initialization component of a host of the BMC. The BMC also receives an indication of a location at an initialization storage device of the host. The BMC then obtains access to the initialization storage device. The BMC reads a second part of the initialization data from the location of the initialization storage device.

Abstract: Technologies are disclosed herein for launching updated firmware file system (FFS) files of an updated firmware. Original FFS files may be stored in a first firmware volume and updates to any of the original FFS files may be stored as updated FFS files in a second firmware volume. When booting up a computer system with an original FFS file and a corresponding updated FFS file, either the original FFS file or the updated FFS file may be executed based at least in part on an indication of the updated FFS file in one of either a black list or a launch list. The first time a computer system is boot up after storing an updated FFS file in the second firmware volume, the updated FFS file may be executed to determine whether the execution of the updated FFS file warrants inclusion in either the black list or the launch list.

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 disclosed herein for updating a firmware file system (FFS) file by preserving the original FFS file in its current firmware volume and then storing an updated version of the original FFS file in a firmware volume for updated FFS files. The updated FFS file may be stored in the firmware volume for updated FFS files referenced to the same FFS file identifier as the original FFS file. During boot-up of a system incorporating the updated firmware, the firmware volume for updated FFS files may be accessed to determine if an updated version of any FFS files are present. If updated FFS files are present, then those updated FFS files may be executed, rather than the original FFS files.

Abstract: In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a pod manager. The pod manager receives a data object for composing a target composed-node. The pod manager determines that the data object includes an indication for high-availability. The pod manager accordingly composes a collection of composed-nodes based on the data object. The pod manager further configures the collection of composed-nodes to function as the target composed-node.

Abstract: Technologies for receiving and using alternate firmware files of a computer are described herein. In some examples, firmware files to be used instead of currently used firmware files are stored in a firmware volume, which is stored in a UEFI partition. A flag is set indicating the presence of a firmware volume containing the alternate firmware files. At boot time, if it is determined that the flag has been set, the computer will utilize files stored in the firmware volume stored in the UEFI partition rather than corresponding files in a firmware.

Abstract: Certain aspects direct to systems and methods for providing an intuitive user interface (UI) for device or vendor independent network switch management via a management controller. The management controller is communicatively connected to a network switch through a Simple Network Management Protocol (SNMP) interface. The management controller provides a web UI. When a remote computing device request the web UI, the management controller sends the web UI to the remote computing device. Thus, a user at the remote computing device may upload the parsed information of the MIB file to the management controller through the UI. The management controller then processes the parsed information of the MIB file, and displays the processed parsed information in a hierarchical organization through the UI. Then the management controller establishes a communication between the management controller and the network switch through the SNMP interface based on the parsed information of the MIB file.

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.