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.
UI Enhancements
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).
Tom Fojta's Blog 
Hi Tom, I cannot work out from the matrix if federated NSX-T with spanned segments is supported yet? Could you clarify? Thx Pin.
Not yet.
😦 Thanks for clarifying Tom… I appreciate its a ‘futures’ conversation, but can you allude if this is planned for a future 10.x minor release or if it’s likely to be held up until the next major release (i.e 11.x / 12.x)?
Tomas,
Thank you so much for this blog and the feedback that you’re provided me in the past.
Have you published a list of Cloud Director functionality that is API only? Or can you point me to a reference?
I extend features from Cloud Director 10.2 using the API. I duplicate some functions in the process, but don’t have a grip on the specific API only features. I know there some branding and multisite calls that I’ve used, and I don’t believe are built-in. Thank you, again.
I am not aware of such list.
Thank you for the post. Question regarding upgrades. Having followed the below instructions to upgrade from 10.1 appliance with embedded postgres to 10.2 (download and install update package on all cells, backup and upgrade DB, restart all cells), can i follow the same instructions to upgrade from 10.2 to 10.3?
https://docs.vmware.com/en/VMware-Cloud-Director/10.0/com.vmware.vcloud.install.doc/GUID-BE64E6B6-EEB5-40FD-8797-45EF62854C06.html
https://docs.vmware.com/en/VMware-Cloud-Director/10.3/VMware-Cloud-Director-Install-Configure-Upgrade-Guide/GUID-BC45668F-83B4-4FC9-9E2D-025AA82B61DF.html
Hi Tomas,
May I missed that, but which NSX–T version is required to use this new VCD 10.3 feature?
https://interopmatrix.vmware.com/#/Interoperability?isHideGenSupported=true&isHideTechSupported=true&isHideCompatible=false&isHideIncompatible=false&isHideNTCompatible=false&isHideNotSupported=true&isCollection=false&col=661,5317&row=175,5755,5458,4926,4090,5371,4729,4198,3413,5316,4232,3787,3394,3777,3645,3451,2852,3216,2714,2595,2526,2176,1689
I have created a PVDC without network pool. When I created OrgvDC network, I can’t find the option of “Imported” as stated in the section of PVDC with no NSX
Currently you can use only direct networks (or VLAN network pool backed routed/isolated) networks in VDC without NSX.