vCloud Director is able to create isolated or routed layer 2 networks within Organizations or vApps on the fly thanks to network pools. The network pools can be port group backed (pre-defined portgroups on static or distributed vSwitch), VLAN backed or isolated byVMware proprietary MAC-in-MAC encapsulation called vCloud Director Network Isolation (VCDNI). Every time an isolated or routed layer 2 network has to be created it is taken from the network pool. In the case of port group backed network pool one pre-defined portgroup is used from the pool. However in the VLAN or VCDNI backed pool a new port group is created on vDSwitch automatically by vCloud Director. There is one important aspect: there is no way to specify security and NIC teaming policy for such portgroup.
VLAN backed portgroup is always using “route based on originating virtual port” teaming policy and all vDSwitch uplinks are set as active.
VCDNI backed portgroup is also always using the same load balancing policy however only one uplink is active and all the others are put into standby mode.
This means that all the uplinks on the vDSwitch which is used for the VLAN or VCDNI network pools have to be compatible. This means they should have the same VLAN trunks defined on the physical switch ports in the case of VLAN backing or the same transport VLAN defined in the case of VCDNI. It is not possible to reserve some uplinks for vMotion or management as is often the case.
If vMotion or management or any other traffic separation is required then these uplinks have to be on a separate static or distributed switch not used for network pools. Otherwise vCloud Director could use such incompatible uplink and since the VLAN is not defined on the physical switch the network traffic will get rejected.