HP 3PAR RedHat and Oracle Linux Implementation Guide

arrays, see the HP 3PAR Priority Optimization technical whitepaper, which is available on the HP
SC website:
HP 3PAR Priority Optimization
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,
or cable pull test). Port shutdown or reset events do not trigger this feature.
Each FC 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 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 multipathing 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 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
• The 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
HP 3PAR OS Persistent Ports Setup and Connectivity Guidelines for FC
Starting with HP 3PAR OS 3.1.2, the HP 3PAR OS Persistent Ports feature is supported for FC
target ports.
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.
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
preferably to different FC switches on the fabric.
• 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”).
FCoE-to-FC Connectivity
The following figures show a basic diagram of FCoE-to-FC connectivity.
FCoE-to-FC Connectivity 17