Patch-ID# 116930-03 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: t3 t300 t310 raid storage firmware loopcard eprom interconnect Synopsis: T3B 3.2.2: System Firmware Update Date: Sep/02/2005 Install Requirements: Additional instructions may be listed below Solaris Release: 2.6 7 8 9 SunOS Release: 5.6 5.7 5.8 5.9 Unbundled Product: T3+ Firmware Unbundled Release: 3.2.2 Xref: Topic: Relevant Architectures: sparc NOTE: This patch release is for the T3B Array only and not the T3 Array. If you have a T3 Array, and are looking to update with the latest patch release, please download patch 109115-17 (or later). The Sun StorEdge T3B disk tray was formerly known as the Sun StorEdge T300 prior to final product shipment. Most of the Sun StorEdge T3B disk tray user documentation has been updated to reflect the new name; however, there are some related software components (such as the Sun StorTools diagnostic package) that still reference this product as the Sun StorEdge T300. Users should be aware that both the Sun StorEdge T3B and Sun StorEdge T300 names refer to the same product and are equivalent in terms of product features and functionality. BugId's fixed with this patch: 6293611 Changes incorporated in this version: 6293611 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.116930-03 # README file for this package disk # All supported disk drive firmwares disk/CHANGELISTS # T3 disk drive firmware release note docs # Released documents with the patch lpc_05.02 # Unit Interconnect Card Firmware patchtoc # t3.sh: Files to Upload To Target T3B previous # Recent previous release patch t3.sh # t3.sh File Upload Utility t3l3_322.bin # Controller firmware level 3 files.tar # T3B System Files Tar Image Problem Description: --------------------------------------------------- (3.2.2 Firmware) --------------------------------------------------- 6293611 system area wipe on T3 and T4 corrupts user data --------------------------------------------------- (3.2.1 Firmware) --------------------------------------------------- 6284924 T3B/T4 should unmount volumes if it finds incompatible drive f/w for Seagate drives 6273852 array-firmwa/array_config data integrity issue after sysipe and rebuild of array 6276050 after drive replacement, unable to read sysarea on newly replaced drive --------------------------------------------------- (3.2.0 Firmware) --------------------------------------------------- 6263822 6120 320_38: data corruption on write, Seagate 300GB disks, currently using 6120 2x6 6213633 6120: Illegal request during recon. 6213640 6120: drv disable by the WXFT task due to write error 6219705 T3B: u1(master) hangs when u2 is diag.master and got disabled 6192321 new vol blockscan command - no indication if working 6220160 StartPortTasks() should not be called before TDMasterInit()/TDSlaveInit() 6213636 6120: u1 assertion - srq_task.c line 2333 6209353 6120/3.2.0.33: multiple drvs receive error "not in an on-line state" during vol mount operation 5091791 T4/T3: "Failed reading system area"disk replacement should get sysarea from others 6211597 Synopsis: 6120/3.2.0.44: cache/mirror do not change to writebehind/on in auto setting 6206096 6120: Befit did not detect a loop_unstable fault as expected 6209073 6120/T3B: drives got bypassed unexpectedly when u4 running loop_unstable and u4 got disabled(.probe) 6204637 T3B: loop card cable missing TX+ signal caused svd.c line 8858 assert 5092808 6120/T3b: lpc reboot causes multiple drive disables and vol unmount 6185440 The Refresh section of T4 firmware is defective when a power supply fails 5107142 T3B 320_27: s55 script, vol mount leads to svh.c line 522 [ip=d272c fp=2202cc4] 6207202 6120: Loop unstable detected as critical and IO bails out when lips ejected on u1 and u4 6201943 Qlogic ISP23xx firmware patch regarding Brocade frame leaking problem 5101526 6120: cache mirror are not turned on when they are set to auto 6195283 6120/T3B: system hangs after Master probe during AltMaster boot 6198737 Key changes needed to make event tracing useful for ENABLE_LOGMASK builds 5083284 6120:xf_lock.c line 583 Assert(lockP->stripe_id != FREE_LOCK) during lpc reboot 6195589 T3B/3.2.0.31: got xf_cmdset.c line 201, Assert(0) after BEFIT is complete 6189595 roll back ISP23xx fw to 3.02.202 for 10 percent performance drop during read cache 6181645 6120: CPU data access exception during vol creation 6181429 6120: u2 takes more than 10min to come up on 2x2 6190151 6120/T3B: Drive download should not be allowed if BEFIT is executing 6188807 6120/T3B BEFIT: Alt. Master can assert if booting during BEFIT 6191210 6120/3.2.0.29: RAS incompatible with non adjacent drv disable testing in RAID 1 5108727 Master controller fails to boot up if Loopcard A is disabled 6183104 6120: AltMaster takes 3 minutes longer than Master to reach Login 5108400 T3B: All drive LEDs of a volume turn amber after disk download is done 6183831 Reconstruction failure for RAID-5 volume 6184766 T3B: Master cntlr hangs when Slave is asserted while running LOOP_UNSTABLE BEFIT 6185440 The Refresh section of T4 firmware is defective when a power supply fails 6183331 6120:BEFIT does not find fault after cntlr take over 5090755 6120/T3B:IO's to array completely die after BEFIT completes IC2 cable fault isol 5105016 6120/T3b: "lpc reboot" can cause loopcard "fault" in fru stat 5099889 6120: Performance degradation in 3.2.0.21 after comparing to 3.1.4.11. 6174458 6120: BEFIT should detect hard faults that are not loss of sync 6180960 6120/T3B: Disallow lpc reboot, enable, disable during BEFIT diagnostics 4852303 T4: Data miscompare - 'at word 0x0, 56 should be 50' 5110149 6120/T3B:systems crash when injecting loop_critical fault + disable controller 5101204 disable u1d6 drive LED turns blue and back to green in 3 seconds 5054810 6120/3.2.0.14: .mcdk disable a drive got bunch Bus Reset message. 5103836 ofdg find u2l2 caused all u1 drives faulty and disabled 5099930 T3B: fru stat shows disabled loopcard u1l1 as master role Support upgrading disk FW from "no VPD page 0x83" to "VPD page 0x83 supported" (See related bug 5077820) 5107102 CPU trap exception after disable 4 drives and boot -r 5086310 Add CLIs to scan block 5093564 T3B:Disk download on one drive results in AMBER LED to be lit on adjacent drive 5107081 6120:BEFIT isolates incorrect FRU as faulty during intermittent fault detection 4970782 6120/T3B:disk fw download fails when FI(BEFIT)is triggered on same drive 5056021 Qlogic fw workaround for Brocade 3900 frame leaking problem 5104486 6120: os_util.c line 869, q_urgent(qid, msgP) => 52 != 0 5034830 Lun permissions improperly set when "lun default > 5105166 6120/T3B: BEFIT triggers back to back for loopcard/IC faults. 5081617 Disk scrubber aborts verification when it encounters multiple errors 5101168 Tuning on Locator LED on u1, turns off attention LED 5088163 sys list displays fc_speed as 2Gb after "sys fc_speed 1 force". 5043559 6120/T3B: IO's fail during controller failover (.probe/enable) test. 5079795 6120: Syslog lost some messages from msgbuff 5093167 No way to restore optimal drive paths in typical customer configuration 5093172 .disk pathstat can unexpectedly fail under certain enc/drive conditions 5090122 6120/T3B: "reset -y" hang when u2l1 is disabled 5083526 6120/T3B: Incorrect Errors/Warnings during bootup 5090981 6120/3.2.0_23: vol stat does not reflect medium err during .vol init parallel 5085907 fault injection + raid 1 + a drv disable, no of IO errors are not consistent 5089611 6120:".seg" CLI doesn't accept hex number as segment size. 5091389 Enable visibility/control over controller/backend ports bypass circuitry 5077444 6120:sometimes drv is disabled during vol add due to system area verify failure 5088054 Fix external host port driver simulation support 5082270 6120:Enabling befit after fault was injected when ondg=off will not triggerBEFIT 5082914 T3B: With loopcard disabled during boot, befit should not trigger 5082903 6120: Drives are not disabled after Befit bypassed both ports 5083849 On system boot, ISP shoud not be unbypassed if LPC is disabled 5082757 6120: 306, CPU data access exception causing data MISMATCH on VXVM mirror vol 5077900 6120/T3B:Drive is not being disabled afer BEFIT isolates fault & recon completes 5086748 3.2 : 6120/T3B : disk firmware download should use encid/slot instead of lid for 5052930 3.2 disk format cmd does not print status when it is complete 5082361 disk download command in T3/T4 must be able download large drive firmware files 5081536 6120/Maserati Volume creation problem with 300GB Drives. 5079839 6120: Using EIM code + 4k blocksize, u2 does not come up after a shutdown 5080922 6120/T3B Message from Polling code (u1l1 is faulty) shouldn't be Error level 5086802 6120:lpc reboot results in IO hang 5083849 On system boot, ISP shoud not be unbypassed if LPC is disabled 5082757 6120: 306, CPU data access exception causing data MISMATCH on VXVM mirror vol 5077900 6120/T3B:Drive is not being disabled afer BEFIT isolates fault & recon completes 5086748 3.2 : 6120/T3B : disk firmware download should use encid/slot instead of lid for 5052930 3.2 disk format cmd does not print status when it is complete 5082361 disk download command in T3/T4 must be able download large drive firmware files 5081536 6120/Maserati Volume creation problem with 300GB Drives. 5080922 6120/T3B Message from Polling code (u1l1 is faulty) shouldn't be Error level 5086802 6120:lpc reboot results in IO hang 5060086 3.2 6120/T3B:Multiple drives disabled when cntrl is killed during BEFIT diagnost 4999218 volCacheWriteHits SNMP token no longer increments 5062791 6120 3.2: Master stops responding after several drive downloads. 5073888 6120/T3B:ctr stays in booting state after being re-enabled 5073617 6120:AMBER LED is turned ON on random drives when loopcard is unplugged/disabled 4972246 6120/T3b: loopcard disable causes loop to go down 5014354 6120: Ability to inject serial faults onto loopcard 5018107 Modify loopcard messages 4941159 6120:Enabling a disabled cntrl takes 25min,stuck at"loop 1 TARGET_ID"phase 15min 5047828 T3B: Pull out u2l1 while system is booting causes u2 take long to boot up 5077795 Amber led should stay on once the copy recon is finished for "write-fault" drive 5077973 6120: wrong volume aborted during disk download with drive offline. 5070583 6120/3.2-IO's to array is hung when BEFIT completes fault isloation. 5079961 6120/T3B: BEFIT triggers if ISP is bypassed and reset 5080299 T3B: Befit messaging issues 5079228 6120:BEFIT sometimes does not trigger/isolate correctly when ICfault is injected 5062138 6120 3.2: Recon to standby was abruptly abort when standby has 3/11/00 error but 5060131 Fine-tune error messages 5072948 With a disk verify process running, re-enable of failed controller is delay 5060671 6120: Online Disk Download Raid 5 degraded does sequential load not parallel 5060667 3.2 Online Disk f/w Download Raid 0 is done sequentially not parallel 5074838 Need easy way to determine ALPA, LOOP I/D, and LID info for a drive 5066873 6120:3.1.5/3.2 the date/time on the alternate mater is 8 hrs behind master date 5069641 RTEC compiler code generation may omit some global data items 5072023 6120: 320_19 qlcf CPU data access exception 5075084 6120: recon shouldn't fail when encounter second medium error 5069831 6120/320_18: SVD allows IOs to retry even when drive failover is in progress 5063703 6120/3.2: Hotplug of multiple drives causes BEFIT to trigger. 5066883 6120:3.2 RAS befit is triggering and bypassing drives which may not be bad 5060575 fru statistic does not report anything in trays w/o ctlr or disabled ctlr 5064857 enable full support for RTEC-enabled binaries 4990583 T3B: Error msg seen during boot up (Assigning Select IDs:...) 5062128 6120: 3.2 -> 3.1.5 can cause data access exception 5064484 Update 6120/ISP2310cs7 isp firmware to latest cs7 main branch 5060008 3.2: When using EIM mode page, drive gets disabled with a write failure 5043589 lid 7f failed attached" occurs after every LIP on back-end loops 5052394 Multiple Disk Fault Tolerance, Phases 2 and 3 5055994 Multiple Disk Fault Tolerance phase 1 4462567 Need error msg if ondg=passive prevents ofdg from launching 4486685 OFDG activity is not logged to host 4486687 OFDG syslog messages too cryptic for user to decode 4794710 ofdg: Results inconsistent plus some clean up required 4892271 120/T4: U1 get asertion cfg_util.c line 1761 while running ofdg check 5064223 Update 6120/T3B ISP2200 firmware to latest main branch 5053687 Add CLI to access opaque segment 5040361 Dummy drives not write bypassed on bootup 5052930 3.2 disk format cmd does not print status when it is complete 5049373 SVD SCSI error handling calls printf from interrupt context 5017094 Modify mesages in controller events 5045045 RFE for online disk firmware download project. 4903038 6120:3.1.13-u1 stuck in "Waiting for configuration data from master" during boot 5044756 Final tuning of error messages after "rcp" and ".logger" is available 5045371 incomplete firmware token blocks testing 6020 revision maint backout session 5037877 Confusing messages in Disk verify code 5007948 tXadb macro file comments support and other misc enhancements 5009746 Parallel drive spin up 5013570 SVD should not log messages at ERR/WARN/NOTICE level 5015148 One drive in a 6320 may cause a multiple drive failure in a tray 4952406 6120 310_27: s03, RAS triggered and disabled u1l1, need to root cause problem 5013833 Delete "Failed" message in HbtDisableDk(). Add new meaningful message instead 5024905 Modify to fix misleading reconstruct and vol verify messages 5031819 T3B,6120: "fru list" doesn't track the info when drives are swapped 5022932 Provide Storage Stack Terminology in ( ) next to incompliant term in syslog 5014707 Modify mirroring messages 5013975 Adjust message level for QLCF driver 5015453 Modify PCU/Battery messages 5030275 DiskPerf token statistics are incomplete in 2xN configurations 5022379 Latent Fault Detection of Non-Volume Disks 5014510 component missing from log message for battery failed stat 5019947 Log debug information in a separate file on RAM disk 5013579 Transfer code logs messages per I/O, in interrupt context, in the case of I/O er 5033020 6120/T3B: Need to display current function call history in the stack --------------------------------------------------- (3.1.6 Firmware) --------------------------------------------------- 5107602 6320: GUI remove multiple volumes caused array master-ctrl coredump, offline 6180857 Cannot recover lost password on T3+ running 3.x FW --------------------------------------------------- (3.1.5 Firmware) --------------------------------------------------- 5047217 6120:Unplugging one loopcard in 2x6 turns on amber LED on other loopcards 5038486 T3B/3.1.4.11: data miscompare - 128 words in error 4992011 OFDG/ONDG u2 health checks on back-end loops always fail 5033787 6120 "boot -r" may cause Assert 5035207 6120/3.1.3.10: error on read block 100 for 16 - lun failover takes too much time 5046359 6120: All enclosure's drive LED turn amber when any loopcard is disabled 5043978 s07 failed due to multiple drives "broken" after enable u4l2 5044894 shelf life check should not be done on T3 5053308 6120/3.2.0.12: Array asserts during reset, after disk format cmd was issued to u 5043884 6120: lpc firmware download causes array reboot 5059651 commands can get stuck in svd layer for quite sometime. 4978663 .disk linkstat works only for a drive in a tray with an enabled RAID controller 5033152 T3B/3.1.3.10: when drive is fault/disabled, amber led is not on. 5043408 T3B: original IP is not preserved during the 1.18 to 3.1.4 upgrade 5037853 6120 failover failed to complete 5009611 seg command to allow Ops to read/write segments 4964912 6120:both controllers of 2x4 or 2x2 system become master 4984663 set flags 0x80000000 command sets incorrect flags value 4997002 assert failure in svh_accept_scsi_cmd() 4986534 6120 syslog get's flooded when a raid5 disk resyncs 5018930 6120: 1st lun permission gets overwritten if permission limit is exceeded 4974618 T3B/313_2: syslog data prints to console instead of log file 5021108 6120 panic in runScheduler implicating time(..) routine 5006522 RAMDISK file system support 4935307 6120:2x6--disable u4 during vol init parallel, after completion, init restarts 4993287 Adjust NOTICE messages to INFO messages 5004498 Separate loglevel 4 (INFO) from DEBUG 4981571 T3B: vol verify logs failure when terminated by running another vol command 4998395 Change some LOG_NOTICE debug messages to LOG_INFO 4965335 T3B 3.1.1 No battery warnings logged in when date is set beyond expiration 4944443 T3B: token for fruLoopVersion does not match lpc version 4936086 6120/T3: PGR IN read keys CDB response has incorrect additional length data. 5005538 savecore altmaster live dump fails if any drive is disabled on u1 4989760 T3B--313.7 & 2.1.6 ctlr stuck at "POST Failed. Hit c to continue" while booting 4991427 Change some LOG_INFO messages to LOG_DEBUG 4998390 T3B/6120: svd should heal loop A during failover. 4965873 6120: Command 'unconfig ud[1-14]' turns AMBER led on wrong drive ON. 4989074 Enhance crashdump message buffer 4252684 Reconstruction rate does not change dynamically. 4946781 6120/T3B: pcu's with failed batteries do not show amber LEDs ------------------------------- PATCH PRE-INSTALL INSTRUCTIONS: ------------------------------- 1) ftp the 'syslog' or the file to which the system log is directed from required T3B on which patch 116930-03 is planned to be installed. 2) Keep this 'syslog' file in a local directory on host system and run following command. egrep -i '0x5D|Threshold|0x15|0x4|Mechanical|Positioning|Exceeded|Disk Error' syslog If you see any of following error messages then take appropriate action of backing up of data from the volume, replace the drive reporting any of these errors, ensure the volume is in optimal working state without any drives disabled and then Install the patch. An Example: Here 'u2d5' and 'u1d3' shows the location of drives. test_host% egrep -i '0x5D|Threshold|0x15|0x4|Mechanical|Positioning|Exceeded|Disk Error' syslog Jun 05 06:16:14 ISR1[2]: W: u2d5 SCSI Disk Error Occurred (path = 0x0) Jun 05 06:16:14 ISR1[2]: W: Sense Key = 0x4, Asc = 0x15, Ascq = 0x1 Jun 05 06:16:14 ISR1[2]: W: Sense Data Description = Mechanical Positioning Error Jul 31 16:19:22 ISR1[1]: N: u1d3 SCSI Disk Error Occurred (path = 0x1) Jul 31 16:19:22 ISR1[1]: N: Sense Key = 0x1, Asc = 0x5d, Ascq = 0x0 Jul 31 16:19:22 ISR1[1]: N: Sense Data Description = Failure Prediction Threshold Exceeded -------------------------------- Patch Installation Instructions: -------------------------------- This patch includes a firmware uploading utility (t3.sh) that simplifies transferring the contents of this patch to a StorEdge T3B system. This script is intended for use on Solaris host systems only. To manually install the contents of this patch see the pertinent section below. *** Warning *** Warning *** Warning *** Warning *** Warning *** BEFORE attempting to load firmware on a StorEdge T3B system, be sure to stop all IO activity from all attached host systems. This procedure requires a T3B system reboot so all necessary host preparations needed to sustain this procedure should be made before starting. It is recommended all T3B volumes be unmounted on Solaris before proceeding with this patch installation. *** Warning *** Warning *** Warning *** Warning *** Warning *** *** IF YOU HAVE MAP3735FC DRIVES INSTALLED READ THE FOLLOWING*** Please read the contents of SunAlert 57620 before continuing with any disk download of any MAP3735FC drive firmware. If this is a new system with MAP3735FC "1201" drive firmware and the system is working fine (volumes mounted after reset OK) then ignore SunAlert 57620. This issue is only exhibited after a manual disk firmware upgrade and the first subsequent reset. If the MAP3735FC drive firmware has been manually upgraded to "1201" and volumes have already been recovered after a subsequent reset then ignore SunAlert 57620. This problem is only exhibited after a manual disk firmware upgrade and the first subsequent reset. This issue will not exhibit itself after the volumes have been recovered. DO NOT ATTEMPT TO DOWNGRADE DISK FIRMWARE to "0801". You can stay at "1201" until T3B FW fix is released in the future. Note: To verify the current firmware version running on a target T3B system, use the 'ver' command at the T3B command line as follows: t3:/:<3>ver T3B Release 3.1.0 Wed Apr 9 22:21:44 PDT 2003 (10.4.32.153) Copyright (C) 1997-2003 Sun Microsystems, Inc. All Rights Reserved. To update the T3B system with the entire contents of this patch follow the steps below after quiescing IOs from the host: 1. System Preparation Once the patch has been downloaded to a Solaris host, extract (if necessary) the contents of the patch to a temporary working directory. 2. Verify the T3B system to be upgraded is reachable on the network: $ ping t3b t3b is alive 3. Verify the T3B system has a root password (the 't3.sh' patch utility uses ftp to transfer the files to the T3B which requires a root password): $ telnet t3b Trying 129.150.47.115... Connected to t3b. Escape character is '^]'. Unauthorized access is prohibited. Login: root Password: <---- Must type password here T3B Release 3.1.0 Wed Apr 9 22:21:44 PDT 2003 (10.4.32.153) Copyright (C) 1997-2003 Sun Microsystems, Inc. All Rights Reserved. t3b:/:<1> If no root password is set on the system, be sure to set one by logging into the T3B system and using the 'passwd' command. 4. Transfer patch contents to T3B system. Note: There is limited space available in the T3B's filesystem area. Therefore, it is important to be sure there is adequate space on the T3B before proceeding with the procedure to ftp firmware images to the unit. It is not necessary to keep old images of controller firmware, unit interconnect card firmware, or eprom binaries on the T3B once those images have been loaded per the instructions provided in this readme. "df" CLI could be used to determine space on the T3B The recommended way to install the contents of this patch on T3B systems is to use the included t3.sh script from a Solaris host that has network access to the target T3B system being upgraded. This utility will transfer the required files in this patch to the target system depositing the files in the correct directories. If a Solaris host isn't available, the contents of this patch can be manually uploaded to the target T3B system using the following method. Note: It is not necessary to transfer all files contained in this patch to a target T3B system. For example, the docs subdirectory in the patch provides reference documentation and is not required by a T3B system. Manual File Installation ------------------------ -> Extract the contents of the 'files.tar' image to a temporary working directory: -> Manually ftp the following files contained in this patch to the corresponding directory on the T3B system: Patch Source Location T3B Destination ------------------------- ------------------------ ./lpc_05.02 /lpc_05.02 ./t3l3_322.bin /t3l3_322.bin (From temporary Working Directory) ./etc/bat.conf /etc/bat.conf ./web/*.htm /web ./web/snmp/t300.mib /web/snmp/t300.mib ./etc/zoneinfo /etc/zoneinfo Automated File Installation --------------------------- Note: The 't3.sh' installs all controller and system files but does not overwrite /etc/hosts and /etc/syslog.conf files on the target T3B system as these files are typically customized per local operating environment requirements. One exception to this is the battery refresh scheduler file on the T3B (/etc/bat.conf). The t3.sh script will make a backup copy of this file on the T3B (to /etc/bat_old.conf) before copying over the new /etc/bat.conf file. Factory default versions of these files do exist in the accompanying files.tar image in this patch should they be required however. To start the installation script, first verify the target T3B system can be reached through the local network (use ping to verify the target T3B system is reachable). Once this has been confirmed, the installation script can be started as follows: ./t3.sh (Note: Be sure the t3.sh script is executable.) The t3.sh utility will prompt for information as follows: Please Enter Hostname or IP Address Of T3B To Be Ugpraded: -> Enter Hostname or IP address of the target T3B system. Please Enter Patch Location Pathname [.]: -> Enter path to where the files.tar image exists. Typically the default current working directory is sufficient (hitting enter will accept the current working directory). Please Enter Your Home Directory Path [/home/joe_user]: -> The home directory of the user ID used when launching the t3.sh script (this is used by ftp to automatically load the patch file contents to the T3B). At this point, the automatic ftp login/upload process should begin. The user will be prompted with a ftp login prompt at which point the user should respond using the default T3B root login and password. 5. Boot the T3B controller boot code. From the T3B command line, type the following to install the level 2 and 3 firmware code: :/:<7>ep download t3l3_322.bin (Caution: be sure all IOs have been quiesced and no host IO activity is scheduled to start until the upgrade procedure has completed) 6. Verify system boot mode set to auto: From the T3B command line, type the following: :/:<9>set bootmode auto 7. Reset the T3B System as follows: :/:<10>reset Reset the system, are you sure? [N]: y 8. Once the system has booted successfully, log into the system and verify the boot code is properly loaded using the 'ver' command as outlined earlier. 9. Load new Unit Interconnect Card Firmware: Using 'lpc version' on the T3B, if the loop card firmware is running downrev firmware, upgrade all loop cards in the partner group as follows from the T3B command line: :/:<1>lpc version LOOP A LOOP B Enclosure 1 5.01 5.01 Enclosure 2 5.01 5.01 :/:<2>lpc download u1l1 lpc_05.02 Repeat the above steps for all units in the partner group (ie u2l1 and u2l2). :/:<3>lpc download u1l2 lpc_05.02 :/:<4>lpc download u2l1 lpc_05.02 :/:<5>lpc download u2l2 lpc_05.02 Note: It is possible to string T3B commands together using the semicolon command. This allows a single command line session to launch several commands without waiting for each command to complete. To upgrade both loop cards one controller for example, one could type the following: :/:<2>lpc download u1l1 lpc_05.02; lpc download u1l2 lpc_05.02 Reboot the loopcards for the upgrade to take effect: :/:<6>lpc reboot u1l1 Repeat the above for the other loopcards From the command line, verify the correct unit interconnect card versions are loaded as follows: :/:<6>lpc version LOOP A LOOP B Enclosure 1 5.02 5.02 Enclosure 2 5.02 5.02 10. type "port list" and verify ports :/:<1>port list port targetid addr_type status host wwn u1p1 1 hard online sun 20030020f204462e u2p1 2 hard online sun 20030020f2044627 11. Verify volumes are visible and mounted. From the command line, enter the following: :/:<2>vol list volume capacity raid data standby v0 71.6 GB 1 u1d1-8 u1d9 12. Setting Time Zone: From the command line, enter the following: :/:<3>set timezone UTC 13. Congratulations, the upgraded T3B is ready to use again. --------------------------------------- DISK FIRMWARE UPGRADE INSTRUCTIONS: --------------------------------------- Note: o A disk drive firmware upgrade may not be necessary. To verify that the most up to date drive firmware versions are installed, run the 'fru list' command on the StorEdge T3B system and compare the results of that output with the latest information found in SunSolve. A set of disk firmwares are included here in this patch (see the disk subdirectory of this patch). o It is recommended that customers back up their data before performing the disk firmware download procedure. o During a disk drive firmware download, the availability of the disk tray is limited. To avoid system problems verify: o A current backup copy of the data on the T3B exists. o The data path between the T3B and the host has been quiesced. There must not be any IO activity during the disk drive firmware download. o The Ethernet connection to the T3B is not being used for any other operation during this procedure. If StorADE, Component Manager or any other application is monitoring the T3B, automatic polling MUST be disabled. Please refer to the StorADE or the Component Manager Users Guide for instructions on how to disable T3B automatic polling. (For useful tip, see Appendix A). o No unnecessary command line program interaction with the T3B system is performed during disk drive firmware downloads. o The disk firmware download will take approximately 20 mins for 9 drives. Do not attempt to interrupt the download or perform other command line functions during the process. The command prompt will return after the download process has completed. o During disk firmware downloads, T3B systems may report following error messages in syslog. This typically happens because of a drive inability to complete a request during the firmware download or the disk may be resetting. These messages do not affect the functionality of the T3B system and may be ignored. An example of messages seen in syslog is: Apr 22 13:43:16 t3b1 ISR1[1]: W: u2d5 SVD_PATH_FAILOVER: path_id = 0 Apr 22 13:37:52 t3b2 ISR1[1]: W: u2d7 SVD_PATH_FAILOVER: path_id = 1 Apr 22 13:38:10 t3b2 ISR1[1]: N: u2d7 SVD_RETRY: Retries Exhausted (ccb = 0x165b044) Apr 22 13:38:10 t3b2 ISR1[1]: N: u2d7 SVD_DONE: Command Error = 0x4 Apr 22 13:38:10 t3b2 ISR1[1]: N: Error - Unit Not Ready (path = 0x1, port = 0x16, lun = 0x0) o If an error is reported in syslog in response to a disk firmware download like the following message, Apr 22 13:38:40 t3b2 sh02[1]: N: u2d7 disk firmware download failed, err=1 Check 'fru stat' and 'fru list', and if the reported drive shows the old firmware version, then retry the firmware download procedure on that drive. If the 'fru stat' shows the state of the failing disk to be 'fault', and both ports are 'bypass' for that disk, the customer data on that disk could be lost. If the volume that contains the failed disk is a RAID 0 volume, or if there are more than one disks failing on that RAID 1 or RAID 5 volume, customer will need to recover the volume. To recover the volume, first try to power cycle the enclosure, o then check 'fru stat' and 'fru list' to see if the failed disk is back online. If the disk state shows 'ready', mount the volume. If everything is successful, the recovery is done. o if the power cycling fails to bring back the disk and the volume, the customer needs to remove the volume, power cycle the enclosure, recreate the volume (LUNs), re-initialize the volume, mount the volume and recover the data from backup. Disk Firmware Upgrade Steps --------------------------- 1. Using ftp, transfer the appropriate disk drive firmware to the T3B root directory from the disk/ subdirectory contained in this patch. Be sure the file is transferred in binary mode. Note: The T3B system limits the filename length of files being transferred to the local disks. Be sure the file name is 12 characters or less in size and that the file name starts with an alphabetic character (not a numeric). It is recommended the file names provided in the disk/ subdirectory not be changed. 2. Establish a telnet connection with the T3B (see T3B product documentation for specific details if necessary). Log into the system as 'root'. 3. Verify all T3B disks are in an optimal state as follows: -> Confirm all disks are ready and enabled using the T3B 'fru stat' command. -> Confirm all disks configured into volumes are in an optimal state using the 'vol stat' command. All drives should report a drive state of zero. If there are drive issues reported, correct these problems before proceeding with the disk drive firmware download procedure. 4. Verify no volume operations are in progress using the 'proc list' command. If a volume operation is in progress, this operation must be allowed to complete before proceeding. 5. Verify no battery refresh operations are in progress using the 'refresh -s' command. If a battery refresh is in progress, it is recommended the refresh operation be allowed to complete before proceeding with disk drive firmware downloads. 6. Unmount T3B volumes To ensure no host IOs are active, unmount all T3B volumes from the host system. In addition, it is recommended the internal T3B volumes be unmounted as follows (using volume v0 as an example) :/:<1>vol unmount v0 7. Install the drive firmware using the T3B 'disk download' command as follows (this example assumes a download is being performed on drives on a master tray. Substitute FILENAME with the file name of the actual disk drive firmware image ftp'd to the tray in step 1): :/:<2>disk download u1d1-9 FILENAME Note: -> In a partner group, the disk download command can only specify one set of 9 drives at a time. -> All drive types specified on the command line *must* be of the same drive type. If individual drives require different firmware versions, multiple invocations of the 'disk download' command must be used to download firmware. -> If the wrong firmware type is specified for a given drive, the disk drive will reject the erroneous file download request and revert back to the disk firmware that was running at the time of the download request. -> It is possible to invoke multiple calls to the download utility by separating the commands with a semicolon as in the following example: disk download u1d1-9 FILENAME; disk download u2d1-9 FILENAME 8. Verify the drive firmware download was successful using the T3B command 'fru list'. 9. Reboot the Sun StorEdge T3B array after all drives have been upgraded. The T3B system can be rebooted using the T3B 'reset' command. Note: In some cases after a drive firmware download, older firmware version strings may still display in the 'fru list' command. A reset of the T3B after the download ensures the version information is updated correctly in internal T3B tables. 10. Once the tray has come back online, log into the array and verify optimal FRU states by doing the following: -> Confirm all disks are ready and enabled using the T3B 'fru stat' command. -> Confirm all disks correctly report model number and new firmware version information correctly using the T3B 'fru list' command. -> Confirm all disks configured into volumes are in an optimal state using the 'vol stat' command. All drives configured in volumes should report a drive state of zero. 11. Remount the unmounted volumes using the T3B 'vol mount' command. In addition, on all attached host systems, remount any T3B volumes that were unmounted in step 6. --------------- Appendix A --------------- The following section describes useful tips. ---------------------------------------------------------------- 1. How to start and stop automatic device monitoring under StorADE. ---------------------------------------------------------------- Using the 'ras_admin' command, one can stop and start the StorADE cron job that monitors all devices. The command syntax for stop the Storage Automated Diagnostic Environment agents: /opt/SUNWstade/bin/ras_admin agent -p The command syntax for start the Storage Automated Diagnostic Environment agents: /opt/SUNWstade/bin/ras_admin agent -s Also, using the 'ras_admin' command, one can view the polling activity status of each devices defined in StorADE. The command syntax is: /opt/SUNWstade/bin/ras_admin device_list The output of this command contains a column labeled 'Active', with 'Y' denoting active monitoring and 'N' for in-active monitoring. For more details about StorADE, please refer to the StorADE User's Guide documentation. ------------------------------------------- Special Install Instructions: ------------------------------------------- If you plan to run several automated file installation scripts (t3.sh) the same time on one host to update many T3B systems, you must enter different "Home Directory Path" since t3.sh script will use $HOME/.netrc for ftp. Please make sure that you have full permission in those directories. Seagate Disk Drives Seagate Technology disk drive models ST373207FSUN72G, ST314670FSUN146G, and ST330000FSUN300G running firmware earlier than version 05xx may interact with the Sun StorEdge T3+ array controller and array controller firmware 3.2.x. This interaction could lead to data integrity issue on the disk drive. The new Seagate A55A firmware corrects the issue. Sun StorEdge T3+ array controller firmware version 3.2.1 has been modified to detect the specific disk drive firmware revisions of the ST373207FSUN72G disk drive which has been the issue. On systems with these Seagate disk drives, and the affected drive firmware levels, the system will not allow the volumes to be mounted until the drive firmware level is updated to drive firmware version A5xx. If your system has ST373207FSUN72G disk drives, please upgrade them with drive firmware version A55A (included in this release) prior to installing 3.2.x array controller firmware. If you should install array controller firmware 3.2.x without the Seagate disk drive firmware A55A, you system will not allow the volumes to be mounted. To remedy this situation, install the Seagate disk drives firmware A55A and reboot the Sun StorEdge T3+ array controller. README -- Last modified date: Wednesday, November 30, 2005