V2T Migration fails with the following "Config translation failed [Reason: [topology_plugin] Can not proceed with migration: edge-X is not deployed on NSX-V and cannot be migrated."

Products

• VMware NSX

Issue/Introduction

Symptoms:

• NSX-V to NSX-T Migration fails with the following "Config translation failed [Reason: [topology_plugin] Can not proceed with migration: edge-x is not deployed on NSX-V and cannot be migrated. If you need to migrate this edge, please rollback and deploy it. Otherwise remove it from NSX-V. Restart migration after this is done.]"
• Once you define the topology and proceed with translate config on the NSX-T migrate UI, you see the above error.
• A DLR exists without a control VM (CVM) deployed on the NSX-V infrastructure.

Migration-coordinator Log:

xxxx-xx-xx: INFO http-nio-127.0.0.1-7450-exec-5 MigrationFacadeImpl 29458 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="migration-coordinator"] Unit: ConfigCollectorL3ToL7, status:
 FAILED, % complete: 0.0, errors: Config translation failed [Reason: [topology_plugin] Can not proceed with migration: edge-1 is not deployed on NSX-V and cannot be migrated. If you need to migrate this edge, please rollback and deploy it. Otherwise remove it from NSX-V. Restart migration after this is done.]Config translation failed [Reason: ]

Environment

VMware NSX-T Data Center

Cause

During the Translate Configuration step, the Migration Coordinator performs a DLR/UDLR appliance deployment check, if there is no Control VM deployed for the DLR, the aforementioned error will be thrown on the UI.

Resolution

• The python file has to be modified for the config migration stage to complete successfully.
• If the customer has a DLR without CVM deployed, then they will have to migrate to the version where the fix is in place.
• If the DLR is not mapped during the config translation phase, there will be traffic disruption until the host migration is complete.

A code change has been made where DLR/UDLR appliance deployment check is removed from versions of NSX-T 4.1.0 and above.

Workaround:

Additional Information

Impact/Risks:
The above error is a V2T migration blocker.