Articles — Page 2

With VCF 9.1.1 released on September 3, 2026, I wanted to continue patching the management services in my lab. This post is a follow-up to my VCF 9.1 management services upgrade walkthrough and focuses on Real-Time Metrics through VCF Operations. VCF 9.1.1 is a maintenance release focused mostly on improving product supportability. The VCF 9.1.1 release notes include the Bill of Materials, upgrade sequence, dependencies, known issues, and the component build numbers. The VCF Operations 9.1.1 release notes list Real-Time Metrics at build 25679622. ...

With VCF 9.1.1 released on September 3, 2026, I wanted to continue patching the management services in my lab. This post is a follow-up to my VCF 9.1 management services upgrade walkthrough and focuses on Log Management through VCF Operations. VCF 9.1.1 is a maintenance release focused mostly on supportability improvements. The main VCF 9.1.1 release notes and the VCF Operations 9.1.1 release notes are the references I used for this upgrade. In VCF 9.1, Log Management is a VCF management service hosted on the VCF services runtime. The supported lifecycle workflow is therefore in VCF Operations under Build -> Lifecycle -> VCF Management -> Upgrade. This walkthrough covers a 9.1.0.x maintenance upgrade; an environment coming from an older VCF or Aria release should follow the matching Log Management upgrade procedure first. ...

With VCF Services Runtime upgraded to 9.1.1, the next component I wanted to upgrade in my lab was SDDC Lifecycle. In this post I will go over upgrading it from 9.1.0.0400 to 9.1.1.0 through VCF Operations. VCF 9.1.1 was released on September 3, 2026. This is a maintenance release focused mostly on supportability improvements. The release notes can be found here. Before You Begin For an existing 9.1.0.x environment, upgrade Fleet Lifecycle to 9.1.1 first, before any other VCF component. In my lab it is already on 9.1.1.0.25713934. Continue to follow the release-specific dependencies in the 9.1.1 release notes when planning the remaining components. ...

With Fleet Lifecycle upgraded to 9.1.1, the next component I wanted to upgrade in my lab was VCF Services Runtime. In this post I will go over upgrading it from 9.1.0.0200 to 9.1.1.0 through VCF Operations. VCF 9.1.1 was released on September 3, 2026. The release notes can be found here. The runtime fixes listed in the VCF Operations release notes include improvements for mixed-case FQDNs, services recovering after a cluster power-on, and log buffers filling the logging disk. ...

With the release of VCF 9.1.1 on September 3, 2026, I wanted to get Fleet Lifecycle in my lab upgraded. This is a maintenance release focused mostly on supportability improvements. The release notes can be found here. In this post I will go over upgrading Fleet Lifecycle through VCF Operations, from 9.1.0.0400 to 9.1.1.0. Before You Begin For an existing 9.1.0.x environment, Broadcom requires us to upgrade Fleet Lifecycle to 9.1.1.0 before any other VCF component. Make sure to follow the 9.1.1 release-specific dependencies when planning the rest of the upgrade. ...

With the release of VMware Cloud Foundation 9.1.1 on September 3, 2026, I wanted to get my VCF Operations lab upgraded. This is a maintenance release focused mostly on supportability improvements. The VCF 9.1.1 release notes can be found here, and the VCF Operations release notes are here. In this post I will go over upgrading VCF Operations from 9.1.0.0400 to 9.1.1 using the upgrade PAK file. If you are still on an older release, I also covered upgrading VCF Operations to 9.0.1 using a PAK file. That is a separate walkthrough, not a required intermediate upgrade. ...

This is the corrected follow-up to my earlier ESXi command-line upgrade articles. The shared public VMware host-update depot used in those examples is no longer valid. Broadcom now uses customer-specific authenticated download URLs, and its current standalone command-line procedure documents an offline depot ZIP with esxcli software profile update. The procedure and release information below were reviewed on August 25, 2026. Reopen the linked Broadcom articles during every change: depot authentication, entitlements, available profiles, release builds and support status can change. ...

This is the corrected follow-up to my older article about simplifying NSX Edge removal in VCF. The most important correction is that the Edge Cluster Deployment Removal Tool does not preserve everything attached to an Edge cluster. Broadcom requires added dependencies to be removed or disconnected before the cleaner runs. The procedure below is based on Broadcom KB 316110, reviewed on August 25, 2026. Always reopen the KB before a change because the attachment, checksum, prerequisites, and supported releases can change. ...

Broadcom published VMSA-2025-0004 on March 4, 2025, for three vulnerabilities affecting VMware ESXi and related desktop and cloud products. Fixed versions are available, and the advisory lists no workarounds for any of the three vulnerabilities. The practical response is therefore straightforward: identify every affected product, move it to a fixed or later supported build using its supported update method, and verify the resulting build. Access restrictions and monitoring remain useful defense-in-depth controls, but they do not replace the update. ...

This post replaces the unsafe package-removal command that appeared in my older article about removing stale NSX packages from an ESXi host. Broadcom now documents a clear distinction between removing NSX through its management workflow and cleaning up VIBs that remain afterward. Warning: Do not manually remove individual NSX VIBs with esxcli software vib remove. Broadcom identifies that method as unsupported. It can break distributed-switch state, disconnect host networking, and in some failure cases leave reimaging as the recovery path. ...