I also can ping external from the service console. Logged onto the ESXi service console, I cannot ping the trouble VM by host name or by IP address, but I can ping OTHER virtual machines not experiencing the issue. All VMware tools have been updated to the latest correct version and match the ESXi host I have followed certain VMware KBs to no success, including:
#MOVE VMWARE VM TO ANOTHER NETWORK TRANSMIT FAILURE WINDOWS#
I have not seen a pattern regarding whether or not it is only certain guest OS that lose network but we are primarily a Windows environment. Here are some of the specs - all environments are virtually identical except for memory: That seems to have fixed that but we still have the issue. VMware saw a bunch of SAN errors in our log files so we updated our SAN firmware to the latest version. I can re-install the virtual adapter completely, and it will re-gain network. I can reboot it and it will re-gain network. I can also fail the troubled VM back over to the prior host and it will regain network. The workaround? Simply "disconnect" the virtual NIC and "reconnect" it, and the VM will start returning packets.
In fact, I can fail over 3 virtual machines from one host to another, and 2 of the 3 may fail over correctly, while one will lose network.
The strange thing is that other guests on the VM host are fine - they do not lose network at all. Occasionally, though far less frequently, virtual machines will also spontaneously lose network over night.
Since configuring our production and DMZ clusters we have been noticing that virtual machines will sometimes drop network connectivity after a successful vMotion or Storage vMotion. I have a couple of tickets open with VMware and our SAN vendor, EqualLogic, on this issue.
0 kommentar(er)
