Upgrade VMware Single Sign On 5.5 (SSO5.5) configured with High Availability
Below are the steps followed in my test lab to upgrade SSO5.5.0 to 5.5.0a
Lab setup:
- Two instance of Single Sign On is installed on Virtual machines
• First instance of Single Sign On (SSO5.5) installed in a basic deployment mode
• Second instance of Single Sign On (SSO5.5) installed in multiple vCenter Servers in a single location
- Configured Single Sign On with Apache Load balancer
- Completed SSO High availability configuration.
- vCenter server and Webclient are installed one another Windows 2008R2 server by providing Apache Load Balancer lookup service URL.
Note: No downtime required for SSO and vCenter server for upgrade SSO deployed in HA.
The steps followed for upgrading:
- Download the VMware-VIMSetup-all-5.5.0a from vmware.com and copied to SSO5.5 Node1.
- Run the SSO installer, it starts the Upgrade of SSO Node1.
- During the SSO Node1 upgrade, Load balance transferred all the transaction to SSO Node2 and user can continue accessing the vCenter server.
- Once the SSO Node1 upgrade completes, copy the VMware-VIMSetup-all-5.5.0a to SSO Node2 and start the upgrade.
- During this time, SSO fail back to the Node1 and the user will be able to continue accessing the vCenter server
- Complete the Upgrade of SSO Node2.
- Upgrade remaining vCenter Components.