Patch-ID# 113722-15 NOTE: *********************************************************************** READ THE TERMS OF THE AGREEMENT ("AGREEMENT") IN THE LEGAL_LICENSE.TXT FILE CAREFULLY BEFORE USING THIS SOFTWARE. BY USING THE SOFTWARE, YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS, PROMPTLY DESTROY THE UNUSED SOFTWARE. *********************************************************************** Keywords: storedge 3310 se3310 se3000 raid storage firmware safte Synopsis: SE3310 415F: StorEdge 3310 array controller firmware upgrade Date: Jun/13/2006 Install Requirements: NA Solaris Release: 8 8_x86 9 9_x86 10 10_x86 SunOS Release: 5.8 5.8_x86 5.9 5.9_x86 5.10 5.10_x86 Unbundled Product: StorEdge 3310 Array Controller Firmware Unbundled Release: 415F Xref: Topic: Relevant Architectures: sparc i386 NOTE: If the StorEdge PCI Dual Ultra3 SCSI Host Adapter, x6758A, is used to connect the Sun StorEdge 3310 array, the qus driver must also be updated. The updated qus driver is available in the following patches: Solaris 8 Operating Environment: 112697 Solaris 9 Operating Environment: 112706 Solaris 10 Operating Environment: 119555 BugId's fixed with this patch: 4702532 4714227 4714811 4717055 4722548 4723464 4726561 4739050 4743721 4764506 4792748 4797299 4799098 4801970 4802207 4806105 4807600 4809787 4809793 4810830 4819226 4824129 4826944 4842604 4847052 4847479 4847938 4865270 4865630 4866684 4876079 4881105 4881109 4881122 4881127 4881132 4881136 4881138 4881139 4888526 4889104 4889967 4903457 4907020 4929829 4937092 4956272 4967518 4969758 4971693 4972674 4975612 4976389 4986468 4988102 4989784 4989809 4995551 5005317 5007650 5007664 5007911 5014319 5016154 5022022 5024472 5026029 5026182 5031134 5036067 5049931 5056104 5056930 5061519 5075581 5082165 5084418 5094779 5094897 6180281 6190524 6194894 6199412 6199413 6199414 6199416 6199449 6199453 6202488 6202496 6203390 6207987 6214522 6232208 6233475 6242752 6246702 6246708 6251454 6253745 6255677 6257852 6263359 6271102 6274609 6280423 6319544 6331219 6363490 6364192 6364194 6377021 6378782 Changes incorporated in this version: 4722548 4967518 6202488 6319544 6331219 6363490 6364192 6364194 6377021 6378782 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: README.113722-15 SUN-STOREDGE-3310-MIB.txt # SNMP MIB for installation in SNMP Managers SUN415F-3310.bin # RAID controller firmware rev 415F patchinfo saftefw_3310_1180.bin # SAF-TE firmware rev 1180 NOTE: Topics Included in this file: * Problem Description * Invoking Sun StorEdge CLI * Upgrading Controller Firmware 4.xx to 4.15 * SAF-TE Firmware Upgrade * After Upgrading * Special Install Instructions ==================== Problem Description: -------------------- This patch contains firmware that is installed on the Sun StorEdge 3310 RAID array controller and expansion chassis using Sun StorEdge CLI, rather than using installpatch or patchadd. Two types of firmware are included: RAID controller firmware that is installed in RAID controller modules, and SAF-TE firmware that is installed in both RAID controller chassis and disk expansion chassis. This patch also contains a SNMP MIB for installation in SNMP Managers such as HP OpenView Network Node Manager. This MIB is specific to the Sun StorEdge 3310. Refer to Appendix F, "SNMP Management Using HP OpenView," in the Sun StorEdge 3000 Family RAID User's Guide for information about MIB installation and use. You do not need to install this patch if you have all of the following firmware revision levels in all of your StorEdge 3310 enclosures: Controller firmware: 415F SAF-TE firmware: 1180 You do need to install this patch if you have any of the following: * controller firmware earlier than revision 415F, or * SAF-TE firmware 1170, 1167, 1159, A000 These README instructions require that RAID controller 4.1x firmware already be present on any arrays being upgraded. If your array currently has version 3.2x controller firmware installed, do NOT attempt to use the instructions in this README to upgrade from version 3.2x to version 4.15. Instead, follow the detailed instructions in the Sun StorEdge 3000 Family RAID Controller Firmware Migration Guide. This document is part of the Sun StorEdge 3000 Family documentation set and can be downloaded by following the links from Sun Product Documentation's Workgroup Storage web page: http://www.sun.com/products-n-solutions/hardware/docs/ Network_Storage_Solutions/Workgroup/ This patch contains firmware that is installed on the Sun StorEdge 3310 array using Sun StorEdge CLI, rather than using installpatch or patchadd. RAID firmware 415F addresses the following issues: 4722548 Selectable menu items in the firmware have no effect or are N/A to the product 4967518 Firmware doesn't track drive failure and the drive can scan back ok. 6202488 disabling media scan persistently 6331219 3310/3320 allow more than 128 luns to be mapped 6363490 Persistent parity error, like a toggled bit on the upper 8-bit of the cable can cause data corruption 6364192 grounded pins on the cable/controller can cause a bus hang 6364194 In single controller boxes implement firmware reset instead of watchdog reset 6377021 controller shutdown occurs after LD fatal fail 6378782 Controller may hang when receiving Bus Device Resets at an unusally high rate SAF-TE firmware 1180 addresses the following issues: 6319544 SAFTE fails to read Unique ID from seeprom (from 113722-11) RAID firmware 413B addresses the following issues: 4797299 Need data checking facility 4819226 Should have percentage complete for adding drives to an LD 4824129 Request for enhancement of messages on controller FW 6242752 Cabling in figure 4.5 and 4.6 does not match table 4.2 6255677 the media scan does not start back up on the rebuilt drive 6257852 LD_RESCUE support removed from SE3000 family without notification 6271102 Secondary RAID controller with disconnected battery reports status as "OK", Write-thru not sustained 6274609 SE3510 with Firmware 4.11I has dirty cache that cannot be destaged to disk 6280423 3310 stops responding after receiving illegal parameter (from 113722-10) RAID firmware 411K addresses the following issues: 4702532 write cache not automatically disabled when battery is off line 4714227 The character interface sometimes fails to respond correctly 4714811 Partition/Offset/Size screen should have more information 4726561 Aborting Parity Check results in "Parity Regeneration Failed" message 4739050 Lun initialization lost if power failure 4743721 SSCS: no method for identifying disk drives 4799098 NVRAM Restore does not prompt for reboot 4801970 SSCS shows a disk incorrectly under "copy and replace" from FW 4802207 SCSI Bus Reset and daemon.error under heavy load test for 3310 4806105 FW 3.25O enhancement to allow multiple simultaneous rebuilds 4807600 The stripe size on SSCS doesn't show actual information on LDs 4847479 sccli> show inquiry-data does not show correct Firmware Revision 4847938 sccli inquiry does not show the IP address 4865270 Battery status should not be affected by I/O 4866684 open tcp/ip ports 4881105 Ability to set Date, Time, and TZ through the External Interface 4881122 Cached blocks from a deleted logical drive are returned on READ 4881127 Duplicate logical drive IDs assigned on same controller 4881136 Periodic cache flushing feature with user-selectable flush interval 4881138 Write-back caching option with accelerated posting of writes 4881139 Logical drive expansion for RAID 1 logical drives 4888526 Temperature events should contain the sensor number 4889967 Time Stamp reported for an event log entry is not constant, it changes over time 4903457 Deassert Reset on Failed Controller (reinit failed ctrlr) loses access to disks 4907020 Request Sense couldn't get sense data on SE3310 when VEA rescan performed 4937092 The SCCLI/GUI does'nt allow us to set scsi-io-timeout > 10 4971693 controller reset request popup not happeneing when changing scsi timeout value 4972674 inability to rebuild RAID drive if online drive has bad blocks 4976389 Download of SAF-TE fw via SSCS interface says it succeeded even though it didn't 4988102 Port scanning/security software cause the SE3310 to hang 4995551 Serialnumbers in eventlog are inconsistent or missing 5007650 Controller offlines disk drive with an "Unexpected Sense Received" event 5007664 Controller may not corectly understand certain AENs sent out by the drives 5007911 Running sccli to busy minnows can cause SCSI transport messages 5014319 SCCLI> show fru is displaying inconstistant results with 3310 out-of-band. 5016154 SCCLI: oob connection failed with "network connection setup failed" 5022022 DRAM parity errors/SDRAM ECC errors can cause data corruption 5024472 Running both sccli and SSCS inband can hang V240 server 5026029 Firmware upgrade/downgrade shown as controller failure detected from sccli. 5026182 Firmware upgrade/downgrade displayes incorrect times stamp via sccli show events 5031134 single failed drive that affects the bus, can crash the controller 5049931 Connection to 'IP' closed by foreign host with 3.25W fw 5061519 Bus resets encountered when se3kxtr is run on SE3310 SCSI (Minnow) 5075581 show config -x returns inconsistant results (262 invalid events 30 days) 5082165 Drives that are exceeding the block allocation threshold are not taken offline by the controller 5084418 show shutdown-status output inaccurate for 3310 after shutdown controller cmd. 5094779 sccli SE3310 shutdown logical-drive gets controller access error and fails 5094897 ld rebuild only gets to 99% 6180281 vxa5kchk hangs with SE3310 RAID attached 6190524 Disconnected tagged cmd(s) and timeout on glm-attached storage after poweroff cluster node 6194894 Controller requires 2 resets after restoring defaults on 411 6199449 Minnow (3310/3510) RAID does not report correct LUN geometry via Mode Sense data 6199453 LEDs keep blinking after fw downloaded 6203390 lack of sccli oob functionality follows logical drives between chassis 6207987 256k read operation causes unrecoverable controller error 6232208 Firmware option defaults listed in SE3310 customer documentation are out-of-date 6233475 wrong package name in the book "Sun StorEdge 3000 Family 2.0 Software Installation Guide" 6246702 lower cache flush settings required for 3310 4.11 firmware 6246708 3310 Raid controller not responding to disk spin-up command 6251454 SE3310: inband reset also fails on SE3310 6253745 a drive with consecutive bad blocks should not bring down the whole array 6263359 Sun Cluster loses quorum and panics when one node rebooted The 113722-10 README file addresses: 6202496 Synopsis: Incorrect information in patch README (from 113722-09) SAF-TE firmware 1170 addresses the following issues: 4989784 addr IDs are not showing correctly on dual-bus config using sccli 6199412 live downloading SAF-TE package firmware, I/O time-outs could occur for normal data traffic 6199413 Configuration Sensing - Split Bus and SCSI ID values could be wrong 6199414 The temperature reading of a power supply is not valid when a supply is not installed 6199416 The IOM temperature readings were not being reported in the SAF-TE Status page 6214522 SE3310 SAFTE > 1159 generates false power supply and fan events when sccli commands are issued (from 113722-07) SAF-TE firmware 1167 addresses the following issues: 5005317 SE3310's Disk LED is not lit Amber 5014319 SCCLI> show fru is displaying inconsistent results with 3310 out-of-band. 5056104 Unexpected SCSI Reset on 3120 multi-initiator conf with X6758A 5056930 Warning messages in sccli operations with SE HBA(X1018A) 5075581 show config -x returns inconsistent results (262 invalid events 30 days) (from 113722-06) RAID firmware 325W addresses the following issues: 4929829 Format inquiry returns failed to SE3310 from Ultra320 LVD PCI HBA & Sun Fire V440 on-board 4969758 SE3310 uses wrong MAC address for ICMP echo reply under some circumstances 4986468 Giving up messages on SE3310 RAID array LUNs 4988102 Port scanning/security software cause the SE3310 to hang This README file addresses the following issue: 5036067 firmware patch should warn user not to remove FRU for 10 minutes. (from 113722-05) This file addresses the following issues: 4989809 Incorrect information and typo in README.113722-05 SAF-TE firmware 1159 addresses the following issues: 4865630 sccli hangs and causes I/O timeouts when 'show frus' is executed 4956272 PS LED does not change state above 40C 4975612 SAF-TE firmware upgrade results in gross phase signal errors. (from 113722-03) RAID firmware 325S addresses the following issues: 4889104 Logical drive initialization phase takes too long 4881109 Controller hangs upon encountering medium error for Raid 0 or NRAID 4881132 Disk status is incorrect when rebuilding after RAID 1 multiple drive failures 4876079 SE 3310 RAID Array syncs at 80 MBytes/sec on Ultra320 scsi ports 4847052 Silent Data Corruption when ATN line is cut 4842604 SE 3310 controller violates SCSI spec for "receive diagnostic" command 4810830 Spelling error in "view and edit Configuration parameters" menu (from 113722-02) RAID firmware 325Q addresses the following issues: 4826944 Copy and Replace function during rebuild causes data corruption 4809793 scsi incomplete retry errors when cache is optimized for Random I/O 4809787 After "defaults restore" fw asks for a controller unique id 4802207 SCSI Bus Reset and daemon.error under heavy load test for 3310 4792748 3310 incomplete read- retrying w VTS 4764506 Enabling secondary RS-232 port causes serial communication failure (from 113722-01) RAID firmware 325O addresses the following issues: 4717055 Running heavy I/O & scsi-resets to VxVM volumes on SE3310 LUNs may cause data loss 4723464 Diskomizer w/scsi resets on Minnow causes aio write/read errors and long boots Patch Installation Instructions: ========================== Invoking Sun StorEdge CLI: --------------------------- Version 2.3 or greater of the "sccli" CLI utility is required. It is included in the SUNWsscs package, which may be downloaded from the Sun Download Center or installed from the optional Sun StorEdge Professional Storage Manager CD. For software installation or upgrading instructions, refer to the "Sun StorEdge 3000 Family Software Installation Guide." Click the link for your array on the Sun Documentation Centers Storage web page at: sun.com/products-n-solutions/hardware/docs/Network_Storage_Solutions/ Select the most recent version of software and then download the Software Installation Guide. The firmware procedures require the user to invoke Sun StorEdge CLI (sccli) using the appropriate syntax for the type of connection used to manage the array. If the array to be upgraded is a standalone SCSI JBOD, invoke sccli with the name of an SAF-TE device: sccli /dev/es/ses If the array to be upgraded is a RAID subsystem attached to a SCSI HBA installed in the local host, type the sccli command with no arguments: sccli If more than one array is connected to local SCSI HBAs, sccli will display a list from which the appropriate device may be selected. If the array has an IP address configured, it may be managed remotely using a network (or "out-of-band") connection. To specify this mode, type: sccli [-w ] where is the password assigned to the controller, and is the hostname or IP address of the array. Use single quote characters to quote the password if it contains any characters that are interpreted specially by the shell. If no controller password is set, the -w option and password argument should be omitted. To verify the version of "sccli" you are running type the following command at the sccli> prompt: version ============================================ Upgrading Controller Firmware 4.xx to 4.15 -------------------------------------------- The following procedure is used for a minor revision upgrade, such as from 4.11 to 4.15. If you are currently running 3.xx firmware, skip to "Special Install Instructions" at the end of this README. ----- Note: ----- Be sure your working directory is the directory in which the patch was unpacked and confirm that the SUN415F-3310.bin file is present. 1. Verify the Product and Revision of the array. Type the following command at the sccli> prompt: show inquiry and examine the output. If the "Product" is "StorEdge 3310 D" and "Device Type: Enclosure" appears, the device is a JBOD chassis and has no controller firmware; skip to the "SAF-TE Firmware Upgrade" section. If the Product is not "StorEdge 3310," this patch does not apply. Select a different device or discontinue installation of this patch. If the firmware version reported is 415F, the RAID controller firmware does not need to be upgraded; skip to the "SAF-TE Firmware Upgrade" Otherwise, continue with step 2. 2. Verify single or dual controller. Type the following command at the sccli> prompt: show redundancy and examine the output. If the "array redundancy" mode is not "Active-Active" AND the "redundancy" status is not "Enabled," skip to step 4 and follow the instructions for upgrading a single-controller configuration or for non-redundant configurations. 3. ONLY if the "show redundancy" command reports that the Redundancy mode is "Active-Active" and that the status is "Enabled" (dual-controller), AND you are currently running 4.13B or later should you continue. ---- Note: ---- Entering the "download controller-firmware" command below will cause a controlled reset and failover of both controller modules. During this process host I/O can be temporarily affected and recoverable errors may be recorded. This may have an impact of IO performance during the upgrade procedure. Retryable I/O errors and bus resets can be visible on attached hosts. Perform the firmware upgrade by typing the following command at the sccli> prompt: download controller-firmware SUN415F-3310.bin The sccli command will display the following messages: sccli: Downloading controller firmware...programming flash memory...done sccli: Engaging firmware...done sccli> Wait until the sccli> prompt appears again, which may take 10 minutes or more, before proceeding. If you see an error message containing the text: "please repeat download command" or "controller firmware download ok, but engage operation is not allowed," the controller was unable to perform the firmware upgrade. Repeat the download as follows: Stop all I/O activity and unmount any filesystems or volumes mounted by a volume manager from the array. Then, type the following command at the sccli> prompt: download controller-firmware -r SUN415F-3310.bin When download completes, skip to step 5. 4. Single-controller or non-redundant configurations require a reset after downloading new firmware. This type of upgrade requires that the controller be reset, which in turn causes the controller to stop servicing I/O requests for several minutes. Stop all I/O activity and unmount any filesystems or volumes mounted by a volume manager from the array. Then, type the following command at the sccli> prompt: download controller-firmware -r SUN415F-3310.bin The sccli command will display the following messages: sccli: Downloading controller firmware...programming flash memory...done sccli: Resetting controller...done sccli> Wait until the sccli> prompt appears again, which may take 10 minutes or more, before proceeding. 5. Verify that the firmware upgrade succeeded by examining the firmware revision again. Type the following command at the sccli> prompt: show inquiry and verify that the firmware revision is now reported as 415F. 6. If no errors occurred, continue to "SAF-TE Firmware Upgrade." ======================== SAF-TE Firmware Upgrade: ------------------------ 1. Verify the SAF-TE firmware version. Type the following command at the sccli> prompt: show safte sccli> show safte Ch Id Chassis Vendor Product ID Rev Package --------------------------------------------------------- 0 14 000187 SUN StorEdge 3310 A 1159 1159 2 15 005632 SUN StorEdge 3310 D 1159 1159 Examine the SAF-TE firmware revision codes displayed in the "Rev" column and "Package" column. If all the lines contain a revision code of 1180 in the "Rev" field and "Package" field, no SAF-TE firmware update is necessary and you should skip to "After Upgrading." In the example above, the "Rev" field and "Package" field is 1159 for both devices and therefore an upgrade is needed. ----- Note: ----- Only one line of information may be displayed for a standalone expansion (JBOD) chassis, and more than two lines may be displayed if a RAID enclosure has expansion chassis connected to it. The Product ID field will be "StorEdge 3310 A" for SAF-TE devices internal to the RAID array chassis, and "StorEdge 3310 D" for SAF-TE devices internal to the expansion chassis. 2. Since the SSCS agent may interfere with the download of SAF-TE code, it is necessary to stop any SSCS agent that may be running on a host connected to the array controller. To stop the SSCS agent, issue the shell command as "root" user: /etc/init.d/ssagent stop If the SSCS agent is running on a Microsoft Windows system connected to the array, use the Services application (Start->Run->services.msc) to stop the SSCS Agent service. StorADE, or any other application that monitors the status of the enclosure, may also interfere with controller or SAF-TE firmware downloads. Stop the StorADE agent software, or any other software that monitors the array, following the procedures described in the documentation for that application. 4. Perform the upgrade. Type the following command at the sccli> prompt: download safte-firmware saftefw_3310_1180.bin ----- Note: ----- When upgrading SAF-TE firmware earlier than revision 1159, it is necessary to repeat the firmware download command twice, even if it looked as if the download operation succeeded the first time. This additional step is required because with 1159 firmware, a portion of the new firmware may not be loaded correctly, in which case the power supplies may not be able to report their status correctly. Enter the same command again at the sccli> prompt: download safte-firmware saftefw_3310_1180.bin It is not necessary to reset the RAID controller afterwards; however, until the next controller reset, the firmware's menu interface may continue to display the old SAF-TE firmware revision. 5. Verify that all SAF-TE devices have been upgraded. Type the following command at the sccli> prompt: show safte sccli> show safte Ch Id Chassis Vendor Product ID Rev Package --------------------------------------------------------- 0 14 012345 SUN StorEdge 3310 A 1180 1180 2 15 005632 SUN StorEdge 3310 D 1180 1180 The lines should now contain a revision of 1180 as indicated by the "Rev" column and the "Package" column. ================ After Upgrading: ---------------- 1. If the SSCS agent was stopped, restart it with the command "/etc/init.d/ssagent start" if it is installed on Solaris, or using the Services utility (Start->Run->"services.msc") if it is installed on Microsoft Windows. 2. If other storage management software such as StorADE was stopped, restart it following the procedures in the documentation for that software. ============================= Special Install Instructions: ----------------------------- These README instructions require that RAID controller 4.1x firmware already be present on any arrays being upgraded. If your array currently has version 3.2x controller firmware installed, do NOT attempt to use the instructions in this README to upgrade from version 3.2x to version 4.15. Instead, follow the detailed instructions in the Sun StorEdge 3000 Family RAID Controller Firmware Migration Guide. This document is part of the Sun StorEdge 3000 Family documentation set and can be downloaded by following the links from Sun Product Documentation's Workgroup Storage web page: http://www.sun.com/products-n- solutions/hardware/docs/Network_Storage_Solutions/Workgroup/ README -- Last modified date: Tuesday, June 13, 2006