Install the Software Image

1. Log in on the GigaVUE node to be updated as an admin user and switch to Configure mode.
2. Use the image fetch command to retrieve the software image from your file server. For example, the following command uses SCP to retrieve the hdd58xx image from the builds folder on 192.168.1.25:

(config) # image fetch scp://user:password@192.168.1.25/builds/hdd58xx.img

The CLI shows you the progress of the image fetch with a series of hash marks, returning you to the system prompt when complete.

3. Use the image install command to install the downloaded image file. For example, to install the image downloaded in the previous step:

(config) # image install hdd58xx.img

The GigaVUE-OS CLI presents a series of status messages as it verifies and uncompresses the image, creates file systems, and extracts the image, returning you to the system prompt when complete.

4. The next step is to tell the GigaVUE node which node image to load at the next system boot. The GigaVUE node has two partitions, each of which has a separate image installed. When you install a new image, it automatically installs on the “next” partition – the one you are not using now. The image boot next command tells the GigaVUE node to boot from the next partition after the one currently booted – the one where you just installed the new image:

(config) # image boot next

Note:  In order for sync to work properly following a reload, ensure that the installation file for the active configuration is present after the image boot next command in the previous step.

5. Save the current configuration with the following command:

(config) # write mem

6. Is this node part of a cluster?
• No – Reboot with the following command.

(config) # reload

When the node comes back up, save the configuration with write memory.

• Yes – Is this the last node in the cluster?
• No - Do not the reload at this time. Proceed to upgrade the next node in the cluster.
• Yes - If this the last node to be upgraded in the cluster (that is, it is the master), reload the cluster using the following CLI command.

(config) # cluster reload

7. Save the current configuration with the following command:

(config) # write mem