Lab: Upgrade ESXi via vLCM and Convert vSphere License to VVF

VCF 9.0Intermediatevcp-foundation⏱ 90 min

Covers Obj 5.2 (VVF Upgrade) and Obj 5.4 (License Management). Demonstrates vLCM image-based upgrade path and VVF license assignment.

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 VVF Standard/Advanced/Enterprise license tiers
Handle license expiry scenarios and grace period behavior

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 VVF pod with vCenter and 3 ESXi hosts. One host at ESXi 8.x (simulated via snapshot) for upgrade exercise.

Credentials

System	Username	Password
vCenter	`administrator@vsphere.local`	Holodeck default
ESXi Host	`root`	Holodeck default

Tasks

Task 1 Pre-Upgrade Compatibility Check and vLCM Image Setup

manageability

vLCM image-based management is the supported upgrade path for VVF 9.0. Understanding pre-checks prevents upgrade failures — a core support skill.

Step 1

vCenter UI → Lifecycle Manager → Images. Review existing image definitions. Note current ESXi version on target host.

Image list shows ESXi 8.x baseline and/or 9.0 image.

Step 2

Create or verify ESXi 9.0 image: Click 'New Image' → select ESXi 9.0 depot → add vendor add-on (e.g., HPE/Dell) if applicable → add any required firmware add-ons.

ESXi 9.0 image created with base image + optional vendor add-on.

Step 3

Navigate to target host → Configure → Image. Click 'Check Compliance'. Review compliance report for hardware compatibility warnings.

Compliance check returns either 'Compliant' or lists specific incompatibilities (drivers, firmware).

Step 4

If non-compliant: review Hardware Compatibility List (HCL) for the specific server model. Document which components need driver updates.

Exam tests knowledge of HCL check before upgrade. Always verify CPU, NIC, and storage controller compatibility.

Step 5

Place host in maintenance mode: Right-click host → Maintenance Mode → Enter. For vSAN, select 'Ensure data accessibility' evacuation mode.

Host enters maintenance mode. All VMs migrated via DRS (or manually if DRS disabled).

Validation Gate

Check: Host is in maintenance mode, vLCM image compliance check completed

Expected: Host shows 'Maintenance Mode' status. Compliance report generated.

Common Errors

Compliance check shows 'Incompatible' for NIC driver

Cause: Driver in current image not certified for ESXi 9.0

Fix: Add updated driver component to the vLCM image before remediation.

Host won't enter maintenance mode — vSAN objects inaccessible

Cause: Insufficient capacity on remaining hosts for vSAN data evacuation

Fix: Use 'Ensure data accessibility' instead of 'Full data migration' if cluster has <3 hosts. Check vSAN health for capacity warnings.

Task 2 Remediate Host with vLCM Image (ESXi Upgrade)

manageability

vLCM remediation is the actual upgrade mechanism. Understanding the workflow, monitoring progress, and troubleshooting failures is essential for support.

Step 1

With host in maintenance mode → Configure → Image → Click 'Remediate'. Select single-host remediation.

Remediation wizard starts. Pre-check validation runs automatically.

Step 2

Review pre-remediation checks: firmware compatibility, available disk space (>2GB on boot device), network connectivity. Accept and proceed.

Pre-checks pass. Remediation begins — host reboots into upgrade mode.

Step 3

Monitor remediation progress in vCenter Tasks panel. Note the stages: staging → pre-check → install → reboot → post-check.

Typical upgrade takes 15-30 minutes. If stuck at 'staging' for >10 minutes, check /var/log/esxupdate.log on the host.

Step 4

After remediation completes, verify: Host → Summary → ESXi version should show 9.0.x. Check Configure → Image → Compliance = 'Compliant'.

ESXi version updated to 9.0.x. Image compliance shows green checkmark.

Step 5

Exit maintenance mode: Right-click host → Exit Maintenance Mode. Verify VMs are migrated back (DRS) or manually power on.

Host exits maintenance mode. DRS rebalances VMs across cluster.

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

Remediation fails at 'staging' phase

Cause: Insufficient boot device space or network timeout downloading image

Fix: Check boot device free space (esxcli storage filesystem list). Verify vCenter can reach depot URL. Try staging manually: esxcli software vib install.

Host fails to reboot after upgrade

Cause: Incompatible driver or firmware causing boot failure

Fix: Boot into ESXi recovery mode. Check /var/log/boot.log. May need to roll back via Alt+F1 console or reinstall with compatible image.

Task 3 Assign VVF License and Verify Entitlements

manageability

VVF licensing is subscription-based with Standard/Advanced/Enterprise tiers. Understanding assignment, entitlements, and expiry is critical for Obj 5.4.

Step 1

vCenter UI → Administration → Licensing → Licenses tab. Review current license keys. Note any evaluation licenses (60-day expiry).

License inventory shows existing keys with type, capacity, and expiration dates.

Step 2

Add VVF license key: Click '+' → enter VVF license key → Name it 'VVF Enterprise Plus'. Note the entitlements listed (vSphere, vSAN, vCenter).

VVF license is a unified key covering vSphere + vSAN + vCenter. No separate per-component keys needed — this is different from legacy vSphere licensing.

Step 3

Assign license to asset: Licensing → Assets tab → select upgraded ESXi host → Assign License → select VVF Enterprise Plus key.

Host license changes from 'Evaluation' to 'VVF Enterprise Plus'. Licensed features column updates.

Step 4

Verify entitlements: Click on the assigned license → Entitlements tab. Confirm: vSphere features (DRS, HA, FT), vSAN features (dedup, compression, encryption), capacity limits.

Entitlements list shows all VVF Enterprise features enabled.

Step 5

Simulate license expiry: Note expiration date. Understand grace period behavior — VVF licenses have a 60-day grace period after expiry during which all features continue to work but vCenter shows warning banners.

Exam tests: after grace period expires, hosts enter 'License Expired' state — no new VM power-on, no vMotion, but existing VMs continue running.

Step 6

Document: Compare VVF Standard vs Advanced vs Enterprise features in a table. Key differentiators: Standard (basic vSphere + vSAN), Advanced (adds encryption, stretched clusters), Enterprise (adds DRS, DPM, storage policies, full vSAN).

Validation Gate

Check: VVF license assigned and entitlements verified

Expected: Host shows VVF license. Entitlements match expected tier features.

Common Errors

License key rejected — 'Invalid license key'

Cause: Key format incorrect or key already consumed on different vCenter

Fix: Verify key format (XXXXX-XXXXX-XXXXX-XXXXX-XXXXX). Check Broadcom licensing portal for key status. Each key tied to specific vCenter Server ID.

Features not available after license assignment

Cause: License tier doesn't include the feature (e.g., Standard doesn't include DRS)

Fix: Check entitlements tab. Upgrade to appropriate tier if feature is required.

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 ESXi 9.0.x

✓ vLCM image compliance is green → Configure → Image shows 'Compliant'

✓ VVF license assigned → Host shows VVF Enterprise Plus license with correct entitlements

✓ Host operational → VMs running, vSAN healthy, no alarms

Cleanup / Restore

• Revert to pre-upgrade snapshot if needed for subsequent labs

• Remove evaluation license keys if no longer needed

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

Test license expiry by setting system clock forward — observe grace period behavior

Compare vLCM image-based vs baseline-based upgrade approaches

⚠ Known Pitfalls (from Community KB)

Never upgrade ESXi without checking vLCM image compliance first — incompatible drivers cause boot failures

vSAN data evacuation in 3-node cluster: use 'Ensure accessibility' not 'Full migration' (insufficient capacity)

VVF license is per-CPU socket, not per-core — verify socket count matches license capacity

References

vSphere Lifecycle Manager DocumentationTier 1 — Official
VVF 9.0 Licensing GuideTier 1 — Official
Broadcom HCLTier 1 — Official

Mark complete