Multi-VTEP with Route Based on Originating Port ID

Most people would avoid link aggregation to ESXi hosts and let vSphere handle the teaming and load balancing, such as using a route based on a physical NIC load (LBT). Unfortunately, VMware NSX does not support LBT. Therefore, the other option is to use route based on the originating port ID with multiple VTEPs.

Route based on the originating port ID does not require any special configuration, such as link aggregation or LACP, in the physical network. VTEPs will be created according to the number of vDS uplinks; if the vDS has four uplinks, four VTEPs will be created even if there are only two vmnics attached. For this reason, it is important to have the number of vDS uplinks matching the number of actual vmnics in the vDS.

Route based on the source MAC hash does the same job, but it uses extra CPU cycles to compute the MAC address hash for every packet. For this reason, a route based on the originating port ID is recommended over a route based on the source MAC hash.