vLCM Cluster Conversion Fails with "Transport Node Profile is not configured" due to Disconnected Compute Manager

Products

• VMware SDDC Manager / VCF Installer
• VMware vCenter Server
• VMware Cloud Foundation

Issue/Introduction

• Attempting to transition a vSphere cluster from baseline-based to image-based lifecycle management using vSphere Lifecycle Manager (vLCM) fails.
  
  
• The vCenter Server UI displays the following error message during the transition pre-check or execution phase:

  "Transport Node Profile is not configured on the cluster but NSX-T Data Center is installed on the following host(s): Apply Transport Node Profile without N-VDS on the cluster, or uninstall NSX-T Data Center."

• Within the NSX-T Manager UI, the Compute Manager (vCenter Server) Connection Status shows as Down.

Environment

• VMware Cloud Foundation 5.2.x
• VMware Cloud Foundation 9.x
• VMware vCenter Server

Cause

This issue occurs due to a communication failure between NSX-T and vCenter Server.  

For vLCM to successfully manage an NSX-enabled cluster via images, a Transport Node Profile (TNP) must be attached at the cluster level. While the vLCM error indicates a missing TNP, the root cause is that the NSX-T Compute Manager is disconnected. Because the connection is Down, vCenter and NSX-T cannot synchronize their inventory data, preventing vLCM from validating the existing TNP.  

A disconnected Compute Manager is typically caused by:

• An expired or recently changed Local SSO(example: [e-mail]) password.
• Recently updated or replaced vCenter Server SSL certificates, which breaks the certificate trust between NSX Manager and vCenter.

Resolution

To resolve this issue re-establish the connection between NSX-T and vCenter Server before retrying the cluster conversion.

1. Resolve the Compute Manager Connection
   
   
   1. Log in to the NSX-T Manager user interface with Admin account.

   2. Navigate to System > Fabric > Compute Managers.

   3. Locate the vCenter Server showing the Connection Status as Down.

   4. Select the Compute Manager and click Edit (or click Resolve if prompted under the Status column).

   5. Update the configuration based on the root cause:

      • Credential Issue: Re-enter the correct credentials for the vCenter Server.

      • Certificate Issue: If prompted with a new thumbprint mismatch, verify and accept the new vCenter Server SSL certificate thumbprint.

   6. Click Save.

   7. Wait a few moments and refresh the UI to confirm the Registration Status is Registered and the Connection Status returns to Up.

2. Verify the Transport Node ProfileIn the NSX-T UI, navigate to System > Fabric > Nodes > Host Transport Nodes.

   1. Change the 'Managed by' dropdown to your resolved vCenter Server.

   2. Locate the target cluster and ensure the correct Transport Node Profile is attached.

3. Retry the vLCM Cluster Conversion

   1. Return to the vSphere Client.

   2. Navigate to the target cluster > Updates tab.

   3. Re-initiate the process to transition from baselines to images. With the synchronization restored, vLCM will successfully detect the TNP and allow the conversion to proceed.