Does anyone know if vCenter 4 Update 1 added a new HA agent test to check for connectivity to the Isolation Address before HA can successfully be configured? In one of our environments the Isolation Address was set to deny ICMP response but we didn't know. After upgrading to vCenter 4 Update 1 (from vCenter 4 (RTM)) we were alerted to this configuration issue and the HA cluster will not complete its HA config. Thanks.
I haven't notice a HA reconfiguration.
And the agent package is dated Sep 2009:
# rpm -qi VMware-aam-haa-2.2.0-1
Name : VMware-aam-haa Relocations: (not relocatable)
Version : 2.2.0 Vendor: VMware
Release : 1 Build Date: Mon 21 Sep 2009 09:37:26 PM CEST
Install Date: Sat 21 Nov 2009 12:54:02 PM CET Build Host: pa-lin-bld474.eng.vmware.com
Group : Applications Source RPM: VMware-aam-haa-2.2.0-1.src.rpm
Size : 10678731 License: VMware, Inc
Signature : (none)
Packager : VMware, 3145 Porter Drive, Palo Alto, CA 94304, USA
URL : www.vmware.com
Summary : VMware HA
Description :
VMware HA
Andre
Andre,
Thanks, didn't think to output RPM information. Based on the RPM information it would seem the HA agent didn't change. Is it possible the HA agent only checks for Host Isolation address connectivity at HA configuration and never again (or at least until HA reconfigure)? That might explain why we were not aware the Host Isolation address was not pingable only "after" we moved to 4.0U1--HA agent had to be reinstalled on ESX host.
Josh
Is it possible the HA agent only checks for Host Isolation address connectivity at HA configuration and never again (or at least until HA reconfigure)?
HA will check for it also when it cannot reach the other ESXs, and use this information to determine the isolation.
So, I suggest in any case to use advanced HA option and add other isolation address (for example the IP of the core switch).
Andre