Firmware lifecycle made simple with vSphere Lifecycle Manager

What is a Hardware Support Manager?

A Hardware Support Manager (HSM) is an OEM management software provided by hardware vendors. Examples of HSMs include DELL OpenManage, HPE OneView, and Lenovo XClarity Integrator. HSMs might be standalone appliances, or integrated into existing OEM management systems depending on the OEM vendor.

You can find the full list of all VMware-certified hardware support managers in the VMware Compatibility Guide at https://www.vmware.com/resources/compatibility/search.php?deviceCategory=hsm

Hardware Support Managers integrate with vSphere and vSphere Lifecycle Manager to include and enable vSphere Lifecycle Manager to coordinate the software and firmware updates to a given host by working through the HSM to do firmware updates when the host has been evacuated and put into maintenance mode by vSphere Lifecycle Manager.

Why use a Hardware Support Manager?

Utilising a Hardware Support Manager allows vSphere administrators to complete full stack software maintenance and monitoring of clusters and hosts. A single remediation operation of a cluster, using vSphere Lifecycle Manager, can manage the ESX version, OEM drivers with vendor add-on bundles, and the firmware of various hardware components in the hosts.

Firmware versions, drivers versions and BIOS/EFI versions can be inspected and monitored for compliance with the VMware Compatibility Guide and vSAN Compatibility Guide.

vSphere Lifecycle Manager interfaces with a registered HSM to orchestrate the lifecycle of firmware components. The HSM performs the firmware lifecycle operation directly on the hardware components residing within the host.

Using a HSM allows vSphere to accurately inspect the firmware and driver versions of hardware components and compare the hardware specifications with the VMware Compatibility Guide and vSAN Compatibility Guide, ensuring full compliance with vSAN hardware requirements.

Integrating a HSM with vSphere Lifecycle Manager simplifies and speeds up total remediation times by using the same maintenance window for the ESX image and host firmware. Often, only a single reboot task is required. Firmware bundles, along with the ESX image, can also be pre-staged to the host further reducing the total maintenance time.

HSM Integration with vSphere

Integration between a HSM and vSphere Lifecycle Manager requires a registration with vCenter from the HSM side. This typically just requires the FQDN of the vCenter and appropriate credentials to establish a trust between the two. This process will vary depending on the HSM used.

In addition, how each HSM presents its firmware packages or bundles, sometimes referred to as hardware support packages (HSP), to vCenter will be a different and unique process.

Firmware packages reside on the HSM system and are not stored in the vSphere Lifecycle Manager depot. The HSM presents metadata about the firmware such as version information and driver compatibility to vSphere Lifecycle Manager for use during compliance checks and remediation.

Refer to the applicable HSM user guide for specific details on HSM configuration.

Note: External links valid at time of publishing. Visit the respective vendors documentation site for current versions.

Some HSMs integrate into the vSphere Client using a client UI plugin and provide a direct user-interface within the vSphere Client. Other HSMs require administration from a separate user-interface provided by the HSM appliance or the OEM management framework it’s a part of.

vSphere Lifecycle Manager Workflow

With a few additional clicks, vSphere administrators can add firmware bundles to their host and cluster images.

vSphere Administrator defines the desired image for the host or cluster. This image comprises, at a minimum the ESX version, and can also include a vendor addon and extra components. Firmware packages are included from a list presented by the registered HSM. Device firmware, drive firmware, EFI/BIOS updates can be part of the bundle presented by the HSM. The firmware packages remain stored on the HSM and are not stored in the vSphere Lifecycle Manager depot. The metadata is presented to vSphere Lifecycle Manager and stored in the desired image definition.
vSphere Lifecycle Manager will orchestrate the sequence of events as needed and normal pre-remediation tasks such as maintenance mode and host evacuation will occur. During vSphere Lifecycle Manager remediation, the ESX version, Vendor addon and components of the image are installed to the ESX host by vSphere Lifecycle Manager.
vSphere Lifecycle Manager will interface with the HSM and the HSM will install the firmware packages directly on the host through the baseboard management controller (BMC). Depending on the firmware and HSM, firmware(s) might be updated before or after the ESXi image and one or more reboots might be needed.

Summary