Patch-ID# 116931-21

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: 6120 raid storage firmware loopcard eprom interconnect
Synopsis: 6120 3.2.5: System Firmware Update
Date: Sep/12/2006


Install Requirements: NA                      
                      
Solaris Release: 8 9

SunOS Release: 5.8 5.9

Unbundled Product: 6120 Firmware

Unbundled Release: 3.2.5

Xref: 

Topic: 

Relevant Architectures: sparc
  	NOTE: 
	This patch release is for the 6120 Array only and not the
	T3 or T3B Array.  If you have a T3 or T3B Array, and are
	looking to update with the latest patch release, please 
	download patch 109115-14 (or later) and 115180-03 (or later)
	respectively.

BugId's fixed with this patch: 4252684 4462567 4486685 4486687 4737352 4762027 4794710 4835325 4850100 4852303 4892271 4903038 4922888 4935307 4936086 4939724 4941159 4943393 4944443 4946781 4952406 4963006 4963472 4964912 4965335 4965873 4970663 4970782 4970867 4972246 4972291 4974311 4974618 4978663 4979437 4979807 4981551 4981571 4982773 4983416 4984663 4985085 4986534 4987280 4989074 4989760 4990583 4991427 4992011 4993287 4997002 4998231 4998366 4998390 4998395 4999218 5003333 5003371 5004498 5005538 5006522 5007948 5008323 5009611 5009746 5013570 5013579 5013833 5013975 5014354 5014510 5014707 5015148 5015453 5017094 5018107 5018708 5018930 5019947 5021108 5022379 5022932 5023583 5024905 5028664 5030275 5031680 5031819 5031895 5033020 5033152 5033787 5034830 5035207 5037853 5037877 5038486 5040361 5043408 5043559 5043589 5043884 5043978 5044756 5044894 5045045 5045371 5046359 5047217 5047828 5049373 5052394 5052930 5053308 5053687 5054810 5055994 5056021 5059651 5060008 5060086 5060131 5060575 5060667 5060671 5062128 5062138 5062791 5063703 5064223 5064484 5064857 5066873 5066883 5069641 5069831 5070583 5072023 5072948 5073617 5073888 5074838 5075084 5077444 5077795 5077900 5077973 5079228 5079795 5079839 5079961 5080299 5080922 5081536 5081617 5082270 5082361 5082757 5082903 5082914 5083284 5083526 5083849 5085907 5086310 5086748 5086802 5088054 5088163 5089611 5090122 5090755 5090981 5091389 5091791 5092808 5093167 5093172 5093564 5099889 5099930 5101168 5101204 5101526 5103836 5104486 5105016 5105166 5107081 5107102 5107142 5107602 5108400 5108727 5110149 6174458 6180857 6180960 6181429 6181645 6183104 6183331 6183831 6184766 6185440 6188807 6189595 6190151 6191210 6192321 6195283 6195589 6198737 6201943 6202029 6204637 6206096 6207202 6209073 6209353 6211597 6213633 6213636 6213640 6219705 6220160 6221933 6238080 6242660 6261918 6263822 6270227 6273852 6282809 6284924 6305510 6311752 6323296 6337736 6345689 6347611 6350979 6359102 6383247 6391146 6402868 6455175

Changes incorporated in this version: 6455175

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: 

/var/sadm/swimages/116931-21/6120.sh
/var/sadm/swimages/116931-21/README.116931-21
/var/sadm/swimages/116931-21/files.tar
/var/sadm/swimages/116931-21/lpc14_7.23.bin
/var/sadm/swimages/116931-21/patchtoc
/var/sadm/swimages/116931-21/t4l1_325.bin
/var/sadm/swimages/116931-21/t4l2_325.bin
/var/sadm/swimages/116931-21/t4l3_325.bin
/var/sadm/swimages/116931-21/t4pt_325.bin

Problem Description:

--------------------------------------------------
 (3.2.5.5 Firmware)
---------------------------------------------------
6455175 Inc FACNV_VERSION 6020 running 3.2.4 cannot get any new replacement drive into the loop. It keeps disabling
--------------------------------------------------
--------------------------------------------------
 (3.2.5.4 Firmware)
---------------------------------------------------
6455175 6020 running 3.2.4 cannot get any new replacement drive into the loop. It keeps disabling 
---------------------------------------------------
 (3.2.4.4 Firmware )
---------------------------------------------------
6402868 System flag should stay clean shutdown after AC loss and array
is on
---------------------------------------------------
 (3.2.4.3 Firmware)
---------------------------------------------------
6391146 Request for change in RAS intermittent error handling and also driver's 01/5D handling
6383247 Storade request the glist info in fruprop.htm page impacts IO performance every 10 minute
 
---------------------------------------------------
 (3.2.4.2 Firmware)
---------------------------------------------------
6323296 NEED ABILITY TO MANIPULATE SCSI MODE SUBPAGE
 
---------------------------------------------------
 (3.2.4.1 Firmware)
---------------------------------------------------
6359102 6320: ISP2300[2] Qlogic External RISC RAM Parity Error Detected after array fw upgrade
6350979 Qlogic 22zz/23xx can transmit when switch BB credit is zero
6337736 6120: xf_util.c line 930, scbP->prev => 36917596 != 0
6345689 Implement a system flag to indicate whether the array system is shutdown properly
6347611 6120 take too long to log off the fabric (10 more min) when dual PCUs failed in the same
 
---------------------------------------------------
 (3.2.3.3 Firmware)
---------------------------------------------------
6359102: 6320: ISP2300[2] Qlogic External RISC RAM Parity Error Detected after array fw upgrade.
6350979: Qlogic 22zz/23xx can transmit when switch BB credit is zero.
 
---------------------------------------------------
 (3.2.3.2 Firmware)
---------------------------------------------------
 
6238080 R-RDYs are not sent in response to FCP frames
6305510 "Disk is replaced" message is logged in the syslog for disk that have never been replaced
6311752 Raise severity of message indicating array00 ROOT[1]: N: Unmounting volumes
4835325 the next scheduled refresh is less than 28 days from previous refresh
 
---------------------------------------------------
 (3.2.3.1 Firmware)
---------------------------------------------------
6270227 u1 failed to boot, with "thermal sensor" fail messages
6242660 Reconstruction attempted on raid 0 volume.
4737352 T4/T3B does not register its FC4-type to McData switch
6202029 T3B/6x20 - COPY RECON puts volume into write-through mode silently
6261918 6120 - SSTM for AIX does not work with single brick
6282809 6120 add enhancement on SCSI sense code 09
6221933 T4/T3B .disk commands does not, but should support disk drive vendor unique mode pages and log pages
 
---------------------------------------------------
 (3.2.2.1 and 2 Firmware)
---------------------------------------------------
6284924 T3B/T4 should unmount volumes if it finds incompatible drive f/w for Seagate drives
 
---------------------------------------------------
 (3.2.1.1 Firmware)
---------------------------------------------------
6273852 array-firmwa/array_config data integrity issue after sysipe and rebuild of array
 
---------------------------------------------------
 (3.2.0.39 Firmware)
---------------------------------------------------
6263822 6120 320_38: data corruption on write, Seagate 300GB disks, currently using 6120 2x6
 
---------------------------------------------------
 (3.2.0.38 Firmware)
---------------------------------------------------
6213633 6120: Illegal request during recon.
6213640 6120: drv disable by the WXFT task due to write error
 
---------------------------------------------------
 (3.2.0.37 Firmware)
---------------------------------------------------
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()
 
---------------------------------------------------
 (3.2.0.36 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.35 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.34 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.33 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.32 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.31 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.30 Firmware)
---------------------------------------------------
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 <fw> is done
6180857 Cannot recover lost password on T3+ running 3.x FW
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
 
---------------------------------------------------
 (3.2.0.29 Firmware)
---------------------------------------------------
5090755 6120/T3B:IO's to array completely die after BEFIT completes IC2 cable fault isol
5107602 6320: GUI remove multiple volumes caused array master-ctrl coredump, offline
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
 
---------------------------------------------------
 (3.2.0.28 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.27 Firmware)
---------------------------------------------------
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 &quot;lun default <all_lun lun <lun#>> <rw ro>
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".
5014354 6120: Ability to inject serial faults onto loopcard
 
---------------------------------------------------
 (3.2.0.26 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.25 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.24 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.23 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.22 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.21 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.20 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.19 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.18 Firmware)
---------------------------------------------------
5047217 6120:Unplugging one loopcard in 2x6 turns on amber LED on other loopcards
5043589 lid 7f failed attached" occurs after every LIP on back-end loops
5052394 Multiple Disk Fault Tolerance, Phases 2 and 3
5038486 T3B/3.1.4.11: data miscompare - 128 words in error
5055994 Multiple Disk Fault Tolerance phase 1
4992011 OFDG/ONDG u2 health checks on back-end loops always fail
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
5033787 6120 "boot -r" may cause Assert
5064223 Update 6120/T3B ISP2200 firmware to latest main branch
 
---------------------------------------------------
 (3.2.0.17 Firmware)
---------------------------------------------------
Remove 5038486 T3B/3.1.4.11: data miscompare - 128 words in error
 
---------------------------------------------------
 (3.2.0.16 Firmware)
---------------------------------------------------
5053687 Add CLI to access opaque segment
5040361 Dummy drives not write bypassed on bootup
5043978 s07 failed due to multiple drives "broken" after enable u4l2
5053308 6120/3.2.0.12: Array asserts during reset, after disk format cmd was issued to u
5052930 3.2 disk format cmd does not print status when it is complete
5043884 6120: lpc firmware download causes array reboot
5059651 commands can get stuck in svd layer for quite sometime.
5038486 T3B/3.1.4.11: data miscompare - 128 words in error
 
---------------------------------------------------
 (3.2.0.15 Firmware)
---------------------------------------------------
5049373 SVD SCSI error handling calls printf from interrupt context
5017094 Modify mesages in controller events
5044894 shelf life check should not be done on T3B
5035207 6120/3.1.3.10: error on read block 100 for 16 - lun failover takes too much time
5045045 RFE for online disk firmware download project.
4903038 6120:3.1.13-u1 stuck in "Waiting for configuration data from master" during boot
5046359 6120: All enclosure's drive LED turn amber when any loopcard is disabled
 
---------------------------------------------------
 (3.2.0.14 Firmware)
---------------------------------------------------
5044756 Final tuning of error messages after "rcp" and ".logger" is available
5037853 6120 failover failed to complete
5045371 incomplete firmware token blocks testing 6020 revision maint backout session
5037877 Confusing messages in Disk verify code
 
---------------------------------------------------
 (3.2.0.13 Firmware)
---------------------------------------------------
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
5043408 T3B: original IP is not preserved during the 1.18 to 3.1.4 upgrade
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
 
---------------------------------------------------
 (3.2.0.12 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.11 Firmware)
---------------------------------------------------
5013975 Adjust message level for QLCF driver
5033152 T3B/3.1.3.10: when drive is fault/disabled, amber led is not on.
5015453 Modify PCU/Battery messages
5030275 DiskPerf token statistics are incomplete in 2xN configurations
 
---------------------------------------------------
 (3.2.0.10 Firmware)
---------------------------------------------------
4978663 .disk linkstat works only for a drive in a tray with an enabled RAID controller
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.2.0.9 Firmware)
---------------------------------------------------
5003333 T3B/314_6: cache fails sense code 80/3d causing I/O failure
4979437 T3 PP stops operation completely when running more while logged in via SSRR
4998366 T3B: dirve amber LED on even after disk download complete
4963472 Data compare error by broken controller card
5023583 T3B/6120/3.1.4.9: u1 assert in svd.c on line line 4029 during drv disable/enable
5003371 T3B/3.1.4_6: data miscompare - 127 words in error (0x1)
4762027 6120/T3B: master went and stay in reboot, alt-master fails take over, system han
5009611 seg command to allow Ops to read/write segments
5031680 6120/T3B: need to disable disk scrubber when download disk firmware
5028664 T3B should unmount volumes if it finds incompatible drive f/w for MANXXX drives
5018708 6120/3.1.3.8: boot -r hangs u1, u2 did not take over
5031895 T3B: Should not be able to select sys blocksize 4k, 8k values
4922888 Turning on Locator LED, turns off attention led (amber) on chassis
 
---------------------------------------------------
 (3.2.0.8 Firmware)
---------------------------------------------------
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()
 
---------------------------------------------------
 (3.2.0.7 Firmware)
---------------------------------------------------
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
 
---------------------------------------------------
 (3.2.0.6 Firmware)
---------------------------------------------------
4987280 T3B:u1 disabled with xf_lock.c line 2515, Assert(mirror_list[fac_ix].lru == 0)=0
5006522 RAMDISK file system support
4970663 T3B/3.1.2_1: lpc offline/online during ctr failover test
4970867 6120: drv bypass due to lpc disable does not last through ctr reset
 
---------------------------------------------------
 (3.2.0.5 Firmware)
---------------------------------------------------
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
5008323 Need to add SCSI Error injection mode page definition
4998395 Change some LOG_NOTICE debug messages to LOG_INFO
4998231 6120, 314_6: recon of unplugged drive (.mcdk 6 2 9) failed, disk unmounted
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
 
---------------------------------------------------
 (3.2.0.4 Firmware)
---------------------------------------------------
4943393 need volDiskIsRoleStandby token added to vol.htm or volprop.htm
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 u<encid>d[1-14]' turns AMBER led on wrong drive ON.
4972291 6120/3.1.3.2: replug drive with .mcdk showed drive was bypassed again.
4985085 T3B: "ep download" get stuck with diskcrubber on
4941159 6120:Enabling a disabled cntrl takes 25min,stuck at"loop 1 TARGET_ID"phase 15min
 
---------------------------------------------------
 (3.2.0.3 Firmware)
---------------------------------------------------
4974311 Turning on locator LED activates lpc blue/amber LEDs
4982773 Amber enclosure led does not come on when loopcard is pulled
4939724 6120 3.1.0.23: boot -r sometimes doesn't wipe all labels; unmounted vols remain
4850100 T3A/T3B/6120 READ CAPACITY opcode (0x25) goes through the wrong mpxio path during
4989074 Enhance crashdump message buffer
 
---------------------------------------------------
 (3.2.0.2 Firmware)
---------------------------------------------------
4983416 Disabling switch port to u1 causes alt master assertion reset
4981551 T3B: controller reset switch does not reset controller in 3.1.3 FW
4963006 6020 pcu amber led is not lit when fan is jammed and pcu becomes fault-enabled
4252684 Reconstruction rate does not change dynamically.
 
---------------------------------------------------
 (3.2.0.1 Firmware)
---------------------------------------------------
4946781 6120/T3B: pcu's with failed batteries do not show amber LEDs
4979807 T3B after upgrade all u1d0[1-9] disks are blinking amber but fru stat says good

Patch Installation Instructions:
-------------------------------- 
 This patch includes a firmware uploading utility (6120.sh) that 
 simplifies transferring the contents of this patch to a StorEdge
 6120 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.
 
  Note: To verify the current firmware version running on a target
       6120 system, use the 'ver' command at the 6120 command line
       as follows:
 
         array00:/:<3>ver
 
        6120 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.
 
 
  If this patch is to be applied to a component that is part of a system
  (6320/6920), please use the revision maintenance to apply patch.
 
  ONLY use the following steps for 6120 that is NOT part of a system(6320/6920):
 
 1. System Preparation
   Once the patch has been downloaded to a Solaris host, change
   directories to the patch directory and run the following command:
 
          # pkgadd -d . SUNWc6120
 
  The resultant files will be located in the following directory:
  /var/sadm/swimages/16931-21
 
 2. Verify the 6120 system to be upgraded is reachable on the network:
 
         $ ping array00
           array00 is alive
 
 3. Verify the 6120 system working correctly. The 6120.sh script supports
empty password, so there is no required to have password in 6120 system.
 
        $ telnet array00
        Trying 129.150.47.115...
        Connected to array00.
        Escape character is '^]'.
 
 
        Unauthorized access is prohibited.
 
 
        Login: root
        Password:       
 
        6120 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.
        array00:/:<1>
 
 4. Transfer patch contents to 6120 system.
 
    Note: There is limited space available in the 6120's reserved system 
          area.  Therefore, it is important to be sure there is 
          adequate space on the 6120 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 6120 once those images have been loaded per the
          instructions provided in this readme.
 
    The recommended way to install the contents of this patch on 
    6120 systems is to use the included 6120.sh script from a Solaris
    host that has network access to the target 6120 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 6120 system using the following
    method.  
 
      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 6120 system:
 
             Patch Source Location        6120 Destination 
             -------------------------    ------------------------
              ./lpc14_7.23.bin            /lpc14_7.23.bin
              ./t4l2_325.bin              /t4l2_325.bin
              ./t4l3_325.bin              /t4l3_325.bin
 
           (From temporary Working Directory)
              ./etc/bat.conf               /etc/bat.conf
              ./web/*.htm                  /web
              ./web/snmp/6120.mib          /web/snmp/6120.mib
              ./etc/zoneinfo               /etc/zoneinfo
 
    Automated File Installation
    ---------------------------
    Note: The '6120.sh' installs all controller and system files but 
          does not overwrite /etc/hosts and /etc/syslog.conf files 
          on the target 6120 system as these files are typically
          customized per local operating environment requirements.  
          One exception to this is the battery refresh scheduler
          file on the 6120 (/etc/bat.conf).  The 6120.sh script
          will make a backup copy of this file on the 6120 (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 6120 
    system can be reached through the local network (use ping to verify 
    the target 6120 system is reachable).  Once this has been confirmed,
    the installation script can be started as follows:
 
       ./6120.sh
 
    (Note: Be sure the 6120.sh script is executable.) 
 
    The 6120.sh utility will prompt for information as follows:
 
      Please Enter Hostname or IP Address Of 6120 To Be Ugpraded: 
 
       -> Enter Hostname or IP address of the target 6120
          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 
           6120.sh script (this is used by ftp to automatically load the patch
           file contents to the 6120).
 
    Enter ftp user:
 
       ->  Enter the default 6120 root login
 
    Enter ftp password:
 
       ->  Enter the root password for the 6120
 
    At this point, the automatic ftp login/upload process should
    begin.  
 
 5. Please refer to section "Upgrading Array Firmware and System Files" in Chapter 6 
    of "817-0200-10: Sun StorEdge 6020 and 6120 Arrays System Manual" for 
    information on upgrading the firmwares.
 
    NOTE: You just NEED to upgrade level 2 and 3 Firmwares

Special Install Instructions:
-------------------------------------------
If you plan to run several automated file installation scripts (6120.sh)
the same time on one host to update many 6120 systems, you must enter
different "Home Directory Path" since 6120.sh script will use $HOME/.netrc
for ftp. Please make sure that you have full permission in those
directories.

README -- Last modified date:  Wednesday, September 13, 2006

