Patch-ID# 103017-04 Keywords: SPARCstorage Array SUNWssaop SUNWssadv Synopsis: SPARCstorage Array Solaris 2.5: Jumbo patch for SSA for Solaris 2.5 Date: Apr/16/96 When to apply: this patch should be applied to Solaris 2.5 machines that have SPARCstorage Arrays attached. Solaris Release: 2.5 SunOS Release: 5.5 Unbundled Product: Unbundled Release: Relevant Architectures: sparc BugId's fixed with this patch: 1225980 1223585 1210986 1221891 1220077 1219355 1229005 1223482 1210487 1210459 1222661 1220380 1226481 1219952 1222661 1220380 1226481 1233881 1232080 1199767 1218530 1234801 1227470 1232506 1201365 1230526 1223384 1237625 1231771 1233108 1189480 1229048 1242923 1220754 1247488 1247694 Changes incorporated in this version: 1242923 1229048 1220754 1247488 1247694 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: SUNWssadv: /kernel/drv/pln /kernel/drv/ssd /kernel/drv/soc SUNWssaop: usr/lib/firmware/ssa/ssafirmware (Version 3.6) usr/sbin/ssaadm usr/sbin/ssacli Problem Description: ******************************************************************* ******************************************************************* IMPORTANT NOTICE: The ssafirmware must be downloaded into the SSA after installing this patch. See the "Special Install Instructions:". ******************************************************************* ******************************************************************* 1242923 Stale SDS data read out of NVRAM. 1229048 pln: High load on 2 SSAs on a single SOCHA leads to performance degred ation. 1220754 SSA Firmware: missing cmds when using suspend/resume. 1247488 SSA Firmware 3.6 install notes needed to be corrected. 1247694 Readme for 103017 does not document SSA booted machines. (from 103017-03) 1233881 SSA firmware 3.3 sometimes restarts during poweron sequence. 1237625 ssd pln soc: Add code for Cray Research suspend/resume functionality + bug fixes. 1234801 RFE: Upgrade ssd to handle predictive failure sense codes. 1233108 soc login logic is faulty. 1232506 ssaadm display of a SSA210 module appears as a SSA100 module. 1232080 pln_ctlr: pdb system paniced with a data fault. 1231771 ssaadm: solaris 2.4, VM2.1, hotspare replace worked but error messages continue. 1230526 SSA lcd icons go to sleep under certain circumstances. 1227470 System hangs when inserting disktray in ssa102 after 'ssaadm stop -tn c n'. 1226481 SSA: Need new ssaadm/ssacli for pluto 2 and fast_write capability 1223384 soc, soc_ucode.c: SSA "Timeout recovery being invoked" OFFLINE/ONLINE. 1222661 ssaadm, ssd: display controller number fails if other host has disk(s) reserved. 1220380 ssaadm does not report clearly whether or not NVRAM is enabled 1218530 On Sunfire core not dumped on SSA even though it says so. 1201365 On dual-ported SSA, IO from one host can prevent access by other host. 1199767 pln_ctlr doesn't check for root when running a USCSI command. 1189480 if sparc storage array present wants it to pause during boot til ssa is ready. (from 103017-02) 1219952 SSA: 3.1 fw causes recursive condition on pluto 200 (from 103017-01) 1229005 SSA V3.x is needed for Pluto2 (aka SSA11x or SSA21x) 1225980 ssd, pln: there should be retries for both read/write in case of media/hw error 1223585 ssd ssafirmware: Don't retry ABORTED commands forever. 1223482 ssa firmware: ESC: data corrupt when doing many SYBASE inserts on SSA 1221891 pln: Set up and pass Task Attribute values based on tagged queuing flags. 1221633 ISP DMA failure transferring data during reads while testing with the scsirw_test. 1220077 Heavy I/O causes pluto2 to panic 1219355 SSA: P200 needs to support 7 disk targets 1210986 ssd: Raid5 : Double failure reported when one disk fails. 1210487 pln enters invalid state after link goes ONLINE. 1210459 pln enters reset recovery before link is taken offline. Patch Installation Instructions: -------------------------------- Refer to the Install.info file for instructions on using the generic 'installpatch' and 'backoutpatch' scripts provided with each patch. Any other special or non-generic installation instructions should be described below as special instructions. Special Install Instructions: ----------------------------- After installing the patch, here is how one goes about upgrading the firmware: 1. Enter the following command to see what the firmware level is for each SPARCstorage Array on your system: # /usr/sbin/ssaadm display controller where controller is either the logical controller name (given as cX) or the physical path of the controller (given as /devices/../../SUNW,soc@3,0/SUNW,plnaxxxxxx,xxxxxxxx:ctlr). For more information, see the ssaadm.1m man page. 2. Look at the output for a line similar to the following to find the firmware level: Firmware Rev: 3.4 3. Determine if you need to upgrade the firmware. If the firmware level produced from the ssaadm command (Step 2) is lower than 3.6 then you must upgrade your firmware. Go to Step 4. If the firmware level produced from the ssaadm command (Step 2) is the 3.6 or higher then you do not have to read any further in these instructions, since your firmware is already at the proper level. 4. If the firmware level produced from the ssaadm command is lower than 2.4 you MUST complete the following steps for those SPARCstorage Arrays that contain firmware revision lower than 2.4. If the firmware is 2.4 or higher you don't need to do step 4 so go to step 5. a) Enable the SSA fastwrite capability: # /usr/sbin/ssaadm fast_write -se b) Disable the SSA fastwrite capability: # /usr/sbin/ssaadm fast_write -sd where controller is either the logical controller name (given as cX) or the physical path of the controller (given as /devices/../../SUNW,soc@3,0/SUNW,plnaxxxxxx,xxxxxxxx:ctlr). CAUTION: This operation may take a few minutes to complete. Do NOT interrupt the operation before it is finished or the system may not be able to communicate with the SPARCstorage Array. 5. Download the SPARCstorage Array firmware to your SPARCstorage Array. If the host is booted off a SSA, the host MUST be rebooted for this operation. If the host is being rebooted only the steps 'e' and 'f' below need to be executed. The following steps must be completed on each SSA to download the firmware safely: a) Stop all I/O activity on the SPARCstorage Array. b) Perform a sync_data to the SSA: # /usr/sbin/ssaadm sync_cache c) Unmount any filesystems residing on the SSA disks. d) Stop all Veritas Volume manager (VxVA) volumes and/or Solistice Disk Suite (SDS) metadevices (if any) running on the SSA. Also insure that ownership of any SDS diskset metadevices have been released since an implicit I/O stream exists while ownership of a diskset is maintained. Please refer to the metaset(1M) manpage for details on taking/releasing ownership of disksets. e) Execute the ssaadm download command to download the new firmware: #/usr/sbin/ssaadm download -f /usr/lib/firmware/ssa/ssafirmware where controller is either the logical controller name (given as cX) or the physical path of the controller (given as /devices/../../SUNW,soc@3,0/SUNW,plnaxxxxxx,xxxxxxxx:ctlr). CAUTION: This operation may take a few minutes to complete. Do NOT interrupt the operation before it is finished or the system may not be able to communicate with the SPARCstorage Array. f) The SSA(s) will now need to be reset for the changes to take effect. If the host is booted off an SSA then the host MUST be shutdown at this point. Reset your SSA(s) by pushing the SYS OK button in the back of the unit(s). This causes the SPARCstorage Array to reboot using the new revision of firmware. If your host boots off an SSA it can now be booted up again. g) Restart the Veritas Volume manager (VxVA) and/or SDS metadevices and reclaim ownership of any SDS diskset metadevices that were relinquished. h) Remount the filesystems that reside on the SSA disks. 6. The firmware download is now complete. I/O activity on the SPARCstorage Array can be restarted.