Skip to main content

 VMware HA - Quick View for Interviews


✅ What is VMware HA?


VMware High Availability (HA) is a feature in vSphere that automatically restarts virtual machines (VMs) on another available host in case of a failure, ensuring minimal downtime.


✅ How Does VMware HA Work?


1 Cluster Configuration - HA is enabled at the cluster level in vSphere.


2 Host Monitoring - Each ESXi host communicates via HA heartbeats.


3 Failure Detection - If a host fails, HA identifies the issue and restarts affected VMs on another host.


4 Resource Allocation - HA ensures sufficient resources are available for failover using admission control policies.


✅ HA Primary Node Election Process


When HA is enabled, one ESXi host is elected as the Primary Node.


All other hosts act as Secondary Nodes.


The primary node is responsible for monitoring cluster health and coordinating VM restarts.


If the primary host fails, a new primary is elected from the remaining hosts.


✅HA Activation Scenarios


1 Host Failure - The ESXi host goes offline, and VMs restart on another host.


2 Network Isolation - The host loses network connectivity but remains powered on. HA restarts VMs on a healthy host.


3 APD (All Paths Down) - The host loses access to shared storage temporarily. HA waits before deciding on a failover.


4 PDL (Permanent Device Loss) - The host


permanently loses access to storage. HA immediately restarts affected VMs on another host.


✅ HA Communication & Heartbeats


HA uses the Management Network for heartbeats.


Datastore Heartbeats are used as a secondary check if network heartbeats fail.


HA detects failures based on heartbeat loss and triggers VM restarts accordingly.


📌 Key VMware HA Ports


UDP 8182 - Used for HA agent communication.


TCP 443- Used for vSphere Client to vCenter communication.


UDP 902 Used for host management.

Comments

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...
  vCenter Troubleshooting Tips, Common Issues & Log Locations 🚀 1. General Troubleshooting Approach A. Check service health first For vCenter Server Appliance (VCSA): Shell https : / / < vcenter - FQDN > : 5480 Show more lines Go to Services → Health to verify: vCenter Server ESXi hosts vSphere Client DNS, NTP, DB connections vpxd, vpxd-svcs, vsphere-ui B. DNS & NTP checks vCenter is highly dependent on correct DNS & time sync. Check: Shell nslookup < vcenter - fqdn > nslookup < esxi - host - fqdn > Show more lines Time drift > 5 minutes causes: Login failures vpxd crashes PSC authentication issues C. Check storage/database health Slow DB/storage = UI slow, tasks hung. For VCSA: Shell df - h du - sh / storage / log / * / var / log Show more lines Free up space if partitions hit >80%. D. Restart critical services safely On VCSA: Shell service - control - - status service - control - - stop - - all service - control - - start - - all ...