Patch-ID# 112141-03 Keywords: l9 robotics firmware upgrade, tape library Synopsis: L9 robotics firmware upgrade Date: Feb/10/2005 Install Requirements: Additional instructions may be listed below Solaris Release: SunOS Release: Unbundled Product: Hardware/Tape Unbundled Release: N/A Xref: Topic: Relevant Architectures: BugId's fixed with this patch: Changes incorporated in this version: 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: L9-SUN-2-06S-dnld_all (1,572,864 bytes) L9-SUN-2-10S-dnld_all (1,736,704 bytes) L9-SUN-2-26S-dnld_all (1,769,472 bytes) L9-SUN-2-33S-dnld_all (1,736,704 bytes) L9-SUN-2-55S-dnld_all (1,867,776 bytes) L9-SUN-2-71S-dnld_all (1,966,080 bytes) README.112141-03 sgen.conf.example ( 2,899 bytes) tload ( 57,472 bytes) Problem Description: 1) Internet Browser compatibility issue fixes new dependency of SUN Java 1.4.1_01 or later runtime plug-in now required for various browser support with this product's Remote Management Card (RMC). 2) Added a Front panel 'emergency' unload capability for HP LTO drives. 3) Added 25 sweeps once/day to the hourly maintenance routine. The default time is 12:00 PM (Noon). The 25-sweep maintenance hour is configurable. This sweeping prevents any oxidation of the transport track surface. 4) Various Front Panel and RMC messages enhanced. 5) Various SCSI, Logging, Error Reporting and Downloading issues addressed. 6) Various Motion enhancements. (from 112141-02) 4736628 Firmware x.33 for L60 can prolong system boot up time. (from 112141-01) 4526533 2.33.S firmware for L9 is needed if a RMC card x-option is installed in a StorEdge L9 to stop "partial availability errors" related to firmware. NOTE: The firmware also needs to be updated in the L9 after any FRU is removed or replaced to assure that the library has the newest firmware possible. Patch Installation Instructions: -------------------------------- None. Special Install Instructions: ----------------------------- --------------------------------------------------------------------------- Instructions for Updating Firmware in the L9 Series -- RMC Method --------------------------------------------------------------------------- The following instructions explain how to, at a high level, upgrade the firmware in the L9 series of libraries. The firmware that gets updated is as follows: Picker/Translator Assembly Library Controller RMC (Remote Management Control) Card NOTE: The GUI interface may be a bit different depending on the firmware level present on the RMC card but most people should be able to follow the steps below and perform the upgrade. Before starting the upgrade procedure, assure that the RMC card is functioning properly and that an Administrator Password (done from front panel) is set up for the library. Also note the IP address for the library to be upgraded since the upgrade is done over the network by means of the host. If the RMC card is not available, see below: Instructions for Updating Firmware via SCSI Download Procedure -- tload Method. To upgrade the firmware, do the following: 1) Move the firmware files onto the directory-of-choice on the host. 2) Open the Mozilla browser and type in the IP address for the library in the Mozilla Location field. When the connection is made, you should see the the IP address followed by: main_id.html 3) During some upgrade installations, the NVRAM settings have been corrupted, before downloading the firmware, document the following information: * SCSI I.D. for Library and all drives * Admin password * Network settings 4) From the left column of choice, click on: Configuration 5) A sub-menu will open, then click on: Firmware Download 6) The Firmware Download page opens (Source Firmware File). Enter the location of the file or else click on Browse to find the file. Then click on the appropriate firmware file until it is highlighted and then click: OK Due to firmware dependencies, multiple firmware loads may be required or the unit may show partial availability. By rule: If 2.06S or 2.10S is currently loaded, first load 2.26S, then load 2.33S, then load 2.55S and finally load 2.71S. If 2.26S is loaded, first load 2.33S, then 2.55S, and finally load 2.71S. If 2.33S is loaded, first load 2.55S, and finally load 2.71S. If 2.55S is loaded, you may load 2.71S. 7) Check the Source Firmware File box and assure the driver file is there, then click: Start Download 8) If the Java Security windows open, click Grant. This is your way of giving permission to do the download. 9) When you are prompted for the Administration Password, enter the password in the field. 10) If the password is accurate and accepted, a Reboot Warning Message appears to assure it will be safe for the library to reboot automatically. NOTE: Assure that no backups or other important functions are occuring on the library. 11) The Download Monitor window appears and some messages are displayed, such as Flash Erase/Rewrite. Please note the Progress Monitor doesn't always stay current. The activity is also displayed on the front panel of the library. 12) The library does a power-on reset and the Download Status Window shows Completed. Close the download status and Mozilla browser windows. 13) Open a new Mozilla browser and type in the IP address for the library in the Mozilla Location field. When the connection is made, you should see the the IP address followed by: main_id.html 14) Making sure a connection is still available to the library as shown above, click on: Identify 15) The library will identify and show the latest loaded version of firmware. 16) From the left column of choice, click on: Status 17) A sub-menu will open, then click on: Overview 18) If the Drive Status is OK for all attached drives go on to step 24. 19) If drive status is: "No drives were detected" From the front panel of the L9, verify the SCSI IDs of the Library and Drives are the same as documented in Step 3. If they have changed, reset the original SCSI IDs. 20) Press the Shift key on the keyboard and click on the Mozilla browser window Reload Icon at the same time. This will reload the library information to the Mozilla browser window without taking the information from cache. 21) From the left column of choice, click on: Status 22) A sub-menu will open, then click on: Overview 23) Verify the Drive Status is OK for all attached drives. 24) Repeat steps 4 through 23 for all remaining firmware files as required in Step 6. When you click on: Identify, and the firmware version shows 2.71S, you have fully completed the upgrade procedure. --------------------------------------------------------------------------- Instructions for Updating Firmware via SCSI -- tload Method --------------------------------------------------------------------------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Contents -------- A.0 Solaris/Driver Requirements B.O Precautionary Statements C.O Patch Installation and Utility Usage Instructions ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A.0 Solaris/Driver Requirements ----------------------------------------------- Solaris 8 and later bundled with a uscsi compliant driver such as the 'sgen' driver is required for this procedure. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ B.0 Precautionary Statements ----------------------------- **WARNING:****WARNING:****WARNING:****WARNING:****WARNING:****WARNING:** B.1 The system MUST BE IDLE during the firmware download process! No other programs should be running while this utility is being used. Failure to do so may cause the devices being upgraded to fail or the system to crash. Any other computers sharing the same I/O bus as the host system must be either disconnected or offline. B.2 If any upgrade failures occur, do not continue upgrading devices. For example, loss of power during download will result in damaged peripherals and require replacement. If any failures occur, please collect the following log file: "/var/adm/messages", and an explorer dump. Please forward these files to your service provider for analysis. B.3 This package will only function on StorEdge L9 Tape Autoloaders. B.4 Please READ instructions below completely BEFORE starting download procedure. Follow the procedures carefully. You may program multiple autoloaders at the same time, however, you may not exit the utility until all autoloaders have completed the download process. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ C.O Patch Installation and Utility Usage Intructions ----------------------------------------------------- C.1 General guidelines for upgrading: EJECT MEDIA FROM DEVICE TO BE UPGRADED. Download utility will eject media from the device if it is found to be loaded. Do NOT attempt to force media back into the drive. STOP ALL APPLICATIONS. The system must be idle during the firmware upgrade process. DISCONNECT or take OFFLINE any other computers sharing the same I/O bus as the host. C.2 Firmware Dependencies and Download Order: Due to firmware dependencies, multiple firmware loads may be required or the unit may show partial availability. By rule: If 2.06S or 2.10S is currently loaded, first load 2.26S, then load 2.33S, then load 2.55S and finally load 2.71S. If 2.26S is loaded, first load 2.33S, then 2.55S, and finally load 2.71S. If 2.33S is loaded, first load 2.55S, and finally load 2.71S. If 2.55S is loaded, you may load 2.71S. In case of any disruption or unforeseen events happening on the relevant bus during the firmware download process, it may be that the upgraded device becomes non-functional. In this event, it will be necessary to replace the device. This would happen as a result of an incomplete or corrupted firmware file being downloaded. Loss of power during the upgrade process would also damage the device. **NOTE** If you cannot upgrade devices due to software application interference, try booting off of the Solaris release CD. **NOTE** After the firmware download is completed, it may be necessary to power cycle the device to ensure fully resetting the device. In turn, this may also require a successive reboot of the host system to ensure all functionality is restored. C.3 Procedure for L9 Tape Autoloader Firmware Download: The procedure to be used for upgrading the device's firmware is explained below. Total upgrade time will be approximately 10-15 minutes for each device. You must have root/super-user privileges in order to perform this operation. a). Ensure you are logged in as root on the machine attached to the L9 tape autoloaders you wish to upgrade. b). Unpack the patch (through tar) into any directory, e.g. /var/spool/patch (Note, if the patch ends in a ".Z" suffix, you will need to first uncompress it.) Example: # uncompress # tar xvf c). Modify the /kernel/drv/sgen.conf file so that the sgen target driver will have a device link allowing access to the L9 tape autoloader via a /dev/scsi/changer device link. SUGGESTED METHOD: ---------------- The sgen.conf.example file included with this patch may be utilized by first moving /kernel/drv/sgen.conf to /kernel/drv/sgen.conf.bak. Secondly, copy the included sgen.conf.example file to /kernel/drv/sgen.conf which supports tape library target (changer) devices operating on a parallel SCSI bus (SCSI target ID's 0-15 are supported). After completing this task, run: /usr/sbin/devfsadm -i sgen to create the /dev/scsi/changer/c#t#d# device link. MANUAL METHOD: ------------- Note: If you have used the SUGGESTED METHOD, skip to step C.2.d below in this section, else for manual sgen modifications: Refer to /kernel/drv/sgen.conf and/or the sgen man page for instructions on how to configure the sgen driver (included in Solaris 8 and later) to support tape library target (changer) devices operating on a parallel SCSI bus. First, copy /kernel/drv/sgen.conf to /kernel/drv/sgen.conf.bak to ensure preservation of the original sgen.conf file. Modify /kernel/drv/sgen.conf to enable sgen attach to tape library target (changer) devices operating on a parallel SCSI bus and enable the appropriate SCSI target ID(s) for your L9 tape autoloader(s). The following lines must exist in /kernel/drv/sgen.conf after modification: device-type-config-list="changer"; name="sgen" class="scsi" target=0 lun=0; where target= (target is set to SCSI ID 0 above). Uncomment the appropriate "name=..." lines to support your L9 tape autoloader SCSI target IDs. Do not modify the lun address as all L9 autoloaders use lun=0 in all cases. After completing this task, run: /usr/sbin/devfsadm -i sgen to create the /dev/scsi/changer/c#t#d# device link. d). In the patch directory, type the "tload" command to load the firmware: # ./tload L9-SUN-2-71S-dnld_all **NOTE** Do not rename the firmware filename or change it to lowercase characters. e). Select the device to be upgraded (see example below--the L9 tape autoloader corresponds to a Vendor ID of HP and Product ID of C7145-8000). f). Answer the question: Do you want to download firmware to this tape device [N]? with a 'y' for yes or anything else for no. Default answer is no. **NOTE** While the SCSI Controller firmware is downloading, the LCD on the autoloader will display various messages. It is good practice to monitor the LCD display while the download is occurring. g). If there is an additional device to be upgraded (same device type and desire to upgrade to the latest firmware), select that device as previously done in C.2.e). & C.2.f). above. Continue in this fashion until all desired devices have been upgraded. h). Quit the "tload" program by typing '0' (see example below). i). Repeat the above sequence of steps if you have had to make multiple firmware upgrades to bring the device to the latest firmware revision. j). After the device has been fully upgraded, the displayed tape device list will be refreshed. Device(s) upgraded should reflect having the new code level, "271S", in the "Rev" field (see example below). k). Upon completion of upgrading all L9 tape autoloaders, the user may move the /kernel/drv/sgen.conf.original file back to the original /kernel/drv/sgen.conf file thus restoring the original sgen configuration. ****************************************************************************** C.3 EXAMPLE # ######################################### # # Launch Tape Firmware Download Utility: # ######################################### # # ./tload L9-SUN-2-71S-dnld_all ATTACHED DEVICES: Device Supplier Product Rev Serial Number Device State -------------- -------- ---------------- ---- ------------- ------------- 1:0ln QUANTUM DLT8000 0258 PXB17P2902 Available 2:c5t5d0 HP C7145-8000 255S PRTN000054 Available Select Device(s) (ex: 1,3-4)0 to quit) [1]: 2 c5t5d0 HP C7145-8000 255S PRTN000054 Selected Do you want to download firmware to this device [N]? y ATTACHED DEVICES: Device Supplier Product Rev Serial Number Device State -------------- -------- ---------------- ---- ------------- ------------- 1:0ln QUANTUM DLT8000 0258 PXB17P2902 Available 2:c5t5d0 HP C7145-8000 255S PRTN000054 Downloading Downloading /dev/scsi/changer/c5t5d0... please wait. ATTACHED DEVICES: Device Supplier Product Rev Serial Number Device State -------------- -------- ---------------- ---- ------------- ------------- 1:0ln QUANTUM DLT8000 0258 PXB17P2902 Available 2:c5t5d0 HP C7145-8000 255S PRTN000054 Writing Flash Select Device(s) (ex: 1,3-4) or 0 to quit) [2]: 0 ATTACHED DEVICES: Device Supplier Product Rev Serial Number Device State -------------- -------- ---------------- ---- ------------- ------------- 1:0ln QUANTUM DLT8000 0258 PXB17P2902 Available 2:c5t5d0 HP C7145-8000 271S PRTN000054 F/W Upgraded # ######################################### # # The example above only upgrades one # device. You do not have to exit with # a "0" and initiate the 'tload' utility # again. You may continue instead and # directly upgrade the next tape device, # following the same steps as before # for each device until all devices # have been upgraded # ######################################### # # ######################################### # # After devices are upgraded, the Rev # will be 271S # ######################################### # # ######################################### # # To Quit, enter '0'. System prompt # will return. # ######################################### # ************************************************************************** ************************************************************************** C.4 tload (ABOUT THE UTILITY): tload - Firmware Download utility for tape drives. SYNOPSIS tload [ filename ] [ -v ] filename firmware/microcode filename DESCRIPTION tload is an firmware download utility for Sun supported tape devices. If the firmware_file is specified, then it will display the list of tape devices present on the host system and asks the user to select the tape device which is to be upgraded. If the firmware_file is not specified, then it will display the list of tape devices present on the host system along with their FIRMWARE revision levels. tload will exit upon completion; please do not attempt to halt or stop prior to utility's menu exit option being presented. The command can be run only as a super-user. DISCLAIMER This utility is ONLY supported for downloading, to Sun supported tape devices, the Sun supported firmware binary (firmware_file) which has officially been released via the official Sun Patch Process. This utility is only supported with the release of firmware (binary) bundled with said patch. Do not attempt to use any other version of 'tload' that may have been acquired previously else device damage may occur. Use only the version provided with this patch, version 4.1 (tload). Use of tload to load non-Sun supported tape devices is at the user's own risk, and is not supported. Use of tload to load Sun supported tape devices with firmware NOT bundled with the utility in an officially released Sun Patch is at the user's own risk, and is not supported. PROBLEMS Any problems regarding this utility by the user following proper procedures should be reported to the user's service provider along with the following items: 1) /var/adm/messages file 2) explorer dump 3) tload -v README -- Last modified date: Thursday, July 14, 2005