The VMware vSphere team released Update 1b a few days ago. The Build no is 3343019.
As usual, it’s wise to review the Release Notes before making changes to live environment. You need to review both the vCenter Server release notes and ESXi release notes.
If you are already on Update 1, and you are using the vCenter appliance, the update to 1b is pretty straight forward. If you are not yet on Update 1, then there are more steps required. Others have documented the steps well, and some good examples are here and here.
The steps are identical for vCenter appliance and the PSC appliance.
Let’s start with the PSC. I don’t think the order matters since this is just a minor update. However, the manual says that “Before you update a vCenter Server with an external PSC, you must apply the patches to the PSC and its replicating partners, if any in the vCenter SSO domain. ”
The VMware ASEAN Lab has 2 external PSC VMs in a single domain. Since this is the setup, let’s start with the first PSC, before we do its replicating partner.
You can do the update via CLI or UI. I’ll do the UI one here to give you the screenshots. Login at root (not email@example.com) to the address https://Your-PSC-address:5480/
I had configured my vCenter to automatically check when I updated it to Update 1. So it’s a pleasant experience to see that it has detected the update. Notice the build number matches. There is a KB article linked to it, which gives a bit more info, such as the size of the update (1.5 GB). At 1.5 GB, this will take a while to complete.
To update, simply click on the Install Updates link and follow the wizard.
Example of third-party products are JRE, tcServer, and SLES OS components. Proceed to update, and you will see the familiar progress below. Click on Show Details to see the actual commands executed. The last status is shown at the top. So if you want to see from the beginning, scroll down. The Stage Packages step took 5 minutes in my case for a PSC and 28 minutes for vCenter. It is safe to click the browser refresh button.
The longest step is the Pre install scripts. In my case, this has been running for >10 minutes.
I had to go and pick up my wife at the airport, so I left the upgrade. When I’m back, it’s already done. This is what it should look like. Notice the build number and release date matches the release notes.
And that’s it! You then repeat for the other replicating PSC in the domain. Once done, you do the same steps for the vCenter.
You might be curious how the update impacts the load on the PSC VM. This VM is a 2 vCPU. As you can see below, the spike is minimal. The CPU Run hit 10348 for 20 seconds, which is around 25% as this is a 2 vCPU (max is 40000).
Let’s look at Storage. The spike t 5:20 pm is the time I did the update. It’s below 300 IOPS for each read or write.
If you want to configure the auto update, simply click on the Settings button. It checks for a weekly update, which is reasonable in most cases
BTW, the PSC also has the https://Your-PSC-address/psc address, while the vCenter only has the https://Your-PSC-address:5480/. The /psc requires the firstname.lastname@example.org, not root. When you login, you get the screen below.
From here, there is a link to the https://Your-PSC-address:5480/ address
Happy updating! FYI: the 2 vCenter and 2 PSC got updated successfully. Didn’t hit any error.