NSX-T Host preparation fails with "Transport Zone cannot be relocated from HostSwitch <X> to HostSwitch <Y> in a single transaction."
book
Article ID: 319037
calendar_today
Updated On:
Products
VMware NSX
Issue/Introduction
Transport Nodes show 'Mismatch' NSX Configuration status in UI after applying a Transport Node Profile to hosts already prepared for NSX-T.
Clicking Mismatch > Match Cluster Configuration > Proceed generates an Alert: "The operation restoring the host's transport node profile with that of cluster has failed: Transport Zone TransportZone/<UUID> cannot be relocated from HostSwitch <current host switch name> to HostSwitch <host switch name in Transport Node Profile> in a single transaction. Delete Host Switch from current Transport Zone to add later to another Transport Zone."
Need to validated host switch Id from the validation error in ESXI host >>Run command from root net-dvs -l >>In problematic host that switch ID different from the expected one
Cause
NSX-T does not automatically move a Transport Zone already in use from one host switch to another.
Resolution
To resolve the Transport Node 'Mismatch' status, there are 2 options depending on whether changing the host switch name is desired:
Option 1: If the existing host switch name is acceptable, reconfigure the applied Transport Node Profile to use the current host switch name seen in vCenter. To update the host switch name configured in the Transport Node Profile, navigate to "System > Fabric > Profiles > Transport Node Profiles > Select profile > Edit"
Option 2: If a new host switch name is desired, NSX-T can be uninstalled from the hosts in question and reprepare the hosts for NSX-T with the a Transport Node Profile with a new host switch name.