VCF Version Comparison: Architecture Differences Across Eras
Objectives
- Compare management plane architecture across VCF 3.x, 5.x, and 9.0; identify key component migrations and integration points
- Document networking architecture evolution from NSX-V (VCF 3.x) to NSX-T 3.x (VCF 4.x) to NSX 4.x (VCF 5.x) to NSX 9.0 (VCF 9.0); analyze API and routing model differences
- Create a cost comparison table across the perpetual per-CPU (VCF 3.x/4.x), per-core subscription key (VCF 5.x) and per-core subscription license file (VCF 9.0) models, using pricing you obtain and cite yourself; identify cost breakpoints
Prerequisites
Access to VCF release documentation (Planning & Preparation guides for 3.x, 5.x, 9.0), networking guides for NSX-V, NSX-T 3.x, NSX 4.x, NSX 9.0, and licensing documentation. No live lab environment required for this task.
Prior labs: holodeck-01 (recommended for context on VCF 9.0 architecture)
Required skills:
- VCF architecture fundamentals (SDDC Manager, vCenter, NSX, vSAN)
- Component versioning and compatibility matrices
- Cost analysis and TCO modeling
- Networking architecture (Layer 2/3, routing models, API paradigms)
Lab Environment
No live lab required. Use VCF documentation, release notes, and reference architectures. A spreadsheet tool (Excel, Google Sheets) and document editor are sufficient.
Resources needed
- VMware Cloud Foundation Planning & Preparation Guide (v3.x, v5.x, v9.0)
- NSX-V, NSX-T 3.x, NSX 4.x and NSX 9.0 reference documentation
- VCF Licensing & Support Guide
- Spreadsheet application for cost modeling
Tasks
Task 1 Compare Management Plane Architecture (3.x → 5.x → 9.0)
manageabilityVCDX panelists probe architectural decisions and trade-offs. Understanding why SDDC Manager shifted from primary management plane (3.x) to orchestrator role (5.x) to part of unified VCF Ops (9.0) demonstrates mastery of enterprise platform evolution. You'll need to explain component responsibilities, API patterns, and operational overhead across generations.
Document VCF 3.x management plane components: SDDC Manager (monolithic), vCenter Server, NSX-V Manager, vRealize Suite integrations. Create a table: [Component | Role | API Type | Integrated? | Single Point of Failure?]
Document VCF 5.x management plane: SDDC Manager (still primary), vCenter Server, NSX-T (unified network platform), Aria Automation and Aria Operations (integrated lifecycle via Aria Suite Lifecycle), Cloud Builder still performs bring-up (deprecated in 5.2, replaced by the VCF Installer in 9.0). Update the table with 5.x components.
Document VCF 9.0 management plane: Shift to 'VCF Ops' unified platform, SDDC Manager remains but with reduced scope, vCenter as managed component, NSX 9.0 (Policy-only management, VPCs, transit gateways), VCF Operations (the former Aria Operations) as the console for observability, lifecycle, certificates and licensing. Create row for VCF 9.0.
Document component mapping: For each generation, map how a given operational task (e.g., 'add new ESXi host to cluster') flows through the management plane. Show the API calls, component interactions, and failure modes.
Analyze operational impact: For each generation, document MTTR (Mean Time To Recovery) for a failed component. Example: If SDDC Manager goes down in 3.x, what operations are blocked? In 9.0, with VCF Ops, what's different?
Document API deprecation: Identify APIs that changed or were removed across generations. Example: the NSX Manager API (/api/v1) is no longer supported in NSX 9.0 and is replaced by the Policy API (/policy/api/v1) (VCF 9.0.1 docs p.235); from VCF 9.0 no new APIs are added to some VCF 5.2-era specification files (VCF 9.0.1 docs p.237). Create a changelog.
Synthesis: Write a 300-400 word summary: 'Why did VCF architecture evolve from 3.x to 9.0, and what operational benefits (or trade-offs) came with each shift?' Address manageability, scalability, and resilience.
Validation Gate
Check: All 7 steps completed with accurate architectural documentation and synthesis
Expected: Comprehensive component mapping and architectural evolution document demonstrating understanding of VCF platform maturation
Common Errors
Task 2 Compare Networking Architecture (NSX-V → NSX-T → NSX 4.x → NSX 9.0)
scalabilityNetworking architecture is a cornerstone of VCF. NSX-V (vSphere-centric, DLR/ESG model) → NSX-T 3.x (own management plane independent of vCenter, T0/T1 model with distributed and service routers, Federation introduced) → NSX 4.x in VCF 5.x → NSX 9.0 in VCF 9.0 (Policy-only, VPCs, transit gateways) represents a fundamental shift in how networks are designed, managed, and scaled. This task forces you to articulate why each model evolved and when to use each.
Document NSX-V networking model (VCF 3.x era): Distributed Logical Router (DLR), Edge Service Gateway (ESG), port groups, VLAN limitations. Create a diagram or table showing: [Component | Role | Location | API Type | High Availability Model]
Document the NSX-T 3.x model (VCF 4.x era) that NSX 4.x in VCF 5.x carries forward: Tier-0 Gateway (T0), Tier-1 Gateway (T1), segments, topology-independent design, Federation with Global and Local Managers. Show how NSX-T's management plane (NSX Manager cluster and its own APIs) became independent of vCenter. Update your table.
Document the NSX 9.0 model (VCF 9.0 era): Policy-only management (Manager API and Advanced UI retired), VPCs realised directly on the transport zone, transit gateways, VPC connectivity and service profiles, Federation carried forward. Show which VCF 5.x design patterns change in 9.0.
Create an API comparison table: [Operation | NSX-V API Call | NSX-T Manager API Call | NSX 4.x/9.0 Policy API Call | Breaking Changes?]. Example: 'Create logical router' or 'Add VLAN to port group'.
Compare routing model differences: NSX-V used DLR with kernel routes (dynamic or static). NSX-T/NSX 4.x uses T0 with BGP, OSPF (single area, no BGP-OSPF redistribution) and static routing, ECMP and VRF gateways. NSX 9.0 adds transit gateways for VPC routing. Document routing scenarios: [Scenario | NSX-V Solution | NSX-T/4.x Solution | NSX 9.0 Solution]
Document multi-site capabilities: NSX-V relied on Cross-vCenter NSX (universal objects); NSX-T 3.x introduced Federation (Global Manager pushing policy to Local Managers, stretched T0/T1 and segments; the NSX-T Data Center 3.0 Release Notes introduce the Global Manager and state Federation was not intended for production in 3.0.x), which NSX 4.x and NSX 9.0 carry forward (VCF 9.0.1 also supports importing Federation-member Local Managers). Create a feature matrix: [Feature | NSX-V | NSX-T 3.x / 4.x | NSX 9.0]
Synthesis: Write a 300-400 word summary: 'What architectural problems did NSX-V solve, why did NSX-T emerge, and what does NSX 9.0 change for a VCF design? Which generation would you defend for which customer scenario, and why?' Address multi-tenancy, scale, and operational complexity.
Validation Gate
Check: All 7 steps completed with accurate routing, API, and federation documentation
Expected: Comprehensive networking architecture evolution document demonstrating mastery of NSX platform maturation and multi-site design patterns
Common Errors
Task 3 Compare Licensing Models & Build a Cost Comparison Table
cost-optimizationLicensing is a business driver for architecture decisions. VCF 3.x/4.x were sold as perpetual per-CPU licences with separate support renewals. From late 2023 Broadcom moved VCF (including 5.x) to per-core term subscriptions, applied in VCF 5.2 as a VCF solution license key or component keys in the vSphere Client (VCF 5.2 docs p.384). VCF 9.0 keeps the subscription model but replaces the 25-character keys with subscription license files obtained through VCF Operations and the VCF Business Services console (VCF 9.0.1 docs p.1457). VCDX panelists expect you to understand total cost of ownership and how licensing constraints drive design.
Research VCF 3.x/4.x licensing: perpetual per-CPU (socket) model with separate annual support and subscription (SnS). Record the editions and the per-CPU price from a source you can cite (archived price list, historical quote). Document: [Processor Socket Count | Edition | Cost per CPU | Annual SnS | Source and date]
Research VCF 5.x licensing under Broadcom: per-core term subscription, delivered as a VCF solution license key or component license keys (VCF 5.2 docs p.384). Obtain a quote or cite a published price for your term. Document: [Processor Type | Cores per CPU | Licensed Cores (apply the vendor's per-CPU core minimum) | Cost per Core per Year | Term | Source and date]
Research VCF 9.0 licensing: per-core term subscription with capacity delivered as license files from the VCF Business Services console and applied through VCF Operations; license keys are no longer used (VCF 9.0.1 docs p.1457). Obtain a quote for the terms you are comparing. Document: [Offering | Licensed Capacity (cores, plus any add-on capacity such as vSAN TiB) | Subscription Term | Annual Cost | Included Support | Source and date]
Build scenario: Design a 16-host cluster (assume 2 sockets per host, 20 cores per socket = 40 cores per host, 640 total cores). Calculate total cost in each licensing model. Show: [Model | Year 1 Cost | Year 3 Cost | Year 5 Cost | Total Maintenance/Support]
Identify breakpoints: at what cluster size, cores per socket and term length does per-core subscription (VCF 5.x keys or VCF 9.0 license files) cost more or less than the perpetual per-CPU licence plus annual SnS (VCF 3.x/4.x)? Create a graph or breakpoint table.
Include hidden costs: Support SKUs, vRealize licensing, Broadcom support levels, NSX licensing (if separate in older versions). Document: [Licensing Model | VCF License | Support | NSX License | Aria License | Total Cost]
Synthesis: Write a 300-word executive summary: 'Why did VCF licensing evolve from socket-based to subscription, and what business benefits or risks come with each model for a 16-host cluster?' Address cash flow, forecasting, and long-term value.
Validation Gate
Check: All 7 steps completed with accurate pricing, TCO calculations, and cost-benefit analysis
Expected: Comprehensive licensing evolution document with runnable cost comparison model demonstrating business acumen alongside technical knowledge
Common Errors
Final Validation
You have completed a comprehensive architectural and financial comparison of VCF across three generations (3.x, 5.x, 9.0). You can articulate why each component evolved, identify API and routing model shifts, and model licensing cost-benefit. This positions you as capable of advising on upgrade paths and business cases — a VCDX-level skill.
✓ Management plane component mapping → 3-generation table with SDDC Manager, vCenter, NSX, Aria roles clearly documented; API changes noted
✓ Networking architecture evolution → DLR/ESG → T0/T1 → Federation comparison; API mapping table with 10+ examples; routing model differences explained
✓ Licensing cost analysis → 3-model TCO for 16-host cluster; breakpoint analysis; hidden costs included; business synthesis
✓ Architectural synthesis → Written summaries (300-400 words each) for management plane, networking, and licensing showing critical thinking about trade-offs
Cleanup / Restore
• Save all comparison tables and cost models in a shared folder or wiki for team reference
• Review your work with a senior architect or VCDX-level peer for feedback on accuracy and insight depth
• Prepare to discuss your findings verbally — VCDX panelists will ask follow-up questions on trade-offs and scenarios
Design Reflection (VCDX)
VCDX panelists will probe: 'Walk us through why you chose VCF 9.0 over 5.x for this design, or vice versa. What architectural constraints or business drivers led you to that decision?' Your answer should reference specific components (SDDC Manager role, NSX federation, Aria integration), API impacts, and cost models. They will also ask: 'Your 16-host cluster is licensed per core on subscription. What happens to cost if the customer adds 8 more hosts next year, or moves to CPUs with more cores per socket?' Your response demonstrates maturity when it acknowledges trade-offs (short-term cost vs long-term flexibility) and shows a structured decision framework.
Requirements
- Accurate architectural documentation across VCF 3.x, 5.x, and 9.0 with component mappings and API changes
- Comprehensive NSX-V to NSX-T to NSX 9.0 networking model comparison with routing and federation analysis
- Complete licensing model comparison (perpetual per-CPU for VCF 3.x/4.x, per-core subscription keys for VCF 5.x, per-core subscription license files for VCF 9.0) with pricing you obtain and cite, and TCO
- Cost breakpoint analysis for a 16-host cluster showing when each licensing model becomes advantageous
- Written synthesis demonstrating critical thinking about architectural evolution and business drivers
Constraints
- Pricing information can be outdated or vary by region; licensing discounts (20-40%) are not publicly advertised
- API documentation for older VCF versions (3.x) is deprecated and difficult to access; reference VMware KB articles and community forums
- Some NSX-V features have no direct NSX-T equivalent (e.g., vShield endpoints); migration paths are complex
- Broadcom subscription model is relatively new (2023+) and evolving; verify current terms with sales before finalizing TCO
- Architectural decisions are context-dependent (budget, scale, skill level, cloud strategy); no single 'best' answer exists across all scenarios
Assumptions
- A 16-host cluster is representative of mid-market enterprise VCF deployments; scaling analysis for smaller or larger clusters should follow the same pattern
- Pricing obtained from public sources (Broadcom, VAR quotes) is representative; negotiate realistic discounts (20-40% off list) in real-world deals
- Support tier is included in pricing model (e.g., Critical, standard, or Flex plans); OpEx includes annual support renewal
- VCF 3.x cannot upgrade directly to 9.0: the management domain and all workload domains must first reach VCF 5.0 or later through sequential in-place upgrades, then a sequential or skip-level upgrade to 9.0 is supported (VCF 9.0.1 docs p.1347)
- Licensing compliance is strictly enforced; over-licensing or under-licensing carries financial or operational risk
- Business drivers for licensing choice (CapEx budget, OpEx budget, long-term commitment tolerance) are known and documented
Risks
- Inaccurate pricing data → TCO model is wrong, decision is misinformed — MITIGATION: cite pricing sources, include discount ranges, get VAR quote
- Missing API deprecations or NSX-V features with no NSX-T equivalent → migration design is flawed — MITIGATION: reference official migration guides, test in lab
- Incorrect core-to-socket conversion or licensing calculations → financial model fails — MITIGATION: show assumptions clearly, include validation checks (e.g., 'Validate: 16 hosts × 40 cores = 640 cores')
- Overestimating support/maintenance costs → TCO is inflated, subscription model looks better than it is — MITIGATION: use real Broadcom support SKU pricing, verify maintenance percentages with VAR
- Architectural decision made solely on cost without considering operational benefits (e.g., NSX Federation enables multi-site policy, saves operational overhead) — MITIGATION: include qualitative factors (MTTR, scalability, feature coverage) alongside cost
Self-Assessment Discussion Prompts
- You're presenting a VCF upgrade business case to the CFO. They ask: 'Why should we pay for subscription licensing (VCF 9.0) instead of staying on socket-based (3.x)?' How do you frame the answer?
- NSX Federation (available since the NSX-T 3.x line and carried into NSX 4.x and NSX 9.0) adds a Global Manager, but your team currently runs single-site VCF. At what point does federation add value? What customer scenarios justify the upgrade complexity?
- Your 16-host cluster is at full licensing capacity on per-CPU VCF 3.x. Adding 8 more 2-socket hosts means licensing 16 more sockets (320 cores at the lab's 40 cores/host). How do you compare that growth under per-CPU and per-core subscription models, and how do you present the growth scenario to management?
- The API changes from VCF 3.x to 9.0 are significant. How would you prioritize rewriting legacy automation scripts? What criteria determine which scripts are critical vs. nice-to-have?
- NSX for vSphere is past end of general support and VCF 9.0 no longer ships the NSX Migration Coordinator; you must first migrate to NSX 4.x with that release's Migration Coordinator, then upgrade to VCF 9.0 (VCF 9.0.1 docs p.234). You have an NSX-V-only deployment. How do you sequence the NSX-V to NSX 4.x migration before the VCF 9.0 upgrade, and what downtime do you plan for?
- Compare the operational complexity of managing a 16-host cluster in VCF 3.x (SDDC Manager centric, no Aria) vs VCF 9.0 (VCF Ops, Aria integrated). What's the MTTR difference for a common failure (e.g., vCenter down)?
Extensions
Extend Cost Analysis to Multi-Site Scenario
Expand the 16-host cluster TCO to a 3-site topology (48 hosts total, federated NSX). Calculate licensing costs for NSX Federation, VCF Operations licensing across sites, and support complexity. How does the cost per host change at scale?
harderCreate an API Compatibility Matrix for Legacy Tools
You have PowerShell scripts written for VCF 3.x/4.x against the SDDC Manager REST API (for example with PowerVCF). Document the migration path to the VCF 9.0 APIs (SDDC Manager, VCF Operations and vCenter REST/OpenAPI, VCF PowerCLI). Create a script translator guide (manual refactoring, not auto-conversion). Test in a Holodeck 9.0 lab.
harderAnalyze NSX-V Workload Migration to NSX-T
Design an NSX-V → NSX 4.x migration with the NSX 4.x Migration Coordinator (a prerequisite for VCF 9.0, which no longer ships it; VCF 9.0.1 docs p.234) for a 16-host cluster with 200+ VMs. Document segment mapping, routing reconfiguration, security policy translation, maintenance windows and rollback plan. Include a 48-hour runbook.
harderBuild a Licensing Reconciliation Tool
Write a Python or PowerShell script that audits a live VCF environment (query SDDC Manager for host count, core count, vRealize licenses) and compares actual vs. licensed capacity. Report under/over-licensing and cost impact. This mirrors real-world compliance checks.
harder⚠ Known Pitfalls
References
- VMware Cloud Foundation 9.0 Planning and PreparationTier 1 — Official
Official VCF 9.0 planning documentation (architecture, component roles, version-specific details). Earlier-version (3.x/4.x/5.x) documentation is published separately on techdocs.broadcom.com; locate the version you are comparing. - VCF 9.0 LicensingTier 1 — Official
Subscription license files from the VCF Business Services console replace 25-character license keys in VCF 9.0 (VCF 9.0.1 docs p.1457). Does not publish prices; obtain pricing from Broadcom or your reseller and cite it. - NSX 4.2 Migration Guide (migrating NSX for vSphere to NSX)Tier 1 — Official
NSX-V migration uses the NSX 4.x Migration Coordinator; VCF 9.0 no longer ships it, so migrate to NSX 4.x first, then upgrade to VCF 9.0 (VCF 9.0.1 docs p.234). - Advanced Network Management with NSX — VCF 9.0 documentation (chapter 'Multisite and NSX Federation')Tier 1 — Official
Federation (Global Manager, Local Managers, stretched gateways and segments) as carried into NSX 9.0; see the 'Multisite and NSX Federation' chapter (VCF 9.0.1 docs p.2274). - Broadcom Product Interoperability MatrixTier 1 — Official
Supported upgrade paths and component version interoperability. Read with the VCF 5.2 and 9.0 release notes for supported upgrade sequences (VCF 9.0 upgrades start from VCF 5.0 or later, VCF 9.0.1 docs p.1347). - William Lam — VCF Architecture Deep DivesTier 3 — Background reading
Community-authored technical blogs exploring VCF architecture choices, Aria integration, and multi-site strategies. Pragmatic perspective on real-world deployment.