Architecting VMware vSAN 6.2 : vSAN Design Overview : 5.6 vSAN Requirements : 5.6.4 Network Requirements : 5.6.4.9 Networking Failover, Load Balancing and Teaming Considerations
   
5.6.4.9 Networking Failover, Load Balancing and Teaming Considerations
Business continuity and disaster recovery (BCDR) is critical in any environment in case of a network failure. vSAN supports teaming configurations for network cards to enhance the availability and redundancy of the network.
Note vSAN does not currently leverage teaming of network adapters for the purpose of bandwidth aggregation and load balancing to enhance performance.
For a predictable level of performance with the use of multiple adapters, configure each adapter with the following teaming algorithms:
Route based on originating virtual port – Active/Passive failover configuration of adapters in the team.
Route based on IP hash – Active/Active failover configuration with:
o Static EtherChannel for standard switches.
o Link Aggregation Control Protocol (LACP) port channel for vSphere distributed switches.
Route based on physical network adapter load – Active/Active failover configuration with LACP port channel for distributed switches. Unavailable for standard switches.
Typically, VMware recommends that configurations use an Active/Active redundancy with a route based on physical adapter load for the teaming in the environment. In this configuration, idle network cards do not wait for a failure to occur. This assumes that LACP has been, or can be, configured in the environment.