Question

HA error "Could not reach Isolation" in Vmware

Answer 1

HA agent error

• The HA agent tries to detect at any time if the Host is in ISOLATED mode, that is, in isolated mode. As it does? Connecting with all the Hosts and devices that you have at your disposal as other Hosts, Datastores and Link Doors.

• If there is a device that can not be contacted, the status of the Host will appear with a Warning that tells us: "vsphere has agent on this host could not reach isolation address".

Resolution of the conflict


The main cause of this error is usually when a device in our infrastructure has changed its IP address or is no longer with us (RIP).

It is also possible that we have configured an IP address incorrectly, such as a gateway.

• How to change the gateway of a Host ?. To change the gateway of a Host we can go to the " Settings" tab, in Software, "DNS and Routing" and click on "Properties".

In the message of the Host that appears in the SUMARY tab we will see which one or which are the Host that can not be reached. Once we have identified the device or the wrong configuration we must restart the HA service.

How to restart the HA agent without restarting the Host? To restart the HA agent of a Host, we must access the Host via SSH and execute the following command:

/sbin/services.sh restart

• Once the process of restarting the HA service on the Host has been completed, the Warning message will no longer appear on the Sumary tab.

• It is possible that the Virtual Machines that were protected by HA in that Host show a Warning message. The Warning message indicates that HA protection was temporarily lost.

• To remove the Warning we can simply click on the Virtual Machine, Alarms and right click on the Alert. We make an Acknlowledge and a Clear of the alert.

• With this we will have resolved a typical HA Agent alarm from our virtual server farm in VMWARE.

---