Upgrade via CLI
- Login to the server where software package is located and use WinSCP or similar program to copy software package to the Load balancer you are intending to upgrade.
- From server, SSH into the Load balancer you are intending to upgrade and extract the software package file using following command for example:
tar -xvzf ZeusTM_104_VMware-Appliance-Upgrade-x86_64.tgz
- From Load balancer CLI get into the extracted directory for example:
Note: Install script may be in different directory depending on the release.
- You may not see any activity after running the scrip on CLI so keep an eye on the GUI of the Load balancer that will still show you the progress.
- On Load balancer GUI you should see following alerts:
INFO 20/Jun/2017:12:34:38 +0100 INFO Starting full upgrade to version 10.4
WARN 20/Jun/2017:12:38:29 +0100 WARN To complete the upgrade a reboot is required lb-server-1
INFO 20/Jun/2017:12:38:26 +0100 INFO Installation of version 10.4 successful. A full reboot is required to complete the upgrade. lb-server-vm-1
- Once reboot alert is received as shown in step above then reboot the Load balancer via GUI System> Traffic Manager>Hardware Restart>Reboot.
Rollback via CLI
To Roll back to a previous software version please follow these steps:
- From server, SSH to Load balancer you are intending to downgrade.
- Execute the rollback script by running following command:
Note: Rollback script may be in different directory depending on the release.
- SSH session to the Load balancer will be lost as soon as you will run the rollback script in step above and Load balancer will go in reboot state.
- Once Load balancer has come back up, SSH again and verify the old version.
- Through the load balancer’s Diagnose->Cluster Diagnosis> verify that the Traffic Manager is operating correctly with require version and that the state of Pools is not different than before the change.
- Apply the rollback procedure to the secondary load balancer if clustered.
Following steps involved in upgrading Stingray Traffic Manager (STM) via GUI.
- Take backup of the LB by navigating to System > Backups > Create a Backup
- Export this configuration and save it in case you need.
- Take Screen capture of Pool Status and or any active alarm against any Pool through the Diagnose>Cluster Diagnosis> section of the web interface. Take a note of any errors.
- Make sure that new installation package already been downloaded.
- Take note of the current traffic activity by navigating to Activity>Current Activity> tab and take screen capture for your record.
Notes: Please note that several services are expected to be offline so just take a note of them.
Upgrade Procedure via GUI
- Obtain the new installation package for example ZeusTM_104r1_Linux-x86_64.tgz and Navigate to the System>Traffic Managers> page on the STM GUI Interface you intend to upgrade
- Click the Upgrade button under System>Traffic Managers>Software Upgrade> section and upload the new installation package.
- Follow the instructions to apply the software upgrade and wait for the package to load.
- Once software package has been loaded successfully onto the LB then message will prompt you to reboot the Load balancer.
- To reboot the LB, navigate to System> Traffic Manager>Hardware Restart>Reboot
- Wait for the LB to come back up.
- Once LB has restarted, login to the LB and verify the latest version is being shown at top left corner.
- Follow steps above to upgrade the secondary load balancer if clustered.
Notes: Software version mismatch alarm is expected if LB are in single site or multi-site cluster.
- Check and Compare the status of configured Pool or any active alarm against any Pool through the Diagnose>Cluster Diagnosis> section before and after the upgrade.
Rollback via GUI
To Roll back to a previous software version please follow these steps:
- Navigate to the System>Traffic Managers> section from STM GUI
- Click the Rollback button and select the old installation package you want to rollback to from drop down list.
- Follow the instructions to apply the software downgrade.
- Wait for the STM to load the package and reboot the LB when prompted to complete the downgrade.
- Once LB has come backup, login to STM’s GUI and from Diagnose->Cluster Diagnosis> section verify that the Traffic Managers is running on the downgraded package and operating correctly with state of Pools and node is no different than before the change.
Upgrading a Stingray Traffic Manager is easy either via CLI or GUI. Following are easy steps to upgrade via the Administration Interface on STM:
Upgrade Procedure via GUI:
1. Obtain the new installation package ( for example ZeusTM_104r1_Linux-x86_64.tgz)
2. Navigate to the System > Traffic Managers page on the Admin Interface of the Traffic Manager you intend to upgrade.
3. Click the Upgrade button and upload the new installation package
4. Follow the instructions to apply the software upgrade.
*Software version mismatch alarm is expected if your upgrading a cluster. This alarm will clear itself once complete cluster is running on same version.
Roll back Procedure via GUI:
1. Navigate to the System> Traffic Managers page on the the Admin Interface of the Traffic Manager you intend to upgrade.
2. Click the rollback button and select the old installation package for example release 9.9.
- Follow the instructions to apply the software upgrade.
Upgrade procedure via CLI:
- Upload and extract the software package for xample ZeusTM_104r1_Linux-x86_64.tgz in /root
- Get into the cd ZeusTM_104r1_Linux-x86_64
- Run the installation script ./zinstall
- Select upgrade and allow to complete.
Through the web interface verify that the load balancer has returned to production operation. Warnings are expected on the Cluster Diagnosis due to the version mismatch within the cluster.
Rollback procedure via CLI
On each load balancer in turn, as required:
- Get into the cd /usr/local/zeus
- Run the rollback script ./zxtm/bin/rollback
- Select version the older version for example 9.9
- Allow the downgrade process to run to completion
Once SSL certificate on Stingray/Brocase/Zeuss reaching expiry, there will be an alert generated on the Loadbalancer in advance to inform you to take necessary action.
If you recieve .pfx certificate from customer, then you would need to convert it in order to import into the Stingray Loadbalancer. Please note that this .pfx file contains public and private key and extension .pfx is associated Microsoft Servers. Private key in received .pfx file received from customer will also be encrypted with password, so customer will provide you password as well do decrypt it before installing into the Stingray Loadbalancer.
What you would need is basically access to any Unix machine that has openssl installed. Then you need to follow these steps:
Extracting the private key from a PKCS12 file:
openssl pkcs12 -in certificate.from.customer.pfx -nocerts -out key.pem -nodes
If you omit the -nodes flag, openssl will prompt you for an encryption password to protect your private key; Stingray does not support such encrypted keys. If you inadvertently create an encrypted key, you can generate the decrypted version as follows:
openssl rsa -in key.pem -out key.decrypted.pem
Extracting the certficate from a PKCS12 file:
openssl pkcs12 -in certificate.from.customer.pfx -nokeys -out cert.pem
Now go into Loadbalncer>SSL tab. Then import cert.pem and key.decrypted.pem file into the Loadbalancer. You would then see the newly imported certificate is now showing into the list of all available SSL certificate.
You would now need to attach the newly imported certificate with the VIP/Pool.
- Just go into the Catalog>SSL tab and select your certificate that is expiring.
- Then click on the VIP/Pool linked to the certificate that is expiring.
- Select the newly imported certificate from the drop-down list of available certificates and click update at the bottom of the page.
You should now see the alert in the load balancer regarding certificate expiry is now cleared. This can be checked in event logs in the load balancer tab and notice that the new certificate activation cause alert to go green from amber.