Upgrade GigaVUE Fabric Components in GigaVUE‑FM for AWS

This chapter describes how to upgrade UCT-V Controller, GigaVUE V Series Proxy and GigaVUE V Series Nodes.

Refer to the following topic for more information:

Prerequisite

Before you upgrade the GigaVUE V Series Proxy and GigaVUE V Series Nodes, you must upgrade GigaVUE‑FM to software version 5.13 or above.

Upgrade UCT-V Controller

Note:  UCT-V Controllers cannot be upgraded. Only a new version that is compatible with the UCT-V's version can be added or replaced in the AWS Fabric Launch Configuration page.

UCT-V Controller version can be changed in the following two ways:

To change the UCT-V Controller version follow the steps given below:

Upgrade between Major Versions

To upgrade between the major versions of UCT-V Controller, you must add the new version of the UCT-V Controller and remove the existing version.

Note:  You can only add UCT-V Controllers which has different major versions. For example, you can only add UCT-V Controller version 6.8.00 if your existing version is 6.9.00.

  1. Go to Inventory > VIRTUAL > AWS.
  2. Click Actions > Edit Fabric. The AWS Fabric Launch Configuration page appears.
  3. Under Controller Versions, click Add.
  4. From the Version drop-down list, select a UCT-V Controller image that matches with the version number of UCT-Vs installed in the instances.
  5. From the Instance Type drop-down list, select a size for the UCT-V Controller.
  6. In Number of Instances, specify the number of UCT-V Controllers to launch. The minimum number you can specify is 1.

You cannot modify the IP Address Type and the Additional Subnets details, provided at the time of UCT-V Controller configuration.

After installing the new version of UCT-V Controller, follow the steps given below:

  1. Install UCT-V with the version same as the UCT-V Controller or upgrade the UCT-V to the same version as the UCT-V Controller. Refer to Configure UCT-V for more detailed information on how to install or upgrade UCT-V.
  2. Delete the UCT-V Controller with older version.

Upgrade within the Same Major Version

This is only applicable if you wish to change your UCT-V Controller version from one minor version to another within the same major version. For example, from 6.10.00 to 6.10.01.

  1. Go to Inventory > VIRTUAL > AWS.
  2. Click Actions > Edit Fabric. The AWS Fabric Launch Configuration page appears.
  3. Under Controller Versions, select a UCT-V Controller image within the same major version from the Version drop-down list.
  4. Specify the Number of Instances. The minimum number you can specify is 1.
  5. Select the Subnet from the drop-down.

You cannot modify the rest of the fields.

Upgrade GigaVUE V Series Nodes and GigaVUE V Series Proxy

GigaVUE‑FM lets you upgrade GigaVUE V Series Proxy and GigaVUE V Series Nodes at a time.

There are two ways to upgrade the GigaVUE V Series Proxy and Nodes. You can:

■   Launch and replace the complete set of nodes and proxy at a time.

For example, if you have 1 GigaVUE V Series Proxy and 10 GigaVUE V Series Nodes in your VPC, you can upgrade all of them at once. First, the new version of GigaVUE V Series Proxy is launched. Next, the new version of GigaVUE V Series Nodes is launched. Then, the old version of V Series Proxy and Nodes are deleted from the VPC.

NOTES:

o   When the new version of nodes and proxy are launched, the old version is not deleted by GigaVUE‑FM until the new version of node and proxy is launched and the status is changed to Ok. Make sure that the instance type of the node and proxy selected during the configuration can accommodate the total number of new and old fabric components present in the VPC. If the instance type cannot support so many Virtual Machines, you can choose to upgrade the fabric components in multiple batches.
o   If there is an error while upgrading the complete set of proxy and nodes present in the VPC, the new version of the fabric is immediately deleted and the old version of the fabric is retained as before.
o   Prior to upgrading the GigaVUE V Series Proxy and Nodes, you must ensure that the required number of free addresses are available in the respective subnets. Otherwise, the upgrade will fail.
■   Launch and replace the nodes and proxy in multiple batches.

For example, if there are 18 GigaVUE V Series Nodes to be upgraded, you can specify how many you want to upgrade per batch.

To upgrade the GigaVUE V Series Proxy and GigaVUE V Series Nodes:

1.   Go to Inventory > VIRTUAL > AWS , and then click Monitoring Domain. The Monitoring Domain page appears.
2. On the Monitoring Domain page, select the connection name check box and click Actions

3. Select Upgrade Fabric from the drop-down list. The Fabric Nodes Upgrade page appears.
4. To upgrade the GigaVUE V Series Nodes or Proxy, select the Upgrade checkbox.
5. From the Image drop-down list, select the latest version of the GigaVUE V Series Proxy or Nodes.
6. Select the Change Instance Type checkbox to change the instance type of the nodes or proxy, only if required.
7. To upgrade the GigaVUE V Series Nodes or Proxy, specify the batch size in the Batch Size box.

For example, if there are 7 GigaVUE V Series Nodes, you can specify 7 as the batch size and upgrade all of them at once. Alternatively, you can specify 3 as the batch size, and launch and replace 3 V Series Nodes in each batch. In the last batch, the remaining 1 V Series Node is launched.

8. Click Upgrade.

The upgrade process takes a while depending on the number of GigaVUE V Series Proxy and Nodes upgrading in your AWS environment. First, the new version of the GigaVUE V Series Proxy is launched. Next, the new version of GigaVUE V Series Nodes is launched. Then, the older version of both is deleted from the project. In the V Series Proxy page, click the link under Progress to view the upgrade status.

Once the nodes are upgraded successfully, the Monitoring Session is re-deployed automatically.