CAUTION: The procedure for changing the default SATP rules to use the round robin I/O multipathing policy is intended to apply only to VMware hosts using HP 3PAR StoreServ Storage LUNs. If the host is sharing storage from other vendors, then before making any I/O policy changes, consideration should be given to the effect that changing the default rules will have on the storage environment as a whole.
A change of the default PSP for a given SATP affects all storage devices (FC, FCoE, iSCSI) that use the same default SATP rule. If a host is sharing multiple storage vendors together with an HP 3PAR StoreServ Storage, and if the other connected storage does not support active/active round robin multipathing using the same SATP rule, such as VMW_SATP_DEFAULT_AA or VMW_DEFAULT_ALUA, then its multipathing will be also be affected.
If the other storage uses a different SATP of its own, then SATP VMW_SATP_DEFAULT_AA mapping should be changed to VMW_PSP_RR to take advantage of
For example, If the HP 3PAR StoreServ Storage and storage X are connected to the same host using VMW_SATP_DEFAULT_AA, and if storage X does not have its own SATP, then it might cause an issue if storage X does not support
ESX/ESXi 4.1 GA - 4.1 Ux
HP 3PAR custom SATP rule for use with persona
#esxcli nmp satp addrule
To remove the above active-active custom SATP rule:
#esxcli nmp satp deleterule
HP 3PAR custom SATP rule for use with persona 11/VMware (ALUA compliant array port presentation)
#esxcli nmp satp addrule
To remove the above ALUA custom SATP rule:
#esxcli nmp satp deleterule
ESXi 5.x
HP 3PAR custom SATP rule for use with persona
#esxcli storage nmp satp rule add