GigaVUE-FM Upgrade
To upgrade GigaVUE-FM, the recommended procedure is to back up your current configuration and perform the pre-upgrade checks (memory requirements, the maximum number of images) before installing the image. You can upgrade via the GigaVUE-FM UI or GigaVUE-OS CLI. It is recommended that you plan your upgrade before performing any upgrade steps.
Rules and Notes
| IMPORTANT: Intent-Based Orchestration (IBO) Policies are removed when upgrading from any pre-5.11 version of GigaVUE-FM to version 5.11.00 or above. IBO Policies will need to be recreated after upgrading to 5.11.00 or above. (Ref: FM-33169) |
| BEST PRACTICES: |
| Before performing an upgrade, in addition to taking a backup of GigaVUE-FM, also take a Sysdump, which provides valuable configuration information that is not captured in the backup. You can use the Sysdump after the upgrade to troubleshoot any upgrade-related issues with your configurations. |
| 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 “Upgrade Software on a GigaVUE Node or a Cluster from GigaVUE-FM” in the GigaVUE-FM User’s Guide. |
| If upgrading from GigaVUE-FM versions lower than 5.8.xx to 5.10.xx : If you are upgrading from a version lower than 5.8.xx to 5.10.xx refer to the GigaVUE-FM Migration instructions in version 5.10 of the Online Documentation Library for details. |
| 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 this document for details. |
| For upgrades to versions 5.11.xx and 5.12.xx, a password change is mandated. |
| For all other versions, the password change is mandated only if the current password is a default password. |
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:
| 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: |
| UCT-V Controller |
| UCT-V's |
| GigaVUE V Series Node |
| GigaVUE V Series Proxy |
| When GigaVUE‑FM manages GigaVUE Cloud Suite components (UCT‑V Controller, UCT‑V, GigaVUE V Series Node, and GigaVUE V Series Proxy), you must keep these components within two releases (N+2) of the GigaVUE‑FM release. Upgrade the components at each GigaVUE‑FM hop before starting the next GigaVUE‑FM upgrade. For example, when upgrading GigaVUE‑FM from 6.1.xx to 6.3.xx, upgrade all Cloud components to 6.3.xx before upgrading GigaVUE‑FM to 6.5.xx. |
Table 1: GigaVUE‑FM Upgrade Summary Table
|
To upgrade to 6.14.xx from... |
Use the recommended upgrade path for GigaVUE‑FM |
|---|---|
|
v6.13.xx |
6.13.00 ► 6.14.xx |
|
v6.12.xx (LTS) |
6.12.xx ►6.14.xx |
|
v6.11.xx |
6.11.xx► 6.12.xx ►6.14.xx |
|
v6.10.xx |
*6.10.02 ► 6.12.xx ► 6.14.xx |
|
v6.9.xx |
6.9.xx►*6.10.02 ► 6.12.xx ► 6.14.xx |
|
v6.8.xx |
6.8.xx►*6.10.02 ►6.12.xx►6.14.xx |
|
v6.7.xx |
6.7.xx►6.8.xx ►*6.10.02 ►6.12.xx ► 6.14.xx |
|
v6.6.xx |
6.6.xx►6.8.xx ►*6.10.02 ► 6.12.xx ► 6.14.xx |
|
v6.5.xx |
6.5.xx ►6.7.xx ► 6.8.xx ►*6.10.02 ► 6.12.xx ► 6.14.xx |
|
v6.4.xx |
6.4.xx ►6.6.xx ►6.8.xx ►*6.10.02 ► 6.12.xx ► 6.14.xx |
|
v6.3.xx |
6.3.xx►6.5.xx►6.7.xx ► 6.8.xx ►*6.10.02 ► 6.12.xx ► 6.14.xx |
|
v6.2.xx |
6.2.00►6.4.xx►6.6.xx ► 6.8.xx►*6.10.02 ► 6.12.xx ► 6.14.xx |
|
v6.1.xx |
6.1.xx►6.3.xx ►6.5.xx ► 6.7.xx ► 6.8.xx ►*6.10.02 ► 6.12.xx ► 6.14.xx |
|
Note:
|
| 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. |
Important Document References
This section lists all information sections that you may require to refer to while updating your device to the 6.13.00 software release.
|
System and Support Requirements |
Refer To |
|---|---|
|
System Requirements |
|
|
Firmware/BIOS information for the GigaVUE-FM Hardware Appliance |
|
|
VMware Requirements for GigaVUE-FM Installation |
|
|
Minimum Virtual Computing Requirements for GigaVUE-FM Installation |
|
|
GigaVUE Cloud Suite System Requirements
|
|
|
Nutanix Requirements |
|
|
OpenStack Requirements |
|
|
Oracle Cloud Infrastructure Requirements |
|
|
OVS-Mirror Requirements |
|
|
Supported Hypervisors for GigaVUE V Series Node |
|
|
Supported Operating Systems for UCT-V |
|
|
Kernel and CPU Requirements for UCT-C |
Kernel and CPU Requirements for Universal Cloud Tap - Container |
|
Supported Platforms for UCT-C |
|
|
Support and Compatibility |
|
|
GigaVUE-FM and GigaVUE-OS Compatibility |
|
|
Supported Browsers for GigaVUE-FM |
|
|
Line Card or Module Removal Procedure (Hot Removal) |
|
