VCF Upgrade from 5.0 to 5.2

Following the previous blog where we uploaded all the bundles of to upgrade the VCF Management Workload Domain offline, I started running the prechecks for the upgrade and the below was the result:

Since this is a test and nested environment, I silenced the precheck alarm

For the vSAN HCL DB

I followed this KB https://knowledge.broadcom.com/external/article/315556/updating-the-vsan-hcl-database-manually.html to update the HCL DB Manually

And for the vCenter Backups,

I initiated a backup job from the vCenter VAMI and it was successful,

Now rerunning all the failed tasks,

Prechecks passed successfully, the next step is to apply the bundles

I’ll start updating now and the below order, is the order for the upgrade:

SDDC Manager

NSX

vCenter

ESXi

The upgrade is now in progress and started with SDDC

The upgrade of the SDDC Manager has now completed successfully

Next Step is to upgrade NSX Manager

Since I don’t have Edge Clusters deployed the NSX Manager upgrade should be smooth

NSX Manager upgrade is now in progress

NSX Manager is completed successfully.

The next step is to upgrade vCenter

vCenter Upgrade is now successful

Final Step is to upgrade ESXi hosts,

In the wizard below, there are couple of options to customize the upgrade options, I’ll use the default ones

Last Step went smooth, which was upgrading the ESXi hosts:

Offline Bundle Transfer Utility

In this blog we’ll discuss how to use the offline bundle transfer utility of VCF to upload install bundles to SDDC Manager in order to prepare for a VCF upgrade from VCF 5.0 to VCF 5.2, the offline bundle transfer utility is useful in case the SDDC manager doesn’t have internet access which is the case in air gapped environment.

The pre-requisites below are required for running the utility:

  • A Windows or Linux computer with internet connectivity (either directly or through a proxy) for downloading the bundles
  • The computer must have Java 8 or later
  • A Windows or Linux computer with access to the SDDC Manager appliance for uploading the bundles
  • To upload the manifest file from a Windows computer, you must have OpenSSL installed and configured ( what I did is I copied the files required to the SDDC Manager appliance using WinSCP after downloading them using the utility, this will be later explained)

First step I downloaded the bundle transfer utility from Broadcom Customer Support Portal

There Utility tool will be used in 2 locations, the PC where the manifest and compatibility files are downloaded as well as in the SDDC Manager,

So first is to extract the OBTU in my PC, which looks like the below:

Second to upload it to the SDDC Manager appliance via WinSCP

I copied it in the same location as suggested in the official documentation where I followed the below steps:

  • mkdir /opt/vmware/vcf/lcm/lcm-tools
  • tar -xvf lcm-tools-prod.tar.gz
  • cd /opt/vmware/vcf/lcm/
  • chown vcf_lcm:vcf -R lcm-tools
  • chmod 750 -R lcm-tools

One issue I was failing on using the utility from my PC was this :

Which I fixed by modifying by changing the default Java 8 installation location to a different folder than the default and modifying the JAVA_HOME environmental variable in my Windows PC

We need to download 3 files from the depot which are

  • Manifest file
  • Compatibility data
  • vSAN HCL file

To download the manifest file:

To download the compatibility data file:

To download the vSAN HCL file:

Finally download the install bundles, I’m upgrading my lab from VCF 5.0 to VCF 5.2 so below are the steps I followed to download the install bundles

Using this command “lcm-bundle-transfer-util –download –outputDirectory C:\Hisham\VMware\VCF\5.2 –depotUser xyz@gmail.com –sv 5.0.0.0 –p 5.2.0.0”

And I selected All, notice here that Avi Controller is now available as part of the VCF 5.2 BOM is this is a new feature to lifecycle Avi Controllers from SDDC Manager ( this is available in VCF 5.2) previously it was a manual installation.

Next is to update the manifest file and Compatibility Matrix file in the SDDC Manager appliance. I uploaded the 3 files downloaded in the previous steps to the SDDC Manager appliance

To update the sourceManifest file , I ran the below command in the SDDC Manager appliance, however I used to get couple of unexplained failures prior to that and the reason is the path of the file need to look something like the below

Not sure the reason behind it, but it had the same path when I downloaded it on my PC so I followed the same path.

Next, I did the same for the compatibility matrix file:

And when I tried to update the vSAN HCL file I got the below error:

ERROR: Cannot upload vSAN HCL to SDDC Manager versions below 5.1.0.0 so probably the one downloaded was not up to date,

Last but not least is to upload the offline bundles downloaded earlier to SDDC Manager

/opt/vmware/vcf/lcm/lcm-tools/bin ]$ ./lcm-bundle-transfer-util –upload –bundleDirectory /nfs/vmware/vcf/nfs-mount/newbundles/

However I noticed when trying to update all bundles on SDDC Manager that only NSX gets uploaded, so instead I uploaded each bundle at time, not sure the reason behind this.

As per the below, the offline bundles are uploaded successfully to the SDDC Manager:

On clicking Plan for Upgrade the below message was showing:

Found this KB for it :

https://knowledge.broadcom.com/external/article/374197/failed-to-find-product-type-for-id-789-w.html

Next step is to run the upgrade precheck:

In the next Blog , We’ll check the upgrade status and start upgrading the Management Workload Domain