Do you want the short answer or the long answer?
The real story:
- After doing several Acropolis (CVM) & NCC (Health check) upgrades before on my customer’s Nutanix clusters today was the first time to do an actual hypervisor upgrade. Since we run everything on VMware we wanted to go from 5.5u2 to 6.0u2. The first things to do is to check all compatibility charts and with Acropolis at 4.6.4 and NCC at 2.2.8 we had green lights all over the board.
- What I always do first before doing anything is running a health check. Since NCC 2.2 you can run some of the checks parallel to save some time:
ncc health_checks run_all -parallel=4
- After the check and make sure DRS is set on automated and vSphere HA is turned on as it should otherwise you won’t be updating anything!
- Next up is heading to Prism, no we’re not doing any cli work when a GUI is better and just as fast!
- The first thing to do is upload the software (Offline bundle zip file from VMware.com and json file from Nutanix.com)
- Go to Software Upgrade
- Select Upload the hypervisor Binary
- Select the binary and the Json files and hit Upload Now
- When this is done hit the arrow besides the upgrade button and select the pre-check (the real upgrade also does this but it is never wrong to check twice!)
- Enter the IP of the vCenter (not DNS!) and credentials
- This won’t take long but if you get bored hit the Nothing do to button for a game of 2048 presented to you by our friends at Nutanix
- You might need to re-open the Software Upgrade but but somewhere it will be done now
- When this finishes successful it’s time to hit the real upgrade button
- You know what to do here right?
- The waiting game has started since there will be a lot of vMotion’s and reboots
- This it might be time for this again
- If you re-open the Software Upgrade bit it will show the versions of ESXi the cluster is now running
- Aaaaaaand we’re done
So actually creating this post took longer then the preparation and actions for the upgrade themselves. For me that was 5 minutes work in preparation and about 20 minutes per host for the upgrade itself.