Patch-ID# 112276-07
Keywords: T3 T300 T310 raid storage firmware loopcard eprom interconnect
Synopsis: T3B 2.01.04: System Firmware Update
Date: May/23/03

Solaris Release: 2.6 7 8 9

SunOS Release: 5.6 5.7 5.8 5.9

Unbundled Product: T3B Firmware

Unbundled Release: 2.01.04

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-13 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: 4785593 4683597 4388177 4729107 4821006 4810681
4785757 4857772

Changes incorporated in this version: 4785593 4683597 4388177 4729107 4821006
4810681 4785757 4857772

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: 

  disk/                  # T3B disk drive firmware 
  docs/                  # Release Notes, pdf manuals
  files.tar              # T3B System Files Tar Image
  lpc_05.02              # Unit Interconnect Card Firmware
  nb214.bin              # Controller firmware
  patchtoc               # t3.sh: Files to Upload To Target T3B 
  previous/              # The previous T3B firmware release
  t3.sh                  # T3B File Upload Utility 
  README.112276-07	 # README file for the patch

Problem Description:

---------------------------------------------------
 (2.01.04 Firmware)
---------------------------------------------------
4785593 T3/T4: array may crash after 497 days of uptime.

4683597 Typo in schd.conf, causes continuous

4388177  Need to hardcode Battery Scheduler Refresh Times

4729107 upgrade from 1.16 to 1.18 - after reset -y the logto and
loglevel change

4821006 T3 FW 1.18.02 loglevel does not work correctly

4810681 T3B/T4: disk download FW A538 fails t3B

4785757 T3B: 2.1.X s/w - Lun permissions/Hwwn groups disappear - after
T3B "reset -y"

4857772 Running ofdg diagnostics causes related to 4810681 bug fix

---------------------------------------------------
 (2.01.03 Firmware)
---------------------------------------------------
4766676 Standard INQUIRY to LUNS greater than 15

4760757 Single byte returned for STANDARD INQUIRY of LUNs greater than 15

4525852 - go to .pROBE when type "ls -l web/snmp"

4648055 Raid 5 'vol disable <disk> to_standby' can cause corruption
after read errors

4664674 T3 Raid1 'vol disable uxdy to_standby' fails

4654238 Drive hot swap results in '2D' for new drive and reconstruct fails

4675955 data miscompare in T3 running madrw with Fujitsu disk drives

4707617 "Unrecovered Read Error" during "vol verify fix" operation
not corrected

---------------------------------------------------
 (2.01.02 Firmware)
---------------------------------------------------
4697868 Handle 03/11 disk error code as the way in 2.1.0.

4697286 Set FCP_STATUS flags and FCP_RESID count correctly and fix
the problem with reservation conflict status.

4717579 Fix for handling case when lun number is outside the
supported range.

4714434 Dynamic addition of T3B volume slices creates LUN permissions
problems.

---------------------------------------------------
 (2.01.01 Firmware)
---------------------------------------------------
4697868 Disk in raid 5 on T3B failed and Oracle database crashed in
clustered config

---------------------------------------------------
 (2.01.00 Firmware)
---------------------------------------------------                            
4492471 Incorrect ASCQ value returned when LUN is read-only and 
        write is attempted on it
4493530 volslice list is not consistent in showing 1mb slice size
4484792 "lun perm list lun #" show every registered wwn 
	even though the access permit is NONE"
4488012 No LIP is now generate by T3 when lun is mounted
4500534 lun perm list wwn # does not show lun permissions of all
	_wwn set to zero.
4501381 LUN perm list wwn # command displays an incorrect number
	of entries.
4505999 lun masking should provide a command to change default
	lun access permission
4474649 - Added support for a CLI command and token to create 
	a binary image of the FRUID SEEPROM.
4530388 BatLifeDBInit is in the critical path and it takes 30 seco
	nds to complete
4517125 File date stamp displayed in GMT not local offset
4288665 Need NTP Support
4532568 Minimum slice size should be 1GB and slice size should be 
	multiple of min
4529823 Restrict volume size to 1TB for unit with 180GB drives
4532541 Ioctl release error on Indy 500 with Sun Cluster Scate 1.1
	script
4599531 SCSI-2 testsuite fail 7 test cases and 2 unresolveds with 
	T3B FW nb210p13.bin
4614866 Too many LIPs caused by a sequence of "lun perm ..." settings
4503207 Set CFLAGS bits after calling qlcf_i_offline(qlcf) in
	qlcf_i_polled_start_cmd
4621541 bug fix- ie code clean up
4533276 Mpxio is not failover when pulling out FC cable while
	purple is reconstructing
4341357 OFDG Health_check does not report correctly with a disabled
	controller.
4626782 More code clean up -with reference to bug 4593081
4615610 cmdlog file does not display time
4638107 code cleanup in volslicing
4637654 Change vol size restriction from 1TB to 2TB
4627352 remove the multicast option in the cli.
4636819 Issuing ntp commands to Alternate Master does not return
	anything but prompt
4636931 tzset needs to map to new timezones
4462327 Redundant non-disk FRU detection needed to avoid system
	shutdowns
4635581 T3B: qualified DIMM's not recognized
4620913 illegal instruction causes probe break
4630221 T3b: The year value is displayed incorrectly with the 'ls -l'
	command.

4487208 Volslice data missing in slave controller after disable then
	enable u2.
4484817
4495302 upgrading from 2.0 to 2.1 enabling volslicing sometimes
	results in VN_VSLRAIDERR
4495745 create volslice through token now accept starting address 0.
4496336
4526195 which is to add volslice support for some new code.
4416729 debugging counter shold be ifdef'd out of production code.
4533027 qlcf: source files are not cstyle clean.
4533024 qlcf: Migrate to qlogic EF firmware base.
4532042 T3 - Require Fabric Point to Point (F_Port) support.
4523900 token interface needed for changing the default access
	right for lun masking
4408563 Improve syslog message for "invalid field in CDB"
4419913 Variable is used without being setting or initialized.
4599614 need to check in Olson time zone source files
4533694 OFDG -y fast_test does not report status.
4533809 Master unit resets itself while running OFDG -y health_chec.
4384987 stack dump added in reset log
4618781 Host can sometimes access a device with permission set to none.
4616946 SCSI-3 PGR:error in medium non-transfer task not propagated
back to cluster task.
4619240 endian swap WWN in GetDeviceMap()
4627363 Fixes 86 uninitialized variable instances.
	Also turns the compiler lint option on by default.
4622029 Qlogic fix for Lip storm problem.
4341673 OFDG - Open serial lines in interconnect cable causes
	inconsistent results.
4336839 OFDG diagnostics do not indicate when a interconnect cable is
	missing.
4613972 add token for future error code return
4623936 T3B-2.10: volslice command doesn't check for valid characters
4631375 T3B2.1 p16 b6 firmware takes an extra argument for
	enable_volslice option.
4631453 Need to use T3 wrappers for certain psos function calls
4618752 2.01 volslice enabled system http reads take too long
4527674 H.E.A.T security software scan causes T3 controller failure
4621445 rstlog is not dumped to syslog automatically
4626963 There are several uninitialized variables which can/may cause
	problems.
4631690 Remainder of uninitialized variables.
4616042 T3B_FW2.1 VM does not detect slices created on T3
4634339 It is possible that entire volume can not be sliced.
4521218 T3B WG password and set command configuration lost when
controller replaced.
	4622616 Firmware 2.1 reports incorrect value for volCapacity
4623335 default lunMaskAccess reporting incorrect access permissions
4316769 Need an in-band method to obtain T3's IP address
4635559 Mismatch in fc_topology config in AM when ISP chip resets
	during I/O failover
4410117 OFDG tests product "ioctl disk failed err" with no fault
	condition apparent.
4619778 need a way to display Current Topology
4628121 Excessive Notice level messages in T3 syslog.

---------------------------------------------------
 (2.00.01 Firmware)
---------------------------------------------------
4474779 Purple returns ASC 90 00 for path that is becoming ACTIVE
4298510 T300 f/w does not support SCSI write buffer and read buffer commands.
4374724 Multiple Non-Adjacent Disk Failures in a RAID 1 stripe cause LUN to unmount.
4410516 cache stays write through even when forcing write behind
4383854 Write-behind cache disabled when RAID 5 disk fails
4498758 Reset causes controller to hang
4488964 silently shut down.
4498487 Firmware reports wrong buffer size for SCSI read/write buffer commands.
4493006 T3 can not clear the key requested by a new PGR command REGISTER_AND_IGNOREKEY.
4470439 Partner Pair testing with 1.17b fails SCSI-3 Cluster TS reserve_r{1,2} test
4497511 PGR does not work correctly when connected via a python TL port.
4388855 Change to Controller firmware version format to dot-dot format
4430163 ISP2100 firmware v1.19.108 Target Mode Hang during MPXIO Unit Test
4495720 Purple 1 incorrectly implements EOFni handling
4414235 syslog priority in a T3 can't be changed
4500452 T3 slave controller PGR data base sometimes is not clean.
4483239 POST - I2C read error at the beginning of a reset.
4504356 T3 needs to take PGR IN/OUT commands on its standby paths.
4483245 u1 hotplug fails to boot
4406749 Lun reconstruction can be slow with light IO from host
4458768 line break handling is broken
4505027 Need to support cross-domain builds
4486603 alternate master reboot while the master pull out
4486451 LUN becomes unavailable while doing DMP test.
4490884 Cache mirror failed after T3 Master ctr disabled (.probe) then enabled
4433886 No message when hit XOR multibit error
4459997 Single Bit Errors Should be Refreshed
4477769 p14 does not report grounded data bit on the accum, p05 does
4486568 Disable adjacent drives, followed by replacement and recon = bad data
4480200 Firmware should stop battery discharge at 6 minutes.
4428036 Alt. Master FRUID info not displayed
4445616 disk port shows 'notReady' instead of 'bypass'
4412662 possible mailbox cmd struct leak in qlcf_start_gauntlet()
4476044 HPUX + HP A5158A hba breaks ioscan
4449891 4 properties with read-only/clear access cannot be cleared.
4434826 Dead T3 -config'ed w/ 2 LUNs, used as quorum panic'ed & killed Cluster for good
4457439 Bad System Area on disk is not fixed when possible during controller takeover
4502467 Testsuite misc_r{11} fails --- T3 - for Single brick
4351210 less than 256 mb cache detected should be warning not notice
4478907 Disabling of standby drive does not work correctly
4426026 sf2 sf_cmd_callback: Lost Frame (read) received 0x8 expected 0x1f4 target 0x1
4508212 T3WG and HP A5158 HBA locks up HPUX SAM utility
4385004 fw 1.16 long hostname gains copy of root password.
4511648 Prism debugger on purple-1 hit program exception with a break point set
4508802 SCSI r/w buffer cmds should ignore SCSI reservation and not cause LUN failover.
4510028 POST diag's error message is misleading and incorrect.
4510037 POST diag anomaly (not meeting design spec).
4411749 too deep a cd leads to instruction access exception and fs messages.
4462253 BIST xor tests don't report correct failing data
4451137 diag syslog messages need controller identification
4514172 UART Enhancement for Loop Card Communication
4506732 Diskomizer stops with data compare error, when run with attenuator
4506206 T3WG sets MultiP bit in standard SCSI inquiry data
4515402 command lock fails to work if open telnet session
4436728 Data compare error, 2 block fails during Controller pull test
4519958 Received data exception during bootup and controller reset.
4517084 Manual XOR tests upper address range unaccessable
4418601 syslog states Please Send ISPDEBUGDUMP to Development Engineering
4520739 Existence of hidden 'psh' commands, should be removed
4475447 sys stat shows controller booting but role is reported as Altmaster
4521979 sub rev printing problem
4511149 cmdlog - keyboard buffer overflow
4509295 REGISTER operation fails on one initiator
4509300 T3 with PGR reservations active fails under IO load
4497687 sysdiag data compare failure is counted as passed
4509888 Bad drive causes vol verify to hang
4348580 two loop mode causes performance impact
4372821 fru stat now gets all drive temperatures.
4386434 Stale FCP port database(Loop Failure)
4524258 P1 and P2 return Success when the host tries to preemptandabort an unexistent Key

-------------------------------------------
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 login as
different users since t3.sh script will use ~/.netrc for ftp.

 --------------------------------
 I. PATCH PRE-INSTALL INSTRUCTIONS:
 ---------------------------------
 
  1) ftp the 'syslog' or the file to which the system log is directed
     from required T3B on which patch 112276-07 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.
 
 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 2.00 2001/07/12 19:35:12 (10.4.32.63)
	 Copyright (C) 1997-2001 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 t3
           t3 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 t3
        Trying 129.150.47.115...
        Connected to t3.
        Escape character is '^]'.
 
 
        pSOSystem (129.150.47.115)
 
        Login: root
        Password:       <---- Must type password here
 
 
	 T3B Release 2.00 2001/07/12 19:35:12 (10.4.32.63)
	 Copyright (C) 1997-2001 Sun Microsystems, Inc.
	 All Rights Reserved.
 
        t3:/:<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 reserved system 
          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.
 
    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
              ./nb214.bin                 /nb214.bin 
 
           (From temporary Working Directory)
              ./etc/schd.conf              /etc/schd.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/schd.conf).  The t3.sh script
          will make a backup copy of this file on the T3B (to 
          /etc/sch_old.conf) before copying over the new 
          /etc/schd.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. 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 Flash      5.01 Flash     
        Enclosure  2    5.01 Flash      5.01 Flash     
 
        :/:<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 t3 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
 
    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 Flash      5.02 Flash     
        Enclosure  2    5.02 Flash      5.02 Flash     
 
 
 6. Boot the T3B controller boot code.
 
    From the T3B command line, type the following to install the
    boot code:  
 
       :/:<7>boot -i nb214.bin
 
   (Caution: be sure all IOs have been quiesced and no host IO activity
             is scheduled to start until the upgrade procedure has completed)
 
 7. Verify system boot mode set to auto:
    From the T3B command line, type the following:
 
       :/:<9>set bootmode auto
 
 8. Reset the T3B System as follows:
 
       :/:<10>reset 
       Reset the system, are you sure? [N]: y
 
 9. 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.
 
10. type "port list" and verify ports
 
      :/:<1>port list
 
      port   targetid   addr_type   status   host   wwn
      u1p1      1        hard       online   sun    50020f2300000f61
      u2p1      2        hard       online   sun    50020f230000297d
 
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 US/Pacific
    This will set the timezone to the Pacific time zone
    
    or,
	
       :/:<3>tzselect
    This will give you a simple menu driven utility to select time zone.

    ** Default time zone is GMT00.
 
  Congratulations, the upgraded T3B is ready to use again.
 

 ---------------------------------------
 II. 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 customer backs 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 Component 
	      Manager is being used to monitor the T3B, automatic polling 
	      must be disabled. Refer to the Component Manager Users 
	      Guide for instructions to disable T3B polling.
 
            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 download, T3B may report following error
          messages in syslog. This could happen because of drive
          incapability to complete the request during the firmware 
	  download or the disk may be resetting. This will not cause 
	  problem to any of T3B functionalities, hence these messages 
	  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, than 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 successfull, 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), reinitialize 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.

