VCF Operations for Logs

Deploying VCF Operations for Logs 9.0.1.0 in VCF 9

Time to get fresh install of VCF Operations for Logs 9.01.0 installed in the homelab. Going to start this off with the assumption that the Online or Offline Depot is configured and you have downloaded required binaries from Binary Management.

From the VCF Operations console >> Fleet Management >> Lifecycle >> VCF Management >> Binary Management

You will Install, Patch and Upgrade binaries.

When the downloads complete, click ‘Overview’ under VCF Lifecycle and we will locate Operations for Logs and click ‘Add’

For this deployment, because it’s my homelab, a single appliance will suffice, however for production it’s recommended you have a minimum of 3 to form a cluster. You can read more about preparations here; VCF Operations for Logs Detailed Design

On the next step, you can generate a certificate containing the FQDNs and IPs for your appliances.

Populate Infrastructure Deployment details, and click Next

Populate general network IP information; Domain, Domain Search Path, DNS, NTP, Gateway and subnet for the appliance.

The next step is to fill out the Components section and there are too many options to list, but ensure to have IPs for your cluster and VM appliance as well as other settings.

Pre-Check successful, let’s get it!

The final screen will be a confirmation, download the settings and even view what the topology will look like.

Success.

VCF

Patching VCF Fleet Appliance to 9.0.1.0

From the VCF Operations console go to Fleet Management >> Lifecycle >> VCF Management and a banner appeared informing you of an upgrade. Click ‘Learn More’

You will see there are no updates available and another symptom I ran into is when trying to download any VCF Operations 9.0.1.0 binaries, I receive the following error

LCMCOMMON92001

Quick Google Search and found a Community Article, shout out to the community member for pointing out the System Patches section. download fails with Error Code: LCMCOMMON92001 | VMware Cloud Foundation

Back into VCF Management under ‘Patch Binaries’ there is a ‘fleet management’ patch available, select and click Download

Navigate to the System Patches section under VCF Management and click ‘New Patch’ This should take you to the patch that was just downloaded.

Ensure to use the ‘Create Snapshot’ feature to take a snapshot of the Fleet Management appliance.

Select the patch and click Next.

Proceed with Review and click ‘Install’ The Fleet appliance should go offline and the VCF Management pane may not show available for a brief moment.

Done..

VCF

Upgrading a vCenter 8.x Workload Domain to 9.0.1.0 in VCF Operations – Part 1

In my previous blog I wrote up the process of importing a vCenter instance while on version 8.x. My next venture is getting it upgraded to VCF 9, this would be vCenter, ESX & NSX.

Now that the domain is part of my VCF Fleet, from the VCF Operations console, go to Fleet Management >> Lifecycle >>

You can see the there is a different icon for the Workload Domain GENAPP

To the right side there is a Configuration Update available.

Upon completion, checked the vCenter and it created a new DVPG, tagged with the correct VLAN and then made the pg Ephemeral

We can move to Plan Upgrade or Plan Patching located under ‘Available Updates’, let’s see what Plan looks like

There is our build out, which we can also customize.

Finally, summary of steps being performed

The next step is Configuring and Scheduling the Upgrade.

Jump to Part 2 – https://khizeran.com/2025/10/24/upgrading-a-vcenter-8-x-workload-domain-to-9-0-1-0-in-vcf-operations-part-2/

Jump to Part 3 – https://khizeran.com/2025/10/24/upgrading-a-vcenter-8-x-workload-domain-to-9-0-1-0-in-vcf-operations-part-3/

VCF

Upgrading a vCenter 8.x Workload Domain to 9.0.1.0 in VCF Operations – Part 2

In a previous blog I covered importing a vCenter instance with a single cluster see here. and if you go to Part 1 of the blog, I covered performing a configuration update needed for the newly imported Workload domain.

The next step is to go back into Lifecycle for the Workload Domain and Configure Update

The wizard for the NSX Precheck will begin, click Next. In my homelab, I have no Edge clusters configured so clicked Next and straight to Run Precheck.

Once the Precheck completes, we can then move forward with performing a Schedule Update and that will give you an option to perform right away or schedule at a later time.

Once the update has kicked off, you can click ‘View Status’ and collapse to view all the components

Hey! Look at that, Step 1 is complete..onto Step 2. Click ‘Configure Update’

This next step will be upgrading a vCenter Server appliance from 8.0 u3 to 9.0. Because this is a single vCenter, we can leverage the Reduced Downtime Feature, but in this case, we will go straight into it.

Confirm Backup

Provide a temporary IP address for the new vCenter (No DNS record required, however optional if you want to reserve for future use.

Schedule the update and switchover options, we’re going for Immediate. The final step is reviewing everything and then proceed.

vCenter upgrade completed!

VCF

Upgrading a vCenter 8.x Workload Domain to 9.0.1.0 in VCF Operations – Part 3

Welcome to the 3rd and final part of this installment of Upgrading a vCenter 8.x Workload Domain to 9.0.1.0 in VCF Operations.

Part 1 – https://khizeran.com/?p=5239

Part 2 – https://khizeran.com/?p=5258

Now that vCenter has been upgraded to 9.0.1, next step is ESX hosts to 9.0.1

You might need to disable DRS VM/Host affinity rules placed when NSX was deployed on the cluster. Re-enable after completion.

Before we ‘Configure Update’ we have to jump into vCenter and create an Image.

Go to the Stack Menu >> Lifecycle Manager >> Image Library and click ‘Create Image’

Provide a unique image name and select the targeted ESXi version. Your environment will vary. Click Validate & Save.

Now it’s saved, we can go into VCF Operations and Import the Image.

Under Fleet Management >> Lifecycle >> click to highlight org name

Import from a vCenter and select the image created earlier, click Import. **This will take some time to finish as a task for the import will be running.**

This task did error out for me because I had an image already with that ESXi build, so resorting to using existing one.

Under Fleet Management >> Lifecycle >> Select the Workload Domain and click ‘Configure Update’

Click ‘Next’ at the Cluster Precheck screen, then select the cluster to be updated

Select the cluster and click ‘Assign Image’

Select Image and click ‘Assign Image’

I un-checked all Upgrade Options and click Next, and then ‘Run Precheck’

The Precheck completed, I have some warnings being this is consumer hardware, Exit Details and then we proceed with schedule.

Click ‘Schedule Update’ run through the prompts of verifying the upgrade and scheduled for ‘Upgrade Now’.

We’re off to the races..

Everything completed successfully, there is our versions. Came a long way from 8.x 🙂