HP 3PAR Operating System Upgrade

HP 3PAR Operating System UpgradePre-Planning Guide

AbstractThis guide is intended for use as a planning tool for HP customers who are system and storage administrators. It provides thefollowing information about HP 3PAR Operating System software upgrades:

An overview of the online and offline upgrade processes for the HP 3PAR OS

Prerequisites for online upgrades

Guidelines for online upgrades

Planning information needed for online upgrades

Veritas Dynamic Multipathing (DMP) prerequisites for online upgrades

Remote versus local methods of upgrading

HP Part Number: QL226-97856Published: July 2014

Copyright 2014 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial

Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under

vendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express

warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall

not be liable for technical or editorial errors or omissions contained herein.

Acknowledgments

Windows is a U.S. registered trademark of Microsoft Corporation.

Contents1 HP 3PAR OS Upgrade Overview..................................................................4

Audience.................................................................................................................................4Supported Upgrade Types.........................................................................................................5

2 Guidelines for Online Upgrades...................................................................6Planning Information for Online HP 3PAR OS Upgrades................................................................6General Guidelines...................................................................................................................6Host Configuration Guidelines....................................................................................................7

HP 3PAR Persistent Ports Feature.............................................................................................9HP 3PAR OS Persona Changes..............................................................................................9

HP 3PAR StoreServ Storage Configuration Guidelines..................................................................13HP 3PAR Remote Copy Guidelines............................................................................................14Remote Versus Local Methods for an HP 3PAR OS Upgrade.........................................................15

Remote HP 3PAR OS Upgrades...........................................................................................15Local HP 3PAR OS Upgrades..............................................................................................16

Start-and-Stop Quorum Witness Steps........................................................................................16

3 Red Hat, Oracle, Linux, and SUSE Guidelines..............................................184 Sun/Solaris Configuration Guidelines.........................................................19

I/O Path Monitoring for Solaris................................................................................................19

5 Symantec Veritas Storage Foundation DMP (VxDMP) and Online Upgrade......22Changing the Veritas DMP Link Restore Interval...........................................................................22Restoring the Veritas DMP Link Restore Interval............................................................................23

6 VMware ESX Server Guidelines..................................................................247 Windows Server OS Guidelines.................................................................25

Rebooting After an Upgrade....................................................................................................25Microsoft MPIO Driver on Windows Server 2008.......................................................................26Microsoft Hotfixes...................................................................................................................27HP Peer Motion Manager........................................................................................................27

8 AIX Guidelines.........................................................................................299 HP-UX Guidelines.....................................................................................30

Issue.....................................................................................................................................31Resolution..............................................................................................................................31

10 Support and Other Resources...................................................................33Contacting HP........................................................................................................................33HP 3PAR documentation..........................................................................................................33Typographic conventions.........................................................................................................36HP 3PAR branding information.................................................................................................36

11 Documentation feedback..........................................................................37

Contents 3

1 HP 3PAR OS Upgrade OverviewThis guide provides the following information on HP 3PAR Operating System (HP 3PAR OS) softwareupgrades:

An overview of the online and offline upgrade processes for the HP 3PAR OS

Prerequisites for online upgrades

Guidelines for online upgrades

Planning information needed for online upgrades

Veritas DMP prerequisites for online upgrades

Remote versus local methods of upgrading

The HP 3PAR StoreServ Storage supports two different methods for upgrading the HP 3PAR OS:online and offline. The upgrades can be performed with a service representative on-site or remotely(from HP). Remote upgrades require that remote operations are available.

CAUTION: When upgrading HP 3PAR Storage Systems from HP 3PAR OS 3.1.2 MU3 to HP3PAR OS 3.1.3 MU1 with Remote Copy groups using non-peer persistent VLUNs for Windows2012 host clusters, the passive node hangs during node restart.

NOTE: The HP 3PAR OS 3.1.x is a 64-bit operating system. Upgrades to the following HP 3PARstorage systems are supported:

HP 3PAR F-Class

HP 3PAR T-Class

HP 3PAR StoreServ 7000 Storage system

HP 3PAR StoreServ 10000 Storage system

NOTE: HP recommends updating host drivers to a supported level of the targeted HP 3PAR OSupgrade version before attempting an online upgrade. This information is available on the HPSingle Point of Connectivity (HP SPOCK) website at:www.hp.com/storage/spockThese documents are provided to assist you in setting up host servers with HP-supported configurationinformation.In addition to this planning document, the HP 3PAR host OS implementation guides are availableon the HP Storage Information Library at:www.hp.com/go/storage/docsHP recommends checking the compatibility information for HP CloudSystem Matrix versions on theHP CloudSystem Matrix Compatibility website:HP CloudSystem Matrix Compatibility

NOTE: HP 3PAR Remote Copy between HP 3PAR OS 2.3.1 systems and HP 3PAR OS 3.1.3systems is not supported.

AudienceThis guide is intended for use as a planning tool for HP customers and for system and storageadministrators who monitor and direct system configurations and resource allocation for HP 3PARStoreServ Storage systems. The tasks and information described in this document assume that theadministrator is familiar with host operating system platforms and the HP 3PAR OS. The appropriateHP 3PAR documentation must be consulted in conjunction with the host and host bus adapter (HBA)vendor documentation for specific details and procedures of system configuration.

4 HP 3PAR OS Upgrade Overview

NOTE: This guide is not intended to reproduce any third-party product documentation. For detailsabout devices such as host servers, HBAs, converged network adapters (CNAs), fabric switches,and non-HP 3PAR software management tools, consult the appropriate third-party documentation.

Supported Upgrade TypesHP 3PAR OS upgrades are performed either online or offline. Online upgrades allow the hostsconnected to the system to continue I/O activity; for offline upgrades, host I/O activity must bestopped. The following types of upgrades are supported:Node-by-Node online upgrade Used for HP 3PAR OS maintenance updates (for example,

HP 3PAR OS 3.1.1 MU1 to 3.1.1 MU2). As of HP 3PAROS 3.1.1, all online upgrades are node-by-node. Each arraynode is upgraded one at a time. A simple or autonode-by-node upgrade occurs with each node upgraded inan HP 3PAR OS predetermined sequence and timing. Anadvanced or manual node-by-node upgrade occurs whenthe node sequence and timing between individual arraynode upgrades are determined by the personneladministrating the online upgrade.

Offline upgrade Used when the customer requests an offline upgrade, orwhen the system is operating several levels below theupgrade package version. If the system is operating severallevels below the upgrade package version, it may be easierto perform the upgrade without all the system checksrequired for online upgrades. All nodes are upgraded, thenrestarted at the same time. The system is unavailable to thehosts during this operation.

The following table lists the supported HP 3PAR OS-level upgrade types.

Table 1 Upgrade Types

Upgrade TypeUpgrade to New HP 3PAR OS LevelUpgrade from Current HP 3PAR OS Level

Node-by-node online3.1.1 MU23.1.1 GA

Node-by-node online3.1.2 GA3.1.1 MU2

Node-by-node online13.1.3 MU13.1.2 GA

Node-by-node online3.1.3 MU13.1.2 MUx

1 When remote-copy groups are started, only online upgrades from HP 3PAR OS 3.1.2.x to HP 3PAR OS 3.1.3 MU1 aresupported.To upgrade from HP 3PAR OS 3.1.1.x to HP 3PAR OS 3.1.3 MU1, you must perform a multihop upgrade, first to HP3PAR OS 3.1.2.MUx, and then to HP 3PAR OS 3.1.3 MU1.

WARNING! For an upgrade from HP 3PAR OS 3.1.1 MU1 to HP 3PAR OS 3.1.2 GA or later,it is no longer necessary to stop HP 3PAR Remote Copy groups when doing an online upgrade.For an upgrade from HP 3PAR OS 3.1.1GA to a later version Remote Copy groups must bestopped.For HP 3PAR StoreServ Storage systems licensed with HP 3PAR Remote Copy software, do notupgrade directly from HP 3PAR OS 2.2.4 to HP 3PAR OS 3.1.1 or later. These upgrade conditionsare not supported and will fail. See HP 3PAR Remote Copy Guidelines (page 14)

Supported Upgrade Types 5

2 Guidelines for Online UpgradesFollow the guidelines in this chapter for online HP 3PAR OS upgrades.

Planning Information for Online HP 3PAR OS UpgradesThe host connectivity environment must adhere to the qualified and supported environments. Formore information, see the interoperability information on the HP SPOCK website.HP service representatives will request this information for review before performing an onlineupgrade. Relevant details include:

Host platform

Architecture (for example, SPARC/x86)

Operating system (version and patch level)

Host multipath software

HBA and CNA (vendor, model, driver, firmware, and version. Also include FCODE and BIOSlevel if booting from the HP 3PAR StoreServ Storage)

Switch (vendor, model and firmware)

Information on host software provided by HP is needed. Examples include: HP 3PAR RecoveryManager (SQL, Exchange, Oracle), HP 3PAR VSS Provider, HP 3PAR MPIO for MicrosoftWindows, HP 3PAR ODM Definition for IBM AIX, HP 3PAR System Reporter, and so on

NOTE: For hosts running AIX and using HP 3PAR MPIO 2.2, upgrade to HP 3PAR ODM3.1 before upgrading from HP 3PAR OS 2.3.1 to HP 3PAR OS 3.1.x. See HP 3PAR ODM3.1 Software for IBM AIX Readme (QL226-96076) for upgrade procedures on the HP SPOCKwebsite.

In addition to verifying that the driver and firmware levels match the information in HP SPOCK,there may be host configuration settings needed as documented in the HP 3PAR host OSimplementation guides. Verify these settings before performing an online upgrade.

Detailed information about drivers, configurations, and interoperability is available on the HPSPOCK website.HP 3PAR host OS implementation guides are available on the HP Storage Information Library:www.hp.com/go/storage/docs

General GuidelinesHP provides the following host software:

HP 3PAR Recovery Manager (SQL, Exchange, Oracle, VMware)

HP 3PAR VSS Provider

HP 3PAR MPIO for Microsoft Windows

HP 3PAR ODM Definition for IBM AIX

HP 3PAR System Reporter

6 Guidelines for Online Upgrades

Observe the following general guidelines according to online HP 3PAR OS updates:

WARNING! All hosts must comply with the current applicable HP 3PAR host OS implementationguides for the target HP 3PAR OS level. Hosts that do not comply completely with the implementationguides may lose connectivity during the HP 3PAR OS upgrade.

Do not perform hardware and configuration changes on the HP 3PAR StoreServ Storageduring the update. For example, software operations (such as servicemag, createvv, oruse of the HP 3PAR StoreServ Storage tuner commands) and hardware operations (such asadding or removing drives and cages) are prohibited during the online update process. Alllogical disk growth operations for common provisioning groups continue uninterrupted asunder normal operation.

Host and environment changes are not allowed during an online upgrade (for example,rebooting, applying patches, or rezoning switches). The upgrade software checks for theexistence of hosts before and after each step, and if host connections do not reappear aftereach step, the upgrade process reverts to the original level.

Any automated processes that communicate with the HP 3PAR StoreServ Storage managementinterface (scripting) must be stopped before performing an online upgrade.

Online upgrades should be scheduled and performed during periods of low I/O activity.System resources are placed offline to be upgraded, system utilization must be lower than50% for each node and I/O port.

Host Configuration GuidelinesObserve the following host configuration guidelines when planning an online HP 3PAR OS upgrade:

Multipathing cabling must adhere to HP 3PAR configuration rules: each defined host musthave at least two operational paths attached to two adjacent nodes. That is, an even-numberednode followed by a consecutive odd-numbered node.Example of Valid pairings:

0 & 1

2 & 3

4 & 5

6 & 7Example of Invalid pairings:

2 & 1

0 & 3

All attached hosts must have multipathing software configured and operational for every HP3PAR storage server volume exported. Hosts must connect to two adjacent nodes, aneven-numbered node followed by a consecutive odd-numbered node on the HP 3PAR StoreServStorage system.Example of Valid pairings:

0 & 1

2 & 3

4 & 5

6 & 7

Host Configuration Guidelines 7

NOTE:

See HP SPOCK streams, on the HP SPOCK website, for supported multipathingenvironments.

For unsupported environments, the hosts should be shut down and in some cases poweredoff. The VLUNs exported to such hosts must be unexported or connections must be logicallydisconnected before the online HP 3PAR OS upgrade.

A host definition must not contain initiators from multiple hosts. For example, host clusterconfigurations must use a separate host definition for each host in the host cluster.

Stop all system administration activities during an HP 3PAR OS online upgrade. Complete orstop all active tasks before proceeding. This includes any provisioning activity, physical copyactivity, virtual copy activity, and dynamic optimization. Stop any automated administrationscripts such as Recovery Manager and VSS Provider for Microsoft Windows.

iSCSI hosts must have active I/O on all paths during the upgrade. The upgrade process rebootsnodes and checks that all hosts are reconnected after each node reboots. The upgrade willnot advance until all hosts re-establish connection. An idle iSCSI host will not reconnect, it isimportant to have I/O on all paths during the upgrade.

The recovery manager for Oracle, SQL, Exchange or VMware may require a newer versionto be compatible to HP 3PAR OS 3.1.1 or later. See the interoperability information on theHP SPOCK website for HP 3PAR OS 3.1.x for supported levels.

An upgraded CLI client for HP 3PAR OS 3.1.1 MU1 or later must be installed on the recoverymanager host. See the HP SPOCK website for information about HP 3PAR OS 3.1.x forsupported levels and host compatibility.

Verify compatibility of any host third-party software to the HP 3PAR OS release 3.1.x.

The HP 3PAR System Reporter requires an upgrade to be compatible with HP 3PAR OS 3.1.x.When you upgrade the HP 3PAR StoreServ Storage to HP 3PAR OS 3.1.x, upgrade the HP3PAR System Reporter application compatible with 3.1.x as mentioned in HP SPOCK withthe bundled HP 3PAR System Reporter CLI Remote Client.

The HP 3PAR Management Console is generally compatible with all HP 3PAR OS 2.3.1,3.1.1, 3.1.2, and 3.1.3 MU1 versions. For the latest features and fixes, it is advisable toupgrade to the current HP 3PAR Management Console release.

For hosts running HP 3PAR Cluster Extension (CLX) software upgrading 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 CLX. Do not upgrade theCLI on those nodes to 3.1.1 CLI. However, if you upgrade to HP 3PAR OS 3.1.1 MU1, youcan upgrade the nodes to 3.1.1 MU1 CLI.For hosts running HP 3PAR CLX upgrading to HP 3PAR OS 3.1.1 MU1, upgrade the host CLIto the HP 3PAR OS 3.1.1 MU1 CLI before the HP 3PAR StoreServ Storage is upgraded to HP3PAR OS 3.1.1 MU1.

CAUTION: When upgrading to HP 3PAR OS 3.1.1 MU1, you must upgrade the HP 3PAROS CLI to HP 3PAR OS 3.1.1 MU1 on any node attached to the array. Otherwise, HP 3PARCLX fails to perform failover/failback operations on HP 3PAR Remote Copy volume groupsor other applications.For an upgrade to HP 3PAR OS 3.1.3, host-based applications must be upgraded to the latestversion in the order specified by the HP 3PAR OS upgrade instructions.


NOTE: After upgrading from HP 3PAR OS 3.1.2 MU3 to 3.1.3 MU1, the passive nodehangs 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 DeviceManager and Disk Manager hang during a re-scan.

To prevent this issue BEFORE upgrading to 3.1.3 MU1: Run the following command on primarygroups on both arrays.Example: setrcopygroup pol auto_failover To correct this issue AFTER upgrading to 3.1.3 MU1: For the non-peer persistent group, removethe following policies:

auto_failoverExample: setrcopygroup pol no_auto_failover

path_managementExample: setrcopygroup pol no_path_management

HP 3PAR Persistent Ports FeatureHP 3PAR OS Persistent Ports feature allows an HP 3PAR StoreServ Storage FC port to assume theidentity (port IP address) of a failed port while retaining its own identity. Where a given physicalport 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 mosthost-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 StoreServStorage online upgrade or node-down event (online upgrade, node restart). Port shutdown or resetevents 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 acomplete 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 Administrators Manual, Using Persistent Ports forNondisruptive 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 ChangesUse 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 toHP 3PAR OS 2.3.1 completes.


Table 2 Persona Translation Table

HP 3PAR OS 2.3.1HP 3PAR OS 2.2.x

Host PersonaTopologyPort PersonaTopology

(No persona) - Loop0 - Loop

6 (Generic - Legacy) - Loop1, 2, 3, 4 - Loop

7 (HP-UX - Legacy) - Loop5 (HP-UX) - Loop

6 (Generic - Legacy) - Point7, 9, 10, 15 - Point

7 (HP-UX -Legacy) - Point8 (HP-UX) - Point

9 (Egenera) - Loop11 (Egenera) - Loop

9 (Egenera) - Point12 (Egenera) - Point

8 (AIX - Legacy) - Loop13 (AIX) - Loop

8 (AIX - Legacy) - Point14 (AIX) - Point

10 (ONTAP - Legacy) - Loop18 (NetApp) - Loop

10 (ONTAP - Legacy) - Point19 (NetApp) - Point

(No persona) - Loop16 (RCFC) - Loop

(No persona) - Point17 (RCFC) - Point

6 (Generic - Legacy)All iSCSI configurations

See Table 3 (page 10) for host persona capabilities in HP 3PAR OS 3.1.3 MU1.

Table 3 Host Persona Capabilities Defined in HP 3PAR OS 3.1.3 MU1

Persona CapabilitiesPersona NamePersona ID

UARepLun, SESLunGeneric1

UARepLun, SESLun, ALUAGeneric - ALUA2

Generic - legacy6

VolSetAddr, Lun0SCCHP-UX - legacy7

NACAAIX - legacy8

SoftInqEGENERA9

SoftInqONTAP - legacy10

SubLun, ALUAVMware11

UARepLun, RTPG, SESLun, Lun0SCCOpenVMS12

UARepLun, VolSetAddr, SESLun, ALUA,Lun0SCC

HP-UX13

UARepLun, SESLun, ALUA, WSCWindows Server15

See Table 4 (page 10) for host persona capabilities in HP 3PAR OS 3.1.2 MU3.

Table 4 Host Persona Capabilities Defined in HP 3PAR OS 3.1.2 MU3


UARepLun, SESLunGeneric1

UARepLun, RTPG, SESLunGeneric - ALUA2


Table 4 Host Persona Capabilities Defined in HP 3PAR OS 3.1.2 MU3 (continued)


Generic - legacy6

VolSetAddr, Lun0SCCHP-UX - legacy7

NACAAIX - legacy8

SoftInqEGENERA9

SoftInqONTAP - legacy10

SubLun, ALUAVMware11

UARepLun, RTPG, Lun0SCCOpenVMS12

Once the HP 3PAR StoreServ Storage is running HP 3PAR OS 2.3.1 or later, it is recommendedthat the host persona for some of the hosts be changed. See Table 5 (page 12) .The table also reflects some changes in host persona for HP 3PAR OS 3.1.2 and HP 3PAR OS3.1.3 MU1 with Windows Servers, VMware ESX OS, Red Hat and SUSE.


Table 5 Host Persona Details Table

HP 3PAR OS 3.1.3MU1 Host Persona

HP 3PAR OS 3.1.2Host Persona

HP 3PAR OS3.1.1 HostPersona

HP 3PAR OS 2.3.1 HostPersona

Operating System

8888AIX

7777HP-UX 11i v1 and 11i v2

71777HP-UX 11i v3

13

10101010NetApp/ONTAP

14111 or 6RHEL 5.8, 6.1 and later2, 3

2

1116RHEL 4 and RHEL 52

14111 or 6SLES 10.4, 11.3 and later 2, 3

2

1116SUSE 10FC and iSCSI2

2666SUSE 11FC and iSCSI 2, 3

1116Solaris 9, Solaris 10,including iSCSI2

2226Solaris 11, including iSCSI2

n/a7n/a7n/a766VMware ESX 3.55

1191196666VMware ESX 4.X8

6666

1191196666VMware ESX 5.0, 5.1, and5.5 6666

1116Windows Server 20033,including iSCSI2

1511226Windows Server 2008 SP1and SP2, including iSCSI10

151121316Windows Server 2008 R212,including iSCSI

15112n/an/aWindows Server 2012

Windows Server 2012 R2

1 HP recommends host persona 13 for HP-UX 11i v3 with HP 3PAR OS 3.1.3 MU1 and later. Changing from host persona7 to host persona 13 can be performed with the host online.

2 Use of generic persona allows the host server to run Host Explorer on the host. It will automatically create LUN 254as a SCSI enclosure device for Host Explorer use.

3 Starting with HP 3PAR OS 3.1.3 MU1, host persona 2, which has asymmetric LUN unit access (ALUA), is supported.HP Recommends host persona 2 for RHEL 5.8, RHEL 6.1, SLES 10.4 , SLES 11.3 and later with HP 3PAR OS 3.1.3 MU1and later. Changing from host persona 1 to host persona 2 is an offline process. This change applies to hosts connectingto the array through FC, FCoE, or iSCSI. For more details, see the HP 3PAR host OS implementation guide specific tothis OS.

4 HP recommends host persona 2 for RHEL 5.8, RHEL 6.1, SLES 10.4 , SLES 11,3 and later with HP 3PAR OS 3.1.3 MU1and later. Changing from host persona 1 to host persona 2 is an offline process.

5 VMware ESX 3.5 is not supported in HP 3PAR OS 3.1.1 or later.


6 Host persona 6 will not be supported for any version of VMware ESX/ESXi with future HP 3PAR OS versions after HP3PAR OS 3.1.3 MU1 and its MUs. HP recommends that customers migrate their VMware ESX configurations on HP3PAR to Host Persona 11 with HP 3PAR OS 3.1.2 or later.

7 VMware ESX 3.5 is not supported in HP 3PAR OS 3.1.1 or later.8 As of VMware ESX 4.0, a change of the SATP rules on hosts to enable active/active round robin by default isrecommended. See the HP 3PAR VMware ESX Implementation Guide for instructions about changing the VMwareESX/ESXi SATP rules. To obtain this document, see the HP Storage Information Library:www.hp.com/go/storage/docs

9 HP recommends host persona 11 for all supported VMware ESX versions with HP 3PAR OS 3.1.2 and later. Changingthe persona from 6 to 11 for existing Persona 6 hosts is an offline process.

10 Enabling host persona 2 will enable A/A multipath on LUNs by default. This change will require a restart. Do not changethe host persona unless you can restart the Windows Server 2008. If you do not restart the server, the host will lose themapping of the LUNs.

11 From HP 3PAR OS 3.1.3 MU1, HP requires host persona 15 for Windows Server2012 R2, Windows Server 2012, andWindows Server 2008 R2 and non-R2 hosts. However, host persona 2 is automatically assigned following an onlineHP 3PAR OS upgrade from OS version 3.1.2. After such an upgrade, you must change host persona 2 to host persona15. Before changing host personas, see Windows Server OS Guidelines (page 25) for instructions to prevent loss ofLUN mapping.

12 Microsoft enables A/A multipathing by default at Windows Server 2008 R2.13 For Windows Server 2008 R2, configurations of persona 6 and 1 need to be changed manually to persona 2 after anupgrade to HP 3PAR OS 3.1.2. The Windows Server host needs to be shut down when the persona change is performedand then brought back online in order to properly configure the ALUA paths support in persona 2.

To change the host persona of a host:

cli% sethost persona

List of host persona's available on an HP 3PAR OS release:

cli% showhost -listpersona

To verify the host persona setting of a host:

cli% showhost persona

NOTE: Hosts that are offline or powered down during an upgrade from HP 3PAR OS 2.2.4 toHP 3PAR OS 2.3.1 are assigned host persona 6 by the upgrade operation. This default persona6 assignment would prevent HP-UX, AIX, and NetApp hosts from operating correctly. Therefore,explicit action is required by the user to set the persona for such hosts according to the personaguidance in Table 5 (page 12).

HP 3PAR StoreServ Storage Configuration GuidelinesThe following guidelines must be observed when planning an online HP 3PAR OS upgrade.

The HP 3PAR StoreServ Storage must be in a healthy state (with no failed or degradedphysical disks, cages, FCALs, nodes, etc.). The HP 3PAR OS upgrade software performs anautomated check and, if the system is not in a healthy condition, causes the upgrade to fail.

A VLUN for each exported volume must be exported to a defined host on at least two fullyoperational paths that span adjacent storage server nodes, an even-numbered node followed

HP 3PAR StoreServ Storage Configuration Guidelines 13

by a consecutive odd-numbered node, on the HP 3PAR StoreServ Storage. (Valid pairings are0 & 1, 2 & 3, 4 & 5, 6 & 7.)

HP 3PAR software applications running on the HP 3PAR StoreServ Storage must be shut down.

Ensure that no HP 3PAR Virtual Copy promotes are in progress. To confirm, check that novolumes are in the started, cpp state. If any promotes are in progress, wait until thepromote finishes to begin the online upgrade.

HP 3PAR Remote Copy GuidelinesWhen planning HP 3PAR OS upgrades where HP 3PAR Remote Copy software is configured, thefollowing rules apply:

It may not be feasible to upgrade all storage systems participating in the HP 3PAR RemoteCopy configuration at the same time, the allowed change between major versions of the HP3PAR OS release is limited to 1 adjacent major release level, that is, from HP 3PAR OS 3.1.2to 3.1.3 MU1. All maintenance update (MU) levels are considered to be in the same majorOS version. Examples:

Support is provided for a maximum of 5 weeks between major version changes.

A change of HP 3PAR OS versions 2.3.1 and 3.1.1 is supported for a period of 5 weeks.

Conversely, an upgrade from HP 3PAR OS 3.1.1 to HP 3PAR OS 3.1.3 MU1 is notsupported, because these are not adjacent.

HP 3PAR StoreServ Storage systems in the HP 3PAR Remote Copy configuration must beupgraded to the same major OS version, as shown in Table 6 (page 14).

Table 6 Remote Copy Upgrades to HP 3PAR OS 3.1.3 MU1

Upgrade TypeUpgrade from HP 3PAR OS

Multihop upgrade12.3.1

Multihop upgrade13.1.1

Direct upgrade3.1.21 Multihop upgrades must be performed within a 5-week period.For more information about supported upgrades, see Supported Upgrade Types (page 5).

NOTE: The E-Class and S-Class storage systems do not support HP 3PAR OS 3.1.1 or later,therefore, they are exempt from the 5-week rule and may continue to run HP 3PAR OS version2.3.1 in a HP 3PAR Remote Copy configuration with the HP 3PAR StoreServ 10000 Storagesystem, T-Class, or F-Class storage systems running HP 3PAR OS version 3.1.1 only.

WARNING! For HP 3PAR StoreServ Storage systems licensed with HP 3PAR Remote Copy, directupgrade is not supported from 2.2.4 to 3.1.1 or later. See Table 7 (page 15)

For systems running HP 3PAR OS 2.2.4 or later with HP 3PAR Remote Copy, only the groupsneed to be stopped. Stop the remote copy groups after the synchronization has completedvia stoprcopygroup group name/s.For details about using the stoprcopygroup command, see the HP 3PAR Remote CopyUser Guide. To obtain this document, see the HP Storage Information Library:www.hp.com/go/storage/docs

HP 3PAR OS 2.2.4 systems with HP 3PAR Remote Copy cannot be upgraded directly to HP3PAR OS 3.1.1 and later. HP 3PAR OS 2.2.4 systems with HP 3PAR Remote Copy must be


upgraded to HP 3PAR OS 2.3.1 MU5 before an upgrade to HP 3PAR OS 3.1.3. (includingoffline upgrades).

When an upgrade to HP 3PAR OS 3.1.1 is performed, HP 3PAR Remote Copy Ethernet portsmust be set to autonegotiate. If they were changed to 100 Mbs full duplex, the links maynot start The autonegotiate setting can be changed in advance of a software upgrade byissuing the following command:

# controlport rcip speed auto

This should be performed on one remote-copy link at a time, making sure to check that thelink is working before setting the other link to autonegotiate.

Table 7 HP 3PAR Remote Copy Support

Supported?HP 3PAR OS Level System BHP 3PAR OS Level System A

Yes2.3.1.nnn2.2.4.nnn

Yes (S-class and E-class systems only)3.1.1.nnn2.3.1.nnn

No3.1.1.nnn2.2.4.nnn


No3.1.3.nnn3.1.1.nnn


WARNING! When HP 3PAR Remote Copy software is configured, direct upgrades performeddirectly from all levels of HP 3PAR OS 2.2.4 to HP 3PAR OS 3.1.1 will fail. This holds true foroffline upgrades and instances when HP 3PAR Remote Copy is simply disabled. For these upgrades,you must first upgrade to HP 3PAR OS 2.3.1 MU5, and only then proceed to upgrade to HP 3PAROS 3.1.1 MU2. In addition, you should not enable HP 3PAR Remote Copy between HP 3PARStoreServ Storage system running HP 3PAR OS 2.2.4 and other HP 3PAR StoreServ Storage systemsrunning HP 3PAR OS 3.1.1.

For details about using HP 3PAR Remote Copy, see the HP 3PAR Remote Copy User Guide. Toobtain this document, see the HP Storage Information Library:www.hp.com/go/storage/docs

Remote Versus Local Methods for an HP 3PAR OS UpgradeThis section contains information regarding the difference between a remote online upgrade anda local online upgrade.

Remote HP 3PAR OS UpgradesRemote HP 3PAR OS upgrades are achieved by utilizing HPs Remote Operations Service Tools(RemOps) (for example, via Ethernet or modem). The process used for remote HP 3PAR OS upgradesdepends on the connectivity model allowed for remote upgrades. There are two connectivity models:Ethernet RemOps Service processor software updates can be downloaded, staged, and

performed remotely through a secure channel.Temporary RemOps In some cases, customers will temporarily open up connectivity to the

service processor for remote operations for software updates. Iftemporary remote operations access can be granted, we can performthe update remotely.

Remote Versus Local Methods for an HP 3PAR OS Upgrade 15

Local HP 3PAR OS UpgradesLocal HP 3PAR OS upgrades are achieved by utilizing an on-site service representative to performthe upgrade. Typically, local HP 3PAR OS upgrades are performed when there is no remoteconnection to the service processor. Additionally, a local HP 3PAR OS upgrade may be combinedwith other on-site activities, such as hardware upgrades or maintenance.

Start-and-Stop Quorum Witness StepsBefore performing an online upgrade to HP 3PAR OS 3.1.3 MU1, stop HP 3PAR Quorum Witness,and restart it upon completion of the upgrade.To stop and start a quorum witness, follow these steps:1. Check the status of the quorum by issuing the showrcopy -qw command. For example:

# showrcopy -qw targetsRemote Copy System InformationStatus: Started, Normal

Target Information

Name ID Type Status Policy QW-IP Q-Status Q-Status-Quals210 3 IP ready mirror_config 10.112.135.205 Started

2. Before upgrading to HP 3PAR OS 3.1.3 MU1, stop the quorum witness on both arrays byissuing the setrcopytarget witness stop command. For example:

# setrcopytarget witness stop s210# setrcopytarget witness stop -remote s210

3. Verify that the quorum witness is in the Not-started state by issuing the showrcopy-qwcommand. For example:

showrcopy -qw targetsRemote Copy System InformationStatus: Started, Normal

Target Information

Name ID Type Status Policy QW-IP Q-Status Q-Status-Quals210 3 IP ready mirror_config 10.112.135.205 Not-started

4. If the HP 3PAR Quorum Witness has been updated to the latest version and a new virtualmachine has been installed, then remove the old HP 3PAR Quorum Witness IP address, andadd the new IP address to your configuration.Follow these steps:a. Stop the quorum witness on both arrays:

# setrcopytarget witness stop s210# setrcopytarget witness stop -remote s210


b. Remove the old quorum witness on both arrays:

# setrcopytarget witness remove s210# setrcopytarget witness remove -remote s210

c. Create the new quorum witness on both arrays:

# setrcopytarget witness create s210# setrcopytarget witness create -remote s210

d. Wait for the quorum state to stabilize, transitioning from the Initializing to theNot-started state. This may take several (1530) seconds. To view the quorum state,issue the following command:

# showrcopy -qw targets

5. After the upgrade to HP 3PAR OS 3.1.3, restart the quorum witness on both arrays by issuingthe setrcopytarget witness start command. For example:

setrcopytarget witness start s210# setrcopytarget witness start -remote s210

6. Verify that the quorum witness has started by issuing the showrcopy-qw command. Forexample:

# showrcopy -qw targetsRemote Copy System InformationStatus: Started, Normal

Target Information

Name ID Type Status Policy QW-IP Q-Status Q-Status-Quals210 3 IP ready mirror_config 10.112.135.205 Started

Start-and-Stop Quorum Witness Steps 17

3 Red Hat, Oracle, Linux, and SUSE GuidelinesObserve the following host configuration guidelines when planning an online HP 3PAR OS upgradefor Red Hat, Oracle, Linux, or SUSE OS:

The SCSI timeout value for RHEL 4 and SUSE 9 must be changed from the default of 30 secondsto 60 seconds. To change the timeout value, see the HP 3PAR host OS implementation guidespecific to the OS. This needs to be performed for both FC- and iSCSI-connected hosts.

QLogic drivers for SUSE 9, 10 and Red Hat 4, 5 should be running with driver parameterPORT-DOWN retry count (qlport_down_retry) set to 1. To set the value, see the HP 3PARhost OS implementation guide specific to the OS.

NOTE: If the HP 3PAR StoreServ Storage array is running HP 3PAR OS 3.1.1 or later youmust modify the HBA parameter by setting qlport_down_retry to 10.If the HP 3PAR StoreServ Storage array is running an HP 3PAR OS version earlier than 3.1.1,set qlport_down_retry to 1.

For hosts using Oracle Clusterware, make the following required changes or adjustmentsbefore performing an upgrade:

For 10gR1 10.1.0.x and 10gR2 10.2.0.1 (without bug 4896338 patched), set cssmiscount to 195:

#set css miscount=195

For 10gR2 10.2.0.1 (with bug 4896338 patched) and later, 11gR1, and 11gR2, cssdisktimeout must not be lowered from its default value of 200.

For all Linux hosts with Oracle Clusterware, install and adjust Linux Hangcheck tickparameters to 30 seconds.

18 Red Hat, Oracle, Linux, and SUSE Guidelines

4 Sun/Solaris Configuration GuidelinesAs of HP 3PAR OS 3.1.1 GA, online upgrades can be successfully performed by means of anode-by-node (aka Advanced) upgrade and pausing between HP 3PAR StoreServ Storage nodeupgrades. Wait for all I/O paths for all Sun Cluster nodes to recover during each pause betweenHP 3PAR StoreServ Storage node upgrades. See I/O Path Monitoring for Solaris (page 19).

NOTE: Solaris 10 MU3 with an iSCSI configuration is not supported for online upgrades.

I/O Path Monitoring for SolarisThe recovery of the I/O paths must be monitored at each individual Sun Cluster node. Status ofthe Sun Cluster I/O paths cannot be assessed from the HP 3PAR StoreServ Storage.Using the Solaris format command, establish the device IDs for the device I/O paths that willneed to be monitored.

# formatSearching for disks...done

AVAILABLE DISK SELECTIONS: 0. c0t1d0 sol9u9 /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/sd@1,0 1. c3t50002AC000A50172d0 /scsi_vhci/ssd@g50002ac000a50172 2. c3t50002AC000A60172d0 /scsi_vhci/ssd@g50002ac000a60172

In the sample output shown above, it can be established that the HP 3PAR data volumes whoseI/O paths are to be monitored are on controller c3 (c3t50002AC000A50172d0

Controller /devices/pci@1f,700000/pci@0/SUNW,qlc@2,1/fp@0,0 Device Address 21340002ac000172,1e Host controller port WWN 210100e08bafe1b5 Class primary State ONLINE Controller /devices/pci@1f,700000/pci@0/SUNW,qlc@2/fp@0,0 Device Address 20340002ac000172,1e Host controller port WWN 210000e08b8fe1b5 Class primary State OFFLINE Controller /devices/pci@1f,700000/pci@0/SUNW,qlc@2/fp@0,0 Device Address 21340002ac000172,1e Host controller port WWN 210000e08b8fe1b5 Class primary State ONLINE

DEVICE PROPERTIES for disk: /dev/rdsk/c3t50002AC000A60172d0s2 Vendor: 3PARdata Product ID: VV Revision: 3111 Serial Num: 01400370 Unformatted capacity: 10240.000 MBytes Write Cache: Enabled Read Cache: Enabled Minimum prefetch: 0x0 Maximum prefetch: 0xffff Device Type: Disk device Path(s):

/dev/rdsk/c3t50002AC000A60172d0s2 /devices/scsi_vhci/ssd@g50002ac000a60172:c,raw Controller /devices/pci@1f,700000/pci@0/SUNW,qlc@2,1/fp@0,0 Device Address 20340002ac000172,1f Host controller port WWN 210100e08bafe1b5 Class primary State OFFLINE Controller /devices/pci@1f,700000/pci@0/SUNW,qlc@2,1/fp@0,0 Device Address 21340002ac000172,1f Host controller port WWN 210100e08bafe1b5 Class primary State ONLINE Controller /devices/pci@1f,700000/pci@0/SUNW,qlc@2/fp@0,0 Device Address 20340002ac000172,1f Host controller port WWN 210000e08b8fe1b5 Class primary State OFFLINE Controller /devices/pci@1f,700000/pci@0/SUNW,qlc@2/fp@0,0 Device Address 21340002ac000172,1f Host controller port WWN 210000e08b8fe1b5 Class primary State ONLINE

It is sufficient to simply monitor the State of the I/O paths during the array online upgrade.

# luxadm display /dev/rdsk/c3*s2 | grep State State OFFLINE State ONLINE State OFFLINE State ONLINE State OFFLINE State ONLINE State OFFLINE State ONLINE

When the State of all paths is ONLINE, the node-by-node upgrade sequence may proceed tothe next array node.

20 Sun/Solaris Configuration Guidelines

On each Solaris Cluster node, issue the following command:

# luxadm display /dev/rdsk/c3*s2 | grep State State ONLINE State ONLINE State ONLINE State ONLINE State ONLINE State ONLINE State ONLINE State ONLINE

NOTE: The luxadm display reports the I/O path State at a point in time and may have tobe run through several iterations on each Solaris Cluster node before all I/O paths are shown asONLINE.

The time for I/O path recovery varies widely between Solaris Cluster configurations and isdependent on the number of LUNs presented, total I/O paths, FC fabric configuration, and I/Oload.

I/O Path Monitoring for Solaris 21

5 Symantec Veritas Storage Foundation DMP (VxDMP) andOnline Upgrade

NOTE: For hosts running RHEL 6 or SLES 11 with Storage Foundation VxDMP 6.0.x, only offlineupgrades are supported when upgrading from HP 3PAR OS 2.3.1 to HP 3PAR OS 3.1.1.

NOTE: HP 3PAR OS online upgrades with attached hosts using Symantec Veritas StorageFoundation VxDMP multipath software require a pause to be implemented between upgrades ofthe array nodes within the system. The pause is to be implemented in order to allow sufficient timefor I/O path recovery to maintain host connectivity to all presented volumes. HP 3PAR testingindicates that a pause of 5 minutes between array node upgrades is sufficient to allow VxDMPI/O path recovery during the upgrade.Pauses exceeding 30 minutes are not recommended.A pause between array node upgrades can only implemented while performing node-by-nodeonline upgrades with the Advanced/manual procedures for HP 3PAR OS 3.1.1 and later. Failureto utilize the node-by-node online upgrades procedures and implement a pause between arraynode upgrades may result in loss of host connectivity and data availability of Veritas disks or diskgroups during the array upgrade.

The default value of the VxDMP link restore (dmp_restore_interval tunable) interval must temporarilybe changed to a value of 1 second before performing an online upgrade of the HP 3PAR OS forthe following VxDMP versions:

All Linux/Solaris/AIX VxDMP versions older than 5.0MP1

All NetApp VxDMP versions older than 5.0MP3

Changing the link restore interval causes the VxDMP software to react to the return of missing pathsmore quickly than it normally would with default settings. Failure to perform the change to theshorter restore interval for the noted VxDMP versions above, may cause a loss of host connectivityto HP 3PAR volumes during the upgrade. For instructions, see Changing the Veritas DMP LinkRestore Interval (page 22). After the online upgrade, reset the link restore interval to the previouslyconfigured value. For instructions, see Restoring the Veritas DMP Link Restore Interval (page 23).As of VxDMP 5.0MP1 for Linux/Solaris/AIX and 5.0MP3 NetApp, Veritas software was modifiedto circumvent the path loss issue related to the link restore interval during an HP 3PAR OS upgradeand no changes to the restore interval are necessary.

Changing the Veritas DMP Link Restore IntervalThe following procedure may be required if you are performing an online upgrade to the HP 3PAROS and Veritas DMP is being used for the multipathing solution on the host. The procedure mustbe repeated for each host server that is connected to the HP 3PAR StoreServ Storage and usingVeritas DMP.Use the following procedure to gather the current settings and change the link restore interval:1. Display the current setting of the link restore interval as follows. Record the interval so that it

can be restored later.

# vxdmpadm stat restored (note the current setting)

2. Stop the daemon.

# vxdmpadm stop restore

22 Symantec Veritas Storage Foundation DMP (VxDMP) and Online Upgrade

3. Restart the daemon with the interval set to 1.

# vxdmpadm start restore interval=1

4. Verify that the daemon is running with the interval set to 1.

# vxdmpadm stat restored

NOTE: The restore daemon reverts to the default value of 300 if or when a host restart occurs.

Restoring the Veritas DMP Link Restore IntervalIf the Veritas DMP link restore interval has been changed to 1 second for HP 3PAR OS onlineupgrade, use the following commands to change the link restore interval to the previous setting onstorage server hosts after completing an online upgrade. The following procedure must be repeatedfor each host server that is connected to HP 3PAR Storage and using Veritas DMP.Use the following procedure to restore the link restore interval to its original setting:1. Stop the daemon.

# vxdmpadm stop restore

2. Restart the daemon with the interval set to what it was previously.

# vxdmpadm start restore interval=

3. Verify the daemon is running with the interval set to the prior setting.

# vxdmpadm stat restored

Restoring the Veritas DMP Link Restore Interval 23

6 VMware ESX Server Guidelines

NOTE: Host persona 11 is the HP-recommended host persona for all supported versions ofVMware ESX with HP 3PAR OS 3.1.2 and later. After HP 3PAR OS 3.1.3 and its MUs, hostpersona 6 will not be supported for any VMware ESX version with HP 3PAR storage systems.For information regarding HP 3PAR host persona support for all supported VMware ESX versions,see Table 5 (page 12).

VMware ESX/ESXi server - Active/Active, with a path policy of Most Recently Used (MRU),does not maintain or re-instate balancing of I/O load after a failover/failback multipath event.This could leave I/O in an unbalanced state, which may yield significant I/O performance issues.Implementation of an MRU path policy is not recommended by HP. As of ESX 4.0, a third pathpolicy choice of Round Robin is available. This is the recommended path selection policy onESX systems where it is available.The VMware vCenter Site Recovery Manager and the HP 3PAR Adapter for VMware Site Replicatorrequire newer versions to be compatible with HP 3PAR OS 3.1.1 or later. For details, see VMwaresSite Recovery Manager Storage Partner Compatibility Matrix:VMware

24 VMware ESX Server Guidelines

7Windows Server OS GuidelinesThis chapter describes host configuration guidelines for Windows Server OS.

Rebooting After an UpgradeOn the first Windows Server 2008, 2008 R2, 2012, or 2012 R2 restart following an HP 3PARarray firmware upgrade (whether a major upgrade or an MU update within the same releasefamily) the Windows server will mark the HP 3PAR LUNs as offline, but the data remains intact.This behavior is seen only in the following cases:

HP 3PAR LUNs are seen by non-clustered Windows servers.

HP 3PAR LUNs are used in Microsoft Failover Clustering, but are not configured as sharedstorage in the Failover Cluster..

The behavior of LUNs being marked offline is not seen if HP 3PAR LUNs are configured as sharedstorage in a Microsoft Failover Cluster.

WARNING! When the HP 3PAR LUNs are marked offline, the Windows server administratormust follow these steps so that the applications can access the HP 3PAR LUNS:1. Click Computer ManagementDisk Management.2. Right-click each of the HP 3PAR LUNs.3. Set the LUNs as online.

To avoid this issue, use one of the following workarounds:

If you are upgrading to HP 3PAR OS 3.1.1, HP 3PAR OS 3.1.2, or any of their MUs:Before upgrading to HP 3PAR OS 3.1.1, HP 3PAR OS 3.1.2, or any of their MUs, HPrecommends the execution of Microsoft KB2849097 on every Windows Server 2008/2012host connected to an HP 3PAR array prior to performing an initial array firmware upgrade.Subsequently, the script contained in KB2849097 will have to be rerun on a host each timenew HP 3PAR LUNs are exported to that host.KB2849097 is a Microsoft PowerShell script designed to modify the Partner Attributes registryvalue that is located at HKLM\System\CurrentControlSet\Enum\SCSI\\\Device Parameters\Partmgr. The value is responsible for the state ofHP 3PAR LUNs following an array firmware upgrade. The script sets the value to "0" essentiallychanging its policy to "online."

NOTE: The following procedure will ensure proper execution of KB2849097, which willprevent the HP 3PAR LUNs from being marked offline when the Windows server is restartedfollowing an array firmware upgrade.

1. Windows Server 2008/2012 requires the PowerShell execution policy to be changedto RemoteSigned to allow execution of external scripts. This must be done before thescript is executed. To change the PowerShell execution policy, open the PowerShellconsole and issue the following command:Set-ExecutionPolicy RemoteSignedYou might be prompted to confirm this action by pressing y.

2. The next step is to save the script as a .ps1 file to a convenient location and execute itby issuing the following command in a PowerShell console window:C:\ps_script.ps1The above command assumes that the script has been saved to C: under the nameps_script.ps1.

Rebooting After an Upgrade 25

3. The Administrator will then be prompted to provide a Vendor String, which is usedto distinguish between different vendor types. The script will only modify those deviceswhose Vendor String matches the one that has been entered into the prompt.Enter 3PAR in the prompt to allow the script to be executed on all HP 3PAR LUNs currentlypresented to the host as shown in the output below:Enter Vendor String: 3PAR

4. The script will then iterate through all HP 3PAR LUNs currently present on the host andset the Attributes registry value to 0. In order to verify that the Attributes valuefor all HP 3PAR LUNs were properly modified, issue the following command:Get-ItemProperty -path"HKLM:\SYSTEM\CurrentControlSet\Enum\SCSI\Disk*Ven_3PARdata*\*\DeviceParameters\Partmgr" -Name AttributesThe Attributes value should be set to 0 as shown in the example below:

PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\Disk&Ven_3PARdata&Prod_VV\5&381f35e2&0&00014f\Device Parameters\PartmgrPSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\Disk&Ven_3PARdata&Prod_VV\5&381f35e2&0&00014f\Device ParametersPSChildName : PartmgrPSDrive : HKLMPSProvider : Microsoft.PowerShell.Core\RegistryAttributes : 0

If you are upgrading to HP 3PAR OS 3.1.3 MU1After an upgrade to HP 3PAR OS 3.1.3 MU1, HP requires that host persona 15 be used forWindows Server 2012 R2 and non-R2 and Windows Server 2008 R2 and non-R2 to preventthis issue from occurring. The host persona must be changed to 15 before the first restart ofthe Windows Server host following the upgrade. Changing to host persona 15 is an onlineprocedure. Use the HP 3PAR OS CLI sethost command to change the persona, and verifyby using the showhost command following the upgrade.

# sethost -persona 15 windowshostshowhostId Name Persona -WWN/iSCSI_Name- Port0 windowshost WindowsServer 10000000C9606724 0:5:1 10000000C9606724 1:5:1

Microsoft MPIO Driver on Windows Server 2008With Windows Server 2008, using the Microsoft native MPIO driver, the load-balancing policydefaults to Active/Passive. HP requires that the load-balancing policy be set to Round Robin.See the HP 3PAR Windows Server 2012 and Windows Server 2008 Implementation Guide formore details on configuring the load-balancing policy.

CAUTION: During an HP 3PAR OS online upgrade from HP 3PAR OS 2.2.4 to HP 3PAR OS2.3.1, or from HP 3PAR OS 2.3.1 to HP 3PAR OS 3.1.1, for Windows Server 2008 and WindowsServer 2008 R2 failover clusters (including failover clusters as guest OS), HP requires that all dataLUNs that are presented to Microsoft failover clusters from the HP 3PAR StoreServ Storage first beput into Maintenance Mode. Once the HP 3PAR OS online upgrade is completed, maintenancemode must be turned off.This does not apply to upgrades from HP 3PAR OS 3.1.1 (that is, those with HP 3PAR OS 3.1.1.xas a base) and later.

26 Windows Server OS Guidelines

To turn maintenance mode on or off for each of the cluster HP 3PAR disks, start the Failover ClusterManager application. Double-click the storage icon to open a Summary of Storage window. Foreach of the clustered HP 3PAR data disks (not including any Quorum Witness disks), right-clickand select the More Actions option from the menu, and select either Turn on maintenance for thedisk or Turn off maintenance for the disk. For details, see Figure 1 (page 27):

NOTE: Does not apply to Windows Server 2008 systems running Veritas DMP driver.

Figure 1 Turning Maintenance Mode ON or OFF

Microsoft HotfixesHotfixes may be required for the support of specific Windows functionality. For more informationabout required hotfixes, see the Windows Server SPOCK configurations on the HP SPOCK website.For Windows Server 2008 and Windows Server 2008 R2 using MS MPIO, Microsoft hotfixesmust be applied before upgrading the HP 3PAR StoreServ Storage. For more information aboutthe required hotfixes, see the Windows Server 2008 and Windows Server 2008 R2 SPOCKconfigurations on the HP SPOCK website.A hotfix, available from Microsoft, is required to support live storage migrations with WindowsServer 2012 using Cluster Shared Volumes on HP 3PAR OS 3.1.2 and later. The hotfix must beapplied before upgrading the HP 3PAR StoreServ Storage. For more information about the requiredhotfix, see the Windows Server 2012 SPOCK configuration on the HP SPOCK website.

HP Peer Motion ManagerHP 3PAR Peer Motion Manager V1.1, V1.2 runs only on Microsoft Windows OSs that are supportedby CLI (Windows Server 2008, Windows Server 2008 R2, Windows Server 2003, Windows

Microsoft Hotfixes 27

Vista Business, and Windows XP Professional). When an HP 3PAR StoreServ Storage is upgradedto HP 3PAR OS 3.1.1 MU1, the CLI must be upgraded to 3.1.1 MU1.

NOTE: The HP 3PAR OS 3.1.1 GA does not support VMware cluster data migration. (HP 3PARPeer Motion Manager 1.1 or earlier can be used for data migration.) However, provided the CLIis upgraded to 3.1.1 MU1, HP 3PAR OS 3.1.1 MU1 supports VMware cluster data migrationusing HP 3PAR Peer Motion Manager 1.2.For HP 3PAR OS 3.1.2 and later, migration is supported using the HP 3PAR Management Console(GUI) for HP 3PAR to HP 3PAR migration, and by using HP StorageWorks Command View for HPEVA to HP 3PAR StoreServ Online Import.

28 Windows Server OS Guidelines

8 AIX GuidelinesHP 3PAR OS online automatic upgrades with AIX Direct Connect attached hosts are not supportedby HP for any HP 3PAR OS upgrades. Online maintenance upgrades can be successfully performedby means of a node-by-node (or advanced) upgrade method. Using this method will cause thesystem to wait for user input between each node restart needed during an online HP 3PAR OSupgrade.This pause time in the upgrade process is used to allow all of the I/O paths to the AIX direct-connecthosts, for all of the presented LUNs, to recover (fail back). To display the paths that must bemonitored for recovery, use the AIX lspath s failed command on the attached host:

# lspath s failedFailed hdisk4 fscsi0Failed hdisk5 fscsi0...

#

After all the paths have recovered, continue with the next node of the HP 3PAR OS.

# lspath s failed#

29

9 HP-UX Guidelines

IMPORTANT: To preserve the boot from SAN (BFS) setup for HP-UX PA-RISC servers running anysupported OS version, the following steps must be completed before rebooting the server and afterthe HP 3PAR OS on the arrays is upgraded.

After the HP 3PAR OS on the array is upgraded, run the following commands before rebootingthe server:1. Run the insf -e command.2. Run the ioscan command.3. Use the setboot command to reset the primary and alternate boot paths as well as HA if it

is available.For example, on 11i v3 (11.31):Using the lvlnboot -v command and the setboot -v | head -5 command on the HP-UXserver.

#lvlnboot -vBoot Definitions for Volume Group / dev/vg00:Physical Volumes belonging in Root Volume Group: /dev/disk/disk8 -- Boot DiskBoot: lvol1 on: /dev/disk/disk8Root: 1vol3 on: /dev/disk/disk8Swap: lvol2 on: /dev/disk/disk8Dump: lvol2 on: /dev/disk/disk8, 0

#setboot -vPrimary bootpath: 1/0/14/1/0.0x21120002ac0010e6.0x4001000000000000(/dev/rdisk/disk8)

IssueIf a rescan of the HP-UX I/O system hardware is run during the HP 3PAR OS online upgradeprocess, ioscan might report device paths with a Software State of NO_HW. This is due to a defectthat causes an unexpected SCSI inquiry response to LUN 0 for HP-UX hosts during the HP 3PAROS online upgrade. It was verified that I/O is not affected and paths remain accessible as longas the server is not restarted during the online upgrade process. When the entire online upgradeprocess is complete, the SCSI inquiry response to LUN 0 is normal and a rescan reports devicepaths with a Software State of CLAIMED.

#ioscan -fnC diskClass | H/W Path Driver S/W State H/W Type Description=====================================================================================

disk 67 0/0/0/5/0/0/0.20.131.97.0.0.1 sdisk NO_HW DEVICE 3PARdataVV /dev/dsk/c15t0d1 /dev/rdsk/c15t0d1disk 69 0/0/0/5/0/0/0.20.131.97.0.0.2 sdisk NO_HW DEVICE 3PARdataVV /dev/dsk/c15t0d2 /dev/rdsk/c15t0d2

If an HP-UX server is restarted during an HP 3PAR OS online upgrade, 1 or more previous knownLUN paths may not be discovered by the HP-UX server. The HP-UX operating systems will notcontinue device discovery when a LUN 0 SCSI Inquiry response returns an unexpected value. Oncethe upgrade is complete, manual intervention by a system administrator is required for the restartedHP-UX server to rediscover HP 3PAR devices as described in the next section.

ResolutionNOTE: This issue was resolved with HP 3PAR OS 3.1.3.GA. If you are upgrading to any of theaffected HP 3PAR OS versions listed above, follow the steps listed below.

During the HP 3PAR OS Online Upgrade process, a rescan of the HP-UX11.31 I/O system hardwarereports device paths with a Software State of NO_HW. Perform the following steps to check thehealth of the data LUN paths and confirm they are reported as online.1. Ensure that the HP-UX 11.31 server was not restarted.2. Scan the HP-UX system hardware and identify the hardware paths for any devices that report

a Software State as NO_HW.

#ioscan -fnC diskClass | H/W Path Driver S/W State H/W Type Description================================================================================

disk 67 0/0/0/5/0/0/0.20.131.97.0.0.1 sdisk NO_HW DEVICE 3PARdataVV /dev/dsk/c15t0d1 /dev/rdsk/c15t0d1disk 69 0/0/0/5/0/0/0.20.131.97.0.0.2 sdisk NO_HW DEVICE 3PARdataVV /dev/dsk/c15t0d2 /dev/rdsk/c15t0d2

3. Verify the health of the data LUN path using the hardware paths from the previous step.

#ioscan -P health -H #ioscan -P health -H 0/0/0/5/0/0/0

Class | H/W Path health=======================================================================

lunpath 9 0/0/0/5/0/0/0.0x23240002ac000e2c.0x0 offlinelunpath 68 0/0/0/5/0/0/0.0x23240002ac000e2c.0x4001000000000000 onlinelunpath 77 0/0/0/5/0/0/0.0x23240002ac000e2c.0x4002000000000000 online

Issue 31

4. If the LUN paths display online, I/O is not affected and paths remain accessible as long asthe server is not restarted during the online upgrade process.

NOTE: HP-UX OS version 11i v2 (11.23) and earlier do not provide the health check utility,however it has been verified that even though the devices are in the NO_HW state, the onlineupgrade will resume without I/O interruption.

If an HP-UX host is restarted during the online upgrade operation, the following steps must beperformed to re-discover 3PAR devices:1. Ensure all InServ nodes have successfully completed the online upgrade and showing the

correct HP 3PAR OS version as follows:

# cli upgradesys -statusSystem is not currently undergoing an online upgrade.First node to be rebooted is node 3 Which will be followed by node 0 Which will be followed by node 2 Which will be followed by node 1

# showversion bRelease version 3.1.2.322 (MU1)Patches: P05, P13

Component Name VersionCLI Server 3.1.2.322 (MU1)CLI Client 3.1.2.322 (MU1)System Manager 3.1.2.428 (P05)Kernel 3.1.2.322 (MU1)TPD Kernel Code 3.1.2.322 (MU1)TPD Kernel Patch 3.1.2.466 (MU1)

2. Scan the HP-UX system hardware for usable I/O system devices:#ioscan -fn

3. If you are using LVM/PVLinks, scan the physical volumes for LVM volume groups and activatethem:#vgscan -v -aRun the following command for each volume group using 3PAR LUNs:#vgchange -a y

4. If you are using VxVM, rebuild the volume device nodes and start the volumes:#vxdctl enable#vxvol g start Verify that the volumes are online:#vxprint ht g

32 HP-UX Guidelines

10 Support and Other ResourcesContacting HP

For worldwide technical support information, see the HP support website:http://www.hp.com/support

Before contacting HP, collect the following information:

Product model names and numbers

Technical support registration number (if applicable)

Product serial numbers

Error messages

Operating system type and revision level

Detailed questions

Specify the type of support you are requesting:

Support requestHP 3PAR storage system

StoreServ 7000 StorageHP 3PAR StoreServ 7200, 7400, and 7450 Storagesystems

3PAR or 3PAR StorageHP 3PAR StoreServ 10000 Storage systems

HP 3PAR T-Class storage systems

HP 3PAR F-Class storage systems

HP 3PAR documentation

See:For information about:

The Single Point of Connectivity Knowledge for HPStorage Products (SPOCK) website:

Supported hardware and software platforms

http://www.hp.com/storage/spock

The HP 3PAR StoreServ Storage site:Locating HP 3PAR documents

http://www.hp.com/go/3par

To access HP 3PAR documents, click the Support link foryour product.

HP 3PAR storage system software

HP 3PAR StoreServ Storage Concepts GuideStorage concepts and terminology

HP 3PAR Management Console User's GuideUsing the HP 3PAR Management Console (GUI) to configureand administer HP 3PAR storage systems

HP 3PAR Command Line Interface AdministratorsManual

Using the HP 3PAR CLI to configure and administer storagesystems

HP 3PAR Command Line Interface ReferenceCLI commands

HP 3PAR System Reporter Software User's GuideAnalyzing system performance

HP 3PAR Host Explorer Users GuideInstalling and maintaining the Host Explorer agent in orderto manage host configuration and connectivity information

HP 3PAR CIM API Programming ReferenceCreating applications compliant with the Common InformationModel (CIM) to manage HP 3PAR storage systems

Contacting HP 33


HP 3PAR-to-3PAR Storage Peer Motion GuideMigrating data from one HP 3PAR storage system to another

HP 3PAR Secure Service Custodian Configuration UtilityReference

Configuring the Secure Service Custodian server in order tomonitor and control HP 3PAR storage systems

HP 3PAR Remote Copy Software Users GuideUsing the CLI to configure and manage HP 3PAR RemoteCopy

HP 3PAR Upgrade Pre-Planning GuideUpdating HP 3PAR operating systems

HP 3PAR F-Class, T-Class, and StoreServ 10000 StorageTroubleshooting Guide

Identifying storage system components, troubleshootinginformation, and detailed alert information

HP 3PAR Policy Server Installation and Setup GuideInstalling, configuring, and maintaining the HP 3PAR PolicyServer HP 3PAR Policy Server Administration Guide

34 Support and Other Resources


Planning for HP 3PAR storage system setup

Hardware specifications, installation considerations, power requirements, networking options, and cabling informationfor HP 3PAR storage systems

HP 3PAR StoreServ 7000 Storage Site Planning ManualHP 3PAR 7200, 7400, and 7450 storage systems

HP 3PAR StoreServ 7450 Storage Site Planning Manual

HP 3PAR StoreServ 10000 Storage Physical PlanningManual

HP 3PAR 10000 storage systems

HP 3PAR StoreServ 10000 Storage Third-Party RackPhysical Planning Manual

Installing and maintaining HP 3PAR 7200, 7400, and 7450 storage systems

HP 3PAR StoreServ 7000 Storage Installation GuideInstalling 7200, 7400, and 7450 storage systems andinitializing the Service Processor HP 3PAR StoreServ 7450 Storage Installation Guide

HP 3PAR StoreServ 7000 Storage SmartStart SoftwareUsers Guide

HP 3PAR StoreServ 7000 Storage Service GuideMaintaining, servicing, and upgrading 7200, 7400, and7450 storage systems HP 3PAR StoreServ 7450 Storage Service Guide

HP 3PAR StoreServ 7000 Storage Troubleshooting GuideTroubleshooting 7200, 7400, and 7450 storage systems

HP 3PAR StoreServ 7450 Storage Troubleshooting Guide

HP 3PAR Service Processor Software User GuideMaintaining the Service Processor

HP 3PAR Service Processor Onsite Customer Care(SPOCC) User's Guide

HP 3PAR host application solutions

HP 3PAR Recovery Manager Software for Oracle User'sGuide

Backing up Oracle databases and using backups for disasterrecovery

HP 3PAR Recovery Manager Software for MicrosoftExchange 2007 and 2010 User's Guide

Backing up Exchange databases and using backups fordisaster recovery

HP 3PAR Recovery Manager Software for Microsoft SQLServer Users Guide

Backing up SQL databases and using backups for disasterrecovery

HP 3PAR Management Plug-in and Recovery ManagerSoftware for VMware vSphere User's Guide

Backing up VMware databases and using backups fordisaster recovery

HP 3PAR VSS Provider Software for Microsoft WindowsUser's Guide

Installing and using the HP 3PAR VSS (Volume Shadow CopyService) Provider software for Microsoft Windows

HP 3PAR Storage Replication Adapter for VMwarevCenter Site Recovery Manager Implementation Guide

Best practices for setting up the Storage Replication Adapterfor VMware vCenter

HP 3PAR Storage Replication Adapter for VMwarevCenter Site Recovery Manager Troubleshooting Guide

Troubleshooting the Storage Replication Adapter for VMwarevCenter Site Recovery Manager

HP 3PAR VAAI Plug-in Software for VMware vSphereUser's Guide

Installing and using vSphere Storage APIs for ArrayIntegration (VAAI) plug-in software for VMware vSphere

HP 3PAR documentation 35

Typographic conventionsTable 8 Document conventions

ElementConvention

Bold text Keys that you press

Text you typed into a GUI element, such as a text box

GUI elements that you click or select, such as menu items, buttons,and so on

Monospace text File and directory names

System output

Code

Commands, their arguments, and argument values

Code variables

Command variables

Bold monospace text Commands you enter into a command line interface

System output emphasized for scannability

WARNING! Indicates that failure to follow directions could result in bodily harm or death, or inirreversible damage to data or to the operating system.

CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.

NOTE: Provides additional information.

RequiredIndicates that a procedure must be followed as directed in order to achieve a functional andsupported implementation based on testing at HP.

HP 3PAR branding information The server previously referred to as the "InServ" is now referred to as the "HP 3PAR StoreServ

Storage system."

The operating system previously referred to as the "InForm OS" is now referred to as the "HP3PAR OS."

The user interface previously referred to as the "InForm Management Console (IMC)" is nowreferred to as the "HP 3PAR Management Console."

All products previously referred to as 3PAR products are now referred to as "HP 3PAR"products.

36 Support and Other Resources

11 Documentation feedbackHP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any errors, suggestions, or comments to Documentation Feedback([email protected]). Include the document title and part number, version number, or the URLwhen submitting your feedback.

37

HP 3PAR Operating System Upgrade Pre-Planning GuideContents1 HP 3PAR OS Upgrade OverviewAudienceSupported Upgrade Types

2 Guidelines for Online UpgradesPlanning Information for Online HP 3PAR OS UpgradesGeneral GuidelinesHost Configuration GuidelinesHP 3PAR Persistent Ports FeatureHP 3PAR OS Persona Changes

HP 3PAR StoreServ Storage Configuration GuidelinesHP 3PAR Remote Copy GuidelinesRemote Versus Local Methods for an HP 3PAR OS UpgradeRemote HP 3PAR OS UpgradesLocal HP 3PAR OS Upgrades

Start-and-Stop Quorum Witness Steps

3 Red Hat, Oracle, Linux, and SUSE Guidelines4 Sun/Solaris Configuration GuidelinesI/O Path Monitoring for Solaris

5 Symantec Veritas Storage Foundation DMP (VxDMP) and Online UpgradeChanging the Veritas DMP Link Restore IntervalRestoring the Veritas DMP Link Restore Interval

6 VMware ESX Server Guidelines7 Windows Server OS GuidelinesRebooting After an UpgradeMicrosoft MPIO Driver on Windows Server 2008Microsoft HotfixesHP Peer Motion Manager

8 AIX Guidelines9 HP-UX GuidelinesIssueResolution

10 Support and Other ResourcesContacting HPHP 3PAR documentationTypographic conventionsHP 3PAR branding information

11 Documentation feedback

HP 3PAR Operating System Upgrade

Documents

Transcript of HP 3PAR Operating System Upgrade