SDDC Lifecycle selected in VCF Operations with the upgrade path from 9.1.0.0400.25570103 to 9.1.1.0.25713940.

Upgrading VCF SDDC Lifecycle to 9.1.1 Step by Step

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. ...

 · Updated  · 
Upgrading VCF SDDC Lifecycle to 9.1.1 Step by Step
VCF Services Runtime ready for upgrade from 9.1.0.0200.25555874 to 9.1.1.0.25714471 in VCF Operations.

Upgrading VCF Services Runtime to 9.1.1 Step by Step

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. ...

 · Updated  · 
Upgrading VCF Services Runtime to 9.1.1 Step by Step
Fleet Lifecycle in VCF Operations showing current version 9.1.1.0.25713934 after the upgrade.

Upgrading VCF Operations Fleet Lifecycle to 9.1.1 Step by Step

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. ...

 · Updated  · 
Upgrading VCF Operations Fleet Lifecycle to 9.1.1 Step by Step
VCF Operations System Status showing a successful upgrade and an online 9.1.1 cluster.

Upgrading VCF Operations to 9.1.1 Using a .PAK File

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. ...

Upgrading VCF Operations to 9.1.1 Using a .PAK File

Updating ESXi with the Authenticated Broadcom Depot or an Offline Bundle

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. ...

Updating ESXi with the Authenticated Broadcom Depot or an Offline Bundle

Safely Removing an SDDC Manager-Deployed NSX Edge Cluster from VCF

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. ...

Safely Removing an SDDC Manager-Deployed NSX Edge Cluster from VCF

VMSA-2025-0004: Current Remediation and Fixed Versions

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. ...

VMSA-2025-0004: Current Remediation and Fixed Versions

Safely Removing Stale NSX VIBs from an ESXi Host

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. ...

Safely Removing Stale NSX VIBs from an ESXi Host

Safely Canceling and Deleting Alerts with the VCF Operations API

The VCF Operations API uses different payloads for finding, canceling, and deleting alerts. Treating those operations as interchangeable can either fail validation or broaden a cleanup beyond the alerts you intended to remove. This follow-up corrects the API section in Bulk Delete Alerts in VCF Operations. The safe sequence is: Query candidate alerts without changing them. Review every returned alert ID and account for pagination. Cancel only the approved IDs with a uuid-values body. Verify those IDs are now CANCELED. Delete the same IDs with a direct AlertQuery body. Query again to confirm that they are gone. Before You Begin Fix or tune the alert definition first. Deleting alert history does not stop the condition from generating new alerts. Use a VCF Operations account whose application role and object scope permit the required alert operations. Take any database backup required by your change policy before a large cleanup. Start with one small batch. The API documents a default query page size of 1,000, so a single response is not proof that you found every match. Use a trusted certificate. The examples intentionally do not bypass TLS verification. Set the appliance name, create a private working directory, and read an existing session token without placing it in shell history. Store the authorization header in a mode-600 file so the token is not expanded into each curl process argument, then remove it as soon as the cleanup is verified: ...

Safely Canceling and Deleting Alerts with the VCF Operations API

Using a 90-Day Planning Horizon Correctly in VCF Operations

A 90-day capacity goal can describe three different things in VCF Operations: past demand used by the projection, future warning lead time, or the future period considered by VM rightsizing. They are controlled separately. This article replaces the earlier 90-day capacity procedure, which incorrectly treated Time Remaining thresholds as a historical lookback setting. The Three Meanings of 90 Days Planning question Relevant control What it does not control Should the forecast consider up to 90 days of past demand? Historical Data window, if that value is available in the installed build Alert severity or procurement lead time Should an alert become critical when exhaustion is projected within 90 days? Time Remaining criticality thresholds Historical lookback Should Recommended Size cover demand projected across a 90-day future horizon? The applicable Time Remaining warning/green threshold plus the documented 30-day extension Past-data retention Changing one row does not configure the other two. ...

Using a 90-Day Planning Horizon Correctly in VCF Operations