Given that I’ve not touched vSphere 5.5 yet, I thought I would try and upgrade some of the VMware components within my company’s solution centre…. and the easiest component to upgrade first would be the VCA that I deployed to run as my test DR environment.
Anyways, so my old VCA was running 5.1a and I wanted to do an upgrade of it to 5.5.
Fired up a browser to the management page – http://vca-ip:5480 – and tried to do an update via the VMware.com repository….. unfortunately there wasn’t an upgrade option available to go to 5.5 (only to upgrade to 5.1b)…… pants…..
So I navigated over to the VMware product download pages to try the get hold of the zip bundled update…. only to find there wasn’t one available… double pants….
So the only option I had was to deploy a brand new version of VCA and then go through the upgrade wizard from within the new VCA. Having never done this before, I thought it would be a messy process….. strangely enough it was very easy!
Although the issue about having to take this path is the requirement to have enough storage space for a second VCA and also another spare IP address which could be used temporarily until the upgrade wizard completes the sync of the old config. Fortunately I have DHCP running so the new VCA picked up an IP without me having to go into the console and configure the network! =)
1. After deploying the new VCA, the wizard allows you to select “Upgrade from previous version”. What this does is connect the new VCA to your old one, and pull over all the old configuration details (like Network)… it looks as if the wizard also pulls over stats and logs as post deployment I can still see all the old tasks and event.
(If this wizard doesn’t start, then click on the Summary tab and under Utilities launch the Setup Wizard)
3. Open up the management console of the old VCA, browse to the Upgrade tab and paste the new VCA key into the window and click “Import key and stop vCenter Server”. Once the import is successful, the old VCA will generate its own SSL key which you need to cut and paste into the new VCA.
5. The setup performs a check on the SSL certificate of the old VCA. If problems are found, the Setup wizard explains the problem and provides an option to generate a new self-signed certificate for the new VCA. Since I’m not using a CA-signed certificate, I’m quite happy to replace the old cert with a new self-signed one.
9. Click Start and sit back, relax and count some chickens as you wait for the upgrade to complete. It took about 15mins for my upgrade to complete, but that could be due to the small environment being managed by the VCA.
Next up, an upgrade to SRM 5.5…….