Multiple RAC Firmware Update System for Rebootless IHS Maintenance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional firmware update methods for Information Handling Systems (IHS) often require downtime and rebooting, which is not customer-friendly and can lead to missed security fixes and performance improvements, especially when multiple RACs are involved and memory constraints are present, potentially causing firmware devices to become bricked during updates.
Innovation Solution
Implementing a multiple RAC-based firmware update system where the first RAC receives a firmware update image and issues a command to the firmware device to request updates from both RACs, ensuring seamless transfer and completion even if one RAC fails, using the Platform Level Data Model (PLDM) specification to manage the update process without rebooting the IHS.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional firmware update methods are used, then firmware can be updated, but the IHS experiences downtime and requires rebooting
Solution Approach 1:
The system divides the RAC functionality into primary and secondary roles, allowing the primary RAC to handle firmware updates while the secondary RAC maintains system operations. This segmentation enables continuous operation during firmware updates by separating update management from system operation responsibilities.
Solution Approach 2:
The system performs preliminary actions by having the primary RAC receive and validate the firmware update image before the actual update is applied. The secondary RAC is prepared in advance to take over if needed, ensuring that updates can be initiated without causing system downtime or requiring reboots.
2Device complexity
If firmware updates are applied to a single RAC, then the update process is simple, but the risk of bricking the firmware device increases
Solution Approach 1:
The system implements beforehand cushioning by maintaining a secondary RAC that can serve as a backup during firmware updates. If the primary RAC fails during the update process, the secondary RAC can take over and complete the update, preventing the firmware device from becoming bricked and ensuring update reliability.
3Quantity of substance
If memory constraints are present during firmware updates, then resource usage is optimized, but the risk of update failure increases
Solution Approach 1:
The system merges the resources of the primary and secondary RACs to handle firmware updates. The secondary RAC can be utilized to store or process firmware images when the primary RAC encounters memory constraints, effectively combining available memory resources to prevent update failures while maintaining optimized resource usage.
Data Source
AI summary
Embodiments of systems and methods to provide a firmware update to devices configured in a redundant configuration in an Information Handling System (IHS) are disclosed. In an illustrative, non-limiting embodiment, an IHS may include first and second Remote Access Controllers (RACs) that each includes computer-executable instructions to receive, by the first RAC, a firmware update image associated with the device in which the firmware update image conforms to a PLDM specification. The first RAC may then, issue a command to the firmware device indicating that the firmware device is to request a firmware update from the first RAC in which the command includes information about the second RAC. The information indicates the ability of the second RAC to complete a transfer of the firmware update image when the first RAC partially completes the transfer of the firmware update image.