Decommissioning ESXi hosts or clusters normally includes removal of protocol endpoints (PEs). The usual FlashArray volume disconnect process is used to disconnect PEs from hosts. As with removal of any non-vVol block storage device however, the best practice is to detach the PE from each host in vCenter prior to disconnecting it from them on the array.
|
|
|
vSphereView 143: Web Client Tool for Detaching a PE from an ESXi Host |
To detach a PE from a host, select the host in the Web Client inventory pane, navigate to the Storage Devices view Configure tab, select the PE to be detached, and click the 
tool to launch the Detach Device confirmation wizard. Click Yes to detach the selected PE from the host.
|
|
|
vSphereView 144: Confirm Detach Wizard |
vSphereView 145 shows the Web Client storage listing after successful detachment of a PE.
|
|
|
vSphereView 145: Detached PE |
Failure to detach a PE from a host (vSphereView 146) typically occurs because there are vVols bound to the host through the PE that is being detached.
|
|
|
vSphereView 146: Failure to Detach PE (LUN) from a Host |
FlashArrays prevent disconnecting a PE from a host (including members of a FlashArray host group) that has vVols bound through it.
The Purity//FA Version 5.0.0 GUI does not support disconnecting PEs from hosts. Administrators can only disconnect PEs via the CLI or REST API.
Before detaching a PE from an ESXi host, use one of the following VMware techniques to clear all bindings through it: