Problem with HA after upgrade to 3.5u1

[tow-eric]

I have 4 host running in a cluster. After I upgraded from 3.0.2u1 to 3.5u1, when I click on my cluster I get the error "Insufficient resources to satisfy HA Failover level on cluster...."

Anyone know what might have caused this as everything was fine before I upgraded, and maybe what I can try to fix it?

Thanks...

[ascari]

Hi

Please, check for resource availability (cpu and mem) if you using resource pools or reservations.

I think that the reason for this warning is for the second service console ip for isolation address. In esx 3.5 for more ha stability you need to configure a second sc in a different vSwitch where the first sc was created.

Try to do it, and assing a different subnet ip at second sc, and then select an host esx, right ckick and select reconfigure for ha.

Look also this kb: http://communities.vmware.com/thread/117250

Bye Alberto

[kjb007]

The HA slot determination has been changed in 3.5. HA uses what it terms as a slot to determine how much failover capacity you have in your cluster. In ESX 3.0, it used to use 150 MB and 150 MHz as the minimums, and it now uses 256 MB and 256 MHz. Mind you, this is assuming that you don't have reservations set for memory and/or cpu.

You can set a value in the HA cluster advanced settings to change the behavior back to what it was previously, and the error should go away.

das.vmMemoryMinMB = 150

das.vmCpuMinMhz = 150

-KjB