HP 3PAR Upgrade Pre-Planning Guide

• The HP 3PAR System Reporter requires an upgrade to be compatible with HP 3PAR OS 3.1.1
or later. When you upgrade the HP 3PAR StoreServ Storage to HP 3PAR OS 3.1.1 or later,
you must then upgrade the HP 3PAR System Reporter CLI to HP 3PAR OS 3.1.1 or later. (If
you upgrade the HP 3PAR System Reporter CLI first, and then upgrade to HP 3PAR OS 3.1.1
or later, HP 3PAR System Reporter will detect only the previous version of HP 3PAR OS.)
• The HP 3PAR Management Console is generally compatible with all HP 3PAR OS 2.2.4,
2.3.1, 3.1.1, 3.1.2, and 3.1.3 versions. For the latest features and fixes, it is advisable to
upgrade to the current HP 3PAR Management Console release.
• For hosts running HP 3PAR Cluster Extension (CLX) software that are being upgraded to HP
3PAR OS 3.1.1, the HP 3PAR OS 2.3.1 CLI must be run on all nodes in the HP 3PAR Cluster
CLX. Do not upgrade the CLI on those nodes to 3.1.1 CLI. However, if you upgrade to HP
3PAR OS 3.1.1 MU1, you can upgrade the nodes to 3.1.1 MU1 CLI.
For hosts running HP 3PAR Cluster CLX that are being upgraded to HP 3PAR OS 3.1.1 MU1,
the host CLI must be upgraded to the HP 3PAR OS 3.1.1 MU1 CLI before the HP 3PAR
StoreServ Storage is upgraded to HP 3PAR OS 3.1.1 MU1.
CAUTION: When upgrading to HP 3PAR OS 3.1.1 MU1, you must upgrade the HP 3PAR
OS CLI to HP 3PAR OS 3.1.1 MU1 on any node attached to the array. Otherwise, HP 3PAR
Cluster CLX will fail to perform failover/failback operations on HP 3PAR Remote Copy volume
groups or other applications.
For an upgrade to HP 3PAR OS 3.1.3, host-based applications must be upgraded to the latest
version in the order specified by the HP 3PAR OS upgrade instructions.
HP 3PAR Persistent Ports
HP 3PAR OS Persistent Ports allows an HP 3PAR StoreServ Storage 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 supported 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 reboot). 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 Support Center website:
HP Support Center
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.
Host Configuration Guidelines 9