This is an odd issue I've had with a network I formerly admined. We found a workaround, but the core issue remains unknown to me.
Situation is a pair of ESX hosts in a cluster. Each had their VMs on their local hard drive. We added a SAN and connected it to the ESXs. After migrating the VMs to their new storage, a curious event occured.
Reply from myvm: bytes=32 time=3ms TTL=128
Reply from myvm: bytes=32 time=3ms TTL=128
Reply from myvm: bytes=32 time=3ms TTL=128
Reply from myvm: bytes=32 time=3ms TTL=128
Reply from myvm: bytes=32 time=3ms TTL=128
Reply from myvm: bytes=32 time=3ms TTL=128
Reply from myvm: bytes=32 time=1546ms TTL=128
Reply from myvm: bytes=32 time=3ms TTL=128
Reply from myvm: bytes=32 time=3ms TTL=128
Reply from myvm: bytes=32 time=3ms TTL=128
Reply from myvm: bytes=32 time=3ms TTL=128
Reply from myvm: bytes=32 time=3ms TTL=128
Reply from myvm: bytes=32 time=3ms TTL=128
Reply from myvm: bytes=32 time=3ms TTL=128
Reply from myvm: bytes=32 time=3ms TTL=128
Reply from myvm: bytes=32 time=3ms TTL=128
Notice the exception? Inside the VM, everything was just fine and dandy, except that on a totally random timing, stuff seemed to quasi-freeze (for a very short timespan) then back to normal. This was not a storage issue, as any VM created straight on the SAN did not exhibit this issue. Our workaround was simply creating most of our servers from scratch (for a variety of reasons, this was quite simple).
Any ideas what could have caused this?
