The second part of my FLUP-grade was to use the tool for vCenter Server Appliance 5.5 to upgrade to 6.0! The issues for me were:
– I use VMware Workstation for a nested lab using AutoLabs.
– The tool relies on your vCSA being hosted on an ESXi Server.
– There are only a few blogs for deploying vCSA 6 on Workstation, that I found.
I’d love to have a proper lab with real equipment, but sadly that is not the case at this moment in time; one day perhaps! Given that my home machine is only so fast, I don’t like to run many nested VM’s on my already virtualized ESXi servers as things become a bit slow. On the the Workstation Layer I have:
– A Domain Controller & VUM Server
– 2-3 Virtual ESXi hosts
– vCSA 5.5
– Openfiler + FreeNas storage VM’s
– A Router
In the ESXi layer, I run small lightweight VM’s mainly for testing features and deployments.
Here is how I upgraded:
2) Next, I shutdown my existing 5.5 vCSA and exported it as an .OVA.
3) Whilst this was happening, I increased the Memory on my ESXi hosts to 12GB each and powered them on. I then used the vSphere client to connect to the hosts directly and imported the vCSA to my first host. I checked the networking of the VM and powered it on.
11) I then chose the smallest deployment type for obvious reasons. At this stage, if I hadn’t increased my hosts memory I wouldn’t have been able to proceed as a warning appears stating insufficient memory. The destination host must have more than 8GB for the VM to live!
13) I then assigned a static IP address for the vCSA 6 to take on my network. As stated in the text, it’s only temporary and when the whole operation is complete the new vCSA assumes the identity of the existing vCSA!
It worked! It might not be the prettiest/recommended/sane method and is only for my home lab scenario, but I really wanted to upgrade from 5.5 to 6.0 vCSA using proper methods in case this is ever needed in Production (and it will be!).
So that ends the chapter of my vCenter FLUP-grade. A bit of a strange journey, but I got there in the end!