vADC Docs

Upgrading Stingray Traffic Manager Virtual Appliance

by on ‎02-22-2013 11:35 AM - edited on ‎07-15-2015 03:53 PM by rickl44 (4,596 Views)

These instructions describe how to upgrade Stingray Traffic Manager Virtual Appliance instances. For instructions on upgrading on other platforms, please refer to Upgrading Stingray Traffic Manager.

 

Before you start

 

There are a few things that have to be checked before an upgrade is attempted to make sure it goes smoothly:

 

  • Memory requirements: Make sure the machine has enough memory. Stingray Traffic Manager requires at the very least 1GB of RAM; 2GB or more are recommended. If the traffic manager to be upgraded has less memory, please assign more memory to the virtual machine.

 

  • Disk Space requirements: Ensure there is enough free disk space. For the upgrade to succeed, at least 500Mb must be free on the root partition, and at least 300MB on the /logs partition.

 

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.

 

Upgrading the Virtual Appliance

 

Riverbed 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 8.1 to 9.0, or 9.0 to 9.1.  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.

 

Important note

 

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 8.1r3 and you wish to upgrade to version 9.1r2.  You must perform the following two steps:

 

  • Perform a full upgrade from your current version to the closest major.minor version, i.e a full upgrade to 9.1
  • Perform a subsequent incremental upgrade from 9.1 to 9.1r2.

 

Performing a Full Upgrade

 

Upgrades between major and minor versions (e.g. 8.1 to 9.0 or 9.0 to 9.1) 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.

 

Command line method

  • Download the installation zpkg package from. This will be a file called something like ZeusTM_91_Appliance-x86_64.zpkg.
  • Copy the file onto the appliance to the /logs partition using an scp or sftp client (e.g. psftp).
  • Log in to the appliance using an 'ssh' client (putty is a good choice) or the console; you can log in using any username that is in the admin group.
  • Check the disk space requirements explained above are still fulfilled after you've uploaded the package.
  • Once connected to the console of the appliance run: z-upgrade-appliance <filename>
  • Confirm that you want to upgrade the appliance.

 

Administration Server (upgrading from 9.0 or later)

Download the tgz upgrade package from Riverbed Support: Software -  Stingray Traffic Manager, 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.

 

Performing an Incremental Upgrade

 

Upgrading revisions in the same product version (e.g. 9.0 to 9.0r2, or 9.0r2 to 9.0r3) are performed using the Administration Server. Download the tgz upgrade package from Riverbed Support: Software -  Stingray Traffic Manager, 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.

Contributors