HP 3PAR VMware ESX Implementation Guide
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 ESX 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
- 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 SW 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
- A Appendix

Figure 18 vSphere Client
• A path policy of MRU (most recently used) does not maintain or reinstate balancing of I/O
load after a failover/failback multipath event. This could leave I/O in an unplanned for and
unbalanced state which may yield significant I/O performance issues. Implementation of an
MRU path policy is not recommended by HP.
NOTE: If I/O is active to a LUN and an attempt is made to modify the path policy, a failure can
occur, indicating:
"error during the configuration of the host: sysinfoException;
Status=Busy: Message=Unable to Set".
If this problem occurs while attempting to change the path policy, reduce the I/Os to that LUN and
then try making the desired changes.
For additional information on this topic, refer to the chapter on "Multipathing" contained in the
VMware SAN Configuration Guide at VMware.
Configuring Round Robin Multipathing on ESX 4.x or later for Fibre Channel
With ESX version 4.0 and later, VMware supports a round-robin I/O path policy for active/active
storage arrays such as HP 3PAR StoreServ Storage. A round-robin I/O path policy is the preferred
configuration for ESX 4.0 and later; however, this path policy is not enabled by default for HP 3PAR
devices.
CAUTION: If you are running Windows Server 2012 or Windows Server 2008 VM Cluster with
RDM shared LUNs, then individually change these specific RDM LUNs from Round Robin policy
to FIXED or MRU path policy.
“LUN Set to Round Robin” (page 43), which is output from a Fibre Channel configuration, shows
a LUN with a path that has been set to Round Robin (VMware).
NOTE: Note that each path status is shown as Active (I/O). The path status for an iSCSI
configuration would be the same.
42 Configuring the Host for a Fibre Channel Connection