10.2 Base Images, Vendor Add-ons & Hardware Support Managers (HSM)

10.2 Base Images, Vendor Add-ons & Hardware Support Managers (HSM)

In traditional enterprise datacenters, server lifecycle management was disjointed. Virtualization administrators used vSphere Update Manager to patch the ESXi hypervisor, while server infrastructure teams used dedicated hardware management tools—such as Dell OpenManage, HPE OneView, or Lenovo XClarity—to update system BIOS, out-of-band management controllers, and network adapter firmware. This operational divide often caused driver-firmware mismatches, uncoordinated reboot cycles, and prolonged maintenance windows. vSphere Lifecycle Manager (vLCM) eliminates this fragmentation through a modular, layered image architecture coupled with Hardware Support Managers (HSM).

---

The Four Modular Layers of a vLCM Cluster Image

A vLCM cluster image represents a complete software and firmware specification for all ESXi hosts within a cluster. Rather than bundling software into monolithic, opaque custom ISOs, vLCM decomposes the target software stack into four distinct, independently manageable layers:

1. ESXi Base Image

The foundational layer of the cluster image is the official ESXi Base Image published directly by VMware/Broadcom. It provides the core hypervisor kernel (vmkernel), system libraries, base networking and storage stacks, and standard inbox drivers. Administrators select a specific major version, update release, or maintenance build (such as a selected supported ESX 9.0 build) from the vLCM depot.

2. Vendor Add-on (OEM Customization Package)

Server hardware manufacturers (such as Dell Technologies, Hewlett Packard Enterprise, Lenovo, and Cisco Systems) engineer proprietary server platforms with specialized onboard controllers, mezzanine adapters, and diagnostic sensors. The Vendor Add-on is a curated software package provided directly by the OEM:

• Device Drivers: Contains certified driver packages for onboard network interface cards (NICs), Fibre Channel host bus adapters (HBAs), and SAS/SATA/NVMe storage controllers.
• Release-specific vendor integration: ESX 9.0 removes legacy CIM services and providers. Use the OEM's current supported management integration rather than importing an old CIM bundle.
• OEM Utilities: Includes hardware diagnostic utilities and platform-specific kernel modules.

When an administrator specifies a Vendor Add-on (for example, Dell Addon for ESXi 8.0U3), vLCM automatically integrates the OEM bundle with the ESXi base image, replacing default inbox drivers with OEM-tested versions.

3. Firmware and Driver Add-on (Hardware Support Manager)

Operating beneath the hypervisor software are the physical server's hardware microcode components: system BIOS, Unified Extensible Firmware Interface (UEFI), baseboard management controllers (BMCs), RAID controller microcode, and network adapter EEPROMs. The Firmware and Driver Add-on links the cluster software image directly to physical hardware firmware, managed through a certified Hardware Support Manager (HSM).

4. Independent Components

In enterprise environments, clusters frequently require auxiliary software packages that are neither part of VMware's base ESXi release nor included in the OEM vendor add-on. The Independent Components layer allows administrators to incorporate discrete VIB packages directly into the desired image:

• Asynchronous Drivers: Specialized device drivers released out-of-band by component manufacturers (e.g., high-performance NVIDIA/Mellanox ConnectX network drivers or specialized GPU acceleration VIBs).
• Enterprise Agent VIBs: Third-party supported vendor components; do not assume an arbitrary guest or backup-product agent is installable in the hypervisor.
• Storage Replication Filters: Custom I/O filter drivers (VAIO) used by third-party replication or caching engines.

By managing these as Independent Components within the cluster image, vLCM ensures that required third-party software is preserved across hypervisor upgrades rather than inadvertently stripped out during remediation.

Layer Composition Summary

---

Hardware Support Manager (HSM) Architecture & Mechanics

A Hardware Support Manager (HSM) is a vendor-developed integration service deployed as a virtual appliance within the vSphere environment. The HSM functions as an intelligent translation bridge between vCenter Server and the server vendor's proprietary hardware management ecosystem:

• Dell Technologies: Dell OpenManage Integration for VMware vCenter (OMIVV) / OpenManage Enterprise (OME) interfacing with the Integrated Dell Remote Access Controller (iDRAC).
• Hewlett Packard Enterprise (HPE): HPE OneView for VMware vCenter interfacing with Integrated Lights-Out (iLO).
• Lenovo: Lenovo XClarity Integrator (LXCI) for VMware vCenter interfacing with Lenovo XClarity Controller (XCC).
• Cisco: Cisco Intersight / UCS Manager integration.

Unified Full-Stack Remediation

Prior to HSM integration, updating a physical host required two disjointed maintenance cycles: first flashing server firmware via the OEM's out-of-band console, rebooting the physical host, and subsequently using VUM to install hypervisor patches with a second reboot.

With an HSM integrated into vLCM, the administrator executes unified full-stack remediation:

1. The administrator defines both the software image (Base + Vendor Add-on) and the hardware firmware package in the cluster image specification.
2. When remediation begins, vLCM coordinates with Distributed Resource Scheduler (DRS) to evacuate virtual machines and place the host into Maintenance Mode.
3. vLCM passes the firmware payload instructions to the registered HSM appliance.
4. The HSM connects out-of-band to the physical host's BMC (iDRAC/iLO/XCC) and stages the hardware firmware (BIOS, storage controller, NIC microcode).
5. vLCM stages and installs the ESXi hypervisor updates and driver VIBs.
6. The host performs the restart sequence required by the payload and hardware. During POST, the server's lifecycle controller flashes the staged firmware payloads. The host then boots directly into the updated ESXi hypervisor.
7. vLCM and the HSM verify that both software and hardware firmware reach 100% compliance before exiting Maintenance Mode and restoring workloads.

VMware Compatibility Guide (vCG / HCL) Integration

vSphere Lifecycle Manager continuously validates configured cluster images against the VMware Compatibility Guide (vCG), formerly known as the Hardware Compatibility List (HCL). vLCM downloads the official compatibility database directly from VMware (or ingests an offline XML manifest in air-gapped environments):

• When an administrator selects a target ESXi base image, vLCM cross-references the server model, CPU microarchitecture, and installed PCI devices against the vCG.
• If a specific network adapter or storage controller is unsupported on the selected ESXi version, or if the installed driver version does not match the certified firmware revision, vLCM flags the discrepancy with yellow warnings or red blocking errors before remediation is permitted.

---

vSAN Integration with vLCM

In hyperconverged infrastructure (HCI) deployments running VMware vSAN, hardware and driver alignment is exceptionally critical. Storage controllers, solid-state drives (SSDs), and NVMe devices in a vSAN cluster communicate directly with the ESXi storage stack without intervening SAN controllers. Mismatched firmware or uncertified controller drivers can cause queue saturation, I/O timeouts, silent data corruption, or catastrophic datastore unresponsiveness.

The Automated vSAN HCL Recommendation Engine

vLCM features deep native integration with the vSAN HCL Recommendation Engine:

• Automated Hardware Discovery: When an administrator enables vLCM on a vSAN cluster, vCenter automatically queries every host's physical storage controllers, NVMe flash drives, SAS/SATA SSDs, and disk backplanes.
• Dynamic HCL Verification: vLCM compares the discovered hardware inventory against the official vSAN Hardware Compatibility Guide database.
• Validated Image Recommendations: When upgrading a vSAN cluster, vLCM does not merely present generic ESXi releases; it generates tailored recommendations that pair the target ESXi base image with the exact certified OEM vendor add-on, storage controller driver, and controller firmware required for stable vSAN operation.

In the vSphere Client under Cluster > Updates > Image > Hardware Compatibility, administrators can view a granular matrix showing each physical component (e.g., Broadcom MegaRAID SAS 9361-8i or Samsung PM1733 NVMe SSD), its detected driver and firmware levels, and its compliance status against the vSAN HCL.

For the release boundary, see Broadcom KB 454750: legacy CIM hardware-monitoring providers are not supported in ESX 9.0.

Review Takeaways

• A desired image combines the base image with applicable vendor, firmware and independent components.
• Hardware Support Managers coordinate supported OEM firmware/driver updates with vLCM.
• ESX 9.0 removes legacy CIM services/providers; use the OEM's current supported integration.
• Validate hardware and vSAN compatibility before remediation; restart requirements depend on the payload.