WilliamLam.com

Custom ESXi "Dummy" Reboot VIB for vSphere Lifecycle Manager (vLCM)

by // 2 Comments

A few weeks back, I had a request from one of our Technical Adoption Managers (TAM) that their customer wanted to create a custom ESXi VIB that could be used with vSphere Lifecycle Manager (vLCM) and would only require the ESXi host to reboot as part of the remediation.

This might sound like a strange request but I suspect the customer was either building out some automation for vLCM or simply getting more hands on with vLCM without applying any changes, which is great because its predecessor, vSphere Update Manager (VUM) will be removed in a future major release of vSphere.

While the customer was able to create a custom VIB by following the instructions in my recent blog post for building a custom VIB for ESXi 8.x, I did noticed that their descriptor.xml did not properly set the live-install-allowed and live-remove-allowed options which controls whether an ESXi host should reboot after installing and removing a VIB from the host respectively.


Since vLCM only works with offline bundles, we actually need to create an offline bundle with our custom ESXi VIB that vLCM can import. To further complicate things, starting with vSphere 7.x, a proper offline bundle that can be imported into vLCM requires the use of components rather than bulletins, which is what VUM previously had used.

With the assistance of the vLCM Engineering team, I was able to create my own "Dummy" ESXi VIB/Offline Bundle that is compatible with both vSphere 7.x and 8.x, which can be used directly by a standalone ESXi host via ESXCLI or imported and lifecycle using vLCM.

[Read more...]

Retrieving detailed vSphere Lifecycle Manager (vLCM) Image information from vSphere Cluster using PowerCLI

by // Leave a Comment

As more and more users are adopting vSphere Lifecycle Manager (vLCM) to simplify the lifecycle and configuration management of their ESXi hosts, you may want to get more information about a given vLCM image that has been associated with a specific vSphere Cluster.

While you can certainly get this information using the vSphere UI, you can also get this detailed information by using the vLCM REST API, which can easily be consumed using variety of vSphere SDK Clients including PowerCLI.

For inventory and/or auditing purposes, automation is typically the answer, especially at scale. I will not bore you with the details, but I recently created the following PowerCLI function called Get-vLCMClusterImageInformation and given the name of a vLCM-enabled vSphere Cluster, it will provide you with the associated ESXi base image and all Solutions and Components that is associated with a given image.

UPDATE (02/06/25) - The script has also been updated to also include information for a vLCM image that has integrated with an Hardware Support Manager (HSM) to provide firmware information.

[Read more...]

Disabling vCenter Lifecycle Manager automatic download using vSphere API

by // 1 Comment

By default, vCenter Server will automatically check and download the latest ESXi updates that can then be used by either the deprecated vSphere Update Manager (VUM) or its replacement which is vSphere Lifecycle Manager (vLCM), both of which can be managed under the Lifecycle Manager section in the vSphere UI.

Interestingly, I have had a number of inquiries about disabling the automatic download setting using automation, as I assume users have setup Update Manager Depot Service (UMDS) instance for consolidated and/or offline access.


Disabling the automatic download in the vSphere UI is very straight forward by going to Lifecycle Manager->Settings->Administration->Patch Downloads and clicking on the Edit button to enable or disable the setting.

Because the Lifecycle Manager section combines functionality for both VUM and vLCM, it can sometimes be confusing on which vSphere API to use and this is important becauase VUM does not have any public API and only subset of its functionality can be automated using specific VUM PowerCLI cmdlets. This is another benefit to using vLCM, not only is it the replacement for VUM going forward, but all of its functionality is available using both the vSphere UI or vSphere REST API.

With that said, the automatic download setting is actually a VUM-based configuration and as mentioned earlier, there are no public APIs for managing these settings. However, I recently found a clever workaround that would allow users to automate disabling this setting.

[Read more...]