7100/S/N-Series Upgrade fails with "image is not High-Availability Upgrade compatible with active image" message

  • 0
  • 1
  • Article
  • Updated 4 years ago
  • (Edited)
Article ID: 16187

7100-Series, firmware and higher
S-Series, firmware and higher
N-Series DFE, firmware and higher

Have configured High Availability Upgrade default settings to always use HAU:
'set boot high-availability default-mode always'.
Attempting to perform a standard firmware upgrade because the old/new firmware have incompatible HAU keys (16129).

No firmware upgrade takes place.
The system remains running the old firmware version.
The new firmware downloads onto the switch but the system does not boot onto it.
NetSight Inventory Manager, if used, reports an error after firmware download: "Device Reported-Error (Check Device HAU Mode/Firmware Compability)".
'dir' command output shows that the new firmware has not been selected to be loaded upon next "(Boot)".
'dir' command output shows that the old firmware remains "(Active)" on the system.
Upon attempting to manually set the next boot image ('set boot system  <filename>'), the system issues CLI message "Error:  <filenameimage is not High-Availability Upgrade compatible with active image."

This set of symptoms may be observed when the old and new firmware versions have different HAU Key values so do not support the "hitless upgrade" process, yet the high-availability setting is such that only a HAU-type upgrade is permitted to occur.

The messaging represents a warning that under the current scenario no upgrade can occur.
The underlying issue is independent of whether NetSight Inventory Manager - or some other automated or manual tool - is used to perform the upgrade.

Functions as Designed (FAD).

If it is desired that HAU upgrades occur where supported but standard upgrades occur where HAU is not supported, then change the default "never" option to instead specify "if-possible" rather than "always":
'set boot high-availability default-mode if-possible'.

Note: Since the default-mode setting only comes into play when the 'set boot system  <filename>' command has been issued without the overriding "high-availability" or "standard" option (true for automated upgrades, and optionally for manual upgrades), an alternate solution which applies to only the current manual upgrade operation is to issue a longer form of the 'set boot system' command in order to reinforce the goal of a standard upgrade:
'set boot system  <filenamestandard'
'Do you want to reset now (y/n) [n]?y'
Photo of FAQ User

FAQ User, Official Rep

  • 13,590 Points 10k badge 2x thumb

Posted 4 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.