Question Packet loss to a VM host but not its guests

[eli2k]

Hi everyone, I am having extensive packet lost to my ESXi hosts. I am able to ping the guests just fine, but the host has issues. It makes it challenging to use the web interface because it will take a while before the UI updates because of this. I'm unable to figure out why this is happening, and wanted to ask for advice for troubleshooting because I am not sure where to start. My router is running on OpenWrt, and I have dumb switches throughout. On the router, I have given static leases to the ESXi hosts. Thank you.



Pinging `esxi2` host:

C:\Users\User>ping esxi2 -t

Pinging esxi2.lan [10.0.0.208] with 32 bytes of data:
Reply from 10.0.0.208: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 10.0.0.208: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.

Ping statistics for 10.0.0.208:
    Packets: Sent = 8, Received = 2, Lost = 6 (75% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\User>ping 10.0.0.208

Pinging 10.0.0.208 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 10.0.0.208: bytes=32 time=1ms TTL=64
Reply from 10.0.0.208: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.208:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\Users\User>ping esxi -t

Pinging esxi.lan [10.0.0.238] with 32 bytes of data:
Reply from 10.0.0.238: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 10.0.0.238: bytes=32 time<1ms TTL=64
Reply from 10.0.0.238: bytes=32 time<1ms TTL=64
Reply from 10.0.0.238: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 10.0.0.238: bytes=32 time<1ms TTL=64
Reply from 10.0.0.238: bytes=32 time<1ms TTL=64
Reply from 10.0.0.238: bytes=32 time<1ms TTL=64
Reply from 10.0.0.238: bytes=32 time<1ms TTL=64
Reply from 10.0.0.238: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.238:
    Packets: Sent = 11, Received = 9, Lost = 2 (18% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging guests of the ESXi host:

C:\Users\User>ping win10-gpu -t

Pinging win10-gpu.lan [2603:8000:8b03:3ee0::bd7] with 32 bytes of data:
Reply from 2603:8000:8b03:3ee0::bd7: time<1ms
Reply from 2603:8000:8b03:3ee0::bd7: time<1ms
Reply from 2603:8000:8b03:3ee0::bd7: time<1ms
Reply from 2603:8000:8b03:3ee0::bd7: time<1ms
Reply from 2603:8000:8b03:3ee0::bd7: time<1ms
Reply from 2603:8000:8b03:3ee0::bd7: time<1ms

Ping statistics for 2603:8000:8b03:3ee0::bd7:
    Packets: Sent = 6, Received = 6, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
C:\Users\User>ping ubuntu-test -t

Pinging ubuntu-test.lan [fd8c:d93f:46b4::b47] with 32 bytes of data:
Reply from fd8c:d93f:46b4::b47: time<1ms
Reply from fd8c:d93f:46b4::b47: time<1ms
Reply from fd8c:d93f:46b4::b47: time<1ms
Reply from fd8c:d93f:46b4::b47: time<1ms
Reply from fd8c:d93f:46b4::b47: time<1ms

Ping statistics for fd8c:d93f:46b4::b47:
    Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
C:\Users\User>ping 10.0.0.157 -t

Pinging 10.0.0.157 with 32 bytes of data:
Reply from 10.0.0.157: bytes=32 time<1ms TTL=64
Reply from 10.0.0.157: bytes=32 time<1ms TTL=64
Reply from 10.0.0.157: bytes=32 time<1ms TTL=64
Reply from 10.0.0.157: bytes=32 time<1ms TTL=64
Reply from 10.0.0.157: bytes=32 time<1ms TTL=64
Reply from 10.0.0.157: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.157:
    Packets: Sent = 6, Received = 6, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

[eli2k]

It was an issue with MAC addresses. I installed ESXi to USB drive inside VMWare Workstation and when it was plugged into the physical host, it retained the MAC address from VMWare Workstation instead of the real MAC address. So I did new installation from physical host this time.