Abstract: An Information Handling System (IHS) includes multiple hardware devices, and a baseboard Management Controller (BMC) in communication with the plurality of hardware devices. The BMC includes executable instructions for identifying at least one non-registered hardware device from among the multiple hardware devices that is not registered for use within the IHS by the BMC. For this non-registered hardware device, the BMC generates power profile data. Using the power profile data of the non-registered hardware device, the BMC determines a level of electrical power to sufficiently supply the plurality of hardware devices of the IHS, and controls one or more power supply units to supply the determined level of electrical power to the plurality of hardware devices.

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: A system for distributing firmware, comprising a group controller operating on a processor and configured to perform an algorithmic process of sending an update task with a download host to one of two or more group members. A group member operating on a processor and configured to perform an algorithmic process of receiving the update task with the download host and to request a payload file from the download host.

Abstract: Methods, systems, and computer programs encoded on computer storage medium, for receiving a request for instrumentation data describing one or more devices in the computing environment, the request received from a resource management interface; retrieving the instrumentation data describing the one or more devices from a resource database; identifying a schema associated with the resource management interface; converting the instrumentation data describing the one or more devices based on the identified schema associated with the resource management interface; and transmitting the instrumentation data describing the one or more devices to the resource management interface.

Abstract: Detecting and reconfiguring of boot parameters of a NVMe subsystem, including identifying a mapping between local boot parameters of a NVMe subsystem and a GUID that corresponds to the NVMe subsystem; determining that the NVMe subsystem has been reset; in response to determining that the NVMe subsystem has been reset: transmitting a discovery request to the NVMe subsystem for remote boot parameters of the NVMe subsystem; comparing the local boot parameters for the GUID with the remote boot parameters for the NVMe subsystem; determining, based on the comparing, that the remote boot parameters for the NVMe subsystem do not match with the local boot parameters for the GUID, and in response, updating values of the local boot parameters for the GUID based on the remote boot parameters of the NVMe subsystem.

Abstract: Detecting and reconfiguring of boot parameters of a NVMe subsystem, including identifying a mapping between local boot parameters of a NVMe subsystem and a GUID that corresponds to the NVMe subsystem; determining that the NVMe subsystem has been reset; in response to determining that the NVMe subsystem has been reset: transmitting a discovery request to the NVMe subsystem for remote boot parameters of the NVMe subsystem; comparing the local boot parameters for the GUID with the remote boot parameters for the NVMe subsystem; determining, based on the comparing, that the remote boot parameters for the NVMe subsystem do not match with the local boot parameters for the GUID, and in response, updating values of the local boot parameters for the GUID based on the remote boot parameters of the NVMe subsystem.

Abstract: Support is provided for remote monitoring and management of non-standard devices of an IHS (Information Handling System) that are not supported by a remote management interface, such as the Redfish management interface. The IHS may be configured for remote management of a non-standard device as part of the manufacture of the IHS. Software for management of the non-standard device is validated against a checksum stored to the IHS during its manufacture to confirm the software for managing the non-standard device has not been altered. If the software is validated, the software is used to initialize a plugin for management of the non-standard device. Data collected by the plugin from monitoring of the non-standard device is provided to a remote access controller of the IHS and the remote access controller issues commands to the non-standard device via the plugin.

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: Embodiments are described for supporting remote monitoring and management of non-standard devices of an IHS (Information Handling System) that are not supported by a remote management interface, such as the Redfish management interface. The IHS may be configured for remote management of a non-standard device as part of the manufacture of the IHS. Software for management of the non-standard device is validated against a checksum stored to the IHS during its manufacture to confirm the software for managing the non-standard device has not been altered. If the software is validated, the software is used to initialize a plugin for management of the non-standard device according. Data collected by the plugin from monitoring of the non-standard device is provided to a remote access controller of the IHS and the remote access controller issues commands to the non-standard device via the plugin.

Abstract: An Information Handling System (IHS) includes multiple hardware devices, and a baseboard Management Controller (BMC) in communication with the plurality of hardware devices. The BMC includes executable instructions for identifying at least one non-registered hardware device from among the multiple hardware devices that is not registered for use within the IHS by the BMC. For this non-registered hardware device, the BMC generates power profile data. Using the power profile data of the non-registered hardware device, the BMC determines a level of electrical power to sufficiently supply the plurality of hardware devices of the IHS, and controls one or more power supply units to supply the determined level of electrical power to the plurality of hardware devices.

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: A system for distributing firmware, comprising a group controller operating on a processor and configured to perform an algorithmic process of sending an update task with a download host to one of two or more group members. A group member operating on a processor and configured to perform an algorithmic process of receiving the update task with the download host and to request a payload file from the download host.

Abstract: A system for distributing firmware, comprising a group controller operating on a processor and configured to perform an algorithmic process of sending an update task with a download host to one of two or more group members. A group member operating on a processor and configured to perform an algorithmic process of receiving the update task with the download host and to request a payload file from the download host.

Abstract: Methods, systems, and computer programs encoded on computer storage medium, for performing an inventory of devices to identify a particular device; creating a data structure for the particular device including data identifying the particular device; providing, a request including the data structure for the particular device; parsing the request and determining that a device class for the particular device is a new device class; in response to determining that the device class for the particular device is a new device class, creating a device-specific class for the particular device and a metaobject format for the particular device; providing the created device-specific class and the metaobject format for the particular device; and creating an instance of the device-specific class for the particular device.

Abstract: A system for distributing firmware, comprising a group controller operating on a processor and configured to perform an algorithmic process of sending an update task with a download host to one of two or more group members. A group member operating on a processor and configured to perform an algorithmic process of receiving the update task with the download host and to request a payload file from the download host.

Abstract: A method, an information handling system (IHS), and a system for capturing video data and serial data during an IHS failure. The method includes detecting, via a controller, an occurrence of a system event log (SEL) incident in the IHS. In response to detecting the occurrence of the SEL incident in the IHS, a data recording window is retrieved from a volatile controller memory. The data recording window contains video data and serial data for a time period up to a time of detection of the SEL incident. The method further includes storing the data recording window including the video data and the serial data for the time period to a non-volatile controller memory.

Abstract: Methods, systems, and computer programs encoded on computer storage medium, for receiving a request for instrumentation data describing one or more devices in the computing environment, the request received from a resource management interface; retrieving the instrumentation data describing the one or more devices from a resource database; identifying a schema associated with the resource management interface; converting the instrumentation data describing the one or more devices based on the identified schema associated with the resource management interface; and transmitting the instrumentation data describing the one or more devices to the resource management interface.

Abstract: Methods, systems, and computer programs encoded on computer storage medium, for performing an inventory of devices to identify a particular device; creating a data structure for the particular device including data identifying the particular device; providing, a request including the data structure for the particular device; parsing the request and determining that a device class for the particular device is a new device class; in response to determining that the device class for the particular device is a new device class, creating a device-specific class for the particular device and a metaobject format for the particular device; providing the created device-specific class and the metaobject format for the particular device; and creating an instance of the device-specific class for the particular device.

Abstract: Service discovery is accomplished across a network with reduced traffic. Network devices often receive multicast discovery requests for various protocols and/or services, which increase network traffic and degrade network performance. Here, though, a server maintains a membership list for a particular protocol. The server populates the membership list with subnet devices that confirm the particular protocol. Whenever the server receives a discovery request associated with the protocol, the server need not clog its subnet with multicast requests. Instead, the server need only retrieve the membership list that is associated with the protocol. The membership list contains the subnet addresses assigned to the subnet devices that confirm the particular protocol.