Before VXLAN gained mass adoption, vCloud Director relied on vCloud network isolation (VCDNI) technology to provide network isolation for virtual machines. Beginning with vCloud Director 8.10, support for VCDNI networks has been deprecated in favor of the VXLAN standard, which provides equivalent isolation capabilities and many additional features. Service providers are encouraged to migrate their legacy VCDNI networks to VXLAN technology. vCloud Director 8.20 automates this migration on a per-network-pool basis. This is a simple, one-button process. To ensure a smooth migration, take a few minutes to understand your existing VCDNI networks and the VMs that connect to them.
IMPORTANT: This migration is not supported for VCDNI network pools hosted on vSphere 6.5. After you upgrade vCloud Director to 8.20, complete this migration before you upgrade any attached vCenter servers to vSphere 6.5.
Migration is enabled in the vCloud Director Web Console by a button labeled Migrate to VXLAN on the Network tab of the Organization VDC Properties page. In the vCloud API, migration is enabled by a POST request to the migrateVcdniToVxlan link in the VDC. The button and link do not appear if the organization VDC does not contain any VCDNI networks.
Internally, the migration workflow follows these steps: