Unable to Detach Transport Node Profile VCF managed environments
search cancel

Unable to Detach Transport Node Profile VCF managed environments

book

Article ID: 436717

calendar_today

Updated On:

Products

VMware NSX VMware Cloud Foundation

Issue/Introduction

  • When attempting to remove or modify a Transport Node Profile (TNP) from a cluster in NSX, the "Detach" option is greyed out.
  • The cluster is part of a VMware Cloud Foundation (VCF) managed environment.
  • vSphere Lifecycle Manager (vLCM) may or may not be active, but the management plane lock persists.

Environment

NSX 4.2.x
VCF 5.x

Cause

In VCF-integrated environments, the Management Plane enforces a strict association between the Cluster and its Transport Node Profile to maintain consistency with the SDDC Manager database. The UI prevents "Detaching" because a cluster cannot exist in an "Unmanaged" state within the VCF framework without triggering a massive configuration drift.

Resolution

Workaround:

Instead of detaching the profile, use the "Profile Swap" method. This allows you to update the configuration (such as adding a new Transport Zone) without breaking the management link.

Step 1: Clone the Existing Configuration

  1. Navigate to System > Fabric > Hosts > Transport Node Profiles.

  2. Open the existing profile and document all settings (Uplink Profile, Teaming Policies, IP Pools, and VNI/VLAN mappings).

  3. Click Add Transport Node Profile to create a new version (e.g., TNP_Cluster_v2).

  4. Apply all original settings, then add the newly required Transport Zone.

    • Note: Ensure the new Transport Zone does not have a conflicting default teaming policy set at the TZ level.

Step 2: Reconfigure the Cluster

  1. Navigate to System > Fabric > Nodes > Host Transport Nodes.

  2. Select the Managed vCenter from the dropdown menu.

  3. Check the box next to the affected Cluster.

  4. Click Configure NSX.

  5. In the deployment wizard, use the dropdown to select the newly created TNP.

  6. Click Save. NSX will now perform a rolling update of the metadata across the hosts in the cluster.

Step 3: Post-Update Validation

  1. Monitor the Realization State in the NSX UI to ensure all hosts return a "Success" status.

  2. Verify the new Transport Zone is visible on the hosts via CLI: esxcli network ens transportzone list

  3. Log into SDDC Manager and perform a Resource Inventory Refresh to ensure the new profile name is acknowledged.

Powered by Wolken Software