4.7.2 Example
This example documents the VCDNI-backed network pool.
The VCDNI-backed network pool example demonstrates how VCDNI networks are created automatically in vSphere and used in vCloud Director.
Figure 20. VCDNI Network Pool Example Configuration
The following are prerequisites:
vSphere Administrator – A virtual distributed vSwitch that is connected to all vSphere (ESXi) hosts that are in the cluster for the underlying p
rovider virtual datacenter.
Network Administrator – All physical switch port uplinks to the distributed vSwitch configured as 802.1Q VLAN Trunk Ports and configured to allow VLAN 20 and VLAN 301.
Cloud Administrator –
vCloud Director VCDNI-
backed n
etwork pool created with VLAN ID 301.
Cloud Administrator – (optional) A vCloud Director external network
(vcd-ext-20),
if external connectivity is needed. Figure 21. VCDNI-Backed Network Pool Creation
Cloud Administrator – Two Organizations (Engineering and QE) provisioned.
Engineering organization
– “High Engineering PAYG” o
rganization virtual datacenter
Network 1 –
“Eng-Ext-Org-Route” organization
virtual datacenter
routed
Engineering organization
– “Default Engineering PAYG” Organization virtual datacenter
Network 2 –
“Eng-Ext-Org-Direct” organization
virtual datacenter
d
irect network
Network 3 –
“vAppNet-ubu1104” vApp network
QE organization
– “High QE PAYG” o
rganization virtual datacenter
Network 4 – “QE-Iso-Org” organization
virtual datacenter
Isolated network
During the creation of an organization virtual datacenter, you can choose the network pool (the VCDNI pool created above) to associate with this virtual datacenter. Multiple organizations and different virtual datacenters within an organization can share the same network pool, but they are assigned separate and isolated networks from the pool.
Table 13. vCloud Director Networks
Network | Network Type | Organization | Organization Virtual Datacenter | Network
Pool | Subnet |
Eng-Ext-Org-Route | Organization virtual datacenter routed | Engineering | High Engineering PAYG | VCDNI pool | 192.168.31.0/24 |
Eng-Ext-Org-Direct | Organization direct | Engineering | Default Engineering PAYG | N/A | 192.168.20.0/24 |
vAppNet_ubu1104 | vApp NAT | Engineering | Default Engineering PAYG | VCDNI pool | 192.168.32.0/24 |
QE-Iso-Org | Organization isolated | QE | High QE PAYG | VCDNI pool | 192.168.33.0/24 |
Table 13 shows that only the d
irect c
onnect organization
virtual datacenter
network does not use a network from the network pool.
Organization d
irect connected networks use a bridged connection from the external network requiring IP configuration on the virtual machines that matches the physical network IP configuration.
After the network pool is created and associated with an organization virtual datacenter the network pools can be consumed. Whenever a routed or isolated organization virtual datacenter or vApp network is created, vCloud Director automatically provisions a port group on dvS01. These port groups are created automatically and do not share the same VLAN (301). However, each port group is treated as a separate Layer 2 network by virtue of the VCDNI technology. The Administrator must define only the IP address settings for this network, as shown in the following figure.
Figure 22. Organization Virtual Datacenter Network – IP Address Settings
The VCDNI-backed network pool example uses the VMware VCDNI filter driver to multiplex an individual VLAN into many separate broadcast domains. The dvSwitch delivers the appropriate Ethernet frames to the appropriate port group based on the match of which vNIC belongs to which port group. For example, a broadcast from a particular vNIC will be delivered only to the other vNICs connected to the same port group even though the other port groups share the same VLAN (301), which is the transport VLAN configured for the VCDNI network pool.
This isolation persists only inside the vSphere boundaries. However it allows isolated communication between vApps connected to the same network pool even if they are on different ESXi hosts in the vSphere cluster.
