OBSOLETE Patch-ID# 111175-02 Keywords: point patch T3 1.16d T300 T310 raid storage firmware loopcard eprom interconnect Synopsis: Obsoleted by: 109115-07 T3 1.16d: 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.16d Xref: Topic: Relevant Architectures: sparc NOTE: 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. 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 patchtoc # t3.sh reference:Files to Upload To Target T3 t3.sh # T3 File Upload Utility nb116d.bin # Controller firmware Problem Description: ------------------------------------------------------------------- 111175-02 (1.16d Point Patch Release) + Disk Drive Firmware Update ------------------------------------------------------------------- 4411125 Seagate Cheetah 4 Drive Firmware Update ----------------------------------------------- 111175-01 (1.16d Firmware Point Patch Release) ----------------------------------------------- 4426777: slowly degrading drives don't get disabled by T3 4406749: Lun reconstruction very slow during light IO 4386836: Drive firmware download can hang Note: In addition to the above three bug fixes, this point patch accumulates and obsoletes 1.16a and 1.16c level firmware. 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 this patch to the corresponding directory on the T3 system: Patch Source Location T3 Destination ------------------------- ------------------------ ./ep2_10.bin /ep2_10.bin ./lpc_05.02 /lpc_05.02 ./nb116c.bin /nb116c.bin (From temporary Working Directory) ./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 nb116d.bin file header: size 251650, checksum 6d33c6dd, 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.16d 2001/03/09 16:20:02 (129.150.47.164) Copyright (C) 1997-2001 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