HP 3PAR Operating System Upgrade Pre-Planning Guide Abstract This guide is intended for use as a planning tool for HP customers who are system and storage administrators.
© 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 (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 for upgrading th
NOTE: This 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. Supported Upgrade Types HP 3PAR OS upgrades are performed either 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.
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 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 according to online HP 3PAR OS updates: WARNING! All hosts must comply 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. • Do not perform hardware and configuration changes on the HP 3PAR StoreServ Storage during the update.
NOTE: ◦ See HP SPOCK streams, on the HP SPOCK website, for supported multipathing environments. ◦ For unsupported environments, the hosts should be shut down and in some cases powered off. The VLUNs exported to such hosts must be unexported or connections must be logically disconnected before the online HP 3PAR OS upgrade. • A host definition must not contain initiators from multiple hosts. For example, host cluster configurations must use a separate host definition for each host in the host cluster.
NOTE: After upgrading from HP 3PAR OS 3.1.2 MU3 to 3.1.3 MU1, the passive node hangs during a restart. This was observed with: HP 3PAR OS 3.1.3 MU1 (including patches), Microsoft Windows Server 2012 R1 Standard Edition and HP Cluster Extension V4.0. ◦ If the boot disk without any clustered disks are presented, the system restarts correctly. ◦ If one of the clustered disks is added, the passive node hangs during the restart.
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 (continued) Persona ID Persona Name Persona Capabilities 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.1 or later, it is recommended that the host persona for some of the hosts be changed. See Table 5 (page 12) .
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 MU1 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 MU1 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.
by a consecutive odd-numbered node, on the HP 3PAR StoreServ Storage. (Valid pairings are 0 & 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 no volumes are in the started, cpp state. If any promotes are in progress, wait until the promote finishes to begin the online upgrade.
upgraded to HP 3PAR OS 2.3.1 MU5 before an upgrade to HP 3PAR OS 3.1.3. (including offline upgrades). • When an upgrade to HP 3PAR OS 3.1.1 is performed, HP 3PAR Remote Copy Ethernet ports must be set to autonegotiate.
Local HP 3PAR OS Upgrades Local HP 3PAR OS upgrades are achieved by utilizing an on-site service representative to perform the upgrade. Typically, local HP 3PAR OS upgrades are performed when there is no remote connection to the service processor. Additionally, a local HP 3PAR OS upgrade may be combined with other on-site activities, such as hardware upgrades or maintenance. Start-and-Stop Quorum Witness Steps Before performing an online upgrade to HP 3PAR OS 3.1.
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 the Not-started state. This may take several (15–30) seconds.
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 OS: • 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 19). NOTE: Solaris 10 MU3 with an iSCSI configuration is not supported for online upgrades.
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 d
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 to be run through several iterations on each Solaris Cluster node before all I/O paths are shown as ONLINE.
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: The restore daemon reverts to the default value of 300 if or when a host restart 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 OS. Rebooting After an Upgrade On the first Windows Server 2008, 2008 R2, 2012, or 2012 R2 restart 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.
To turn maintenance mode on or off for each of the cluster HP 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 Quorum Witness 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.
Vista Business, and Windows XP Professional). When an HP 3PAR StoreServ Storage is upgraded to 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 3PAR Peer Motion Manager 1.1 or earlier can be used for data migration.) However, provided the CLI is upgraded to 3.1.1 MU1, HP 3PAR OS 3.1.1 MU1 supports VMware cluster data migration using HP 3PAR Peer Motion Manager 1.2. For HP 3PAR OS 3.1.
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 restart needed during an online HP 3PAR OS upgrade.
9 HP-UX Guidelines IMPORTANT: To preserve the boot from SAN (BFS) setup for HP-UX PA-RISC servers running any supported OS version, the following steps must be completed before rebooting the server and after the HP 3PAR OS on the arrays is upgraded. After the HP 3PAR OS on the array is upgraded, run the following commands before rebooting the server: 1. Run the insf -e command. 2. Run the ioscan command. 3.
Issue If a rescan of the HP-UX I/O system hardware is run during the HP 3PAR OS online upgrade process, ioscan might report device paths with a Software State of NO_HW. This is due to a defect that causes an unexpected SCSI inquiry response to LUN 0 for HP-UX hosts during the HP 3PAR OS online upgrade. It was verified that I/O is not affected and paths remain accessible as long as the server is not restarted during the online upgrade process.
4. If the LUN paths display online, I/O is not affected and paths remain accessible as long as the 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 online upgrade will resume without I/O interruption.
10 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 34 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 HP 3PAR Remote Copy Software User’s Guide Updating HP 3PAR operating systems HP 3PAR Upgrade Pre-Planning Guide Identifying storage system compo
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 8 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
11 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.
