Lab: Upgrade ESXi via vLCM and Convert vSphere License to VVF
Objectives
- Upgrade ESXi host to 9.0 using vLCM image-based lifecycle management
- Understand vSphere-to-VVF conversion requirements and pre-checks
- Assign VVF license to upgraded host and verify entitlements
- Differentiate the VVF 9 primary license (VMware vSphere Foundation, cores) from add-on licenses (vSAN TiB capacity) and from pre-9 license keys still used for ESX 8.x hosts
- Handle license expiry: 90-day evaluation, the 90-day post-expiry update window, and the 180-day usage report
Prerequisites
VVF lab with vCenter deployed and at least one ESXi host running a prior version (or simulated via snapshot)
Prior labs: vvf-support-01
Required skills:
- vCenter UI navigation
- SSH to ESXi
- vLCM basics
Lab Environment
Holodeck vSphere Foundation 9.0 instance (New-HoloDeckInstance -VVF). Holodeck deploys VVF at 9.0.0.0 or later only, so it cannot provide an ESX 8.x host: for the upgrade exercise add a nested ESX 8.0 U3 host built outside Holodeck to the cluster, or run Tasks 1-2 as a walkthrough.
Credentials
| System | Username | Password |
|---|---|---|
| vCenter | administrator@vsphere.local | Holodeck documented default (Post Deployment table) |
| Nested ESX hosts | root | Holodeck documented default (Post Deployment table) |
Tasks
Task 1 Pre-Upgrade Compatibility Check and vLCM Image Setup
manageabilityvLCM image-based management is the supported upgrade path for VVF 9.0. Understanding pre-checks prevents upgrade failures — a core support skill.
vCenter UI → Lifecycle Manager → Images. Review existing image definitions. Note current ESXi version on target host.
Create or verify ESX 9.0 image: Click 'New Image' → select ESX 9.0 depot → add vendor add-on (e.g., HPE/Dell) if applicable → add any required firmware add-ons.
Navigate to target host → Configure → Image. Click 'Check Compliance'. Review compliance report for hardware compatibility warnings.
If non-compliant: review Hardware Compatibility List (HCL) for the specific server model. Document which components need driver updates.
Place host in maintenance mode: Right-click host → Maintenance Mode → Enter. For vSAN, select 'Ensure data accessibility' evacuation mode.
Validation Gate
Check: Host is in maintenance mode, vLCM image compliance check completed
Expected: Host shows 'Maintenance Mode' status. Compliance report generated.
Common Errors
Task 2 Remediate Host with vLCM Image (ESXi Upgrade)
manageabilityvLCM remediation is the actual upgrade mechanism. Understanding the workflow, monitoring progress, and troubleshooting failures is essential for support.
With host in maintenance mode → Configure → Image → Click 'Remediate'. Select single-host remediation.
Review pre-remediation checks: firmware compatibility, available disk space (>2GB on boot device), network connectivity. Accept and proceed.
Monitor remediation progress in vCenter Tasks panel. Note the stages: staging → pre-check → install → reboot → post-check.
After remediation completes, verify: Host → Summary → ESXi version should show 9.0.x. Check Configure → Image → Compliance = 'Compliant'.
Exit maintenance mode: Right-click host → Exit Maintenance Mode. Verify VMs are migrated back (DRS) or manually power on.
Validation Gate
Check: ESXi host upgraded to 9.0 and operational
Expected: esxcli system version get returns 9.0.x. Host is out of maintenance mode with VMs running.
Common Errors
Task 3 Assign VVF License and Verify Entitlements
manageabilityVVF 9.0 licensing is subscription-based with one primary license — VMware vSphere Foundation (cores) — plus add-on licenses such as vSAN (TiB); there are no Standard/Advanced/Enterprise VVF tiers (VCF 9.0.1 docs p.1458). Licenses are assigned in VCF Operations to vCenter instances and the components are licensed automatically. Understanding assignment, usage reporting and expiry is critical for Obj 5.4.
In VCF Operations open License Management > Licenses and select the Version 9+ tab (VCF Operations must be registered with the VCF Business Services console, connected or disconnected mode — check under License Management > Registration). Review the licenses present: the primary VMware vSphere Foundation (cores) license and the VMware vSAN (TiB) add-on. Note any component still in evaluation mode — evaluation lasts up to 90 days (VCF 9.0.1 docs p.1463; a 9.0.1 known issue shows 60 days in the ESX/Installer UI).
Add license capacity: in the VCF Business Services console (vcf.broadcom.com) the default license holds the subscribed capacity; in VCF Operations add the license with available capacity. There is no per-component key — one primary license covers vSphere, vSAN and vCenter for vSphere Foundation.
Assign the license: in VCF Operations assign the VMware vSphere Foundation (cores) license to the vCenter instance. The ESX hosts and other components under that vCenter are licensed automatically; then assign the vSAN (TiB) add-on if the cluster uses vSAN.
Verify usage: review the core count (vSphere 9.0 counts a minimum of 16 cores per CPU, p.80) and the vSAN TiB usage against the subscribed capacity, and note the usage-report cadence — a usage report is required at least every 180 days (connected mode sends it automatically; disconnected mode uploads a usage file).
Understand expiry: evaluation lasts up to 90 days; when a license expires (subscription ended, or usage not reported and the license not refreshed within 180 days) you have 90 days to update it, with notifications in VCF Operations and vCenter. After those 90 days ESX hosts disconnect from vCenter, most host management operations are prevented and new workloads cannot be created or started; running workloads are not stopped (p.1458, p.1475). There is no 'License Expired' host state.
Document: compare the VVF 9 primary license (cores), the vSAN add-on (TiB) and version 8 license keys for not-yet-upgraded ESX hosts in a table: what each covers, where it is assigned (VCF Operations vs vCenter Licensing for 8.x keys), and how usage is reported.
Validation Gate
Check: VVF license assigned and entitlements verified
Expected: Host shows VVF license. Core and vSAN TiB usage within the subscribed capacity (there are no VVF tiers).
Common Errors
Final Validation
ESXi host upgraded to 9.0 via vLCM and VVF license assigned with correct entitlements
✓ ESXi version is 9.0.x → esxcli system version get returns ESX 9.0.x
✓ vLCM image compliance is green → Configure → Image shows 'Compliant'
✓ VVF license assigned → vCenter shows the VMware vSphere Foundation (cores) license assigned, hosts licensed, and the vSAN TiB add-on applied
✓ Host operational → VMs running, vSAN healthy, no alarms
Cleanup / Restore
• Revert to pre-upgrade snapshot if needed for subsequent labs
• Leave the VCF Operations license assignment in place; record the next usage-report date
Design Reflection (VCDX)
Upgrade sequencing is a critical design decision. In production, rolling upgrades must consider vSAN fault domains, DRS admission control, and N+1 capacity during maintenance windows.
Requirements
- Upgrade ESXi to 9.0 with zero VM downtime
- Maintain vSAN data availability during upgrade
Constraints
- Holodeck environment has limited hosts — full data migration may not be possible
- Boot device size limits image staging
Assumptions
- Hardware is on VVF 9.0 HCL
- Sufficient cluster capacity for maintenance mode evacuation
Risks
- Boot failure after upgrade requires physical console access
- vSAN rebuild after maintenance mode exit impacts cluster performance
Self-Assessment Discussion Prompts
- Why must you use 'Ensure data accessibility' vs 'Full data migration' for vSAN evacuation in a 3-node cluster?
- What happens to running VMs if a host fails to reboot after vLCM remediation?
- How does VVF subscription licensing differ from legacy perpetual vSphere licensing?
Extensions
Upgrade all 3 hosts in sequence — practice rolling upgrade workflow
Review the 180-day usage-report reminder and the expiry notifications in VCF Operations (do not move system clocks forward — that breaks certificates and vSAN)
Explain why vCenter 9.0 offers images only (baselines removed, p.226) and how a baseline-managed 8.x cluster is converted to images before the upgrade
⚠ Known Pitfalls
References
- vSphere Lifecycle Manager DocumentationTier 1 — Official
- VVF 9.0 Licensing GuideTier 1 — Official
- Broadcom HCLTier 1 — Official