Skip to main content

 In vSphere, Permanent Device Loss (PDL) and All Paths Down (APD) are two distinct storage connectivity issues. PDL indicates a permanent and unrecoverable loss of a storage device, while APD signifies a temporary loss of access, where the system expects the device to potentially return. VMware vSphere, including VMware Cloud Foundation (VCF), provides mechanisms to handle both PDL and APD to ensure virtual machine availability. 

Here's a more detailed explanation:

Permanent Device Loss (PDL):

Definition:

PDL occurs when a storage device is permanently lost, meaning it's unlikely to be recovered. This can be due to hardware failure, a device being removed without proper procedures, or other unrecoverable errors. 

vSphere Handling:

vSphere interprets certain SCSI sense codes from the storage array as indicators of PDL. Once a PDL is detected, the ESXi host stops retrying I/O to the affected device and the affected VMs are failed over if VM Component Protection (VMCP) is enabled. 

Example:

A storage controller reporting a failure or a LUN being permanently removed would be considered PDL. 

All Paths Down (APD):

Definition:

APD occurs when a storage device becomes unavailable to the ESXi host, and the host cannot determine if the loss is temporary or permanent. 

vSphere Handling:

The ESXi host will retry I/O to the affected device for a configured timeout period (default is 140 seconds). If the device recovers within that time, operations continue without interruption. If the device remains unavailable after the timeout, the host starts to fast-fail I/O operations to the device, but virtual machine I/O continues to be retried indefinitely. 

Example:

A network issue causing a storage array to become unreachable, or a host reboot, could lead to an APD condition. 

VMware Cloud Foundation (VCF) and PDL/APD: 

Integration:

VCF, which integrates vSphere, vSAN, and NSX, also provides mechanisms to handle PDL and APD events. 

Automated Remediation:

VCF's automation capabilities can be leveraged to orchestrate failover procedures and ensure virtual machines are migrated to healthy hosts in the event of PDL or APD. 

Consistency:

VCF aims to provide a consistent and reliable infrastructure, and its management capabilities play a crucial role in mitigating the impact of storage connectivity issues. 




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 ...