Comments on riether.com: HA errors after update to esx 3.5 u2

I had the same problem after upgrade to 3.5 U2. Wh...

2008-10-05T18:36:00.000+02:00

I had the same problem after upgrade to 3.5 U2. When I compared the Security Profile rules for both cluster nodes, I found out that on problematic node there is no "aam" ports allowed. I add "aam" rule and it looks like solved this issue in my case.

Even i had similar issues, all I did was update th...

2008-09-21T19:54:00.000+02:00

Even i had similar issues, all I did was update the Virtual Center to Virtual Center 2.5 Update 2 from Update 1 and after the reboot of the Virtual Center Server, the ESX HA Cluster broke. I did not apply any patches to these ESX hosts which are in cluster and still they were broke. I was lucky to have them back by Re-configuring the HA.

Well, there must have been something really messed...

2008-08-08T13:39:00.000+02:00

Well, there must have been something really messed up on my systems.

I disabled HA on the cluster and then renabled it again.

Now I do have the /etc/opt/vmware/aam and FT_HOSTS file on the ESX 3.5 U2 systems.

I have to see whether they keep on functioning, but until now they are.

VMWare ESX works in mysterious ways.

With kind regards,

Jos Rossiau

Dear Jos,
I am not certain if a fresh install o...

2008-08-08T12:04:00.000+02:00

Dear Jos,
I am not certain if a fresh install of 35u2 leaves the /etc/opt/vmware/aam completely out as all my machines are updated ones from 35u1. therefor you could be right and it could be that this one´s changed with a fresh 35u2 install.

best regards
Joerg

Hi, I have updated my hosts to ESX 3.5 U2 but I ca...

2008-08-08T11:59:00.000+02:00