This section illustrates the physical host network connectivity options for different VxRail profiles and connectivity options when only using a dedicated vDS for NSX traffic. The VxRail vDS is only used for system traffic.
The following diagram illustrates a VxRail deployed with 2x10 predefined network profile on the 4-port NDC which aligns to option E in . The remaining two ports are used for the second vDS for the NSX traffic.
The second option is VxRail deployed with a 4x10 predefined network profile consuming all four ports of the NDC. This places vSAN and vMotion onto their own dedicated physical NICs on the NDC. The NSX-T traffic uses a dedicated vDS and uplinks connecting to pNICs on the PCI-E 10 GbE, this aligns to option H in .
The final option for a 10GbE network environment we want to illustrate provides NIC level redundancy across the NDC and PCIe for both system traffic on the VxRail vDS and NSX-T traffic on the dedicated NSX-T vDS. The VxRail is deployed with the custom profile option using one port from NDC and one from PCIe. Similarly, the NSX-T vDS will use a port from each NIC. This aligns to option G in .
The first 25 GbE option shown in the following diagram uses the 2-port 25 GbE NDC for the VxRail vDS. A dedicated vDS is created for the NSX-T traffic using the two ports of the PCI-E card, option F in .
As with the previous option, additional PCIe cards can be added to the node for other traffic, for example, backup, replication, and so on.
The second option requires a total of six 25GbE ports. The VxRail is deployed with the 4x25 custom profile option as previously discussed using the two port NDC. The two port PCIe and the second vDS for NSX-T traffic require an additional 2x25 GbE card. This aligns to option I in .
The following last option provides full NIC level redundancy for both VxRail system traffic and also NSX-T traffic using two NICs NDC and PCIe connected to the TOR switches. The VxRail is deployed with the 2x25 custom profile using a port from NDC and the PCIe. The dedicated vDS for NSX-T traffic uses the remaining free pNIC on each NIC with one interface from each NIC connected to each TOR.