I'm planning to upgrade VMware Cloud Director to version 10.6.1.1.
Since NSX-V is currently deployed in our environment, we are also considering a migration to NSX-T.
The versions of the products currently in use are as follows:
・VMware Cloud Director 10.4.1 (Initially deployed as version 5.x, currently using the appliance version)
・vCenter 7.0u3 (Initially deployed as version 5.5u2)
・ESXi 7.0u3
・NSX-V Manager 6.4.14 (Initially deployed as vShield Manager 5.5u2)
The current environment is as follows:
・NSX-V was introduced solely for use with Cloud Director, and only NSX Manager has been deployed.
・On the vSphere side, none of the NSX networking features such as Edge or Distributed Firewall are being used.
・On the Director side, neither Edge Gateway nor Provider Gateway is being used.
・All external networks for Organization VDCs created in Director are directly connected to distributed port groups created on the vSphere Distributed Switch.
・When creating each Provider VDC in Director, the option "Create default VXLAN network pool" was selected, resulting in the automatic creation of network pools with the backing type "VXLAN" under cloud resources.
(However, there are currently zero Organization VDCs associated with each network pool.)
・The Organization VDCs under each Provider VDC created above are labeled with the backing type "NSX-V".
Given this usage environment, is a migration to NSX-T even necessary?
If it is possible to eliminate NSX entirely, we would prefer to do so, as we have no plans to use NSX-T features in either vSphere or Director going forward.
If migration is not required, would it be acceptable to simply decommission the NSX-V Manager?
Thank you for your time.