VMware Infrastructure Administration Guides

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

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

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

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

If you’re moving vCenter Server from 8.0 U3x to 9.1.0.0 (typically as part of a VCF 9.1 deployment or a VVF 9.1 upgrade) the run can fail partway through with: Error attempting Upgrade Database Schema Please check vcintegrity migration logs for details. This is one of those failures that looks scary in the UI but has a clean, well-understood root cause: a handful of orphaned rows in the vcIntegrity database that trip a new foreign-key constraint introduced in 9.1. Below is the whole story; what the error means, how to read the logs, why it happens, and how to clear it so the upgrade completes. It’s the same shape of problem I wrote about in fixing PostgreSQL on Fleet Management 9.0.1: a schema change colliding with pre-existing data. ...

If you have upgraded your VMware Cloud Foundation (VCF) environment to version 5.x from an earlier release, you may find yourself unable to update BOM (Bill of Materials) components from the SDDC Manager UI. The “Update Now” or “Configure Update” button is greyed out and you see a frustrating error: “Update cannot be started now as compatibility file is missing” This post walks through the symptoms, root cause, and the step-by-step fix based on Broadcom KB 396202. ...

If you’ve been working with VCF Operations 9.1, you may have noticed that on the Build > Lifecycle > VCF Management > Components page, manually-added components such as VCF Operations for Networks, Log Management, Real-Time Metrics or VCF Automation no longer have a “Delete” option available in the UI. In VCF Operations 9.0, this was possible on the Fleet Management > Lifecycle > Components page by clicking the three vertical dots next to a component and selecting Delete. That option is gone in 9.1. ...

If you need to pull log events programmatically from VMware Aria Operations for Logs (formerly vRealize Log Insight), filtering by a specific hostname, this guide walks you through the entire process, from authentication to querying the powerful internal API endpoint. This approach is inspired by Brock Peterson’s excellent series on the Aria Operations for Logs API, expanded here with full session authentication steps and hostname-specific query examples. Prerequisites Before we begin, you’ll need: ...

In a previous post I covered how to configure VCF Operations 9 to use 90 days of usage data for rightsizing recommendations. That gives you a solid foundation, but once you start reviewing the recommendations, you will quickly notice that the engine does not enforce any organizational sizing standards. For example, the engine might recommend reducing a VM from 8 vCPUs to 5, or suggest removing just 1 GB of RAM. Both are technically valid from a demand perspective, but in practice: ...

As organizations adopt VMware Cloud Foundation 9.0, a common question comes up: what do I do with my existing vCenter 8.x environments? The good news is that VCF 9.0 supports backwards compatibility with 8.x vCenter instances. You can import them as workload domains directly from the VCF Operations console, bringing your legacy infrastructure under VCF management without rebuilding from scratch. In this post I will walk through the full import process (from prerequisites and networking requirements to NSX deployment and validation) so you know exactly what to expect before you hit the “Import” button. ...