If a single vDS is used for the deployment all system traffic and NSX traffic will share the same vDS, there are four options for the deployment, two uplinks with 2x10GbE, two uplinks with 2x 25GbE, four uplinks with 4x10 and now four uplinks with 4x25 profiles. A 2-uplink profile can either be 2x10 or 2x25. The following diagram illustrates the connectivity and teaming configuration for the VxRail vDS used for system traffic and NSX traffic with either 2x10 or 2x25 profile.

Note: There is an issue in VCF 4.0.0/4.0.1 where the edge uplinks distributed port groups are not configured during deployment and left in Active/Unused configuration. In certain failure scenarios where connectivity is lost to Active T1, all traffic to and from the segments connecting the T1 could be dropped. A manual step is needed to configure the port groups as Active or Standby after deployment. This impacts Mgmt WLD with AVN enabled or the Edge cluster deployment using Edge Automation from SDDC Manager. This issue is resolved in 4.1 as the uplink port groups are configured as Active/Standby.

Figure 13.          Single VxRail vDS with NSX traffic and two uplinks

Figure 14.          Single VxRail vDS with NSX traffic and four 10GbE uplinks

This final diagram illustrates the new 4x25 profile that is introduced in VxRail version 7.0.100. It uses both an NDC and PCIe to achieve NIC level redundancy.

Figure 15.          Single VxRail vDS with NSX traffic and four 25GbE uplinks