VCF 5.1 provides the ability to fully separate VxRail system traffic and NSX traffic for both the management WLD and VI WLD using a secondary system vDS along with a third vDS which can be dedicated for NSX traffic. For the management WLD, additional inputs would be required in the deployment parameter sheet. Cloud Builder can create a third vDS during VCF bring-up allowing the ability to have two system vDS and an NSX dedicated overlay vDS. When deploying CB using a two system vDS VxRail Manager should create the system vDSs during the first run. With VCF 5.1 each vDS created must have a Transport Zone Type assigned to it defined in the input parameter sheet. Zone type can be either VLAN, Overlay or both. This supports new functionality allowing NSX DFW rules to be applied to the System VLAN Portgroups. In VCF 5.1 the VI WLD, SDDC Manager UI now supports creating VxRail VI workload domains using an advanced NIC profile allowing to have a total of three vDSs per cluster. Between the three only a single vDS can support NSX overlay traffic. Workflow Optimization support now has feature parity between WFO UI and WFO script, as shown in the following table.

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.

Table 8.      Workflow optimization support