README: 1.5 TB Half High LTO-5 Tape Drive Microcode

Table of Contents

README: 1.5 TB Half High LTO-5 Tape Drive Microcode

Drive SELF-TEST Procedure

Readme Change History

README: 1.5 TB Half High LTO-5 Tape Drive Microcode

SAS Feature Code: 5638, 8247, 8241

5638 - Feature code for internal SAS HHLTO5 drive
8247 - Old feature code for SAS HHLTO5 in 7226 enclosure
8241 - New feature code for SAS HHLTO5 in 7226 enclosure

SAS Current Version: G9N1

Fibre Channel Feature Code: 8248

Fibre Channel Current Version: G9N1

Date: December 14, 2016

General information

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

This package is being provided to allow the update of 1.5TB Half High LTO-5 Tape Drive Microcode Tape Drives to the latest level of microcode that is currently shipping from IBM.

Users are responsible to install the latest microcode level.
The microcode and instructions are available at the IBM external web site:
http://www.ibm.com/support/fixcentral

Operating System levels supported:

All levels of AIX that this product was announced on.

Installation Time:

The typical time to install this microcode is .2 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 diagnostics.
The AIX diagnostic package will need the microcode and dsdata files in this package.

Note: Atape does not require the dsdata file.
This tape drive package will get you to step where you will need to use the AIX Diagnostics.

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 Power Systems 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.

SAS Feature Code: 5638, 8247, 8241

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 1.5TB Half High LTO-5 tape drive do the following AIX command:

 lscfg -vl rmt0               <--- change the drive number to reflect
                                   the actual rmt address of the 1.5TB
                                   Half High LTO-5 tape drive.

The output of the lscfg command will look like the following with the:

• "Device Specific.(Z1)" showing the "Microcode Level":
  As of October 2011 there are 2 different P/Ns for the LTO5 drive. The drives are functionally equivalent and are fully interchangeable.

  rmt0             U789C.001.DQDA282-P2-D1  SAS 1/2-inch Cartridge Tape
Drive (1500000 MB)
 
        Manufacturer................IBM
        Machine Type and Model......HH LTO Gen 5
        Device Specific.(Z1)........G9N1
        Serial Number...............68000948
        Load ID.....................A1700D77
        Part Number.................46C2006
        FRU Number..................46C2007
        EC Level....................M10843
        Device Specific.(Z0)........0180060283001002
        Device Specific.(Z3)........N1

or

  rmt0             U789C.001.DQDA282-P2-D1  SAS 1/2-inch Cartridge Tape
Drive (1500000 MB)
 
        Manufacturer................IBM
        Machine Type and Model......HH LTO Gen 5
        Device Specific.(Z1)........G9N1
        Serial Number...............68003223
        Load ID.....................A1700D77
        Part Number.................46X5681
        FRU Number..................46X5683
        EC Level....................M11484
        Device Specific.(Z0)........0180060283011002
        Device Specific.(Z3)........N1

Microcode History

The microcode update will bring the IBM 1.5TB Half High LTO5 SAS tape drive up to the current level of microcode which is:
G9N1

Table 1. Microcode History

Tape Drive P/N	Tape Drive FRU P/N	Microcode Level	Load ID	Date Released	What does this microcode change
46C2006	46C2007	A6S1	A1700D77	Sept 17, 2010	First Microcode level shipped.
46C2006	46C2007	A9Q4	A1700D77	Nov 15, 2010	Enhancements for preventing stuck tape. Enhancements to internal trace. Fix to encryption LED operation. Channel enhancements. Wait longer for the SAS calibration to complete during connectivity.
46C2006	46C2007	B174	A1700D77	March 20, 2011	Enhancements for sticky/stuck tape conditions Enhancements for internal drive tracing and internal logging. Ethernet implementation Internal code enhancements. Fixed to prevent write protect error when the drive was in sleep mode. Fixed to prevent head stick during shipping Fixed incompatible medium to report correct ASQ/ASCQ
46X5681 46C2006	46X5683 46C2007	B6W1	A1700D77	August 29, 2011	Fix another cause of stuck tape. Read/Write Channel enhancements
46X5681 46C2006	46X5683 46C2007	BBNM	A1700D77	April 15, 2012	If a bezel door get stuck above the internal carrier the drive will try a recovery procedure to unstick the door. Fix for threader not stopping at parked position at MTR in some instances: FSC 2E05, 2E08, 2E0C, 2E16 Fix for some causes of the tape coming off the spool. Fix for FSC 2E0C - This can cause a stuck tape. Enhancement for servo related failures: FSCs 78XX related to PES acquire Improve velocity stall detection
46X5681 46C2006	46X5683 46C2007	C7RD	A1700D77	October 25, 2012	Fix: LTO5 HH drive could see problems reading LTO3 media on code after B6W1 Fix for a drive time out during Write operations Fix Unexpected bus reset can be seen as lost resource at the customer
46X5681 46C2006	46X5683 46C2007	D2AD	A1700D77	June 25, 2013	Fix for SAS Hang - seen as timeout Internal RW Channel enhancements Fix cartridge load issue Fix for possible head position issue at unload of tape.
46X5681 46C2006	46X5683 46C2007	D8D5	A1700D77	October 4, 2013	Fix for a read command timeouteout Enhancement for servo acquire and tracking Fix for drive been in unloading status for a long time Improvements to avoid Cartridge Memory update failure unload of tape.
46X5681 46C2006	46X5683 46C2007	E4J1	A1700D77	May 28, 2014	Complete eject wasn't performed after power resume Race condition caused unload not to execute Cmd hang on unload during write flush ERP improvements for FSC 7067 write perms Check if need to invoke a head brush action when entering sleep mode
46X5681 46C2006	46X5683 46C2007	F991	A1700D77	Dec 2, 2015	Fix CM read/write problem; Fix servo amplitude check. Performance degradation (cannot change from speed 14); Panic when entering power down mode (inconsistent power amp); False EOT shutdown detection after tension shutdown; Diag fails with Wrt Protect err if sleep mode; Fix drive head Go To Home Error on HH drives; Fix BOT run off if false detect of BOT in MTR.
46X5681 46C2006	46X5683 46C2007	G361	A1700D77	Jun 12, 2016	Fix MLOI block handling on Writes Fix load hold flush behavior panic due to overlapping flush requests UNLOAD should return GOOD status when cart already ejected fix wrong handling of echo buffer LocBot status not suppressed correctly on rewind FSC 2E0D on HH drives (due to velocity unstability) BFF4 panic due to aborted Write commands Fix Ldr Blk park position after Idle Mode Unload
46X5681 46C2006	46X5683 46C2007	G9N1	A1700D77	December 12, 2016	Fix queue hang after abort Calibration hang Fix SAS Hard Reset write state cleanup 2E0C false detection on thread Segment handling for dup dsnum at wrapturn FSC 78B0 improvement (over rotation at stoplock) Correct FELO/FULO during media read Panic due to extra call to complete function

Fibre Channel Feature Code: 8248

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 1.5TB Half High LTO5 Fibre Channel tape drive do the following AIX command:

 lscfg -vl rmt0               <--- change the drive number to reflect
                                   the actual rmt address of the 1.5TB
                                   Half High LTO-5 tape drive.

The output of the lscfg command will look like the following with the:

• "Device Specific.(FW)" showing the "Microcode Level":
  As of October 2011 there are 2 different P/Ns for the LTO5 drive. The drives are functionally equivalent and are fully interchangeable.

 rmt0             U789C.001.DQDA282-P1-C3-T1-W500507631249F9FF-L0  IBM
3580 Ultrium Tape Drive (FCP)
 
        Manufacturer................IBM
        Machine Type and Model......ULT3580-HH5
        Serial Number...............1068017781
        Device Specific.(FW)........G9N1
 

Microcode History

The microcode update will bring the IBM 1.5TB Half High LTO5 Fibre Channel tape drive up to the current level of microcode which is:
G9N1

Table 2. Microcode History

Tape Drive P/N	Tape Drive FRU P/N	Microcode Level	Load ID	Date Released	What does this microcode change
95P7970	95P7981	B6W1	None	March 18, 2012	First Microcode level shipped.
95P7970	95P7981	BBNM	None	April 15, 2012	If a bezel door get stuck above the internal carrier the drive will try a recovery procedure to unstick the door. Fix for threader not stopping at parked position at MTR in some instances: FSC 2E05, 2E08, 2E0C, 2E16 Fix for some causes of the tape coming off the spool. Fix for FSC 2E0C - This can cause a stuck tape. Enhancement for servo related failures: FSCs 78XX related to PES acquire Improve velocity stall detection
95P7970 35P3075	95P7981 35P3077	C7RD	None	October 25, 2012	Add new RoHS compliant Drive P/N 35P3075, FRU P/N 35P3077 Fix: LTO5 HH drive could see problems reading LTO3 media on code after B6W1 Fix for a drive time out during Write operations Fix Unexpected bus reset can be seen as lost resource at the customer
95P7970 35P3075	95P7981 35P3077	D5AD	None	June 25, 2013	Fix for SAS Hang - seen as timeout Internal RW Channel enhancements Fix cartridge load issue Fix for possible head position issue at unload of tape.
95P7970 35P3075	95P7981 35P3077	D8D5	None	October 4, 2013	Fix for a read command timeouteout Enhancement for servo acquire and tracking Fix for drive been in unloading status for a long time Improvements to avoid Cartridge Memory update failure unload of tape.
95P7970 35P3075	95P7981 35P3077	E4J1	None	May 28, 2014	Complete eject wasn't performed after power resume Race condition caused unload not to execute Cmd hang on unload during write flush ERP improvements for FSC 7067 write perms Check if need to invoke a head brush action when entering sleep mode
95P7970 35P3075	95P7981 35P3077	F991	None	Dec 2, 2015	Fix CM read/write problem; Fix servo amplitude check. Performance degradation (cannot change from speed 14); Panic when entering power down mode (inconsistent power amp); False EOT shutdown detection after tension shutdown; Diag fails with Wrt Protect err if sleep mode; Fix drive head Go To Home Error on HH drives; Fix BOT run off if false detect of BOT in MTR.
95P7970 35P3075	95P7981 35P3077	G361	None	Jun 12, 2016	Fix MLOI block handling on Writes Fix load hold flush behavior panic due to overlapping flush requests UNLOAD should return GOOD status when cart already ejected fix wrong handling of echo buffer LocBot status not suppressed correctly on rewind FSC 2E0D on HH drives (due to velocity unstability) BFF4 panic due to aborted Write commands Fix Ldr Blk park position after Idle Mode Unload
95P7970 35P3075	95P7981 35P3077	G9N1	None	December 12, 2016	Fix queue hang after abort Calibration hang Fix SAS Hard Reset write state cleanup 2E0C false detection on thread Segment handling for dup dsnum at wrapturn FSC 78B0 improvement (over rotation at stoplock) Correct FELO/FULO during media read Panic due to extra call to complete function

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.

• If the user downloads the 13 HHLTO5.bin file the user will put the downloaded file into the /tmp directory and then use the instructions in the section of this README titled "AIX bin file".
• If the user downloads the TapeHHLTO5-G9N1-01.rpm file the user will put the downloaded file into the /tmp directory and then use the instructions in the section of this README titled "RPM file".

From a CD-ROM.

• If the CD-ROM process is used to put the HHLTO5.bin file on the user system the microcode files will expanded into the /tmp/LTO5_web directory. The next step is to follow the instructions in this README titled "AIX bin file" and copy the files to the appropriate directory. The building and putting of the files into the /tmp/LTO5_web directory was done by the user when they used the CD-ROM build instructions.
• If the CD-ROM process is used to put the TapeHHLTO5-G9N1-01.rpm file on the user system the microcode files will be in the tmp/microcode/RPM directory. To put the microcode in the appropriate directory for the system the user executes the following AIX commands:
  cd /tmp/microcode/RPM
  rpm -ihv --ignoreos TapeHHLTO5-G9N1-01.rpm (add --force if previous rpm package installed and get conflict error)
  This puts the following files in the /etc/microcode directory for system use:
  • HH_LTO_Gen_5.A1700D77.dsdata
  • HH_LTO_Gen_5.A1700D77.G9N1
  • HH_LTO_Gen_5.FC.G9N1
  The next step is to follow the instructions in this README titled "Verifying the Microcode".

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

• Download the HHLTO5.bin file to the eServer pSeries to the /tmp directory.
• Do the following AIX commands to make the file executable:
  cd /tmp
  chmod +x HHLTO5.bin
• To expand the HHLTO5.bin file use the following command:
  ./HHLTO5.bin

  Note: The ./ before the command insures AIX paths thru the current directory to find the command.

• This will put the following files in the /tmp/LTO5_web directory:
  • HH_LTO_Gen_5.A1700D77.dsdata
  • HH_LTO_Gen_5.A1700D77.G9N1
  • HH_LTO_Gen_5.FC.G9N1

RPM file

• Download the TapeHHLTO5-G9N1-01.rpm file to the eServer pSeries to the /tmp directory.
• To expand the TapeHHLTO5-G9N1-01.rpm file use the following commands:
  cd /tmp
  rpm -ihv --ignoreos TapeHHLTO5-G9N1-01.rpm
• This will put the following files in the /etc/microcode directory:
  • HH_LTO_Gen_5.A1700D77.dsdata
  • HH_LTO_Gen_5.A1700D77.G9N1
  • HH_LTO_Gen_5.FC.G9N1

Verifying the Microcode

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

• Change to the directory where you just put the microcode.
  cd /tmp/LTO5_web
  or
  cd /etc/microcode
• Use the AIX command sum to verify the checksum of the microcode file:
  sum HH_LTO*
• Compare the sum you got with the sum of the microcode files here, if they do not match recheck your steps in creating the file on the system:
  

  34189  5047 HH_LTO_Gen_5.A1700D77.G9N1
  63839     2 HH_LTO_Gen_5.A1700D77.dsdata
  19374  5124 HH_LTO_Gen_5.FC.G9N1
  

Updating the microcode in the drive

You need to determine how you are going to download the microcode:

• AIX diagnostics.

AIX diagnostics naming and supported directory for the microcode and dsdata file.

• AIX diagnostics requires the microcode file and the dsdata file to be in the /etc/microcode directory.
• For Atape it is not necessary to copy the files to another directory. Atape can use any directory. Use the /tmp/LTO5_web 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/LTO5_web
 
cp HH_LTO_Gen_5.A1700D77.dsdata /etc/microcode/.
 
cp HH_LTO_Gen_5.A1700D77.G9N1   /etc/microcode/.

To use AIX Diagnostics Microcode download

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

• Using the AIX Diagnostics menu
• Using the AIX Diagnostics via command line input.

Using the AIX Diagnostics menu

To use the AIX Diagnostics menu for microcode download do the following:

Note: There are differences between AIX levels of AIX Diagnostics. In some cases the step after Task selection is Microcode Tools, or Download Microcode. The following steps are general instructions to download microcode.
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

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 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.

Note: If the microcode download fails install:

• Insure the checksum is correct for the files that you have downloaded
• If the download to the tape drive fails, use the eject button on the tape drive to reset the drive. Some microcode download failures leave the drive in way that the tape drive will not complete a download without the tape drive being reset.
  To reset the tape drive press the eject button and hold the eject button pressed in for 15 seconds, this will cause a drive reset.

To Update the Microcode on IBM i System

Please follow the instructions in the following link to update the tape drive firmware under IBM i system:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Removable%20Media%20on%20IBM%20i/page/Updating%20firmware%20on%20selected%20stand%20alone%20drives

Use Atape to update the Fibre Channel Drive Only.

Note: Atape must be installed on the system prior to running AIX diagnostics.

Enter AIX diagnostics and select "Task Selection"
Select "IBM Tape Drive Service Aids"
Select "Microcode load" and fill in the required fields.

Note: The microcode file used by Atape for the Fibre Channel LTO5 tape drive is:
/tmp/LTO5_web/HH_LTO_Gen_5.FC.G9N1

Drive SELF-TEST Procedure

Description

The following procedure is designed to allow you to quickly perform a complete set of diagnostic tests on your Half High LTO-5 tape drive, without impacting server operation. This 5 < minute test can also be used to verify good performance of individual LTO5 tape cartridges.

Enter Diagnostic Mode:

• Verify that a tape cartridge is not loaded in drive.

  To unload a cartridge, press the eject button on the front of the drive.

• To Start Drive SELF-TEST:

  Press and hold the eject button for more than 6 seconds, and less than 20 seconds(at 20 seconds the drive will do a manual reset and not run the full drive self test), release the button. The Ready LED will continue flashing, indicating that the drive is waiting for a cartridge to be inserted.The drive will wait up to 15 seconds for a cartridge to be inserted. If no cartridge is inserted the drive will exit self test.

Running the Self-Test:

• Start the self-test by inserting IBM Test Tape P/N 45E1129 into the drive. If an IBM Test Tape is not available, you can substitute a scratch (blank) LTO5 data cartridge.

  Note:
  Important!
  Use a blank cartridge that does not contain customer data. During this self-test, the cartridge will be rewritten with a test pattern and any customer data will be destroyed.

  Overall test duration is about 5 < minutes.

  Note:

  • A cartridge must be loaded within 15 seconds -- otherwise, the drive will automatically revert back to normal operation. If necessary, return to step 1 to reenter diagnostic mode.
  • Use a cartridge that is not write-protected. If a write-protected cartridge is inserted while the drive is in diagnostic mode, the cartridge will be ejected -- see step below.
  • Self-testing can only be performed using a write-compatible cartridge type, and with a cartridge that is not damaged -- see step below.
  • If a cleaning cartridge is inserted while the drive is in diagnostic mode, cleaning will occur and the drive will then return to normal operating mode. To reenter diagnostic mode, return to the "Enter Diagnostic Mode" step.
• At any time, self-testing can be stopped by pressing the eject button. After a current test operation is completed, the cartridge will be ejected and drive will return to normal operation.
• While self-testing is in progress, the Ready LED will continue to flash. The following 3 test steps are performed:
  • The initialization sequence has an approximate duration of 20 seconds. The Activity LED indicates tape movement.
  • The hardware test has an approximate duration of 2 minutes. During that time, a static test is performed on the drive's electrical components, and proper operation of the cartridge load/unload mechanism is verified.
  • The write/read test has an approximate duration of 3 minutes. The Activity LED indicates tape movement.

Interpreting the Results:

Test Passed:

When self-testing has completed successfully and no problems were detected, the cartridge is unloaded from the drive and all LEDs and SCD are off. Proper function of both the drive and tape cartridge have been verified.

Note: When the Amber Clean LED remains on, it indicates that self-testing has completed successfully -- but cleaning is required. Clean the drive by inserting an IBM Cleaning Cartridge (P/N 35L2086).

The drive is no longer in diagnostic mode, and has been returned to normal operation.

Drive Failure:

When a drive problem is detected, the cartridge will remain loaded inside the drive and the Amber Fault LED ( ! ) will flash.

Following a self-test failure, the tape cartridge will remain loaded inside drive, and the drive will remain in diagnostic mode. Press the eject button to unload tape cartridge and return drive to normal operation.

Repeat self-test using another tape cartridge, If the test passes replace any defective media.

If the test again failed contact IBM Service for assistance.

Media Failure:

When a media problem is detected, the cartridge will remain loaded inside the drive, and the Amber Clean LED will flash.

Repeat self-test using another tape cartridge, and replace any defective media.

Incorrect cartridge:

When the drive has determined that an incorrect tape cartridge was inserted, the cartridge is unloaded and both the Activity and Clean LEDs will flash. Self-testing cannot be performed if the inserted cartridge is one of the following:

• Write-protected
• Damaged
• Media type that is not write-compatible with the drive

Press the eject button, to end self-test and return the drive to normal operating mode. Then return to step 1 and run the self-test using a suitable cartridge.

Return to Normal Operation:

Following a self-test failure, the tape cartridge will remain loaded inside drive, and the drive will remain in diagnostic mode. Press the eject button to unload tape cartridge and return drive to normal operation.

Readme Change History

Table 3. Readme Change History

Date Changed	What does this change
May 28, 2014	Update for E4J1 FW release
Oct 9, 2014	Update for adding SAS feature code 8247, 8241
Jul 30, 2015	Update for adding firmware update instructions for IBMi
Dec 2, 2015	Update for F991 FW release
Jun 12, 2016	Update for G361 FW release

Jun 12, 2016

• Update for G9N1 FW release