Isolation of ESXi hosts is validated on the basis of heartbeats. The timeline for declaring isolation of SLAVE and master ESXi is different. In this case we will discuss isolation of slave ESXi.

HA triggers a master election process before it will declare a slave ESXi host is ISOLATED. In this timeline, “s” refers to seconds:

• T0 – Isolation of the host (slave)
• T10s – Slave enters “election state”
• T25s – Slave elects itself as master
• T25s – Slave pings “isolation addresses”
• T30s – Slave DECLARES itself isolated
• T60s – Slave “triggers” isolation response

When an ESXi host is isolated, the value in “power on” FILE is raised to 1, HA READS this file and validates that ESXi host has been isolated. There is one Power on file per ESXi host and this file contains entries of all those VM’s which are currently powered on an ESXi host.

Isolation of ESXi hosts is validated on the basis of heartbeats. The timeline for declaring isolation of slave and master ESXi is different. In this case we will discuss isolation of slave ESXi.

HA triggers a master election process before it will declare a slave ESXi host is isolated. In this timeline, “s” refers to seconds:

When an ESXi host is isolated, the value in “power on” file is raised to 1, HA reads this file and validates that ESXi host has been isolated. There is one Power on file per ESXi host and this file contains entries of all those VM’s which are currently powered on an ESXi host.