With VxRail 4.7.000 being released today for VxRail upgrades, I wanted to walk through part of the process. First, ALWAYS check SolVe for the procedure to run the upgrade in your environment. It will provide the detailed procedure you need to follow for this upgrade.
For the upgrade, I downloaded the file locally and then did a local file upgrade. This process takes the 4.7.000 package and uploads it to the VxRail Manager VM to stage the code on the system – this includes ESXi as well as the HW/FW updates.
After the package is uploaded and unpacked, the system will show you which components will be upgraded during the entire process.
Once that is complete, we’re ready to start the upgrade. In my environment, I’ve deployed the internal VCSA/PSC that comes with VxRail. Because of that, the upgrade from VxRail Manager will also upgrade those 2 components. For the most part, the upgrade is like any other upgrade, with the exception of the internal vCenter/PSC components. Instead of performing an upgrade on those components, we will actually deploy a new VCSA/PSC and then migrate the information from the existing one.
As part of this install/migrate process, we will need to provide a temporary IP address for the system to use:
For the internal vCenter based VxRail systems, you’ll see the window open for this temporary IP. The upgrade will use that IP to install a new PSC, migrate the information from the old one, and then power down the old PSC and re-IP the new one with the original IP and do the same for the VCSA.
Just as with any other VxRail upgrade, you’ll also see a warning message that VxRail Manager will reboot and you’ll be disconnected. In my testing, the upgrade of the VxRail Manager did take longer than other upgrades from within the 4.5 family.
After the VxRail Manager upgrade is completed, the next step is to upgrade the VCSA and PSC. Just remember, if you’ve deployed your VxRail to an external (or your provided) vCenter, VxRail Manager will not perform any upgrades on that system – please refer to SolVe for the versions you need to be at.
For the internal VCSA/PSC installs, you will see the system deploy new temporary instances of each VM. The first one will be the PSC – you can see here VxRail Manager will show a message to the fact that a temporary PSC is deployed and you’ll also see it within vCenter.
You will see the same for the VCSA:
After the system is done it will move onto the VxRail nodes and non-disruptively upgrade them one by one.
When the upgrade is done, you’ll see the following inside VxRail Manager:
At this point, you’ll want to hit the “Refresh” button to update the information on the “Installed Components” link. Once that’s done, you’ll be able to verify that you’re now on VxRail 4.7.000.
After that’s completed…you can now log into vCenter and start using the new HTML5 Client! YES!!!
Don’t forget to generate a new procedure from SolVe before performing this upgrade – that’s the best way to make sure you’re setting yourself and the VxRail up for success and a smooth upgrade.