Academy/VCF 9.0 Support (2V0-15.25)/License Management — VCF 9.0 Licensing Model
This lab targets VCF 9.0

License Management — VCF 9.0 Licensing Model

VCF 9.0Beginnersupportadmin⏱ 30 min

VCFFTS9 course content — VCF 9.0 focused

Objectives

  • Explain the evolution from license keys to license files in VCF 9.0
  • Describe per-vCenter licensing (not per-host) and CPU core-based auto-claiming
  • Navigate VCF Business Services (VCFBS) console for connected/disconnected mode
  • Identify which add-ons use the 9.0 license system (vSAN TiB, Private AI Foundation with NVIDIA) and which follow their own licensing
  • Perform license registration, assignment, and usage reporting in VCF Operations
  • Explain subscription expiry behavior (warning → 90-day grace → host disconnect) and the 180-day usage-reporting rule

Prerequisites

Active Holodeck VCF 9.0 lab or access to VCF documentation

Required skills:

  • Basic VMware terminology

Tasks

Task 1 VCF 9.0 Licensing Model

VCF 9.0 keeps the per-core subscription introduced in the 5.x era but changes the mechanism: 25-character license keys are replaced by a license file imported into VCF Operations, licenses are assigned to vCenter instances, and usage must be reported at least every 180 days (VCF 9.0.1 docs p.77). Understanding the mechanism is critical for budgeting and for explaining cost structures to customers.

Understand the new license file model replacing legacy license keys

Step 1
Licensing Evolution: Keys to Files

VCF 5.x: license keys per component, no consumption data required, major-version-specific, managed in Broadcom Support Portal. VCF 9.0: single digitally signed license FILE for all components, consumption data required, version-agnostic, managed in VCF Business Services (VCFBS) console. License file benefits: auto-pooling, splitting/merging doesn't invalidate, secure (forgery prevention).

[HOLODECK NOTE] Holodeck deployments use evaluation licenses (90-day). The VCFBS console registration and license file workflow cannot be fully tested in Holodeck without a valid Broadcom subscription. Connected mode (automatic license sync) requires internet access from the VCF Operations appliance — Holodeck environments are typically air-gapped or NAT'd. Focus study on understanding the workflow conceptually rather than hands-on license management in Holodeck.

Step 2
Per-vCenter Licensing Model

VCF 9.0 = per-vCenter licensing (not per-host). ESX hosts auto-claim licenses from attached vCenter based on CPU core count. Each vCenter instance is assigned one primary license plus optional add-on licenses; the license file itself is imported into VCF Operations (one file carries all licences, p.77), not assigned to a vCenter. One allocation can serve many vCenter instances (if entitlements suffice). New ESX hosts get 90-day evaluation period. vCenter and ESX must be 9.0+ to use license files.

Step 3
VCF Business Services Console

VCFBS = new license management portal. Tenants and users managed with Broadcom credentials. License entitlements distributed across tenants. Connected mode: VCF Operations auto-registers with VCFBS. Disconnected mode: manual download/upload of registration files and license files. Usage info flows to VCFBS for compliance — prevents overallocation.

Step 4
Products Not Yet on VCF 9.0 License Model

Add-ons on the 9.0 license system: VMware vSAN (TiB) and VMware Private AI Foundation with NVIDIA (cores), assigned in VCF Operations after the primary license. Other add-ons (for example vDefend, Avi Load Balancer, VMware Live Recovery) are licensed as described in their own documentation and do not necessarily follow the VCF model.

Validation Gate

Check: Calculate the core license count for: 8 hosts, each with 2× 32-core CPUs

Expected: 8 hosts × 2 sockets × 32 cores = 512 cores to license. This is the base count. Add-ons are licensed separately, each in its own unit: the vSAN add-on in TiB (VCF includes a default vSAN TiB entitlement, p.1458), Private AI Foundation in cores, others per their own documentation (p.1461).

Common Errors

Confusing perpetual license (VCF 5.x) with subscription model (VCF 9.0)
Fix: The move from perpetual per-CPU licences to per-core subscriptions happened during the VCF 5.x era (perpetual end of availability, 2024 — VCF 5.2 release notes p.63); 5.x subscription keys are term licences. VCF 9.0 changes the mechanism, not the metric: license files instead of 25-character keys, assignment to vCenter instances in VCF Operations, and 180-day usage reporting. Existing perpetual licenses remain valid for their version but cannot be used for VCF 9.0. Plan for subscription cost in OpEx, not CapEx.
Not understanding the VCF edition tiers
Fix: VCF 9.0 has tiered editions with different feature sets. Base VCF includes vSphere, vSAN, NSX, VCF Operations, VCF Automation. Add-ons differ: vSAN capacity beyond the per-core entitlement is a TiB add-on and Private AI Foundation with NVIDIA is a per-core add-on, both on the 9.0 license system; vDefend, Live Recovery and Avi follow their own licensing documentation. Map customer requirements to the correct edition to avoid over- or under-licensing.
Miscounting cores for licensing
Fix: VCF per-core licensing counts physical CPU cores, not vCPUs. Hyper-threading does not double the core count. A dual-socket server with 2× 32-core CPUs = 64 licensed cores. Minimum core count per server may apply — check current Broadcom licensing terms.

Task 2 License Management in VCF Operations

License management in VCF 9.0 is handled through VCF Operations and the VCF Business Services console; license keys survive only for 5.x domains during a mixed-BoM upgrade. Understanding how to apply, track, and troubleshoot licensing is an operational skill that impacts compliance and support eligibility.

Manage licenses through VCF Operations console

Step 1
Registration & License Assignment

Workflow: License Management > Registration in VCF Operations. Connected: auto-registration, activation code created. Disconnected: download registration file from VCF Ops → upload to VCFBS → download signed license file → import to VCF Ops. After registration: assign licenses + add-ons (e.g., vSAN) to vCenter instances. ESX hosts auto-licensed when added to vCenter.

Step 2
Usage Reports & Compliance

Connected mode: usage reports generated automatically. Disconnected mode: generate signed gzip usage report → upload to VCFBS to refresh license info. License consumption and capacity visible in VCF Operations console. Entitlement validation: signature, feature set/components/expiration, capacity.

Step 3
Subscription Expiry & Upgrade Licensing

Expiry notification: notifications are displayed before the license expiration (VCF 9.0.1 docs p.1458); p.1458 states no lead time, so record when the first notice appears in your environment. Expiry applies when the subscription ends OR when license usage has not been submitted and the licenses updated within 180 days — in connected mode usage is sent automatically but you must still click Update Licenses (p.77, p.1463); this is the most common 'licenses expired' troubleshooting scenario. Grace period: 90 days after expiry. After 90 days without renewal: ESX hosts disconnected from vCenter, running VMs continue but no new VMs can be powered on, no changes allowed. During upgrade from VCF 5.x: licenses reset to 90-day evaluation mode to enable transition to new model. Precise expiry behavior: (1) ahead of expiry — alerts appear in both VCF Operations and vCenter; emails are sent from the VCF Business Services console. (2) On expiry — 90-day grace period begins; customer remains notified; renewal during grace period causes no disruption. (3) After 90-day grace — VCF expiration invoked: ALL affected ESX hosts are disconnected from their respective vCenter instances; running VMs continue to run but no additional VMs can be powered on; no changes allowed to the VCF instance. (4) On renewal after expiration — hosts automatically reconnect and normal operations resume.

Validation Gate

Check: Where in VCF do you manage and monitor license compliance?

Expected: VCF Operations → License Management (registration, licenses, assignment to vCenter instances, usage), and across VCF Operations instances in the VCF Business Services console (vcf.broadcom.com). SDDC Manager license keys apply only to VCF 5.x domains still on the source BoM during an upgrade.

Common Errors

Running VCF with expired evaluation licenses in production
Fix: VCF 9.0 evaluation mode lasts up to 90 days (60 days applied to VCF 5.2.x; a 9.0 UI display of 60 days is a known cosmetic issue). When it ends, unlicensed ESX hosts disconnect from vCenter and new workloads cannot be started; existing VMs keep running. Replace evaluation licenses with production licenses before expiry to avoid disruption to provisioning operations.
Not tracking license compliance across workload domains
Fix: Each workload domain consumes licenses independently. Adding hosts to a workload domain increases the core count. Use VCF Operations License Management (and the VCF Business Services console across instances) to track usage against entitlement. Over-deployment without sufficient licenses impacts Broadcom support eligibility.

Design Reflection (VCDX)

Licensing is always a VCDX defense topic — panelists ask about cost per VM, TCO comparisons with public cloud, and whether your licensing covers the add-ons your design requires. Know your per-core count and be able to calculate licensing cost on the spot.

Requirements

  • Understand VCF 9.0 per-core subscription licensing model
  • Calculate core counts for licensing
  • Track license compliance across domains

Constraints

  • Per-core licensing — no per-VM or per-socket option in 9.0
  • Add-ons require separate subscriptions in their own unit (vSAN add-on in TiB, Private AI Foundation in cores; others per their own documentation — p.1461)
  • Evaluation mode lasts up to 90 days (VCF 9.0; 60 days applied to VCF 5.2.x)

Assumptions

  • Customer has purchased appropriate VCF edition for their requirements
  • VCF Operations is registered with the VCF Business Services console and licenses are assigned to vCenter instances within the 90-day evaluation period after bring-up (no license keys in 9.0, p.1457)

Risks

  • Under-licensing causing compliance issues and support eligibility impact
  • Budget overrun from add-on licensing not included in initial estimates

⚠ Known Pitfalls

Presenting a VCDX design with vDefend micro-segmentation but not accounting for vDefend add-on licensing cost — panelists will catch this.
Confusing physical cores with logical processors (hyper-threads) when calculating license requirements.

References

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