At the time of initial implementation, you will have the option to select and assign the teaming and failover policy on each portgroup for each required VxRail network. The following load-balancing policies are supported for VxRail clusters:
- Route based on the originating virtual port ̶̶ After the virtual distributed switch selects an uplink for a virtual machine or VMkernel adapter, it always forwards traffic through the same uplink. This option makes a simple selection based on the available physical uplinks. However, 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 virtual machine based on the virtual machine MAC address. While it requires more resources than using the originating virtual port, it 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, as this policy has a dependency on the logical link setting of the physical port adapters on the switch.
VxRail applies a default teaming and failover policy configuration based on the following rules:
- If the teaming policy is set to ‘Active-Active’, the default load balance policy set by VxRail is: Route based on physical NIC load.
- If the teaming policy is set to ‘Active-Standby’, the default load balance policy set by VxRail is: Route based on originating virtual port.