How to Unregister NSX-V Manager from a VMware Cloud Director Environment.

Products

• VMware Cloud Director

Issue/Introduction

To unregister NSX-V Manager from VMware Cloud Director, follow these step-by-step instructions:

Identify the VirtualCenter (vCenter) URN. You need to know the URN of the vCenter Server that is associated with NSX-V Manager.

1. Login to the Cloud Director UI as a Provider.
2. Open the API Explorer via the Help dropdown.
3. Locate the VirtualCenter section, and perform the GET against the list of vCenters - /1.0.0/virtualCenters/.
4. Locate the vCenter in question and note the Id value returned.
5. Example: urn:vcloud:vimserver:<<UUID>>.

Environment

VMware Cloud Director 10.x

Resolution

By following these steps, you can unregister NSX-V Manager from VMware Cloud Director while keeping the associated vCenter Server intact.

1. Now to remove the NSX Manager, you will need to pull back the JSON details for that specific vCenter.
   1. GET /1.0.0/virtualCenters/{vcUrn}
2. From the response payload obtained in the previous step, remove the "nsxVManager" element. This element contains the configuration details of NSX-V Manager.
3. Update the VirtualCenter configuration: Make a PUT API call to the same endpoint as before (PUT/1.0.0/virtualCenters/{vcUrn}), but this time include the modified configuration payload obtained in the previous step. The payload should not contain the "nsxVManager" element anymore.
4. Check the VMware Cloud Director user interface or API to confirm that NSX-V Manager is successfully unregistered. Ensure that the associated vCenter Server is still connected and functioning properly.
   
   Note:
   Before unregistering NSX-V Manager, ensure that there are no Org VDCs using NSX-V objects (such as VXLAN networks, Edge Gateways, vApps, or DHCP Edges).
   Also, confirm that no Org VDCs are using a VXLAN network pool managed by the NSX-V Manager that will be unregistered.
   
   
   1. If the NSX-V instance no longer exists in the environment, API may fail with errors similar to :
      
      com.vmware.vcloud.api.presentation.service.BadRequestException: Cannot unregister
shield manager because network pools are still backed by it: Network_Pool_Name
[#####-####-####-####] at
com.vmware.vcloud.management.system.SystemServiceImpl.validateSafeToUnregisterS
hieldManader(SvstemServicelmol.iava:1226)
      
      
   2. Similarly, deletion of network pool reported in the error may fail with errors similar to:
      
      l/O error on GET request for "https//NSX_FQDN:443/api/2.0/vdn/scopes/vdnscope-#". No route to host (Host unreachable); nested exception is java.net.NoRouteToHostException: No route to host (Host unreachable)

Database modifications is required to remove stale network pool references from 'network_pool' and it's dependent tables of VCD database. Please raise a support request following  Creating and managing Broadcom support cases and note this Article ID (320502) in the problem description.