![]() The other odd thing is that if I create a brand NEW VM, I can vmotion it from host to host to host all day long with zero problems. For example, after moving one VM, wireshark on a system on the same VLAN saw ARP broadcasts from that VM requesting the MAC address of the network gateway. Traffic sniffing shows that some packets from a moved VM are getting out to the network, but not all. ![]() We have checked the MAC address table on the switch stack and it is being properly updated as soon as the vmotion finishes. This configuration has been in production for years, and vmotion worked fine on many occasions. The nic teaming is configured for Ip Hash with Switch notify. The hosts are connected to a Cisco switch stack with two nics each, configured with cross stack etherchannel. Again, move them back to the original host and all is well. Sometimes with a pattern like that, and sometimes not. 8 pings go fine, then 10 time out, then 8 or 9 are fine. Some VM's, after being moved, will have intermittent network outages. Move them back to the original host, and they immediately start pinging again.This also happens if I shutdown the VM, THEN migrate it, and power it back up again. However, when the VM's finished moving to another host.they stopped responding on the network entirely. Wasn't strictly necessary (the disk was hot swappable) but hey, better safe than sorry. One of the hosts had one of it's OS disks go bad, so I started vmotioning systems off of it so I could put it maintenance mode before replacing the disk. We have vmotioned VM's in the past without incident, but since it's not something we need to do on a regular basis, it's been a while. We have a a vSphere cluster of 6 hosts that has been running quite well for years.
0 Comments
Leave a Reply. |