System and method for secure management of non-registered components of an information handling system using a baseboard management controller
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.
1. An Information Handling System (IHS), comprising:
a plurality of hardware devices; and
a Baseboard Management Controller (BMC) in communication with the plurality of hardware devices, the BMC including:
a baseboard processor; and
baseboard memory including baseboard instructions that, upon execution by the baseboard processor, cause the BMC to:
receive a message associated with a non-registered hardware device that is not registered to be managed by the BMC, wherein hardware device data for the non-registered device does not exist in the IHS, the message formatted according to a native protocol of the BMC; <transmit the message to a device plugin associated with the non-registered hardware device, wherein 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;
forward the converted message to the non-registered hardware device using the protocol of the non-registered hardware device;
obtain configuration information from the device plugin, the configuration information comprising one or more telemetry parameters to be obtained from the non-registered hardware device; and
generate telemetry reports associated with the non-registered hardware device using the configuration information stored in the device plugin.
2. The IHS of claim 1 , wherein the instructions further cause the BMC to transmit the message to the device plugin using a secure Hypertext Transfer Protocol (HTTP), version 2 channel.
3. The IHS of claim 2 , wherein the instructions further cause the BMC to secure the HTTP, version 2 channel using a CSRF (cross site request forgery) token.
4. The IHS of claim 2 , wherein the device plugin is restricted to only acting on the message when received through the HTTP, version 2 channel.
5. The IHS of claim 1 , wherein the device plugin comprises an applications program interface (API) of a BMC service module executed on the IHS.
6. The IHS of claim 1 , wherein the baseboard instructions further cause the BMC to:
determine that the non-registered hardware device is not enrolled for use with the BMC;
enroll the non-registered hardware device for use with the BMC by storing information associated with the non-registered hardware device in the baseboard memory; and
remotely manage the non-registered hardware device by generating the message through a RESTful interface.
7. The IHS of claim 6 , wherein the baseboard instructions further cause the BMC to:
determine that the received message comprises an industry standards organization modeled action, the industry standards organization associated with a RESTful interface from which the received message has been obtained;
determine that the message is not enrolled for use by the first non-registered hardware device;
enroll the message for use with the non-registered hardware device; and
remotely manage the non-registered hardware device by generating the enrolled message through the RESTful interface.
8. The IHS of claim 1 , wherein the baseboard instructions further cause the BMC to:
receive one or more event messages from the non-registered hardware device;
store the one or more event messages in the baseboard memory; and
transmit the one or more event messages to a RESTful interface in communication with the BMC in response to a request received from the RESTful interface.
9. The IHS of claim 8 , wherein the baseboard instructions further cause the BMC to control a periodicity of how often the one or more messages are stored in the baseboard memory.
10. The IHS of claim 8 , wherein the event messages comprise information associated with one or more parameters of the non-registered hardware device, and wherein the baseboard instructions further cause the BMC to determine a subset of the one or more parameters to be monitored by the BMC, and store the information associated with subset of parameters in the baseboard memory.
11. A method comprising:
receiving, using instructions stored in at least one memory and executed by at least one processor, a message associated with a non-registered hardware device that is not registered to be managed by a Baseboard Management Controller (BMC), wherein hardware device data for the non-registered device does not exist in an Information Handling System (HIS) (IHS) in which the non-registered hardware device is configured, the message formatted according to a native protocol of the BMC, the BMC in communication with a plurality of hardware devices comprising the non-registered hardware device; and
transmitting, using the instructions, the message to a device plugin associated with the non-registered hardware device, wherein the device plugin comprises:
converting, using the instructions, the message into a protocol associated with the non-registered hardware device;
forwarding, using the instructions, the converted message to the non-registered hardware device using the protocol of the non-registered hardware device;
obtaining configuration information from the device plugin, the configuration information comprising one or more telemetry parameters to be obtained from the non-registered hardware device; and
generating, using the instructions, telemetry reports associated with the non-registered hardware device using the configuration information stored in the device plugin.
12. The method of claim 11 , further comprising:
determining that the non-registered hardware device is not enrolled for use with the BMC;
enrolling the non-registered hardware device for use with the BMC by storing information associated with the non-registered hardware device in the baseboard memory; and
remotely managing the non-registered hardware device by generating the message through a RESTful interface.
13. The method of claim 12 , further comprising:
determining that the received message comprises an industry standards organization modeled action, the industry standards organization associated with a RESTful interface from which the received message has been obtained;
determining that the message is not enrolled for use by the first non-registered hardware device;
enrolling the message for use with the non-registered hardware device; and
remotely managing the non-registered hardware device by generating the enrolled message through the RESTful interface.
14. The method of claim 11 , further comprising:
receiving one or more event messages from the non-registered hardware device;
storing the one or more event messages in the baseboard memory; and
transmitting the one or more event messages to a RESTful interface in communication with the BMC in response to a request received from the RESTful interface.
15. The method of claim 14 , further comprising controlling a periodicity of how often the one or more messages are stored in the baseboard memory.
16. The method of claim 14 , wherein the event messages comprise information associated with one or more parameters of the non-registered hardware device, wherein the method further comprises determining a subset of the one or more parameters to be monitored by the BMC, and storing the information associated with the subset of parameters in the baseboard memory.
17. One or more computer-readable storage devices having instructions stored thereon for providing remote management of an IHS (Information Handling System), wherein execution of the instructions by one or more processors of the IHS causes the one or more processors to:
receive a message associated with a non-registered hardware device that is not registered to be managed by a Baseboard Management Controller (BMC), wherein hardware device data for the non-registered device does not exist in the IHS, the message formatted according to a native protocol of the BMC, the BMC in communication with a plurality of hardware devices comprising the non-registered hardware device; and
transmit the message to a device plugin associated with the non-registered hardware device, wherein 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;
forward the converted message to the non-registered hardware device using the protocol of the non-registered hardware device;
obtain configuration information from the device plugin, the configuration information comprising one or more telemetry parameters to be obtained from the non-registered hardware device; and
generate telemetry reports associated with the non-registered hardware device using the configuration information stored in the device plugin.
18. The storage devices of claim 17 , wherein the instructions further cause the BMC to:
determine that the non-registered hardware device is not enrolled for use with the BMC;
enroll the non-registered hardware device for use with the BMC by storing information associated with the non-registered hardware device in the baseboard memory; and
remotely manage the non-registered hardware device by generating the message through a RESTful interface.
19. The storage devices of claim 18 , wherein the instructions further cause the BMC to:
determine that the received message comprises an industry standards organization modeled action, the industry standards organization associated with a RESTful interface from which the received message has been obtained;
determine that the message is not enrolled for use by the first non-registered hardware device;
enroll the message for use with the non-registered hardware device; and
remotely manage the non-registered hardware device by generating the enrolled message through the RESTful interface.
20. The storage devices of claim 17 , wherein the instructions further cause the BMC to:
receive one or more event messages from the non-registered hardware device;
store the one or more event messages in the baseboard memory; and
transmit the one or more event messages to a RESTful interface in communication with the BMC in response to a request received from the RESTful interface.