These instructions describe how to upgrade a Zeus Traffic Manager or Zeus Load Balancer appliance (virtual or hardware).
These instructions describe how to upgrade a Zeus Traffic Manager or Zeus Load Balancer appliance (virtual or hardware). For instructions on upgrading Zeus software, please
<a target="_blank" href="http://community.riverbed.com/t5/Answers/How-do-I-upgrade-my-Zeus-Traffic-Manager-software/m-p/16558/highlight/true#M166">see here</a>
Before you start
There are a few things that have to be checked before an upgrade is attempted to make sure it goes smoothly.
Make sure 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:
[email protected]/# df -k
Filesystem 1K-blocks UsedAvailableUse%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
Zeus software is stored on one of two primary partitions, and log files are stored on a separate disk partition.
When you install a new 'Full' release, it 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 a previous major release.
When you install a 'revision' release, it adds the new installation files to the currently active primary partition. You can use the 'rollback' script to make a previous revision active.
If the disks are too full, you have to free up some space. Try the following:
# rm -rf /opt/zeus/.upgrade
# rm -rf /opt/zeus.extract.<br># rm -rf /usr/share/zxtm-
3. If you've uploaded anything to /root that isn't needed any more, delete those files.
4. Remove old versions of the traffic manager software as described
<a target="_blank" href="http://community.riverbed.com/t5/Answers/Freeing-Space-on-the-Virtual-Appliance/m-p/16344/highlight/true#M86">here</a>
5. Back up some old log files and remove them from /logs.
6. Extend the logs partition as described in the VA Getting Started Guide .
<font size="3"><strong>Upgrading from one revision to another<br>
Upgrading revisions in the same product version (e.g. 4.2r1 to 4.2r2) are performed using the Administration Server. Download the upgrade package from your customer page , go to the System -> Upgrade page, upload the upgrade 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 Management software is restarted. Sometimes 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.
Upgrades between minor and major versions (e.g. 4.1 to 4.2 or 5.1 to 6.0) are performed using a commandline script 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.
Download the ZXTM Install package from customer.zeus.com . This will be a file called something like ZeusTM_60_Appliance-x86_64.zpkg.
Copy the file onto the appliance using an scp or sftp client (e.g. psftp ).
Connect to the console of the appliance using a 'ssh' client (putty is a good choice). You can use any username that is in the admin group.When skipping versions, you must upgrade to the 'r0' release first and then apply the upgrade to the latest revision as described
<a target="_blank" href="http://community.riverbed.com/t5/Answers/How-do-I-upgrade-a-Virtual-or-Hardware-Appliance-to-a-later/m-p/16474/highlight/true#M129">above</a>
. For example if you want to upgrade from 5.0r1 to 6.0r1, you need to take two steps:
5.0r1 -> 6.0 -> 6.0r1
Installation caveats for earlier releases
Upgrades to version 5.1r2 or earlier
When upgrading a virtual or hardware appliance to version 5.1r2 or earlier, you should not skip version numbers; you must apply the 'r0' upgrade packages for each intervening major and minor version. For example, to upgrade from version 4.2 to version 5.1r2, you should upgrade as follows: 4.2 -> 5.0r0 -> 5.1r0 -> 5.1r2. This caveat does not apply if upgrading from 4.1 (or later) directly to 6.0 (or later). You can upgrade directly to your chosen major release (e.g. 6.0), then directly to the desired 'r' release as described above.
Upgrades from version 4.0
To upgrade a hardware appliance from ZXTM 4.0, you need to follow
<a target="_blank" href="http://community.riverbed.com/t5/Answers/How-do-I-upgrade-an-appliance-from-ZXTM-4-0/m-p/16506/highlight/true#M144">these instructions</a>
Traffic IP Group issues when upgrading from version 4.1
Note: If you have Traffic IP Groups using the 'keeptogether' flag that contain 'passive' machines, you should mark all machines as active before upgrading from ZXTM 4.1 to ZXTM 4.2 or later. Once the upgrade is complete, set these machines to 'passive' again.
Releases prior to 4.2 don't correctly handle the combination of keeptogether flag and passive machines, so leaving your configuration unchanged while upgrading may cause Traffic IP addresses to appear on multiple ZXTM machines.
For more detailed information, please refer to the appropriate 'Getting Started' guide in the product documentation .</p>