cloud1~cloud9 not working...

[qqxk]

EVE is fantastic! I love it.
I encountered the following issue, please help:

My EVE is installed on esxi 6.5 and some other vm running on the esxi server as well.
I have vswitch0 to NIC1 and 2 port groups using this vswitch:
#1: port group named VM Mgmt, vlan id = 10
#2: port group named vlan20, vlan id = 20

I mapped these 2 port groups to EVE 2 vmnet： vmnet1 and vmnet2.
router1 connected to cloud0 which is working fine.
router2 connected to cloud2 (or cloud1), router 2 couldn't reach the vms using port group vlan20 (cloud1 and cloud2 both failed).

How I should configure esxi or EVE or vm in order to make cloud1/cloud2 work?

Thanks for your help in advance.

[ramindia]

EVE is fantastic! I love it.
I encountered the following issue, please help:

My EVE is installed on esxi 6.5 and some other vm running on the esxi server as well.
I have vswitch0 to NIC1 and 2 port groups using this vswitch:
#1: port group named VM Mgmt, vlan id = 10
#2: port group named vlan20, vlan id = 20

I mapped these 2 port groups to EVE 2 vmnet： vmnet1 and vmnet2.
router1 connected to cloud0 which is working fine.
router2 connected to cloud2 (or cloud1), router 2 couldn't reach the vms using port group vlan20 (cloud1 and cloud2 both failed).

How I should configure esxi or EVE or vm in order to make cloud1/cloud2 work?

Thanks for your help in advance.

Paste your Vswitch config, and EVE-NG Interface mapping.
also ifconfig output of EVE-NG to understand

R!

[Uldis (UD)]

We found this glitch,

Adding new VMNET interface on eve, it becomes as eth1, second interface after mgmt.
And all existing cloud interfaces move one step down
cloud1 becomes as cloud2, before cloud1 corresponding vmane1, now is Cloud2...
and your binding
So we will do workarround for this.
Please patience.
Problem is that adding new interface on esxi it mess corresponding cloudX to vmnetx

will come back shortly

UD

[ecze]

It is a esxi issue...
EVE-NG doesn't manage interface order.
Order is 'natural' using PCI.Id

A manual setting in esxi is necessary to force using a good PIC.iD

E.

[qqxk]

It is a esxi issue...
EVE-NG doesn't manage interface order.
Order is 'natural' using PCI.Id

A manual setting in esxi is necessary to force using a good PIC.iD

E.

Is that possible to provide a solution, either on esxi or anywhere else?
Thanks!!

[qqxk]

We found this glitch,

Adding new VMNET interface on eve, it becomes as eth1, second interface after mgmt.
And all existing cloud interfaces move one step down
cloud1 becomes as cloud2, before cloud1 corresponding vmane1, now is Cloud2...
and your binding
So we will do workarround for this.
Please patience.
Problem is that adding new interface on esxi it mess corresponding cloudX to vmnetx

will come back shortly

UD

I watch a youtube video and it seems the cloud1~9 works on the vm running on vmware workstation. Is there any workaound to fix the problem, even it's a bit dirty?
Thanks.

[Uldis (UD)]

it is esxi related, VM ware did bad, organizing order of interfaces..
we looking how to fix

no workarround here, known esxi bug
https://communities.vmware.com/thread/484245

VM ware saying PLAN your interfaces at the begin !!!