Oracle Exalogic Elastic Cloud Software
 
Exalogic Elastic Cloud X5-2 Quarter Rack
 

PLA-Support>Eng Systems>Exalogic/OVCA>Oracle Exalogic>MW: Exalogic Core
 

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-9416331321>

Applies to:

Symptoms

You are applying an Exalogic Patch Set Update (PSU) to a compute node within an Exalogic rack using the exapatch utility with the Exalogic Lifecycle Toolkit (ELLC). On one of the nodes exapatch execution took much longer than expected over an hour) and eventually terminated with following message indicating patching was not successful with additional confirmation of the failure in the associated exapatch log file:

 
Following the patch application when you inspect the node the imageinfo and imagehistory commands, outputs suggest that the patch has been applied. But you see the following error from the CheckHWnFWProfile command that indicates the raid disk controller firmware was not updated as expected:

Cause

You have experienced unexpected behavior during the patch application which prevented the update of the disk controller firmware being upgraded from within the patching processes as should be expected.
 

Solution

As long as the output from other commands used to validate expected post patching state, such as imageinfo, imagehistory and CheckSWProfile look as expected and there is no evidence of anything unexpected other than the disk controller not being at the supported firmware version, then the patching can be completed by using the following steps to manually apply the firmware update to the disk controller:

1. Check output from the MegaCli64 command to see if there is a Pending Image installed to the disk controller that is waiting for a further reboot to be activated.
   
   Execute:
   
   /opt/MegaRAID/MegaCli/MegaCli64 -AdpAllInfo -a0|more
    
   Review the output for any information in the Pending Image section for entries that would illustrate that a rom has been flashed to the disk controller that would be activated by a further reboot. If such an entry exists it should be sufficient to boot the node one additional time for the firmware controller update to be fully activated. After rebooting the node review CheckHWnFWProfile output to confirm the expected firmware revision is now present.
   
   
   
2. Execute /opt/exalogic.tools/tools/CheckHWnFWProfile and look for the line containing the path to the rom:
   
   [root@elorl03cn05 ~] /opt/exalogic.tools/tools/CheckHWnFWProfile
   ...
   Supported disk controller Version: 12.12.0-0079
   Current disk controller Version : 12.12.0-0048
   Disk controller is not at the supported firmware version. It requires firmware update...
   Supported disk controller Firmware at: /opt/exalogic/firmware/disk_controller/12_12_0_0079.rom
   ...
    
   
   
3. Run /opt/exalogic.tools/tools/UpdateFirmware to manually apply the disk controller firmware update"
   
   Execute: /opt/exalogic.tools/tools/UpdateFirmware -lf <path_to_expected_disk_controller_firmware>, for example:
   
   [root@elorl03cn05 ~] /opt/exalogic.tools/tools/UpdateFirmware -lf /opt/exalogic/firmware/disk_controller/12_12_0_0079.rom
    
   
   
4. Review output from the MegaCli64 command to confirm there is now a Pending Image awaiting activation by the reboot
   
   Execute:
   
   [root@elorl03cn05 ~] /opt/MegaRAID/MegaCli/MegaCli64 -AdpAllInfo -a0|more
    
   
   
5. Reboot the compute and following the restart review output from CheckHWnFWProfile output to confirm that the expected firmware revision is now present.
   
   

References

This solution has no attachment