Permanent PDL is the action that results when you modify the storage array configuration by removing, masking, or unmasking LUNs or by bringing down a path or a component in the path. It may also be caused by storage manager actions such as array lease rotation, rebalancing capacity/workload retiring storage, or maintaining components in the path.
Transient PDL is the action that results due to changes in the storage that are not triggered by administrative actions. These are unusual events and, in general, are not common routines. For example, a dead interface such as Network switch, HBA, or array, or storage network reconfiguration.
To recover powered up virtual machines on a device that has been affected by PDL to the device/LUN:
- Run this command to list the virtual machines and identify the virtual machines that are to be powered on:
esxcli vm process list
You see an output similar to:
RH4U5-101VM
World ID: 8339
Process ID: 0
VMX Cartel ID: vm_cartel_ID
Where vm_cartel_ID is the cartel ID of the virtual machine to be powered on.
- Power off the virtual machine from the vSphere Client or the vSphere Web Client. If the virtual machine is unresponsive, execute the below command to kill or power down the virtual machine:
kill -9 vm_cartel_ID
- Run this command to remap or to bring the PDL device online:
esxcli storage core adapter rescan -A vmhbax
For example:
esxcli storage core adapter rescan -A vmhba1
esxcli storage core adapter rescan --adapter vmhba1
Note: Alternatively, you can also use the VMware vSphere Client to bring the device online. To bring the devices online using the vSphere Client, navigate to Host > Configuration > Storage > Datastores and click Rescan All.