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

Top 10 high-level EC2 scenario-based questions to challenge your AWS & DevOps skills

 Here are 10 high-level EC2 scenario-based questions to challenge your AWS & DevOps skills 1. Your EC2 instance is running but you can’t connect via SSH. What troubleshooting steps will you take?  Check Security Group inbound rules (port 22 open to your IP).  Verify Network ACLs (NACLs not blocking inbound/outbound).  Confirm instance’s Public IP / Elastic IP.  Validate Key Pair and correct permissions on .pem.  Ensure SSM Agent is installed (Session Manager can help).  Check system logs on the console for OS-level issues. 2. You terminated an EC2 instance by mistake. How can you prevent this in the future? Enable Termination Protection in EC2 settings. Use IAM permissions to restrict TerminateInstances. Tag critical instances and set resource policies. 3. Your EC2 instance needs to access an S3 bucket securely. What’s the best way to configure this? Best practice: Attach an IAM Role with least privilege policy to the EC2 instance. Avoid hardcoding...

GitOps-Driven Management of VKS Clusters: Enabling GitOps on VCF 9.0 (Part 03)

  GitOps-Driven Management of VKS Clusters: Enabling GitOps on VCF 9.0 (Part 03) In the Part-02 blog, we walked through the process of deploying an Argo CD instance within a vSphere Namespace on  VMware Cloud Foundation (VCF) 9.0 , enabling a GitOps-based approach to manage Kubernetes workloads in a vSphere environment. With Argo CD successfully installed, we now have a powerful toolset to drive declarative infrastructure and application delivery. In this blog post, we’ll take the next step by demonstrating how to  provision and manage VKS clusters  directly through the Argo CD  UI and CLI . This allows us to fully operationalise GitOps within the private cloud, delivering consistency, scalability, and automation across the Kubernetes lifecycle. Importance of Managing the Kubernetes Cluster with a Gitops Approach Adopting a GitOps-based approach for managing Kubernetes clusters enables declarative, version-controlled, and automated operations by leveraging Git a...
 https://knowledge.broadcom.com/external/article?articleNumber=389217 VMware Aria Suite Backup and Restore Documentation Issue/Introduction This article host backup and restore documentation for VMware Aria Suite 2019 product lines. Environment VMware Aria Suite 8.x VMware Aria Automation 8.x VMware Aria Automation Orchestrator 8.x Cause Technical documentation has been migrated from docs dot vmware dot com to  https://techdocs.broadcom.com . During this migration, some content considered End of Life (EOL) or End of General Support (EOGS) was not targeted for migration. Resolution PDF files are provided in this article while these documents are restored to https://techdocs.broadcom.com. Attachments Backup & Restore with EMC Avamar for VMware Aria Suite.pdf get_app Backup & Restore with Netbackup for VMware Aria Suite.pdf get_app VMware Aria Suite Backup and Restore by Using vSphere Data Protection.pdf get_app