Upgrading VMware Cloud Foundation from 9.0.2 to 9.1 sequence and execution guide

Products

• VCF Automation

Issue/Introduction

• When performing a major upgrade of a VMware Cloud Foundation (VCF) environment from version 9.0.2 to 9.1, standard automated binary management in legacy interfaces does not display 9.1 release binaries automatically. Administrators require a structured, multi-phase sequence to properly upgrade management components, initialize new VCF Management Services (VCMS) runtime components, and align workload domain services.

Environment

 

• Product: VMware Cloud Foundation

• Version: 9.0.2 upgrading to 9.1

 

Cause

• VCF 9.1 introduces a decoupled binary management architecture and a new unified service-oriented runtime (VCF Management Services / VCMS). Because 9.1 binaries are not automatically populated in legacy 9.0.x interfaces, manual package upload and strict phase execution are required to transition from the legacy architecture to the 9.1 framework.

Resolution

Execute the VCF 9.0.2 to 9.1 upgrade adhering to the following phase sequence:

Phase 1: Manual Upgrade of VCF Operations

1. Obtain the VCF Operations 9.1 upgrade PAK file from the Broadcom Support Portal.

2. Log in to the VCF Operations Administration Interface at https://<primary-node-FQDN-or-IP-address>/admin.

3. Navigate to Software Update and upload the 9.1 PAK file.

4. Perform the cluster state management sequence:

   • Navigate to the System Status Page.

   • Take the cluster offline.

   • Take image-based snapshots of all primary nodes.

   • Bring the cluster back online. (Note: The cluster must be fully online before installation starts).

5. Click Next, then Install.

6. Upon completion, verify that VCF Operations and all Cloud Proxies report version 9.1.

Phase 2: SDDC Manager Lifecycle Upgrade

1. Access Build -> Lifecycle -> VCF Instance -> MGMT Domain -> SDDC Manager Updates.

2. Run environment prechecks.

   • vSAN Precheck Note: If using an external storage provider instead of vSAN, acknowledge and manually override the expected vSAN precheck failure only after validating external storage.

3. Take a snapshot of the SDDC Manager VM.

4. Click Update Now and monitor progress until SDDC Manager displays version 9.1.0.

Phase 3: Deployment of VCF Management Services (VCMS)

1. Ensure the Software Depot contains all 9 required sub-components:

   • VCF Services Runtime

   • Fleet Lifecycle

   • SDDC Lifecycle

   • Software Depot

   • Identity Broker

   • Salt RaaS

   • Salt Master

   • Telemetry

   • License Server

2. Reserve a dedicated IP block for VCMS with all lower-case FQDNs:

   • Minimum: /28 CIDR block (12 IP addresses).

   • Recommended: /27 CIDR block (30 IP addresses).

3. In SDDC Manager, navigate to Build -> Lifecycle -> VCF Instance -> SDDC Manager Upgrade tab.

4. Select Available Upgrade and click Install for VCF Management Services.

5. Input the VCF Operations FQDN, administrative credentials, reserved IP range, and lower-case FQDNs.

6. Confirm deployment completion (verifying 4 new VMs and the License Server in inventory).

Phase 4: Workload Domain and Advanced Component Upgrades

1. Upgrade components in the strict required sequence:

   1. VCF Identity Broker (VIDB): Migrates legacy identity systems into the VCF Services Runtime IAM framework.

   2. VCF Automation (VCFA): Upgrade after Identity Broker migration finishes.

   3. VCF Operations for Networks and Logs: Upgrade to align with 9.1 standards.

2. Register license management via the new central License Server:

   • Connected Mode: Automatic transfer.

   • Disconnected Mode: Manually register with the VCF business service console.

Phase 5: Core Infrastructure Lifecycle

1. Proceed with standard lifecycle updates for core infrastructure:

   • NSX Manager

   • vCenter Server

   • ESXi Hosts

   • NSX Edge Cluster nodes

Additional Information

Techdocs: https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-1/deployment/upgrading-cloud-foundation.html