After successful migration from NSX-V to NSX-T in VMware Cloud Director you might wish to unregister NSX-V Manager and completely delete it from the vCenter. This is not so easy as the whole VCD model was build on the assumption that vCenter Server and NSX-V Manager are tied together and thus retired together as well. This is obviously no longer the case as you can now use NSX-T backed PVDCs or not use NSX at all (new feature as of VCD 10.3).
VMware Cloud Director (version 10.3+) adds API support to unregister NSX-V Manager without removing the vCenter Server. To do so you need to use the OpenAPI PUT VirtualCenter call. You will first have to run GET call with the VC URN to retrieve its current configuration payload, remove the nsxVManager element and then PUT it back.
Example:
GET https://{{host}}/cloudapi/1.0.0/virtualCenters/urn:vcloud:vimserver:cd0471d4-e48f-4669-8852-de1fdd2648aa
Response:
{
"vcId": "urn:vcloud:vimserver:cd0471d4-e48f-4669-8852-de1fdd2648aa",
"name": "vc-01a",
"description": "",
"username": "vcd@vsphere.local",
"password": "******",
"url": "https://vc-01a.corp.local",
"isEnabled": true,
"vsphereWebClientServerUrl": null,
"hasProxy": false,
"rootFolder": null,
"vcNoneNetwork": null,
"tenantVisibleName": "Site A",
"isConnected": true,
"mode": "IAAS",
"listenerState": "CONNECTED",
"clusterHealthStatus": "GREEN",
"vcVersion": "7.0.0",
"buildNumber": null,
"uuid": "1da63a23-534a-4315-b3fa-29873d542ae5",
"nsxVManager": {
"username": "admin",
"password": "******",
"url": "http://192.168.110.24:443",
"softwareVersion": "6.4.8"
},
"proxyConfigurationUrn": null
}
PUT https://{{host}}/cloudapi/1.0.0/virtualCenters/urn:vcloud:vimserver:cd0471d4-e48f-4669-8852-de1fdd2648aa
{
"vcId": "urn:vcloud:vimserver:cd0471d4-e48f-4669-8852-de1fdd2648aa",
"name": "vc-01a",
"description": "",
"username": "vcd@vsphere.local",
"password": "******",
"url": "https://vc-01a.corp.local",
"isEnabled": true,
"vsphereWebClientServerUrl": null,
"hasProxy": false,
"rootFolder": null,
"vcNoneNetwork": null,
"tenantVisibleName": "Site A",
"isConnected": true,
"mode": "IAAS",
"listenerState": "CONNECTED",
"clusterHealthStatus": "GREEN",
"vcVersion": "7.0.0",
"uuid": "1da63a23-534a-4315-b3fa-29873d542ae5",
"proxyConfigurationUrn": null
}
In order for the NSX-V Manager removal to succeed you must make sure that:
- Org VDCs using the vCenter Server do not have any NSX-V objects (VXLAN networks, Edge Gateways, vApp or DHCP Edges)
- Org VDCs using the vCenter Server do not use VXLAN network pool
- There is no VXLAN network pool managed by the to-be-removed NSX-V Manager
If all above is satistfied you will not need to remove existing Provider VDCs (if they were in the past using NSX-V). They will become NSX-less (so you will not be able to use NSX-T objects in them). NSX-T backed PVDCs will not be affected at all.
Tom Fojta's Blog 
Thanks — also works the opposite way, in case you have NSX-T but want to add NSX-V later in your lab.
How do you get the vcURN?
https://developer.vmware.com/apis/1170/vmware-cloud-director/doc/doc/operations/GET-VirtualCenter.html
You can also see it in your browser URL when editing VC in VCD.
hello Tomas,
we are not using any nsx-v feature except distributed firewall that only managed manually from vsphere.
for the vcloud, i unconfigured the cluster from vxlan but the provider network pool is still ‘nsx’ type. the ‘ip pool usage’ is 0%. in this situation, can i remove the nsx-v from vcloud or should i create vlan type network pool and migrate all thenants to it?…..
The VXLAN network pool must be removed from VCD. So you need to remove this network pool from every Org VDC that is configured to use it (even if you did not create any networks from it) and then delete it. You do not need to create VLAN type network pool as Org VDCs can be configured without network pool.
Must the string of stars after “passwordL” be replaced with the real password?
Hi Tomas,
once the Org VDC is detached from NSX-V. Is there a way to attach it to an NSX-T manager through the UI or API?
Yes. You can create new PVDC which is backed by NSX-T Geneve NP and then merge it with NSX-less PVDC. You will then be able to use NSX-T for all the Org VDCs in the merged PVDC.