HP 3PAR VMware ESX Implementation Guide

and starting point for further optimization of IO throughput with PSP Round-Robin. With the exception
of ESX/ESXi 4.0 versions, it is preferable to set the IOPS value within a SATP custom rule.
CAUTION: VMware specifically warns not to directly edit the esx.conf file.
NOTE:
• The setting of IOPs=1 is a new recommended initial value as documented in the HP technical
white paper HP 3PAR StoreServ Storage and VMware vSphere 5 Best Practice (HP document
#4AA4–3286ENW). You can change this setting to suit the demands of various workloads.
• SATP rule changes cannot be affected through vSphere GUI.
• SATP rule changes through esxcli commands populate the esx.conf file.
• A custom SATP rule is an additional SATP rule that either modifies or redefines parameters of
an existing SATP default rule, defines the targeted devices affected, and has a unique custom
rule name.
• A custom SATP rule cannot be changed or edited. A custom SATP rule must be removed before
creating a new one with the changes added to affect a change in the parameters of the custom
rule.
• SATP and PSP creation, changes, additions, or removals take effect for any new devices
presented afterward without the need for server reboot.
• The host must be rebooted for SATP rule creation, changes, additions, or removals to take
effect on existing, previously presented devices.
• Path policy changes done on an individual device basis, either done via vCenter or esxcli
command, supersede the PSP path policy defined in a SATP rule, and such path policy changes
to individual devices are maintained through host reboots.
• Valid PSP for SATP VMW_SATP_DEFAULT_AA rules are:
◦ VMW_PSP_RR
◦ VMW_PSP_FIXED
◦ VMW_PSP_MRU
VMW_PSP_RR is preferred.
• Valid PSP for SATP VMW_SATP_ALUA rules are:
◦ VMW_PSP_RR
◦ VMW_PSP_MRU
VMW_PSP_FIXED is not a valid PSP to be defined within an ALUA SATP rule. VMW_PSP_RR
is preferred.
Changing from HP 3PAR host persona 6/Generic-legacy to host persona 11/VMware or vice
versa:
• A change from persona 6 to 11, or from persona 11 to 6, the HP 3PAR OS requires either
taking the affected array ports offline, or disconnecting the host for which the persona is being
changed.
• For existing devices targeted in a custom SATP rule to be claimed by the rule, the ESX/ESXi
OS requires a host reboot.
HP recommends using the following procedure to change from persona 6 to 11, or from persona
11 to 6:
Multipath Failover Considerations and I/O Load Balancing 43