Important GigaVUE-FM Upgrade Guidance
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 GUI or CLI. It is recommended that you plan your upgrade before performing any upgrade steps. Refer Supported Upgrade Paths for GigaVUE-FM for details on upgrade path.
Best Practice: 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 take a snapshot of GigaVUE-FM before performing a version upgrade on GigaVUE‑FM to ensure quick recovery in case of upgrade failures.
GigaVUE-FM Upgrade Guidance for GigaVUE Cloud Suite
Starting from software version 6.10.00, the Secure Communication feature in GigaVUE-FM enhances security by enabling mutual Transport Layer Security (mTLS)-based authentication across GigaVUE Fabric Components. Upon upgrading to 6.10.00, this feature will be implemented. Before upgrading GigaVUE-FM and the fabric components, ensure that the necessary ports are open as mentioned in Network Firewall Requirement for GigaVUE Cloud Suite.
Monitoring session migration steps for V Series Node 1 upgrade:
When you upgrade GigaVUE-FM with a Monitoring Session in V Series Node 1 to version 6.12 from an earlier release, follow these steps to ensure a successful migration:
| Undeploy the existing V Series Node 1 Monitoring Session. |
| Delete any Egress VXLAN TEPs with the Multi-Tunnel feature enabled. |
| Recreate the Egress VXLAN TEP with the required configuration and enable the Multi-Tunnel flag. |
| Establish a Link connection between the LB application and the Egress VXLAN TEP. |
| Deploy the Monitoring Session. |
AMX upgrade impact from version 6.13 or lower to 6.14:
Upgrading V Series Nodes with Application Metadata Exporter (AMX) from version 6.13 (or lower) to version 6.14 involves a change in the internal session data storage format. This change may result in the loss of existing control sessions during the upgrade process. To ensure a smooth upgrade and to avoid any disruption to control session data, contact Gigamon Technical Support before upgrading your AMX nodes to version 6.14.
GigaVUE-FM Upgrade Guidance for Application Intelligence
Starting from Software version 6.5.00, Application Intelligence solution can be configured from the Monitoring Session Page. You cannot create a new Application Intelligence Session or edit an Application Intelligence Session for virtual environment from the Application Intelligence page.
In the Monitoring Session page, Application Filtering can be configured either with Pass All or Advanced Rules in the fifth Rule Set. You cannot configure Application Filtering with both Pass All and Advanced Rules in the fifth Rule set. Therefore, before upgrading your GigaVUE-FM to 6.5.00, ensure that none of the existing Application Intelligence Session has Application Filtering configured with both Advanced Rules as Drop and No Rule Match Pass All in the fifth rule set. Otherwise, after upgrading to 6.5.00, you must delete that particular Application Intelligence Session to continue with your migration process.
For this reason, before upgrading to 6.5.00, you must edit the fifth rule set in the Application Filtering such that either only Advanced Rule as Drop or No Rule Match Pass All exists. Else, after upgrading to 6.5.00, you must delete that particular Application Intelligence Session to continue with your migration process. Refer to Migrate Application Intelligence Session to Monitoring Session section in the respective cloud deployment guides for more detailed information on how to migrate the existing Application Intelligence Session to the Monitoring Session page.
GigaVUE-FM Migration Guidance
GigaVUE-FM v5.8.01 introduced several significant changes that included improvements in usability and performance. These changes involved upgrading and replacing databases and changing the underlying operating system. For this reason, when upgrading from any pre-5.8.xx version of GigaVUE-FM to version 5.8.xx or above, you must first migrate your existing configurations and data such as audit logs, events, syslogs, and statistics from your current pre-5.8.xx GigaVUE-FM version to GigaVUE-FM v6.14.00.
Special migration steps and supported upgrade paths are provided under Migrate GigaVUE-FM. After GigaVUE-FM v5.10.xx, migration is no longer needed when upgrading to future versions. For supported upgrade paths requiring a special migration step, see Supported Upgrade Paths for GigaVUE-FM.
Guidance for FMHA when Encryption Mode is Certificate based Authentication
You must ensure that the following key usages are added to your PKI certificate before upgrading the FMHA:
| serverAuth (TLS Web Server Authentication) |
| clientAuth (TLS Web Client Authentication) |
| ipsecEndSystem |
| ipsecTunnel |
| ipsecUser |
Note: This is not applicable for FMHA with Pre-shared key.
To configure the certificate in FMHA, refer to Setting up Certificate (PKI) based Encryption in FMHA.
