Solved

vSphere - automatic migrating and errors

Posted on 2016-10-27
9
71 Views
Last Modified: 2016-11-17
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
0
Comment
Question by:garryshape
  • 4
  • 2
  • 2
  • +1
9 Comments
 
LVL 10

Accepted Solution

by:
Richardson Porto earned 250 total points
ID: 41863225
You may have DRS (Distributed Resource Scheduler) enabled in your cluster... if you want avoid virtual machines migrate automatically, just disable DRS or change it to Manual or Partially Automated. The following VMware KB article shows how to disable it: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007655
1
 
LVL 118

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE)
Andrew Hancock (VMware vExpert / EE MVE) earned 125 total points
ID: 41863228
you need to ensure that two hosts vMotion can communicate with on another, and you do this using VMKPING (not PING!).

at the console or remotely logged on via SSH

so login to host

<10.13.99.21>:

and check you can VMKPING

  <10.13.99.20>:

and vice versa

There is a communication fault somewhere
0
 
LVL 11

Assisted Solution

by:Mr Tortur
Mr Tortur earned 125 total points
ID: 41863789
Hi,

I am not attempting to migrate any VM. Is it doing that automatically somewhere? Anyway to turn off?
Well explained by Richardson Porto, I don't see any other possibility to have automatic "VMotion" except DRS. Or maybe there is someone other than you logged in vCenter and doing these VMotion migration, but you should see it at the user column on the task.

I can manually migrate a VM if I choose the right network, so I'm not sure why this error would be generated.
If you say a manual VMotion is working, there is no need to check about VMotion..
In theory you must have a dedicated IP range for VMotion and both ESX's VMotion vmnic must be able to communicate physically, that's all.

Also what do you mean by "if I choose the right network" please ?
0
 

Author Comment

by:garryshape
ID: 41865598
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?
0
Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

 
LVL 118
ID: 41865685
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.
0
 
LVL 11

Expert Comment

by:Mr Tortur
ID: 41866874
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.
0
 

Author Comment

by:garryshape
ID: 41870946
The VM's appear to be on the VM Network of the standard switch on the host, not on the Distributed Switch.
0
 
LVL 118
ID: 41870951
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.
0
 
LVL 118
ID: 41890417
do you require any additional help to close this questiom?
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Virtual Machine Guest OS on RDM 2 63
V2V Hyper-V RODC to ESXi 4 62
Could not power on VM : msg.vmk.status.VMK_NO_SPACE. 6 58
vm server with sound card 3 27
When we have a dead host and we lose all connections to the ESXi, and we need to find a way to move all VMs from that dead ESXi host.
In this article, I will show you HOW TO: Suppress Configuration Issues and Warnings Alert displayed in Summary status for ESXi 6.5 after enabling SSH or ESXi Shell.
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:

911 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now