OBSOLETE Patch-ID# 104710-01 Keywords: ssafirmware ssaadm disk FW Synopsis: OBSOLETED by 104708 Date: Mar/21/97 Solaris Release: 2.5.1 SunOS release: 5.5.1 Unbundled Product: Unbundled Release: Topic: SunOS 5.5.1: ssafirmware and ssaadm patch NOTE: THIS PATCH REQUIRES THE SSD/PLN PATCH (104708-01). THE CONTENTS OF THIS PATCH WILL BE COMBINED WITH THE SSD/PLN PATCH IN THE FUTURE. BugId's fixed with this patch: 1190977 1220596 1223884 1238425 1241003 1257125 1263860 4007520 4010805 Changes incorporated in this version: Relevant Architectures: sparc Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: 104708 on Feb/23/99 Files included with this patch: /usr/lib/firmware/ssa/ssafirmware /usr/sbin/ssaadm Problem Description: 1190977 When a disk tray is removed from a running pluto the led does not note it. 1220596 P200 needs to support Tabasco 8th non-disk target: environmental sensing card 1223884 pluto resets itself when a tray is pulled under heavy load 1238425 Pulling out a tray causes Pluto to lose all disk reservations on that tray 1241003 offline/online looping problem with 3.5 firmware 1257125 patch 103766-01: download 3.7 f/w to pluto cause FW option get lost 1263860 SSA: performance degradation with 3.8 firmware. 4010805 ssaadm -v fc_s_download fails when boot disk target id is 10 or more 4007520 HA 1.2 hangs, does not boot up with mirror disk failure Patch Installation Instructions: -------------------------------- Refer to the Install.info file within the patch 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. Special Install Instructions: ----------------------------- This patch requires the ssd/pln patch (104708-01) to be applied as well. 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.9 3. Determine if you need to upgrade the firmware. If the firmware level produced from the ssaadm command (Step 2) is lower than 3.11 then you must upgrade your firmware. Go to Step 4. If the firmware level produced from the ssaadm command (Step 2) is the 3.11 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.