Academy/VCF Evolution: Version History & Migration Paths (2.x → 9.0)
VCF

VCF Evolution: Version History & Migration Paths (2.x → 9.0)

VCF 9.0vcdx-distinguished

Understand the evolution of VMware Cloud Foundation from initial SDDC concepts through VCF 9.0's paradigm shift to unified operations. Trace feature maturity, licensing changes, and upgrade paths for brownfield migrations.

Version Evolution

This section uniquely spans VCF 2.x through 9.0.x. The version timeline topic covers all major releases. Upgrade path content focuses on 5.2→9.0 as the most relevant current migration. Brownfield adoption covers converting existing vSphere estates — the most common real-world scenario.

Learning Outcomes

  • Trace VCF evolution from 2.0 through 9.0 and articulate the key paradigm shifts at each major version
  • Plan a VCF 5.x→9.0 upgrade (sequential or skip-level from 5.0+) including pre-checks, the management-planes-first sequence, and rollback strategy
  • Design a brownfield VCF adoption plan for an existing vSphere environment
  • Explain the licensing evolution from socket-based to core-based to Broadcom subscription model
  • Identify the top 5 upgrade failure modes and their mitigations

VCF Evolution: Detailed Version Map and Paradigm Shifts#

VCF Version Timeline (release dates and bills of materials from Broadcom KB 314608, 'Correlating VMware Cloud Foundation version with the versions of its constituent products', updated Sep 2026, and the VCF 5.2 / 9.0.x release notes)

EraRelease (GA)Hypervisor / vCenterNSXManagement stackWhat changed
VCF 3.x3.10 (26 May 2020) … 3.11.0.1 (11 Apr 2022)vSphere 6.7 U3NSX-V 6.4.x; NSX-T 3.0.3 alongside from 3.11Cloud Builder + SDDC Manager; vRealize Suite Lifecycle Manager 2.xLast NSX-V-based line; NSX-V reached end of support, so 3.x estates had to migrate to NSX-T on the way to 4.x
VCF 4.x4.0 (14 Apr 2020) → 4.5.2 (17 Aug 2023)vSphere 7.0 → 7.0 U3NSX-T 3.0 → 3.2.3Cloud Builder + SDDC Manager; vRealize Suite (vRSLCM 8.x) — from 4.4 vRealize upgrades run through vRealize Suite Lifecycle Manager and leave the VCF BOMNSX-T only; vSphere with Tanzu (Workload Management) arrives with vSphere 7; Federation support
VCF 5.x5.0 (01 Jun 2023), 5.1 (07 Nov 2023), 5.2 (23 Jul 2024), 5.2.1 (09 Oct 2024), 5.2.1.1 (05 Dec 2024), 5.2.1.2 (30 Apr 2025), 5.2.2 (05 Sep 2025), 5.2.3 (24 Feb 2026), 5.2.4 (27 May 2026)vSphere 8.0 U1a (5.0) → 8.0 U2 (5.1) → 8.0 U3 (5.2) → 8.0 U3j (5.2.4)NSX 4.1.0 (5.0) → 4.1.2 (5.1) → 4.2.0 (5.2) → 4.2.4 (5.2.4)Cloud Builder + SDDC Manager; Aria Suite Lifecycle 8.10 (5.0) → 8.14 (5.1) → 8.18 (5.2) gating the Aria productsvRealize renamed Aria; VCF Import Tool (5.2) for brownfield convert/import; vSAN ESA stretched clusters on vSAN ReadyNodes from 5.2 (VCF on Dell VxRail from 5.2.1.1); the last Cloud Builder line
VCF 9.0.x9.0 (17 Jun 2025), 9.0.1 (29 Sep 2025), 9.0.2 (20 Jan 2026)ESX 9.0 / vCenter 9.0NSX 9.0VCF Installer (replaces Cloud Builder, becomes SDDC Manager); SDDC Manager 9.0 (UI deprecated); VCF Operations 9.0 with the fleet management appliance; VCF Automation 9.0; VCF Identity BrokerPrivate cloud / fleet / instance / domain hierarchy; VCF Operations as the console; vSAN ESA default; per-core subscription licensing
VCF 9.1.x9.1.0 (12 May 2026), 9.1.1 (03 Sep 2026)ESX 9.1 / vCenter 9.1NSX 9.1VCF management services runtime hosting the lifecycle and operational componentsSee the VCF 9.0 → 9.1 delta section of this Academy for the 9.1 changes

Version numbers 6, 7 and 8 were never used for VCF: the product jumped from 5.x to 9.0 to align with the vSphere, vSAN and NSX 9.0 release numbers.

Upgrade Compatibility (documented)

FromToRule
Any VCF 5.0 or later9.0.xSequential or skip-level upgrade is supported (VCF 9.0 Management Domain Upgrade Overview). The management planes (VCF Operations and the fleet management appliance) are upgraded or deployed first, then the core components per instance
Below 5.0 (3.x, 4.x)9.0.xUpgrade the management domain and every workload domain to VCF 5.0 or later first, then to 9.0
5.x5.2.xSequential or skip-level upgrades are supported within the 5.x line (5.2.1, 5.2.2 and 5.2.3 release notes)
3.x4.xSequential upgrades through the documented 3.x → 4.x path, with the NSX-V to NSX-T migration as a separate project

There is no mandatory stepping stone at 5.2: a 5.0 or 5.1 estate may upgrade directly to 9.0. VCF 5.2.x remains in support in parallel (5.2.4 shipped in May 2026) for estates that stay on the Cloud Builder/SDDC Manager model.

Paradigm Shifts

NSX-V to NSX-T (VCF 4.0, April 2020)
VCF 4.0 shipped NSX-T 3.0 with vSphere 7.0 and dropped NSX-V for new deployments; 3.x estates ran a separate NSX-V to NSX-T migration before moving to 4.x. Design impact: Tier-0/Tier-1 gateway model, Geneve overlay and a REST/Policy API replaced the NSX-V DLR/ESG model and its vCenter-centric tooling.
Kubernetes on VCF (VCF 4.0 onwards)
vSphere with Tanzu (Workload Management) arrived with vSphere 7 in VCF 4.0 and evolved into the vSphere Supervisor with VKS clusters in 9.0. Design impact: one platform serves VMs and containers; namespaces and VKS clusters consume vSAN through storage policies and NSX through the Supervisor's network integration.
vRealize to Aria to VCF Operations (VCF 4.4 → 5.x → 9.0)
From VCF 4.4 the vRealize products were lifecycled by vRealize Suite Lifecycle Manager rather than the VCF BOM; VCF 5.x renamed them Aria (Aria Suite Lifecycle 8.10 → 8.18); VCF 9.0 replaced them with VCF Operations (with fleet management), VCF Automation and VCF Operations for logs/networks. Aria Suite Lifecycle has no upgrade path to 9 — the fleet management appliance takes over during the upgrade.
Brownfield adoption (VCF 5.2 Import Tool → VCF 9.0 converge)
VCF 5.2 introduced the VCF Import Tool to convert an existing vSphere environment into a management domain or import it as a VI workload domain. VCF 9.0 carries the capability forward as 'converge' through the VCF Installer and VCF Operations, so existing vCenter estates become VCF Instances or workload domains without a rebuild.
Installer, fleet and console (VCF 9.0, June 2025)
The VCF Installer replaces Cloud Builder and becomes the instance's SDDC Manager after bring-up. SDDC Manager stays in every VCF Instance (its UI is deprecated; appliance and API remain) while VCF Operations with the fleet management appliance becomes the fleet-level console for lifecycle, certificates, passwords and identity across instances. Design impact: the first instance's management domain hosts the fleet-level components and is the management single point to protect.

Licensing and Commercial Evolution

Per-CPU licensing (through the vSphere 6.x era)
vSphere and vSAN were licensed per CPU socket; from vSphere 7 (April 2020) a CPU licence covered up to 32 cores and larger CPUs needed additional licences.
Per-core subscription (Broadcom, 2024 onwards)
VCF and vSphere Foundation are sold as per-core subscriptions; every CPU is counted as at least 16 cores (vSphere 9.0 install notes). VCF includes vSphere, vSAN capacity (1 TiB per VCF core; vSphere Foundation includes 0.25 TiB per core), NSX, VCF Operations and VCF Automation; add-ons cover vSAN capacity beyond the entitlement, Avi Load Balancer and vDefend. Licensing is managed in VCF Operations (connected or offline mode). Design impact: CapEx to OpEx, licensed cores drive the host BOM, and the design records the licensing mode and renewal date as constraints.

Key Takeaways

  • VCF 9.0 accepts sequential or skip-level upgrades from any VCF 5.0 or later release; estates below 5.0 first upgrade to 5.0+. There is no mandatory 5.2 stepping stone and there were never VCF versions 6, 7 or 8.
  • NSX-V to NSX-T (VCF 4.0, April 2020, NSX-T 3.0 with vSphere 7.0) was the largest architectural shift of the 3.x → 4.x era: new gateway model, Geneve overlay and Policy API, with the migration run as a separate project.
  • VCF 9.0 deprecates the SDDC Manager UI, not SDDC Manager: the appliance and API remain in every VCF Instance, the VCF Installer replaces Cloud Builder and becomes SDDC Manager, and VCF Operations with fleet management becomes the console for Day-2 operations.
  • Licensing moved from per-CPU (32-core cap from vSphere 7) to Broadcom per-core subscription with a 16-core minimum per CPU; VCF includes vSAN capacity at 1 TiB per core (vSphere Foundation: 0.25 TiB per core) and is licensed through VCF Operations.
  • VCF 5.2.x remains a supported line in parallel with 9.x (5.2.4 released May 2026); the 2V0-13.25 exam targets 9.0, so cite the 9.0 BOM and name 5.2 only when the question is about the legacy Cloud Builder / SDDC Manager model.

Upgrade Path Planning: 5.2.x to 9.0.x#

Strategic Planning for 5.2 → 9.0 Migrations

Pre-Upgrade Checks and Compatibility Validation

  1. Compatibility Matrix Validation
  • Source version: the management domain must be at VCF 5.0 or later (sequential or skip-level upgrade to 9.0). Below 5.0, upgrade the management domain and all workload domains to 5.x first
  • Target versions come from the VCF 9.0 BOM (SDDC Manager 9.0, vCenter 9.0, ESX 9.0, NSX 9.0, vSAN 9.0); check the Product Interoperability Matrix for anything outside the BOM
  • Plan for the SDDC Manager UI deprecation: in 9.0 the SDDC Manager UI (and its password, certificate and identity-configuration APIs) is deprecated, while SDDC Manager itself stays in every VCF Instance; these Day-2 tasks move to VCF Operations
  1. HCL (Hardware Compatibility List) Validation
  • CPU minimum: verify all ESXi hosts meet VCF 9.0 CPU requirements (generally Haswell-era or newer)
  • Disk space: VCF 9.0 components require more storage (VCF Operations with the fleet management appliance and collectors consume more space)
  • Network requirements: NSX 4.1 requires higher bandwidth for telemetry (Broadcom's expanded observability)
  • Storage HCL: if using vSAN, verify SSD models are on 9.0 HCL (some older models deprecated)
  1. Backup and Rollback Strategy
  • Snapshot all management cluster VMs (SDDC Manager, vCenter, NSX, vSAN) before upgrade begins
  • Export SDDC Manager backup (Settings > Backup & Restore) — essential for rollback
  • Backup vCenter database (FCLI backup or native vCenter backup)
  • Backup NSX-T config (NSX System > Backup & Restore)
  • Document current vSAN cluster config, cluster UUID, witness node (if stretched cluster)
  • Test restore procedure in pre-prod if available (many customers skip this, then regret during actual failures)

Upgrade Sequence (documented order)

VCF 9.0 docs ('Upgrading a VCF Instance with version 5.x to version 9.0.x') and KB 390634: upgrade the management planes first, then the core SDDC components in a distinct order.

  1. Management components (before the core upgrade)
  • Must be on version 9 first: VCF Operations, the VCF Operations fleet management appliance and the VCF Operations collector. VMware Aria Suite Lifecycle has no upgrade path to 9: patch it to 8.18 Patch 6 or later, and the fleet management appliance is deployed during the Aria Operations to VCF Operations upgrade
  • Optional upgrades: VCF Automation, VCF Operations orchestrator, VCF Operations for networks
  • New installations, not upgrades: VCF Operations for logs, and VCF Identity Broker (VMware Identity Manager has no upgrade path)
  1. SDDC Manager and VCF services (First)
  • Prerequisites: a recent file-based backup of SDDC Manager to an external SFTP server, a snapshot of the SDDC Manager appliance, and a green update precheck
  • After the upgrade, add the VCF endpoint in VCF Operations (Administration > Integrations) and enable collection
  1. NSX Manager, and NSX Global Manager if used (Second)
  • Back up NSX Manager; the upgrade coordinator upgrades the management plane first, then the edge nodes and the host transport nodes
  1. vCenter (Third)
  • Upgrade to vCenter 9.0 (reduced downtime upgrade available)
  1. ESX hosts (Fourth)
  • Rolling, cluster by cluster; upgrade the vSAN on-disk format only after every host is on ESX 9.0

Workload domains can be upgraded before or after the management domain, as long as all components in the workload domain are compatible.

Common Upgrade Failures and Mitigations

  1. SSL Certificate Expiry

Problem: During vCenter upgrade, auto-signed or issued SSL certs can expire mid-process, causing upgrade to hang.

Mitigation: Pre-upgrade, check all certificate expiration dates (vCenter, NSX Manager, ESXi, SDDC Manager). Renew any expiring within 6 months. Use FCLI to validate cert chain.

Recovery: If upgrade fails due to cert, manually refresh cert on halted system, then retry upgrade.

  1. NTP Drift

Problem: If management cluster time drift >30 sec during upgrade, NSX Manager and vCenter can't communicate, causing timeout failures.

Mitigation: Pre-upgrade, validate all management cluster VMs and ESXi hosts are synchronized to within 100ms. Check SDDC Manager NTP sync status (vCenter Settings > Date & Time).

Recovery: Stop upgrade, sync time (chronyc force-step or similar), then retry.

  1. Insufficient Disk Space

Problem: VCF 9.0 components (VCF Operations, fleet management appliance, VCF Automation) require more disk; SDDC Manager scratch partition can fill during upgrade, causing rollback.

Mitigation: Pre-upgrade, verify free space on all management cluster disks: SDDC Manager (/root and /var min 50GB free), vCenter (/storage/core min 100GB free), NSX Manager (/var min 30GB free).

Recovery: Extend disks (if hypervisor allows), clear logs/temp, retry upgrade.

  1. Workload Domain Instability During Upgrade

Problem: If workload domain VMs are still running heavy workloads during SDDC Manager upgrade, NSX-T upgrade can trigger unexpected vMotion, overloading network.

Mitigation: Pre-upgrade, pause or drain workloads from workload domains. Disable vSAN rebalance, pause HA monitoring during NSX upgrade.

Recovery: Re-enable HA monitoring, let vMotion complete naturally; manually migrate stuck VMs if needed.

  1. NSX Edge Gateway Failure

Problem: During NSX Edge upgrade, if edge is single-node (not HA), north-south traffic drops, causing tenant workload outages.

Mitigation: Pre-upgrade, validate all edges are in HA mode (2+ edge nodes per edge gateway). Plan upgrade during maintenance window. Pre-position backup edges if single-node edges exist.

Recovery: Manually trigger failover to standby edge, complete upgrade, validate traffic flow.

Rollback Procedures

Plan the rollback point for each component before you start.

  1. SDDC Manager
  • If the upgrade fails and cannot be fixed, revert to the pre-upgrade snapshot (or restore the file-based backup) and re-run after fixing the root cause
  1. NSX Manager
  • The upgrade takes a local backup of the NSX Manager nodes (/config_bak) and stops if that backup fails
  • Roll back the NSX Manager nodes from that backup before the edge node and host transport node upgrades start
  • Once edge or host transport node upgrades have started, Broadcom Support must first roll those back before the NSX Manager nodes can be rolled back
  1. vCenter
  • If the upgrade fails, resolve the issue and retry the failed task; if it cannot be resolved, restore vCenter from its file-based backup
  • A vCenter reduced downtime upgrade (RDU) rolls back automatically if it fails
  1. ESX hosts and vSAN
  • Once the vSAN on-disk format is upgraded, you cannot roll back software on the hosts or add certain older hosts to the cluster; validate every host first

After all upgrades complete: remove the VM snapshots taken before the upgrade and back up the newly installed components.

Where lifecycle management lives after the upgrade

In VCF 5.2, SDDC Manager's Lifecycle Management is the console for every bundle (SDDC Manager, Aria Suite Lifecycle, NSX, vCenter, ESXi). In VCF 9.0 lifecycle management is not deprecated or made manual: it moves up a level.

  • VCF Operations > Fleet Management > Lifecycle is the console: component inventory and upgrades per VCF Instance, VCF Operations and VCF Automation components, cluster image updates through vSphere Lifecycle Manager.
  • SDDC Manager executes the instance steps (its UI is deprecated; the appliance and API remain in every instance).
  • Binaries come from the online depot or, offline, from the VCF Download Tool; the Product Interoperability Matrix remains the reference for anything outside the release BOM.
  • Upgrade pre-checks run before each stage; the release notes for 9.0.1 add that SDDC Manager must reach 9.0.1 or later before NSX, vCenter or ESX in a 5.x → 9.0.x upgrade.
Implications:
Admins moving from 5.2 learn the VCF Operations console and the fleet-level view; the per-instance sequence is unchanged in spirit (SDDC Manager → NSX → vCenter → ESX)
Each stage is still validated before the next, from the console rather than by hand
A 'manual, no orchestration' upgrade plan is the opposite of the 9.0 model and would fail a design review

Key Takeaways

  • Documented upgrade order for 5.x → 9.0: management planes first (VCF Operations + fleet management), then core components SDDC Manager → NSX → vCenter → ESX, then the vSAN on-disk format
  • Pre-upgrade checklist is critical: SSL certs, NTP sync, disk space validation prevent 80% of failures
  • SSL certificate expiry and NTP drift are the top 2 silent killers; validate both before starting upgrade
  • Roll back NSX Manager before the edge and host transport node upgrades start (after that, Broadcom Support first); after the vSAN on-disk format upgrade, host software cannot be rolled back
  • Lifecycle management is not deprecated in VCF 9.0: VCF Operations (Fleet Management > Lifecycle) drives upgrades with SDDC Manager executing per instance; validate each stage before the next, but do not plan on manual per-component upgrades.

Brownfield VCF Adoption: Converting Existing vSphere to VCF#

Real-World Path: Adopting VCF on Existing vSphere Estates

Why Brownfield Adoption Matters

Most enterprises do not build VCF from scratch. They hold existing vSphere clusters (often on vSphere 7 or 8), NSX already deployed or not at all, vSAN or array storage, and workloads that cannot be rebuilt. Two releases give two different brownfield paths:

VCF 5.2 — VCF Import ToolVCF 9.0 — Converge
What it doesConverts an existing vSphere environment into a VCF management domain, or imports one as a VI workload domainConverges an existing vSphere (or vSphere Foundation) environment into a new VCF Instance / new fleet, or a new instance in an existing fleet; existing vCenters are imported as workload domains afterwards
ToolingVCF Import Tool (script bundle: precheck run on the target vCenter appliance; check, convert and import run on the SDDC Manager 5.2.x appliance)VCF Installer deployment wizard (new fleet or instance) and VCF Operations (workload-domain import)
NetworkingvCenter must not have an NSX instance registered; NSX is deployed by the tool (NSX bundle required)9.0.0: a new NSX 9.0 instance is deployed during convergence; 9.0.1+: vCenters with existing NSX registrations (without ELM) can be converged, including NSX Edge nodes
DocumentationVCF 5.2 Administration: Considerations Before Converting or Importing Existing vSphere Environments (pp.458-462)VCF 9.0.x: Converging Existing Virtual Infrastructure to a VCF or a vSphere Foundation Platform (pp.1330-1340)

VCF 5.2: VCF Import Tool — Documented Guardrails

Software BOM alignment (management domain conversion): VCF Import Tool 5.2 requires vCenter 8.0 Update 3a or later and ESXi 8.0 Update 3 or later; Import Tool 5.2.1 / 5.2.1.2 require vCenter 8.0 U3c and ESXi 8.0 U3b or later. VI workload domain import supports vCenter 7.0 Update 3h / ESXi 7.0 Update 3g or later. Import Tool 5.2.1.2 requires an NSX 4.2.3.1 bundle uploaded to SDDC Manager before the import script runs.

Single Sign-On: each SSO domain may contain only one vCenter; Enhanced Linked Mode is not supported — remove the vCenter from the ELM ring first. SSO domain names do not need to be unique inside a VCF instance.

vCenter placement: the vCenter VM must be co-located on a cluster it manages (management domain) or located in the management domain or co-located (VI workload domain).

Storage: the default cluster must use vSAN, NFS v3, VMFS on FC (or VMFS on FCoE from 5.2.1). NFS 4.1, vVols and native iSCSI are not supported. vSAN stretched clusters cannot be imported. OSA compression-only is not supported (enable dedupe or disable compression). Host minimums: VCF 5.2 — all clusters 4 nodes minimum; VCF 5.2.1.x — vSAN clusters 3 nodes minimum, NFS or FC clusters 2 nodes minimum.

Network: vCenter must not have an existing NSX instance registered (the tool deploys NSX). vSphere Distributed Switches only (no standard or Cisco virtual switches; with Import Tool 5.2.1.2 + SDDC Manager 5.2.1.1 hosts may also carry a standard switch). VMkernel IP addresses statically assigned; one VMkernel interface per traffic type; dedicated vMotion network; at least two 10 Gb uplinks per host (5.2.1.2 allows differing uplink counts and LACP; earlier versions neither); teaming policies must match VCF standards; one vDS per cluster unless on 5.2.1.2 (shared vDS supported).

Compute: no VxRail-managed clusters; no vSphere Configuration Profiles; all clusters on vSphere 8.0 U3 or later (management conversion); consistent ESXi build per cluster; DRS fully automated; a single vSphere Lifecycle Manager method per vCenter (mixed images/baselines only with 5.2.1.2); Normal Lockdown Mode across all hosts not supported; standalone hosts and single-host clusters only with 5.2.1.2 (no Day-N operations on them).

What a converted or imported domain can do (Table 315): NSX VLAN-backed deployment yes; NSX Edge deployment, AVN and Aria Lifecycle in VCF-aware mode only after enabling virtual networking on the imported domain; FC and NFS as principal storage yes; vCenter appliances co-located in a workload-domain cluster yes.

VCF 9.0: Converge — What Changed

The converge process 'relaxes many of the constraints from previous releases' (VCF 9.0 What's New). It brings in clusters with shared vDS, clusters with active LACP, VMFS and NFS external storage, remote datastores and vSAN storage clusters, vCenters with NSX (including Edge nodes) as workload domains, and two-node ROBO vSAN deployments.

Supported configurations for converging to a management domain (VCF 9.0.x table): VDS 8.0 or later; ports aligned with VMware Ports and Protocols; statically assigned VMkernel IPs; dedicated vMotion network; LACP-enabled vDS; hosts with multiple ≥10 Gbps uplinks or a single ≥10 Gbps pNIC; shared vDS across clusters; vCenter VM hosted on a cluster managed by the same vCenter; vSphere Configuration Profiles and vLCM-image clusters (convert baseline clusters to images before ESX 9.0); fully automated DRS; standalone hosts and single-host clusters if another cluster qualifies. From 9.0.1: vCenters with existing NSX registrations without ELM, and NSX Local Managers that are part of a Federation (only the Local Manager converts).

Not supported: Cisco virtual switches; vCenters without a vDS; custom vCenter ports; dynamically allocated VMkernel IPs; shared vMotion networks; multiple NSX Manager instances per vCenter; NSX bare-metal Edge nodes; VxRail-managed clusters; vCenters with ELM (break ELM with cmsso-util after upgrading when no NSX is registered); vCenter VM hosted on a cluster of a different vCenter; baseline-managed clusters; manual or partially automated DRS; clusters using vCenter HA; partial import (all clusters of a vCenter import together); vVols is deprecated in 9 and not recommended.

Minimum component versions before the Installer workflow: converging to VCF 9.0.0 needs vCenter 9.0 and ESX 9.0 (upgrade first); converging to 9.0.1 or 9.0.2 accepts vCenter 8.0 Update 3 and ESX 8.0 Update 1 or later (and NSX 4.2.1 or later where NSX is registered), so the Installer upgrades them as part of the convergence.

Converge procedure (VCF 9.0.x, vCenter + ESX scenario):

  1. Verify the supported configurations and minimum versions; upgrade vCenter and ESX where the scenario requires it.
  2. Deploy the VCF Installer appliance (4 vCPU, 16 GB, 914 GB).
  3. Download the VCF binaries to the Installer depot (online or via the VCF Download Tool).
  4. Run the deployment wizard with the existing vCenter as a building block: choose a new VCF fleet or an instance in an existing fleet; missing components (NSX if not registered, SDDC Manager, VCF Operations and fleet management, optionally VCF Automation) are deployed into the existing cluster, which becomes the management domain.
  5. Validate, deploy, then import and upgrade the remaining workload-domain vCenters from VCF Operations.

Scenarios with existing Aria Operations, Aria Suite Lifecycle or Aria Automation have their own documented sequences (Aria Suite Lifecycle is replaced by the fleet management appliance; Aria Automation is upgraded to VCF Automation and imported).

Storage Considerations

vSAN estates: VCF 9.0 converge accepts vSAN clusters, vSAN storage clusters and two-node ROBO vSAN; existing data stays in place, storage policies continue to apply. In VCF 5.2 the imported vSAN cluster must not be stretched and must meet the 3/4-node minimums above.

External storage: VMFS and NFS datastores (and remote datastores) are supported principal storage in 9.0 converge; 5.2 import supports vSAN, NFS v3 and VMFS on FC (FCoE from 5.2.1), not NFS 4.1, vVols or native iSCSI.

Do not expect the import to re-layout data, change RAID levels or enable space efficiency: it registers the cluster and applies VCF governance; storage design changes remain a separate Day-N activity.

Licensing

VCF 9.x is a per-core subscription with a 16-core minimum per CPU, licensed in VCF Operations (connected or offline mode); VCF Operations runs 90 days in evaluation until licensed. Existing perpetual vSphere/vSAN/NSX entitlements are a commercial conversation with Broadcom, not something the Import Tool or the Installer calculates — the technical work is to size the licensed cores (current hosts plus growth) and to pick the licensing mode. Mixed perpetual-plus-subscription estates are a transition state to plan around, not a supported long-term model for a VCF Instance.

Brownfield Adoption Roadmap: Example Scenario (VCF 9.0.1)

Company: mid-size enterprise, 50 ESX hosts across three vSphere 8.0 U3 clusters under one vCenter (no ELM), NSX 4.2.1 registered, vSAN storage.

Phase 1 — Assess (weeks 1-4): run the supported-configuration table against the estate: vDS 8.0+, static VMkernel IPs, dedicated vMotion, fully automated DRS, vLCM images (convert baseline clusters), vCenter VM co-located, no vCenter HA. Record every gap with its remediation.

Phase 2 — Remediate (weeks 5-8): convert baseline clusters to images, set DRS to fully automated, align ports with VMware Ports and Protocols, confirm NSX 4.2.1+.

Phase 3 — Converge (weeks 9-10): deploy the Installer, download binaries, run the wizard as a new VCF fleet with the existing vCenter and NSX; the default cluster becomes the management domain; SDDC Manager, VCF Operations and fleet management are deployed; the Installer becomes SDDC Manager.

Phase 4 — Operate (weeks 11-16): license in VCF Operations; validate Fleet Management > Lifecycle, Certificates and Passwords; import any further vCenters as workload domains from VCF Operations; schedule the component upgrades to the 9.0.x BOM through Fleet Management > Lifecycle.

Phase 5 — Scale (months 5-12): add workload domains and hosts through VCF Operations; converge further sites as instances in the same fleet.

Common Brownfield Adoption Challenges

  1. Enhanced Linked Mode — vCenters in an ELM ring cannot be converged (9.0) or imported (5.2) until ELM is broken; VCF SSO is the 9.0 replacement for cross-vCenter login.
  2. Switch and uplink hygiene — standard switches, dynamic VMkernel IPs, shared vMotion networks and sub-10 Gbps uplinks are the usual blockers; fix them before the wizard pre-checks do.
  3. Lifecycle method — baseline-managed clusters must become image-managed before ESX 9.0; plan the conversion per cluster.
  4. NSX state — 5.2 requires no NSX registered (the tool deploys it); 9.0.0 likewise deploys new NSX; 9.0.1+ converges existing NSX without ELM. Know which release you are converging to.
  5. Licensing — size the licensed cores and settle the commercial conversion early; the technical convergence does not wait for finance, but VCF Operations evaluation mode does end after 90 days.

Key Takeaways

  • Two brownfield paths: VCF 5.2 uses the VCF Import Tool (convert to a management domain or import as a VI workload domain, with SDDC Manager 5.2.x); VCF 9.0 'converges' an existing vSphere estate through the VCF Installer (new fleet or instance) and imports further vCenters as workload domains from VCF Operations.
  • 5.2 import guardrails: one vCenter per SSO domain (no ELM), vCenter without an NSX registration (the tool deploys NSX), vDS only with static VMkernel IPs and a dedicated vMotion network, principal storage vSAN / NFS v3 / VMFS-FC (no stretched vSAN, NFS 4.1, vVols or iSCSI), 4-node clusters (3 with 5.2.1.x), fully automated DRS, no VxRail or Configuration Profiles.
  • 9.0 converge relaxes the constraints: shared vDS, LACP, VMFS/NFS/remote datastores and vSAN storage clusters, vCenters with NSX and Edge nodes (9.0.1+, without ELM), two-node ROBO vSAN; still not supported — ELM, vCenter HA clusters, baseline-managed clusters, manual DRS, VxRail, custom vCenter ports, partial import of a vCenter.
  • Minimum versions before the 9.0.x Installer workflow: 9.0.0 needs vCenter 9.0 and ESX 9.0; 9.0.1/9.0.2 accept vCenter 8.0 U3 and ESX 8.0 U1 or later (NSX 4.2.1+ where registered).
  • Licensing is a per-core subscription (16-core minimum per CPU) managed in VCF Operations; perpetual-to-subscription conversion is a commercial agreement with Broadcom, not a tool step — size the licensed cores early and plan around the 90-day VCF Operations evaluation window.

VCF 5.2 Deep Dive: VCF 5.2 Architecture & Components#

VCF 5.2 Architecture & Components VCF 5.2

VMware Cloud Foundation 5.2 is the integrated SDDC platform that most enterprises run in production today. It unifies vSphere (ESXi + vCenter), vSAN, NSX, and the optional Aria Suite under a single lifecycle-managed control plane orchestrated by SDDC Manager. A VCF deployment is always created by the Cloud Builder appliance through a process called bring-up, after which Cloud Builder is powered off and SDDC Manager becomes the authoritative Day-N controller. This section documents every architectural role, component, and deployment option required for a VCDX-level understanding of VCF 5.2.

1. SDDC Manager — the central orchestrator

SDDC Manager is a 4 vCPU / 16 GB RAM / 908 GB Photon appliance that runs in the management domain and owns the following responsibilities:

  • Inventory of truth: keeps the authoritative database of hosts, clusters, workload domains, NSX/vCenter instances, licenses, network pools, and credentials. Underlying store is PostgreSQL (platform DB) on the SDDC Manager appliance.
  • Bring-up handoff: after Cloud Builder completes the first-run workflow, inventory and control move to SDDC Manager. Cloud Builder is then powered off.
  • Workload-domain lifecycle: creates, expands, shrinks, renames and deletes VI workload domains (dedicated vCenter, optional dedicated or shared NSX Manager cluster, optional NSX Edge cluster).
  • Host lifecycle: commissions ESXi hosts into an Unassigned Hosts pool, assigns them to clusters, and decommissions them back.
  • Lifecycle Management (LCM): downloads install/upgrade/async-patch/flexible-BOM/independent-SDDC-Manager bundles from the online VMware Depot or an offline depot, stages them, runs upgrade prechecks, and drives the upgrade sequence in the required order.
  • Certificate Management: integrates with Microsoft CA, OpenSSL, or any third-party CA to replace VMCA-issued certs on vCenter, NSX, Avi LB, SDDC Manager, and Aria Suite Lifecycle. ESXi certs are not managed by SDDC Manager.
  • Password Management: rotates, updates, retries and manages passwords for vCenter root, NSX root/admin/audit, ESXi root, SDDC Manager local users, and Aria components.
  • Backup & Restore: orchestrates file-based backups over SFTP (encrypted with a backup passphrase) and image-based snapshots; supports full or partial restore.
  • Drift reconciliation: detects and applies Configuration Updates (FEATURE or FIX) from the Repository to keep component configs aligned with the current VCF BOM.
  • REST API and PowerShell modules: exposes the VMware.VCF.* PowerShell modules and a full REST API at https://<sddc-manager-fqdn>/v1/. Developer Center in the UI provides an API Explorer.
  • SoS utility: /opt/vmware/sddc-support/sos runs health checks, collects support bundles, and performs log analysis.

SSH login to SDDC Manager uses the vcf service account; root is kept for break-glass. Key paths: /opt/vmware/vcf/version.txt (current VCF version), /var/log/vmware/vcf/bringup/ (bring-up logs), /opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.sh (safe service restart).

2. Cloud Builder appliance — the bring-up engine

Cloud Builder is a disposable 4 vCPU / 4 GB RAM / 279 GB (25.1 GB thin / 253.8 GB thick) Photon appliance whose only job is to stand up the first management cluster and hand it off to SDDC Manager.

  • Deployment targets: can run on any ESXi host, VMware Workstation, or Fusion. It does not need to run on VCF hardware — only needs L3 reachability to the management VLAN, DNS, and NTP.
  • Two input methods: the Excel Deployment Parameter Workbook uploaded through the UI at https://<cloud-builder-fqdn>/, OR a JSON payload through the API (JSON is required for custom CA-signed ESXi certificates).
  • Validation: before bring-up Cloud Builder validates DNS forward and reverse lookups, NTP, VLAN reachability, MTU, ESXi fingerprints/thumbprints, vSAN HCL, license keys, and password complexity. Failures highlight the workbook cells in red.
  • Bring-up deliverables: deploys four management ESXi hosts into a vSAN cluster, the management vCenter Server, a 3-node NSX Manager cluster, SDDC Manager, and optionally Aria Suite Lifecycle; creates the vSphere Distributed Switch per the vDS profile; configures licenses.
  • Log path: /opt/vmware/bringup/logs/vcf-bringup-debug.log is the primary debug log; root logs live under /var/log/vmware/vcf/bringup/.
  • After success: download the deployment report, click Finish, launch SDDC Manager, then power off the Cloud Builder VM. It is not part of Day-2 operations and must not be deleted — Broadcom requires it be kept for support but powered off.

3. vSphere — ESXi and vCenter Server

vSphere is the compute foundation. Every workload domain has exactly one dedicated vCenter Server appliance, and every vCenter runs in the management domain (never co-located with the workloads it manages, except for the management vCenter itself).

  • vCenter HA in VCF: only vSphere HA is supported to protect vCenter. vCenter HA (active/passive/witness) and vSphere FT are NOT supported for VCF-managed vCenters.
  • Tiny — 10 hosts / 100 VMs
  • Small — 100 hosts / 1,000 VMs (default for management domain)
  • Medium — 400 hosts / 4,000 VMs (default for VI workload domain)
  • Large — 1,000 hosts / 10,000 VMs (16 vCPU / 39 GB)
  • X-Large — 2,000 hosts / 35,000 VMs in vSphere 8.0; 2,500 hosts / 45,000 VMs in vSphere/VCF 9.0 (24 vCPU / 58 GB)
  • ESXi: a host in a VCF-managed cluster has its certificate regenerated after hostname/FQDN is set, runs the vSphere Cluster Services VMs (vCLS), and is enrolled as an NSX host transport node when the cluster joins NSX.

4. vSAN — the default principal storage

  • vSAN OSA (Original Storage Architecture) remains the default in VCF 5.2: each host contributes one flash cache device + one or more capacity devices, combined into disk groups. Minimum 2 disk groups per host, 600 GB minimum cache tier, 256 minimum storage controller queue depth, 32 GB host RAM to support the maximum number of disk groups. For hybrid configurations, cache tier must be at least 10% of capacity tier.
  • vSAN ESA (Express Storage Architecture) is optional and requires vLCM images, NVMe TLC flash, hosts on the ESA ReadyNode HCL, and 25-GbE NICs + 512 GB RAM per host. vSAN ESA clusters on vSAN ReadyNodes can be stretched from VCF 5.2 (5.2 release notes); on VCF on Dell VxRail, ESA stretch starts at 5.2.1.1 (earlier VxRail releases stretch OSA only).
  • vSAN Max is a disaggregated, storage-only cluster type (renamed vSAN storage clusters; the VCF 5.2 docs already list "vSAN Storage Clusters (formerly vSAN Max)", p.136). Provides a remote datastore to other vSAN ESA or vSAN Compute clusters. Minimum 4 hosts, max 24 hosts per vSAN Max cluster plus up to 104 compute clients (128 total).
  • vSAN Compute Clusters — hosts with no local storage that mount a remote vSAN OSA/ESA/Max datastore from another cluster within the same workload domain.
  • Free-space guardrail: keep at least 30% free on the vSAN datastore.

5. NSX — the network virtualization plane

  • NSX Manager cluster = 3 nodes + 1 VIP (4 IPs total on the same L2). The management-domain NSX Manager is always dedicated; VI workload domains may share an NSX Manager cluster — up to 14 VI workload domains can share one NSX Manager cluster in the same SSO domain, or up to 16 isolated VI workload domains.
  • NSX Manager sizes: Extra-Small (CSM only), Small (PoC), Medium — up to 128 hosts (default for management domain), Large — up to 1,024 hosts (default for VI workload domains), Extra-Large — up to 2,048 hosts. Non-default sizes in a VI WLD require the API.
  • NSX Edge VM form factors (VCF 5.2 Edge cluster deployment, Edge Form Factor): Small — 4 GB RAM, 2 vCPU, 200 GB disk, lab and proof-of-concept only; Medium — 8 GB RAM, 4 vCPU, 200 GB, production with load balancing; Large — 32 GB RAM, 8 vCPU, 200 GB, production with load balancing at higher scale; Extra Large — 64 GB RAM, 16 vCPU, 200 GB, the largest services footprint. Throughput depends on the services configured and the host NICs; size from the NSX configuration maximums rather than a fixed Gbps band.
  • NSX Federation uses a manually-deployed Global Manager cluster (3 active + 3 standby) across VCF instances. Max 4 locations per cross-instance Tier-0; 4 with Medium GM, 16 with Large/XL GM. Required RTEP MTU: 1,500 minimum, 1,700 preferred, 9,000 recommended; max 500 ms latency (150 ms for workload mobility).
  • Transport zones: one overlay TZ per NSX instance (shared across all clusters of that instance), plus one VLAN TZ for N–S and one for VLAN-backed segments.
  • Routing: BGP is the required dynamic routing protocol. Keep-alive 4 s, hold-down ≤ 12 s.

6. The Aria Suite (formerly vRealize)

VCF 5.2 completes the vRealize → Aria rename that began in late 2022. The components deploy through VMware Aria Suite Lifecycle (formerly vRealize Suite Lifecycle Manager), itself driven by SDDC Manager. All Aria VMs live in the management domain.

Former nameVCF 5.2 nameRole
vRealize Suite Lifecycle ManagerVMware Aria Suite LifecycleLCM orchestrator for the Aria stack; deployed on demand from SDDC Manager; 178 GB thin storage.
vRealize OperationsVMware Aria OperationsMulti-cluster capacity, performance and compliance analytics for vSphere, vSAN, NSX and Aria Automation.
vRealize AutomationVMware Aria AutomationSelf-service cloud catalog, Cloud Templates (formerly Blueprints), Code Stream, SaltStack Config.
vRealize Log InsightVMware Aria Operations for LogsCentralised syslog collection, content packs and dashboards.
vRealize Network InsightVMware Aria Operations for NetworksFlow-based network visibility, micro-segmentation planning, NSX health.
Workspace ONE Access (VIDM)VMware Workspace ONE AccessIdentity broker and authentication source for the Aria stack (required minimum Medium for Aria Automation).

Workspace ONE Access sizes range from Extra-Small (3,000 users) up to Extra-Extra-Large (100,000 users). A clustered deployment is always 3 nodes behind an NSX load-balancer VIP, requiring 5 IPs on the cross-instance segment. Storage per Workspace ONE Access node: 100 GB thin.

7. Management Domain vs. VI Workload Domain

Workload domains are the primary unit of consumption in VCF. A workload domain is a logical set of vSphere clusters managed by a dedicated vCenter Server, with optional NSX networking, provisioned by SDDC Manager.

AttributeManagement domainVI workload domainIsolated VI workload domain
PurposeHosts VCF management VMs (SDDC Manager, vCenters, NSX Managers, Aria)Hosts customer workloadsCustomer workloads with a separate identity boundary
SSO domainOwns the primary SSO domainShares SSO with mgmt domain (ELM ring topology)Has its OWN SSO domain
Min hosts (single AZ, vSAN default)4 (3 with 5.2.1)3 (4 recommended); 2 if NFS/FC/vVols + vLCM imagesSame as VI WLD
Min hosts (multi-AZ)8 equally split6 (8 recommended)Same as VI WLD
vCenter size defaultSmallMediumMedium
NSX ManagerDedicated clusterDedicated OR shared (up to 14 WLDs per cluster)Dedicated OR shared (up to 16 isolated WLDs per cluster)
Max per VCF instance1 (required first)25 workload domains total per instance; 15 per single SSO domain; up to 24 isolated
Upgraded first in LCMYes — alwaysAfter management domainAfter management domain

8. Standard vs. Consolidated architecture

VCF 5.2 supports two architectural models. Standard is the VMware-recommended best practice and the starting point for every reference design.

AttributeStandardConsolidated
SeparationManagement workloads isolated on the management domain; customer workloads run only in VI workload domains.Both management and customer VMs share the management domain; separated via resource pools.
Design-element referenceVCF-ARCH-RCMD-CFG-001 (Recommendation)Permitted for smaller environments; migratable to Standard later.
Hardware footprintLarger — needs separate clusters per roleSmaller — single cluster for everything
Max scaleUp to 25 workload domains1 consolidated domain; limited scale-out
When chosenTier-1 enterprises, production SDDCsPoC, labs, SMB, remote sites with strict hardware budgets

Both models use the same bring-up path. A consolidated domain can be scaled up to a standard architecture later by adding a VI workload domain and migrating workloads off the management cluster.

9. Deployment options (VCF topologies)

  • Single VCF instance, single AZ — baseline; up to 25 workload domains; vSphere HA protects against host failures.
  • Single VCF instance, multiple AZs (stretched) — management domain must be stretched first before any VI workload-domain cluster can be stretched; up to 2 AZs; requires at least 10 Gbps between AZs and < 5 ms RTT; witness in a third location.
  • Multiple VCF instances, single AZ each — typically paired with NSX Federation for unified policy across sites.
  • Multiple VCF instances, multiple AZs per instance — maximum resilience; each instance is internally stretched and all instances are federated.

10. Component interaction at steady state (Day-2)

After bring-up, the control plane interacts as follows:

  • SDDC Manager talks to each vCenter via its SSO credential; to NSX Manager via admin API; to ESXi only indirectly (via vCenter) for non-LCM operations; to Aria Suite Lifecycle via its API.
  • Workload-domain vCenter Server instances are joined in an Enhanced Linked Mode (ELM) ring within a single SSO domain (up to 15 vCenters). Isolated workload domains have their own SSO.
  • NSX Manager is the control plane for all transport nodes (ESXi + Edge VMs); NSX Global Manager (when Federation is used) writes global state that is replicated to each NSX Local Manager.
  • Aria Operations, Aria Operations for Logs and Aria Operations for Networks collect telemetry from vCenter, NSX and Aria Automation; Aria Automation consumes vCenter/NSX/vSAN/Workspace ONE Access for self-service cloud.
  • Workspace ONE Access is the identity broker for the Aria stack; vCenter SSO is the identity broker for vSphere/NSX/SDDC Manager. VCF 5.2 adds optional external IdP integration (one of: ADFS, Okta, or Microsoft Entra ID — only one at a time).

Reference documentation: VCF 5.2 Documentation Portal · VCF 5.2 Design Guide · VCF 5.2 Administration Guide · VMware Aria Suite TechDocs.

Version Comparison

VCF 5.2

Cloud Builder + SDDC Manager orchestration; separate Aria Suite

VCF 9.0

VCF Installer replaces Cloud Builder; VCF Operations consolidates Aria

Key Takeaways

  • SDDC Manager is the Day-N controller (4 vCPU/16 GB/908 GB Photon appliance) with PostgreSQL as single source of truth
  • Cloud Builder (4 vCPU/4 GB/279 GB) is disposable — powered off after bring-up, never deleted
  • Each workload domain has exactly one dedicated vCenter; vCenter HA (active/passive/witness) is NOT supported in VCF
  • NSX Manager cluster is 3 nodes minimum; shared across domains OR dedicated per domain
  • vSAN is the ONLY supported storage for management domain boot/config; NFS/VMFS for workload domains

VCF 5.2 Deep Dive: Component BOM & Versions#

VCF 5.2 Component BOM & Versions VCF 5.2

A BOM (Bill of Materials) is the precise set of component versions that a specific VCF release certifies together. Every workload domain in a VCF instance tracks its current BOM state, and LCM enforces that in-place upgrades move the entire BOM atomically — with the exception of three 5.2-introduced features (Independent SDDC Manager Upgrade, Flexible BOM Upgrade, and Async Patch) that allow bounded deviations. This section documents the VCF 5.2 BOM, the hardware and network prerequisites that enforce it, and the specific minimums you must budget for a design.

Core VCF 5.2.x BOM (authoritative components)

The BOM evolves across 5.2 maintenance releases (5.2.0 → 5.2.1 → 5.2.1.1 → 5.2.1.2 → 5.2.2 …). Always confirm against the Broadcom Interoperability Matrix and the VCF 5.2 Release Notes before building a design. The table below reflects the baseline GA BOM family.

ComponentVCF 5.2 family versionRole / Notes
SDDC Manager5.2.xPhoton appliance, 4 vCPU / 16 GB / 908 GB. Independent upgrades allowed from 5.2 using SDDC-Manager-only bundles (4th version digit, e.g. 5.2.0.1).
Cloud Builder5.2.x4 vCPU / 4 GB / 279 GB Photon appliance. Disposable after bring-up (power off; do not delete).
vSphere ESXi8.0 Update 3 (default) — 7.x also supported via Flexible BOMDPU-backed hosts require ESXi 8.0 U3 + VCF 5.2 and must boot UEFI. Heterogeneous ESXi and vCenter build levels supported through Flexible BOM.
vCenter Server8.0 Update 3Only vSphere HA is supported to protect VCF-managed vCenters — vCenter HA and FT are NOT supported.
vSAN8.0 U3 (ships with ESXi)vSAN OSA is the default; vSAN ESA is supported with strict prerequisites; vSAN Max is the disaggregated storage-only topology.
NSX4.2.x (supports 4.1.x during split-BOM)Manager cluster = 3 nodes + VIP (4 IPs). Shared NSX Manager supported up to 14 VI WLDs in one SSO (16 isolated).
VMware Aria Suite Lifecycle8.18Entry point for deploying the rest of the Aria stack. 178 GB thin storage.
VMware Aria Operations8.18Formerly vRealize Operations.
VMware Aria Automation8.18Formerly vRealize Automation.
VMware Aria Operations for Logs8.18Formerly vRealize Log Insight.
VMware Aria Operations for Networks6.13.xFormerly vRealize Network Insight; optional.
VMware Workspace ONE Access21.08.0.xIdentity broker for Aria; clustered = 3 nodes + VIP.
VMware Avi Load Balancer22.1.x (formerly NSX ALB)Optional for Tanzu Supervisor, Aria VIPs, AVI-based L7 load balancing.
VMware Cloud Foundation Import ToolMatching 5.2.x buildLives on SDDC Manager at /home/vcf/vcf-import-package/vcf-brownfield-import-<build>/vcf-brownfield-toolset; script vcf_brownfield.py.
Async Patch Tool1.2External CLI; delivers NSX / vCenter / ESXi critical patches outside the main BOM cadence.
Bundle Transfer UtilityShipped with SDDC Managerlcm-bundle-transfer-util — only supported method for offline depot workflows.

Hardware compatibility requirements (non-negotiable)

  • Every ESXi host must be on the VMware Compatibility Guide and, for vSAN, on the vSAN ReadyNode HCL (use vSAN ESA ReadyNode HCL for ESA clusters).
  • DPU-capable hosts (SmartNICs) require ESXi 8.0 U3 and UEFI boot.
  • All hosts in a single management-domain default cluster must be homogeneous (VCF-ESX-RCMD-CFG-002).
  • Boot device — high-endurance SSD, minimum 128 GB to maximise ESX-OS data space.
  • Hyperthreading MUST NOT be counted when sizing CPU (VCF-ESX-RCMD-CFG-003). Size against physical cores only.
  • TPM modules, if present, must run the latest 2.0 firmware. If present but unused, disable in BIOS (KB 312159).
  • All hosts in a cluster must share the same DPU vendor when DPUs are used.

Minimum host specs

ElementMinimumRecommended
CPUModern 64-bit x86-64 on VMware HCLNewer generation to support vCPU:pCPU over-commit budgets (2:1 mgmt, 8:1 VI)
RAM32 GB (vSAN OSA max disk groups)512 GB (vSAN ESA requirement)
Boot deviceHigh-endurance SSD 128 GBNVMe boot
vSAN OSA cache≥1× 600 GB flashPer vSAN ReadyNode
vSAN OSA capacity≥2 capacity devicesPer vSAN ReadyNode
vSAN ESA disks≥2 NVMe TLCPer vSAN ESA ReadyNode
NIC speed10-GbE minimum25-GbE (ESA requires 25-GbE). 100-GbE on each ToR for dedicated Edge.
NICs per host2 pNICs (single vDS profile)4 pNICs (allows traffic separation and dual-vDS profiles)
Out-of-band managementRequiredIPMI / iDRAC / iLO

Supported storage types

StoragePrincipal (boot)SupplementalNotes
vSAN OSAYes (all domain types)YesDefault; scale out / up; HCI Mesh supported for remote datastore mount within the same workload domain.
vSAN ESAYesYesRequires vLCM images, NVMe TLC, ESA-compatible HCL hosts, 25-GbE NICs, 512 GB RAM. Stretching an ESA cluster is supported on vSAN ReadyNodes from VCF 5.2 (release notes); on VCF on Dell VxRail from 5.2.1.1 (earlier VxRail releases stretch OSA only).
vSAN MaxYes (storage-only cluster)Yes (mounted to other clusters)4–24 hosts vSAN storage-only + up to 104 compute clients. New cluster type in VCF 5.2.
NFS v3Yes (VI WLD only; requires vLCM images; min 2 hosts)YesDatastore name, share path and NFS server IP must be defined. Read/write required.
VMFS on FCYes (VI WLD only; requires vLCM images; min 2 hosts)YesZoning and datastore must pre-exist; volumes must be mounted on hosts before commissioning.
vVolsYes (VI WLD only; min 2 hosts with vLCM images)YesVASA provider must be added to vCenter before cluster creation.
NFS v4.1, iSCSI, CIFSNoYes (supplemental only)Never principal storage.

Network requirements (MTU, VLANs, IP pools)

  • VLAN range accepted: 0–4094 (validate against fabric).
  • MTU range (Network Pool): 1,500–9,000. Default vDS is 9,000.
  • MTU minimums: physical switches and vDS carrying overlay, vSAN or vMotion need 1,600 bytes minimum for Geneve overlay (1,700 or more recommended for Geneve header growth); 9,000 for jumbo frames.
  • NSX Federation RTEP MTU: minimum 1,500, preferred 1,700, jumbo recommended 9,000.
  • Host-to-ToR: 25-GbE or higher (10-GbE minimum); dedicated Edge clusters recommend 100-GbE per ToR.
  • Stretched cluster: ≥10 Gbps between AZs, < 5 ms RTT.
  • NSX Federation latency: ≤ 500 ms between instances (≤ 150 ms for Cross vCenter vMotion).
  • Remote cluster (satellite) WAN: min bandwidth 10 Mbps, max latency 100 ms.
  • No LAG/LACP/vPC/EtherChannel on ESXi host uplinks.
  • BGP timers required: keep-alive 4 s; hold-down ≤ 12 s.
  • VMkernel MTU defaults: management 1500, vMotion 9000, vSAN 9000, NFS 9000, Host TEP 9000.

VLANs and subnets you must plan

VLANSingle-AZMulti-AZ additional
VM Management (optional separate port group)Required if separating mgmt-VM traffic from host mgmt—
Host ManagementRequired (HA gateway within instance)Second AZ Host Management — required with HA gateway in AZ2
vSphere vMotionRequiredSecond AZ vMotion
vSANRequired for default management clusterSecond AZ vSAN
Host Overlay (TEP)RequiredSecond AZ Host Overlay
NFSRequired if NFS is principal storage—
Uplink01 / Uplink02Required (unique; gateway optional)Per AZ if stretched Edges
Edge OverlayRequired (different VLAN from Host Overlay)Per AZ
Edge RTEP (Federation only)Required for FederationStretched with same VLAN/IP in both AZs
Management and witness at third location—Required (Multi-AZ)

IP pool minimums to budget

  • NSX Manager cluster — 4 IPs (3 nodes + VIP) per cluster.
  • NSX Global Manager — 4 IPs per cluster × 2 (active + standby).
  • Host TEP / Edge TEP — one IP per transport node per VLAN; use DHCP or static IP pool on the NSX Host Overlay VLAN.
  • Stretched cluster — witness VM (vSAN Witness Appliance) at a third site.
  • Workload Management (Tanzu) — pod subnet /22, service subnet /24, ingress /27, egress /27 minimums.
  • Workspace ONE Access cluster — 5 IPs on the cross-instance segment (3 nodes + VIP + service).
  • Temporary IP per vCenter upgrade from VCF 4.5.x source (and every 5.2.1 vCenter RDU upgrade) — can be reused across vCenters sequentially; parallel upgrades need additional IPs.

vSAN-specific numbers you will be asked about

ParameterValue
Free space minimum on vSAN datastore30%
vSAN OSA disk groups per host (min)2
vSAN OSA cache tier (min size)600 GB
vSAN OSA controller min queue depth256
vSAN OSA hybrid cache % of capacity≥ 10%
vSAN ESA NIC minimum25-GbE
vSAN ESA RAM per host512 GB
vSAN OSA RAM for max disk groups32 GB
Stretched cluster witness sizingTiny (10 VMs / 750 components), Medium (500 VMs / 21,833 cpts), Large (45,000 cpts), XL (64,000 cpts)

Password-complexity reference for component accounts

AccountLengthNotes
SSO domain administrator, vCenter root8–20Upper/lower/digit/special from @ ! # $ % ^ ?; disallowed * {}[]()/\\\\'"\`~,;:.<>
NSX root, NSX UI/CLI admin, NSX audit, SDDC Manager admin@local12–127Same charset; NSX root/UI/audit require ≥ 5 different characters.
SDDC Manager root, SDDC Manager super-user vcf, Cloud Builder admin/rootMinimum 15Same charset; must not include dictionary words (e.g. VMware1! is rejected).

Supported special characters: @ ! # $ % ? ^. Always disallowed: * { } [ ] ( ) / \\\\ ' " \ ~ , ; : . `

Other limits to memorize

  • Max hosts per vSphere cluster — 64.
  • Max NSX Edge cluster size — 10 nodes (min 2).
  • Active/Active Tier-0 max uplink nodes — 8; Active/Standby — 2.
  • Max workload domains per VCF instance — 25.
  • Max workload domains per single SSO domain (ELM) — 15 including the management domain.
  • Max isolated VI workload domains per VCF instance — 24.
  • Max convert/import domains — 24.
  • WLD name — 3–20 chars, alphanumeric, no spaces.
  • Delete WLD — up to 20 minutes; create WLD — up to ~5 hours.

Reference documentation: VCF 5.2 Design Guide · VCF 5.2 Deployment Guide · NSX 4.2 Documentation · vSAN 8.0 Documentation.

Key Takeaways

  • VCF 5.2 BOM: ESXi 8.0U3, vCenter 8.0U3, NSX 4.2.x, vSAN 8.0U3
  • Flexible BOM allows independent component updates within tested compatibility ranges
  • Boot device minimum is 128 GB (SSD/NVMe recommended, no SD cards for production)
  • 32 GB RAM minimum per ESXi host; 512 GB+ recommended for production workload domains

VCF 5.2 Deep Dive: VCF 5.2 Deployment & Day-0#

VCF 5.2 Deployment & Day-0 VCF 5.2

VCF bring-up is a one-time, highly-orchestrated process: fill the Deployment Parameter Workbook, upload it into Cloud Builder, and Cloud Builder deploys vCenter, NSX Manager, SDDC Manager, and (optionally) Aria Suite Lifecycle on four prepared ESXi hosts (the bring-up minimum for standard and consolidated architectures alike; the 3-node figure applies only to clusters converted with VCF Import Tool 5.2.1.x), forming the management domain on a vSAN cluster. Once complete, SDDC Manager becomes the authoritative Day-N controller and Cloud Builder is powered off.

Planning prerequisites

  • Use the official Planning and Preparation Workbook and Deployment Parameter Workbook from the Broadcom Support Portal.
  • Rack and cable the four management ESXi hosts on leaf-spine (default) with 25-GbE or higher host-to-ToR links; disable LAG/LACP on all ESXi uplinks.
  • Prepare DNS — forward and reverse records for: each ESXi host, Cloud Builder, SDDC Manager, vCenter, NSX Manager cluster (3 nodes + VIP = 4 records), Aria Suite Lifecycle (if bundled), and any Aria VMs.
  • Configure NTP reachable from the management VLAN. Synchronise the Cloud Builder clock to the same source.
  • Ensure external services are ready: AD / LDAP (for post-deploy IdP), syslog target, SFTP server for backups.
  • Obtain licenses: VCF 5.2 uses traditional 25-character license keys (per-component: vSphere, vSAN, NSX, HCX, Aria, Workspace ONE Access). New vSphere 8.x / vSAN 8.x licenses are required when upgrading from older VCF versions.
  • Determine FIPS-140-2 mode: optional, set at bring-up ONLY — cannot be changed afterward.
  • Determine custom ESXi certificates: only JSON bring-up (not Excel) supports Custom ESXi certificate mode (securitySpec.esxiCertsMode=Custom, rootCaCerts).

Complete deployment workflow (20 steps)

  • Complete the Planning & Preparation Workbook.
  • Prepare physical infrastructure (racks, cabling, ToR switches, DNS/NTP servers).
  • Deploy the Cloud Builder OVA on ESXi, Workstation, or Fusion (4 vCPU / 4 GB / 279 GB).
  • SSH to Cloud Builder, verify ping to each ESXi host and DNS forward + reverse lookups.
  • (Optional) Create a custom ESXi ISO: Get-DepotBaseImages / Get-DepotAddons / New-IsoImage, or use vSphere Lifecycle Manager image export.
  • Install ESXi on all four management hosts (mount ISO, UEFI/BIOS boot, accept EULA, select boot disk ≥128 GB, set root password).
  • Configure host network via DCUI (F2): Configure Management Network → VLAN → Static IPv4 → DNS → set FQDN → confirm reboot.
  • Configure the VM Network port group VLAN on each host using the VMware Host Client.
  • Configure NTP on each host — Edit NTP Settings → enable → start with host → add servers → Save → Start.
  • Regenerate self-signed certificates after FQDN is set: enable SSH, run /sbin/generate-certificates, reboot, disable SSH. Cert files live at /etc/vmware/ssl/rui.crt and rui.key.
  • (Optional) Replace ESXi certs with external CA-signed certificates (copy to /etc/vmware/ssl as rui.crt / rui.key). This path requires JSON bring-up.
  • Download the Deployment Parameter Workbook from the Broadcom Support portal.
  • Fill in the workbook sheets: Credentials, Hosts and Networks (VLANs, vDS profile, hosts, inclusion ranges, thumbprints, NSX host overlay), Deploy Parameters (DNS / NTP / DNS zone / CEIP / FIPS, License Keys, vSphere, NSX, SDDC Manager).
  • (Optional) Convert the workbook to JSON to enable custom ESXi certs or automation.
  • Log into the Cloud Builder UI at https://<cloud-builder-fqdn>/ with admin credentials.
  • Accept EULA → Select VMware Cloud Foundation → acknowledge prerequisites.
  • Upload the completed workbook → wait for validation → resolve warnings/errors (Cloud Builder flags red cells for missing/invalid data).
  • Click Deploy SDDC. Cloud Builder provisions vCenter, NSX Manager cluster, SDDC Manager and forms the management domain. Watch /opt/vmware/bringup/logs/vcf-bringup-debug.log if something stalls.
  • On success, download the deployment report, click Finish, launch SDDC Manager, then power off Cloud Builder.
  • Day-0 hardening: configure online/offline depot, SFTP/file-based backups, replace VMCA certs with MS CA / OpenSSL / 3rd-party CA, rotate passwords, configure automation account.

The Deployment Parameter Workbook

The workbook is the authoritative input to bring-up. It has four tabbed sheets:

  • Introduction — overview, guidance and version notes.
  • Credentials — accounts & initial passwords for ESXi, SSO admin, vCenter root, NSX root/CLI/audit, SDDC Manager root/vcf/admin@local, Cloud Builder admin/root.
  • Hosts and Networks — VLANs, MTUs, IP ranges/subnet masks for mgmt, vMotion, vSAN, overlay; vDS profile choice; four (or more) host records with FQDN/IP; vSAN and vMotion IP inclusion ranges; optional ESXi SSL/SSH thumbprints.
  • Deploy Parameters — Existing Infrastructure (DNS, NTP, DNS zone, CEIP, FIPS); License Keys (vSphere, vSAN, NSX, SDDC Manager); vSphere Infrastructure; VMware NSX (VIP, subnet); SDDC Manager network.

Workbook rules: yellow cells contain sample values — replace them. Red cells flag missing or failed validation. Never copy and paste between cells (triggers Excel formula breakage). Workbook Excel validation is limited — Cloud Builder performs the authoritative validation on upload.

Password complexity at bring-up

The workbook rejects passwords that fail these rules:

Account typeLengthComplexity
SSO admin, vCenter root8–20Mix upper/lower/digit and one of @ ! # $ % ^ ?; no * {}[]()/\\\\'"\`~,;:.<>
NSX root, NSX UI/CLI admin, NSX audit12–127Same charset, plus at least 5 different characters
SDDC Manager admin@local12–127Same as NSX without 5-different-chars requirement
SDDC Manager root & super-user vcf, Cloud Builder admin & root≥15Same charset, must not contain dictionary word (e.g. VMware1! is rejected)

vDS profile choice

At bring-up you choose one of three profiles; other configurations require the API.

ProfileTopologypNICs
Profile 1Single vDS carrying Management + vMotion + vSAN + Host Overlay2 or 4 pNICs
Profile 2Two vDS — Primary: Management + vMotion + Host Overlay; Secondary: vSAN4 pNICs
Profile 3Two vDS — Primary: Management + vMotion + vSAN; Secondary: Host Overlay4 pNICs

Default vDS MTU = 9000. Each vDS can carry either an Overlay or VLAN Transport Zone. With vSAN ReadyNodes, the vDS count is frozen at bring-up — you cannot add a vDS to a cluster later.

ESXi thumbprint validation (optional)

If Validate Thumbprints = Yes in the workbook, collect each host's SSH fingerprint and SSL thumbprint before upload:
Start TSM-SSH temporarily on each host (VMware Host Client → Manage → Services), run the commands below from an SSH session on Cloud Builder (replace esxi-fqdn with the host FQDN), then stop TSM-SSH again (VCF 5.2 docs p.382):

# SSH fingerprint
ssh-keygen -lf <(ssh-keyscan esxi-fqdn 2>/dev/null)
# SSL thumbprint
openssl s_client -connect esxi-fqdn:443 < /dev/null 2> /dev/null | openssl x509 -sha256 -fingerprint -noout -in /dev/stdin

Cluster minimums you must honour at bring-up

ClusterSingle AZ minimumMulti-AZ minimum
Management default (vSAN)4 hosts at bring-up (3 only when converting an existing cluster with VCF Import Tool 5.2.1.x)8 hosts, equally distributed + witness
Management additional (vSAN)3 (4 recommended)6 (8 recommended)
Management additional (NFS/FC/vVols)3 minimumn/a
VI WLD (vSAN)3 (4 recommended)6 (8 recommended)
VI WLD (NFS/FC/vVols + vLCM images)2 minimumn/a
NSX Manager cluster3 nodes always
NSX Global Manager cluster (Federation)3 nodes active + 3 nodes standby
NSX Edge clusterMin 2 nodes; max 10
Workspace ONE Access cluster3 nodes behind NSX LB VIP
Anti-affinity floor for 3-node VM clusterMinimum 4 physical hosts in the underlying vSphere cluster

HA admission-control policy

Cluster typeCPU/Memory reserved
Management default, single AZ25%
Management default, multi-AZ50%
Additional or VI clusters, single AZ33%
Additional or VI clusters, multi-AZ50%

Compute overcommit — vCPU:pCPU ≤ 2:1 on the management domain, ≤ 8:1 on VI workload domains.

Creating a VI Workload Domain (Day-0+)

After bring-up, the first VI workload domain is created in SDDC Manager UI or API. Prerequisites:

  • DHCP on the NSX Host Overlay VLAN or a static IP pool.
  • Min 3 hosts in SDDC Manager inventory (2 for NFS/FC/vVols + vLCM images); 3 for Workload Management.
  • For vVols, the VASA provider must be added to vCenter first.
  • Free pNIC on each host; vLCM image available if using vLCM images.
  • NSX Manager and vCenter install bundles downloaded into SDDC Manager and matching the mgmt-domain versions.
  • Unique WLD name — 3–20 chars, no spaces, alphanumerics.
  • Passwords ready for the new vCenter root and NSX admin — 12–16 chars with upper + lower + digit + special from ! @ # $ ^ *; no dictionary words, palindromes, four-char monotonic sequences or three consecutive repeats.
  • All FQDNs/IPs resolvable in DNS.
  • NFS: datastore name, share path, NFS server IP; read/write permissions.
  • VMFS-FC: zoning done, volumes mounted, datastore created on hosts first.
  • License Now requires: NSX, vSAN (if used) and vSphere licenses.

Stretched cluster deployment

  • Management domain default cluster must be stretched first — prerequisite for stretching any VI WLD cluster.
  • Single stretch cluster = 8 hosts (4 per AZ) + witness in a third fault domain; site disaster tolerance = Site mirroring – stretched cluster.
  • Bandwidth ≥10 Gbps between AZs; RTT < 5 ms.
  • vSAN witness appliance sizes: Tiny (10 VMs / 750 witness components), Medium (500 VMs / 21,833), Large (>500 VMs / 45,000), XL (>500 VMs / 64,000).
  • Witness VMkernel adapter for vSAN witness traffic must be different from vSAN data VMkernel; on each ESXi host place vSAN-witness traffic on the Management VMkernel; on the witness appliance the same VMkernel carries management and witness traffic.
  • vSAN ESA or OSA clusters can be stretched on vSAN ReadyNodes from VCF 5.2 (5.2 release notes; Stretching vSAN Clusters: ESA or OSA); on VCF on Dell VxRail, ESA stretch starts at 5.2.1.1 and earlier releases stretch OSA only.
  • Only clusters created via the Stretch Cluster API are treated as stretched by VCF.

Import / convert an existing vSphere environment (VCF 5.2 new capability)

Starting with VCF 5.2, customers can convert an existing vSphere environment into a VCF management or workload domain without greenfield bring-up. The VCF Import Tool lives on SDDC Manager at /home/vcf/vcf-import-package/vcf-brownfield-import-<build>/vcf-brownfield-toolset; the primary script is vcf_brownfield.py.

  • Convert — a vSphere environment becomes the management domain.
  • Import — an existing vSphere environment is added as a VI workload domain (up to 24 convert/import domains per instance).
  • Requirements include: a supported vCenter on port 443 (custom ports not supported) at the BOM-aligned version, compatible ESXi builds consistent within each cluster, no NSX instance registered to the vCenter (the Import Tool deploys NSX from the uploaded bundle), one vCenter per SSO domain (ELM not supported), vDS-only networking with static VMkernel IPs, supported principal storage, and passing the Import pre-checks (network topology, certs, storage).
  • Workflow: run pre-check → generate inventory JSON → validate → run import → resolve remediations → verify in SDDC Manager.
  • Troubleshoot via /home/vcf/vcfimport alt path and support bundles (sos --health-check).

Day-0 hardening checklist

  • Configure Depot Settings — Online (VMware Depot via Broadcom Support Portal account) or Offline (FQDN/IP, port, user/pass; disables online depot).
  • Configure backups — SFTP target for file-based backup of SDDC Manager and each NSX Manager; image-based backups for vCenter (supplied by third-party).
  • Replace VMCA certificates with MS CA, OpenSSL or third-party CA.
  • Rotate all bring-up passwords via SDDC Manager Password Management.
  • Configure IdP: add AD over LDAP/OpenLDAP identity sources in vCenter SSO; optionally configure one external IdP (ADFS, Okta, or Microsoft Entra ID — Okta & Entra require vSphere 8.0 U2+ and NSX 4.1.2+).
  • Configure SoS baseline — sudo /opt/vmware/sddc-support/sos --health-check.
  • Power off Cloud Builder (do not delete).

Reference documentation: VCF 5.2 Getting Started & Deployment Guide · VCF 5.2 Design Guide.

Key Takeaways

  • Bring-up is a 20+ step automated workflow driven by Cloud Builder
  • Deployment Parameter Workbook (Excel) or JSON payload are the two input methods
  • Pre-validation checks: DNS, NTP, VLAN, MTU, ESXi thumbprints, vSAN HCL, licenses, passwords
  • Minimum 4 ESXi hosts for the management domain at bring-up, standard or consolidated architecture (consolidated needs more hosts for the customer workloads, not fewer); 3-node applies only to Import Tool 5.2.1.x conversions

VCF 5.2 Deep Dive: VCF 5.2 Day-2 Operations#

VCF 5.2 Day-2 Operations VCF 5.2

Day-2 in VCF 5.2 spans every operational task after bring-up: host and cluster life-cycling, certificate and password management, identity providers, backup/restore, monitoring, shutdown/startup, and administrative automation. This section covers SDDC Manager's operational surface, incorporates the ten authoritative VCF 5.2 operations study notes, and aligns with the Broadcom Administration and Operations guides.

1. SDDC Manager administration surface

  • UI: https://<sddc-manager-fqdn>/. Login with vcf/admin@local or an SSO identity. First-login onboarding guides you through depot, backup, CEIP, and password rotation.
  • API: https://<sddc-manager-fqdn>/v1/ exposed via the Developer Center. Swagger-style API Explorer in the UI.
  • SSH: vcf service account (sudo to root for break-glass).
  • CEIP: activate/deactivate from Administration → Customer Experience Improvement Program. Can be toggled at any time.
  • Health checks: sudo /opt/vmware/sddc-support/sos --health-check. Full SoS catalog below.
  • Service restart: echo 'y' | /opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.sh.
  • Version: cat /opt/vmware/vcf/version.txt.
  • PowerShell: VMware.VCF.* modules (installed via PowerShell Gallery) let you script every SDDC Manager operation.

2. Host management — commissioning, decommissioning, maintenance

  • Commissioning (Administration → Hosts → Commission Hosts): host must be installed, on the management VLAN, with FQDN in DNS, NTP configured, and a valid SSH fingerprint / SSL thumbprint. ESXi cert must be regenerated after FQDN change. Host is placed in the Unassigned Hosts pool.
  • Network pool is chosen during commissioning. A network pool bundles vMotion + vSAN (and optionally NFS) ranges. MTU range 1500–9000; VLAN range 0–4094.
  • Assignment: commissioned hosts join a cluster via Add Host (Inventory → Workload Domains → domain → Clusters → Actions → Add Host). For NSX-Edge-hosting clusters only L2 uniform NIC configurations are allowed; L2 non-uniform and L3 non-uniform are not permitted on such clusters.
  • Decommissioning: host must first be removed from its cluster. SDDC Manager then removes NSX host transport node role, certificates, and credentials.
  • Lockdown mode: configured in vCenter per host; Normal mode required for SDDC Manager LCM tasks on that host. KB 336894 describes disabling lockdown when LCM fails.
  • Replace host components — SDDC Manager supports replacement of disks, memory, NICs per the runbook in the Operations Guide (put host in maintenance mode → replace → exit maintenance → SDDC Manager auto-discovers; for NIC changes you may re-bind uplinks to the vDS).

3. Cluster management — add/remove hosts, scale out, delete

  • Add host (prereqs): host Active in inventory; balanced cluster warning if new host does not match pre-existing hosts; license present; same principal storage type (mgmt = vSAN; VI = any); for VMFS-FC pre-zoning + datastore; if Edge-hosting cluster only L2 uniform NICs; IP pool must have capacity; DPU vendor must match.
  • Add cluster: min 3 hosts (2 for NFS/FC/vVols + vLCM images); License Now requires vSphere + vSAN licenses; DHCP on Host Overlay VLAN unless static pool configured.
  • Expand / Shrink / Rename: SDDC Manager tracks cluster state and rebalances vSAN after resize; rename propagates to vCenter.
  • Multi-rack compute VI WLD: dedicated host uplink profile per rack, separate host TEP VLAN per rack, dedicated host TEP IP pool per rack. Uses L3 fabric between racks.
  • Delete WLD: up to ~20 minutes; KB 78635 for NSX Edge cluster deletion; KB 95445 to re-register NSX as an SSO relying partner.
  • Drift (Sync): under WLD → Manage Workload Domain Configuration Drift; SDDC Manager reconciles out-of-band changes in vCenter / NSX Manager. Backed by Configuration Updates of type FEATURE or FIX.

4. License key management

  • Administration → Licensing. 25-character license keys per product (vSphere, vSAN, NSX, SDDC Manager, Aria).
  • Update, add, relicense, or run a license-check; SDDC Manager tracks capacity use across all WLDs.
  • New vSphere 8.x / vSAN 8.x keys are required when upgrading to the VCF 5.2 BOM.
  • KB 319282 — VCF solution-license-key guidance.

5. Storage management (Day-2)

  • vSAN — Storage Management → vSAN. Maintain 30% free space floor. Mount remote vSAN datastore (OSA from OSA, ESA from ESA/Max) within the same WLD via HCI Mesh. Datastores on non-VCF clusters cannot be mounted on VCF clusters and vice versa.
  • NFS — datastore name, share path, NFS server IP; NFS mount requires vDS network pool and MTU 9000 preferred.
  • VMFS on FC — zoning, volume mount, datastore creation on hosts before adding to cluster.
  • HCI Mesh — cross-cluster remote datastore consumption (vSAN OSA or ESA). Administered via vSphere Client.
  • vVols — VASA provider required in vCenter; certificate rotation coordinated with VASA.

6. Monitoring & Supportability

  • SDDC Manager Notifications banner — fires on expiring certs (<30 days), failed tasks, and health events.
  • SoS utility: /opt/vmware/sddc-support/sos — full-stack health check, log collection, password check, certificate check, vSAN health, DNS/NTP validation.
  • Support dir: /var/log/vmware/vcf/sddc-support/.
  • DNS / NTP server updates — Administration → VMware CEIP → DNS Configuration / NTP Configuration; propagates changes across ESXi, vCenter, NSX, SDDC Manager.
  • Integrate with Aria Operations for Logs for centralized syslog and Aria Operations for capacity/performance.

7. User, group, and identity-provider management

  • Roles: Admin, Operator, Viewer.
  • Identity sources (vCenter SSO): AD over LDAP, OpenLDAP — added to the SSO domain as sources.
  • External IdP integration (VCF 5.2): one at a time — ADFS, Okta, or Microsoft Entra ID. Okta and Entra ID require vSphere 8.0 U2+ and NSX 4.1.2+.
  • Local service accounts: SDDC Manager vcf, admin@local; Cloud Builder admin, root; component root accounts per product.

8. Authoritative Day-2 study notes (from VCF 5.2 documentation)

The following seven study notes capture step-by-step procedures that the Broadcom documentation calls out as authoritative. Each note is sourced from the VCF 5.2 Administration and Operations guides. The remaining three standalones on lifecycle topics appear in the Lifecycle Management section.

VCF 5.2 Certificate Management VCF 5.2

Default signing CA per component
ComponentDefault signing CALCM
SDDC ManagerManagement domain VMCASDDC Manager UI or plug-in.
NSX Local ManagerManagement domain VMCASDDC Manager.
NSX EdgeNot applicable—
NSX Global ManagerSelf-signedManual — VCF does not manage.
vCenter ServerLocal workload-domain VMCASDDC Manager.
ESXiESXi VMCAManual, or API with Trusted Root for enterprise CA-signed initial deployment.
Supported external CAs
  • Microsoft Active Directory Certificate Services (enterprise CA).
  • OpenSSL (lab / disconnected).
  • Third-party CA via manual CSR + signed-cert install.
Microsoft CA integration prerequisites
  • CA URL MUST start with https:// and end with /certsrv, e.g. https://ca.rainpole.io/certsrv.
  • The same Windows Server must host both Certification Authority and Certification Authority Web Enrollment roles.
  • Web Server (IIS) with Basic Authentication enabled on the CertSrv site.
  • A “VMware” certificate template duplicated from the Web Server template, with Enhanced Key Usage Server Authentication + Client Authentication, Request Handling: Allow private key to be exported.
  • SDDC Manager account with Enroll permission on that template.
Standard rotation workflow
  • Administration → Security → Certificates → select component → Generate CSR.
  • Generate Signed Certificate (auto-signs via configured CA) OR upload an externally signed cert.
  • Install Certificate. SDDC Manager snapshots the target, installs the cert, and removes the snapshot.
Expired-certificate remediation order (critical)
  • Replace NSX Local Manager cluster/node cert (SDDC temporarily skips CA validation).
  • Replace vCenter cert with a VMCA-signed cert (SDDC temporarily skips CA validation).
  • Replace SDDC Manager cert.
  • Use SDDC Manager UI to replace NSX and vCenter again with the real external CA-signed certs.
Trust-store management
  • If a cert is rotated outside SDDC Manager, it must be added to the SDDC Manager trust store (available VCF 4.5.1+).
  • List: GET /v1/sddc-manager/trusted-certificates.
  • Remove by alias: DELETE /v1/sddc-manager/trusted-certificates/{alias}.
  • Add via Developer Center or POST /v1/sddc-manager/trusted-certificates with PEM payload.
Banner & auto-renewal

VCF 5.2 displays an expiry banner 30 days before cert expiry. There is no auto-renewal — auto-renewal is a VCF 9.x feature. Keep a calendar reminder aligned with the 30-day banner and the 15-day/5-day SoS thresholds.

VCF 5.2 Password Policy Matrix VCF 5.2

Default expiration
AccountDefault max ageNotes
SDDC Manager admin@localNeverBreak-glass; rotate manually.
SDDC Manager vcf (super user)365 daysUsed by automation.
SDDC Manager root90 daysAppliance root.
SDDC Manager backup365 daysInternal backup user.
administrator@vsphere.local90 daysDefault SSO admin; does not lock out.
vCenter root90 days (warn 7)Appliance root.
NSX Manager / Edge admin, root, audit90 daysPAM-governed; 12-127 char complexity.
Workspace ONE Access local users60 daysManaged by WSA policy.
ESXi local users99999 daysPractically never; set by Security.PasswordMaxDays.
Cloud Builder admin, root90 daysMin 15 chars.
Complexity requirements
AccountLengthCharacter classes
SDDC Manager root, vcf; Cloud Builder admin, root15+ (15–127)upper + lower + digit + special; no dictionary words.
SSO admin, vCenter root8–20min 1 upper, 1 lower, 1 digit, 1 special; max 1 identical adjacent.
NSX admin, NSX UI/CLI, NSX audit, SDDC admin@local12–1274 classes; keep ≤ 20 chars if using SDDC Manager password rotation — longer strings break rotation.
ESXi localretry=3, disabled/disabled/disabled/7/7 tiersPAM passwdqc; PasswordHistory = 0 by default.
Account lockout defaults
ComponentMax failsWindowUnlock durationNotes
ESXi5 (Security.AccountLockFailures)n/a900 s (AccountUnlockTime)Applies to ESXi Shell & API.
vCenter SSO5180 s900 sExcludes administrator@vsphere.local and system accounts.
vCenter appliance3—root 300 s / others 900 s/etc/security/faillock.conf may reset on restart.
NSX Manager API5180 s900 sPer-user.
NSX Manager CLI5—900 sVia PAM.
NSX Edge CLI5900 s900 s—
SDDC Manager local usersPAM faillock defaults—900 s—
Password rotation workflow (SDDC Manager)
  • Administration → Security → Passwords.
  • Select components → Rotate Now or Schedule (default 90-day cadence for rotatable components).
  • For credentials changed out-of-band, run Remediate Password to resynchronize SDDC Manager.
  • Use Credentials Lookup utility to retrieve current passwords; never read them from the backend DB.
  • Banner notification fires 14 days before expiry in the SDDC Manager UI.
Special caveats
  • Workspace ONE Access password rotation must be driven through Aria Suite Lifecycle for clustered deployments so the embedded Postgres user stays in sync.
  • Disallowed specials are documented per component; generally $ & / | are restricted in NSX and SDDC accounts.

VCF 5.2 Shutdown and Startup — Authoritative Order VCF 5.2

Why order matters

SDDC Manager and the NSX / vCenter control plane have dependencies that prevent clean shutdown if services are stopped in the wrong sequence. Violating the published order produces stale NSX control-plane state, vSAN object-alignment errors on restart, and vCenter inventory corruption.

Shutdown order — VI workload domains first (VCF 5.2 Administration, Table 339)
  1. Virtualised customer workloads (shut down gracefully or move off).
  2. Site Recovery Manager for the VI workload domain.
  3. vSphere Replication for the VI workload domain.
  4. NSX Edge nodes for the VI workload domain.
  5. NSX Manager nodes for the VI workload domain.
  6. vSphere Cluster Services (vCLS) VMs — place the cluster in Retreat Mode (config.vcls.clusters.domain-c<id>.enabled = false) so the vCLS VMs are removed.
  7. ESXi hosts and vSAN for the VI workload domain — vSAN Shutdown Cluster wizard, hosts into maintenance mode, power off.
  8. vCenter Server for the VI workload domain (last, so it can orchestrate steps 6-7).
Shutdown order — management domain (Table 341)
  1. Aria Automation cluster.
  2. Aria Operations analytics cluster and remote collectors.
  3. Clustered Workspace ONE Access.
  4. Aria Suite Lifecycle.
  5. Site Recovery Manager for the management domain.
  6. vSphere Replication for the management domain.
  7. Aria Operations for Logs.
  8. NSX Edge nodes for the management domain.
  9. NSX Manager nodes for the management domain.
  10. SDDC Manager.
  11. vSphere Cluster Services (Retreat Mode), management vCenter Server, management ESXi hosts and vSAN (Shutdown Cluster wizard).
Startup order — management domain first (Table 342)
  1. Management ESXi hosts, vCenter Server, vSphere Cluster Services and vSAN (exit Retreat Mode; the Shutdown Cluster wizard's Restart Cluster brings vSAN back).
  2. SDDC Manager.
  3. NSX Manager nodes for the management domain.
  4. NSX Edge nodes for the management domain.
  5. Aria Operations for Logs.
  6. vSphere Replication for the management domain.
  7. Site Recovery Manager for the management domain.
  8. Aria Suite Lifecycle.
  9. Clustered Workspace ONE Access.
  10. Aria Operations analytics cluster and remote collectors.
  11. Aria Automation cluster.
Startup order — each VI workload domain (Table 343)
  1. vCenter Server for the VI workload domain.
  2. ESXi hosts for the VI workload domain (and vSAN: Restart Cluster; exit vCLS Retreat Mode; re-enable HA).
  3. NSX Manager nodes, then NSX Edge nodes for the VI workload domain.
  4. vSphere Replication, then Site Recovery Manager.
  5. Virtualised customer workloads.
Key commands
  • Retreat Mode: Configure > vSphere Cluster Services > Advanced Options → set config.vcls.clusters.domain-c<id>.enabled to false, save, wait 1 minute; vCLS VMs auto-remove.
  • vSAN Shutdown wizard: Cluster > Actions > vSAN > Shutdown Cluster (8.0+); wizard handles on-disk quiescence, witness (for stretched), and power-off order.
  • Host enter maintenance (no data migration, preferred for planned shutdown): esxcli system maintenanceMode set -e true -m noAction.
Common failure modes
  • Skipping Retreat Mode leaves vCLS VMs stuck during vSAN shutdown — they are protected from power-off and block the wizard.
  • Shutting down the management vCenter before SDDC Manager (vCenter is in the last management step, after SDDC Manager) leaves SDDC Manager unable to drive the cluster shutdown.
  • Powering VI NSX Edges off after VI NSX Managers can strand BGP sessions and produce stale VTEP state.

VCF 5.2 Backup and Restore VCF 5.2

SDDC Manager backup (documented example schedule)
  • SDDC Manager file-based backup is not configured by default: register an external SFTP target first, then set Administration > Backup > SDDC Manager Configurations > Backup Schedule (VCF 5.2 docs p.664).
  • Documented example values: Automatic Backup enabled, daily at 04:02 AM, Take Backup on State Change enabled; retain last 7 backups, hourly backups for 1 day, daily backups for 7 days. Recommended frequency is daily with 7-day retention (p.663).
  • Encryption passphrase protects the tarball.
  • External SFTP target is a prerequisite for file-based backup and restore.
SFTP requirements (authoritative)
  • Publish BOTH a 256-bit ECDSA and a 2048-bit RSA SSH public key.
  • Allowed host-key algorithms: rsa-sha2-512, rsa-sha2-256, ecdsa-sha2-nistp256/384/521.
  • FIPS MAC: hmac-sha2-256. FIPS Kex: diffie-hellman-group-exchange-sha256. SHA-1 rejected.
  • SFTP host fingerprint must be captured in the SDDC Manager backup config; path, user, password or key required.
NSX Local Manager backup
  • Configured automatically during bring-up; cluster backup runs hourly.
  • Inventory backups on change (~5-minute cadence).
  • Retained 7 days on the same SFTP endpoint.
vCenter Server backup
  • Configured on the vCenter VAMI (port 5480) — not through SDDC Manager.
  • Targets: SFTP, FTPS, HTTP(S), SCP, NFS, SMB.
  • Recommendation: weekly full + daily incremental, or daily full for smaller vCenters.
  • Coordinate SDDC Manager and all same-SSO vCenter backup schedules into the SAME 5-minute window for consistent restore.
File-based restore of SDDC Manager
  • Deploy a new SDDC Manager appliance from OVA matching the backup version.
  • Provide the SFTP location and encryption passphrase.
  • Restore runs in approximately 45 minutes; full NSX + vCenter inventory reconciliation ≈ 2 hours.
Image-based (VM-level) backup

Not supported as a primary recovery mechanism for SDDC Manager. Use file-based restore for SDDC Manager; use native vCenter restore for vCenter; use NSX file-based restore for NSX Manager. Image-based backup may supplement, but do not attempt quiesced VMDK snapshots of SDDC Manager for production recovery.

RPO / RTO
ScenarioRPORTO
SDDC Manager daily24 h~45 min
NSX Local Manager hourly1 h~2 h (cluster rebuild + inventory reconcile)
vCenter daily full24 h30–60 min

VCF Import Tool (VCF 5.2 / 5.2.1) VCF 5.2

Purpose

Brings brownfield vCenter / NSX / ESXi estates under VCF management without reinstalling. Two scenarios:

  • Convert (Scenario A): existing vCenter environment becomes the management domain of a new VCF instance — SDDC Manager is deployed fresh and imports the existing components.
  • Import (Scenario B): existing vCenter environment becomes a VI workload domain of an existing VCF instance.
Build / version matrix
  • VCF Import Tool 5.2: pairs with SDDC Manager 5.2.x.
  • VCF Import Tool 5.2.1.2 + SDDC Manager 5.2.1.1 — first release that supports LACP on imported vDS.
  • Target vCenter MUST use HTTPS port 443. Custom ports are not supported.
  • VMFS-FCoE as principal for a converted management default cluster is supported from VCF 5.2.1.
Supported principal storage on import
  • Converted management default cluster: vSAN, NFS v3, VMFS-FC, VMFS-FCoE (5.2.1+). Greenfield management domains still require vSAN.
  • NFS v4.1, VVOLs, and native iSCSI are NOT supported for a converted default management cluster.
  • VI WLDs (via Import scenario): vSAN / NFS v3 / VMFS-FC (VMFS-FCoE from 5.2.1); NFS 4.1, vVols and native iSCSI are not supported for imported or converted domains (Table 315 lists vVols as No for both).
Cluster constraints
  • Management domain default cluster minimum: 4 hosts at bring-up; a converted cluster needs 4 nodes with Import Tool 5.2 and 3 with 5.2.1.x.
  • VI workload domain minimum: 3 hosts (2 with NFS / VMFS-FC / vVols + vLCM images).
  • All hosts in an imported cluster must share the same ESXi patch level and the same vDS version.
  • Source vDS must not use LACP unless Import Tool 5.2.1.2 + SDDC 5.2.1.1.
High-level workflow
  • The VCF Import Tool is a script bundle (vcf-brownfield-import-<build>.tar.gz), not a VM or OVA. Scenario A only: copy it to the target vCenter appliance, extract it and run python3 vcf_brownfield.py precheck (read-only), then remove it from the vCenter.
  • Deploy SDDC Manager OVA (Scenario A only) — do not yet associate with the vCenter.
  • Copy the NSX bundle and the VCF Import Tool to the SDDC Manager appliance (/home/vcf/vcf-import-package), extract it and run python3 vcf_brownfield.py check against the target vCenter to produce the readiness report.
  • Remediate: align ESXi builds, remove unsupported LACP (if unsupported combo), confirm no NSX instance is registered to the vCenter (the tool deploys NSX; upload the NSX bundle to SDDC Manager first), clean up unsupported storage (NFS 4.1, vVols, native iSCSI, stretched vSAN), align vDS names, ensure no custom port 443 overrides, break ELM if present.
  • Run python3 vcf_brownfield.py convert (Scenario A) or import (Scenario B) from the SDDC Manager appliance — the tool drives SDDC Manager inventory ingestion.
  • Post-import: run the Sync workflow in SDDC Manager to reconcile configuration drift, then rotate passwords and certificates through SDDC Manager to bring them under policy.
SSO rules
  • Scenario A: the existing SSO domain becomes the VCF SSO domain. Default vsphere.local still permitted but a custom SSO domain is preserved.
  • Scenario B: the imported vCenter must be alone in its SSO domain — Enhanced Linked Mode is not supported for import or convert; remove the vCenter from any ELM ring first. SSO domain names need not be unique within the VCF instance.
Post-import housekeeping
  • Rotate all credentials through SDDC Manager.
  • Configure SFTP backup target; run first SDDC Manager backup.
  • Ensure NSX Manager cluster backup has switched to SDDC-configured hourly cadence.
  • Install licenses via SDDC Manager > Administration > Licensing.

Stretched vSAN Clusters in VCF 5.2 VCF 5.2

Supported topology
  • Two data sites (AZ1, AZ2) plus a witness host at a third site.
  • Supported for management default cluster (multi-AZ min 8 hosts) and for VI workload domain clusters (multi-AZ min 6, 8 recommended).
  • Each site is represented by a vSAN Fault Domain; witness is a vSAN Witness Appliance (virtual ESXi).
  • ESA clusters can be stretched on vSAN ReadyNodes from VCF 5.2; on VCF on Dell VxRail from 5.2.1.1 (earlier VxRail releases stretch OSA only). A cluster with a mounted vSAN remote datastore or a storage policy shared with other clusters cannot be stretched.
  • HCI Mesh is NOT supported on stretched clusters.
Latency and bandwidth
LinkRTTBandwidth
AZ1 ↔ AZ2 (data-to-data)< 5 ms≥ 10 Gbps
Data ↔ Witness≤ 200 ms (≤ 10 hosts/site); < 100 ms (11–15 hosts/site)100 Mbps minimum (generic vSAN)
NSX Manager inter-node< 10 ms—
NSX Manager ↔ Transport Node< 150 ms—
Cross-vCenter vMotion< 150 ms—
VLAN and MTU
  • Each AZ has its own management, vSAN, vMotion, NSX Host Overlay VLANs routed between sites.
  • vSAN / vMotion / Overlay MTU 9000 end-to-end; Geneve minimum 1700 per VCF 5.2.
  • Witness traffic separation (WTS) recommended: dedicated VMkernel on data hosts pointing to the witness network.
Storage policy
  • Site Disaster Tolerance = Dual site mirroring. FTT within site configurable (1 or 2) depending on host count.
  • Preferred site defined; secondary takes over on preferred-site failure.
  • Read Locality automatic — reads served from the local site except during recovery.
HA configuration
  • Admission control: 50% CPU/memory for multi-AZ (VCF-CLS-RCMD-CFG-004 family).
  • Set multiple das.isolationaddress0..4 pointing to gateways at both AZs.
  • Set das.iostatsinterval = 0 to reduce false positives on VMCP.
  • Configure VM/Host DRS groups and VM-Host should rules to anchor workloads to their preferred AZ.
Unsupported configurations
  • ESA + stretched cluster.
  • Stretched + HCI Mesh.
  • Stretched + vSAN Max.
  • Witness appliance on either data AZ (must be third site or colocated with management of a separate instance).
SDDC Manager stretch workflow
  • Deploy the vSAN Witness Appliance at the third site; add to management vCenter (not to any VCF cluster).
  • Run the SDDC Manager stretch cluster API: PATCH /v1/clusters/{id} with a clusterUpdateSpec containing clusterStretchSpec (VCF 5.2 docs p.590).
  • SDDC Manager configures fault domains, witness, NSX transport node profiles, DRS/HA settings.
  • Post-stretch: verify with sos --health-check --domain-name <domain-name>.

NSX Federation in VCF 5.2 VCF 5.2

Concept

NSX Federation unifies the NSX control plane across multiple VCF instances. Each instance retains its NSX Local Manager; a new NSX Global Manager cluster (active + standby) provides cross-instance network/security object definitions and policy push.

Deployment requirements
  • NSX Global Manager cluster: 3 Medium nodes (active); optional 3-node standby cluster at the secondary instance.
  • Deployed manually — SDDC Manager does not orchestrate NSX Global Manager lifecycle in VCF 5.2.
  • Each instance must run the same NSX version (patch levels aligned).
  • Inter-instance RTT < 500 ms (VCF-NET-REQD-CFG-006).
  • Cross-vCenter vMotion mobility: < 150 ms.
Topology options
  • Active / Standby: one location runs the primary Global Manager cluster; the other is standby, promoted manually.
  • Stretched networks (Tier-1 spanning two locations) or Tier-1s pinned to a single location with cross-location Tier-0 ECMP.
  • Distributed Firewall policy defined on Global Manager, pushed to every Local Manager.
Constraints in VCF 5.2
  • AVN (Application Virtual Networks) is NOT supported when the management NSX is part of Federation.
  • NSX Global Manager upgrades are manual — follow the NSX upgrade guide, always upgrade Global Manager before any Local Manager in the same federation.
  • NSX Global Manager certificates are self-signed by default and must be manually rotated.
  • Configuration drift reconciliation (Sync) only applies to Local Managers; Global Manager is out of SDDC Manager scope.
Federation-aware upgrade order
  • NSX Global Manager standby cluster first (VCF 5.2 Table 351, Upgrade NSX With Federation).
  • Then the active NSX Global Manager cluster.
  • Each instance's NSX Local Manager and Edges.
  • Then continue the usual per-instance order: vCenter → ESXi.
Tier-1 location config
  • Tier-1 can be location-specific (pinned) or stretched (active-active across locations).
  • Edge cluster placement must satisfy service HA: Active-Standby needs exactly 2 Edges at the service location; Active-Active up to 8.

9. Backup & restore — comprehensive matrix

ComponentMethodNotes
SDDC ManagerSFTP file-based backupEncrypted with a backup passphrase. Configure under Administration → Backup Configuration. Recommended every 24 h. On-demand backups run before upgrades.
vCenter ServervCenter built-in file-based backup (FTPS/SCP/HTTP/HTTPS/SMB/NFS/SFTP)Can also be image-based snapshot backed up by third-party (Veeam, Avamar).
NSX ManagerNSX native SFTP backupSchedule interval + on-demand. Cluster backups include all three nodes.
NSX EdgeBacked up as part of NSX Manager backupRedeploy from NSX Manager if an Edge is lost.
Aria Suite LifecycleImage-based + file-basedFollows Aria Suite LCM backup workflow.
Workspace ONE AccessImage-basedCluster: snapshot all 3 nodes coordinated.
ESXiConfig backup via host (host profile or vim-cmd hostsvc/firmware/backup_config)Not centrally orchestrated by SDDC Manager.

10. Key paths, commands and URLs (quick reference)

  • Cloud Builder bring-up log: /opt/vmware/bringup/logs/vcf-bringup-debug.log
  • Cloud Builder logs dir: /var/log/vmware/vcf/bringup/
  • SDDC Manager support logs: /var/log/vmware/vcf/sddc-support/
  • SoS utility: /opt/vmware/sddc-support/sos
  • Service restart: echo 'y' | /opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.sh
  • ESXi cert regenerate: /sbin/generate-certificates (cert files in /etc/vmware/ssl as rui.crt / rui.key)
  • vSAN HCL JSON URL: historically https://partnerweb.vmware.com/service/vsan/all.json (endpoint retired post-Broadcom; current HCL data via https://compatibilityguide.broadcom.com/; cached locally at /opt/vmware/bringup/tmp/all.json)
  • NFS bundle mount: /nfs/vmware/vcf/nfs-mount/bundle/
  • SDDC Manager import tool dir: /home/vcf/vcf-import-package/vcf-brownfield-import-<build>/vcf-brownfield-toolset
  • Postgres: DB platform, user postgres.
  • Trusted cert API: GET /v1/sddc-manager/trusted-certificates, DELETE /v1/sddc-manager/trusted-certificates/{alias}.
  • Cloud Builder UI: https://<cloud-builder-fqdn>/ with admin default user.
  • vCenter management interface: https://<vcenter-fqdn>:5480 (port 443 required for import).

11. Important KB references

  • KB 88287 — supported async patches.
  • KB 78635 — deleting an NSX Edge cluster.
  • KB 95445 — re-register NSX as a relying partner after WLD delete.
  • KB 378126 — 100 HTTP API req/sec NSX limit.
  • KB 336894 — disable Lockdown Mode to unstick LCM.
  • KB 70656 — TRUSTED_ROOT_CRLS store issue.
  • KB 85527 — CertGenVVS tool.
  • KB 408300 — using non-certified ESA disks for PoC only.
  • KB 319282 — VCF solution license-key guidance.
  • KB 92227 — vSphere with Tanzu specific upgrade sequence.
  • KB 312168 — offline depot configuration.
  • KB 312159 — disabling unused TPM modules.

Reference documentation: VCF 5.2 Administration Guide · VCF 5.2 Operations Guide · vSAN 8.0 Documentation.

Key Takeaways

  • Password rotation is critical: SDDC Manager manages passwords for vCenter, NSX, ESXi, Aria components
  • Certificate management supports Microsoft CA, OpenSSL, and third-party CAs (ESXi certs NOT managed)
  • SoS utility (/opt/vmware/sddc-support/sos) is the primary health check and support bundle tool
  • Backup strategy: file-based (SFTP) and image-based (snapshots) with encrypted backup passphrase

VCF 5.2 Deep Dive: VCF 5.2 Lifecycle Management#

VCF 5.2 Lifecycle Management VCF 5.2

Lifecycle Management in VCF is the orchestrated, prescribed-order upgrade and patching of every component in a workload domain's Bill of Materials. SDDC Manager is the sole entry point: it downloads bundles from the depot, stages them, runs pre-checks, and enforces the upgrade sequence. VCF 5.2 introduces three important flexibilities — Independent SDDC Manager Upgrade, Flexible BOM, and native Async Patch — while keeping the same six BOM-state machine and strict management-domain-first rule.

1. Upgrade path support (5.2 target)

  • You can upgrade to VCF 5.2.x sequentially or with skip-level from VCF 4.5, 5.0, or 5.1.
  • Any VCF instance running a release earlier than 4.5 must first upgrade the management domain and all VI workload domains to 4.5.x before targeting 5.2.
  • For clusters with vSphere with Tanzu / Workload Management, consult KB 92227 for the Supervisor-aware upgrade sequence.
  • Verify the Broadcom Interoperability Matrix and the VCF 5.2.x Release Notes before any upgrade.

2. Bundle types & depot

SDDC Manager supports two depot modes (one at a time): Online (VMware Depot via Broadcom Support Portal) and Offline (FQDN/IP, port, user/pass). Switching to offline disables and removes the online depot connection.

  • Install Bundles — binaries for creating VI workload domains (vCenter, NSX, Aria Suite Lifecycle). Labelled Install Only Bundle in the UI.
  • Upgrade Bundles — the main LCM artefact. Upgrades a specific component to a target BOM version.
  • Async Patch Bundles — critical out-of-cycle patches to NSX Manager / vCenter / ESXi when no upgrade bundle exists. Starting in VCF 5.2 these can be downloaded directly in the SDDC Manager UI or via the Bundle Transfer Utility (pre-5.2 required the Async Patch Tool just to fetch them).
  • Independent SDDC Manager Bundles — 4th-digit bundles (e.g. 5.2.0.1) that upgrade SDDC Manager by itself once the instance is at 5.2+.
  • Flexible BOM Upgrade Bundles — let you select specific target versions per component (including async-patch versions) when upgrading.

3. The six BOM states

StateMeaning
Source BOMAll components at the previous VCF version's BOM.
SDDC Manager onlySDDC Manager upgraded to 5.2; all other BOM components still on source.
Split BOMManagement domain OR a VI WLD partially updated to 5.2 (an upgrade is in progress).
Mixed 4.5.x/5.x BOMSome WLDs on 5.2 and at least one VI WLD on a 4.5.x source BOM.
Mixed 5.x BOMSome WLDs on 5.2 and at least one VI WLD on a 5.0 or 5.1 source BOM.
Target BOMAll components at 5.2.

4. Upgrade order (management-domain first, always)

  • SDDC Manager (management domain) — must upgrade first. Always backed up automatically before upgrade.
  • Aria Suite (via Aria Suite Lifecycle) — Workspace ONE Access → Aria Operations for Logs → Aria Operations → Aria Automation → Aria Operations for Networks.
  • NSX Global Manager (if using Federation).
  • NSX Local Manager cluster (management domain).
  • NSX Edge cluster.
  • ESXi host transport nodes (via vLCM image remediation).
  • vCenter Server (management domain).
  • ESXi hosts (management cluster, vLCM image remediation).
  • vSAN on-disk format upgrade (post-ESXi, if required).
  • Repeat steps 3–9 for each VI Workload Domain — but you may upgrade multiple VI WLDs in parallel (different WLDs) subject to resource windows.
  • Post-upgrade tasks: clear stale ARP after vCenter switchover (ip -s -s neigh flush all), NFS re-mount validations, re-run SoS health-check.

Summary: SDDC Manager (the VCF upgrade bundle, once per instance) → Configuration Updates → Aria Suite Lifecycle and the Aria products → NSX (Global Managers first if federated, then Local Managers and Edges) → vCenter → ESXi clusters (vLCM images) → vSAN on-disk format; then the same NSX → vCenter → ESXi sequence for each VI workload domain. Skip-level upgrades are supported: VCF 5.2.x can be reached sequentially or skip-level from VCF 4.5 or later (Lifecycle Management Guide).

5. Upgrade prerequisites (authoritative list)

  • Allocate a temporary IP address per vCenter upgrade when upgrading from 4.5.x (management subnet; can be reused sequentially). Also required for every 5.2.1 vCenter RDU upgrade.
  • Obtain updated vSphere 8.x / vSAN 8.x licenses.
  • Verify no expired or expiring passwords (Password Management dashboard).
  • Verify no expired or expiring certificates on every workload domain.
  • Verify ESXi TPM module status: if present, run latest 2.0 firmware or disable in BIOS (KB 312159).
  • Verify ESXi hardware is on the target version's VMware Compatibility Guide.
  • Manually update the vSAN HCL database (KB 2145116).
  • Back up SDDC Manager, every vCenter, and every NSX Manager (file-based and image-level). Take a cold snapshot of SDDC Manager.
  • Ensure no failed workflows and no resources in activating or error state — halt and call Broadcom Support if any.
  • Read the 5.2 Release Notes for known upgrade issues.
  • Deactivate all VCF 4.x async patches and run inventory sync before upgrading (VCF 5.0+ no longer requires the Async Patch Tool for upgrades from async-patched VCF).
  • Review the NSX Upgrade Guide's Operational Impacts section.
  • Ensure no active alarms in vSphere Client.
  • Download the upgrade bundles for every component being upgraded.

6. Pre-check procedure (VCF 5.2)

  • Inventory → Workload Domains → [domain] → Updates → Run Precheck.
  • Target Version dropdown: choose General Upgrade Readiness or a specific 5.2.x target.
  • Parallel prechecks across multiple WLDs are supported.
  • The precheck validates ~40 items: disk space, backup currency, certificate state, vSAN health, NTP skew, password state, BOM compatibility, drift.
  • Versions prior to SDDC Manager 5.0 run the legacy Precheck Update — Versions Prior to SDDC Manager 5.0 variant.

7. Bundle download (online)

  • Administration → Depot Settings → Authenticate for the VMware Depot with Broadcom Support Portal credentials.
  • Lifecycle Management → Bundle Management → Bundles tab. The Availability column shows Available (apply now) or Future (another bundle must apply first).
  • Click View Details for version/release-date details; Download Now or Schedule Download; see the Download History tab.

8. Offline / dark-site depot workflow

  • On an internet-connected host, run the Bundle Transfer Utility (lcm-bundle-transfer-util) with --download and the required manifest; only this tool is supported.
  • Transport bundles to the dark site.
  • On the SDDC-Manager-side, configure the Offline Depot (Administration → Depot Settings → Set Up → FQDN/IP, port, user/pass). This disables and removes the online depot connection.
  • Upload bundles to the depot with --upload.
  • VCF 5.2+ supports shared offline depots across multiple SDDC Manager instances (KB 312168).

Proxy: SDDC Manager supports an HTTPS proxy for online depot. The Bundle Transfer Utility accepts its own proxy options.

9. Transition from vSphere Lifecycle Manager Baselines to Images

  • VCF 5.2 encourages moving clusters from vLCM Baselines (the older workflow) to vLCM Images for declarative management.
  • Prerequisites: supported topology, all hosts at the baseline target, current NSX Transport Node profile compatible, valid vLCM image candidate from the depot.
  • Compliance states: Compliant, Non-compliant, Unknown, In Progress, Staged. Some known false positives can be added to the cluster's Ignore List.
  • PowerShell: menu-driven wrapper provided; key cmdlets reach the Compliance-Check / Transition / Remediation APIs.
  • API path: POST /v1/clusters/{id}/vlcm-transition with image spec.

10. Management domain upgrade — step by step

  • Run precheck against the management domain; resolve all failures.
  • Apply the VCF upgrade bundle to SDDC Manager.
  • Apply Configuration Updates (drift) required for the target BOM.
  • Upgrade Aria Suite via Aria Suite Lifecycle workflow.
  • If Federation: upgrade NSX Global Manager first (LCM orchestrated).
  • Upgrade the management-domain NSX Manager cluster (prechecked, then applied; upgrade affects only this WLD's NSX because shared NSX cluster upgrades wait for all sharing WLDs).
  • Upgrade the management-domain vCenter Server (uses a temporary IP when source is 4.5.x).
  • Upgrade the management-cluster ESXi hosts via vLCM image remediation (SDDC Manager orchestrates cluster remediation: host → maintenance → remediate → exit → next).
  • Post-upgrade tasks: verify SSO/ELM, vSAN health, NSX health, Aria integration, SDDC Manager dashboards.

11. VI workload domain upgrade — step by step

  • Precheck the VI WLD.
  • Component order: NSX Local Manager cluster → NSX Edge cluster → ESXi transport nodes → vCenter Server → ESXi hosts → (optional) vSAN on-disk format.
  • For shared NSX Manager deployments, NSX Manager is upgraded only when every host cluster in every sharing WLD is selected for upgrade. Upgrading just one of the sharing WLDs upgrades its transport nodes but leaves NSX Manager at the source BOM.
  • Post-upgrade: re-test HA, DRS, vSAN, NFS re-mounts, Edge service health.

12. Patching (5.2+)

  • Lifecycle Management → Plan Patching: browse available async and upgrade patches per domain.
  • Install vCenter / ESXi / NSX patches in place of a full upgrade when only a fix-level patch is needed.
  • SDDC Manager precheck enforces compatibility; incompatible combinations block apply.

13. Independent SDDC Manager Upgrade

  • Allows upgrading just SDDC Manager (and the VCF services) without touching vCenter / NSX / ESXi.
  • Delivered via a dedicated bundle tile in the UI (4th-digit version such as 5.2.0.1).
  • Prerequisites: instance already at 5.2+, no failed workflows, backups current, depot configured.
  • Useful for consuming new VCF orchestration capabilities early; managed components can remain at their current BOM for a time-bounded window.

14. Troubleshooting upgrades

  • SDDC Manager issues: restart services script above; check /var/log/vmware/vcf/sddc-support/; run sos --health-check.
  • vCenter issues: after switchover, traffic stalls on hosts — clear stale ARP with ip -s -s neigh flush all; see KB 370882 for vCenter 6.5 → 8.0 U3 upgrade edge cases.
  • NSX shared-cluster issues: verify every sharing WLD is selected; KB 95445 to re-register NSX post-WLD delete.
  • Lockdown on ESXi blocks LCM tasks — KB 336894 to disable.

15. Authoritative lifecycle study notes (from VCF 5.2 documentation)

The following two notes are sourced directly from the VCF 5.2 Lifecycle Management Guide and the Async Patch Tool 1.2 documentation.

SDDC Manager Upgrade States and Bundle Types VCF 5.2

Upgrade BOM states

The six states are those of §3 above (Lifecycle Management Guide, Upgrade States and Terminology): Source BOM, SDDC Manager only, Split BOM, Mixed 4.5.x/5.x BOM, Mixed 5.x BOM, Target BOM. SDDC Manager functions available during the upgrade vary with the state of each domain. Flexible BOM is an upgrade option (below), not a BOM state; a component carrying an async patch is still described by these six states.

Bundle types (Lifecycle Management Guide, Other Bundle Types)
  • Upgrade Bundles: the main lifecycle artefact — component upgrades for the management domain and VI workload domains.
  • Install Bundles: software binaries to install VI workload domains (vCenter and NSX) and Aria Suite Lifecycle; downloaded the same way as upgrade bundles and marked "Install Only Bundle" in the UI.
  • Async Patch Bundles: critical patches for NSX Manager, vCenter and ESXi when no update or upgrade bundle is available; VCF 5.1 and earlier need the Async Patch Tool to download them, from VCF 5.2 they download through the SDDC Manager UI or the Bundle Transfer Utility.
  • Not bundle types: the independent SDDC Manager upgrade and the Flexible BOM upgrade are upgrade options surfaced in the Updates view; Configuration Updates (drift reconciliation) are applied from the Repository's Configuration Updates tab and are delivered with the release, not as a bundle class of their own.
Flexible BOM Upgrade
  • VCF 5.2 introduces Flexible BOM: permits upgrading vCenter or NSX ahead of ESXi within a support matrix.
  • Guardrails enforced by SDDC Manager precheck — incompatible combinations block.
  • Intended for customers pinned on a specific ESXi build.
Configuration Updates (drift reconciliation)
  • Types: FEATURE (adds prescribed capability) and FIX (re-aligns existing state).
  • CloudAdminRoleConfigDrift (VCF 5.0).
  • DvpgConfigurationDrift (VCF 5.1) — creates VM_MANAGEMENT DVPG and migrates management VMs for traffic separation.
  • RegisterSDDCmanagerAsVCExtensionConfigDrift (VCF 5.2).
  • vSAN HA isolation-address drift, Compute Manager registration drift.
  • Apply through SDDC Manager Repository → Configuration Updates tab.
Precheck (VCF 5.2)
  • UI location: Inventory → Workload Domains → [domain] → Updates → RUN PRECHECK.
  • Target Version dropdown: “General Upgrade Readiness” + available VCF targets.
  • Parallel precheck across multiple workload domains supported.
  • Validates ~40 items — disk space, backup status, certs, vSAN health, NTP skew, password health, BOM compatibility, drift.
  • Versions prior to SDDC Manager 5.0 run the legacy “Precheck Update - Versions Prior to SDDC Manager 5.0” variant.

Flexible BOM Upgrade and Async Patch Tool VCF 5.2

Async Patch Tool (ASPT)
  • Delivered as a separate Broadcom-supplied CLI.
  • Applies critical component patches (NSX / vCenter / ESXi) outside the main BOM cadence.
  • Not required to enable the 5.x→5.x upgrade path — SDDC Manager natively exposes async patches starting VCF 5.2 under Plan Patching.
  • For 4.y → 5.x upgrades from an async-patched 4.y state, ASPT is still required to unblock the upgrade path.
  • Runtime prompts: patch selection, parallel download confirmation, deployment confirmation; supports dry-run mode.
  • Log path: /var/log/async-patch-tool/.
Flexible BOM
  • Allows vCenter or NSX to be upgraded ahead of ESXi within a published support matrix.
  • SDDC Manager precheck enforces compatibility; non-supported combinations block the upgrade.
  • Useful for pinning ESXi on an unchanged vSphere build while adopting a newer NSX or vCenter patch.
Independent SDDC Manager Upgrade
  • Upgrades SDDC Manager and the VCF services without touching vCenter / NSX / ESXi.
  • Delivered via a dedicated bundle tile in the UI.
  • Useful for consuming new VCF orchestration capabilities sooner; the managed components can remain on their current BOM for a time-bounded window.
Bundle Transfer Utility (offline)
  • CLI: lcm-bundle-transfer-util — only supported download tool for offline use.
  • Workflow: (1) on internet-connected host, download the manifest and bundles with --download; (2) transport to dark site; (3) on SDDC Manager side, --upload to the local depot.
  • VCF 5.2+ supports shared offline depots (KB 312168).
  • Configuring an offline depot DISABLES and removes the online depot connection — SDDC Manager supports one depot type at a time.
Temporary-IP rules for vCenter upgrades
  • Required for every vCenter upgrade from a VCF 4.5.x source.
  • Required for all VCF 5.2.1 vCenter RDU upgrades.
  • IP can be reused sequentially across vCenters; parallel upgrades need additional temp IPs.
  • If traffic stalls on hosts after switchover: clear stale ARP with ip -s -s neigh flush all.
NSX upgrade scope in shared-NSX deployments

When several workload domains share an NSX Manager cluster, NSX Manager is only upgraded when every host cluster in every sharing workload domain is selected for upgrade. Upgrading just one of the sharing workload domains upgrades its transport nodes but leaves the NSX Manager cluster on the source BOM.

16. Async Patch Tool 1.2 — reference

  • Delivered as a separate Broadcom-supplied CLI; not required for 5.x → 5.x upgrades (starting VCF 5.2, async patches are exposed in SDDC Manager natively under Plan Patching).
  • Still required for 4.y → 5.x upgrades from an async-patched 4.y state (unblocks the path).
  • Two modes: online (fetches bundles over the internet) and offline (pre-staged bundles).
  • Runtime prompts: patch selection, parallel download confirmation, deployment confirmation. Supports dry-run.
  • Log path: /var/log/async-patch-tool/.
  • Upgrade matrix after applying an async patch is documented in KB 88287.

17. Flexible BOM Upgrade — reference

  • Lets you choose specific target versions per component (e.g. upgrade vCenter ahead of ESXi) within a published support matrix.
  • SDDC Manager precheck enforces compatibility; non-supported combinations are blocked.
  • Typical use case: pin ESXi on an unchanged vSphere build while adopting a newer NSX or vCenter patch.
  • Procedure: Lifecycle Management → Upgrades → select a WLD → choose Flexible BOM Upgrade → pick component target versions → precheck → apply.

18. Drift remediation (Configuration Updates)

Configuration Updates are prescribed JSON workflows SDDC Manager runs against a workload domain to (re)align its configuration to the current BOM. Two categories:

  • FEATURE — adds a prescribed capability (e.g. DvpgConfigurationDrift in VCF 5.1 creates the VM_MANAGEMENT DVPG and migrates management VMs for traffic separation).
  • FIX — re-aligns an existing state (e.g. vSAN HA isolation-address drift, compute-manager registration drift).

Examples: CloudAdminRoleConfigDrift (VCF 5.0), DvpgConfigurationDrift (VCF 5.1), RegisterSDDCmanagerAsVCExtensionConfigDrift (VCF 5.2). Apply through SDDC Manager → Repository → Configuration Updates tab.
Reference documentation: VCF 5.2 Lifecycle Management Guide · VCF 5.2 Release Notes & Interop.

Version Comparison

VCF 5.2

LCM via SDDC Manager with online/offline depot bundles

VCF 9.0

Lifecycle managed through VCF Operations (Fleet Management > Lifecycle) across the fleet, with SDDC Manager executing per instance

Key Takeaways

  • LCM downloads bundles from VMware Depot (online) or offline depot, stages, runs prechecks, then upgrades
  • Upgrade sequence: SDDC Manager (VCF bundle) → Configuration Updates → Aria Suite Lifecycle / Aria products → NSX → vCenter → ESXi clusters → vSAN on-disk format; management domain first, then each VI workload domain
  • Async patches allow out-of-cycle security fixes without full BOM upgrade
  • Skip-level upgrades ARE supported: sequential or skip-level to VCF 5.2.x from VCF 4.5 or later (below 4.5, reach 4.5 first); within 5.x, 5.2.1/5.2.2/5.2.3 are reachable skip-level

VCF 5.2 Deep Dive: VCF 5.2 → 9.0 Migration Guide#

VCF 5.2 → 9.0 Migration Guide VCF 5.2 → 9.0

VCF 9.0 is a major re-architecture, not a maintenance release. It re-scopes VCF from a per-instance SDDC into a fleet-wide private cloud, retires the SDDC Manager UI as the fleet control plane, renames the Aria suite, makes vSAN ESA the default, replaces Cloud Builder with VCF Installer, and shifts licensing from 25-char keys to subscription license files. Understanding these shifts is mandatory for any architect designing a brownfield VCF 5.2 environment with a forward-looking migration path.

1. Architectural shifts at a glance

AreaVCF 5.2VCF 9.0
Top-level constructSDDC / VCF instance managed by SDDC ManagerVCF Private Cloud → VCF Fleet → one or more VCF Instances (plus standalone vCenters)
Fleet control planeSDDC Manager UI (per instance)VCF Operations Console — new fleet-level UI in VCF Operations
Bring-up toolingCloud Builder appliance (disposable)VCF Installer — replaces Cloud Builder
ESXi product nameESXiESX (the "i" is dropped)
Aria OperationsVMware Aria OperationsVCF Operations (adds fleet management appliance + collector groups)
Aria AutomationVMware Aria AutomationVCF Automation
Aria Operations for LogsAria Operations for Logs (Log Insight)VCF Operations for Logs (Day-2 install; native logging in VCF Ops 9.0 as alternative)
Aria Operations for NetworksAria Operations for Networks (vRNI)VCF Operations for Networks (Day-2 install)
Remote clustersRemote clusters (min bandwidth 10 Mbps, max 100 ms)VCF Edge (min 10 sites, 8 CPU cores/host, max 256 cores/site)
TanzuTanzu Kubernetes Grid (TKG)VKS (vSphere Kubernetes Service) under vSphere Supervisor Platform
IdentityvCenter SSO + optional external IdPVCF Identity Broker brokers VCF Single Sign-On (embedded in vCenter OR 3-node appliance cluster)
License modelPer-component 25-character keysSubscription license files; primary license covers components; capacity pooling
License consoleSDDC Manager UIvcf.broadcom.com Business Services console + VCF Operations
vSAN defaultvSAN OSAvSAN ESA (default); OSA still supported
NSX Manager modeManager + Policy modes both availablePolicy-only mode; Manager mode removed
Workload networkingSegments, Tier-0, Tier-1 via NSX ManagerAdds VPC (Virtual Private Cloud) + NSX Transit Gateway (TGW) constructs usable from vSphere Client
SDDC Manager UIPrimary Day-2 control surfaceDeprecated — workflows moved to VCF Operations + vSphere Client

2. Component renaming cheat sheet

VCF 5.2 nameVCF 9.0 name
ESXiESX
Cloud BuilderVCF Installer
SDDC Manager UI (fleet scope)VCF Operations Console
VMware Aria OperationsVCF Operations
VMware Aria AutomationVCF Automation
VMware Aria Operations for Logs (Log Insight)VCF Operations for Logs
VMware Aria Operations for Networks (vRNI)VCF Operations for Networks
Remote clustersVCF Edge
Tanzu Kubernetes Grid (TKG)VKS (vSphere Kubernetes Service)
SDDC (concept)VCF Instance + VCF Fleet taxonomy
vSphere NamespacesvSphere Namespaces (now under vSphere Supervisor Platform)
vCenter SSO (standalone)VCF Single Sign-On via VCF Identity Broker
vSAN MaxvSAN storage clusters (not a 9.0 change: the VCF 5.2 docs already list "vSAN Storage Clusters (formerly vSAN Max)", p.136)

3. New concepts in VCF 9.0

  • VCF Private Cloud — top-level construct; contains one or more VCF Fleets.
  • VCF Fleet — a set of VCF Instances plus standalone vCenters managed by a single set of fleet-level management components (VCF Operations + VCF Automation).
  • VCF Instance — the unit that used to be called the "SDDC": management domain + zero or more workload domains.
  • VCF Operations Console — new UI/UX that replaces the fleet-scope of SDDC Manager.
  • VCF Operations fleet management appliance — adds infra-management automation workflows to VCF Operations.
  • VCF Operations collector groups / nodes — collect data from vCenter, NSX, vSAN adapters (scale-out data collection).
  • VCF Identity Broker — brokers VCF SSO; embedded in vCenter or 3-node appliance cluster.
  • VCF Single Sign-On models — Fleet-Wide SSO, Cross VCF Instance SSO, Single VCF Instance SSO.
  • VPC (Virtual Private Cloud) + NSX Transit Gateway — tenant-oriented networking constructs now manageable from vSphere Client.
  • VCF Automation Organization types — All Apps Organizations vs. VM Apps Organizations.
  • vSphere Supervisor deployment modes — Single-Zone, Multi-Zone (3 vSphere Zones), Single Host, Easy Supervisor (simplified PoC).
  • vSphere Zones — boundaries mapping to vSphere clusters, tagged as Management and/or Workload zones.
  • Simplified Supervisor Model — single control plane VM, single vNIC, no load balancer.
  • Continuous Availability VCF Operations Model — pair of nodes across two AZs (<10 ms).
  • Native logging in VCF Operations 9.0 — new product-internal logging solution; optional alternative to deploying VCF Operations for Logs.
  • Marketplace plug-in — for downloading/installing management packs.
  • Custom Management Pack Builder — design/test/install custom packs via JSON/XML REST APIs.
  • Diagnostic Findings — consolidated known issues + VMSA-based security exposures + best practices.
  • Log Assist — uploads support bundles directly to Broadcom Support from VCF Operations.
  • Configuration Management with Git repository integration for template versioning.
  • Unified non-disruptive TLS certificate management with auto-renewal for VMCA, MSCA, OpenSSL and external CAs.
  • VCF Business Services console (vcf.broadcom.com) for subscription license management, usage analytics, and contract management.

4. Licensing — 5.2 vs 9.0

AspectVCF 5.2VCF 9.0
Delivery25-character license keys per componentSubscription license files; single primary license per product covers components automatically
Management UISDDC Manager → LicensingVCF Business Services (vcf.broadcom.com) + VCF Operations
Registration modesOnline only (local entry in SDDC Manager)Connected and Disconnected; usage report required every 180 days
Advanced featuresPer-component allocationCapacity pooling, license splitting/merging, license sharing across tenants, portability (CSP/hyperscaler)
Provider / hyperscalern/aTFC (commit, 125% max) and non-TFC (100% max) licensing models
vSAN licensePer-host capacityvSAN TiB licensing — 1 TiB per VCF core, 0.25 TiB per vSphere Foundation core
Evaluation mode60 days on all hostsSame general rule, BUT stateless Auto Deploy ESX hosts have NO evaluation period — must be immediately licensed

5. UI consolidation — where each workflow lives

WorkflowVCF 5.2 (SDDC Manager UI)VCF 9.0
Workload domain creationSDDC Manager → InventoryVCF Operations → Inventory → Detailed View
Host commissioningSDDC Manager → Administration → HostsvSphere Client (or legacy SDDC Manager UI as alternative)
Network pool managementSDDC Manager → Administration → Network SettingsvSphere Client
License managementSDDC Manager → LicensingVCF Operations + VCF Business Services
Edge cluster + distributed connectivityNSX ManagerSimplified vCenter workflow (Network Connectivity); Broadcom-recommended defaults
VPC / VPC Subnet CRUDNSX ManagervSphere Client (directly from VM Actions menu → External IP via 1:1 NAT)
Stretched cluster operationsSDDC Manager + APIVCF Operations API Explorer (POST /v1/clusters with symmetric/asymmetric topology + site affinity)

6. Networking changes

  • NSX Manager mode removed: VCF 9.0 is Policy-only. Any Manager-mode constructs from earlier NSX versions must be converted to Policy objects before upgrade (NSX Promote or manual Policy re-creation).
  • VPC and VPC Subnets — new NSX-native tenant networking constructs usable directly from vSphere Client.
  • Distributed Connectivity — a new alternative to Centralized Connectivity that does not require Edge nodes for east-west segments; VLAN-backed transit gateway option.
  • Simplified Edge workflow — max 10 Edge nodes per Edge cluster (min 2) in the vCenter simplified workflow.
  • Edge-node password management — VCF can now auto-manage Edge CLI/Root passwords during Edge cluster creation/import.

7. Storage changes

  • vSAN ESA is default; vSAN OSA remains supported but is no longer the primary recommendation.
  • vSAN storage clusters (formerly vSAN Max; the name is already used in the VCF 5.2 docs, p.136) — storage-only cluster type providing remote datastore to ESA or Compute clusters.
  • New vSAN Compute stretch cluster type — consumer of a remote stretched vSAN datastore; no local witness; symmetric/asymmetric topology with site affinity.
  • Stretched cluster expansion now available via API for ESA, OSA, Compute, and Storage cluster types.
  • Multi-rack L3 vSAN HCI cluster deployment via API (greenfield in 9.0).
  • vVols deprecated — critical bug fixes only in 9.0, future removal announced. Plan exits now.

8. Domain & workload management changes

  • Import Existing vCenter workflow enhanced — NSX Federation Local Manager import in 9.0.1+; DFW auto-enables on DVPGs.
  • vSphere Supervisor can now be activated directly at WLD creation (requires Centralized Connectivity).
  • Configuration Drift sync via VCF Operations reconciles out-of-band changes (formerly SDDC-Manager-Repository-driven).
  • VCF Operations API Explorer (Developer Center → APIs & SDKs) now hosts the SDDC Manager API and is the primary path for LACP, L3 multi-rack, and stretched cluster operations.

9. Upgrade path from VCF 5.2 to 9.0

  • Target version: 9.0 directly from 5.2.x is supported if the management domain is at 5.2 and all VI WLDs are at 5.2 (or within a supported Mixed-BOM window documented in the 9.0 Release Notes).
  • Review the new licensing model: you must register with the VCF Business Services console (vcf.broadcom.com) and convert per-component keys to subscription licenses.
  • Ensure all NSX objects are in Policy mode; convert any remaining Manager-mode objects before upgrade.
  • Evaluate vVols usage and plan an exit (deprecated).
  • Budget for VCF Installer, new VCF Operations / Automation footprints, and Identity Broker cluster.
  • Validate hardware for vSAN ESA default (NVMe TLC, 25-GbE, 512 GB RAM per host).
  • Upgrade sequence (high level, VCF 9.0 'Upgrading a VCF Instance with version 5.x to version 9.0.x'): management planes first — deploy the VCF Operations fleet management appliance (replaces Aria Suite Lifecycle, which has no upgrade path to 9) → upgrade Aria Operations to VCF Operations → Aria Automation to VCF Automation → deploy VCF Identity Broker (new) → Operations for networks, Operations for logs (new deployment) → then, per instance, SDDC Manager (to 9.0.1 or later before the rest) → HCX if used → NSX → vCenter → ESX → vSAN on-disk format; management domain first, workload domains before or after as long as they stay compatible → move Day-2 workflows from the SDDC Manager UI to the VCF Operations console.
  • Post-upgrade: re-test every Day-2 workflow in its new location (host commissioning in vSphere Client; license mgmt in VCF Ops/Business Services; VPC via vSphere Client).

10. Breaking changes & removed features

  • SDDC Manager UI is deprecated as the fleet control plane; scripts and runbooks that depend on its workflow endpoints must be ported.
  • NSX Manager mode is removed — Policy mode only.
  • vVols is deprecated (critical bug-fix only; future removal announced).
  • Per-component 25-char license keys retire in favour of subscription license files.
  • "SDDC" as a management construct is replaced by the VCF Instance + VCF Fleet taxonomy.
  • "ESXi" rebrands to "ESX" in all product names and CLI paths where applicable.
  • "Cloud Builder" is replaced by "VCF Installer" — retain existing Cloud Builder OVAs only for rebuild of 5.2 instances.
  • Remote Clusters are rebranded as VCF Edge with new minimums — some 5.2 remote-cluster designs must be re-validated against 9.0 Edge sizing.
  • Tanzu Kubernetes Grid (TKG) is now VKS under vSphere Supervisor Platform — plan Kubernetes namespace continuity carefully.
  • Stateless Auto Deploy ESX hosts have no evaluation period in 9.0 — must be licensed immediately.

11. Migration design guardrails (what to tell customers now running 5.2)

  • Every new VCF 5.2 deployment should assume a 9.0 migration within 24 months — stage the design for it: plan DNS/IP for Identity Broker cluster, plan hardware refresh to vSAN ESA NVMe, avoid new vVols deployments, standardise on NSX Policy-mode workflows.
  • Design Aria deployments with name-agnostic integrations (avoid hard-coding "Aria Operations" endpoints in monitoring scripts) — renaming to VCF Operations will break them.
  • Audit license entitlement — ensure Broadcom Support account can sign into vcf.broadcom.com.
  • Define a documented "day-2 handoff map" for every operational runbook so the team knows which workflows are in SDDC Manager UI today vs. where they will live post-upgrade (vSphere Client / VCF Ops Console / VCF Business Services).
  • If running NSX Federation, review the 9.0 Federation Local Manager import changes (9.0.1+).
  • If running vSphere with Tanzu, plan the TKG → VKS transition using the documented Supervisor upgrade model.

Reference documentation: VCF 9.0 Documentation Portal · VCF 9.0 Deployment & Upgrade Guide · VCF Business Services console.

Version Comparison

VCF 5.2

Source version — must be fully patched before upgrade to 9.0

VCF 9.0

Target version — VCF Installer replaces Cloud Builder; SDDC Manager remains per VCF Instance, while fleet-level workflows move to VCF Operations and the vSphere Client

Key Takeaways

  • VCF 9.0 upgrades are supported sequentially or skip-level from any VCF 5.0+ release; 5.2 is not a mandatory stepping stone (and VCF 6/7/8 never existed). Below 5.0, first reach 5.0+.
  • Pre-upgrade checklist: VUM baselines cleared, snapshots removed, vSAN health green, NSX backup taken
  • HCX is the recommended tool for workload migration between VCF instances
  • Brownfield adoption: convert existing vSphere to VCF using Import Workload Domain workflow

VCF 5.2 Deep Dive: VCF 5.2 Design Patterns & Blueprints#

VCF 5.2 Design Patterns & Blueprints VCF 5.2

The VCF 5.2 Design Guide organises every architectural decision into Requirements (REQD — mandatory; deviations not permitted) and Recommendations (RCMD — best practice; deviations permitted with justification). Each decision is tracked with an ID like VCF-<AREA>-REQD-<TYPE>-<NNN> (for example VCF-NET-REQD-CFG-001). This section enumerates the design blueprints, the key decision catalogues, and the design patterns for multi-rack and dedicated Edge deployments.

1. Decision ID taxonomy

PrefixArea
VCF-ARCH-*Architecture (standard vs consolidated)
VCF-WLD-*Workload domain
VCF-EXT-*External services (DNS, NTP, AD, certificate authorities, SFTP)
VCF-NET-*, VCF-NET-L3MR-*, VCF-NET-DES-*Physical network (leaf-spine, multi-rack)
VCF-VSAN-*, VCF-VSAN-WTN-*, VCF-VSAN-L3MR-*, VCF-VSAN-ESA-L3MR-*, VCF-VSAN-MAX-*vSAN (generic, witness, multi-rack, ESA multi-rack, Max)
VCF-CLS-*, VCF-CLS-L3MR-*vSphere cluster
VCF-ESX-*ESXi host
VCF-VCS-*vCenter Server
VCF-VDS-*, VCF-VDS-L3MR-*vSphere Distributed Switch
VCF-NSX-LM-*NSX Local Manager
VCF-NSX-GM-*NSX Global Manager (Federation)
VCF-NSX-EDGE-*, VCF-NSX-MR-EDGE-*NSX Edge (std, multi-rack)
VCF-NSX-BGP-*, VCF-NSX-MRE-BGP-*BGP routing
VCF-NSX-OVERLAY-*, VCF-NSX-L3MR-OVERLAY-*Overlay (Geneve)
VCF-NSX-AVN-*Application Virtual Network
VCF-NSX-LB-*Load balancing (NSX)
VCF-SDDCMGR-*SDDC Manager
VCF-VASL-*VMware Aria Suite Lifecycle
VCF-WSA-*Workspace ONE Access
VCF-LCM-*Lifecycle management
VCF-ACTMGT-*, VCF-SDDC-RCMD-SEC-*Information security (access & certificate management)

2. Core network-design decisions (leaf-spine)

  • VCF-NET-REQD-CFG-001: Do not use EtherChannel (LAG, LACP, or vPC) for ESXi host uplinks.
  • VCF-NET-REQD-CFG-002: Use VLANs to separate physical network functions.
  • VCF-NET-REQD-CFG-003: Configure VLANs as members of an 802.1Q trunk.
  • VCF-NET-REQD-CFG-004: Set MTU to at least 1,700 bytes on physical ports, vDS, vDS port groups, and N-VDS switches for Overlay (Geneve), vSAN and vMotion. Geneve absolute minimum is 1,600; 1,700 provides growth; 9,000 recommended jumbo frames.
  • VCF-NET-L3MR-REQD-CFG-001: For multi-rack compute VI workload-domain clusters, provide separate VLANs per rack for host management, vSAN, vMotion and host overlay.
  • VCF-NET-L3MR-REQD-CFG-002: Subnets per rack must be routable and reachable between leaf switches.
  • VCF-NET-REQD-CFG-005 (Federation): Set RTEP MTU to at least 1,500 (1,700 preferred, 9,000 recommended) between instances.
  • VCF-NET-REQD-CFG-006 (Federation): Inter-instance latency < 500 ms.
  • VCF-NET-REQD-CFG-007 (Federation): Provide routed connection between NSX Manager clusters; unique routable IPs per fault domain.
  • Host-to-ToR uplink speed: recommended 25-GbE or higher; 10-GbE minimum; dedicated Edge cluster recommends 100-GbE per ToR.

3. vSAN design — key decisions

  • VCF-VSAN-REQD-CFG-001: Provide sufficient raw capacity for the workload domain's initial need.
  • VCF-VSAN-REQD-CFG-002: Provide the required minimum number of hosts per cluster type.
  • VCF-VSAN-REQD-CFG-003 (ESA): Verify all hardware on vSAN HCL.
  • VCF-VSAN-MAX-REQD-CFG-001: At least four nodes for the initial vSAN Max cluster.
  • VCF-VSAN-REQD-CFG-004 (Stretched): Add Site disaster tolerance = Site mirroring – stretched cluster to the default vSAN storage policy.
  • VCF-VSAN-REQD-CFG-005 (Stretched): Two fault domains (one per AZ); assign each host to its AZ fault domain.
  • VCF-VSAN-REQD-CFG-006 (Stretched): Create an individual vSAN storage policy per stretched cluster.
  • VCF-VSAN-WTN-REQD-CFG-001..006: Deploy witness appliance in a third location; size to required cluster capacity; connect its first VMkernel to the witness-site management network; static IP; DNS forward/reverse; internal NTP sync.
  • VCF-VSAN-L3MR-REQD-CFG-001: Configure vSAN fault domains per rack in L3 multi-rack clusters.
  • VCF-VSAN-ESA-L3MR-REQD-CFG-001: Minimum 4 racks for L3 multi-rack ESA clusters.

4. vSphere (ESXi + vCenter) decisions

  • VCF-ESX-REQD-CFG-001..002: Install at least the minimum number of ESXi hosts; verify each host matches the required CPU/memory/storage spec.
  • VCF-ESX-REQD-SEC-001: Regenerate each ESXi host's certificate after assigning its FQDN.
  • VCF-ESX-RCMD-CFG-001: Use vSAN ReadyNodes for every management-domain host.
  • VCF-ESX-RCMD-CFG-002: Homogeneous hardware across the default management cluster.
  • VCF-ESX-RCMD-CFG-003: Size CPU by physical cores only — do not count hyperthreading.
  • VCF-ESX-RCMD-CFG-004: Boot device ≥ 128 GB.
  • VCF-ESX-RCMD-NET-001..002: Separate host management VLAN from VM management VLAN.
  • VCF-VCS-REQD-CFG-001: Dedicated vCenter appliance for the management domain of each VCF instance.
  • VCF-VCS-REQD-SSO-STD-001: Join all vCenter instances within the VCF instance to a single SSO domain (max 15).
  • VCF-VCS-REQD-SSO-STD-002: Create a ring topology between vCenter instances (ELM).
  • VCF-VCS-REQD-SSO-ISO-001: Isolated WLDs each in their own SSO domain (up to 25 WLDs per instance).
  • VCF-VCS-RCMD-CFG-001..005: Default Small for mgmt domain, Medium for VI; protect with vSphere HA (restart priority = high); add appliance to first-AZ VM group for stretched clusters.
  • HA-only policy: vCenter HA and vSphere FT are NOT supported for VCF-managed vCenters — only vSphere HA.

5. NSX decisions

  • VCF-NSX-LM-REQD-CFG-001..002: NSX Manager cluster on VM management network; three nodes in the default mgmt cluster.
  • VCF-NSX-LM-RCMD-CFG-001..006: Appropriately sized nodes, VIP on shared L2, DRS anti-affinity, HA high restart priority; for stretched, VM group for first AZ.
  • VCF-NSX-EDGE-REQD-CFG-001..004: Edge management on VM management network; two pNICs (vmnic0, vmnic1) with fp-eth0/1 pinned (failover); dedicated edge overlay VLAN distinct from host overlay; uplink profile with three teaming policies (default = load balance source both active, named = failover uplink1 only, named = failover uplink2 only).
  • VCF-NSX-MR-EDGE-REQD-ENV-001 / CFG-001: Place ≥1 Edge VM per Edge cluster onto each vSphere cluster in a separate rack; connect each Edge management interface per rack to the VM management network.
  • VCF-NSX-OVERLAY-REQD-CFG-001..005: All ESXi hosts as transport nodes using TNPs; MTU ≥ 1,600 for Geneve; single overlay TZ per NSX instance.
  • VCF-NSX-AVN-REQD-CFG-001..005: Create one cross-instance NSX segment for mobile Aria components; local-instance segments per VCF instance; in Federation extend the cross-instance segment and migrate local-instance segments to local-instance Tier-1 gateways.
  • VCF-NSX-AVN-RCMD-CFG-001: Use overlay-backed AVNs with eBGP between DC fabric and Edge nodes.
  • VCF-NSX-LB-REQD-CFG-001..007: Deploy a standalone Tier-1 gateway for load balancing AVNs; connect to the cross-instance segment; in Federation deploy cold-standby in second instance and plan manual LB-rule sync.
  • VCF-NSX-BGP-REQD-CFG-001..012: ECMP between Tier-0 and L3 devices via two VLANs; named teaming policies; VLAN TZ for edge uplink; Tier-1 in active-standby; stretched ECMP requires IP prefix list + route-map out with AS-path prepend (local AS twice) + route-map in for default route with lower local-preference.
  • Required BGP timers — keep-alive 4 s, hold-down ≤ 12 s.

6. Routing & operating models

OptionNotes
Static routingManual; not supported with vSAN stretched clusters.
OSPFNot supported with vSAN stretched clusters or NSX Federation; cannot combine with BGP on same Tier-0.
BGP (recommended)Supported for all VCF topologies; fully automated via Edge workflows.
Service Router modelUse / constraints
Active-Active (ECMP)Bandwidth-independent; failover ≈ 2 s (VM) / sub-second (bare metal); up to 8 Edge nodes; N+7 availability; no stateful services (no SNAT/DNAT).
Active-StandbyBandwidth-independent; ≈ 2 s / sub-second failover; single active node; supports stateful services (NAT); N+1 availability.

7. SDDC Manager, Aria Suite Lifecycle, Workspace ONE Access

  • VCF-SDDCMGR-REQD-CFG-001..003: Deploy SDDC Manager in the first AZ of the management domain, default config, on VM management network.
  • VCF-SDDCMGR-RCMD-CFG-001..004: Internet or authenticated proxy for depot; VMware Customer Connect / Broadcom Support account with VCF entitlement; external CA for certificates.
  • VCF-VASL-REQD-CFG-001..002: Deploy Aria Suite Lifecycle per VCF instance in the management domain via SDDC Manager.
  • Global Environment — contains Workspace ONE Access (required before deploying Aria Automation).
  • VCF Mode — infrastructure inventory retrieved from SDDC Manager, deployments synced back (limited to one instance of each Aria product).
  • Standalone Mode — manually-entered infra, multiple product instances allowed.
  • Global Environment → VCF Mode, Cross-instance Logical DC, Workspace ONE Access.
  • Cross-instance → Aria Operations analytics/collector + Aria Automation cluster.
  • Each instance → Aria Operations for Logs cluster per VCF instance.
  • Workspace ONE Access clustered LB config: monitor URL /SAAS/API/1.0/REST/system/health/heartbeat, HTTP 200 OK; LEAST_CONNECTION algorithm; HTTP 1.1; SNAT Auto Map; JSESSIONID cookie persistence (rewrite mode); L7 HTTP VS on port 443; application profile timeout 3,600 s with X-Forwarded-For insert.
  • Workspace ONE Access integrations: supported with NSX; not supported directly with vCenter or SDDC Manager (they use vCenter SSO).

8. Information Security decisions — access & accounts

ComponentAccess methods
SDDC ManagerUI, API, SSH (active by default; root login not permitted)
NSX Local ManagerUI, API, SSH (deactivated by default)
NSX EdgesAPI, SSH (deactivated by default)
NSX Global ManagerUI, API, SSH (per deployment setting)
vCenter ServerUI, API, SSH (active by default), VAMI (:5480)
ESXiDCUI, ESXi Shell, SSH (Shell + SSH deactivated by default), VMware Host Client
Aria Suite LifecycleUI, API, SSH (active by default)
Workspace ONE AccessUI, API, SSH (active by default)
AccountManagement methodDefault expiry
admin@local (SDDC Manager)Manual via APINever (break-glass)
vcf (SDDC Manager)Manual via OS365 days
root (SDDC Manager)Manual via OS90 days
Backup passphraseRotate/update/remediate/schedule via UI/API365 days
administrator@vsphere.localRotate/update/remediate/schedule via SDDC Manager90 days
NSX Local Manager admin/root/auditRotate/update/remediate/schedule via SDDC Manager90 days
NSX Edges admin/root/auditRotate/update/remediate/schedule via SDDC Manager90 days
NSX Global Manager admin/root/auditManual via Global Manager UI/API90 days
vCenter rootRotate/update/remediate/schedule90 days
administrator@isolatedsso.localRotate via SDDC Manager90 days
vCenter service accounts (svc-sddc-manager, svc-nsx-manager, svc-vrslcm)System-managed; auto-rotated every 30 daysNone
ESXi rootRotate/update/remediate/schedule via SDDC Manager99,999 (never)
ESXi svc-vcf-esxiRotate/update/remediate/schedule90 days

9. Information Security decisions — certificates

ComponentDefault signing CALCM owner
SDDC ManagerManagement-domain VMCASDDC Manager or SDDC Manager vSphere plug-in
NSX Local ManagerManagement-domain VMCASDDC Manager or Plug-in
NSX Edgesn/a (no per-Edge certificate)—
NSX Global ManagerSelf-signedManual
vCenter ServerLocal WLD VMCASDDC Manager
ESXiLocal WLD VMCAManual (CA-signed via API with Trusted Root cert at deploy)
Aria Suite LifecycleManagement-domain VMCASDDC Manager or Plug-in
  • VCF-SDDC-RCMD-SEC-001: Replace VMCA-signed certs on all management appliances with internal-CA-signed certs.
  • VCF-SDDC-RCMD-SEC-002: Use SHA-2 or higher.
  • VCF-SDDC-RCMD-SEC-003: Perform SSL cert LCM for all mgmt appliances via SDDC Manager or Plug-in.

10. Reference topology blueprints (Rainpole)

BlueprintArchitectureTopologyStorageRouting
Blueprint 1 — Single Instance / Single AZStandard1 instance, 1 AZvSANBGP (Leaf-Spine)
Blueprint 2 — Consolidated / Single AZConsolidated1 instance, 1 AZvSANBGP (Leaf-Spine)
Blueprint 3 — Single Instance / Multi-AZStandard + Stretched1 instance, up to 2 AZsvSAN OSA or ESA (ESA stretch from 5.2 on ReadyNodes, 5.2.1.1 on VxRail)BGP with stretched ECMP rules
Blueprint 4 — Multi-Instance / Single AZ eachStandard + Federation≥2 instances, 1 AZ eachvSANBGP + NSX Federation
Blueprint 5 — Multi-Instance / Multi-AZ eachStandard + Stretched + Federation≥2 instances, up to 2 AZs eachvSAN OSABGP + NSX Federation + stretched ECMP

All blueprints use the same default design-elements catalogue (External Services, Leaf-Spine, Management Domain, Aria Suite Lifecycle, Workspace ONE Access, LCM, Account + Cert Management). Blueprints 3 and 5 add the Stretched Clusters addendum. Blueprints 4 and 5 add the NSX Federation addendum. Each blueprint is fully parameterised in the Rainpole reference deployment.

11. Cluster & Edge design patterns

Design Pattern — Multi-Rack Compute VI Workload Domain Cluster

Deploy a compute cluster spanning multiple racks with vSAN storage and a Layer-3 network fabric, providing rack-level resiliency. Architecture: Standard; Workload domain: VI; Cluster-to-rack: spans multiple racks; Physical network: Leaf-Spine. Applies the L3-multi-rack variants of Physical Network, vSAN, vSphere Cluster, vSphere Networking, and Overlay decision sets.

Design Pattern — Dedicated Edge Scale and Performance

Deploy an NSX Edge cluster on its own dedicated vSphere cluster for maximum performance with a consistent bandwidth budget to north-south traffic. Architecture: Standard; Workload domain: VI; Topology: Single Instance Single AZ (can combine with multi-rack Edge for Multi-Instance Single AZ). Applies the Leaf-Spine Dedicated-Edge and vSphere Networking Dedicated-Edge decision sets.

Design Pattern — Multi-Rack Edge Availability

Deploy an NSX Edge cluster with Edge VMs on two dedicated vSphere clusters in two independent racks for rack-level resiliency. Architecture: Standard; Workload domain: VI; Topology: Single Instance Single AZ. Applies the multi-rack Edge Node and BGP Routing decision sets (VCF-NSX-MR-EDGE-*, VCF-NSX-MRE-BGP-*).

12. Authoritative design-blueprint study notes (from VCF 5.2 documentation)

VCF 5.2 Design Blueprints, Topologies, and Patterns VCF 5.2

Four supported deployment topologies
  • Single Instance - Single Availability Zone: one VCF instance, one AZ; baseline for SMB and tier-2 workloads.
  • Single Instance - Multiple Availability Zones: stretched management and (optionally) VI clusters across two AZs within a metro.
  • Multiple Instances - Single AZ each: two or more independent VCF instances (DC+DC). Usually paired with NSX Federation for unified policy.
  • Multiple Instances - Multiple AZ: maximum resiliency; each instance internally stretched, and all instances federated.
Reference design blueprints

The VCF 5.2 documentation defines five topology design blueprints (the Blueprint 1–5 table in §10; VCF 5.2 docs p.259–277) and three worked examples for the fictitious organisation Rainpole ("Design Blueprint One/Two/Three: Rainpole", p.278–285). Cite those pages; a search of the VCF 5.2 documentation for "Rainpole Core/Metro/Federation/Edge/Secure" did not surface such a set.

Architecture models
  • Standard: separate management vs VI WLDs. Baseline for VCDX-level design.
  • Consolidated: management and initial workloads share the management cluster. Constrained by 2:1 CPU ratio; acceptable for small environments only; split into standard as scale grows.
Cluster design patterns
  • Default management cluster: vSAN (greenfield) or NFS v3 / VMFS-FC / VMFS-FCoE (converted via Import Tool in 5.2.1+). Min 4 hosts at bring-up (3 only for a cluster converted with Import Tool 5.2.1.x).
  • Additional management cluster: for Aria Suite, Avi Controllers, or migration staging. Principal storage flexible.
  • VI workload domain cluster: tenant-facing. Principal vSAN / NFS v3 / VMFS-FC / vVols.
  • Stretched cluster: OSA or ESA on vSAN ReadyNodes from VCF 5.2 (on VCF on Dell VxRail, ESA from 5.2.1.1); 8-host minimum for the management default cluster in multi-AZ.
  • vSAN Max cluster: ESA-only storage cluster, 4–24 hosts, 104 compute-only hosts via HCI Mesh; not for management default cluster.
  • Remote cluster: 2–16 hosts (minimum 2 with external storage), maximum 100 ms latency and minimum 10 Mbps to the central site (VCF 5.2 docs p.166).
  • Dedicated Edge cluster: 100-GbE host-to-ToR, separate from compute; Large Edge VMs for production L7 LB; up to 10 Edge nodes per cluster.
vDS profile options (bring-up)
  • Profile 1: one vDS carrying management, vMotion, vSAN and host overlay traffic; two or four pNICs.
  • Profile 2: two vDS, four pNICs — primary vDS for management, vMotion and host overlay; secondary vDS for vSAN.
  • Profile 3: two vDS, four pNICs — primary vDS for management, vMotion and vSAN; secondary vDS for host overlay.
  • Other vDS and pNIC combinations need the VCF API at bring-up (VCF 5.2 docs p.380).
NIOC (Network I/O Control) share values — VCF 5.2 design recommendations
TrafficShare level (value)Recommendation
ManagementNormal (50)VCF-VDS-RCMD-NIO-002 — prioritised above vMotion, below VM and storage traffic
vMotionLow (25)VCF-VDS-RCMD-NIO-003 — vMotion takes longer under contention, which is acceptable
Virtual machine trafficHigh (100)VCF-VDS-RCMD-NIO-004 — VMs are the most important asset
vSANHigh (100)VCF-VDS-RCMD-NIO-005 — storage traffic protected under contention
All other traffic types (NFS, vSphere Replication, Fault Tolerance, iSCSI, NSX overlay as applicable)Low (25)VCF-VDS-RCMD-NIO-006

NIOC is enabled on the management domain vDS (VCF-VDS-RCMD-NIO-001). vSphere share levels are Low = 25, Normal = 50, High = 100; custom values are possible but the recommendations use the levels.

Multi-rack design
  • Dedicated Edge cluster on a separate rack requires host-to-ToR 100 GbE and a routed overlay.
  • Compute VI workload domains span racks using the leaf-spine design; each rack gets its own VLANs and subnets for host management, vSAN, vMotion and host overlay, routed between the leaf switches (VCF-NET-L3MR-REQD-CFG-001/002).
  • Cluster-to-rack mapping must keep vSAN failure domains intact — prefer “one cluster per rack” or define rack-aware fault domains.
Identity provider constraints (VCF 5.2)
  • Only ONE external IdP at a time: ADFS, Okta, or Microsoft Entra ID.
  • Okta and Entra require vSphere 8.0 U2+ and NSX 4.1.2+.
  • AD over LDAP / OpenLDAP is an identity source added to vCenter SSO, not a full external IdP.
  • Workspace ONE Access clustered = 3 nodes behind NSX LB VIP; requires 5 IPs on the cross-instance segment.

13. Sizing reference at a glance (from the Design Guide)

RoleDefault in VCF 5.2
Management-domain vCenter ServerSmall (100 hosts / 1,000 VMs)
VI workload-domain vCenter ServerMedium (400 hosts / 4,000 VMs)
Management-domain NSX ManagerMedium (up to 128 ESXi hosts)
VI workload-domain NSX ManagerLarge (up to 1,024 ESXi hosts)
NSX Edge (default)Medium
SDDC Manager4 vCPU / 16 GB / 908 GB
Cloud Builder4 vCPU / 4 GB / 279 GB
Aria Suite Lifecycle178 GB thin
Workspace ONE Access (per node)100 GB thin
Workspace ONE Access minimum size for Aria AutomationMedium (10,000 users)

14. HA admission control & overcommit (design reminders)

ClusterHA reserved (CPU/RAM)
Mgmt default, single AZ25%
Mgmt default, multi-AZ50%
Additional / VI, single AZ33%
Additional / VI, multi-AZ50%
  • Management domain CPU overcommit: vCPU:pCPU ≤ 2:1.
  • VI workload domain CPU overcommit: vCPU:pCPU ≤ 8:1.
  • vSAN free-space floor: 30%.
  • Anti-affinity for 3-node management VM clusters requires at least 4 physical hosts underneath.

Reference documentation: VCF 5.2 Design Guide — Design Elements Summary · NSX 4.2 Documentation · vSAN 8.0 Documentation.

Key Takeaways

  • Consolidated architecture: management and customer workloads share the management domain's default cluster, separated by resource pools (bring-up minimum 4 hosts plus capacity for the workloads); suited to small environments and proofs of concept, with the standard architecture recommended for production
  • Standard architecture: separate management and workload domains (recommended for production)
  • Multi-AZ design: stretch clusters across availability zones with vSAN stretched cluster
  • Network design: one vDS (bring-up Profile 1) or two vDS (Profiles 2 and 3), chosen at bring-up; VLAN-backed or overlay (NSX) segments

Labs in This Section

References

Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.