HP 3PAR Upgrade Pre-Planning Guide

NOTE: After upgrading from HP 3PAR OS 3.1.2 MU3 to 3.1.3 MU1, the passive node
hangs during a restart. This was observed with: HP 3PAR OS 3.1.3 MU1 (including patches),
Microsoft Windows Server 2012 R1 Standard Edition and HP Cluster Extension V4.0.
◦ If the boot disk without any clustered disks are presented, the system restarts correctly.
◦ If one of the clustered disks is added, the passive node hangs during the restart.
◦ If the clustered disks are added while the passive nodes are running, both the Device
Manager and Disk Manager hang during a re-scan.
To prevent this issue BEFORE upgrading to 3.1.3 MU1: Run the following command on primary
groups on both arrays.
Example: setrcopygroup pol auto_failover <group_name>
To correct this issue AFTER upgrading to 3.1.3 MU1: For the non-peer persistent group, remove
the following policies:
◦ auto_failover
Example: setrcopygroup pol no_auto_failover <group_name>
◦ path_management
Example: setrcopygroup pol no_path_management <group_name>
HP 3PAR Persistent Ports Feature
HP 3PAR OS Persistent Ports feature 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 feature is transparent to most
host-based multipathing software, which can keep all of its I/O paths active.
The HP 3PAR OS Persistent Ports feature minimizes I/O disruption during an HP 3PAR StoreServ
Storage online upgrade or node-down event (online upgrade, node restart). Port shutdown or reset
events do not trigger this feature.
NOTE: Use of HP 3PAR OS Persistent Ports feature 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)
• The HP 3PAR Command Line Interface Administrator’s Manual, “Using Persistent Ports for
Nondisruptive Online Software Upgrades”
• The appropriate HP 3PAR host OS implementation guide
HP 3PAR manuals are available on the HP Storage Information Library at:
www.hp.com/go/storage/docs
HP 3PAR OS Persona Changes
Use Table 2 (page 10) when migrating directly from HP 3PAR OS 2.2.x to HP 3PAR OS 2.3.1.
The change occurs automatically as part of the online or offline upgrade.
NOTE: VCN is disabled by default on all ports when HP 3PAR StoreServ Storage migration to
HP 3PAR OS 2.3.1 completes.
Host Configuration Guidelines 9