I need to bring up a Workload domain that is configured with two network cards. Each one has 2 ports. For redundancy purposes and for old legacy networking practices:
Card 1 port 1 - vmnic0 attached to Switch A - vSAN, vMotion, ESXI, NSX-T
Card 1 port 2 - vmnic1 attached to Switch B - Workload vLANs
Card 2 port 1 - vmnic2 attached to Switch A - vSAN, vMotion, ESXI, NSX-T
Card 2 port 2 - vmnic3 attached to Switch B - Workload vLANs
I am using the APIs to create a Workload domain and was wonder how I script it to use vmnic0 and vmnic2 instead of vmnic0 and vmnic1. Is it done under the hostNetworkSpec? If so, what value do I put in for moveToNvds?
"hostSpecs": [
{
"id": "***host id***",
"licenseKey":"LICENSE_KEY",
"hostNetworkSpec": {
"vmNics": [
{
"id": "vmnic0",
"vdsName": "VDS01",
"moveToNvds": true
},
{
"id": "vmnic1",
"vdsName": "VDS02"
"moveToNvds": false
},
{
"id": "vmnic2",
"vdsName": "VDS01"
"moveToNvds": true
},
{
"id": "vmnic3",
"vdsName": "VDS02"
"moveToNvds": false
}
]
}
},
Any help would be appreciated. Hoping that I am not going to far down the wrong path to resolve the issue, so I am asking for directions 🙂
Ok, if I am reading it correctly, then I would need something akin to this:
"vdsSpecs": [ {
"isUsedByNsxt": true,
"name": "VDS01",
"portGroupSpecs": [ {
"name": "VDS01-pg-mgmt",
"transportType": "MANAGEMENT"
},
{
"name": "VDS01-pg-vsan",
"transportType": "VSAN"
},
{
"name": "VDS01-pg-vmotion",
"transportType": "VMOTION"
} ]
} ]
At which point the ""isUsedByNsxt": true," flag would place the NSX-T configuration on this vDS as well. VDS01 would carry vMotion, vSAN, ESXI Management, and NSX-T. For the hostNetworkSpec, can it IGNORE vmnics or does each one have to be assigned a vDS and port group configuration?
Configuration 1: vmnic1 and vmnic3 to carry VM Workloads
"vmNics": [
{
"id": "vmnic0",
"vdsName": "VDS01",
"moveToNvds": true
},
{
"id": "vmnic1",
"vdsName": "VDS02",
"moveToNvds": false
},
{
"id": "vmnic2",
"vdsName": "VDS01",
"moveToNvds": true
},
{
"id": "vmnic3",
"vdsName": "VDS02",
"moveToNvds": false
}
]
Configuration 2: Can we bypass configuring vmnic1 and vmnic3 and configure the vDS later?
"vmNics": [
{
"id": "vmnic0",
"vdsName": "VDS01",
"moveToNvds": true
},
{
"id": "vmnic2",
"vdsName": "VDS01",
"moveToNvds": true
}
]
This turned out to be a valid way to create the workload domain using vmnic0 and 2 instead of 0 and 1:
"vmNics": [
{
"id": "vmnic0",
"vdsName": "VDS01",
},
{
"id": "vmnic2",
"vdsName": "VDS01",
}
]
I am not sure what the moveToNvds does and how it is used if I want to create the VM workload vDS during the bring up. I am assuming that the NSX-T configurations will automatically attach to VDS01 because it is declared with the "isUsedByNsxt".
movetonvds is legacy and no longer required. The IsUsedbyNSXT stipulates which VDS to use for NSX-T.
I appreciate that information!
I left it out during the bring up, good to now it is not required for something this simple.