Managing ESX host lifecycle operations with vSphere Lifecycle Manager Images (vLCM)
Article ID: 379388
Updated On:
Products
Issue/Introduction
With vSphere 7.0, VMware launched a feature called vSphere Lifecycle Manager Images (vLCM), which uses a declarative model, to holistically define the desired state of the ESX host image; including the target ESX version, add-on, firmware & drivers. This feature enables all the ESX hosts, to adhere to the desired state; by enforcing consistency across the cluster. When a host drifts from the desired state, the host can be ‘remediated’ to become compliant to the desired state, once again.
With the launch of vSphere 9.0, we are announcing the removal of major functionalities in vSphere Lifecycle Manager Baselines (previously known as vSphere Update Manager VUM).
Environment
vCenter 9.0
Resolution
Customers should transition from using vSphere Lifecycle Manager Baselines (VUM), to instead using vSphere Lifecycle Manager Images (vLCM) for managing the lifecycle of ESX hosts.
- For an overview of vLCM, see the documentation - Managing Host and Cluster Lifecycle
- For details on how to transition existing clusters to vLCM, see the user guide - Convert a Cluster That Uses Baselines Into a Cluster That Uses vSphere Lifecycle Manager Images
- vLCM will no longer be able to download updates from internet facing VMware by Broadcom public repositories. Download URLs are no longer common but unique for each customer, therefore will require to be re-configured. Refer KB 390098 for the steps to be followed if you are not seeing latest releases in Software Depot tab.
Scenarios for a VUM managed cluster:
| Scenario | What is allowed/blocked with VUM | Workaround |
| Cluster contains all 8.x ESX host(s) |
|
Transition from VUM to vLCM to overcome restrictions due to VUM |
| Cluster contains all 9.x ESX host(s) |
|
|
| Cluster contains 8.x and 9.x ESX host(s) |
|
Additional Information
Impacted areas are listed below:
| Operation | Expected behaviour |
| Rollup Bulletin | 'Rollup' bulletins will not be released from 9.0 onwards. |
| Patching of 9.x ESX host using VUM | Patching of 9.x ESX host using VUM is blocked |
| Patching of 8.x ESX host using VUM | Patching of 8.x ESX host using VUM is allowed |
| ISO import | ISO import is blocked |
| ISO based upgrade using VUM | ISO based upgrade is blocked for any ESX host version |
| For a ESX host, moved from VUM managed Cluster to DC/Folder which has never been in connected state | It will become vLCM managed SAH |
| Existing VUM managed Cluster with 8.x ESX host(s) | Cluster will continue to remain VUM managed. Behavioural changes related to patching, ISO based upgrade using VUM, 'Rollup' are applicable. Refer to respective row for knowing the exact change in behaviour. |
| Existing 8.x VUM managed SAH | SAH will continue to remain VUM managed. Behavioural changes related to patching, ISO based upgrade using VUM, 'Rollup' are applicable. Refer to respective row for knowing the exact change in behaviour. |
| ESX host movement of vLCM managed SAH to VUM managed cluster | Any vLCM managed SAH can now be moved to a VUM managed cluster |
| ESX host moved from vLCM managed cluster to DC/Folder | ESX host will become vLCM managed SAH. If the ESX host cannot be image managed then ESX host movement will fail and the ESX host continues to be part of the vLCM managed Cluster. |
| Creation of a new VUM managed Cluster | VUM managed cluster creation is not supported. Cluster will be managed by vLCM by default |
| Addition of ESX host(s) to an existing Cluster | ESX host(s) of 8.x/9.x versions can be added to any existing cluster |
| Adding a new VUM managed Standalone ESX Host(SAH) | VUM managed SAH addition is not supported. New SAH will be managed by vLCM by default |
| 9.x ESX host moved from VUM managed Cluster to DC/Folder | 9.x ESX host will become vLCM managed SAH when moved from VUM managed cluster to DC |
| 8.x ESX host moved from VUM managed Cluster to DC/Folder | 8.x ESX host continues to become VUM managed SAH |
Feedback
