HP 3PAR Operating System Upgrade Pre-Planning Guide Abstract This guide is intended for use as a planning tool for HP customers.
© 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.
Contents 1 HP 3PAR OS Upgrade Overview..................................................................4 Audience.................................................................................................................................4 Supported Upgrade Types.........................................................................................................5 2 Guidelines for Online Upgrades...................................................................
1 HP 3PAR OS Upgrade Overview This guide provides the following information on HP 3PAR Operating System Operating System (HP 3PAR OS) 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 DMP prerequisites for online upgrades • Remote versus local methods of upgrading The HP 3PAR StoreServ Storage supports two different methods
Supported Upgrade Types HP 3PAR OS upgrades may either be performed online or offline. Online upgrades allow the hosts connected to the system to continue I/O activity; for offline upgrades, host I/O activity must be stopped. 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 3PAR OS 3.1.1, all online upgrades are node-by-node. Each array node is upgraded one at a time.
2 Guidelines for Online Upgrades Follow the guidelines in this chapter for online HP 3PAR OS upgrades. Planning Information for Online HP 3PAR OS Upgrades The host connectivity environment must adhere to the qualified and supported environments. For more information, see the appropriate interoperability information on the HP SPOCK website. HP service representatives will request this information for review before performing an online upgrade.
Observe the following general guidelines in respect to online HP 3PAR OS updates: WARNING! All hosts must be compliant with the current applicable HP 3PAR host OS implementation guides for the target HP 3PAR OS level. Hosts that do not comply completely with the implementation guides may lose connectivity during the HP 3PAR OS upgrade. • Hardware and configuration changes should not be performed on the HP 3PAR StoreServ Storage during the update.
◦ 4&5 ◦ 6&7 Invalid pairings are: • ◦ 2&1 ◦ 0&3 All attached hosts must have multipathing software in place and operational for every HP 3PAR 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 HP 3PAR storage server system. Valid pairings are: ◦ 0&1 ◦ 2&3 ◦ 4&5 ◦ 6&7 NOTE: See HP SPOCK streams, available on the HP SPOCK website, for supported multipathing environments.
• The HP 3PAR System Reporter requires an upgrade to be compatible with HP 3PAR OS 3.1.1 or later. When you upgrade the HP 3PAR StoreServ Storage to HP 3PAR OS 3.1.1 or later, you must then upgrade the HP 3PAR System Reporter CLI to HP 3PAR OS 3.1.1 or later. (If you upgrade the HP 3PAR System Reporter CLI first, and then upgrade to HP 3PAR OS 3.1.1 or later, HP 3PAR System Reporter will detect only the previous version of HP 3PAR OS.
NOTE: VCN will be disabled by default on all ports when HP 3PAR StoreServ Storage migration to HP 3PAR OS 2.3.1 completes. Table 2 Persona Translation Table HP 3PAR OS 2.2.x HP 3PAR OS 2.3.
Table 4 Host Persona Capabilities Defined in HP 3PAR OS 3.1.2 MU3 Persona ID Persona Name Persona Capabilities 1 Generic UARepLun, SESLun 2 Generic - ALUA UARepLun, RTPG, SESLun 6 Generic - legacy 7 HP-UX - legacy VolSetAddr, Lun0SCC 8 AIX - legacy NACA 9 EGENERA SoftInq 10 ONTAP - legacy SoftInq 11 VMware SubLun, ALUA 12 OpenVMS UARepLun, RTPG, Lun0SCC Once the HP 3PAR StoreServ Storage is running HP 3PAR OS 2.3.
Table 5 Host Persona Details Table Operating System HP 3PAR OS 2.3.1 Host Persona HP 3PAR OS 3.1.1 Host Persona HP 3PAR OS 3.1.2 Host Persona HP 3PAR OS 3.1.3 Host Persona AIX 8 8 8 8 HP-UX 11i v1 and 11i v2 7 7 7 7 HP-UX 11i v3 7 7 7 71 13 NetApp/ONTAP 2, 3 RHEL 5.8, 6.1 and later 10 10 10 10 1 or 6 1 1 14 2 RHEL 4 and RHEL 52 SLES 10.4, 11.
6 7 Host Persona 6 will not be supported for any version of VMware ESX/ESXi with future HP 3PAR OS versions after HP 3PAR OS 3.1.3 and its MUs. HP recommends that customers migrate their VMware ESX configurations on HP 3PAR to Host Persona 11 with HP 3PAR OS 3.1.2 or later. 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 is recommended.
• 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 no volumes are in the started, cpp state. If any promotes are in progress, wait until the promote finishes to begin the online upgrade.
Table 6 HP 3PAR Remote Copy Support (continued) HP 3PAR OS Level – System A HP 3PAR OS Level – System B Supported? 3.1.1.nnn 3.1.2.nnn Yes 3.1.1.nnn 3.1.3.nnn Yes 3.1.2.nnn 3.1.3.nnn Yes WARNING! When HP 3PAR Remote Copy software is configured, direct upgrades performed directly from all levels of HP 3PAR OS 2.2.4 to HP 3PAR OS 3.1.1 will fail. This holds true for offline upgrades and instances when HP 3PAR Remote Copy is simply disabled.
1. Check the status of the quorum by issuing the showrcopy -qw command. For example: # showrcopy -qw targets Remote Copy System Information Status: Started, Normal Target Information Name ID Type Status Policy QW-IP Q-Status Q-Status-Qual s210 3 IP ready mirror_config 10.112.135.205 Started 2. Stop the quorum witness by issuing the setrcopytarget witness stop command. For example: # setrcopytarget witness stop s210 3.
3 Red Hat, Oracle, Linux, and SUSE Guidelines Observe the following host configuration guidelines when planning an online HP 3PAR OS upgrade for Red Hat, Oracle, Linux, or SUSE OSs: • The SCSI timeout value for RHEL 4 and SUSE 9 must be changed from the default of 30 seconds to 60 seconds. To change the timeout value, see the HP 3PAR host OS implementation guide specific to the OS. This needs to be performed for both FC- and iSCSI-connected hosts.
4 Sun/Solaris Configuration Guidelines As of HP 3PAR OS 3.1.1 GA, online upgrades can be successfully performed by means of a node-by-node (aka “Advanced”) upgrade and pausing between HP 3PAR StoreServ Storage node upgrades. Wait for all I/O paths for all Sun Cluster nodes to recover during each pause between HP 3PAR StoreServ Storage node upgrades. See “I/O Path Monitoring for Solaris” (page 18). NOTE: Solaris 10 MU3 with an iSCSI configuration is not supported for online upgrades.
Class primary State OFFLINE 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 ON
State State OFFLINE ONLINE When the State of all paths is ONLINE, the node-by-node upgrade sequence may proceed to the next array node.
5 Symantec Veritas Storage Foundation DMP (VxDMP) and Online Upgrade NOTE: For hosts running RHEL 6 or SLES 11 with Storage Foundation VxDMP 6.0.x, only offline upgrades 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 Storage Foundation VxDMP multipath software require a pause to be implemented between upgrades of the array nodes within the system.
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.
6 VMware ESX Server Guidelines NOTE: Host persona 11 is the HP-recommended host persona for all supported versions of VMware ESX with HP 3PAR OS 3.1.2 and later. After HP 3PAR OS 3.1.3 and its MUs, host persona 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).
7 Windows Server OS Guidelines This chapter describes host configuration guidelines for Windows Server OSs. Rebooting after an Upgrade On the first Windows Server 2008, 2008 R2, 2012, or 2012 R2 reboot following an HP 3PAR array firmware upgrade (whether a major upgrade or an MU update within the same release family) the Windows server will mark the HP 3PAR LUNs as offline, but the data remains intact.
3. The Administrator will then be prompted to provide a Vendor String, which is used to distinguish between different vendor types. The script will only modify those devices whose 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 currently presented to the host as shown in the output below: Enter Vendor String: 3PAR 4.
See the HP 3PAR Windows Server 2012 and Windows Server 2008 Implementation Guide for more 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 OS 2.3.1, or from HP 3PAR OS 2.3.1 to HP 3PAR OS 3.1.
the required hotfixes, see the Windows Server 2008 and Windows Server 2008 R2 SPOCK configurations on the HP SPOCK website. A hotfix, available from Microsoft, is required to support live storage migrations with Windows Server 2012 using Cluster Shared Volumes on HP 3PAR OS 3.1.2 and later. The hotfix must be applied before upgrading the HP 3PAR StoreServ Storage. For more information about the required hotfix, see the Windows Server 2012 SPOCK configuration on the HP SPOCK website.
8 AIX Guidelines HP 3PAR OS online automatic upgrades with AIX Direct Connect attached hosts are not supported by HP for any HP 3PAR OS upgrades. Online maintenance upgrades can be successfully performed by means of a node-by-node (or advanced) upgrade method. Using this method will cause the system to wait for user input between each node reboot needed during an online HP 3PAR OS upgrade.
9 Support and Other Resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
For information about: See: Migrating data from one HP 3PAR storage system to another HP 3PAR-to-3PAR Storage Peer Motion Guide 30 Configuring the Secure Service Custodian server in order to monitor and control HP 3PAR storage systems HP 3PAR Secure Service Custodian Configuration Utility Reference Using the CLI to configure and manage HP 3PAR Remote Copy software HP 3PAR Remote Copy Software User’s Guide Upgrading HP 3PAR operating systems HP 3PAR Upgrade Pre-Planning Guide Identifying storage sy
For information about: See: Planning for HP 3PAR storage system setup Hardware specifications, installation considerations, power requirements, networking options, and cabling information for HP 3PAR storage systems HP 3PAR 7200, 7400, and 7450 storage systems HP 3PAR StoreServ 7000 Storage Site Planning Manual HP 3PAR StoreServ 7450 Storage Site Planning Manual HP 3PAR 10000 storage systems HP 3PAR StoreServ 10000 Storage Physical Planning Manual HP 3PAR StoreServ 10000 Storage Third-Party Rack Physic
Typographic conventions Table 7 Document conventions Convention Element 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
10 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
