VMware vCloud Director networks

Users of the platform can work with VMware vCloud Director networks as follows:

• Manage private networks

  • vApp networks, which may be isolated or have an external connection

• Synchronize these external networks:

  • External networks outside the Org VDC but connected to the Edge, for use by load balancers but not VM vNICs

  • External networks outside the Org VDC with a direct connection to OrgVDC as OrgVDCNetwork

  • Isolated Org VDC networks, for use by VM vNICs but not load balancers

• Synchronize and create and delete these external networks in the Virtual datacenters view

  • OrgVDC networks inside the OrgVDC and routed through the Edge

Configure external connections for private networks

• For private networks, the property "vcd.parentnetwork" will determine if there is a connection to allow outgoing traffic. This can be set for the platform and the enterprise. The value can be any existing orgNetwork name or "none" for isolated private networks. The default value is "edge-uplink", which uses the external network connected to the orgVdc Edge gateway.

• If you configure a parent network, then by default, the platform will fence the VCD vApp, which means that the configuration is "natrouted" and VCD will retain the IP and MAC addresses of the Edge gateway across deployments.

• To prevent the platform from creating fenced VCD vApps, set the "vcd.fenceVapp" property to false on the Remote Services server.

Onboarding external networks

• In VCD when you create an external network that can support load balancers (direct or routed), you must create a static IP pool with the number of IP addresses to reserve for load balancers. The platform uses a configuration property to set the number of addresses to reserve for load balancers. If you do not create the static IP pool, the platform will onboard the network but you cannot use it for load balancers. The number of static IPs reserved for load balancers is also a limit on the number of load balancers that users can create in a network.

Administrators can create NAT networks for public cloud regions and users can manage NAT rules for their VMs. The platform does not discover or onboard NAT networks.

The platform does not onboard or manage static routes for VCD networks.