How do I upgrade my Zeus Traffic Manager software?
You can upgrade a running copy of the Traffic Manager software with very little downtime. There are two ways to perform the upgrade: using the Administration Interface, or using the command line. The upgrade procedure:
The downtime is rarely more than one or two seconds. If necessary, you can then install a new license key file using the Zeus Admin Server, for example, to enable new product features.
Upgrading your Zeus Traffic Manager software via the Administration Interface
Upgrading your ZXTM software via the command line
Upgrading a ClusterIf you have a cluster of traffic managers, you can upgrade each one in turn. Do not make any configuration changes until you have upgraded the entire cluster to the same software version. NotesNote: If you have Traffic IP Groups using the 'keeptogether' flag that contain 'passive' machines, you should mark all machines as active before upgrading to ZXTM 4.2. 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. Java ExtensionsThe Java Extensions feature added in ZXTM 5.0 requires a supported Java Runtime Environment installed on the ZXTM system. The JRE is not included with the software package provided by Zeus. Zeus supports the Sun JRE, versions 1.5 and above. To roll back to a previous software versionYou can use the 'rollback' script to revert back to a previously installed version of Zeus software, or to roll forward to a later version that you installed previously:
You will then be shown a list of the different software versions that you have installed, and asked to chose which one you would like to roll back or forwards to. When you roll back (or forwards) to a different version, the software will use the configuration that was last active with that version. For example, If you upgraded from version 5.1 to version 6.0 two weeks ago, then roll back to version 5.1, it will use the configuration that version 5.1 last used two weeks ago. Rolling forwards from early versions of ZXTMEarly versions of ZXTM did not include the rollback script. If the rollback script is not present, you can manually modify the zxtm, zxtmadmin and admin symlinks. The symlinks point to the current version of each software component.
Comments:This public messageboard is not a forum for technical support. To report technical support problems, please contact our dedicated Support team using the instructions at the bottom of this page.
Comment from:
Rangarajan Radhakrishnan [Visitor]
The upgrade appears to change the permissions of the log directory (when they are intentionally modified). I think it would be nice if the upgrade warns before changing the log directory permissions.
Comment from:
Martin [Visitor]
Agreed with the previous comment, it would be nice if the upgrade process moved the log directory to the new version directory since %zeushome% points to a symlink depending on version number. This is an undocumented feature (aka bug? :-).
|
Recently...
Other Resources
|





