Article Original Creation Date: 2010-07-28
Problem
This issue is replicated by the customer's scenario below:
Will an FWU in a policy action go through/past the maximum number of attempts? If not, what kind of error is raised (SKIP, FAIL)? How can this be monitored?
Environment
Solaris 10
Oracle 10,
Weblogic 9.2 SP1
Tomcat 5.25
Solution
The maximum number of Firmware (FW) upgrade attempts setting only applies to what we call Inventory-based firmware upgrades. These are the firmware upgrades that are controlled by the OBSOLETE,VALID,RECOMMENDED,etc options on Hardware/Firmware screens. The preference for the maximum number of FW upgrade attempts does not apply to FW upgrades done via the CSR UI, or via the Firmware Upgrade Policy Action.
- The Inventory based automatic fwu is only applied in the default BOOT/Bootstrap workflow.
- The Force Upgrade option is used to perform the upgrade if the device is already at the same firmware revision that the policy action is defined to use. If the firmware revision on the device is different from the firmware that the policy is defined to use (whether it is newer or older, to allow for both upgrades and downgrades), then the Force Upgrade option is not checked.
- The query checks for whether the number of attempts is greater than or equal to the maximum defined. So the check is:
int maxAttempts = getMaxACSFirmwareUpgradeAttempts();
int attemptCount = currentCount.getAttemptCount();
if (attemptCount >= maxAttempts) {
// over the max number of attempts
return false;
} else {
// a reattempt, but still within the threshold
return true;
}
- The fail count could climb above the maximum if the upgrade path is changed. This has been corrected in SG4.1