Link to home
Start Free TrialLog in
Avatar of Garry Shape
Garry ShapeFlag for United States of America

asked on

vSphere - automatic migrating and errors

I have a mini environment with two hosts esxi 5.5, vCenter 6.0.
for some reason I keep seeing in the status pane an error:

Migrate virtual machine
ServerName01
A general system error occurred: 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.

View details:

Migrate virtual machine:A general system error occurred: 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.
See the error stack for details on the cause of this problem.
Time: 10/27/2016 7:01:13 PM
Target: ServerName01
vCenter Server: vc.domain.com
Error Stack
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 [168649488:1477612873751395] vMotion migration [168649488:1477612873751395] stream thread failed to connect to the remote host <10.13.99.21>: The ESX hosts failed to connect over the VMotion network
Migration [168649488:1477612873751395] failed to connect to remote host <10.13.99.21> from host <10.13.99.20>: Host is down.

I am not attempting to migrate any VM. Is it doing that automatically somewhere? Anyway to turn off?

Also, I can manually migrate a VM if I choose the right network, so I'm not sure why this error would be generated.
Where should I check on that?

It's just two hosts
ASKER CERTIFIED SOLUTION
Avatar of Richardson Porto
Richardson Porto
Flag of Brazil image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Garry Shape

ASKER

Thanks for the feedback/help.
I've turned DRS off, that fixed the errors.

Now, I can vmotion the VM's between hosts. So I'm not sure why automatic is not working.
Is DRS supposed to use a specific port group for that?
vMotion uses VMKernel Portgroups.

I would check your network, and VMKernel Portgroups which are selected for use with vMotion.

This can be done using VMKPING.

OR, upload screenshots of your networking here.
Hi,
as mentioned, check if you have only one or several vmkernel configured for use with VMotion on each host.
You should have only one vmkernel per host with box "use for VMotion traffic" checked, in your vswitch properties and then vmkernel properties.
The VM's appear to be on the VM Network of the standard switch on the host, not on the Distributed Switch.
The host is trying to use a vMotion Portgroup, which does not communicate with the destination server's vMotion portgroup.

again, troubleshooting, if you cannot easily see the issue, is to use VMKPING and send packets through each VMKernel portgroup.
do you require any additional help to close this questiom?