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 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.