At the time of initial implementation, you can select and assign the teaming and failover policy on each port group for each required VxRail network.
- Route based on the originating virtual port: After the VMware VDS selects an uplink for a VM or VMkernel adapter, it always forwards traffic through the same uplink. This option makes a simple selection based on the available physical uplinks. This policy does not attempt to load balance based on network traffic.
- Route based on source MAC hash: The virtual switch selects an uplink for a VM based on the VM MAC address. This option requires more resources than the originating virtual port, but has more flexibility in uplink selection. This policy does not attempt to load balance based on network traffic analysis.
- Use explicit failover order: Always use the highest order uplink that passes failover detection criteria from the active adapters. No actual load-balancing is performed with this option.
- Route based on physical NIC load: The virtual switch monitors network traffic, and attempts to adjust overloaded uplinks by moving traffic to another uplink. This option does use additional resources to track network traffic.
VxRail does not support the route based on IP hash policy. This policy has a dependency on the logical link setting of the physical port adapters on the switch.
- Active/Active: The default load balance policy set by VxRail is Route based on physical NIC load.
- Active/Standby: The default load balance policy set by VxRail is Route based on originating virtual port.
- Route based on originating virtual port
- Route based on source MAC hash
- Use explicit failover order