This lab targets VCF 9.0

Lab: Create & Apply Cluster Image

VCF 9.0Intermediatevcp-foundation⏱ 120 min

VVF 9.0 administrator lab (2V0-16.25). Built for a Holodeck VVF instance.

Objectives

  • Compose a vLCM cluster image from the depot: base image, vendor add-on, components (Obj 4.2)
  • Run compliance check and remediation pre-check
  • Remediate the cluster and confirm compliance

Prerequisites

Holodeck VVF 9.0 instance deployed and healthy

Lab Environment

Holodeck vSphere Foundation 9.0 instance (New-HoloDeckInstance -VVF; -vSANMode OSA by default, ESA where the physical layer supports it): vCenter managing one vSAN cluster of nested ESX hosts, plus VCF Operations. VVF has no SDDC Manager and no NSX. Firmware through a hardware support manager is physical-lab only.

Credentials

SystemUsernamePassword
vCenteradministrator@vsphere.localHolodeck documented default (Post Deployment table)
Nested ESX hostsrootHolodeck documented default (Post Deployment table)

Tasks

Task 1 Create & Apply Cluster Image

Cluster image management via vLCM is the standard lifecycle approach in vSphere 9.0. Understanding image composition (base ESXi + vendor add-on + components) and the compliance check workflow is essential for Day-2 operations.
Step 1

Lifecycle Manager → Settings: sync the online depot (entitled download token) or import the ESX 9.0 offline bundle into the depot (VCF 9.0.1 docs p.246). Binaries come from the Broadcom support portal or depot, not vmware.com.

Step 2

(Physical servers only) Register the vendor hardware support manager as a vCenter extension — for Dell that is OpenManage Integration for VMware vCenter (OMIVV), for HPE iLO Amplifier or OneView, for Lenovo XClarity Integrator (p.1811). In Holodeck skip firmware.

Step 3

Cluster → Updates → Image → Edit: choose the ESX base image version, the vendor add-on (if any) and extra components → Save. vLCM composes the image from the depot; it is not built by importing an ISO.

Step 4

Record the image composition (base image build, add-on version) in the lab log; vLCM images have no separate 'tag'.

Step 5

Check Compliance for the cluster against the new image.

Step 6

Run the remediation pre-check: it reports issues (for example a host that cannot enter maintenance mode, or a missing driver) before anything changes.

Step 7

Remediate: vLCM puts hosts into maintenance mode one at a time, applies the image and reboots them (there is no 'preview mode').

Step 8

Verify: the cluster shows Compliant; on a host, vmware -v shows the new build.

Validation Gate

Check: After creating and applying a cluster image: verify all hosts show 'Compliant' status, no hosts are in maintenance mode, and vSAN health is green

Expected: All hosts compliant with the cluster image. No hosts pending reboot. vSAN health shows all checks green after rolling update completes.

Common Errors

Creating a cluster image without the vendor add-on (firmware/drivers)
Fix: A cluster image with only base ESXi lacks vendor-specific drivers and firmware. VMs may run but hardware features (RAID controller, NIC offloads, GPU passthrough) won't function correctly. Always include the vendor add-on (e.g., Dell OpenManage Integration, HPE Agentless Management) in the cluster image.
Applying an image update during production hours without pre-check
Fix: Image remediation reboots hosts sequentially (rolling update). If DRS cannot evacuate VMs from a host (insufficient capacity), remediation stalls. Always run: (1) compliance check first, (2) verify DRS can evacuate each host, (3) schedule during maintenance window. Pre-check: vLCM → Check Compliance → Review remediation impact.
Not validating the cluster image in a test cluster first
Fix: A new cluster image (especially with firmware updates) can cause boot failures on incompatible hardware. Always validate the image on a non-production cluster or single host first. In Holodeck, test on a nested cluster before applying to production-simulated domains.
Mixing image-managed and baseline-managed clusters
Fix: vSphere 9.0 removed baseline-based patching. All clusters use image-based management via vLCM. If upgrading from vSphere 7.x/8.x, convert baseline-managed clusters to vLCM images BEFORE upgrading hosts to ESX 9.0 — vCenter 9.0 no longer supports baselines (VCF 9.0.1 docs p.1417, Transitioning from vSphere Lifecycle Manager Baselines). Mixed management modes are not supported.

Final Validation

Gate: every check below passes with the evidence recorded in the lab log.

✓ Image → Cluster image saved with the chosen base image and add-on

✓ Compliance → All hosts Compliant after remediation

✓ Cluster state → No host left in maintenance mode; vSAN health green

Cleanup / Restore

• Leave the image in place; record its composition

Design Reflection (VCDX)

Lifecycle management is a Day-2 operational requirement in VCDX designs. Panelists test whether you planned for patching cadence, image composition, and the operational impact of rolling updates on cluster availability.

Requirements

  • Create cluster images with base ESXi + vendor add-on + components
  • Validate images before production deployment
  • Schedule remediation during maintenance windows

Constraints

  • vSphere 9.0 requires image-based management only (no baselines)
  • Rolling updates require DRS capacity to evacuate each host
  • Firmware updates may require additional reboot cycles

Assumptions

  • Vendor add-on packages are available and compatible
  • DRS has sufficient headroom to evacuate VMs during rolling update

Risks

  • Boot failure from incompatible firmware in cluster image
  • Stalled remediation from insufficient DRS evacuation capacity

⚠ Known Pitfalls

Applying cluster image updates without pre-checking DRS evacuation capacity — if a host can't be evacuated, the update stalls mid-process.
Forgetting vendor add-on in the cluster image — base ESXi without vendor drivers causes hardware feature degradation.

References

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