12.07.2015 Views

vsphere-esxi-vcenter-server-55-storage-guide

vsphere-esxi-vcenter-server-55-storage-guide

vsphere-esxi-vcenter-server-55-storage-guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 15 Managing Storage DevicesDetecting PDL ConditionsA <strong>storage</strong> device is considered to be in the permanent device loss (PDL) state when it becomes permanentlyunavailable to your ESXi host.Typically, the PDL condition occurs when a device is unintentionally removed, or its unique ID changes, orwhen the device experiences an unrecoverable hardware error.When the <strong>storage</strong> array determines that the device is permanently unavailable, it sends SCSI sense codes tothe ESXi host. The sense codes allow your host to recognize that the device has failed and register the stateof the device as PDL. The sense codes must be received on all paths to the device for the device to beconsidered permanently lost.After registering the PDL state of the device, the host stops attempts to reestablish connectivity or to issuecommands to the device to avoid becoming blocked or unresponsive.The vSphere Web Client displays the following information for the device:• The operational state of the device changes to Lost Communication.• All paths are shown as Dead.• Datastores on the device are grayed out.The host automatically removes the PDL device and all paths to the device if no open connections to thedevice exist, or after the last connection closes. You can disable the automatic removal of paths by setting theadvanced host parameter Disk.AutoremoveOnPDL to 0. See “Set Advanced Host Attributes in the vSphereWeb Client,” on page 131.If the device returns from the PDL condition, the host can discover it, but treats it as a new device. Dataconsistency for virtual machines on the recovered device is not guaranteed.NOTE The host cannot detect PDL conditions and continues to treat the device connectivity problems asAPD when a <strong>storage</strong> device permanently fails in a way that does not return appropriate SCSI sense codes oriSCSI login rejection.Permanent Device Loss and SCSI Sense CodesThe following VMkernel log example of a SCSI sense code indicates that the device is in the PDL state.H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x25 0x0 or Logical Unit Not SupportedFor information about SCSI sense codes, see Troubleshooting Storage in vSphere Troubleshooting.Permanent Device Loss and iSCSIIn the case of iSCSI arrays with a single LUN per target, PDL is detected through iSCSI login failure. AniSCSI <strong>storage</strong> array rejects your host's attempts to start an iSCSI session with a reason Target Unavailable.As with the sense codes, this response must be received on all paths for the device to be consideredpermanently lost.Permanent Device Loss and Virtual MachinesAfter registering the PDL state of the device, the host terminates all I/O from virtual machines. vSphere HAcan detect PDL and restart failed virtual machines. For more information, see “PDL Conditions and HighAvailability,” on page 130.VMware, Inc. 125

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!