"Edge node(s) are not deployed on v-cluster on vCenter" when using vcdNSXMigrator.py script to migrate from NSX for vSphere to NSX-T with vCD

Products

• VMware NSX

Issue/Introduction

• During the precheck phase of the tool, it fails with ERROR:

[vcdNSXMigratorAssessmentMode]:[updateInventoryLogs]:460 [ERROR] [MainThread] | Assessment mode for NSX-V migration to NSX-T failed
[vcdNSXMigratorAssessmentMode]:[updateInventoryLogs]:461 [ERROR] [MainThread] | Check <apth-to-file>ORG-NSX-VCD-NSX-Migrator-preCheck-Summary-<date/time>.log file for failed validations.

• Checking the file ORG-NSX-VCD-NSX-Migrator-preCheck-Summary-<date/time>.log you see the following:

| Validating whether the edge transport nodes are deployed on v-cluster or not | Edge Transport Node/s - 'Edge-05, ...' are not deployed on v-cluster on vCenter - <vCenter FQDN> | Failed |

• The edge node where deployed in the NSX UI with a resource group.

Environment

VMware NSX

VMware vCloud Director

Cause

There appears to be a validation requirement in the script, that the edge node(s) be deployed on clusters and not assigned to a resource pool, the issue occurs when the edge node(s) are deployed and a resource group is assigned during deployment.

Resolution

1. The following API can be used to determine if a resource pool was used, when deploying the edge node(s):
   GET /api/v1/transport-nodes
2. Look for the edge node(s) that the script is erroring out on in the GET API results, check the 'vm_deployment_config' details, it should say 'domain-#####' for the 'compute_id', like below:
   ...
"vc_id" : "f2e9bbe1-####-####-####-6fa1f5247c25",
"compute_id" : "domain-c######",
"storage_id" : "datastore-##",
"management_network_id" : "dvportgroup-##",
...
3. If it was a resource pool, it would look like:
   ...
"vc_id" : "f2e9bbe1-####-####-####-6fa1f5247c25",
"compute_id" : resgroup-######,
"storage_id" : "datastore-##",
"management_network_id" : "dvportgroup-##",
...
4. Redeploy the edge node(s) using a cluster and not a resource pool and rerun the script.

Note: This is an issue with the script, not within the NSX product, this script is no longer supported by Broadcom.