Upgrade Operations

Users with ADMIN privileges can download software, firmware and SSL certificate from either the local machine using HTTP or a remote machine using FTP with all the upgrade binaries available on the FTP server. The software download and activation does not affect service. During the software download operation, existing functionality of the node remains unaffected, unless otherwise stated in the release notes.

A firmware upgrade involves the upgrade of boot loader, root file system and operating system. The firmware bundle is checked for checksum and the version. Firmware download is non-service affecting and requires a warm restart to take effect.

During documentation upgrade, the documentation bundle is checked for checksum and the version.

The five steps involved in the unified upgrade operations are:

• Software download: Downloads the software from remote or local machine onto the node. The upgrade bundle present in the remote server is usually a collection of compressed files (in tar format) containing a catalogue, the software and the firmware. If the upgrade bundle does not contain the software and firmware, the software and firmware needs to be upgraded separately. During upgrades from a local machine, the software and firmware are upgraded separately.
• Check upgrade: Checks the correctness and integrity of the downloaded software files.
• Load upgrade: Loads the downloaded content into the proper directory on the node.
• Invoke upgrade: Invokes the new software on the node. The node goes for a warm reboot. After invoking, the new software and firmware comes into effect and the node is upgraded.
• Commit upgrade: Completes the upgrade process. After committing upgrade, the user cannot revert to the previous software version.

NOTE: Only software image files (with extension .img) can be downloaded using HTTP, where as firmware files, software load and documentation can be downloaded using FTP. The Upgrade operations menu is applicable only for some Tejas Product.