README: 200GB LTO-2 Tape Drive Microcode


Table of Contents

README: 200GB LTO-2 Tape Drive Microcode

  • Date: May 5, 2006
  • Version: 0218
  • General information
  • Operating System levels supported:
  • Installation Time:
  • Can microcode be installed Concurrently?
  • Is system reboot needed to activate the microcode
  • Microcode Download information:
  • Additional Cautions
  • Machines Affected:
  • Microcode History
  • Feature Code 5755
  • Feature Code 1997
  • Display Microcode Level
  • Putting the microcode on the system
  • From the IBM WEB site via the user downloading the files.
  • From a CD-ROM.
  • Packaged Microcode Files
  • AIX bin file
  • RPM file
  • Verifying the Microcode
  • Updating the microcode in the drive
  • Copy Dsdata and Microcode to appropriate directory
  • To use AIX Diagnostics

  • README: 200GB LTO-2 Tape Drive Microcode

    Date: May 5, 2006

    Version: 0218

    This is the level of microcode shipped in the drive when the drive was announced.

    There is no microcode included in this package as the drive already has this microcode in the drive.

    This package is here as an informational reference only.


    General information

    ******* Please read this entire notice *********

    This package is being provided to allow the update of older 200GB LTO-2 Tape Drive Microcode Tape Drives to the latest level of microcode that is currently shipping from IBM.

    Users are encouraged to install the latest microcode level themselves. The microcode and instructions are available at the IBM external web site:
    download.html


    Operating System levels supported:

    All levels of AIX that this product was announced on.


    Installation Time:

    The typical time to install this microcode is .3 hrs.
    The microcode becomes active when installed and does not require a system reboot to become active.


    Can microcode be installed Concurrently?

    Yes, but the tape drive must be available with no tape in the drive, and no other processing running to the tape drive.


    Is system reboot needed to activate the microcode

    A reboot is not needed as the microcode is active in the drive when the drive completes microcode download.


    Microcode Download information:

    In order to complete the microcode download to the tape drive you will need to use the AIX 5.1 diagnostics and higher, For the AIX diagnostic package you will need the microcode and dsdata files in this package.
    This tape drive package will get you to step where you will need to use the AIX 5.1 and higher Diagnostics to download the microcode into the tape drive.


    Additional Cautions

    Remove any tape cartridge from the drive prior to attempting the microcode download.
    Do not power off the tape drive during microcode download as this may damage the tape drive microcode requiring the tape drive to be replaced.


    Machines Affected:

    All pSeries machines this product was announce on. In general if the tape drive configures and is available with the VPD showing the Machine Type and microcode level as described in this README the machine is one affected.


    Microcode History

    The microcode update will bring the IBM 200GB LTO-2 tape drive up to the current level of microcode which is:
    0218

    Feature Code 5755


    Table 1. Microcode History
    Tape Drive P/N Tape Drive FRU P/N Microcode Level Load ID What does this microcode change

    96P1773
    23R3247
    96P1775
    23R3248
    0218 A1700D54 First Microcode level shipped.

    Feature Code 1997


    Table 2. Microcode History
    Tape Drive P/N Tape Drive FRU P/N Microcode Level Load ID What does this microcode change

    96P1776 96P1777 0218 A1700D5A First Microcode level shipped.


    Display Microcode Level

    Note: In some cases you may already have the most current level of microcode already installed. The following instructions show you how to check the tape drive microcode level.

    To display the level of microcode in the IBM 7206-220 or the internal 200GB LTO-2 tape drive do the following AIX command:

     lscfg -vl rmt0               <--- change the drive number to reflect
                                       the actual rmt address of the 200GB
                                       LTO-2 tape drive.
    

    The output of the lscfg command will look like the following with the "Device Specific.(Z1)" showing the microcode level:

    Feature Code 5755

    rmt0         P1/Z1-A8  LVD SCSI 1/2-inch Cartridge Tape Drive (200000 MB)
     
            Manufacturer................IBM
            Machine Type and Model......HH LTO Gen 2
            Device Specific.(Z1)........0218
            Serial Number...............2000006A
            Device Specific.(LI)........A1700D54
            Part Number.................96P1773
            FRU Number..................96P1775
            EC Level....................H81465
            Device Specific.(Z0)........0180030283000130
            Device Specific.(Z3)........N1
    

    Feature Code 1977

    rmt1       P1/Z1-A2  LVD SCSI 1/2-inch Cartridge Tape Drive (200000 MB)
     
          Manufacturer................IBM
          Machine Type and Model......HH LTO Gen 2  H0
          Device Specific.(Z1)........0218
          Serial Number...............25000092
          Device Specific.(LI)........A1700D5A
          Part Number.................23R3247
          FRU Number..................23R3248
          EC Level....................H81465
          Device Specific.(Z0)........0180030283000130
          Device Specific.(Z3)........N1
    


    Putting the microcode on the system

    There are 2 ways a user can get the microcode files. Each of these will put the microcode on the user's system but the user may have to move the files to appropriate directory for system use.

    From the IBM WEB site via the user downloading the files.

    When the user downloads the microcode files from the IBM web site the packaged microcode files will be put into the /tmp directory.

    From a CD-ROM.

    Note: AIX commands and file names are case sensitive.
    If the users AIX permission does not allow the copy to the above stated directory or file then the user will be prompted for a new location.


    Packaged Microcode Files

    AIX bin file

    RPM file


    Verifying the Microcode

    To insure the file was downloaded without error do the following:


    Updating the microcode in the drive

    AIX diagnostics requires the microcode file and the dsdata file to be in the /etc/microcode directory.

    Copy Dsdata and Microcode to appropriate directory

    Copy the Dsdata and Microcode files to appropriate directory for use by AIX diagnostics.

    Note: The copy command copies the file to the new directory with the same name when you use the period(.) after new directory name.

    For AIX Diagnostics

    If you downloaded the RPM file and executed it the microcode is in the correct directory with the correct name for AIX diagnostic use.
    If you downloaded the .bin file and executed it then you need to do the following AIX commands:

    cd /tmp/LTO_web
     
    cp LTO-2.A1700D54.dsdata /etc/microcode/.
     
    cp LTO-2.A1700D54.0218   /etc/microcode/.
     
    cp LTO-2.A1700D5A.dsdata /etc/microcode/.
     
    cp LTO-2.A1700D5A.0218   /etc/microcode/.
    

    To use AIX Diagnostics

    There are 2 ways to do the microcode download using the AIX diagnostics.

    Using the AIX Diagnostics menu

    To use the AIX 5.1 diagnostics menu for microcode download do the following:  
    diag (enter)  
    Task Selection (enter)  
    Download Microcode (enter)

    Select the drive you wish to download microcode to and follow the system instructions.

    Note: When the system asks where the microcode file is to be found select /etc/microcode, not diskette.

    Using the AIX Diagnostics via command line input.

    The command line to download microcode will use the highest level of microcode in the /etc/microcode directory for the device selected. To use the AIX 5.1 diagnostics command line input for microcode download do the following:

    Note: If the previous level of microcode is not in the /etc/microcode directory you will need to use the -f option(force) as the diagnostics expect the previous level to be present in the /etc/microcode directory.  
    diag -c -d rmt0 -T "download" (enter)

    or

    diag -c -d rmt0 -T "download -f" (enter)