VCF 4.2.1 - adding WLD to existing MGMT domain - physical nics 0,1 issue

[planglois2020]

VCF MGMT domain install went fine and running well.    As we add WLD,  VCF defaults to nic0,1 which have embedded 1GB nics that are not connected.

We have 25GB nics that fall in nic2,3 - there seems to be no magical way to do this other way than API to run something to reference nic2,3 as nic0,1.

Any idea what this code would look like in API calls?   or any other suggested way - disabling the nics in bios was an option that didn't work.

Thank you! 

[shank89]

Hi

You can try and use the code in this example, change it to suit your needs.

 https://www.lab2prod.com.au/2020/09/vcf-wld-usingapi-multinic.html

You could also use the developer API in sddc manager or look at the vcf API reference guide.

[planglois2020]

Thanks Shank,

I really trying to achieve this before starting the WLD  If I can demonstrate to VCF that my uplinks are Nic2,3 then all is needed.

Let me know what you think.  Thanks Patrick

[shank89]

For a custom NIC mapping, you have to do this at time of validation / creation using a JSON.  I'm not sure what else you require?

[planglois2020]

Finally resolved by mapping vmnics at the host level and pointing connected vmnics 2,3 to 0,1.  Solved and full WLD build was successful.

Thanks for your help!

[shank89]

For future reference, if you wish to use those vmnics instead of the default 0 and 1.. .rather than re-mapping them, build out a custom json, it's much easier and cleaner.