VMware Cloud Community
Eternal_Snow
Contributor
Contributor
Jump to solution

VMotion failed in standalone network

Hi,

Check this first: http://communities.vmware.com/message/1503426#1503426

I follow this article to create the VMkernal in a separated network. But when I try to use vMotion, I get this error:

A general system error occurred: The VMotion failed because the ESX hosts were not able to connect over the VMotion network. Please check your VMotion network settings and physical network configuration.

How to fix it? Thanks.

0 Kudos
25 Replies
Eternal_Snow
Contributor
Contributor
Jump to solution

su -l works.

I CANNOT vmkping to vmkernel ip, even the one of this server.

0 Kudos
AWo
Immortal
Immortal
Jump to solution

Check if the physical NIC has an active link.

Check if it belongs to a VLAN and put both VMotion VMlernel NIC's into that VLAN.

Check if there are any layer three restrictions on that switch so that the IP address subnet range you use (192.168.9.0) can't be used.

If possible remove the Virtual Machine port group, temporarily from that vSwitch.


AWo

VCP 3 & 4

Author @ vmwire.net

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
Eternal_Snow
Contributor
Contributor
Jump to solution

the NIC status is good (green in NIC side and switch side, reported by IDC member).

all NICs in that vSwitch from all servers are in the same vlan. no upper link, no router.

I've removed the port group from this vSwitch.

Result:

ping to IP of console: passed

ping to Name of console: passed

ping to VMkernal: failed

0 Kudos
Eternal_Snow
Contributor
Contributor
Jump to solution

It's passed. I know the reason.

The subnets of service console and vmkernel are the same one.

Change the vmkernel IPs to another subnet: passed....

Thank you very much.

0 Kudos
AWo
Immortal
Immortal
Jump to solution

9098_9098.gif

It should be able to ping its own VMkernel IP via vmkping, but as you said even this is not possible.

Is the NIC you use for the VMotion listed as an active NIC under the VMkernel properties (it can be active, standby or not used)? Scroll down in the VMotion VMkernel properties (you already send a screenshot from).

AWo

VCP 3 & 4

Author @ vmwire.net

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
AWo
Immortal
Immortal
Jump to solution

9099_9099.gif

AWo

VCP 3 & 4

Author @ vmwire.net

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos