Org VDC registered as NSX-V when backed by a non-NSX Provider VDC

Products

• VMware Cloud Director

Issue/Introduction

• You can see an Org VDC is registered as NSX-V even if is backed by a provider VDC(PVDC) that is not using NSX at all in VMware Cloud Director (VCD).
• When you try to create a new Org VDC using the non NSX backed PVDC, the new Org VDC always gets a backing type as NSX-V in the VCD UI. 

Environment

VMware Cloud Director 10.6.1.2

Cause

This behavior is expected by design in VMware Cloud Director when legacy NSX-V components are still present in the underlying environment.

When an Org VDC is created or updated from a PVDC that has no NSX backing, VCD evaluates the associated vCenter Server instance. If that vCenter Server still has an active registration or remnants of an NSX-V Manager, VCD's network provider resolution logic defaults the Org VDC's backing type to NSX-V.

Resolution

As explained above this is an expected behavior in VCD. If there is an NSX-V Manager registered in VCD with the registered vCenter under which the Prov VDC with no NSX associated is getting its resources, then the Org VDC will get its "Backing Type" =  "NSX-V".

If we want the Org VDCs to be of "Backing Type" = "none" we would need to unregister that NSX-V Manager from VCD, as mentioned in the KB 320502.