VasanthanB
Contributor
Contributor

VCF4.3(on VxRail) CloudBuilderVM thrown error as"All provided vmnics do not map on VDS

Is there any difference between VCF 4.2 vs 4.3 deployment?.

I was following same method of VCF 4.2 method(with revised worksheet parameter as per VCF4.3 expectation),But i'm getting below error in builder VM JSON spec validation step

"All provided vmnics [vmnic0, vmnic1, vmnic2, vmnic3] do not map to same port group of VDS m01-vds01"

My deployment on VCF on VxRail 7.0.202 with 4 NIC deployment.

 

 

 

0 Kudos
5 Replies
shank89
Expert
Expert

What vds profile are you using, can you share pictures or the spreadsheet?

Shashank Mohan

VCAP-NV 2020 | VCP-DCV2019 | CCNP Specialist

https://lab2prod.com.au
0 Kudos
VasanthanB
Contributor
Contributor

Thanks for looking on this.

VCF on VxRail worksheet (VCF4.3) doesnot have option to choose vds profile option(This was missing in VCF4.3)

vcf.jpg

 

0 Kudos
shank89
Expert
Expert

Can you have a look what your excel spreadsheet looks like in JSON? 

https://my-cloudy-world.com/2021/08/26/vmware-cloud-foundation-manually-generating-the-json-using-de...

Shashank Mohan

VCAP-NV 2020 | VCP-DCV2019 | CCNP Specialist

https://lab2prod.com.au
cathalp
Contributor
Contributor

There is a change in VCF 4.3 for VxRail, the vmnics provided need to map to uplinks used for one of these three system traffic dPGs..

Management

vSAN

vMotion

In VCF 4.2 it defaulted to the Mgmt dPG uplinks, regardless of the values provided for the VxRail system vDS in the input spreadsheet.

VxRail will use just two uplinks for these types of traffic by default so you need to decide what two uplinks in the Mgmt WLD you want to use for NSX-T traffic.

So in your input spreadsheet you need to select two vmnics associated with uplinks for either Mgmt, vSAN or vMotion.

VasanthanB
Contributor
Contributor

Thanks for your input @cathalp ,Let me try on 2 dedicated vmnic for NSX-T traffic.

0 Kudos