The previous VMware Cloud Director 10.2 release brought many new networking features, the current one 10.3 continuous in the same fashion. Let me give you a brief run down.
The UI has been enhanced to surface formerly API only features such as the ability to configure dual stack IPv4/IPv6 networks:
or configure DHCP in gateway or network mode:
The service provider can now assign/change primary IP address of Org VDC Edge Gateway in the UI:
It is also possible to configure (extend) an external network port group backing without using API.
New NSX-T Backed Provider VDC Features
As NSX-T backed PVDCs now support both Tier-0/VRF and port group backing for external networks, to avoid confusion the Tier-0/VRF GWs were separated into its own tab.
The port group backed external networks can be either traditional VDS port groups, or NSX-T segments. The latter option gives the ability to use NSX-T distributed firewall on such external network (provider managed directly in NSX-T).
Distributed Firewall now supports dynamic groups that can be defined utilizing VM Tag or VM name.
vApps support routed vApp networks including DHCP service on vApp isolated networks. This is achieved by deploying standalone Tier-1 GWs that are connected to Org VDC networks via service interface. The Org VDC network must be overlay backed (not VLAN). vApp fencing is still not supported as NSX-T does not provide this functionality.
A few additional small enhancements ranging from support for Guest VLAN tagging, reflexive NAT to DHCP pool management.
Provider VDC with no NSX
The creation of Provider VDC does not require network pool specification anymore. Such PVDC will thus not provide any NSX-V or T features (routing, DHCP, firewalling, load balancing). The Org VDC network can than be backed by VLAN network pool or use VDS backed
imported direct networks.
NSX-V vs NSX-T Feature Parity
Let me conclude with traditional NSX-V / NSX-T VCD feature comparison chart (new updates highlighted in green).