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. This configuration is also used for the vCenter Server network where the VxRail Manager is connected. The vSAN, vMotion, and external management (vSphere) network use load-based teaming policy.

VxRail has several predefined network profiles that can be used to deploy the VxRail in various configurations depending on the required network design and the physical networking requirements. The following tables show the teaming policies for each port group for a VxRail deployed with a predefined 2x10 or 2x25 GbE network profile:

Table 1.   Predefined 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. The following table shows the teaming policy for each port group that is created with the predefined 4x10 profile:

Table 2.   Predefined 4x10 profile

Finally, VxRail version 7.0.100 introduced a new 4x25 profile, which is available with the following network layout:

Table 3.      Predefined 4x25 profile

VxRail 7.0.130 introduced a feature that allows you to create custom profiles. With this feature, you can essentially select what uplinks/vmnics pairings to use for each type of system traffic. For more details about custom profiles, see VxRail vDS and custom profiles.