HP 3PAR InForm Operating System 3.1.

1 Upgrade Pre-Planning Guide

Abstract
This guide is intended for use as a planning tool for HP customers. It provides the following information on HP 3PAR InForm Operating System (InForm OS) software updates: An overview of the online and offline update processes for the InForm OS Prerequisites for online updates Guidelines for online updates Planning information needed for online updates Veritas dynamic multipathing (DMP) prerequisites for online updates Remote versus local methods of upgrading

HP Part Number: QL226-96529 Published: March 2012

 Copyright 2012 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 and 12.212, Commercial 1 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.

Contents
1 Introduction...............................................................................................4
Audience.................................................................................................................................4 Typographical Conventions........................................................................................................4 Advisories................................................................................................................................5

2 InForm OS Update Overview.......................................................................6

Supported Update Types...........................................................................................................6 Remote Copy Support Across InForm OS Levels.............................................................................6

3 Guidelines for Online Updates.....................................................................8

General Guidelines...................................................................................................................8 Host Configuration Guidelines....................................................................................................9 InForm OS 2.3.1 Persona Changes.......................................................................................13 Storage Server Configuration Guidelines...................................................................................15 General Configuration Guidelines........................................................................................15 Remote Copy Guidelines....................................................................................................15 Planning Information for Online InForm OS Updates....................................................................16

4 Veritas DMP and Online Updates...............................................................17

Changing the Veritas DMP Link Restore Interval...........................................................................17 Restoring the Veritas DMP Link Restore Interval............................................................................17

5 6 7 8

Sun Cluster Configuration Guidelines..........................................................19 Exanet ExaStore Clustered NAS System Prerequisites.....................................20 VMware ESX Server..................................................................................21 Remote Versus Local Methods for an InForm OS Update................................22
Remote InForm OS Updates.....................................................................................................22 Local InForm OS Updates........................................................................................................22

Contents

1 Introduction
This guide is intended for use as a planning tool for HP customers. It provides the following information on HP 3PAR InForm Operating System (InForm OS) software updates: An overview of the online and offline update processes for the InForm OS Prerequisites for online updates Guidelines for online updates Planning information needed for online updates Veritas DMP prerequisites for online updates Remote versus local methods of upgrading

NOTE: HP recommends updating host drivers to a supported level on InForm OS 3.1.x before attempting an online update. This information is available on the HP Single Point of Connectivity (SPOCK) website: www.hp.com/storage/spock These documents are provided to assist you in setting up host servers with HP-supported configuration information. In addition to this planning document, the implementation guides are available on the HP Business Support Center (BSC) website: http://www.hp.com/go/3par/

Audience
This guide is intended for system and storage administrators who monitor and direct system configurations and resource allocation for HP 3PAR Storage Systems. The tasks described in this document assume that the administrator is familiar with host platforms and the Inform OS. Although this guide attempts to provide the basic information that is required to establish communications between the HP 3PAR Storage System and the host, and to allocate the required storage for a given configuration, the appropriate HP 3PAR documentation must be consulted in conjunction with the host and host bus array (HBA) vendor documentation for specific details and procedures. NOTE: This implementation guide is not intended to reproduce any third-party product documentation. For details about 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.

Typographical Conventions
This guide uses the following typographical conventions:
Typeface ABCDabcd Meaning Example

Used for dialog elements such as When prompted, click Finish to complete the titles, button labels, and other screen installation. elements. Used for paths, filenames, and screen Open the file output. \os\windows\setup.exe Used to differentiate user input from screen output. # cd \opt\3par\console

ABCDabcd

ABCDabcd

Introduction

Typeface <ABCDabcd> [ABCDabcd]

Meaning Used for variables in filenames, paths, and screen output. Used for options in user input.

Example # controlport offline <node:slot:port> Modify the content string by adding the -P[x] option after -jar inform.jar # .\java -jar inform.jar -P[x]

Advisories
To avoid injury to people or damage to data and equipment, be sure to observe the cautions and warnings in this guide. Always be careful when handling any electrical equipment. NOTE: guide. Notes are reminders, tips, or suggestions that supplement the procedures included in this

Required
Requirements signify procedures that must be followed as directed in order to achieve a functional and supported implementation based on testing at HP. WARNING! Warnings alert you to actions that can cause injury to people or irreversible damage to data or the operating system. CAUTION: Cautions alert you to actions that can cause damage to equipment, software, or data.

Advisories

2 InForm OS Update Overview

The HP 3PAR Storage System servers support two different methods for updating the InForm OS: online and offline. The updates can be performed with a service representative on-site or remotely (from HP). Remote updates require that remote operations are available. NOTE: Because InForm OS 3.1.x is a 64-bit operating system, only T-class and F-class system upgrades are supported.

Supported Update Types

InForm OS updates may either be performed online or offline. Online updates allow the hosts connected to the system to continue I/O activity, for offline updates host I/O activity must be stopped. The following types of updates are supported: Half-System Online Update: Used when there is major OS-level change. (For example, updating from 2.3.1 to 3.1.1 is a major OS-level change.) Half of the nodes are updated at one time, then the other half of the nodes are updated at one time. Single-Node Online Update: Used when the OS maintenance level changes. For example: The update from 2.3.1.298 (maintenance update 3 [MU3]) to 2.3.1.400 [MU5]) is a single-node update from maintenance level .298 to maintenance level .400. Each node is updated one at a time. Although the total time to perform this update is longer than a half-system online update, the impact on the system is less because all but one node remains available to the hosts. Each node takes approximately 20 minutes to update. Offline Update: Used when the customer requests an offline update, or when the system is operating several levels below the update package version. If the system is operating several levels below the update package version, it may be easier to perform the update without all the system checks required for online updates. All nodes are updated, then rebooted at the same time. The system is unavailable to the hosts during this operation.

The following table lists the supported InForm OS-level update types. Table 1 Update Types
Update from Current InForm OS Level 2.3.1.x 2.2.4.x 3.1.1 GA Update to New InForm OS Level 3.1.1.x 2.3.1.400 (MU5) 3.1.1 MU1 Update Type Half-system Half-system Single-node online

WARNING! For InForm OS 2.2.4.x and OS 2.3.1.x, all Remote Copy groups must be stopped before updating to InForm OS level 3.1.1.x. For HP 3PAR Storage Systems licensed with Remote Copy, do not upgrade directly from InForm OS 2.2.4 to InForm OS 3.1.1. These upgrade conditions are not supported and will fail. See Remote Copy Support Across InForm OS Levels (page 6)

Remote Copy Support Across InForm OS Levels

Remote Copy is supported only between adjacent HP 3PAR InForm OS release levels. For example, an HP 3PAR Storage System running InForm OS 2.2.4.nnn cannot be in a Remote Copy configuration with an HP 3PAR Storage System running InForm OS 3.1.1 GA or 3.1.1 MU1. To take advantage of Remote Copy features introduced in InForm OS 3.1.1, each HP 3PAR Storage System in the link will need to be at OS 3.1.1 (all MU versions are treated as the same OS version). S-class and E-class HP 3PAR Storage Systems cannot run InForm OS 3.1.1.
6 InForm OS Update Overview

Table 2 Remote Copy Support

InForm OS Level System A 2.2.4.nnn 2.3.1.nnn 2.2.4.nnn InForm OS Level System B 2.3.1.nnn 3.1.1.nnn 3.1.1.nnn Supported? Yes Yes No

WARNING! When Remote Copy is configured, direct upgrades performed directly from all levels of InForm OS 2.2.4 to OS 3.1.1 GA or MU1 will fail. This holds true for offline upgrades and instances when Remote Copy is simply disabled. For these upgrades, you must first upgrade to InForm OS 2.3.1 MU5, and only then proceed to upgrade to InForm OS 3.1.1 MU1. In addition, you should not enable Remote Copy between HP 3PAR Storage Systems running InForm OS 2.2.4 and other HP 3PAR Storage Systems running InForm OS 3.1.1.

Remote Copy Support Across InForm OS Levels

3 Guidelines for Online Updates

Several guidelines need to be followed for online InForm OS updates. The guidelines are divided into several categories: General Host configuration Storage server configuration

General Guidelines
Observe the following general guidelines in respect to online InForm OS updates: WARNING! All hosts must be compliant with the current applicable implementation guides for the target InForm OS level. Hosts that do not comply completely with the implementation guides may lose connectivity during the InForm OS upgrade. Hardware and configuration changes should not be performed on the HP 3PAR Storage System server during the update. For example, software operations (such as servicemag, createaldvv, or use of the HP 3PAR Storage System tuner commands) and hardware operations (such as adding/removing drives, cages, etc.) are prohibited during the online update process. All logical disk growth operations for Common Provisioning Groups continue uninterrupted as under normal operation. The storage server must be in a healthy state (with no failed or degraded physical disks, cages, FCALs, nodes, etc.). The InForm OS update software performs an automated check. No host or environment changes are allowed during an online update (for example, rebooting, applying patches, or rezoning switches). The update software checks for the existence of hosts before and after each step, and if host connections do not reappear after each step, the update process reverts to the original level. Any automated processes that communicate with the HP 3PAR Storage System server management interface (scripting) must be stopped before performing an online update. Online updates should be scheduled and performed during periods of low I/O activity. As system resources are placed offline to be updated, system utilization must be lower than 50% for each node and I/O port. If the CLI command takes more than 4 seconds to respond, check the DNS lookup speed. Use the following command to verify performance:
ping a <ip address>

where <ip address> is the IP address of the HP 3PAR Storage System. If the DNS lookup speed is slow, contact the system administrator to change the DNS settings. DNS lookup can also be sped up by adding the HP 3PAR Storage System to the local DNS mapping file. For example, on a Windows 32bit OS, go to the following location and add an entry there for the HP 3PAR Storage System. c:\WINDOWS\system32\drivers\etc\hosts After you save the file, the CLI command should respond normally.

Guidelines for Online Updates

Host Configuration Guidelines

Observe the following host configuration guidelines when planning an online InForm OS update: All attached hosts must have multipathing software in place and operational for every storage server volume exported, and the host(s) must be connected to two adjacent nodes, an even-numbered node followed by a consecutive odd-numbered node, on the storage system. (Valid pairings are 0 & 1, 2 & 3, 4 & 5, 6 & 7). WARNING! An HP 3PAR Storage System running InForm OS Version 2.2.4.158 or earlier, using iSCSI with CHAP authentication connecting to all supported hosts, will fail to re-enable all paths to a host in two scenarios: a revert or an HP 3PAR Storage System reboot (shutdownsys reboot). HP recommends that all hosts connecting this way be upgraded to 2.2.4.MU6. If during the upgrade a revert does occur, then re-issue the target CHAP password on the HP 3PAR Storage System. This must be followed by issuing the discovery of targets command on the host. Doing this will re-enable all previous CHAP enabled iSCSI paths to the host. NOTE: See SPOCK streams, available on the HP SPOCK website, for supported multipathing environments: www.hp.com/storage/spock NOTE: For unsupported environments, the hosts should be shut down (and in some cases powered off), or the vLUNs exported to these hosts must be unexported, or FC must be logically disconnected, before execution of the online InForm OS update. Multipathing cabling must adhere to HP 3PAR configuration rules: each defined host must have at least two operational paths attached to two adjacent nodes (i.e. even-numbered node, followed by a consecutive odd-numbered node. Valid pairings are 0 & 1, 2 & 3, 4 & 5, 6 & 7. Invalid pairings are 2 & 1, 0 & 3). All host paths must be identified with a single host name. All system administration activities must be stopped during an Inform OS online update. All active tasks must complete or be stopped before proceeding. This includes any provisioning activity, physical/virtual copy activity, and dynamic optimization. Be sure to have the customer stop any automated administration scripts that may be running as well (Recovery Manager and VSS Provider for Microsoft Windows). For VxDMP, depending on the level, the customer should set the link restore interval to a value of 1 second before starting the online update. This causes the DMP software to react to the return of missing paths more quickly than it normally would. For instructions, see Veritas DMP and Online Updates (page 17). After the online update, reset the link restore interval to the previously configured value. Follow this procedure for each host that is running VxVM for its DMP.

Host Configuration Guidelines

NOTE:

The following hosts do not require this change:

AIX hosts using Veritas VxDMP 5.0 with MP1 and HP 3PAR ODM 1.2 or later AIX hosts using Veritas VxDMP 5.1 with HP 3PAR ODM for Veritas 1.3 or later AIX hosts using Veritas VxDMP 6.0 with HP 3PAR ODM for Veritas 1.3 or later Linux hosts using VxDMP 5.1_GA or later Linux hosts using Veritas VxDMP 6.0_GA or later Linux hosts using Veritas VxDMP4.1 MP4 Linux hosts using Veritas VxDMP5.0 MP3 or later Solaris hosts using Veritas VxDMP4.1 MP2 or later Solaris hosts using Veritas VxDMP5.0 MP1 or later Solaris hosts using Veritas VxDMP5.1_GA or later Solaris hosts using Veritas 6.0_GA or later

With Windows 2008, using the Microsoft native MPIO driver, the load-balancing policy defaults to Active/Passive. HP requires that the load-balancing policy be set to Active/Active.

10

Guidelines for Online Updates

See the HP 3PAR Windows 2008 Implementation Guide for more details on configuring the load-balancing policy. CAUTION: During an InForm OS online update from OS 2.2.4 to OS 2.3.1, or from OS 2.3.1 to OS 3.1.1, for Windows 2008 and Windows 2008 R2 failover clusters (including failover clusters as guest OS), HP requires that all data LUNs that are presented to Microsoft failover clusters from the HP 3PAR Storage System server first be put into Maintenance Mode. Once the InForm OS online update is completed, the maintenance mode must be turned off. To turn the maintenance mode on or off for each of the cluster 3PAR disks, start the Failover Cluster Manager application. Double-click the storage icon to open a Summary of Storage window. For each of the clustered HP 3PAR data disks (not including any Witness/Quorum disks), right-click and select the More Actions option from the menu, and select either Turn on maintenance for the disk or Turn off maintenance for the disk. For details, see Figure 1 (page 11): NOTE: Does not apply to Windows 2008 systems running Veritas DMP driver.

Figure 1 Turning Maintenance Mode ON or OFF

For Windows 2008 and Windows 2008 R2 using MS MPIO, Microsoft hotfixes must be applied before updating the HP 3PAR Storage System: Microsoft KB 2406705 for Windows 2008 R2, available at: http://support.microsoft.com/kb/2406705 Microsoft KB 968287 for Windows 2008, available at: http://support.microsoft.com/kb/968287

HP 3PAR Peer Motion Manager (PMM) runs only on Microsoft Windows OSs that are supported by CLI (Windows 2008, Windows 2008 R2, Windows 2003, Windows Vista Business, and Windows XP Professional). When an HP 3PAR Storage System is upgraded to InForm OS 3.1.1 MU1, the CLI must be upgraded to 3.1.1 MU1.

Host Configuration Guidelines

1 1

NOTE: The InForm OS 3.1.1 GA does not support VMware cluster data migration. (HP 3PAR PMM 1.1 or earlier can be used for data migration.) However, provided the CLI is upgraded to 3.1.1 MU1, InForm OS 3.1.1 MU1 supports VMware cluster data migration using HP 3PAR PMM 1.2. iSCSI hosts must have active I/O on all paths during the upgrade. The upgrade process reboots one node at a time and checks that all hosts have reconnected after each node is rebooted. The upgrade will not advance until all hosts re-establish connection. Because an idle iSCSI host will not reconnect, the workaround is to have I/O on all paths during the upgrade. The SCSI timeout value for RH4 and SUSE 9 must be changed from the default of 30 seconds to 60 seconds. Refer to the specific implementation guide for changing the timeout value. This needs to be performed for both Fibre Channel- and iSCSI-connected hosts. QLogic drivers for SUSE 9, 10 and RedHat 4, 5 should be running with driver parameter PORT-DOWN retry count (qlport_down_retry) set to 1. Refer to the specific implementation guide for setting the value. Solaris 10 MU3 with an iSCSI configuration is not supported for online updates. For hosts using Oracle Clusterware, make the following required changes or adjustments before performing an update: For 10gR1 10.1.0.x and 10gR2 10.2.0.1 (without bug 4896338 patched), set css miscount to 195 (# set css miscount=195). For 10gR2 10.2.0.1 (with bug 4896338 patched) and later, 1 1gR1, and 1 1gR2, css disktimeout must not be lowered from its default value of 200. For all Linux hosts with Oracle Clusterware, install and adjust Linux Hangcheck tick parameters to 30 seconds.

Even if a direct connected HP host running Tachyon based HBAs (example A5158A, A6795A) is configured correctly, if the HP host is not doing I/O during the online update, the update may revert to the previous software level. The workaround for this requires ioscan or I/O to be performed while doing an online update if the direct connect HP host does not have mounted file systems. This is not applicable for QLogic based HP cards (example A6826A, AB3790). 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 unplanned for and 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 path policy choice of Round Robin is available. This is the recommended path selection policy on ESX systems where it is available.

12

Guidelines for Online Updates

NOTE: For ESX 4.0, systems, HP recommends changing the ESX Scsi.ConflictRetries from its default value of 80 to a value of 200 when connected to an HP 3PAR Storage System running InForm OS version 2.2.4 or earlier. This change lengthens the time allowed for I/O retries due to ESX SCSI-2 reservation conflicts on VMFS LUNs caused by delayed processing of SCSI-2 reservation commands on the HP 3PAR Storage System, thereby helping to avoid VM I/O failure. Changing this value can be achieved through use of the VMware ESX VI/vSphere client: ESX server+Configuration tab, SoftwareAdvanced Settings+Scsi, scroll to Scsi.ConflictRetries, and change the value in the field. Click OK to complete the change. A reboot is not required for the change to take effect. The VMware vCenter Site Recovery Manager and the HP 3PAR Adapter for VMware Site Replicator require newer versions to be compatible with InForm OS 3.1.1. For details, see VMwares Site Recovery Manager Storage Partner Compatibility Matrix: http://www.vmware.com/pdf/srm_storage_partners.pdf The recovery manager for Oracle, SQL, Exchange or VMware may require a newer version to be compatible to InForm OS 3.1.1. See the HP 3PAR OS InForm Configuration Matrix for InForm OS 3.1.x for supported levels. Please verify compatibility of any host third-party software to the InForm OS release 3.1.1. The HP 3PAR System Reporter requires an update to be compatible with InForm OS 3.1.1. When you upgrade the HP 3PAR Storage System to InForm OS 3.1.1, you must then upgrade the HP 3PAR System Reporter CLI to InForm OS 3.1.1. (If you upgrade the HP 3PAR System Reporter CLI first, and then upgrade to InForm OS 3.1.1, HP 3PAR System Reporter will detect only the previous version of InForm OS.) An updated CLI client for InForm OS 3.1.1 MU1 must be installed on the Recovery Manager host. See the HP 3PAR OS InForm Configuration Matrix for InForm OS 3.1.1 for supported levels. For host compatibility, see the HP SPOCK website: www.hp.com/storage/spock The InForm Management Console (IMC) is generally compatible with all 2.2.4, 2.3.1, and 3.1.1 InForm OS levels. For the latest features and fixes, it is advisable to upgrade to the current IMC release. For hosts running HP 3PAR Cluster Extension (CLX) software that are being upgraded to HP 3PAR InForm OS 3.1.1, the InForm OS 2.3.1 CLI must be run on all nodes in the HP 3PAR CLX. Do not upgrade the CLI on those nodes to 3.1.1 CLI. However, if you upgrade to InForm OS 3.1.1 MU1, you can upgrade the nodes to 3.1.1 MU1 CLI. For hosts running HP 3PAR CLX that are being upgraded to HP 3PAR InForm OS 3.1.1 MU1, the host CLI must be updated to the InForm OS 3.1.1.MU1 CLI before the HP 3PAR Storage System is updated to InForm OS 3.1.1.MU1. CAUTION: When upgrading to InForm OS 3.1.1 MU1, you must upgrade the InForm CLI to InForm OS 3.1.1 MU1 on any node attached to the array. Otherwise, HP 3PAR CLX will fail to perform failover/failback operations on Remote Copy volume groups or other applications.

InForm OS 2.3.1 Persona Changes

Use Table 3 (page 14) when migrating directly from InForm OS 2.2.x to OS 2.3.1 or OS 3.1.1. The change occurs automatically as part of the Rolling Upgrade or by Offline Upgrade. NOTE: VCN will be disabled by default on all ports when HP 3PAR Storage System server migration to 2.3.1 completes.
Host Configuration Guidelines 13

Table 3 Persona Translation Table

2.2.x Port Persona - Topology 0 - Loop 1, 2, 3, 4 - Loop 5 (HPUX) - Loop 7, 9, 10, 15 - Point 8 (HPUX) - Point 1 (Egenera) - Loop 1 12 (Egenera) - Point 13 (AIX) - Loop 14 (AIX) - Point 18 (NetApp) - Loop 19 (NetApp) - Point 16 (RCFC) - Loop 17 (RCFC) - Point All iSCSI configurations 2.3.1 Host Persona - Topology (No persona) - Loop 6 (Generic - Legacy) - Loop 7 (HPUX - Legacy) - Loop 6 (Generic - Legacy) - Point 7 (HPUX -Legacy) - Point 9 (Egenera) - Loop 9 (Egenera) - Point 8 (AIX - Legacy) - Loop 8 (AIX - Legacy) - Point 10 (ONTAP - Legacy) - Loop 10 (ONTAP - Legacy) - Point (No persona) - Loop (No persona) - Point 6 (Generic - Legacy)

Once the HP 3PAR Storage System server is running InForm OS 2.3.1, it is recommended that the host persona for some of the hosts be changed. See Table 4 (page 14) . Table 4 Host Persona Details Table
Operating System Red Hat 4 and 5, SUSE 10 and 1 - Fibre channel and 1 iSCSI (Except SUSE 1 1 iSCSI, which should be left at Persona 6) W2k3 including iSCSI Solaris (except Solaris 8), including iSCSI W2k8 SP1 and SP2 and Solaris 8, including iSCSI Persona when migrated to 2.3.1 6 Change to Persona 1 Notes Use of generic persona allows the host server to run Host Explorer on the host. It will automatically create LUN 254 as an SCSI enclosure device for Host Explorer use.

6 6 6

1 1 2 Enabling host persona 2 will enabled A/A multipath on LUNs by default This change will require a reboot. Do not change the host persona unless you can reboot the W2k8 server. If you do not reboot the server, the host will lose the mapping of the LUNs. Microsoft enables A/A multipathing by default at Windows 2008 R2 For VMware 4.0 only change the SATP rules on host to enable Active/Active Round Robin by default. Refer to the HP 3PAR VMware ESX Implementation Guide for instructions about changing the ESX 4.0 SATP rules.

W2k8 R2 including iSCSI VMware (3.5, 4.0)

6 6

1 6

14

Guidelines for Online Updates

To change the host persona of a host:

<persona _number> <host_name>

cli% sethost persona

To verify the host persona setting of a host:

cli% showhost persona <host_name>

NOTE: If a host server is powered down during an upgrade from InForm OS 2.2.x to InForm OS 2.3.1 or OS 3.1.1, the recommended host persona for the type of host that is down should apply, as the upgrade assigns host persona 6 to the server. In some cases, it would prevent the host from operating correctly, as is the case with HP-UX, AIX, and NetApp.

Storage Server Configuration Guidelines

The following guidelines must be observed when planning an online InForm OS update:

General Configuration Guidelines

A vLUN for each exported volume must be exported to a defined host on at least two fully operational paths that span adjacent storage server nodes, an even-numbered node followed by a consecutive odd-numbered node, on the storage system. (Valid pairings are 0 & 1, 2 & 3, 4 & 5, 6 & 7.) HP 3PAR software applications running on the HP 3PAR Storage System server must be shut down. Ensure that no HP 3PAR Virtual Copy promotes are in progress. To confirm, check that no volumes are in the started, cpp state. If any promotes are in progress, wait until the promote finishes to begin the online update.

Remote Copy Guidelines

WARNING! For HP 3PAR Storage Systems licensed with Remote Copy, do not upgrade directly from InForm OS 2.2.4 to InForm OS 3.1.1. These upgrade conditions are not supported and will fail. See Remote Copy Support Across InForm OS Levels (page 6) For systems running InForm OS 2.2.4 or later with Remote Copy, only the groups need to be stopped. Stop the remote copy groups after the synchronization has completed via stoprcopygroup group name/s. InForm OS 2.2.4 systems with Remote Copy cannot be upgraded directly to InForm OS 3.1.1. InForm OS 2.2.4 systems with Remote Copy must be upgraded to InForm OS 2.3.1 before an upgrade to InForm OS 3.1.1. (including offline upgrades). Remote Copy Ethernet ports must be set to autonegotiate. If they were changed to 100 Mbs full duplex, the links may not start when performing a software update to InForm OS 3.1.1. The autonegotiate setting can be changed in advance of a software update by executing controlport rcip speed auto <value> <n:s:p>. This should be performed on one RC link at a time, making sure to check that the link is working before setting the other link to autonegotiate.

Storage Server Configuration Guidelines

15

Planning Information for Online InForm OS Updates

The host connectivity environment must adhere to the qualified and supported environments (see the appropriate HP 3PAR OS InForm Configuration Matrix. HP service representatives will request this information for review before performing an online update. Relevant details include: Host platform Architecture (for example, SPARC/x86) OS (version and patch level) DMP software HBA (vendor, model, driver, firmware, and version. Also include FCODE and BIOS level if booting from the HP 3PAR Storage System server) Switch (vendor, model and firmware) Information on host software provided by HP is needed. Examples include: HP 3PAR Recovery Manager (SQL, Exchange, Oracle), HP 3PAR VSS Provider, HP 3PAR MPIO for Microsoft Windows, HP 3PAR ODM Definition for IBM AIX, HP 3PAR System Reporter, etc. In addition to verifying the driver/firmware levels match the HP 3PAR OS InForm Configuration Matrix, there may be host configuration settings that are needed as documented in the HP 3PAR implementation guides. These settings need to be verified before an online update is performed.

The HP 3PAR OS InForm Configuration Matrix is available on the HP SPOCK website: www.hp.com/storage/spock

16

Guidelines for Online Updates

4 Veritas DMP and Online Updates

For all servers that are connected to the HP 3PAR Storage System server and use Veritas DMP (VxDMP) for the multipathing solution (except as noted in Host Configuration Guidelines (page 9)), the default value of the link restore interval must be changed before performing an online update of the InForm OS.

Changing the Veritas DMP Link Restore Interval

The following procedure is required if you are performing an online update to the InForm OS and Veritas DMP is being used for the multipathing solution on the host. The procedure must be repeated for each host server connected to the HP 3PAR Storage System server and using Veritas 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

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: occurs.

The restore daemon reverts to the default value of 300 if or when a host reboot

Restoring the Veritas DMP Link Restore Interval

If you are using Veritas DMP, use the following commands to change the link restore interval to the previous setting on storage server hosts after completing an online update. The following procedure must be repeated for each host server connected to the HP 3PAR Storage System server 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=<prior setting>

Changing the Veritas DMP Link Restore Interval

17

3.

Verify the daemon is running with the interval set to the prior setting.
# vxdmpadm stat restored

18

Veritas DMP and Online Updates

5 Sun Cluster Configuration Guidelines

There are some InForm OS online configuration rules to be aware of for Sun Cluster configurations. InForm OS online upgrades with attached Sun Cluster hosts are not supported by HP for major InForm OS releases before InForm OS 3.1.1. (For example, an update from InForm OS 2.3.1 to 3.1.1 is considered a major OS release that is not supported). As of InForm OS 2.2.4 MU2, online maintenance updates can be successfully performed by using the pause option for the upgrade, for example, 2.2.4 MU2 to 2.2.4 MU4 or 2.3.1 GA to 2.3.1 MU1. Wait for all I/O paths for all Sun Cluster nodes to recover during each pause between InServ node updates. Refer to the details about implementing the pause option below. As of InForm OS 3.1.1 GA, online updates can be successfully performed by means of a single-node (aka node-by-node) update and implementing the pause option between HP 3PAR Storage System node updates. Wait for all I/O paths for all Sun Cluster nodes to recover during each pause between HP 3PAR Storage System node updates. Refer to the details about implementing the pause option below.

Implementing the pause option for an online maintenance update will cause a wait for user input in between each node reboot needed during an online InForm OS update. This pause time in the upgrade process is used to allow all of the I/O paths to all of the Sun Cluster nodes, for all of the presented LUNs to recover (failback). In Sun Cluster, this is a function of Solaris SSTM MPxIO. Failure to wait for all I/O paths to return results in fatal I/O errors and off-lining of Sun Cluster resources. The recovery of the I/O paths must be monitored at each individual Sun Cluster node. Status of the Sun Cluster I/O paths cannot be assessed from the HP 3PAR Storage System server. On each individual Sun Cluster node the command mpathadm list lu is run, and the output is analyzed to see that all paths to all devices are enabled. Identifying all paths as enabled is accomplished by noting that Operational Path Count: equals Total Path Count: for all devices in the list. The command mpathadm list lu outputs the current path status. Running the command multiple times on each Sun Cluster node may be necessary in order to monitor the paths as they come up. The upgrade should be paused until Operational Path Count: matches Total Path Count: in the mpathadm list lu output for all devices on all Sun Cluster nodes. Note that the pause time necessary may be many minutes, depending on the number of host cluster nodes, I/O paths, and devices. Sample output; in this case all paths are up:
# mpathadm list lu /dev/rdsk/c4t50002AC0003200D8d0s2 Total Path Count: 4 Operational Path Count: 4

Sample output; in this case all paths are not up: NOTE: Only two of four paths are up in the output below, continue to wait until Total Path Count equals Operational Path Count.
/dev/rdsk/c4t50002AC0003100D8d0s2 Total Path Count: 4 Operational Path Count: 2

19

6 Exanet ExaStore Clustered NAS System Prerequisites

There are special procedures that will need to be performed on an Exanet ExaStore v4.0.x Clustered NAS system when an InForm OS update needs to take place. In the standard ExaStore configuration, NAS clients that connect to the ExaStore might experience excessive periods of I/O quiescence during the InForm OS upgrade. Contact Exanet for details on obtaining this script as well as specific usage instructions. An overview of the process is included for quick reference: The procedure includes running two scripts: 1. Pre-upgrade script, which performs the following: 2. Modifies appropriate configuration values. Generates the post-upgrade script so that the system can be returned to the standard configuration after the InForm OS software update is completed.

Post-upgrade script, which sets all appropriate values that were modified in the Pre-upgrade script back to their original values.

20

Exanet ExaStore Clustered NAS System Prerequisites

7 VMware ESX Server

Once the HP 3PAR Storage System server is upgraded to InForm OS 2.3.1, the VMware ESX Server Scsi.ConflictRetries parameter should be returned to its default value or 80 on all VMware ESX servers that connect to the HP 3PAR Storage System, if previously changed to 200 as directed by HP. InForm OS 2.3.1 contains a fix for the issue in previous InForm OS versions where ESX SCSI-2 reservation release commands could be delayed by the Sysmgr configuration lock resulting in virtual machines I/O errors.

21

8 Remote Versus Local Methods for an InForm OS Update

Read this section for information regarding the difference between a remote online update and a local online update.

Remote InForm OS Updates

Remote InForm OS updates are achieved by utilizing HPs Remote Operations Service Tools (RemOps) (for example, via Ethernet or modem). The process used for remote InForm OS updates depends on the connectivity model allowed for remote updates. There are three connectivity models: Ethernet RemOps: Service processor software updates can be downloaded, staged, and performed remotely. Modem RemOps: The service processor software CD can be supplied to the customer to place in the service processor CD-ROM drive, and the update can be performed remotely. Temporary RemOps: In some cases, customers will temporarily open up connectivity to the service processor for Remote Operations for software updates. If temporary Remote Operations access can be granted, we will be able to perform the update remotely.

Local InForm OS Updates

Local InForm OS updates are achieved by utilizing an on-site service representative to perform the update. Typically, local InForm OS updates are performed when there is no remote connection to the service processor. Additionally, a local InForm OS update may be combined with other on-site activities, such as hardware updates or maintenance.

22

Remote Versus Local Methods for an InForm OS Update