These instructions describe how to upgrade Traffic Manager Virtual Appliance instances. For instructions on upgrading on other platforms, please refer to Upgrading Traffic Manager.
There are a few things that have to be checked before an upgrade is attempted to make sure it goes smoothly:
The unix command df shows how much space is available, for example:
root@stingray-1/ # df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda5 1426384 839732 514764 62% /
varrun 517680 44 517636 1% /var/run
varlock 517680 0 517680 0% /var/lock
udev 517680 48 517632 1% /dev
devshm 517680 0 517680 0% /dev/shm
/dev/sda1 139985 8633 124125 7% /boot
/dev/sda8 621536 17516 604020 3% /logs
If the disks are too full, you have to free up some space. Please follow the suggestions in the topic Freeing disk space on the Virtual Appliance.
Traffic Manager software is stored on one of two primary partitions, and log files are stored on a separate disk partition.
Full Upgrades are required when you upgrade to a new major or minor version number, such as from 18.2 to 19.1, or 19.1 to 19.2. Full upgrades include a new operating system installation.
A full upgrade is installed in the unused primary partition, configuration (including the /root directory) is migrated across and the bootloader updated to point to the new partition. You can edit the bootloader configuration to fall back to the other primary partition if you need to roll back to the previous instance.
Incremental Upgrades are required when you install a release with a new revision number, such as from 9.1 to 9.1r1. The new software is added to the currently active primary partition. You can use the 'rollback' script to make a previous revision active.
If you wish to upgrade from one major.minor version to a later major.minor version with a later revision, you will need to upgrade in two steps: the full upgrade, and the subsequent incremental upgrade.
For example, suppose that you are running version 17.3r2 and you wish to upgrade to version 18.2r1. You must perform the following two steps:
Upgrades between major and minor versions (e.g. 18.2 to 19.1 or 19.1 to 19.2) can either be performed via Administration Server (when upgrading from version 9.0 or later) or using a command-line script (z-upgrade-appliance) to install the new version into a spare section of the hard disk. This process involves one reboot and the downtime associated with that reboot.
Any configuration changes made in the existing version after the upgrade has been run won't be preserved when the new version is started; you should reboot the appliance as soon as possible (using the System -> Reboot button in the UI or using the 'reboot' command).
Before upgrading it is prudent to have a backup of your configuration.
Download the tgz upgrade package from the download site, go to the System -> Upgrade page, upload the upgrade tgz package, and follow the instructions.
Once complete, the current configuration will be migrated to the newly installed version, and this version will be automatically selected on the next reboot.
Upgrading revisions in the same product version (e.g. 18.2 to 18.2r2) are performed using the Administration Server. Download the tgz upgrade package from the download site, go to the System -> Upgrade page, upload the upgrade tgz package, and follow the instructions.
You will need to complete this process for each Appliance in your cluster.
Expected downtime for an upgrade will be a couple of seconds while the Traffic Manager software is restarted. On very rare occasions, it will be necessary to reboot the Appliance to complete the upgrade. The user interface will inform you if this is necessary when the upgrade is complete. You should ensure that the Appliance is rebooted at the most appropriate time.