I recently had this problem, but forgot to take a screenshot for the blog, sorry guys.
I was patching an HA/DRS cluster using VUM and none of the VMs would migrate off one specific host. The error it gave was “A general system error occured: Failed to start migration pre-copy Error 0xbad010d. The Esx host failed connect over the VMotion network”.
Immediately I enabled SSH on the troubled host and used vmkping to ping every vmotion interface/ip of all nodes of the cluster. As I was doing this, vmotions started working fine.
I googled it and found this article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1013150
Problem is it states it’s fixed in 4.0 Update 2, yet my host is 4.1.
In short, here’s what I did:
|
1 |
Get-VMHostService | ? {$_.key -eq "TSM-SSH"} | Start-VMHostService |
and then
|
1 |
vmkping 192.168.0.5 |
and pinged every vmotion IP address for EVERY node in the cluster, including it’s own IP address.
Hope that helps someone!