Upgrade Software on a GigaVUE Node or a Cluster from GigaVUE-FM

This section describes the steps to upgrade the software on GigaVUE nodes and clusters. You can upgrade software by using an image that is located on an external image server, or you can use GigaVUE-FM as the image server for H Series and TA Series nodes. G Series nodes can only be upgraded with an external image server. Refer to Upgrade G Series Node.

Note: When using GigaVUE-FM to upgrade software on the nodes, it is imperative that the minimum version on the node be at version 4.3.xx. If the software is not updated to version 4.3.xx, refer to the GigaVUE-OS Upgrade Guide and use either the CLI or GigaVUE-FM at the node level to upgrade the node to the latest revision.

Before upgrading a node or a cluster, it is important to note the following:

•

GigaVUE-FM can upgrade up to 32 nodes at a time. For example, if you select a cluster with 8 nodes and 28 standalone nodes, GigaVUE-FM will fail to upgrade as the total number of nodes exceeds the limit.

•

Check if the device that you want to upgrade has enough disk space. The disk space is computed based on the last synchronized time. A newly added node may sometimes show low disk space. Wait for approximately 5 minutes for the configuration sync to complete or rediscover the device and then check the disk space.

•

When the upgrade process is complete, a post-upgrade sanity check is performed. Physical inventory snapshot of nodes, cards, ports, maps, and GigaSMART operations are captured and the numbers from before and after the upgrade are compared. Sometimes, these numbers do not match immediately after the upgrade, as the device is still being configured. GigaVUE-FM checks every minute whether the nodes have joined the cluster. If the nodes joined do not increment in 30 minutes, then the sanity check will fail.

After the nodes join the cluster, GigaVUE-FM again checks every minute for other configuration objects to come up. If the configuration objects do not increment in 10 minutes, the sanity check will fail. When the sanity check fails, GigaVUE-FM provides an ability to view the configuration object that failed the sanity check.

•

GigaVUE-FM v5.5.00 supports the installation of bootloader on GigaVUE H Series and GigaVUE TA Series nodes during the GigaVUE-OS image upgrade, but it does not automatically activate it.

Note: Depending on your configuration, you may need to enable physical bypass mode before performing the GigaVUE-OS image upgrade, and then restore it after the upgrade is complete.

During the GigaVUE-OS image upgrade, GigaVUE-FM v5.5.00 first upgrades the GigaVUE-OS image and then reboots the system. After the GigaVUE H Series or GigaVUE TA Series node has rebooted with the new GigaVUE-OS image, the bootloader installation will automatically initiate from GigaVUE-FM.

Note: The bootloader upgrade will apply only if there is a bootloader version change in the specific GigaVUE-OS software release. Refer to the GigaVUE-OS Upgrade Guide for the upgrade procedures and to check the bootloader version changes.

When the installation process completes, a message about the bootloader installation will appear in the GigaVUE-FM Task Log Details.

Important: The newer bootloader version only goes into effect after an additional manual reboot. You must explicitly reload the GigaVUE H series or GigaVUE TA series device to update the bootloader version. This additional reboot will cause the optical-protection switches of the relevant Bypass Modules to change states multiple times.

Recommendation: To avoid this state-change behavior, enable the physical bypass before performing the GigaVUE-OS image upgrade. Refer to “Configuring Inline Bypass Examples: Protected Inline Bypass Using Bypass Combo Modules” section in the GigaVUE-OS-CLI Reference Guide for instructions on how to enable the physical bypass.

Note: Starting in GigaVUE-OS software version 4.7, the default password admin123A! for the admin user is no longer valid when logging in to the node. When upgrading from the CLI, the configuration jump-start script requires the user to change the default password for the admin user. However, if the node is upgraded to software version 4.7 or later using GigaVUE-FM, the admin password on the node is not changed.

No Default Password on admin User

Starting in GigaVUE-OS 4.7, the default password admin123A! for the admin user is no longer allowed. When upgrading a node to GigaVUE-OS 4.7 from GigaVUE-FM, if the target node uses the default password, you must change the password on the node upgraded to GigaVUE-OS 4.7. If a device is upgraded to GigaVUE-OS 4.7 from GigaVUE-FM, the next time you log into the device directly the following message is displayed the following message is displayed:

Admin account password must be changed via the CLI to a non-default value for security purposes.

Therefore, If you want to upgrading a node to GigaVUE-OS version 4.7 from GigaVUE-FM, and the target node is using the default password, it is recommended that you do the following to ensure a smooth transition:

Log in to the target node through H-VUE and change the password for the admin user. For details on setting the admin password through H-VUE, refer to the GigaVUE-OS H-VUE User’s Guide.

Select System > Node Credentials.

Click Add.

In the Node IP field, enter the node IP for the target node from step 1.

For Username, enter the admin’s username.

In the Password and Confirm Password fields, enter the password for the node created in step 1.

Click Save.

Select Authentication > RBAC, and then do the following:

Select Use node credentials entered during “Add Physical Node” for all node operations by all GigaVUE-FM users.

Click Save.

Upgrade the node from GigaVUE-FM.