Error: "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 Cent" during vLCM cluster image creation in VCF

Products

• VMware NSX
• VMware Cloud Foundation

Issue/Introduction

Validation fails when attempting to use a vCenter cluster for a vSphere Lifecycle Manager (vLCM) image or during a VMware Cloud Foundation (VCF) upgrade.

Symptoms:

• vCenter cluster image creation or transition fails during pre-checks.
• The following error appears: Error: 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.

Environment

• VMware Cloud Foundation 5.x / 9.x
• VMware NSX 4.x
• vSphere Lifecycle Manager (vLCM)

Cause

When VMware Cloud Foundation (VCF) prepares a cluster for NSX, it attaches the Transport Node Profile (TNP). Upon completion, VCF often detaches the TNP.

vLCM requires an active Transport Node Profile (TNP) attachment to manage a cluster as a single image. The validation check fails if the TNP was detached after initial preparation or if communication between NSX and vCenter (Compute Manager) is disrupted.

Resolution

Follow these steps to ensure the Transport Node Profile is correctly applied:

1. 1. Log in to the NSX Manager UI.
   2. Navigate to System > Fabric > Compute Managers and verify the vCenter connection status is Up.
   3. Navigate to System > Fabric > Hosts.
   4. Change the Managed by dropdown to the target vCenter Server.
   5. Locate the affected cluster and click Configure NSX.
   6. Apply the appropriate Transport Node Profile to the cluster.
   7. Verify the status transitions to Success or Up.
   8. Return to the vSphere Client and retry the vLCM workflow.
      
      
      

For more details on profile creation, see Adding a Transport Node Profile.

Additional Information

If no TNP exists, follow the documentation for Adding a Transport Node Profile

For further assistance, see Contact Broadcom Support or Creating and Managing Broadcom Cases