Virtual NIC on VM couldn't ping externally after Vmotion

Posted by ToreTrygg on Server Fault See other posts from Server Fault or by ToreTrygg
Published on 2010-01-12T11:24:09Z Indexed on 2010/04/02 9:03 UTC
Read the original article Hit count: 384

Filed under:
|

Today I vmotioned 5 MS SQL 2005 servers over to a new DRS Cluster. All SQL servers use the "Production_LAN" network and a single virtual NIC of type "VMXNET 3".

The first 4 SQL VM (Windows 2003 Standard or Enterprise x32 bit) vmotioned over without a hitch.

The last SQL VM I vmotioned (Windows 2003 Standard x64 bit R2) vmotioned over without error, but I upon completion, I could no longer ping the VM. I went into the VM and could not even ping the gateway, however I could ping the loopback. This SQL server is extremely busy in comparison with the previous 4 VM's. I restarted the server and it came back up with the virtual nic working just fine.

The build of both servers (vmotioner and vmotionee) is ESX 4.0.0 175625 - So, pre-update 1.

Should I suspect the network switch/VM for possibly not updating the mac table on the switch?

Anybody else ever have this issue or know what may have caused it?

Thank you!

© Server Fault or respective owner

Related posts about vmotion

Related posts about vsphere