VMotion/HA intermittent errors after Update 2

[jrgreeno]

After upgrading my ESX blades to 3.5u2, I am seeing VMotion/HA errors in the VC.

If I manually move a VM from one host to another the action times out or is "unable to communicate with the remote host".

When I Reconfigure for HA, the errors subside for about a day and both HA and manual VMotion work fine.

I have verified host connectivity to and from each of the ESX hosts using ping and vmkping using both short and FQDN. I've also populated the hosts file with the proper IPs and hostnames.

Is there something else I could be missing?

What logs exactly do I need to be looking at to help diagnose these HA errrors?

Thanks for the help...

[Jasemccarty]

What version of VC are you using?

I had nothing but problems with HA/DRS in VC 2.5 U2.

When I upgraded to VC 2.5 U3, all my problems went away.

Jase McCarty

http://www.jasemccarty.com

Co-Author of VMware ESX Essentials in the Virtual Data Center

(ISBN:1420070274) from Auerbach

[kjb007]

Make sure that the hostnames you added are all lowercase in the hosts file. This caused problems before. Also, are you adding your hosts to vc via IP or FQDN? Make sure to use FQDN.

-KjB

[Jasemccarty]

With VC 2.5 U3, the issue with lowercase hostnames is removed.

That was part of my problem.

Jase McCarty

http://www.jasemccarty.com

Co-Author of VMware ESX Essentials in the Virtual Data Center

(ISBN:1420070274) from Auerbach

[jrgreeno]

As far as I know, It's 2.5U2 although I had to change the version in the SQL table to get the server service to start.

When I start the client on the VCS it says:

VIC 2.5.0 Build 119598

VC 2.5.0 Build 119598

I just checked the download section on the site and don't see a 2.5u3 download only U2? - Strike that, found it, getting ready to try it.

ESX servers are added to VC via FQDN. When I look in the VIC, I see server.domain.com.