3PAR InForm® Operating System 2.3.1 Upgrade Pre-Planning Guide 3PAR, Inc.
Changes The material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, 3PAR Inc. assumes no liability resulting from errors or omissions in this document or from the use of the information contained herein. 3PAR reserves the right to make changes in the product design without reservation and without notification to its users.
InForm OS Version 2.3.1 Release 2.3.1 Upgrade Pre-Planning Guide The following topics are covered in this guide: Introduction 3 InForm OS Update Overview 4 Guidelines for Online Updates 5 Planning Information for Online InForm OS Updates 14 Veritas DMP and Online Updates 15 Sun Cluster Configuration Guidelines 16 Exanet ExaStore Clustered NAS System Prerequisites 17 VMware® ESX Server 18 Remote versus Local Methods for InForm OS Update 18 1.
Release 2.3.1 Upgrade Pre-Planning Guide InForm OS Version 2.3.1 NOTE: 3PAR recommends updating host drivers to a supported level on InForm OS 2.3.1 before attempting an online update. Refer to the 3PAR InForm OS 2.3.1 Configuration Matrix (P/N 320-200172) for more information about supported driver levels on InForm OS 2.3.1. 2.0 InForm OS Update Overview The 3PAR InServ Storage Servers support two different methods for updating the InForm OS: online and offline.
InForm OS Version 2.3.1 Release 2.3.1 Upgrade Pre-Planning Guide software on all the nodes in an alternate location designated as the new software repository. The update proceeds by loading the new revision of the software on all of the controller nodes within the system simultaneously. The update process is considered complete and successful once all the nodes have re-initialized using the new revision of the software.
Release 2.3.1 Upgrade Pre-Planning Guide InForm OS Version 2.3.1 3.2 Host Configuration Guidelines Observe the following host configuration guidelines when planning an online InForm OS update: ■ All attached hosts must have multi-pathing software in place and operational for every storage server volume exported, and the host(s) must be connected to two horizontally adjacent nodes on the InServ Storage Server. NOTE: Check the 3PAR Configuration Matrix for supported multi-pathing environments.
InForm OS Version 2.3.1 ■ Release 2.3.1 Upgrade Pre-Planning Guide All system administration activities must be stopped while performing an Inform OS Online Update. This includes any provisioning activity, physical/virtual copy activity, and dynamic optimization. All active tasks must complete or be stopped before proceeding. 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).
Release 2.3.1 Upgrade Pre-Planning Guide ■ InForm OS Version 2.3.1 With Windows 2008 and 2008R2 Failover Clusters, including Failover Clusters as guest OS clustering in a virtual environment (for example: Win2008 R2 Failover Cluster as virtual machines on VMware ESX), server node-failover can occur while performing online software updates of the InForm OS.
InForm OS Version 2.3.1 ◆ ■ Release 2.3.1 Upgrade Pre-Planning Guide Microsoft KB 968287 for Windows 2008 The SCSI timeout value for RH4, 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 RH 4, 5 should be running with driver parameter PORTDOWN retry count (qlport down retry) set to 1.
Release 2.3.1 Upgrade Pre-Planning Guide ■ InForm OS Version 2.3.1 Recovery Manager for Oracle, SQL, Exchange or VMWare, may require a newer version to be compatible to InForm OS 2.3.1. Refer to the 2.3.1 Configuration Matrix for supported levels. ■ ■ Please verify compatibility of any host 3rd party software to the InForm OS release 2.3.1. System Reporter may require an update to be compatible to the InForm OS release 2.3.1. Refer to the 2.3.1 Configuration Matrix for supported levels.
InForm OS Version 2.3.1 Release 2.3.1 Upgrade Pre-Planning Guide 3.2.1 InForm OS 2.3.1 Persona Changes Use Table 1-1 below when migrating from InForm OS 2.2.x to 2.3.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 InServ Storage Server migration to 2.3.1 completes. Table 1-1. Persona Translation Table 2.2.x 2.3.
Release 2.3.1 Upgrade Pre-Planning Guide InForm OS Version 2.3.1 Once that InServ Storage Server is running InForm OS 2.3.1 it is recommended that the Host Persona for some of the hosts be changed. SeeTable 2 below. Table 2. Host Persona Details Table Persona when Change migrated to to 2.3.1 Persona Operating System Red Hat 4 and 5, SUSE 10 and 11 - Fibre channel and Notes Use of Generic persona allows the Host 6 1 server to run “Host Explorer” on the iSCSI (Except SUSE 11 iSCSI, host.
InForm OS Version 2.3.1 Release 2.3.1 Upgrade Pre-Planning Guide To verify the Host Persona setting on a host: cli% showhost persona NOTE: If a host server is powered down during an upgrade from 2.2.x to 2.3.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 HPUX, AIX, and NetApp. 3.
Release 2.3.1 Upgrade Pre-Planning Guide InForm OS Version 2.3.1 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. ■ Remote Copy VVs must be the same size on the primary and the secondary system. Earlier releases of InForm OS allowed the secondary VV in a remote copy group to be larger than the primary.
InForm OS Version 2.3.1 Release 2.3.1 Upgrade Pre-Planning Guide 5.0 Veritas DMP and Online Updates For all servers that are connected to the InServ Storage Server and use Veritas DMP for the multi-pathing solution (except as noted on page 6), the default value of the link restore interval must be changed before performing an online update of the InForm OS. 5.
Release 2.3.1 Upgrade Pre-Planning Guide InForm OS Version 2.3.1 5.2 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 InServ Storage Server and using Veritas DMP.
InForm OS Version 2.3.1 Release 2.3.1 Upgrade Pre-Planning Guide 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 InServ Storage 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.
Release 2.3.1 Upgrade Pre-Planning Guide InForm OS Version 2.3.1 The procedure includes running two scripts: 1 Pre-upgrade script, which performs the following: ◆ Modifies appropriate configuration values. ◆ Generates the post-upgrade script so that the system can be returned to the standard configuration after the 3PAR InForm OS software update is completed. 2 Post-upgrade script, which sets all appropriate values that were modified in the Preupgrade script back to their original values. 8.
InForm OS Version 2.3.1 ■ Release 2.3.1 Upgrade Pre-Planning Guide 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. 9.2 Local InForm OS Updates Local InForm OS updates are achieved by utilizing an on-site service representative to perform the update.
Release 2.3.1 Upgrade Pre-Planning Guide 20 InForm OS Version 2.3.
