Release Notes

Configuration and management
17 Dell EMC SC Series and VMware vSphere Virtual Volumes Best Practices | 3161-BP-SC
4.2.3 PowerCLI
PowerCLI can also be used to manage the Path Selection Policy for protocol endpoints. Of the three methods
covered here, PowerCLI is going to be the fastest and most consistent across an environment. The following
PowerCLI reveals a protocol endpoint is using the VMW_PSP_MRU Path Selection Policy:
Get-Cluster -Name "New VVol Cluster" | Get-VMHost | Get-ScsiLun | where
{$_.Vendor -eq “COMPELNT” CapacityMB -lt 1 –and $_.Multipathpolicy -eq
“MostRecentlyUsed”}
PowerCLI reflects a list of protocol endpoints using the Most Recently Used PSP
We can use similar PowerCLI to modify the PSP to Round Robin:
Get-Cluster -Name "New VVol Cluster" | Get-VMHost | Get-ScsiLun | where
{$_.Vendor -eq “COMPELNT” –and CapacityMB -lt 1 –and $_.Multipathpolicy -eq
“MostRecentlyUsed”} | Set-ScsiLun -Multipathpolicy RoundRobin
PowerCLI now reflects a list of protocol endpoints using the Round Robin PSP
4.3 Changing the default Path Selection Policy
Rather than change the PSP after devices are created and presented to the hosts in the vSphere cluster, it
can be configured automatically as newly presented devices are discovered by the hosts. This would provide
device PSP consistency within the cluster. Following are examples of a few methods which can be used to
accomplish this.
4.3.1 esxcli
The following esxcli changes the default PSP for the VMW_SATP_ALUA SATP to Round Robin on a single
host. This command would need to be executed on each host:
[root@tssrv251:~] esxcli storage nmp satp set -P VMW_PSP_RR -s VMW_SATP_ALUA
Default PSP for VMW_SATP_ALUA is now VMW_PSP_RR