文本讲义分析upgrade

1、Module 4informos upgradeCourse ObjectivesAt the end of this presentation the student should be able to:Understand the 3PAR software upgrade processUnderstand the naming of InformOS versionsExplain how to upgrade the InformOS and install patches 3PAR software upgrade processMail with InServ SN with t

2、he request.SWINS Team initiates the Host worksheet process with the Customer/Point of Contact.Customer/Point of Contact to complete Host worksheet and revert. SWINS Team assign a Deployment Engineer to review host worksheet and provide analysis.Deployment Engineer completes Host worksheet review in

3、5 business days and provides analysis to the customer/Point of Contact.Waiver required from the customer if there are pliant hostsSWINS Team schedules the activity and assigns remote support for the activity (Lead time of 3-4 business days is requested)InForm OS Versions 2.1.x, 2.2.1, 2.2.2 , 2.2.3

4、2.2.4 2.2.4 MU7 most recent 2.2.4 version.1 MU5 most recent 2.3.1 version3.1.1 64-bit supported only at P10000 (V-class), T/F class3.1.1 MU1 most recent 3.1.1 versionOfficially supported versions are two major versions 2.3.1 and 3.1.1This means only 2.3.1 and 3.1.1 will be fixedProblems enco

5、untered at earlier version will still be investigated but will not be fixedSee below notes for InForm OS version and MU mappingInForm OS PatchesPatches are released on a per need basiscritical bug fixes, new PD model supportPatch naming: P01, P02, P03 . P12, P13, P14 3.1.1 P01 P06 P91Patches are onl

6、ine installableUsually with no effect to host IO. Alert may occur when major process restart happens.Patches cannot be deinstalledDegradation due to a bad patch will be fixed via a new patch reissueSP patch is also released on a per need basisSP Patch naming: Sppatch P001 P002 P003 P004InForm OS Upd

7、ate Overview OS Update OverviewThe 3PAR InServ Storage 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 3PAR). Remote updates require that remote operations are available.Online

8、UpdatesThe InServ Storage Servers support online, non-disruptive updates of the InForm OS. Online updates are achieved by installing the new software on all the nodes in an alternate location designated as the new software repository.Offline UpdatesOffline updates require that all hosts connected to

9、 the InServ Storage Server should be shut down before he InForm OS update.memoTypes of OS Upgrade There are three types of InformOS upgrade:Half-system Online UpdateUsed when there is major OS level change, e.g.2.3.1 to 3.1.1Used when there is OS maintenance level change before 3.1.1, e.g. 2.3.1.MU4

10、 to 2.3.1 MU5Half of the nodes are updated at one time, then the other half of the nodes are updated at one time.Single-node Online UpdateUsed when there is OS maintenance level change after 3.1.1, e.g. 3.1.1.GA to 3.1.1 MU1Each node is updated one at a time.Offline OS upgradeUsed when the customer

11、requests an offline update, or when the system is operating several levels below the update package version.All nodes are updated, then rebooted at the same time. The system is unavailable to the hosts during this operation.Single node update- automatic vs. manualWhen executing single-node online up

12、date, you may choose to use automatic upgrade or manual upgrade:Automatic upgradeWill involve the InServ automatically installing the software and rebooting the nodes. There is no interaction with the user during this process and no control as when nodes will reboot Manual upgradeWill stop between e

13、ach node reboot. You will be required to enter y to continue to the next node. The maximum wait time should be limited to 30 Minutes. General GuidelinesObserve the following general guidelines in respect to online InForm OS updates:Hardware and configuration changes should not be performed on the In

14、Serv during the For example, software operations (such as servicemag, createaldvv, or use of the 3PAR 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 Provisioni

15、ng Groups continue uninterrupted as under normal operation.The storage server must be in a “healthy” state (e.g. 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 upd

16、ate (for example, rebooting, applying patches, or re-zoning 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

17、with the InServ management interface (scripting) must be stopped before performing an online update.Whenever possible, schedule and perform online updates during periods of low I/O activity.Mechanism of InForm OS Upgrade and Installing Patches via SPInForm OS or patch install to the SP from CDROM or

18、 from staged softwarestaged software via CDROM or via connection portalinstalled (into the SP) InForm OS or patch is saved at an SP directory (as package files)/sp/prod/data/updates/os/For OS upgrade, “upgradesys” is called from spmaint tool For Patch installation, “upgradesys” is run at the cli.upg

19、radesys -load /sp/prod/data/updates/os/patch/3.1.1/P13.patchInForm OS Upgrade Analysis/Preparation Process (1)Reference docs: Support Matrix, Preupgrade Planning GuideCustomer to provide Host WorkSheetHosts analyzed against Support Matrix for support conformanceInServ configuration analyzed also for

20、 health status and configuration conformance.All known issues are also consideredInForm OS Upgrade is currently owned by 3PAR NTSS Team. Field dispatch is requested on customers that do not allow remote access.InForm OS Upgrade Analysis/Preparation Process (2)Customer host/OS/server/HBA/cluster/FC switch against Support MtxNo error or problem situation at InServ config (using health check file)single pathed