cafe99
Contributor
Contributor

can't vmotion vm to another host

Jump to solution

Hi,

I have 2 dell PE1950 with additional 2 port intel Pro NIC card and Dell MD3000i storage, running ESX 4.1 build 260274 manage by vCenter Server ver 4.1 build 258902.

For Host 1 (192.168.1.40) :

PortGroup Name VLAN ID Used Ports Uplinks

VM Network 131 0 0 vmnic3

vMotion 0 1 vmnic3

Service Console 3 0 1 vmnic3

VMkernel 2 0 1 vmnic3

vMotion IP Address : 192.168.133.40

VMkernel IP Address 192.168.131.55 for MD3000i iSCSI storage

for Host 2 (192.168.1.50):

PortGroup Name VLAN ID Used Ports Uplinks

vMotion 0 1 vmnic3

VM Network 131 0 1 vmnic3

Service Console 3 0 1 vmnic3

VMkernel 2 0 1 vmnic3

vMotion IP Address : 192.168.133.50

VMkernel 2 IP Address 192.168.131.50 for MD3000i iSCSI storage

Trying to vmotion VM from host 2 to host 1, I had a error :

Error message from 192.168.1.50: 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.

from Host 2 :

# vmkping 192.168.133.40

PING 192.168.133.40 (192.168.133.40): 56 data bytes

--- 192.168.133.40 ping statistics ---

3 packets transmitted, 0 packets received, 100% packet loss

# vmkping 192.168.133.50

PING 192.168.133.50 (192.168.133.50): 56 data bytes

64 bytes from 192.168.133.50: icmp_seq=0 ttl=64 time=0.070 ms

64 bytes from 192.168.133.50: icmp_seq=1 ttl=64 time=0.057 ms

64 bytes from 192.168.133.50: icmp_seq=2 ttl=64 time=0.070 ms

--- 192.168.133.50 ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 0.057/0.066/0.070 ms

from Host 1:

# vmkping 192.168.133.50

PING 192.168.133.50 (192.168.133.50): 56 data bytes

--- 192.168.133.50 ping statistics ---

3 packets transmitted, 0 packets received, 100% packet loss

# vmkping 192.168.133.40

PING 192.168.133.40 (192.168.133.40): 56 data bytes

64 bytes from 192.168.133.40: icmp_seq=0 ttl=64 time=0.087 ms

64 bytes from 192.168.133.40: icmp_seq=1 ttl=64 time=0.050 ms

64 bytes from 192.168.133.40: icmp_seq=2 ttl=64 time=0.043 ms

--- 192.168.133.40 ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 0.043/0.060/0.087 ms

# vmkping 192.168.133.50

PING 192.168.133.50 (192.168.133.50): 56 data bytes

--- 192.168.133.50 ping statistics ---

3 packets transmitted, 0 packets received, 100% packet loss

Can any help to tell me, what I had done wrongly?

Thanks!

Choong Leng

from Singapore.

0 Kudos
1 Solution

Accepted Solutions
mcowger
Immortal
Immortal

Your networking is in correct - the fact that you cnt do a vmkping between the is why you get that error. You need to correct your networking such that you can.

--Matt

VCP, VCDX #52, Unix Geek, Storage Nerd

9773_9773.gif

--Matt VCDX #52 blog.cowger.us

View solution in original post

0 Kudos
6 Replies
vmroyale
Immortal
Immortal

Hello and welcome to the forums.

In the properties of the vMotion portgroup, on the General tab, do you have the vMotion checkbox checked?

Good Luck!

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com
cafe99
Contributor
Contributor

Hi,

Thanks for the respond.

Yes, already done that when I configure the vmotion portgroup.

Help me. Thanks!

0 Kudos
mcowger
Immortal
Immortal

Your networking is in correct - the fact that you cnt do a vmkping between the is why you get that error. You need to correct your networking such that you can.

--Matt

VCP, VCDX #52, Unix Geek, Storage Nerd

9773_9773.gif

--Matt VCDX #52 blog.cowger.us

View solution in original post

0 Kudos
mittim12
Immortal
Immortal

In your print screen it doesn't look your have a VLAN specified. Are you using VLANs? If so are you setting the VLAN on the physical network port? As mcowger said if you can't connect over vmkping it's a sign of something within your network setup






If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

a_p_
Leadership
Leadership

I agree with the others.

To me this looks like a design/configuration issue.

You have all networks on ONE uplink! There's a "Service Console 3"!?

Please attach screen shots of your virtual network configuration and describe what you try to achieve.

André

0 Kudos
cafe99
Contributor
Contributor

Problem solve.

I think I had a hardware issue on the physical switch.

I move all the physical servers and iSCSI storage to a new switch and all are working properly.

I will like to thanks all of you that trying to help on this issue.  You are very much appreciated.

Thanks again.

Cheers!

Choong Leng from Singapore.

0 Kudos