We have the following in our WAAS deployment. All CM's and WAE's are running v 220.127.116.11.
> Primary CM
> Standby CM
> 7 x WAE's (functioning as Application Accelerators)
I tried upgrading one of the WAE's the other day to v 4.4.5c.4 and received an error that the Primary CM needs to be upgraded first before any of the WAE's.
My questions are as follows:
1. The Standby CM and 1 of the WAE's are in our QA enviroment - can I upgrade the Standby CM and WAE in the QA lab or do I need to upgrade the Primary CM first and then the Standby CM and WAE's etc. I basically would like to ensure the latest version works well before rolling this out and the QA lab is the best place to do this without affecting production ???
2. I noticed v 5.x.x is released and I would prefer to upgrade to this version. Would I first need to upgrade all the CM's & WAE's to the latest version in the v 4.4.5.x release or can I jump straight from v 18.104.22.168 to v 5.x.x.x ???
1- You can upgrade the standby and any WAE's on your LAB, but this is not the best practice.. I sense issues with the CMS database..if the standby and the CM are on different subnets you won't be able to check on the Standby status once it comes back from the upgrade.
Also just to clarify, it is a prerequisite to upgrade the secondary Central Manager before you upgrade the Primary Central Manager, as described in Upgrading the Standby Central Manager.
2- You can upgrade directly to version 5.0.x. refer to the update Paths chart below:
I am confident the new version 5.x will do it's job ok...
have a nice day!