NSX-T 3.1.x UI shows Transport Nodes Tunnels down after V2T migration

Products

• VMware NSX

Issue/Introduction

• System --> Fabric --> Nodes shows some host transport nodes are in "degraded" status and have some tunnels in "down" status after the v2T migration.
• Log lines similar to the below are encountered on the NSX Manager in /var/log/syslog

  INFO pool-33-thread-1 LcpReplicatorImpl 14183 - [nsx@6876 comp="nsx-controller" level="INFO" subcomp="replication"] TN data ########-####-####-####-############ was not expired shortly since the source is MP (v-t migration)
  
  INFO pool-33-thread-1 LcpReplicatorImpl 14183 - [nsx@6876 comp="nsx-controller" level="INFO" subcomp="replication"] TN data was not expired yet. Stop removing TN key ########-####-####-####-############.

Environment

VMware NSX-T Data Center

Cause

When migrating from NSX-v to NSX-T, some NSX-v TEPs migrated to NSX-T are left unused if hosts fail to migrate. This causes the migration workflow to failed to complete due to the unused TEPs. 

Resolution

This issue is resolved in VMware NSX Data Center 3.2.1, available at Broadcom downloads.

If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

Workaround

1. Download the file kb397357.tgz attached here and upload to the /tmp dir of any NSX Manager node.
2. SSH into the NSX Manager node.
3. Check if dir "/var/log/migration-coordinator/v2t" exists by executing:
   ls -l /var/log/migration-coordinator/v2t
4. If it does not exist, create the dir by running:
   mkdir /var/log/migration-coordinator/v2t
5. Navigate to the directory by executing:
   cd /opt/vmware/migration-coordinator-tomcat/bin/v2t/config-migrator/
6. Extract the file by running:
   tar -xvzf /tmp/kb397357.tgz
7. Change the permissions by executing:
   chown -R umc:umc *
8. Run the script by executing:
   python3 main.py -c sandbox/config.json -s finalize-infra runtime