Applying VCF 9.1.1 Express Patch 2 to your VCF Management Domain
We recently released VCF 9.1.1 Express Patch 2, Release Notes can be found here. For a review of VCF Express Patches check out William Lam's blog on the topic here. There is a nice KB available here as well, which details VCF versioning.
In this blog we will be applying Express Patch 2 to our VCF 9.1.1.0100 Management Domain Fleet Components. For details on the content of VCF 9.1.1.0200 go here.
I used the VCF Planner to plan my upgrade, here's what it provided.
Before starting any of this, make sure your Software Depot is connected so you have access to the necessary binaries.
As you can see my environment is at 9.1.1.0100.
The first step to applying Express Patch 2 is to upgrade Fleet Lifecycle.
Click the three dots next to UPGRADE and select the Target Version, this is what you'll be upgrading to.
Click SET TARGET VERSION.
You can now see what Fleet Lifecycle will be upgraded to. Click UPGRADE and you'll see the Upgrade in progress.
You can watch the progress in the Tasks tab.
Once complete it will look like this (it took about 60m).
Back on the Upgrade tab you'll notice Fleet Lifecycle has now been upgraded.
Once complete it's a best practice to perform a Lifecycle Metadata Sync.
We're done with the first step in our plan.
Next we'll upgrade VCF Operations. Go to Build - Lifecycle - VCF Management - Upgrade - SELECT VERSION - CUSTOMIZE PATCH VERSIONS and select the 9.1.1.0100 Target Version from the dropdown for VCF Operations.
Once selected click SET VERSION. You can then click RUN PRECHECKS to confirm prerequisites.
Assuming all pre-checks pass, you can then upgrade by selecting VCF Operations and clicking UPGRADE.
Once done it will look like this.
Back on the Compnents tab you'll notice now both Fleet Lifecycle and VCF Operations have been upgraded.
You'll notice in the VCF Planner instructions it tells us to upgrade Management Services Runtime before pathcing vIDB and/or Salt Component, so let's do that now.
Go to Build - Lifecycle - VCF Management - Upgrade - SELECT VERSION - CUSTOMIZE PATCH VERSIONS and select the 9.1.1.0100 Target Version for the VCF Services Runtime Component.
Click SET VERSION, then click RUN PRECHECKS.
Once done select the VCF Services Runtime you want to upgrade and click UPGRADE (ignore the other instance you see in this lab).
Once done you'll see it in the Tasks tab.
Back on the Components tab you'll notice that VCF Services Runtime has been upgraded, along with Fleet Lifecycle and VCF Operations which we did previously. Keep in mind that not all will show 9.1.1.0200 due to different versions of each technology being included in Express Patch 2.
Back to the VCF Planner, which indicates VCF Automation must be patched before the VCF Migration Service.
Let's do that now. Go to Upgrade - SELECT VERSION - CUSTOMIZE PATCH VERSIONS and select the 9.1.1.0200 version for VCF Automation.
Click SET VERSION.
Select VCF Automation and click RUN PRECHECKS and one complete click UPGRADE.
Once complete it will look like this in the Tasks tab.
Next we'll upgrade the Migration Service Engine (which doesn't show as a Component on the Components tab). Go to Upgrade - SELECT VERSION - CUSTOMIZE PATCH VERSIONS and select the 9.1.1.0200 Target Version.
As we've done a few times now, click the RUN PRECHECK then click UPGRADE, and confirm it finishes in the Tasks Tab.
At this point we've completed the following:
Fleet Lifecycle (9.1.1.0200)
VCF Operations (9.1.1.0100)
VCF Services Runtime (9.1.1.0100)
VCF Automation (9.1.1.0200)
Migration Service Engine (9.1.1.0200)
Next we'll update the Software Depot the same way we've done the others, I won't go through these step-by-step.
Next up is the Identity Broker.
Next up is the Salt RaaS and Salt Master Components.
Next up is Log Management.
Next is the Telemetry Component.
Next are the Real-time Metrics and Real-time Metrics Store Components. We'll do these concurrently.
Next up is VCF Operations for Networks.
The last Component to be done is SDDC Lifecycle.
We've now patched Fleet Lifecycle and all it's Components.
In our next blog we'll contine on with SDDC Manager, vCenter/s, NSX and ESX. Hope this was helpful!
Comments