Abstract: A DC-SCM undiscoverable device configuration system includes a DC-MHS computing device with an operational system, a discoverable device, an undiscoverable device, and a DC-SCM device coupled to the operational system and the discoverable device. The DC-SCM device receives and store static undiscoverable device operation information for the undiscoverable device and, during initialization operations for the DC-MHS computing device, retrieves static discoverable device operational information for the discoverable device and the static undiscoverable device operation information and uses it to configure operation of the operational system. During runtime operations for the DC-MHS computing device, the DC-SCM device retrieves dynamic discoverable device operational information from the discoverable device and the static undiscoverable device operation information, and uses it to modify operation of the operational system.

Abstract: A BMC memory expansion system includes a computing device having a BMC device that provides services for the computing device, a memory subsystem, a computing device component coupled to the memory subsystem, and a memory agent subsystem coupled to the BMC device and the computing device component. The memory agent subsystem receives a service memory request from the BMC device and, in response, instructs the computing device component to operate as a memory proxy and reserve the memory subsystem for use by the BMC device to provide a BMC reserved memory subsystem. The memory agent subsystem then transmits data from the BMC device and via the computing device component to the BMC reserved memory subsystem, and from the BMC reserved memory subsystem and via the computing device component to the BMC device, to allow the BMC device to provide at least one of the services for the computing device.

Abstract: A DataCenter Secure Control Module (DC-SCM) as-a-service system includes a DataCenter Modular Hardware System (DC-MHS) computing device having a Host Processor Module (HPM) and a networking device that is coupled to the HPM and a network, and a DC-SCM provisioning system that is coupled to the networking device via the network. The DC-SCM provisioning system provides a networking device service instance for the networking device, receives a networking device DC-SCM functionality configuration for the networking device through the network via the networking device service instance, and configures at least one image to provide networking device DC-SCM functionality defined by the networking device DC-SCM functionality configuration. The networking device receives the at least one image via the network, and executes the at least one image to perform the networking device DC-SCM functionality with the HPM.

Abstract: A DC-SCM composable BIOS system includes a DC-MHS computing device having a DC-SCM device with a BIOS subsystem and a BIOS configuration database. During initialization operations for the DC-SCM device that are part of an initialization of the DC-MHS computing device, the DC-SCM device determines that the DC-SCM device requires a BIOS image to be composed in order to operate with the DC-MHS computing device, and identifies a DC-MHS computing device processing system configuration and a DC-MHS computing device hardware configuration of the DC-MHS computing device. The DC-SCM device then retrieves BIOS modules from the BIOS configuration database based on the DC-MHS computing device processing system configuration and the DC-MHS computing device hardware configuration of the DC-MHS computing device, and uses them to compose the BIOS image. The DC-SCM device then provides the BIOS image in the BIOS subsystem, and causes a second initialization of the DC-MHS computing device.

Abstract: An Information Handling System (IHS) includes multiple hardware devices, and a Baseboard Management Controller (BMC) in communication with the hardware devices. The BMC includes executable code to cause the BMC to receive a message associated with a non-registered hardware device that is not registered to be managed by the BMC in which the message formatted according to a native protocol of the BMC. The code further causes the code to transmit the message to a device plugin associated with the non-registered hardware device in which the device plugin comprises custom instructions that, upon execution by a system processor, cause the IHS to convert the message into a protocol associated with the non-registered hardware device, and forward the converted message to the non-registered hardware device using the protocol of the non-registered hardware device.

Abstract: Methods and systems are provided for managing dynamic devices of an IHS (Information Handling System) that include re-programmable logic circuitry. The dynamic devices of the IHS are identified and the type of a dynamic device is determined based on operations implemented by the re-programmable logic circuitry of that dynamic device. The dynamic device is enrolled for management by a remote access controller of the IHS based on its determined type. Messages are registered for management of the dynamic device, where the messages are selected based on its determined type. Remote management of the dynamic device is initiated using the registered messages. Any programming that changes the type of the dynamic device of the dynamic device is detected. If a change is detected, the dynamic device is enrolled for remote management using updated messages based on its updated type.

Abstract: An Information Handling System (IHS) includes multiple hardware devices, and a Baseboard Management Controller (BMC) in communication with the hardware devices. The BMC includes executable code to cause the BMC to receive a message associated with a non-registered hardware device that is not registered to be managed by the BMC in which the message formatted according to a native protocol of the BMC. The code further causes the code to transmit the message to a device plugin associated with the non-registered hardware device in which the device plugin comprises custom instructions that, upon execution by a system processor, cause the IHS to convert the message into a protocol associated with the non-registered hardware device, and forward the converted message to the non-registered hardware device using the protocol of the non-registered hardware device.

Abstract: Methods and systems are provided for managing dynamic devices of an IHS (Information Handling System) that include re-programmable logic circuitry. The dynamic devices of the IHS are identified and the type of a dynamic device is determined based on operations implemented by the re-programmable logic circuitry of that dynamic device. The dynamic device is enrolled for management by a remote access controller of the IHS based on its determined type. Messages are registered for management of the dynamic device, where the messages are selected based on its determined type. Remote management of the dynamic device is initiated using the registered messages. Any programming that changes the type of the dynamic device of the dynamic device is detected. If a change is detected, the dynamic device is enrolled for remote management using updated messages based on its updated type.

Abstract: Systems and methods are provided for updating hot-pluggable devices of an information handling system using dynamic EFI System Resource Table (ESRT) entries to implement an ESRT entry update procedure for hot-pluggable devices. Extended configuration space (e.g., such as PCIe Extended Config Space) of a hot-pluggable device may be utilized to store firmware update version information such as firmware version details, which is used in the OS space to update the ESRT table, and the system OS may read and apply the updated firmware version information and apply the firmware update immediately without additional OS reboots.

Abstract: A method and information handling system (IHS) that optimizes boot time. The method includes a basic input output system (BIOS) performing an authentication check of drivers during an initial boot process. The results of the authentication check are stored along with an unified extensible firmware interface (UEFI) image for each driver in an authentication results data structure (ARDS). In response to receipt of a subsequent request to enable a secure boot of the IHS, when the initial boot process was performed with the secure boot disabled, the ARDS is accessed to determine if any of the drivers failed the authentication check. When none of the drivers have failed the authentication check, the boot process is continued using the UEFI images of the drivers. When at least one of the drivers has failed its authentication check, a notification is output indicating a failure of the authentication check.

Abstract: Systems and methods are provided for updating hot-pluggable devices of an information handling system using dynamic EFI System Resource Table (ESRT) entries to implement an ESRT entry update procedure for hot-pluggable devices. Extended configuration space (e.g., such as PCIe Extended Config Space) of a hot-pluggable device may be utilized to store firmware update version information such as firmware version details, which is used in the OS space to update the ESRT table, and the system OS may read and apply the updated firmware version information and apply the firmware update immediately without additional OS reboots.

Abstract: Systems and methods are provided that may be implemented to deliver firmware for pre-boot updates of targeted information handling system device/devices using custom update capsules (e.g., such as custom unified extensible firmware interface capsules) and a separately-stored firmware update package that is remotely or locally stored. The custom update capsules may contain instruction payload information that may be used to determine location and desired components of the separately-stored firmware update package, and that also may be used to determine whether existing driver/drivers are to be retained in a firmware module in system memory or to be unloaded and replaced with a new (e.g., upgraded or downgraded) driver version in a firmware module in system memory as part of the firmware update.

Abstract: Systems and methods are provided that may be implemented to deliver firmware for pre-boot updates of targeted information handling system device/s using custom update capsules (e.g., such as custom UEFI capsules) and a separately-stored firmware update package that is remotely or locally stored. The custom update capsules may contain instruction payload information that may be used to determine location and desired components of the separately-stored firmware update package, and that also may be used to determine whether existing driver/s are to be retained in a firmware module in system memory or to be unloaded and replaced with a new (e.g., upgraded or downgraded) driver version in a firmware module in system memory as part of the firmware update.

Abstract: A method and information handling system (IHS) that optimizes boot time. The method includes a basic input output system (BIOS) performing an authentication check of drivers during an initial boot process. The results of the authentication check are stored along with an unified extensible firmware interface (UEFI) image for each driver in an authentication results data structure (ARDS). In response to receipt of a subsequent request to enable a secure boot of the IHS, when the initial boot process was performed with the secure boot disabled, the ARDS is accessed to determine if any of the drivers failed the authentication check. When none of the drivers have failed the authentication check, the boot process is continued using the UEFI images of the drivers. When at least one of the drivers has failed its authentication check, a notification is output indicating a failure of the authentication check.