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
HP 3PAR OS Persistent Ports
The HP 3PAR OS Persistent Ports (or virtual ports) feature minimizes I/O disruption during an
HP 3PAR StoreServ Storage online upgrade or node-down event (online upgrade, node reboot).
Port shutdown or reset events do not trigger this feature.
Each FC, FCoE, or iSCSI target storage array port has a partner array port automatically assigned
by the system. Partner ports are assigned across array node pairs.
HP 3PAR OS Persistent Ports allows an HP 3PAR StoreServ Storage FC, FCoE, or iSCSI port to
assume the identity (port IP address) of a failed port while retaining its own identity. Where a given
physical port assumes the identity of its partner port, the assumed port is designated as a persistent
port. Array port failover and failback with HP 3PAR OS Persistent Ports is transparent to most
host-based multipathing software, which can keep all of its I/O paths active.
NOTE: Use of HP 3PAR OS Persistent Ports technology does not negate the need for properly
installed, configured, and maintained host multi-pathing software.
For a more complete description of the HP 3PAR OS Persistent Ports feature, its operation, and a
complete list of required setup and connectivity guidelines, see the following:
• HP Technical white paper HP 3PAR StoreServ Persistent Ports (HP document
#F4AA4-4545ENW)
This document is available on the following HP SC website:
HP Support Center
• HP 3PAR Command Line Interface Administrator’s Manual, “Using Persistent Ports for
Nondisruptive Online Software Upgrades”
This document is available on the following HP SC website:
HP Support Center
Fibre Channel
Starting with HP 3PAR OS 3.1.2, the HP 3PAR OS Persistent Ports feature is supported for FC
target ports.
The Persistent Ports feature is enabled by default for HP 3PAR StoreServ Storage FC ports starting
with HP 3PAR OS 3.1.2 software and later.
Starting with HP 3PAR OS 3.1.3, the Persistent Port feature has additional functionality to minimize
I/O disruption during an array port “loss_sync” event triggered by a loss of array port connectivity
to fabric.
HP 3PAR OS Persistent Ports Setup and Connectivity Guidelines for FC
Specific cabling setup and connectivity guidelines need to be followed for HP 3PAR OS Persistent
Ports to function properly:
• HP 3PAR StoreServ Storage FC partner ports must be connected to the same FC Fabric and
switch.
• The FC fabric being used must support NPIV, and NPIV must be enabled.
• The host–facing HBAs must be configured for point-to-point fabric connection (there is no
support for direct-connect “loops”).
14 Configuring the HP 3PAR StoreServ Storage for Fibre Channel