NVDS to VDS API migration fails with "####-####-###46b is not a Discovered Node, this API is not supported on it."

Products

• VMware NSX

Issue/Introduction

 

When performing an NVDS to VDS migration using Option 1 as outlined in the NSX-T Administration Guide, the process may fail at Step 10 with the following error:

####-####-###46b is not a Discovered Node, this API is not supported on it.

Despite this failure, checking the topology summary status using the API below shows the host in the UPGRADE_READY state with no reported errors:

GET https://<nsx_manager_ip>/api/v1/nvds-urt/status-summary/<precheck_id>

 

Environment

VMware NSX 3.2.2

Cause

 

Transport Node (TN) updates are failing due to an InvalidOwnerException. This occurs because the Transport Node was originally created by the nsx-t-superuser, but the current update attempt is initiated by the nsx-policy user (typically used by the Transport Node Collection (TNC) Provider).

Since ownership does not match, the update is rejected. As a result, the TNs are not updated with the required EXTRACONFIG profile, which leads to errors when invoking the migrate_to_vds API.

 

Resolution

 

Workaround:

1. Clean up old topology
   Trigger the following API to clean up any existing topology:

POST https://<nsx_manager_ip>/api/v1/nvds-urt?action=cleanup

2. Create a new precheck
   Use the following API to initiate a new precheck. Note the precheck_id from the response:

POST https://<nsx_manager_ip>/api/v1/nvds-urt/precheck

3. Generate URT topology
   Use the precheck_id from Step 2 in the following API to generate the topology:

GET https://<nsx_manager_ip>/api/v1/nvds-urt/topology/<precheck_id>

4. Apply the topology
   Apply the generated topology using the payload received from Step 3 in the Body:

POST https://<nsx_manager_ip>/api/v1/nvds-urt/topology?action=apply

5. Trigger migration for the host
   Use the following API to initiate host migration:

POST https://<nsx_manager_ip>/api/v1/transport-nodes/<tn_id>?action=migrate_to_vds

---

If You Encounter the Following Error:

Error in API /nsxapi/api/v1/infra/sites/default/enforcement-points/default/host-transport-nodes/####-####-###46b?action=migrate_to_vds caused by exception com.vmware.nsx.management.nvdsupgrade.common.exception.NvdsUpgradeException: 
{"moduleName":"NvdsUpgradeUrt Service","errorCode":250052,"errorMessage":"####-####-###46b is not a Discovered Node, this API is not supported on it."}

Follow these additional steps:

6. Reapply the topology
   Reapply the topology using the same payload from Step 3:

POST https://<nsx_manager_ip>/api/v1/nvds-urt/topology?action=apply

7. Retry host migration
   Trigger the migration again using:

POST https://<nsx_manager_ip>/api/v1/transport-nodes/<tn_id>?action=migrate_to_vds

8. Verify upgrade status
   Ensure the upgrade stage has progressed to TN_MIGRATION_COMPLETED:

GET https://<nsx_manager_ip>/api/v1/nvds-urt/status-summary/<precheck_id>

---

Note:
In most cases, Steps 1–5 should be sufficient. If you encounter the error described above, proceed with Steps 6–8.

Additional Information

All versions before and including 3.2.5 can potentially hit this issue.