Patch-ID# 114704-02 Keywords: T3 T300 T310 raid storage firmware Synopsis: T3 IBM DDYT369_F65Y DDYT183_F65Y Firmware Update Date: May/02/2003 Install Requirements: See Special Install Instructions Solaris Release: 2.6 7 8 9 SunOS Release: 5.6 5.7 5.8 5.9 Unbundled Product: Hardware/Disk Unbundled Release: IBM_DDYST18350:DDYST36950_18-36GB_disks Xref: Topic: Relevant Architectures: sparc NOTE: This patch release is for the T3 Array only and T3+ Array only. BugId's fixed with this patch: 4811138 Changes incorporated in this version: 4811138 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: DDYT369_F65Y # 36 GB IBM T3 disk drive firmware patchtoc # t3.sh: Files to Upload To Target T3 previous/ # Recent T3 Firmware Versions t3.sh # T3 File Upload Utility DDYT183_F65Y # 18 GB IBM T3 disk drive firmware Problem Description: 4811138 IBM DDYFT3695SUN disk fails to reallocate bad block 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. 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 drive firmware 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. Manual File Installation ------------------------ -> Manually ftp the following files contained in this patch to the corresponding directory on the T3 system: Patch Source Location T3 Destination ------------------------- ------------------------ ./DDYT183_F65Y /DDYT183_F65Y ./DDYT369_F65Y /DDYT369_F65Y Automated File Installation --------------------------- 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 of the drive firmware 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. 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. Establish a telnet connection with the T3 (see T3 product documentation for specific details if necessary). Log into the system as 'root'. 2. 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. 3. 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. 4. 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. 5. 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 6. 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 uploaded (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, you have to install the patches for those drive firmwares individually. -> 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. *** EXAMPLE *** # This is a sample run of T3 patch installation hoohoo/usr/PATCHES/TEST/fwpatch_1.0/T3-PATCH-DEV/114704-02.test>./t3.sh Please Enter Hostname or IP Address Of T3 To Be Ugpraded: 10.4.41.226 10.4.41.226 is alive Please Enter Patch Location Pathname [.]: Looking For Patch Contents In [.]... ----------------- ./patchtoc ------------------- S173404_AA27 image located Enter Your Home Directory Path [/]: Enter ftp user root Enter ftp password test Creating Auto ftp File In [//.netrc]... Invoking ftp Connected to 10.4.41.226. 220 10.4.41.226 T300 FTP server ready. 331 Password required for root. 230 User root logged in. bin 200 Type set to I. prompt Interactive mode off. cd / 250 CWD command successful. lcd /tmp/upload.21121 Local directory now /tmp/upload.21121 put S173404_AA27 200 PORT command successful. 150 Opening BINARY mode data connection for S173404_AA27 226 Transfer complete. local: S173404_AA27 remote: S173404_AA27 570496 bytes sent in 23 seconds (24.02 Kbytes/s) quit 221 Goodbye. Cleaning Up Temporary Files... hoohoo/usr/PATCHES/TEST/fwpatch_1.0/T3-PATCH-DEV/114704-02.test> hoohoo/usr/PATCHES/TEST/fwpatch_1.0/T3-PATCH-DEV/114704-02.test> hoohoo/usr/PATCHES/TEST/fwpatch_1.0/T3-PATCH-DEV/114704-02.test>telnet 10.4.41.226 Trying 10.4.41.226... Connected to 10.4.41.226. Escape character is '^]'. pSOSystem (10.4.41.226) Login: root Password: T300 Release 1.18.00 2001/11/16 13:35:09 (10.4.41.226) Copyright (C) 1997-2001 Sun Microsystems, Inc. All Rights Reserved. qatest:/:<1> qatest:/:<1>ls -l S173404_AA27 -rwxrwxrwx 1 root 570496 Apr 06 2003 01:13 S173404_AA27 qatest:/:<2> qatest:/:<2>disk download u1d2 S173404_AA27 pass qatest:/:<3> qatest:/:<3>fru list u1d2 ID TYPE VENDOR MODEL REVISION SERIAL ------ ----------------- ----------- ----------- ------------- -------- u1d2 disk drive SEAGATE ST173404FSUN AA27 3CE028YS qatest:/:<4> qatest:/:<4> qatest:/:<4>exit Connection closed by foreign host. *** END EXAMPLE *** Special Install Instructions: ------------------------------------------- None. README -- Last modified date: Friday, May 2, 2003