High Availability Upgrade Preconditions

The following preconditions must be met for an high availability upgrade to occur:

• HAU Compatibility Key — The target image must have the same HAU Compatibility Key as the active image. To display the HAU key, use the dir command, specifying the image to display, or use the dir command image option to display all images. The HAU key field in the display specifies whether the image displayed is compatible with the current image. If “HAU compatible” is appended to the key field, a high availability upgrade can be performed between the displayed image and the current image.
• Configuration restore-points — Configuration restore-points may be set, but must not be configured. A configured restore-point would cause upgraded slots to boot with different configuration data, and all slots must be running the same configuration data.
• (7100-Series) The 7100-Series chassis are members of a Virtual Switch Bonded (VSB) system with each chassis configured for a unique HAU group.
• Upgrade Groups (S-Series) — At least two upgrade groups are required, and each group must contain at least one operational module at the start of a high availability upgrade.
• Platform (S-Series) – S-Series S4, S6, and S8 platforms require the presence of at least 2 fabric modules in the system. See the following bullet for an exception to this rule.
• Virtual Switch Bonding (VSB) (S-Series) — High availability upgrade is not allowed if the reset of any single upgrade group would break all VSB interconnect bond links. An exception to this rule:
  • High availability upgrade is allowed in a bonded system that would break either the two fabric module restriction or the all VSB interconnect links restrictions, if:
  • A single HAU group is configured per chassis
  • All chassis slots are members of that upgrade group

In this case, the upgrade is performed per physical chassis.