Configuration mismatch in NSX for host transport node "Cannot update TransportNode/<uuid> to remove TransportZone/<uuid> as this TransportZone has LogicalSwitches with # VIF attachments"

Products

• VMware NSX

Issue/Introduction

• An NSX Transport Node Profile is applied to the vSphere ESX cluster
• ESX hosts are already prepared for NSX and have been for some time
• You have removed a Transport Zone from a Transport Node Profile
• One or multiple Transport Nodes within the cluster show NSX Configuration with a Validation Error
• There are no Virtual Machines powered on and connected to NSX segments (either Overlay or VLAN) that use the removed Transport Zone on the Transport Nodes with the Validation Error
• On an affected Transport Node, you see the removed Transport Zone UUID being applied after you have already removed the Transport Zone from the Transport Node Profile
  
  /var/run/log/nsx-syslog
<TIMESTAMP> In(###) nsx-opsagent[######]: NSX ###### - [nsx@6876 comp="nsx-esx" subcomp="opsagent" s2comp="nsxa" tid="#####" level="INFO"] [HostConfigReply] sending HostConfig RPC reply...:
<TIMESTAMP> In(###)[+] nsx-opsagent[######]: host_switches {
<TIMESTAMP> In(###)[+] nsx-opsagent[######]:   switch_id: "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##"
<TIMESTAMP> In(###)[+] nsx-opsagent[######]:   host_switch_profiles {
<TIMESTAMP> In(###)[+] nsx-opsagent[######]:     uplink_profile {
<TIMESTAMP> In(###)[+] nsx-opsagent[######]:       teaming_policy: LOADBALANCE_PORT_ID
<TIMESTAMP> In(###)[+] nsx-opsagent[######]:   transportzone_id: "<TZ-UUID>" <--------- this is the TZ VLAN UUID that was removed from the Transport Node Profile

Environment

VMware NSX

Cause

The Transport Node has received an outdated Transport Node Profile still containing the removed Transport Zone.

Resolution

Workaround:

Resync the Transport Node Profile to the affected Transport Nodes.

Via API:

POST /policy/api/v1/infra/sites/{site-id}/enforcement-points/{enforcementpoint-id}/host-transport-nodes/{host-transport-node-id}?action=resync_host_config

Via UI:

1. From NSX manager: System > Fabric > Hosts 
2. Select the transport node and click on 'Configure NSX'
3. Complete the next steps without making any changes 

Additional Information

Starting with NSX 4.0.1.1, the user interface displays a warning, if at any point, your host transport node goes out of sync with the Management Plane.
To initiate the resync operation, select Actions > Sync Transport Node for your host transport node

If you do have VMs powered on and connected to NSX segments (either Overlay or VLAN), please review the following KB for details on removing the Transport Zone:
https://knowledge.broadcom.com/external/article?articleNumber=393793