Custom baseboard management controller (BMC) firmware stack monitoring system and method
An Information Handling System (IHS) includes multiple hardware devices, and a baseboard Management Controller (BMC) in communication with multiple hardware devices of the IHS. The BMC includes executable instructions for monitoring a parameter of one or more of the hardware devices when a custom BMC firmware stack is executed on the BMC. The instructions that monitor the parameter are separate and distinct from the instructions of the custom BMC firmware stack. The instructions also control the BMC to perform one or more operations to remediate an excessive parameter when the parameter exceeds a specified threshold.
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 comprising one or more processors and one or more memory units including instructions that, upon execution by the processors, are executed to:
when a custom BMC firmware stack is executed on the BMC to control a parameter of one or more of the hardware devices of the IHS, monitor the parameter by a vendor provided BMC firmware stack, wherein the instructions of the vendor provided BMC firmware stack are separate and distinct from the instructions of the custom BMC firmware stack, and wherein the custom BMC firmware stack is provided independently of the vendor; and
when the parameter exceeds a specified threshold, control, by the vendor provided BMC firmware stack, the BMC to perform one or more operations to remediate the excessive parameter.
2. The IHS of claim 1 , wherein the instructions are further executed to:
log the monitored parameter and the performed operations in a logfile, the logfile encrypted using a private key that is known to the vendor of the IHS, wherein the private key is unique to the IHS from among a plurality of the IHSs; and
transmit the encrypted logfile to the vendor.
3. The IHS of claim 2 , wherein the BMC further comprises a coprocessor that is executed to verify whether or not the instructions have been tampered with, and log the verification in the encrypted logfile at an ongoing basis.
4. The IHS of claim 1 , wherein the instructions are further executed to receive user input for selecting a type of one or more of the parameters that are to be monitored by the instructions.
5. The IHS of claim 1 , wherein the BMC comprises a bootloader that is executed to:
in response to detecting that the custom BMC firmware stack is booted on the BMC, load the instructions into a first portion of the memory units that is separate and distinct from a second portion of the memory units in which the custom BMC firmware stack is loaded.
6. The IHS of claim 5 , wherein the instructions are further executed to restrict access to the first portion of the memory units by the custom BMC firmware stack.
7. The IHS of claim 1 , wherein the instructions are further executed to remediate the excessive parameter by controlling a fan speed of one or more fans configured in the IHS.
8. The IHS of claim 1 , wherein the instructions are further executed to remediate the excessive parameter by controlling access to a memory storage component of the BMC by the custom BMC firmware stack.
9. The IHS of claim 1 , wherein the instructions are further executed to remediate the excessive parameter by locking the BIOS of the IHS in a user input mode.
10. The IHS of claim 1 , wherein the instructions are further executed to remediate the excessive parameter by writing a warning message to a shared memory location of the BMC, wherein the custom BMC firmware stack is configured to read the warning message from the shared memory location and display the warning message for view by a user.
11. A method comprising:
when a custom Baseboard Management Controller (BMC) firmware stack is executed on the BMC to control a parameter of one or more of the hardware devices of the an Information Handling System (IHS), monitoring the parameter by a vendor provided BMC firmware stack, wherein the instructions of the vendor provided BMC firmware stack are separate and distinct from the instructions of the custom BMC firmware stack, and wherein the custom BMC firmware stack is provided independently of the vendor; and
when the parameter exceeds a specified threshold, controlling, by the vendor provided BMC firmware stack, the BMC to perform one or more operations to remediate the excessive parameter.
12. The method of claim 11 , further comprising:
logging the monitored parameter and the performed operations in a logfile, the logfile encrypted using a private key that is known to the vendor of the IHS, wherein the private key is unique to the IHS from among a plurality of the IHSs; and
transmitting the encrypted logfile to the vendor.
13. The method of claim 12 , further comprising verifying, using a coprocessor, whether or not the instructions have been tampered with, and log the verification in the encrypted logfile at an ongoing basis.
14. The method of claim 11 , further comprising receiving user input for selecting a type of one or more of the parameters that are to be monitored by the instructions.
15. The method of claim 11 , further comprising in response to detecting that the custom BMC firmware stack is booted on the BMC, loading, by a bootloader, the instructions into a first portion of the memory units that is separate and distinct from a second portion of the memory units in which the custom BMC firmware stack is loaded.
16. The method of claim 15 , further comprising restricting access to the first portion of the memory units by the custom BMC firmware stack.
17. The method of claim 11 , further comprising remediating the excessive parameter by at least one of controlling a fan speed of one or more fans configured in the IHS, controlling access to a memory storage component of the BMC by the custom BMC firmware stack, locking the BIOS of the IHS in a user input mode, and writing a warning message to a shared memory location of the BMC, wherein the custom BMC firmware stack is configured to read the warning message from the shared memory location and display the warning message for view by a user.
18. A hardware memory device having program instructions stored thereon that, upon execution by a baseboard Management Controller (BMC) of an Information Handling System (IHS), cause the BMC to:
when a custom BMC firmware stack is executed on the BMC to control a parameter of one or more of the hardware devices of the IHS, monitor the parameter by a vendor provided BMC firmware stack, wherein the instructions of the vendor provided BMC firmware stack are separate and distinct from the instructions of the custom BMC firmware stack, and wherein the custom BMC firmware stack is provided independently of the vendor; and
when the parameter exceeds a specified threshold, control, by the vendor provided BMC firmware stack, the BMC to perform one or more operations to remediate the excessive parameter.
19. The hardware memory device of claim 18 , wherein the instructions are further executed to:
log the monitored parameter and the performed operations in a logfile, the logfile encrypted using a private key that is known to the vendor of the IHS, wherein the private key is unique to the IHS from among a plurality of the IHSs; and
transmit the encrypted logfile to the vendor; and
verify, using a coprocessor, whether or not the instructions have not been tampered with, and log the verification in the encrypted logfile at an ongoing basis.