Starting with Cloud Foundation 3.9.1, you can isolate vmkernel traffic (management, vSAN, vMotion, or overlay) across multiple physical NICs (pNICs). You can enable four pnics per host in NSX for vSphere workload domains, and up to six pnics per host in NSX-T workload domains. Each vDS supports two pNICS, so you must define additional vDSes and map traffic per vDS as appropriate. This capability is available for Cloud Foundation 3.9.1 deployments or when upgrading to Cloud Foundation 3.9.1.

You can use hosts with additional pNICs for the following:
  • Management domain (by using these hosts in the Cloud Foundation bring-up process)
  • Creating VI workload domains
  • Adding clusters to the management domain or VI workload domains
  • Adding hosts to a cluster

For multi-pNIC use cases and API examples, see About Using Hosts with Multiple Physical NICs with VMware Cloud Foundation.

You can stretch an NSX for vSphere cluster that contains hosts with multiple pNICs (four pNICs and two vDSes) enabled. An NSX-T cluster with with the following pNIC combinations can be stretched using manual guidance:
  • four pNICs (one vDS and one N-VDS)
  • six pNICs (two vDS and one N-VDS)
For information on stretching an NSX for vSphere cluster, see Stretching Clusters in the VMware Cloud Foundation Operations and Administration Guide. For information on stretching an NSX-T cluster, see About Deployment of VMware NSX-T Workload Domains with Multiple Availability Zones for VMware Cloud Foundation.

Traffic isolation across physical NICs is not supported through the UI. You must enable the additional pNICs on hosts before commissioning them to Cloud Foundation. You can then update the API spec to map traffic flow to reflect your physical topology. For information on using APIs, see VMware Cloud Foundation API Reference Guide.