VMware Cloud Foundation Upgrades — 5.x to 9.0 & Conversion
Objectives
- Identify the three paths to VCF 9.0 (new, vSphere conversion, VCF 5.x upgrade)
- Describe the two-phase vSphere to VCF 9.0 conversion process
- Explain the VCF 5.x upgrade sequence: Phase 1 (Aria → VCF) then Phase 2 (SDDC→NSX→vCenter→ESX)
- List component version requirements for upgrade (Aria Ops 8.14+, Automation 8.18+)
- Identify which VCF 9.0 components are now required vs optional
- Assess infrastructure readiness across 5 dimensions
Prerequisites
Active Holodeck VCF 9.0 lab or access to VCF documentation
Required skills:
- Basic VMware terminology
Tasks
Task 1 Paths to VCF 9.0 Private Cloud
Understand the three upgrade/conversion paths to VCF 9.0
Path 1: New Deployment — fresh VCF 9.0 via VCF Installer. Path 2: Existing vSphere — two phases: (a) in-place upgrade to vSphere 9.0, (b) converge using VCF Installer. Path 3: Existing VCF 5.x — in-place upgrade executed in two phases.
[HOLODECK NOTE] Holodeck environments are typically deployed fresh (Path 1) since they are lab/test environments. Upgrade testing (Path 3: VCF 5.x→9.0) is possible in Holodeck but requires a pre-existing 5.x deployment — this means deploying a 5.x Holodeck first, then performing the upgrade. This is resource-intensive (two full deployments worth of RAM/storage). Conversion (Path 2: vSphere→VCF) can be tested but the nested environment may not surface all real-world compatibility issues.
Phase 1: In-place upgrade of vSphere (vSphere 8.0 → 9.0). Phase 2: VCF Installer converges existing vCenter 9.0 into management domain vCenter. Then use VCF Operations to import existing vSphere as VI workload domain. Finally VCF Operations Fleet Management installs remaining VCF management components.
Phase 1 — Aria components upgrade: (1a) Aria Operations → in-place upgrade to VCF Operations 9.0 using LCM 8.18 Patch 2; (1b) Deploy VCF Operations Collector (new, required); (1c) Deploy VCF Operations Fleet Management (new, required); (1d) Optional: deploy VCF Operations Identity Broker; (2) Import Aria Operations for Logs; (3) Import Aria Automation 8.18+ → upgrade to VCF Automation 9.0; (4) Import Aria Operations for Networks. Phase 2 — VCF stack upgrade (sequential): SDDC Manager → NSX Manager → vCenter → ESX hosts.
Validation Gate
Check: What is the supported upgrade path from VCF 4.5 to VCF 9.0?
Expected: VCF 4.5 → VCF 5.2.x (intermediate upgrade) → VCF 9.0. No direct path from 4.x to 9.0. Each hop requires its own maintenance window, pre-checks, and backups.
Common Errors
Task 2 Upgrade Planning & Prerequisites
Assess infrastructure readiness and plan upgrade execution
Five dimensions: Compatibility (HW/SW with existing systems), Complexity (integration with existing systems), Risk Assessment (impact analysis), Timeframe (upgrades take longer than new deployments), Scalability (existing constraints: site footprint, power, cooling). Architecture comparison: vSphere (vCenter + custom scripts) → VCF 9.0 (unified fleet + built-in automation + scalable multi-instance architecture).
Compute/Storage: valid VCF 9.0 subscription, resource sizing check (VCF 9.0 may need more CPU/memory/storage), HW compatibility verification. Networking: VDS migration requirements, NSX compatibility assessment. VCF Automation: blueprint compatibility check. Assessment tools: feature compatibility assessment (4-page comparison matrix in lecture manual). CRITICAL: All workload domains must be at VCF 5.0 or higher before upgrading to 9.0. If any workload domain is below 5.0, upgrade it to 5.0 first, then proceed with the 9.0 upgrade.
For Phase 1 upgrades: Aria Operations 8.14+ (if managed by LCM) or 8.18+ (if managed by vCenter), Aria Automation 8.18+, Aria Operations for Networks 6.13+. LCM must be patched to 8.18 Patch 2 first. VCF Operations is now REQUIRED (was optional). VCF Operations Fleet Management is now REQUIRED (new). VCF Operations Collector is REQUIRED (new, not deployed before).
Required in 9.0 (was optional): VCF Operations, VCF Operations Fleet Management. New required component: VCF Operations Collector. Optional (unchanged): VCF Automation, VCF Operations for Networks, VCF Operations for Logs. During upgrade: licenses reset to 90-day evaluation mode. Legacy components continue using license keys until fully upgraded.
Validation Gate
Check: What is the component upgrade sequence within the management domain?
Expected: SDDC Manager → vCenter → NSX Manager cluster → ESXi hosts (rolling) → vSAN on-disk format. Management domain completes before any workload domain begins.
Common Errors
Design Reflection (VCDX)
Upgrade and migration strategy is a key VCDX defense topic. Panelists test whether your design accommodates future upgrades and whether you have a rollback plan. The 5.x-to-9.0 upgrade is particularly relevant given the architectural changes.
Requirements
- Plan upgrade path from current VCF version to 9.0
- Ensure management domain resources for mandatory new components
- Document rollback strategy per component
Constraints
- No direct upgrade from VCF 4.x to 9.0
- Management domain must upgrade before workload domains
- VCF 9.0 requires additional compute resources for VCF Operations/Automation
Assumptions
- Current environment is healthy (no degraded vSAN objects, no NSX alarms)
- Maintenance window is sufficient for full upgrade sequence
Risks
- Mid-upgrade failure requiring manual rollback
- Insufficient management domain resources for new VCF 9.0 components
- Compatibility issues with third-party integrations after upgrade
⚠ Known Pitfalls (from Community KB)
References
- VCF 9.0 Upgrade GuideTier 1 — Official
- VCF Conversion GuideTier 1 — Official