By using the VMware Cloud Foundation API, you can deploy an example workload domain with 4 physical NICs per host.
In VMware Cloud Foundation 3.10, you can use the SDDC Manager public API to automate multiple physical NIC configurations when using for NSX-T.
In this example workload domain, for traffic separation, one vSphere Distributed Switch handles the system traffic for vSphere management, vSphere vMotion, and vSAN in the initial cluster of the example workload domain and one N-VDS handles the workload traffic, for example, NSX-T overlay. You assign a pair of physical NICs to each switch.
Component |
Value |
|
---|---|---|
SDDC Manager FQDN |
sfo01m01sddc01.sfo01.rainpole.local |
|
Workload domain name | sfo01-w01 | |
vCenter Server FQDN |
sfo01w01vc01.sfo01.rainpole.local |
|
Number of hosts |
4 |
|
Cluster name |
sfo01-w01-cl01 |
|
Number of physical NICs per host |
4 |
|
vSphere Distributed Switch configuration |
vSphere Distributed Switch instances |
sfo01-w01-c01-vds01 |
vmnic configuration for vSphere Distributed Switch sfo01-w01-c01-vds01 |
vmnic0, vmnic1 |
|
NIC teaming policy for vSphere Distributed Switch sfo01-w01-c01-vds02 |
Route based on physical NIC load (default) |
|
Distributed port groups for vSphere Distributed Switch sfo01-w01-c01-vds02 |
|
|
NSX-T Manager configuration |
NSX-T Manager VIP FQDN |
sfo01wnsx01.sfo01.rainpole.local |
NSX-T Manager member FQDNs |
|
|
N-VDS configuration |
N-VDS instance |
Auto-generated name |
vmnic configuration for N-VDS |
vmnic2, vmnic3 |
|
Uplink Profile Teaming Policy |
Load Balance Source that is, load balancing between uplink-1 and uplink-2 based on the source port ID |
|
Traffic Segments |
Overlay |
|
Storage type |
vSAN |