NSX-V to NSX-T migration failed on host migration phase Failed error messages: TransportZones should be unique across all HostSwitches on a TransportNode
search cancel

NSX-V to NSX-T migration failed on host migration phase Failed error messages: TransportZones should be unique across all HostSwitches on a TransportNode

book

Article ID: 322537

calendar_today

Updated On:

Products

VMware NSX Networking

Issue/Introduction

Symptoms:
  • 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 xxxxxxxx-edd4-48dd-9c21-1be38b2113e2:host-32 [Transport Node failed with '400: TransportZones should be unique across all HostSwitches on a TransportNode,
TransportZone xxxxxxxx-88b7-410f-9e96-485b70756151 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.
2023-03-04 02:22:51,290 1081 CM.plugins.tz_plugin INFO The user chose segment [ls-vlan-641:ls-vlan-741] for dvpg [vSwitch2] with VLAN 0
2023-03-04 02:22:51,290 1081 CM.plugins.tz_plugin DEBUG Updating maps for VLAN 0 DVPGs ['vSwitch2'] in dvs-200 matching ls-vlan-641 in TZ tz_edge
2023-03-04 02:22:51,290 1081 CM.plugins.tz_plugin DEBUG No VLAN 0 dvpg is left in vds vDS-Switch2
2023-03-04 02:22:51,291 1081 CM.plugins.tz_plugin INFO The user chose segment [ls-vlan-641:ls-vlan-641] for dvpg [vSwitch1] with VLAN 0
2023-03-04 02:22:51,291 1081 CM.plugins.tz_plugin DEBUG Updating maps for VLAN 0 DVPGs ['vSwitch1'] in dvs-102 matching ls-vlan-641 in TZ tz_edge
2023-03-04 02:22:51,291 1081 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-coordinatormigration-coordiantor.log file found on the NSX-T Manager
2023-03-04T03:18:03.794Z ERROR task-executor-1-workitem-HOST-xxxxxxxx-edd4-48dd-9c21-1be38b2113e2:host-18 WorkItem 23570 SYSTEM [nsx@6876 comp="nsx-manager" errorCode="MP30033" level="ERROR" subcomp="upgrade-coordinator"] Error reported by plugin during upgrade of upgrade unit xxxxxxx-edd4-48dd-9c21-1be38b2113e2:host-
18com.vmware.nsx.management.upgrade.exceptions.UpgradeUnitUpgradeException: null
...
2023-03-04T03:18:09.594Z  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 xxxxxxxx-edd4-48dd-9c21-1be38b2113e2:host-18 [Transport Node failed with '400: TransportZones should be unique across all HostSwitches on a TransportNode, TransportZone xxxxxxx-88b7-410f-9e96-485b70756151 is already associated with HostSwitch null. for url: http://localhost:7440/nsxapi/api/v1/transport-nodes'], canSkip: false
2023-03-04T03:18:09.594Z  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 xxxxxxxx-edd4-48dd-9c21-1be38b2113e2:host-18 [Transport Node failed with '400: TransportZones should be unique across all HostSwitches on a TransportNode, TransportZone xxxxxxxx-88b7-410f-9e96-485b70756151 is already associated with HostSwitch null. for url: http://localhost:7440/nsxapi/api/v1/transport-nodes'].
2023-03-04T05:48:02.612Z  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-T Data Center

Cause

There is a V2T plugin, which blocks the migration, if a Transport Zone (TZ) is assigned to two separate VDS on a host.
For Bring Your Own Topology (BYOT) and modular host migration modes only: when you choose VLAN segments for VLAN DVPGs in VDS's, the segment's TZs will be assigned to the VDS's. If a TZ is assigned to two VDS's 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 created.

Resolution

This issue is resolved in NSX-T 3.2.3 and 4.1.0 available at VMware Downloads.

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-2",
                    "dvs_uuid":"50 02 be 84 b8 de 83 0f-91 99 15 e3 ae 7a c1 49",
                    "host_switch_name":"nvds.vDS-Switch2",
                    "is_overlay":"false",
                    "mtu":8800,
                    "transport_zone_ids":[
                        "xxxxxxxx-88b7-410f-9e96-485b70756151"
                    ],
                    "uplink_profile_index":0
                },
                {
                    "dvs_id":"dvs-1",
                    "dvs_uuid":"50 02 42 27 9f 6a 37 ee-b8 9d 95 ea 59 d1 ac b7",
                    "host_switch_name":"nvds.vDS.switch1",
                    "is_overlay":"false",
                    "mtu":8800,
                    "transport_zone_ids":[
                        "xxxxxxxx-88b7-410f-9e96-485b70756151"
                    ],