NSX-T migration from NSX for vSphere fails during layer 3 config translation with error: Invalid NSX V Manager IP address

Products

• VMware NSX

Issue/Introduction

• You are migrating from NSX for vSphere to NSX-T 3.2.2.x or 4.0.x.
• During this migration, as per the documentation, you define the NSX for vSphere manager and vCenter it uses using FQDN, as configured in NSX for vSphere.
• Then later during the layer 3 configuration translation stage, you are presented with an error similar to:

Config translation failed [Reason: [topology_plugin] Can not proceed with migration: Invalid NSX V Manager IP address nsx-v-manager.local is provided for mapping [{'v_edges': ['edge-10', 'edge-11'], 'policy_gateway_name': 'T0-01', 'policy_gateway_path': '/infra/tier-0s/T0'}, {'v_edges': ['edge-12'], 'policy_gateway_name': 'T0-02', 'policy_gateway_path': '/infra/tier-0s/T0-02'}, {'v_edges': ['edge-13'], 'policy_gateway_name': 'T1', 'policy_gateway_path': '/infra/tier-1s/T1'}, {'v_edges': ['edge-19'], 'policy_gateway_name': 'T1-02', 'policy_gateway_path': '/infra/tier-1s/T002'}]

Environment

VMware NSX 4.x
VMware NSX-T Data Center 3.x

Cause

Incorrect validation occurs here during the define topology for layer 3 and fails when the NSX for vSphere manager is defined using an FQDN address.

Resolution

This is a known issue impacting VMware NSX.
If you believe you have encountered this issue and the workaround does not work for you, please open a support request with Broadcom Support GSS and refer to this KB.

Workaround

• Instead of doing the mapping in the UI, you can create the layer 3 mapping json file and import it.
  
  Or
  
  
• You can use the auto generated mapping file as below and edit it.

 

To get the auto generated layer 3 json mappings to use.

• After the first failure and before you rollback, copy the file:
  /var/log/migration-coordinator/v2t/l3_mapping.json

• Edit this file and change the FQDN address of the NSX for vSphere manager to use an IP address, save the file somewhere other than the path it is found in:
  /var/log/migration-coordinator/v2t/
  
  
• The reason to save somewhere else, is that when you rollback the file will be deleted.
  • You can save it in: /repository/
    
    
• Then, during the migration again and in the 'Define Topology for layer 3', you have the option to import the mappings file, use the file we exported and edited, it will have the mapping you previously entered and also the NSX for vSphere manager IP address.