Error: Transition from vSphere Baselines to vLCM Images not supported in VCF

Products

• VMware NSX

Issue/Introduction

When attempting to convert a cluster from vSphere Baselines to vSphere Lifecycle Manager (vLCM) Images in a VMware Cloud Foundation (VCF) environment, the operation fails with a support error. This typically occurs when there is an inconsistency in the NSX configuration.

Symptoms

Users see the following error in the vSphere Client:

• Transition from vSphere Baselines to vSphere Lifecycle Manager Images is not supported with VMware Cloud Foundation.
• The vum-server.log shows: EligibilityCheck.UnsupportedNsxtConfiguration.

 

Environment

• VMware Cloud Foundation 4.x, 5.x
• VMware NSX 4.x
• vCenter Server 8.0.x

Cause

The transition is blocked for two primary reasons:

1. VCF Version Constraints: Direct transition was not supported in VCF versions prior to 5.2.
2. NSX Profile Configuration: Even in supported versions, the transition fails if the cluster is not associated with a valid Transport Node Profile (TNP) within NSX.

Resolution

Fixed in release VCF 5.2 and higher. See Download Broadcom products and software for steps to download this release.

To resolve the configuration blocker in VCF 5.2+:

1. Log in to the NSX Manager UI.
2. Navigate to System > Fabric > Nodes > Host Transport Nodes.
3. Select the vCenter and cluster, then ensure a Transport Node Profile (TNP) is attached.
4. Return to the vSphere Client and retry the Transition to Image check.
5. Remediate the hosts. Note: This requires placing hosts in Maintenance Mode and performing a reboot.

For VCF 4.x and 5.1:

1. Continue managing existing clusters using vSphere Baselines.
2. Deploy any new clusters as vLCM Image-based directly from the SDDC Manager to ensure future compatibility.

Additional Information

• Transitioning from Baselines to Images (VCF TechDocs)
• To speak with a customer representative or a Support Engineer, see Contact Support.