Supported Upgrade Paths for GigaVUE-FM

Supported upgrade paths for GigaVUE‑FM 6.1.xx and later:

You can upgrade your GigaVUE‑FM instance to any of the subsequent two versions. To upgrade your GigaVUE‑FM from 6.1.xx to later versions, the supported upgrade paths are:

IMPORTANT:
■   When you are upgrading to 6.13, you must upgrade all fabric components within 30 days of upgrading GigaVUE‑FM to ensure version compatibility before the next UCT-V certificate renewal. Complete the following upgrades immediately after the GigaVUE‑FM upgrade to ensure that UCT‑V certificates renew only after all components are running compatible versions, reducing the risk of registration or communication failures:
o   UCT-V Controller
o   UCT-V's
o   GigaVUE V Series Node
o   GigaVUE V Series Proxy
■   When GigaVUE‑FM is managing GigaVUE Cloud Suite components (UCT‑V Controller, UCT‑V, GigaVUE V Series Node, and GigaVUE V Series Proxy), you must keep the versions of these components within two minor releases (N–2) of the GigaVUE‑FM release. For example, GigaVUE‑FM 6.12.xx does not support managing or upgrading Cloud components that remain on 6.9.xx.

6.1.xx > 6.3.xx > 6.5.xx > 6.7.xx > 6.8.xx > *6.10.02 > 6.12.xx > 6.13.xx

6.2.xx > 6.4.xx > 6.6.xx > 6.8.xx > *6.10.02 > 6.12.xx > 6.13.xx

6.3.xx > 6.5.xx > 6.7.xx > 6.8.xx > *6.10.02 > 6.12.xx > 6.13.xx

6.4.xx > 6.6.xx > 6.8.xx > *6.10.02 > 6.12.xx > 6.13.xx

6.5.xx > 6.7.xx > 6.8.xx > *6.10.02 > 6.12.xx > 6.13.xx

6.6.xx > 6.8.xx > *6.10.02 > 6.12.xx > 6.13.xx

6.7.xx > 6.8.xx > *6.10.02 > 6.12.xx > 6.13.xx

6.8.xx > *6.10.02 > 6.12.xx > 6.13.xx

6.9.xx > *6.10.02 > 6.12.xx > 6.13.xx

*MongoDB changes were introduced in 6.10.02. You must upgrade to 6.10.02 before moving to 6.11.xx or later.

IMPORTANT:
■  To prevent upgrades outside the supported paths, which may cause GigaVUE‑FM to corrupt, a prevention mechanism has been introduced in GigaVUE‑FM version 6.12. Starting from GigaVUE‑FM version 6.12, any unsupported upgrade attempt is blocked and marked as failed. Review the FMCTL log (/var/log.fm-ctl.log) for details on the failure.
■  For versions prior to 6.12, unsupported upgrade paths are not automatically blocked. You must follow the correct upgrade sequence mentioned above. If you fail to follow, it may cause GigaVUE‑FM to corrupt or lockup.

  • Best Practice: Always upgrade your GigaVUE-FM instance before upgrading the GigaVUE-OS nodes. You can upgrade the attached nodes from the device or from GigaVUE-FM. The latter is recommended. Refer to “Upgrading Software on a GigaVUE Node or a Cluster from GigaVUE-FM” in the GigaVUE Fabric Management Guide.

  • If upgrading from GigaVUE-FM versions lower than 5.10.xx: You cannot directly upgrade your GigaVUE-FM instance to release 5.10.00 from a release prior to 5.8.xx. If your current version of GigaVUE‑FM is 5.7.xx or lower and you want to upgrade to software version 6.13.xx, you must first migrate to GigaVUE‑FM 5.10.xx and then upgrade to 5.11.xx.

    Note:  For instructions on how to migrate refer to Migrate GigaVUE-FM in GigaVUE 5.10 Documentation.

  • If upgrading from GigaVUE-FM versions lower than 5.5.00: While upgrading from any version lower than 5.5.00, an association of more than one VPort to the same GigaSMART group needs to be removed for any existing GTP GigaSMART operation.

  • If upgrading from GigaVUE-FM versions lower than 5.4.00: Be aware of the minimum memory requirement changes between releases. Earlier releases specified 4GB of memory for the OVA template; whereas versions after 5.4.00 require 8GB and versions after 5.7.00 require 16GB. If the existing virtual or physical hardware running GigaVUE-FM is configured with less memory than required, then increase the amount of memory available to the GigaVUE-FM machine. Refer to GigaVUE-FM Memory and CPU Requirements in the GigaVUE Release Notes for additional details.