NVDS to CVDS migration issues - Transport node Id's not seen in migration topology

Products

• VMware NSX

Issue/Introduction

- Few hosts out of all the other hosts in the cluster are not able to be migrated from NVDS to CVDS

- These hosts are added to the cluster after the NSX upgrades from 3.1 to 3.2.3.1 and while prechecks are still active

- While doing the NVDS to CVDS migration using API option Step 6 (reference: https://techdocs.broadcom.com/us/en/vmware-cis/nsx/nsxt-dc/3-2/administration-guide/host-switches/migrate-host-switch-to-vsphere-distributed-switch.html)

       --> The pre-check will build a recommended migration topology based on the discovered v-NDS switches and host states. Use the following command to view the recommended topology:

curl -k -n -X GET https://nsx-l-01a/api/v1/nvds-urt/topology/<Precheck-ID>

      --> The output of the above API doesn't show those the transport node IDs of few hosts that were moved into the cluster when prechecks were still active while performing the NSX upgrade

Environment

VMware NSX-T Data Center

Resolution

Workaround:

1. Uninstall the NSX from these hosts (reference: https://techdocs.broadcom.com/us/en/vmware-cis/nsx/nsxt-dc/3-2/installation-guide/uninstall-nsx-from-a-host-transport-node.html)

2. Add the new VDS that was created on to these hosts (reference: https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/vsphere-networking-7-0/basic-networking-with-vnetwork-distributed-switches/manage-networking-on-multiple-hosts-on-a-vsphere-distributed-switch/adding-hosts-to-a-vsphere-distributed-switch.html)

3. Once the VDS is added, from NSX UI, configure the NSX by selecting the VDS under the Host switch and configure the transport node (reference: https://techdocs.broadcom.com/us/en/vmware-cis/nsx/nsxt-dc/3-2/installation-guide/host-transport-nodes/preparing-esxi-hosts-as-transport-nodes/prepare-esxi-cluster-hosts-as-transport-nodes.html)