In VMware vSphere environments, planned network infrastructure upgrades (such as core switch replacements) can result in a total loss of management and VM network connectivity for ESXi hosts. If the hosts and virtual machines (VMs) are left powered on while the network is down, the vSphere High Availability (HA) cluster may incorrectly identify this as a host failure or isolation event.
Symptoms:
vSphere HA triggers a "Host Isolation" or "Host Dead" event.
Virtual machines are unexpectedly powered off or restarted on other hosts.
DRS migration tasks fail due to a lack of network connectivity for vMotion.
vCenter Server alarms for Host connection failure or Host is not responding.
Product: VMware vSphere ESXi
Versions: 7.x, 8.x (including 8.0 Update 3)
Component: High Availability (HA), Distributed Resource Scheduler (DRS)
Configuration: Environments with shared storage (SAN/NFS) where hosts remain powered on during network maintenance.
By default, vSphere HA uses network heartbeats to monitor host liveness. If a host loses management network connectivity for more than 30 seconds, the HA Master host declares that host as "Dead" or "Isolated." If the Host Isolation Response is configured to restart VMs, HA will attempt to move those workloads. During a cluster-wide network outage, these migration and restart attempts will fail, leading to unnecessary downtime and potential data inconsistency since the underlying storage remains active.
To prevent unintended cluster responses during scheduled network maintenance, follow these steps:
This prevents HA from reacting to the loss of network heartbeats.
Log in to the vSphere Client.
Navigate to the Cluster in the inventory.
Click the Configure tab.
Under Services, select vSphere Availability.
Click Edit.
Uncheck the Enable Host Monitoring checkbox.
Click OK.
This ensures that no vMotion migrations are initiated while the network is unavailable.
Navigate to the Cluster > Configure tab.
Under Services, select vSphere DRS.
Click Edit.
Change the Automation Level to Manual.
Click OK.
Once the network maintenance is complete and physical connectivity/routing has been verified:
Navigate back to vSphere Availability and re-check Enable Host Monitoring.
Navigate back to vSphere DRS and return the Automation Level to its previous state (e.g., Fully Automated).