V2T Migration Error: Config translation failed [Reason: Transport Zone failed with "host-xxx"]

Products

• VMware NSX

Issue/Introduction

• NSX-V to NSX-T Migration fails with the following error:
  Config translation failed [Reason: Transport Zone failed with "host-xxx"]

• In the NSX-T Manager var/log/migration-coordinator/migration-coordinator.log, similar messages can be seen:
  
  INFO task-executor-10-1-workitem-PRECHECK-ConfigTranslator ExecutionMonitorServiceImpl 2959748 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="upgrade-coordinator"] Execution monitor service invoked to react to failure of node ConfigTranslator [Config translation failed [Reason: Transport Zone failed with ''host-xxx'']]


• In the NSX-T Manager var/log/migration-coordinator/v2t/vc-collection.log, similar messages can be seen:

ERROR    Failed to refresh networking configuration on Host: host-xyz.domain, Exception [Traceback (most recent call last):   File "/opt/vmware/migration-coordinator-tomcat/bin/v2t/config-collector/vc_collector.py", line 660, in collect_host_config     net_sys.Refresh()   File "/usr/lib/python3/dist-packages/pyVmomi/VmomiSupport.py", line 556, in     self.f(*(self.args + (obj,) + args), **kwargs)   File "/usr/lib/python3/dist-packages/pyVmomi/VmomiSupport.py", line 368, in _InvokeMethod     return self._stub.InvokeMethod(self, info, args)   File "/usr/lib/python3/dist-packages/pyVmomi/SoapAdapter.py", line 1481, in InvokeMethod     raise obj # pylint: disable-msg=E0702 pyVmomi.VmomiSupport.vmodl.fault.HostNotConnected: (vmodl.fault.HostNotConnected) {    dynamicType = ,    dynamicProperty = (vmodl.DynamicProperty) [],    msg = 'Unable to communicate with the remote host, since it is disconnected.',    faultCause = ,    faultMessage =
INFO     Failed to create vc client connection, not collecting VC Config ,error : Traceback (most recent call last):   
INFO     host.config.network AttributeError: 'NoneType' object has no attribute 'network'

Environment

VMware NSX

Cause

V2T config collection marks a host as disconnected if it is unable to successfully issue an API call on vCenter to refresh its host network configuration with the latest configuration on the host. This blocks the V2T migration from proceeding forward if the disconnected host is in the migration scope.

Resolution

To workaround the issue, you must do either of the following:

1. Correct the underlying network issue and reconnect the host to vCenter.
2. or Remove the host from vCenter that is in the disconnected state and part of the migration plan.

Re-attempt the migration.