Redundant Firmware Failover for Continuous Service Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Firmware updates in data processing systems typically require rebooting, leading to service disruptions, which is unacceptable in high availability systems and business-critical transactions.
Innovation Solution
A method that updates firmware in a redundant configuration, allowing a fail-over from a primary to a backup firmware component, enabling continuous service without disruption by installing and activating the updated firmware in a backup component while maintaining service availability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If firmware is updated by rebooting the data processing system, then the firmware update is completed, but service disruption occurs
Solution Approach 1:
The system is divided into multiple firmware components (first firmware component and second firmware component) that can operate independently. This segmentation allows one component to be updated while the other continues to provide service, resolving the contradiction between completing firmware updates and maintaining service availability.
Solution Approach 2:
The updated firmware code is installed in the second firmware component before the first firmware component is updated. This preliminary action ensures that a functional firmware version is already in place, allowing seamless fail-over and preventing service disruption when the primary component is updated.
2Productivity
If firmware is updated without rebooting, then service availability is maintained, but the update process becomes complex
Solution Approach 1:
The system changes the operational state parameters of firmware components by introducing active and inactive states. This allows the update process to modify firmware in an inactive state while the active component continues servicing, maintaining service availability without excessive complexity.
Solution Approach 2:
A fail-over mechanism acts as an intermediary between firmware updates and service continuity. This mediator automatically switches service from the first firmware component to the second firmware component when needed, simplifying the update process while maintaining service availability.
3Reliability
If redundant firmware configuration is implemented, then service continuity is ensured during updates, but system complexity increases
Solution Approach 1:
The system creates a copy of the firmware component (second firmware component as backup of first firmware component). This copying approach ensures service continuity during updates while keeping the redundancy mechanism simple and manageable through automated fail-over logic.
Data Source
AI summary
A method, system, and computer usable program product for updating firmware without disrupting service are provided in the illustrative embodiments. An updated firmware code is sent to a first firmware component and a second firmware component. The first firmware component is a primary firmware component and the second firmware component is a backup firmware component in a redundant firmware configuration. The updated firmware code is installed in second firmware component. The updated firmware code is activated in a third firmware component. The third firmware component is in communication with the first firmware component. A fail-over from the first firmware component to the second firmware component is performed such that a user communicating with the data processing system and receiving a service using the first firmware component continues to receive the service using the second firmware component without a disruption in the service.