In many cases, it is desirable to upgrade a virtual appliance by deploying a virtual appliance at the newer version and importing the old configuration. For example, the size of the Traffic Manager disk image was increased in version 9.7, and deploying a new virtual appliance lets a customer take advantage of this larger disk. This article documents the procedure for deploying a new virtual appliance with the old configuration in common scenarios.
These instructions describe how to upgrade and reinstall Traffic Manager appliance instances (either in a cluster or standalone appliances). For instructions on upgrading on other platforms, please refer to Upgrading Traffic Manager.
This process will replace a standalone virtual appliance with another virtual appliance with the same configuration (including migrating network configuration). Note that the Traffic Manager Cloud Getting Started Guide contains instructions for upgrading a standalone EC2 instance from version 9.7 onwards; if upgrading from a version prior to 9.7 and using the Web Application Firewall these instructions must be followed to correctly back up and restore any firewall configuration.
Upgrading a cluster of Virtual Appliances (except Amazon EC2)
This process will replace the appliances in the cluster, one at a time, maintaining the same IP addresses. As the cluster will be reduced by one at points in the upgrade process, you should ensure that this is carried out at a time when the cluster is otherwise healthy, and of the n appliances in the cluster, the load can be handled by (n-1) appliances.
Because EC2 licenses are not tied to the IP address, it is recommended that new EC2 instances are deployed into a cluster before removing old instances. This ensures that the capacity of the cluster is not reduced during the upgrade process. This process is documented in the "Creating a Traffic Manager Instances on Amazon EC2" chapter in the Traffic Manager Cloud Getting Started Guide. The clusterPwd may also need to be fixed as above.
Thanks for the great article,
So by using the article above to Upgrade a cluster of Virtual Appliances, is there any downtime involved or it will be transparent to the users ?
Just wanted to add 2 things:
If you are restricting the access to the machine with the dedicated IP of you members of the cluster, the IP of the machine you are removing is removed from the restricted access so before (re)joining the cluster make sure to add manually the IP again in the other members of the cluster
And if you are making an upgrade between 2 different versions and you do have extra files they are not copied because of the folders path being zeus/$version$/yourfiles...and if you have 2 differents versions not working so a scp is necessary
It is transparent for users if you make sure that you have no traffic on the node you are exiting from the cluster
I have the standaalone VTM
How I can check the the application firewall is enabled or not?
and during the export of config backup there is option of include the application firewall or not . what i need to do on that?
and same for the import ?