Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 182126

vmotion intermittently failing until vmk recreated

$
0
0

Hi,

 

I have seen various other similar examples but so far not a solution for the problem I have.

 

I have several servers all connected to a distributed switch.  Normally they seem to work ok and do vmotions etc... without problems.

 

In order to ensure a consistant configuration, all my ip addresses, switches, interfaces, vmk are the same number on each server

 

My vmotion vmk is vmk3 on every server and has a vlan id of say 123 again on every server.

 

The uplinks are again the same on every server ie vmnic0 is dvuplink1 on each server etc...

 

vmotions have and do work but occasionally they fail at the 9% mark with the error

 

 

The vMotion migrations failed because the ESX hosts were not able to connect over the vMotion network.  Check the vMotion network settings and physical network configuration.
vMotion migration [-1408035057:1363186092657433] failed to create a connection with remote host <1.2.3.11>: The ESX hosts failed to connect over the VMotion network
Migration [-1408035057:1363186092657433] failed to connect to remote host <1.2.3.11> from host <1.2.3.15>: Timeout
The vMotion failed because the destination host did not receive data from the source host on the vMotion network.  Please check your vMotion network settings and physical network configuration and ensure they are correct.

 

If I then SSH onto the servers I can ping the local vmotion vmk ie if on .11 I can ping .11 but can't ping .15 and vice versa.  If I delete the vmk from the server and recreate it with the exact same details it starts working again and then at some point in the future may fail in the same way.

 

We are running 5.0 u1 on each server, all built from same iso.


Viewing all articles
Browse latest Browse all 182126

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>