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.

For certain teaming modes, VMware software creates multiple VTEPs to load balance traffic among the physical vNICs.

For information on teaming mode descriptions, refer to the VMware vSphere documentation.

Teaming Policy table

Teaming Mode

Multiple VTEPs Created

vDS Version

Ether channel

Note

If you are using blade chassis, validate that it supports ether channel before choosing this teaming mode.

No

5.1 and later

Failover

No

5.1 and later

LACPv1

No

5.1

LACPv2

No

5.5

Source MAC (MAC Hash)

Yes

5.5

Note

LBT mode is not supported.

Logical Distributed Routers have the following teaming policy restrictions:

Source MAC and Source Port teaming policy will work with one VTEP and one active uplink. You can have multiple uplinks with fail-over policy where the other uplinks are in standby state.

Plain VXLAN switching (without Logical Distributed Router) will work with multiple VTEPs and multiple uplinks.

Static Lag and LACP is supported with one VTEP and multiple uplinks.