Hello all,
I've been testing ESXi for some weeks now. It's running on consumerclass hardware, Asus P5K, E6650, 4GB ram, Intel "e1000" 82541PI Gbit NIC.
Every couple of minutes i loose all network connectivity the ESXi host (and my VM's, my infrastructure client, etc).£
The only solution is to reboot the network managment,
and sometimes even the ESXi host.
Observing the problem, i found something strange.
This is a ping result, when everything is working fine.
10.0.0.50 is my ESXi host:
-
ping 10.0.0.50
Pingen naar 10.0.0.50 met 32 byte gegevens:
Antwoord van 10.0.0.50: bytes=32 tijd<1 ms TTL=64
Antwoord van 10.0.0.50: bytes=32 tijd<1 ms TTL=64
Antwoord van 10.0.0.50: bytes=32 tijd<1 ms TTL=64
Antwoord van 10.0.0.50: bytes=32 tijd<1 ms TTL=64
arp -a
10.0.0.50 00-50-da-44-8c-49 dynamisch
-
Now it gets interesting, here is a ping result when i have lost connection:
-
ping 10.0.0.50
Pingen naar 10.0.0.50 met 32 byte gegevens:
Antwoord van 10.0.0.50: bytes=32 tijd<1 ms TTL=250
Antwoord van 10.0.0.50: bytes=32 tijd<1 ms TTL=250
Antwoord van 10.0.0.50: bytes=32 tijd<1 ms TTL=250
Antwoord van 10.0.0.50: bytes=32 tijd<1 ms TTL=250
arp -a
10.0.0.50 00-1d-7e-d0-56-34 dynamisch
-
The only kind of connection i can 'establish' at this point, is that ping result. Al other (VI client, RDP to VM's, Putty SSH to host) fail.
How come i still get an ping answer from my ESXi host? And why did the Time to live change? And more importantly, the ARP result (MAC ID) also changed, wich is impossible. But that is causing my problem.
I found posts about similar problems, but even the latest updates (including a e1000 driver update) dit not help.
To add to the confusion i also have this problem with 3com NIC's, wich use another driver. Only the period differs, on 3com NIC's i get a couple of hours connection before this problem occurs.
Does anyone has a solution for this?
