Support and News Forum

Hi all
On a Supermicro Server which was running ESXi 6.7 and EVE-NG community last release updated and which was working fine, I reinstalled from scratch an ESXi 7.0 last update with EVE-NG community last release updated and now the dhcp offers are not transmitted to the device inside EVE-NG through the cloud0. With tcpdump on EVE-NG server, we can see the dhcp dialog and their offers, but they never reach the target.
If I set a static IP address on the device inside EVE-NG all is working fine with cloud0.

I have no teaming on the Supermicro server.
I have promiscuous mode enabled on the vswitch.

I tried with the last GNS3 VM with web interface and this is the same behavior, so the issue is not on EVE-NG, but I do not find anything on the web to explain this issue...

If someone had this issue, please share the workaround.
Thank you
Regards

I dont think that Supermicro is in supported ESXi 7.0 servers list mate.
It can be 7.0 unsupported NIC card on your box either

Hi, you are probably right.
Did you plan to support Ubuntu 18.04 with the community edition?
Thanks
Regards

Hi, I think that it's not an ESXi issue.

I had an EVE-NG bare metal that was working fine and that I did not update from at least 8 mounths.
This morning I did an "apt update" and "apt upgrade" and now I have the same behavior, the dhcp offers are not transmitted to the devices in the lab.

Thanks
Regards

Regarding network and NICs we did not touch EVE, so newest version has same as before. EVE Community for sure

Hi, I just found my issue one hour ago.

After testing the same behavior on:

- an ESXi 7.0b
- a bare metal
- a MacBook pro with Fusion pro

The only common item was that I quick checked with a VPCS, and the issue was the VPCS. Using a virtual switch it works fine on the ESXi 7.0b.

It looks like VPCS is unable to complete the dhcp dialog...

Thanks
Regards

OH man,
VCPS is known buggy thing, I even think remove it from EVE at all...
VPCS is useful only as small host respond to IP, and only if it is connected to node.
Strictly do not use connect VPCS to the cloud !!!!

Ok thanks, I never use the VPCS but I had the bad idea to use it to quick check my new configuration...
Sorry