The VxRail initial build will apply the load-balancing policy of ‘Failover Order’ for all VxRail network traffic on the Network Daughter Card (NDC) ports, and assign the uplinks to an ‘Active/Standby’ configuration for each traffic type.
Figure 26 Default VxRail teaming and failover policy
Starting with VxRail version 4.7.410, the teaming policy and uplink configuration on the NDC ports can be modified after the VxRail initial build. None of these policy options require any updates to be made to the physical switch configuration to enact. The following load-balancing policies are supported for VxRail clusters running version 4.7.410 or higher:
After the virtual 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.
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.
The virtual switch monitors network traffic, and makes adjustments on 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 there is a dependency on the logical link setting of the physical port adapters on the switch, and link settings such as static port channels, LAGs, and LACP are not supported with VxRail.
The ‘Failover Order’ on the teaming policy can be changed from ‘Active/Standby’ to ‘Active/Active’ after VxRail cluster initial build.