Copy&Past from NSX Design Guide Page 74:
• VDS offers great flexibility for what concerns uplinks connectivity. Every port-group defined as part of a VDS could,
in principle, make use of a different teaming option, depending on the requirements of the traffic associated to that
specific port-group.
• The teaming option associated to a given port-group must be the same for all the ESXi hosts connected to that
specific VDS (even if belonging to separate clusters). Still referring to the case of the VXLAN transport port-group,
if the LACP teaming option is chosen for the ESXi hosts part of compute cluster 1, this same option must be
applied to all the other compute clusters connected to the same VDS. Trying to choose a different teaming option
for a different cluster would not be accepted and will trigger an error message at the time of VXLAN provisioning.
• If LACP or Static EtherChannel is selected as the teaming option for VXLAN traffic for clusters belonging to a given
VDS, then the same option should be used for all the other port-groups (traffic types) defined on the VDS. The
reason is that the ether-channel teaming choice implies a requirement of configuring a port-channel also on the
physical network side. Once the physical ESXi uplinks are bundled in a port-channel on the physical switch (or
switches), using a different teaming method on the host side may result in unpredictable results (and often in loss
of communication).
Teaming Policy for Virtual Distributed Switches:
You should choose a teaming policy for VXLAN transport based on the topology of your physical switches. It is recommended that you do not mix teaming policies for different portgroups on a vSphere Distributed Switch. If uplinks are shared in these different teaming policies, then traffic will be interrupted. For a Logical Distributed Router, mixed teaming policies may result in routing problems. As a best practice - if you want to use IP hash based teaming (Ether channel, LACPv1, or LACPv2), use all uplinks on the vSphere Distributed Switch for the team and do not have portgroups on that vSphere Distributed Switch with different teaming policies.