There is a mixture of teaming algorithms for the port groups on the vDS. The VxRail management network that is used for node discovery uses route-based on the originating virtual port with one active and one standby adapter. The vSAN, vMotion, and external management (vSphere) network use load-based teaming policy. NSX-V VTEP does not support load-based teaming so this is also created with route-based on the originating virtual port. Finally, the NSX-V ESG port groups are created with just one active uplink that is pinned to each physical vmnic. The following table shows the teaming policies for each port group for a VxRail deployed with 2x10 or 2x25 GbE profile.

Port Group teaming policy for 2x10 or 2x25 GbE profile

You can also deploy a VxRail cluster with a 4x10 network profile for either a Mgmt WLD or a VI WLD. This is not the VVD standard, but it is permitted for VCF on VxRail. The following table shows the teaming policy for each port group that is created with this profile.

Port Group teaming policy for 4x10 profile

Note: The NSX-V deployment uses vmnic2 and vmnic3 on the vDS for the VTEPs so VXLAN traffic is mixed with vSAN and vMotion. As a day 2 operation, you can move this traffic to vmnic0/vmnic1, if desired, to keep this traffic separate from vSAN.