Before You Begin
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. 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. |
| GigaVUE‑HC2 and GigaVUE-HC2-Plus devices have 4GB RAM and can go into a low memory condition. It is always recommended to do a reload before the image install as part of the upgrade process. |
| 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 HC 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 HC 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.
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” in the GigaVUE-OS CLI Reference Guide for instructions on how to enable the physical bypass.
Note: 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 using GigaVUE-FM, the admin password on the node is not changed.
