A general system error occurred migration failed while copying data. No route to host

[GaneshNetworks]

While i am migrating one VM from one ESX 3.5 to another ESX3.5 host it throws an error.

What does this error mean:

A general system error occurred migration failed while copying data. No route to host.

How to fix this problem?

Thanks,

Ganesh

[Hoschi201110141]

Hi

I think your two hosts have no route to each other. When ever possible use Full-Qualified Domain Names. Doublecheck all your networksettings (IP/GW/DNS). Try to ping each other Host from the Service-Console of each host.

When this is not working post a bit more information please.

Regards

Hoschi

[GaneshNetworks]

All the servers that are configured in the cluster is pinging each other. let me give a brief explanation about this problem.

There is no default gateway has been set to all ESX boxes that are configured in that cluster. Is there any command to find out the default gateway of all ESX boxes. When i tried randomly, it throws an error:

Any idea about this problem?

Note: I have configured CDP in all boxes. But it doesn't show any useful info.

Thanks,

Ganesh

[Hoschi201110141]

Hi Ganesh

Becaus i don't know your Networkconfiguration, it's a bit dificult... like a ridle.

I think your mainproblem is a misconfiguration of VMotion.

Try to put the hosts where you like to have VMotion in the same subnet. When you use VLAN's.. don't forget to configure the switches behinde the ESX host. If you can post the ip and subnetmask from both host's Service Console and VMotion VMkernel-Interface we can see maybe a bit more.

Maybe you have the following scenario:

The Service Console is in a diffrent VLAN / Subnet with an other Gateway then the both Hosts and each of these hase a diffrent VLAN / Subnet for his VMotion Interface.

In these Case you can ping each other host to the Service Console IP. Did you try this with the IP's / Interfaces which you use for VMotion?

It's maybe not best practice but for testing try to address the VMotion Interfaces with IP's from the Service Console VLAN / Subnet.

[GaneshNetworks]

The scenario which is mentioned in your last post is 100% opt to my environment.

Service console port is configured in different subnets. VMKernel port is isolated from the SC ports, thats the reason why can't ping VMKernel IP from SC. What all are the things do i need to change to ping the VMKernel ports from SC port?

SC port is configured with class A IP and VMK port is configured with class C IP.How can i explain this scenario to my networking team to work on them flawlessly.

As you are driving me in the correct direction, i am giving points to you by clicking "Helpful Answer". Thanks HOSCHI.

Note: Production networks are all working fine with its configuartion. Only the problem with its VMKernel port, which doesn't allow me to vMotion.

Thanks,

Ganesh

[Ham21]

Hi,

find the details

Note: Production networks are all working fine with its configuartion. Only the problem with its VMKernel port, which doesn't allow me to vMotion.

-------> The production network will not have any issues becoz the GATEWAY details are being done at the router level by the networking team. for VMotion to happen successfully we have to configure it at the ESX Host level. In order to perform this please do the below steps.

To change the default gateway address, edit the /etc/sysconfig/network file and change the GATEWAY to the proper values. before this you have to get the GATEWAY Details from the Networking team to perform routing between CLASS A ans CLASS C.

For the changes to take place, reboot the host or restart the network service with the command:
[root@server root]# service network restart

In GUI,

Edit the properties of VMkernal port group and SC port group to update the default gateway ip address.

I hope this will resolve the issue

Thanks