Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Architecture Guide—VMware Cloud Foundation on VxRail: VCF 4.5 on VxRail 7.0
Executive Summary Architecture Overview Workload Domain Architecture VxRail Virtual Network Architecture
Introduction
VxRail virtual distributed switch (system vDS)
VxRail vDS NIC teaming
Additional VCF NSX networks
VxRail vDS with NSX networks
NSX vDS
Two vDS (system and NSX) network topologies
Network Virtualization NSX-T WLD Design Enabling VCF with Tanzu Features on Workload Domains Physical Network Design Considerations Storage Options Multi-site Design Considerations Operations Management Architecture Life Cycle Management Cloud Management Architecture

NSX vDS

Home > Integrated Products > VxRail > Guides > Architecture Guide—VMware Cloud Foundation on VxRail: VCF 4.5 on VxRail 7.0 > NSX vDS

NSX vDS

  • Starting with VCF 4.0.1, you can fully separate system traffic and NSX-T traffic for both the management WLD and VI WLD using a second vDS dedicated for NSX traffic. For the management WLD, additional optional inputs are required. Cloud Builder creates and configures the second vDS during VCF bring-up. For the VI WLD, a script available in Developer Center in the SDDC Manager must be used to add a VxRail cluster with a second vDS to the VI WLD. The additional input that is needed for the vDS must be provided to the script during execution.

    Note: VCF orders the vmnic to uplink mapping on the vDS lexicographically (lowest to highest), even if the order in the input spreadsheet for the Mgmt WLD or the input to the script in the VI WLD are not ordered lexicographically.