NSX-V to NSX-T migration failed on host migration phase Failed error messages: TransportZones should be unique across all HostSwitches on a TransportNode
Article ID: 322537
Updated On:
Products
VMware NSX
Issue/Introduction
- You are in the process of migrating from NSX-V to NSX-T (V2T).
- During the process of host migration you see a similar error to the one below:
TN migration stage failed for host ########-####-####-####-############:host-## [Transport Node failed with '400: TransportZones should be unique across all HostSwitches on a TransportNode,
TransportZone ########-####-####-####-############ is already associated with HostSwitch null. for url: http://localhost:7440/nsxapi/api/v1/transport-nodes']
TransportZone ########-####-####-####-############ is already associated with HostSwitch null. for url: http://localhost:7440/nsxapi/api/v1/transport-nodes']
- The upgrade window was paused during the V2T migration until a workaround could be found.
- You may see similar entries in the /var/log/migration-coordinator/v2t/cm.log found on the NSX-T Manager where the migration is running.
CM.plugins.tz_plugin INFO The user chose segment [ls-vlan-###:ls-vlan-###] for dvpg [vSwitch2] with VLAN 0
CM.plugins.tz_plugin DEBUG Updating maps for VLAN 0 DVPGs ['vSwitch2'] in dvs-102 matching ls-vlan-### in TZ tz_edge
CM.plugins.tz_plugin DEBUG No VLAN 0 dvpg is left in vds vDS-Switch2
CM.plugins.tz_plugin INFO The user chose segment [ls-vlan-###:ls-vlan-###] for dvpg [vSwitch1] with VLAN 0
CM.plugins.tz_plugin DEBUG Updating maps for VLAN 0 DVPGs ['vSwitch1'] in dvs-101 matching ls-vlan-### in TZ tz_edge
CM.plugins.tz_plugin DEBUG No VLAN 0 dvpg is left in vds vDS-Switch1
CM.plugins.tz_plugin DEBUG Updating maps for VLAN 0 DVPGs ['vSwitch2'] in dvs-102 matching ls-vlan-### in TZ tz_edge
CM.plugins.tz_plugin DEBUG No VLAN 0 dvpg is left in vds vDS-Switch2
CM.plugins.tz_plugin INFO The user chose segment [ls-vlan-###:ls-vlan-###] for dvpg [vSwitch1] with VLAN 0
CM.plugins.tz_plugin DEBUG Updating maps for VLAN 0 DVPGs ['vSwitch1'] in dvs-101 matching ls-vlan-### in TZ tz_edge
CM.plugins.tz_plugin DEBUG No VLAN 0 dvpg is left in vds vDS-Switch1
- You may see similar entries in the /var/log/migration-coordinator/migration-coordinator.log file found on the NSX-T Manager
ERROR task-executor-1-workitem-HOST-########-####-####-####-############:host-## WorkItem 23570 SYSTEM [nsx@6876 comp="nsx-manager" errorCode="MP30033" level="ERROR" subcomp="upgrade-coordinator"] Error reported by plugin during upgrade of upgrade unit ########-####-####-####-############:host-##com.vmware.nsx.management.upgrade.exceptions.UpgradeUnitUpgradeException: null
...
INFO http-nio-127.0.0.1-7450-exec-4 MigrationFacadeImpl 23570 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="migration-coordinator"] Component: HOST, status: FAILED, % complete: 0.0, details: TN migration stage failed for host ########-####-####-####-############:host-## [Transport Node failed with '400: TransportZones should be unique across all HostSwitches on a TransportNode, TransportZone ########-####-####-####-############ is already associated with HostSwitch null. for url: http://localhost:7440/nsxapi/api/v1/transport-nodes'], canSkip: false
INFO http-nio-127.0.0.1-7450-exec-4 UpgradeQueryServiceImpl 23570 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="upgrade-coordinator"] Returning upgrade status summary for HOST details as TN migration stage failed for host ########-####-####-####-############:host-## [Transport Node failed with '400: TransportZones should be unique across all HostSwitches on a TransportNode, TransportZone ########-####-####-####-############ is already associated with HostSwitch null. for url: http://localhost:7440/nsxapi/api/v1/transport-nodes'].
INFO http-nio-127.0.0.1-7450-exec-1 UpgradeServiceImpl 23570 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="upgrade-coordinator"] Component type = HOST , Upgrade Status = FAILED, Progress Percentage = 0 , Progress Message =
...
INFO http-nio-127.0.0.1-7450-exec-4 MigrationFacadeImpl 23570 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="migration-coordinator"] Component: HOST, status: FAILED, % complete: 0.0, details: TN migration stage failed for host ########-####-####-####-############:host-## [Transport Node failed with '400: TransportZones should be unique across all HostSwitches on a TransportNode, TransportZone ########-####-####-####-############ is already associated with HostSwitch null. for url: http://localhost:7440/nsxapi/api/v1/transport-nodes'], canSkip: false
INFO http-nio-127.0.0.1-7450-exec-4 UpgradeQueryServiceImpl 23570 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="upgrade-coordinator"] Returning upgrade status summary for HOST details as TN migration stage failed for host ########-####-####-####-############:host-## [Transport Node failed with '400: TransportZones should be unique across all HostSwitches on a TransportNode, TransportZone ########-####-####-####-############ is already associated with HostSwitch null. for url: http://localhost:7440/nsxapi/api/v1/transport-nodes'].
INFO http-nio-127.0.0.1-7450-exec-1 UpgradeServiceImpl 23570 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="upgrade-coordinator"] Component type = HOST , Upgrade Status = FAILED, Progress Percentage = 0 , Progress Message =
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
Environment
VMware NSX 4.x
VMware NSX-T Data Center 3.x
Cause
There is a V2T plugin which blocks the migration if a Transport Zone (TZ) is assigned to two separate VDSes on a host.
For Bring Your Own Topology (BYOT) and modular host migration modes only: when you choose VLAN segments for VLAN DVPGs in VDSes, the segment's TZs will be assigned to the VDSes. If a TZ is assigned to two VDSes that are on one host to be migrated, The plugin generates blocking feedback to force the user to rollback and retry the migration, because otherwise the Transport Node (TN) will have the same TZ ID in two host-switches and will fail to be created.
For Bring Your Own Topology (BYOT) and modular host migration modes only: when you choose VLAN segments for VLAN DVPGs in VDSes, the segment's TZs will be assigned to the VDSes. If a TZ is assigned to two VDSes that are on one host to be migrated, The plugin generates blocking feedback to force the user to rollback and retry the migration, because otherwise the Transport Node (TN) will have the same TZ ID in two host-switches and will fail to be created.
Resolution
This issue is resolved in VMware NSX-T 3.2.3 and NSX 4.1.0, available at Broadcom downloads.
If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.
Workaround:
Removing the below section from the host-tn-config.json in the /var/log/migration-coordinator/v2t folder skips the migration of the overlapping segments.
"dvs_id":"dvs-102",
"dvs_uuid":"50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## 02",
"host_switch_name":"nvds.vDS-Switch2",
"is_overlay":"false",
"mtu":8800,
"transport_zone_ids":[
"########-####-####-####-############"
],
"uplink_profile_index":0
},
{
"dvs_id":"dvs-101",
"dvs_uuid":"50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## 01",
"host_switch_name":"nvds.vDS-Switch1",
"is_overlay":"false",
"mtu":8800,
"transport_zone_ids":[
"########-####-####-####-############"
],
"dvs_uuid":"50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## 02",
"host_switch_name":"nvds.vDS-Switch2",
"is_overlay":"false",
"mtu":8800,
"transport_zone_ids":[
"########-####-####-####-############"
],
"uplink_profile_index":0
},
{
"dvs_id":"dvs-101",
"dvs_uuid":"50 ## ## ## ## ## ## ##-## ## ## ## ## ## ## 01",
"host_switch_name":"nvds.vDS-Switch1",
"is_overlay":"false",
"mtu":8800,
"transport_zone_ids":[
"########-####-####-####-############"
],
Feedback
Yes
No
Powered by
