Hello since today are the VMotion timed out it starts and hangs with 10 %.
I have 2 DL380 G5 and a iSCSI MSA in the background
I reconfigured alreday the HA and DRS also restarted the VM Kernel
Any other Ideas?
Regards
Hannes
exacly my problem, right after aplying patches
see http://communities.vmware.com/thread/227186 to read my solution.
Hannes,
Make sure that both ESX hosts have the Datastores mapped EXACTLY the same,
If you SSL, console both ESX hosts and go:
cd /vmfs/volumes
then:
ls -lah
You should see the datastores that you have mounted - if you find that the guid provided for your datastore is not identical on both hosts, you need to remap one of them, so that they are!
Make sure you are careful . . .names etc are case sensitive.
The same applies to the names of your port groups for the VMs.
Please post back if this does not resolve your issue.
Hi Rolohm,
past all steps without success , unfortunately:(
Thanks for helping
Hannes
Hi Bulletprooftool
all volumes are idetical any other Ideas?
Thanks for answer
Hannes
Hi Athlon
yes vmkping is working fine
thanks for answer
Hannes
Hannes,
What error do you get when the vmotion fails? Is it "Error communicating to remote host"
There is a bug in VC with http session, and its been fixed in VC2.5U5, check the release notes below, hope this helps
This release resolves the following issue:
*A
Firewall Between ESX Server Hosts and VirtualCenter Server Might Drop
an Idle HTTP Connection Between the Hosts and the VirtualCenter Server
and Cause Errors*
This release resolves an issue where if
the HTTP connection between a remote ESX Server host and the
VirtualCenter Server is idle for more than 30 minutes, the firewall
with default session timeout policy drops the idle HTTP connection. The
dropped connection causes the host to be disconnected from the
VirtualCenter Server and reconnected later. When the connection is
dropped, initiating any operations on the remote ESX Server host causes
the VirtualCenter Server to display an error message similar to the
following:
An error occurred while communicating with the remote host.
A new advanced setting entry vpxd.httpClientIdleTimeout
can be used to configure the timeout value for an idle HTTP connection.
The default value for this entry is 15 minutes (900 seconds), ensuring
that the VirtualCenter Server closes the idle HTTP connection after the
connection has been idle for 15 minutes. If a firewall session timeout
value is set to less than 15 minutes, the value for vpxd.httpClientIdleTimeout should be changed to be smaller than the firewall's timeout value.