After upgrading to esxi 5.0 623860 we are experiencing network disturbance when doing a live migration (not storage migration)
Both high priority and standard priority. There are no network spikes when looking at the s-flow traffic. Also there are no spanning tree negotiations during the network disturbance.
But still, our monitoring system gets network time-outs on plenty of the monitored servers that is not being migrated. This has also been seen on ESX 4.1.
Has anyone else experience this?
Hi,
You mention network time-outs of other virtual machines when a vMotion operation occurs, but do you also experience loss of network connectivity within the virtual machine when migrating the virtual machine with vMotion?
High and standard priority identify the CPU priority of the vMotion process within the host, it should not impact network connectivity.
Can you share more information about your (vMotion) network design?
After all, it was a networking issue. We created a separate VLAN for vKernel. This was shared with management earlier. Problem solved.