User's Manual
Table Of Contents
- HP 3PAR VMware ESX Implementation Guide
- Contents
- 1 Introduction
- 2 Configuring the HP 3PAR StoreServ Storage for Fibre Channel
- 3 Configuring the HP 3PAR StoreServ Storage for iSCSI
- 4 Configuring the HP 3PAR StoreServ Storage for FCoE
- 5 Configuring the Host for a Fibre Channel Connection
- Installing the HBA and Drivers
- Installing Virtual Machine Guest Operating System
- Multipath Failover Considerations and I/O Load Balancing
- Performance Considerations for Multiple Host Configurations
- ESX/ESXi 4.1, ESXi 5.x Additional Feature Considerations
- Storage I/O Control
- vStorage APIs for Array Integration (VAAI)
- HP 3PAR VAAI Plugin 1.1.1 for ESXi 4.1
- HP 3PAR VAAI Plugin 2.2.0 for ESXi 5.x
- UNMAP (Space Reclaim) Storage Hardware Support for ESXi 5.x
- Out-of-Space Condition for ESX 4.1 and ESXi 5.x
- Additional New Primitives Support on ESXi 5.x
- VAAI and New Feature Support Table
- VAAI Plugin Verification
- VMware All Paths Down
- 6 Configuring the Host as an FCoE Initiator Connecting to a FC target or an FCoE Target
- 7 Configuring the Host for an iSCSI Connection
- Setting Up the Switch, iSCSI Initiator, and iSCSI target ports
- Installing iSCSI on VMware ESX
- Installing Virtual Machine Guest Operating System
- Creating a VMkernel Port
- Configuring a Service Console Connection for the iSCSI Storage
- Configuring the VMware iSCSI Initiator
- iSCSI Failover Considerations and Multipath Load Balancing
- Performance Considerations for Multiple Host Configurations
- ESX/ESXi Additional Feature Considerations
- 8 Allocating Storage for Access by the ESX Host
- 9 Booting the VMware ESX Host from the HP 3PAR StoreServ Storage
- 10 Support and Other Resources
- 11 Documentation feedback
ESX/ESXi 4.0 GA - 4.0 Ux
NOTE:
• Though 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 wherein no attempt should be made to change iops
from its default value of 1000 (iops = 1000). If the iops value is changed, upon the next
host reboot, an invalid value for iops is picked up and iops are then 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"
42 Configuring the Host for a Fibre Channel Connection