VCD operations on vCenter

Things to do on vSPhere with respect to VCD:-

• Increase the port from 128 to 4096 this will require a reboot.
• Use ephemeral binding so that ports are crated and destroyed when not needed.
• ephemeral binding "ephemeral-no binding on switch " should be manually set if you are using port group backed , for Vlan backed this is automatically set by VCD.

When a vAPP is powered on

1. vCenter server creates a port group for its vAPP networks.
2. vShield Edge device is deployed
3. vApp is connected to its assigned network.

VCD Network Pools

Network pool :-
A Network pool is a predefined collection of vsphere network resources that can be used by
vcloud director to dynamically create a limited number of organization and app networks.

Network pool consists of : Vlan ID,Port groups,virtual network switches and VCDNI networks

1. Each  Org vDC can only be assigned one network pool
2. single network pool can be used by mutiple organization vDCs
3. single organization can have multiple organization vDCs and connect to multiple networks pools.

 Network pool  must be one of below :-

1. VLAN backed :-No special MTU (max transfer Unit) settings rout able.v Cloud director creates port groups in vcenter.Vlan trunking must be enabled.Planned VCD VLAN-IDs should be pre-programmed into the physical network switch 
2. VCD-NI backed:-very secure VLAN ID not an issue.MAC to MAC encapsulation.MTU should be increased by 24 bytes for VCD-NI-backed network pools.MTU setting on the physical switch should match virtual switch MTU settings.MTU settings on network pool configuration should also match
3. port-group backed --should preexist
   MTU setting on the physical switch should match virtual switch MTU settings 

External networks do not use network pools because external networks are created by the provider .