VMotion failed in standalone network

[Eternal_Snow]

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.

[AWo]

Do you have a vSwitch with a VMotion enabled VMkernel on both ESX servers?

Do both ESX servers have a unique IP address in the same subnet for their VMotion kernel?

Does "vmkping

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

[Eternal_Snow]

triple yes.

[AWo]

DNS working?

If you do not have DNS, add the servers to the "/etc/hosts" files.

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!=

[Eternal_Snow]

another yes.

but need a long name with domain name.

for example: esx1.mycompany.local

DNS hosted in my domain controller running windows.

[AWo]

Can you post screenshots of your VMotion vSwitch setup of both servers, please?

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!=

[Eternal_Snow]

hmm, i found that I cannot ping to vmotion now...

[AWo]

If vmkping does not work, VMotion won't work either. Check this again. Also the physical setup (are the switch ports where the VMkernels are connected to in the same VLAN or on the same switch, etc.).

I meant screenshots of the VMkernel setup....

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!=

[Eternal_Snow]

2 of my servers

[AWo]

Looks fine.

You said you found ping not working in the post before the last one? Does "vmkping 192.168.9.41/42" work or not, now?

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!=

[Eternal_Snow]

I've tested to ping from a windows client in that vlan.

Result: Failed

Is that different?

[AWo]

Yes, it is. Use "vmkping" from the console. That is a VMKernel ping....

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!=

[Eternal_Snow]

command not found.

and i cannot use find | -name 'vmking*' to find file.

could you tell me the folder of that command? thanks

[AWo]

vmkping, not vmking. And you'll find it in "/usr/sbin".

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!=

[Eternal_Snow]

cannot find it.

[Eternal_Snow]

i found that i cannot login with root user, or i cannot sudo bash with root's password.

password is correct coz i just use it in vSphere client login window.

[AWo]

You must use "./vmkping" as there is no path on that folder. And you must be root.

Have you tried "su -l" when you are logged in as some non-root user?

Are you using the physical console? Maybe some keys are different from the keyboard layout (like z and y).

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!=

[Eternal_Snow]

I'm using SSH coz the server is very far away from my client side.

and I'm tried to use sudo -l but no use. I get 'Sorry, try again.' every time. I'm sure the password is typed correctly. T.T

[Eternal_Snow]

when i call ./vmkping without root permission, i get this error:

syscall version mismatch (compiled: 0xb2ca79d9, kernel: 0x2ab04000)

[Eternal_Snow]

su -l works.

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

[AWo]

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!=

[Eternal_Snow]

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

[Eternal_Snow]

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.

[AWo]

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!=

[AWo]

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!=

[AWo]

Try "su -l" not sudo. However, you must be root. If the password don't work...

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!=