To complete an upgrade to VCF 9, all clusters must transition from vLCM baseline management (formerly VUM) to vLCM image management. The ESX upgrade portion of the VMware Cloud Foundation 9.x process requires vLCM image-managed clusters as a prerequisite.
However, vLCM images for heterogeneous hardware-based clusters are only supported starting in ESX 9. This seemingly creates a circular dependency where the transition must occur after the ESX 9 upgrade, but the upgrade normally requires the transition first. To resolve this, a special process is required to temporarily allow the vCenter Update Manager (VUM) service to perform the upgrade to ESX 9 on these specific clusters.
The system cannot upgrade to a vLCM Image-managed cluster without first upgrading to ESX 9, but vLCM image management on heterogeneous hardware clusters is not supported until the hosts are already running ESX 9.
The vCenter Update Manager service can be unrestricted via a Broadcom-provided PowerShell script or vCenter APIs, provided that one or more heterogeneous-hardware clusters are detected in the inventory.
Important Caveats:
Option 1: PowerShell (Preferred)
Requirements:
Note: Before installing VCF.PowerCLI uninstall VMware.PowerCLI to avoid conflicts between the two modules.
Steps:
|
Status |
Meaning |
Action Required |
|
N/A |
vCenter version not supported |
Upgrade to vCenter 9.0 or later |
|
Unrestricted |
Success - VUM Services Unrestricted |
Ready to proceed to ESX 9.0 upgrade |
|
Restricted |
No heterogeneous clusters located |
Transition clusters to vLCM images normally |
|
Failed |
vCenter Task failed or blocked |
Open a support case |
Option 2: API (Using Developer Center)
Requirements:
Steps:
Support
For product issues, please open a standard Broadcom support case.
For bugs or enhancement requests with this script, please open a github issue.