Migrate GigaVUE-FM

This section provides information about migrating your GigaVUE-FM to the latest version. Refer to the following sections for details:

GigaVUE-FM migration is supported only on VMware ESXi, GigaVUE-FM Hardware Appliance, and AWS platforms.

Migration Overview

Starting with release 5.8.00, GigaVUE-FM introduces several significant changes, which include improvements in usability and performance. These changes include upgrading and replacing databases and changing the underlying operating system. So, you must migrate your existing configurations and data such as audit logs, events, syslogs, and statistics from your current GigaVUE-FM version (either 5.7 or lower) to the latest version of GigaVUE-FM. You cannot directly upgrade your GigaVUE-FM instance to the latest version. You must first upgrade to a special migration version that provides the tools to manage and perform the migration. You can then upgrade to the latest version of GigaVUE-FM. Refer to Supported GigaVUE-FM Migration and Upgrade Paths.

Plan Your Migration

This section will help you plan your migration. It provides details about the scope of the migration, the best migration method to use for your deployment, and how to complete the migration process.

Refer to the following sections for details:

 

S.No

Purpose

Refer to:

1.

Ensure that you meet the migration requirements and also, keep in mind the limitations before starting the migration process.

Migration—Rules and Notes

2.

Determine the migration and upgrade path.

Supported GigaVUE-FM Migration and Upgrade Paths

3.

Complete the migration process.

GigaVUE-FM Migration on VMware
GigaVUE-FM Migration on Hardware Appliance
GigaVUE-FM Migration on AWS

Migration—Rules and Notes

Keep in mind the following rules and notes before you proceed with migration:

Migration to the latest version of GigaVUE-FM is supported only on VMware ESXi, GigaVUE-FM Hardware Appliance, and AWS platforms.
Undocumented environments are not supported for migration.
The minimum size of hard disk for VMware, AWS, and GigaVUE-FM Hardware Appliance is 40Gb.
Ensure that you plan for a maintenance window depending on the size of the data that you plan to migrate and the network latency.

Following table provides a guideline for the maintenance window that you can refer to when you plan for migration:

Note that the actual migration time may vary depending on your configurations.

Data Set

Statistics Loss Time

Management Loss Time

Estimated Migration Time

Environment 1

No.of nodes

2

10 minutes

5 minutes

2 hours (for 25 days of data)
35 minutes (for 7 days of data)

No.of Ports

6

No.of Maps

6

No.of Events

1000

No.of Syslogs

1000

No.of Audit logs

1000

Environment 2

No.of nodes

40

1 hour

5 minutes

8 hours (for 25 days of data)
4 hours (for 7 days of data)

No.of Ports

2000

No.of Maps

1000

No.of Events

10000

No.of Syslogs

10000

No.of Audit logs

10000

Environment 3

No.of nodes

300

3 hours

5 minutes

10 hours (for 7 days of data)

No.of Ports

12000

No.of Maps

6000

No.of Events

10000

No.of Syslogs

10000

No.of Audit logs

10000

The custom SSL certificates and private keys will not be migrated. You must upload them manually. For instructions, refer to Install Third-Party Certificate.
Any configurations that you have set up using DHCP will not be migrated.
If you have associated the IP address of your current version of GigaVUE-FM to the IP interface, after the migration is completed, you must manually associate the IP address of the new GigaVUE-FM to the IP interface.
It is recommended to upgrade GigaVUE-FM using the local admin credentials and set the First Priority field under the Authentication Priority section to Local. Refer to the "Configure AAA Authentication Options" section in the GigaVUE Administration Guide.

Supported GigaVUE-FM Migration and Upgrade Paths

Use the following table to determine the supported migration and upgrade path for your current version of GigaVUE-FM:

From GigaVUE-FM Version

To
GigaVUE-FM Version

Special Migration Version of GigaVUE-FM

Supported Upgrade Path

5.9.xx

5.10.xx

N/A

5.9.xx > 5.10.xx

5.8.xx

5.10.xx

N/A

5.8.xx > 5.10.xx

5.8.xx

5.9.xx

N/A

5.8.xx > 5.9.xx

5.7.xx

5.10.xx

5.7.02.21

5.7.xx > 5.7.02.21 > 5.10.xx

5.7.xx

5.9.01

5.7.02.12

5.7.xx > 5.7.02.12 > 5.9.01

5.7.xx

5.9.00

5.7.02.11

5.7.xx > 5.7.02.11 > 5.9.00

5.7.xx

5.8.01

5.7.02.01

5.7.xx > 5.7.02.01 > 5.8.01

5.7.xx

5.8.00

5.7.01.01

5.7.xx > 5.7.01.01 > 5.8.00

5.6.xx

5.10.xx

5.7.02.21

5.6.xx > 5.7.02.21 > 5.10.xx

5.6.xx

5.9.01

5.7.02.12

5.6.xx > 5.7.02.12 > 5.9.01

5.6.xx

5.9.00

5.7.02.11

5.6.xx > 5.7.02.11 > 5.9.00

5.6.xx

5.8.01

5.7.02.01

5.6.xx > 5.7.02.01 > 5.8.01

5.6.xx

5.8.00

5.7.01.01

5.6.xx > 5.7.01.01 > 5.8.00

5.5.xx

5.10.xx

5.7.02.21

5.5.xx > 5.6.01 > 5.7.02.21 > 5.10.xx

-or-

5.5.xx > 5.7.02 > 5.7.02.21 > 5.10.xx

5.5.xx

5.9.01

5.7.02.12

5.5.xx > 5.6.01 > 5.7.02.12 > 5.9.01

-or-

5.5.xx > 5.7.02 > 5.7.02.12 > 5.9.01

5.5.xx

5.9.00

5.7.02.11

5.5.xx > 5.6.01 > 5.7.02.11 > 5.9.00

-or-

5.5.xx > 5.7.02 > 5.7.02.11 > 5.9.00

5.5.xx

5.8.01

5.7.02.01

5.5.xx > 5.6.01 > 5.7.02.01 > 5.8.01

-or-

5.5.xx > 5.7.02 > 5.7.02.01 > 5.8.01

5.5.xx

5.8.00

5.7.01.01

5.5.xx > 5.6.01 > 5.7.01.01 > 5.8.00

-or-

5.5.xx > 5.7.02 > 5.7.01.01 > 5.8.00

5.4.xx

5.10.xx

5.7.02.21

5.4.xx > 5.6.01 > 5.7.02.21 > 5.10.xx

-or-

5.4.xx > 5.7.02 > 5.7.02.21 > 5.10.xx

5.4.xx

5.9.01

5.7.02.12

5.4.xx > 5.6.01 > 5.7.02.12 > 5.9.01

-or-

5.4.xx > 5.7.02 > 5.7.02.12 > 5.9.01

5.4.xx

5.9.00

5.7.02.11

5.4.xx > 5.6.01 > 5.7.02.11 > 5.9.00

-or-

5.4.xx > 5.7.02 > 5.7.02.11 > 5.9.00

5.4.xx

5.8.01

5.7.02.01

5.4.xx > 5.6.01 > 5.7.02.01 > 5.8.01

-or-

5.4.xx > 5.7.02 > 5.7.02.01 > 5.8.01

5.4.xx

5.8.00

5.7.01.01

5.4.xx > 5.6.01 > 5.7.01.01 > 5.8.00

-or-

5.4.xx > 5.7.02 > 5.7.01.01 > 5.8.00

Note:  For deployments with GigaVUE-FM 5.3.xx or lower, upgrade to GigaVUE-FM 5.4.xx and then follow the upgrade path listed in the above table to migrate to the latest version of GigaVUE-FM. Refer to the “Installation and Upgrade” section in the GigaVUE-FM and GigaVUE-VM User’s Guide of the respective versions.

GigaVUE-FM Migration on VMware

Use this option if your current instance of GigaVUE-FM is running on VMware ESXi. Migrating using this option minimizes the downtime and the loss of statistical data. For details about the supported special migration version, refer to Supported GigaVUE-FM Migration and Upgrade Paths.

GigaVUE-FM Migration on Hardware Appliance

Use this option if you have a GigaVUE-FM Hardware Appliance running on GigaVUE-FM version 5.7 or lower that you want to migrate to the latest version of GigaVUE-FM.

Note:  The migration process explained in this section is common for both GigaVUE-FM Hardware Appliance and GigaVUE-FM Hardware Appliance 2.0.

GigaVUE-FM Migration on AWS

Use this option if you want to migrate your GigaVUE-FM instance running on the AWS platform.

Note:  The migration process is applicable only if your current deployment has GigaVUE-FM 5.7. For deployments with GigaVUE-FM 5.6 or lower, you must deploy a fresh installation of the latest version of GigaVUE-FM and create the configurations again.

Refer to the following sections for details:

Frequently Asked Questions (FAQ)

What versions of GigaVUE-FM are supported for migration?

Migration is supported for 5.7 to 5.8, 5.9, and 5.10. Refer to the Supported GigaVUE-FM Migration and Upgrade Paths table for details.

 

What if I am already running GigaVUE-FM 5.8?

If the GigaVUE-FM version is already in 5.8 or above, then migration is not needed, you can just perform an upgrade.

 

What platforms are supported for migration?

Migration to the latest version of GigaVUE-FM is supported only on VMware ESXi, GigaVUE-FM Hardware Appliance, and AWS platforms.

 

What if I am running GigaVUE-FM v5.7 or older on a platform that does not support migration?

In this case, you will need to perform a fresh installation of GigaVUE-FM 5.8 or above. Beyond v5.8, migration is not needed, you can just perform an upgrade.