Why did I fail to update firmware on both HA cluster nodes?
Last modified date:
2025-08-26
Applicable Products
- QuTS hero h5.3.0 or later
- High Availability Manager 1.1 or later
Root Cause
When updating firmware in a high-availability (HA) cluster, the update process may not complete successfully due to any of the following:
- Unstable network connection
If the link between the HA nodes is interrupted or delayed, synchronization may stall, preventing the update from progressing through both nodes. - Heavy I/O causing synchronization delays
If large volumes of read/write operations occur continuously during the firmware update, the system may remain in an unsynchronized state.- One node may complete the firmware update, but if the system cannot switch the active and passive roles, firmware on the other node cannot be updated.
- If synchronization exceeds the timeout period (65 minutes), the update process is stopped.
Solution
- Before starting a firmware update, verify that HA network connections are stable to avoid interruptions during the process.
- Perform firmware updates during periods of low I/O activity to minimize the risk of synchronization delays or timeouts.
- If a previous firmware update failed resulting in only one node with updated firmware, you must perform the firmware update again.
Both nodes must run identical firmware versions to maintain proper HA operation.
