Before You Begin
Before you start installing the software image, perform the following checks:
Change Default admin Password
Check the password on the admin account. If you are using the default password on this account (admin123A!), the best practice is to change it to a non-default password before you upgrade. Refer to the Password Policies section in the GigaVUE-OS CLI Reference Guide for more details.
When the upgrade is complete and the node has rebooted, log in with your non-default password.
If you have not changed the default password before the upgrade, when the upgrade is complete and the node has rebooted, you will be prompted to enter a non-default password. The jump-start script will automatically launch and prompt the system administrator to change the password on the admin account.
Check Number of Images
Check the number of images currently available for installation on the node with the following command:
(config) # show images
The maximum number of images allowed on GigaVUE HC Series or GigaVUE TA Series nodes at any one time is three.
If there is already the maximum number of images listed in the Images available to be installed section of the show images output, use the image delete command to remove at least one of the existing images before you fetch a new one.
The recommendation is to delete any unused images.
Note: Once an image is installed, you can delete the uploaded image.
Check U-Boot Version
If you are upgrading from an older software version, check the U-Boot version using the following command:
(config) # show version
For example on a GigaVUE‑HC2 node, the following output is displayed:
U-Boot version: 2011.06.8
Check that the U-Boot version matches the version listed in Software Image Filenames for GigaVUE‑OS Nodes in the Bootloader Version column.
If you do not have the same version, you will have to do a U-Boot installation, after the image installation. Refer to Install U-Boot (If a Newer Version is Available).
Check Coreboot Version
If you are upgrading from an older software version, check the coreboot version using the following command:
(config) # show version
For example on a GigaVUE-TA100 node, the following output is displayed:
1st flash version: coreboot-ta100-0.2.4 Wed Jan 20 15:19:09 CST 2016 **2nd flash version: coreboot-ta100-0.2.5 Fri Sep 25 19:54:15 CST 2015
Check that the coreboot version matches the version listed in Software Image Filenames for GigaVUE‑OS Nodes in the Coreboot Version column.
If you do not have the same version, you will have to do a coreboot installation, after the image installation. Refer to Install Coreboot (If a Newer Version is Available).
