Updating firmware without disrupting service

• US 8,856,776 B2
• Filed: 02/05/2009
• Issued: 10/07/2014
• Est. Priority Date: 02/05/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Mahajan, Ajay Kumar, Patel, Atit D
• Primary Examiner(s): Zhen, Li B
• Assistant Examiner(s): MACASIANO, JOANNE GONZALES
• Application Number:
  US12/366,175
• Publication Number:
  US 20100199272A1
• Time in Patent Office: 2,070 Days
• Field of Search: 717/168, 717/171
• US Class Current: 717/173
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 8/656 while running

Abstract

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.

Claims

1. A computer implemented method for updating firmware without disrupting service in a data processing system, the computer implemented method comprising:

sending, from a source, an updated firmware code to a first firmware component and a second firmware component, the first firmware component being a primary firmware component and the second firmware component being a backup firmware component in a redundant firmware configuration in the data processing system where an application is executing using a processor;

installing the updated firmware code in the second firmware component;

sending, from the first firmware component, the updated firmware code to a third firmware component;

activating the updated firmware code in the third firmware component, the third firmware component being in communication with the first firmware component, and the third firmware component not being a redundant firmware component for the first firmware component;

performing a fail-over from the first firmware component to the second firmware component 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, wherein performing the fail-over results in a fourth firmware component detecting a change in a code of the second firmware component and the fourth firmware component failing over to the third firmware component, and wherein the processor in the data processing system continues to execute the application without disruption during the fail-over from the first firmware component to the second firmware component in the data processing system;

detecting, at a fourth firmware component, that the first firmware component includes the updated firmware code, the fourth and the first firmware components being in communication with each other;

requesting, at the fourth firmware component and responsive to the detecting, the updated firmware code from the first firmware component; and

rebooting the fourth firmware component with the updated firmware code.

2. The computer implemented method of claim 1, wherein activating the updated firmware code in the third firmware component further comprises:

installing the updated firmware code in the third firmware component; and

booting up the third firmware component with the updated firmware code.

3. The computer implemented method of claim 1, wherein the first firmware component is a primary service controller, the second firmware component is a backup service controller, and wherein the computer implemented method further comprises:

queuing an instruction directed at the first firmware component; and

processing, following performing the fail-over, the instruction at the second firmware component.

4. The computer implemented method of claim 1, further comprising:

taking a snapshot of a plurality of firmware components active in a network supported by the first and the second firmware components, the plurality of firmware components including a plurality of node controllers; and

verifying, following performing the fail-over, that the plurality of firmware components are active in the network and communicating with the second firmware component.

5. A computer usable program product comprising a computer-usable storage device including computer usable code for updating firmware without disrupting service in a data processing system, the computer usable code comprising:

computer usable code for sending, from a source, an updated firmware code to a first firmware component and a second firmware component, the first firmware component being a primary firmware component and the second firmware component being a backup firmware component in a redundant firmware configuration in the data processing system where an application is executing using a processor;

computer usable code for installing the updated firmware code in the second firmware component;

computer usable code for sending, from the first firmware component, the updated firmware code to a third firmware component;

computer usable code for activating the updated firmware code in the third firmware component, the third firmware component being in communication with the first firmware component, and the third firmware component not being a redundant firmware component for the first firmware component;

computer usable code for performing a fail-over from the first firmware component to the second firmware component 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, wherein performing the fail-over results in a fourth firmware component detecting a change in a code of the second firmware component and the fourth firmware component failing over to the third firmware component, and wherein the processor in the data processing system continues to execute the application without disruption during the fail-over from the first firmware component to the second firmware component in the data processing system;

computer usable code for detecting, at a fourth firmware component, that the first firmware component includes the updated firmware code, the fourth and the first firmware components being in communication with each other;

computer usable code for requesting, at the fourth firmware component and responsive to the detecting, the updated firmware code from the first firmware component; and

computer usable code for rebooting the fourth firmware component with the updated firmware code.

6. The computer usable program product of claim 5, wherein the computer usable code for activating the updated firmware code in the third firmware component further comprises:

computer usable code for installing the updated firmware code in the third firmware component; and

computer usable code for booting up the third firmware component with the updated firmware code.

7. The computer usable program product of claim 5, wherein the first firmware component is a primary service controller, the second firmware component is a backup service controller, and wherein the computer usable program product further comprises:

computer usable code for queuing an instruction directed at the first firmware component; and

computer usable code for processing, following performing the fail-over, the instruction at the second firmware component.

8. The computer usable program product of claim 5, further comprising:

computer usable code for taking a snapshot of a plurality of firmware components active in a network supported by the first and the second firmware components, the plurality of firmware components including a plurality of node controllers; and

computer usable code for verifying, following performing the fail-over, that the plurality of firmware components are active in the network and communicating with the second firmware component.

9. The computer program product of claim 5, wherein the computer usable code is stored in a computer readable storage medium in a data processing system, and wherein the computer usable code is transferred over a network from a remote data processing system.

10. The computer program product of claim 5, wherein the computer usable code is stored in a computer readable storage medium in a server data processing system, and wherein the computer usable code is downloaded over a network to a remote data processing system for use in a computer readable storage medium associated with the remote data processing system.

11. A data processing system for updating firmware without disrupting service in a data processing system, the data processing system comprising:

a storage device including a storage medium, wherein the storage device stores computer usable program code; and

a processor, wherein the processor executes the computer usable program code, and wherein the computer usable program code comprises;

computer usable code for sending, from a source, an updated firmware code to a first firmware component and a second firmware component, the first firmware component being a primary firmware component and the second firmware component being a backup firmware component in a redundant firmware configuration in the data processing system where an application is executing using the processor;

computer usable code for installing the updated firmware code in the second firmware component;

computer usable code for sending, from the first firmware component, the updated firmware code to a third firmware component;

computer usable code for activating the updated firmware code in the third firmware component, the third firmware component being in communication with the first firmware component, and the third firmware component not being a redundant firmware component for the first firmware component;

computer usable code for performing a fail-over from the first firmware component to the second firmware component 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, wherein performing the fail-over results in a fourth firmware component detecting a change in a code of the second firmware component and the fourth firmware component failing over to the third firmware component, and wherein the processor in the data processing system continues to execute the application without disruption during the fail-over from the first firmware component to the second firmware component in the data processing system;

computer usable code for detecting, at a fourth firmware component, that the first firmware component includes the updated firmware code, the fourth and the first firmware components being in communication with each other;

computer usable code for requesting, at the fourth firmware component and responsive to the detecting, the updated firmware code from the first firmware component; and

computer usable code for rebooting the fourth firmware component with the updated firmware code.

12. The data processing system of claim 11, wherein the computer usable code for activating the updated firmware code in the third firmware component further comprises:

computer usable code for installing the updated firmware code in the third firmware component; and

computer usable code for booting up the third firmware component with the updated firmware code.

13. The data processing system of claim 11, wherein the first firmware component is a primary service controller, the second firmware component is a backup service controller, and wherein the data processing system further comprises:

computer usable code for queuing an instruction directed at the first firmware component; and

computer usable code for processing, following performing the fail-over, the instruction at the second firmware component.

14. The data processing system of claim 11, further comprising:

computer usable code for taking a snapshot of a plurality of firmware components active in a network supported by the first and the second firmware components, the plurality of firmware components including a plurality of node controllers; and

computer usable code for verifying, following performing the fail-over, that the plurality of firmware components are active in the network and communicating with the second firmware component.