HP 3PAR VMware ESX Implementation Guide

1. Stop all host I/O and apply the necessary SATP changes (create custom SATP rule and/or
modify default SATP rule PSP defaults) to the ESX/ESXi host.
2. Shut down the host.
3. Change the host persona on the array.
4. Boot the host.
5. Verify that the target devices have been claimed properly by the SATP rule.
ESX/ESXi 4.0 GA - 4.0 Ux
NOTE:
• Although ESX 4.0 GA - 4.0 Ux supports custom SATP rules, the -P options for setting PSP
(path policy) within the custom rule are not supported. PSP must be defined within the default
SATP rules.
• ESX 4.0 GA - 4.0 Ux has a known issue where no attempt should be made to change iops
from its default value of 1000 (iops = 1000). If the iops value is changed, at the next host
reboot, an invalid value for iops is retrieved and iops become unpredictable.
• If the custom rule is not created for ALUA, 3PARdata VV’s are claimed by the
VMW_SATP_DEFAULT_AA SATP rule even though the array persona is 11/VMware (ALUA
compliant array port presentation).
HP 3PAR SATP rules for use with persona 6/Generic-legacy (Active-Active array port presentation)
A “custom” SATP rule is not used. The PSP (path policy) is changed on the default active-active
SATP rule. The default multipath policy for VMW_SATP_DEFAULT_AA is VMW_PSP_FIXED (Fixed
path). The default is changed to the preferred PSP (path policy) of round-robin.
# esxcli nmp satp setdefaultpsp -s VMW_SATP_DEFAULT_AA -P VMW_PSP_RR
HP 3PAR SATP rules for use with persona 11/VMware (ALUA compliant array port presentation)
# esxcli nmp satp setdefaultpsp -s VMW_SATP_ALUA -P VMW_PSP_RR
# esxcli nmp satp addrule -s "VMW_SATP_ALUA" -c "tpgs_on" -V "3PARdata" -M "VV" -e "HP 3PAR Custom iSCSI/FC/FCoE ALUA
Rule"
To remove the above ALUA custom SATP rule:
# esxcli nmp satp deleterule -s "VMW_SATP_ALUA" -c "tpgs_on" -V "3PARdata" -M "VV" -e "HP 3PAR Custom iSCSI/FC/FCoE ALUA
Rule"
44 Configuring the Host for a Fibre Channel Connection