OBSOLETE Patch-ID# 110760-02 Keywords: T3 T300 T310 cluster raid storage firmware loopcard eprom interconnect Synopsis: Obsoleted by: 109115-07 T3 1.16a: Cluster System Firmware Update Date: May/02/2001 Solaris Release: 2.6 7 8 SunOS Release: 5.6 5.7 5.8 Unbundled Product: T3 Firmware Unbundled Release: 1.16a Xref: Topic: Relevant Architectures: sparc BugId's fixed with this patch: 4411125 Changes incorporated in this version: 4411125 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: 109115-07 Files included with this patch: disk/README.disk # T3 disk drive firmware version notes disk/S* # T3 disk drive firmware images docs/cli.pdf # Administrators Guide docs/ios.pdf # Installation, Operation, and Service Manual docs/relnote.pdf # Release Notes docs/taskmap.pdf # Installation Task Map ep2_10.bin # Controller EPROM Flash files.tar # T310 System Files Tar Image lpc_05.02 # Unit Interconnect Card Firmware nb116a.bin # Controller firmware patchtoc # t3.sh reference:Files to Upload To Target T3 t3.sh # T3 File Upload Utility NOTE: --------------------------------------- T3 Sun Cluster 2.2 Patch --------------------------------------- This patch is intended for use on T3 systems configured in SunCluster 2.2 configurations only. If the T3 system(s) are not being used in a Sun Cluster configuration, patch 109115-04 (or later) should be used. The Sun StorEdge T3 disk tray was formerly known as the Sun StorEdge T300 prior to final product shipment. Most of the Sun StorEdge T3 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 T3 and Sun StorEdge T300 names refer to the same product and are equivalent in terms of product features and functionality. --------------------------------------- Sun Cluster 2.2 / T3 Known Issues --------------------------------------- 4399132: During volume reconstruction if recon_rate = "high" nodes cannot join cluster. If the reconstruction rate in a T3 system is set to high, and a volume is being reconstructed (such as after a disk replacement), SC 2.2 nodes will not be able to successfully join the cluster. It is recommended the factory default setting of medium for the reconstruction rate be used when T3 systems are used in a cluster. 4386836: Drive firmware download or T3 boot command can hang When upgrading an existing T3 system running 1.16 level firmware to 1.16a, a known problem exists where the system is unable to allocate enough memory to run the ''boot'' command. The end result of this problem is the ''boot -i'' command used to load the new firmware never returns to the command line prompt. In some cases, the same type of behaviour has been observed with systems running 1.16 (or 1.16a) level firmware and trying to run the ''disk download'' command to upgrade drive firmware. To workaround this issue, a T3 system reset followed by another attempt at the failing command usually works. The system reset can be accomplished by establishing a new telnet session with the T3 being upgraded (using another window on your host system), followed by a T3 reset command. Once the T3 system has completed the reset cycle, again establish a new telnet session with the T3, and re-run the desired ''boot -i'' or ''disk download'' command. In some instances, even with a T3 system reset, enough memory is not freed up to load and execute the boot command. In these cases, the firmware upgrade procedure can be performed using the T3 serial/console port. Should this become necessary, it is recommended a Sun Authorized Service Provider be called to perform this operation. Problem Description: --------------------------------------------------------- 110760-02 (1.16a Firmware) + Disk Drive Firmware Update) --------------------------------------------------------- 4411125 Seagate Cheetah 4 Drive Firmware Update --------------------------------- 110760-01 (1.16a Firmware ) --------------------------------- 4373662: SunCluster 2.2: Surviving node fails to take over if no LIP occurs 4377075: Offline hosts sometimes not detected by T3 --------------------------------- 109115-04 (1.16 Firmware) --------------------------------- 4345011 Failed disk drive can caused partner group to go offline 4345036 Assert Reset (3000):qlcf.c line 3289 Assert(ccb->cam_ccb_list 4363630 Probe break in qlcf.c due to unexpected ISP chip status 4337653 Enabling a disabled controller through CM sometimes fails 4348500 panic on cluster master results in reservation conflict on T3 4353469 battery refresh stuck in a discharge loop 4361866 during drive hot plug test , dex io errors and probe break 4296017 cache stays at writethrough after controller/loopcard failover 4339555 ofdg run with a bad u2l1 causes T300 reboot loop 4341193 Upgrade/Downgrade lpc fr/to 4.13 & 5.01 caused amber LED 4342142 EU: Multiple drives bypassed when using .probe in fail-over t 4346447 Tokens don't provide accurate status after a ctr enable 4350267 Disk is being bypassed during volume initialization 4353101 rack configuration fails FC cable to hub failure test 4353660 MADRW errors because T3 is busy handling drive disable 4353667 Interrupted more command results in performance loss 4353731 Incorrect value in LPC 5.01 fw download disables T3 4359814 Multi drive hot plugs cause ISP chip dumping data 4363780 Target Reset Not Issued To Clear Reservations 4322151 Missing controller doesn't start overtemp shutdown timer 4338553 Incorrect display of lpc SN's in fru list 4351027 tftpboot of nb113.bin on systems w/new drives drops to ADMIN 4352277 Battery refresh does not properly maintain interval specified 4371858 README.109115-03 states t3.sh prompts with T3 login prompt 4371912 README.109115-03 identifies wrong ftp step 4371926 README.109115-03 does not identify how to determine disk drive type 4371933 README.109115-03 should tell user to remount volumes 4383266 t3.sh script fails if executed from directory other than "." --------------------------------- 109115-03 (1.14 Firmware) --------------------------------- T3 Disk Drive Firmware included in patch. --------------------------------- 109115-02 (1.14 Firmware) --------------------------------- 4344316 Stray IOCB's cause probe break 4350265 Back-end cache mirroring enable problem 4346571 EU: Probe break on controller exhausted mbox commands 4326248 t3.sh patch installation script overwrites .netrc 4290158 Reconstruction doesn't start after boot with a failed disk 4304266 No drive reconstruct if drive fails when volume is unmounted 4306056 More robust DRAM parity error reporting/handling 4302850 Cluster: rsv100.bin fails scsi2 reservation test suite 4309906 volume create/delete/mount/unmount POST operation returns early 4309901 CM unable to detect or notify failed volume initializations 4311688 Drives are offlined when unmount and recreate a LUN with one lun 4317086 Separating a partner group will cause single unit boot cycle 4306345 sysAutoDisable token doesn't give enough info about autodisable 4292138 System needs manual loop failure isolation facility 4326147 multi-controller disable during heavy load/stress test 4280101 ISP2100 f/w panic during PCI/DMA errors 4305281 T3 trying to use AL_PA 0x01, can cause config problems 4262121 Need http token for ondg output 4290161 Excessive LIPs can cause SCSI 'Report Lun' issues 4290677 ISP2100:Outgoing Mailbox 0 register reports 0x8002 (sys err) 4293211 T3 should immediately execute scsi "report lun" & inquiry 4293252 Qlogic firmware LIP'ing prematurely 4297464 Master Controller disable during drive hot plug simulation 4311922 T3 syslog date stamp often off by timezone offset 4313092 Controller failover test needs a second reseat to boot 4317148 elemprop.htm page shows wrong values for fruPowerBatLife 4326190 Miscellaneous sys command changes 4326920 running ofdg 'health_check' with u1l1 disabled resets T3 4282275 Some system default settings need to be removed 4291723 Fan failure injection Doesn't Correctly Initiate LED 4307139 Some syslog entries to be moved from warning to notice 4308583 Back-end loop failure test causes stale FC-AL port 4317596 Copyright login banner should be updated 4335062 Loop 1 split should not be allowed in Non-HPC enviroments 4323931 SGI:T3 locks up in a hang status until SYNC cmd issue 4329797 http traffic during ofdg -y fast_find causes probe break 4331699 T3 with one lun can Qfull and stop all i/o for 60 seconds 4335848 Drives being spun down by controller firmware 4329876 infinite loop after restart from TDL probe break 4331817 token for controller temperature should be celsius 4260918 A bad interconnect cable causes repeated LIPs 4299474 T3 POST should be able to detect cache memory parity errors 4325782 Intercept all exception vectors for CPU 4331682 OFDG Abort tokens should be removed 4332462 Probe break after reset -y, following boot -i file 4335250 Drive component failure caused probe break during ofdg run 4323937 Reservation not cleared with SCSI Reset 4335070 CM2.1 after "Disable" of u2ctr, "Disable" goes inactive 4324402 CM showed wrong loop card as disabled 4332909 Upgrade from 0.95 to 1.00 results in probe break 4333385 Excessive characters to passwd command causes probe break 4333439 File system check got a verify volume failure 4333611 Double disk pull (w/standby) on RAID 1/5 causes boot loop 4334609 fru stat loop cable display is reversed 4328814 battery/pcu LED should go amber on battery hold test failures 4335870 New HPC Vendor ID breaks T3 back-end cache mirroring 4336121 firmware shuts off all token access during OFDG tests 4334945 ONDG error token indicates prematurely testing is complete 4336123 CM2.0 and T3 FW1.11 result in number format exception 4336487 Loop card firmware 5.01 doesn't show the vendor/model fields 4333578 Progress indicator does not work for OFDG 4311701 OEM:With cache mirroring enabled need to support write caching 4317995 T3 volumes got unmounted during heavy load/stress 4330350 ofdg uses inconsistent loop card device names 4332202 When in writebehind cache mode, enabling failed controller fails 4334419 Battery Scheduler File To Be Moved to 14 Days 4328000 sys command option 'vendor' is available through usage 4338106 OFDG diag status never updates to show it completed 4337620 Controller Firmware Should reset hung Qlogic Chips 4342258 Patch readme to install firmware incorrect -------------------------------------- 109115-01 -------------------------------------- (1.01a RR Firmware Release) Patch Installation Instructions: -------------------------------- This patch includes a firmware uploading utility (t3.sh) that simplifies transferring the contents of this patch to a StorEdge T3 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 T3 system, be sure to stop all IO activity from all attached host systems. This procedure requires a T3 system reboot so all necessary host preparations needed to sustain this procedure should be made before starting. It is recommended all T3 volumes be unmounted on Solaris before proceeding with this patch installation. Note: To verify the current firmware version running on a target T3 system, use the 'ver' command at the T3 command line as follows: t3:/:<3>ver T300 Release 1.14 2000/07/12 19:22:50 (192.168.209.123) Copyright (C) 1997-2000 Sun Microsystems, Inc. All Rights Reserved. To update the T3 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 T3 system to be upgraded is reachable on the network: $ ping t3 t3 is alive 3. Verify the T3 system has a root password (the 't3.sh' patch utility uses ftp to transfer the files to the T3 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 T300 Release 1.14 2000/07/12 19:22:50 (192.168.209.123) Copyright (C) 1997-2000 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 T3 system and using the 'passwd' command. 4. Transfer patch contents to T3 system. Note: There is limited space available in the T3's reserved system area. Therefore, it is important to be sure there is adequate space on the T3 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 T3 once those images have been loaded per the instructions provided in this readme. The recommended way to install the contents of this patch on T3 systems is to use the included t3.sh script from a Solaris host that has network access to the target T3 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 T3 system using the following method. Note: It is not necessary to transfer all files contained in this patch to a target T3 system. For example, the docs subdirectory in the patch provides reference documentation and is not required by a T3 system. Manual File Installation ------------------------ -> Extract the contents of the 'files.tar' image to a temporary working directory: -> Manually ftp the following files contained in the files.tar image to the corresponding directory on the T3 system: files.tar Source Location T3 Destination ------------------------- ------------------------ ./ep2_10.bin /ep2_10.bin ./lpc_05.02 /lpc_05.02 ./nb116a.bin /nb116a.bin ./etc/schd.conf /etc/schd.conf ./web/*.htm /web ./web/snmp/t300.mib /web/snmp/t300.mib 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 T3 system as these files are typically customized per local operating environment requirements. One exception to this is the battery refresh scheduler file on the T3 (/etc/schd.conf). The t3.sh script will make a backup copy of this file on the T3 (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 T3 system can be reached through the local network (use ping to verify the target T3 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 T3 To Be Ugpraded: -> Enter Hostname or IP address of the target T3 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 T3). 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 T3 root login and password. 5. Load new Unit Interconnect Card Firmware: Using 'lpc version' on the T3, if the loop card firmware is running downrev firmware, upgrade all loop cards in the partner group as follows from the T3 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 T3 controller boot code. From the T3 command line, type the following to install the boot code: :/:<7>boot -i nb116a.bin file header: size 2677a4, checksum 74343c14, start 20010, base 20000 (Caution: be sure all IOs have been quiesced and no host IO activity is scheduled to start until the upgrade procedure has completed) 7. Download the new EPROM Code. From the T3 command line, type the following: :/:<8>ep download ep2_10.bin Done with writing EPROM code of controller 1 Start writing EPROM code of controller 2 Done with writing EPROM code of controller 2 8. Verify system boot mode set to auto: From the T3 command line, type the following: :/:<9>set bootmode auto 9. Reset the T3 System as follows: :/:<10>reset Reset the system, are you sure? [N]: y 10. 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. Output should be similar to the following: T300 Release 1.16a 2000/11/21 19:42:08 (192.168.209.123) Copyright (C) 1997-2000 Sun Microsystems, Inc. All Rights Reserved. 11. 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 12. 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 13. Congratulations, the upgraded T3 is ready to use again. Drive Firmware Upgrade Instructions ------------------------------------ Note: A disk drive firmware upgrade may not be necessary. To verify the most up to date drive firmware versions are installed, run the 'fru list' command on the StorEdge T3 system and compare the results of that output with the information found in the README.disk file (see the disk subdirectory of this patch). During a disk drive firmware download, the functionality of the disk tray is limited. To avoid system problems verify: o A current backup copy of the data on the T3 exists. o The data path between the T3 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 T3 is not being used for any other operation during this procedure. If Component Manager is being used to monitor the T3, automatic polling must be disabled. Refer to the Component Manager Users Guide for instructions to disable T3 polling. o No unnecessary command line program interaction with the T3 system is performed during disk drive firmware downloads. Note: 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. Disk Firmware Upgrade Instructions ------------------------------------ 1. Using ftp, transfer the appropriate disk drive firmware to the T3 root directory from the disk/ subdirectory contained in this patch. Be sure the file is transferred in binary mode. Note: The T3 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 T3 (see T3 product documentation for specific details if necessary). Log into the system as 'root'. 3. Verify all T3 disks are in an optimal state as follows: -> Confirm all disks are ready and enabled using the T3 '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 T3 volumes To ensure no host IOs are active, unmount all T3 volumes from the host system. In addition, it is recommended the internal T3 volumes be unmounted as follows (using volume v0 as an example) :/:<1>vol unmount v0 7. Install the drive firmware using the T3 '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 T3 command 'fru list'. 9. Reboot the Sun StorEdge T3 array after all drives have been upgraded. The T3 system can be rebooted using the T3 '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 T3 after the download ensures the version information is updated correctly in internal T3 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 T3 'fru stat' command. -> Confirm all disks correctly report model number and new firmware version information correctly using the T3 '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 T3 'vol mount' command. In addition, on all attached host systems, remount any T3 volumes that were unmounted in step 6. Special Install Instructions: ----------------------------- None. README -- Last modified date: Friday, June 8, 2001