README: 80GB VXA-2 Tape Drive Microcode

Table of Contents

README: 80GB VXA-2 Tape Drive Microcode

Drive SELF-TEST Procedure

README: 80GB VXA-2 Tape Drive Microcode

Date: August 28, 2008

Version: 2152

General information

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

This package is being provided to allow the update of older 80GB VXA-2 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 themselves. The microcode and instructions are available at the IBM external web site:
http://www14.software.ibm.com/webapp/set2/firmware/gjsn

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.
If the microcode install is done with Genucode the tape drive Vital Product Data(VPD) will not show the new microcode level until you use the AIX rmdev and mkdev commands to remove and add back the tape drive.

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, or the Genucode program. If the system does not have the AIX 5.1, or later, diagnostics you will need to get the Genucode package from the WEB.
For both the AIX diagnostic package or for Genucode 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 or Genucode 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 and RS/6000 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 80GB VXA-2 tape drive up to the current level of microcode which is:
2152

Table 1. Microcode History

Tape Drive P/N	Tape Drive FRU P/N	Microcode Level	Load ID	What does this microcode change
19P4897	19P4898	1000	A170029C	First Microcode level shipped.
19P4897	19P4898	1003	A170029C	Reduced tape path loading tension. Turn on cleaning indication when media damage is suspected. Increase use of internal cleaning wheel. Correct electronic SCSI Chip switch from DVD to SE.
19P4897	19P4898	1005	A170029C	Changes the manufacturer name from Exabyte to IBM in the vital product data. No actual change in manufacturer. Reduces the space required for the filemark and setmark. Improved Read Buffer Command Data collection used in problem determination. Retry of stuck cartridge unload during cartridge unload operation.
19P4897	19P4898	1009	A170029C	Provide iSeries support. Correct false broken tape indication. Improve tape handling in the vertical position when the drive is powered off during high speed tape operation. Change the reporting of hardware error to report a media error. Fault Symptom Code(FSC) 19, 1D, 3D, 58, 5A will generate SenseKey 03 instead of 04. Software calibration to reduce media errors.
19P4897	19P4898	100C	A170029C	Correct handling of mixing of SCSI commands to non existent Logical Unit Numbers(LUNs) on the tape drive and simultaneous other SCSI commands to the drive. Correct for TAPE_ERR1 when the system activity to other areas causes data delivery to the tape drive to be slow.
19P4897	19P4898	100E	A170029C	Use "Active Negation" when the tape drive operates in Single Ended(SE) mode. This may reduce the chance of SCSI errors on very active SCSI bus. Correct for TAPE_ERR1 when the system activity to other areas causes data delivery to the tape drive to be slow.
19P4897	19P4898	2104	A170029C	Motion recovery change for tape stuck on stationary portion of drum during tape path unload. Improved drum spin up to prevent tape to be pulled out of supply reel side of cartridge Improved zero length write buffer command handling. Correct intermittent write protect indication during write operation. Enhanced broken tape handling. Cartridge eject failure - error indication enhancement. Snug tape during Emergency tape path unload. Enhanced end of tape handling. Enhanced SCSI ID control for Autoloader use. Enhanced SCSI LUN query handling.
19P4897 24R1988	19P4898 24R1989	2105	A170029C A1700D58	Provide support for new "X" media. The "X6" and "X10" media require a minimum microcode level of "2105" for proper end of tape handling and tape speed. Release of new drive P/N 24R1988 and FRU P/N 24R1989 Note: The tape drive microcode is for the tape drive Part Number and Device Specific(LI) combination. Use the specific microcode file that corresponds to the tape drive Part Number and Device Specific(LI) combination.
19P4897 24R1988	19P4898 24R1989	2107	A170029C A1700D58	Retry for cartridges that get stuck behind the tape drive door, the drive will reload the cartridge and then retry ejecting it. Randomize load position. Previously the drive would always load the tape in the same position putting more wear on that particular spot on the tape. This microcode randomizes this operation to spread the wear more evenly over the load part of the tape. Enhanced end of tape handling. Enhanced handling of blank(unused) tapes.
19P4897 95P1870 24R1988 96P1771	19P4898 95P1871 24R1989 96P1772	210A	A170029C A1700D58	Reduce un-necessary cleaning indications. This microcode fixes a calculation error where the drive was miscalculating a soft error rate that caused the cleaning request to be displayed prematurely. Changed the handling of non-supported media to not flash the amber LED, but instead to just eject the media without flashing the fault LED. Support for new RoHS compliant drive P/N's. This is the minimum microcode level to be used in P/N's 95P1870, 95P1871, 96P1771, and 96P1772.
19P4897 95P1870 24R1988 96P1771	19P4898 95P1871 24R1989 96P1772	210D	A170029C A1700D58	Reduce the dwell time(time that the tape is stopped and the scanner(write/read head) is left spinning on the tape). Reduced from 60 seconds to 2 seconds. Statistical data and customer data gets re-located on the tape when tapes get old, the drive moves the data further down the tape to areas of less usage to prolong tape life.
19P4897 95P1870 24R1988 96P1771	19P4898 95P1871 24R1989 96P1772	210F	A170029C A1700D58	Insure cleaning LED is on when the tape drive exceeds the time since last cleaned maximum. Turn on the cleaning required LED for any media error. Update the Vital Product Data(VPD) for P/N's 96P1771, 24R1988, 96P1772, and 24R1989, to remove the "H0" from the VPD When a tape drive is powered off prior to rewinding the tape after writing data to the tape, the next time the tape drive powers on the drive does a "Format Recovery". This microcode level implements a LED sequence for this format recovery. Improve handling of tape ejection when the tape drive exceeds the tape maximum temperature. Change Cleaning and Test cartridge part numbers to current part numbers for AIX diagnostics. Change from 19P4879 to 24R2135, and from 19P4880 to 24R2138.
19P4897 95P1870 24R1988 96P1771	19P4898 95P1871 24R1989 96P1772	2120	A170029C A1700D58	Correct the cause of tape drive time out. (TAPE_ERR4) Add tape drive and media "Dead bits" to the sense data returned by the drive for use by the IBM support centers in problem determination. The drive "Dead bit" is set by the drive if the drive determines the drive needs service(the drive will fail AIX diagnostics if this bit is set). The drive media "Dead bit" and or the media "warning" bit are set are set if the drive determines the media must be replaced(media "Dead bit" or if the drive determines the media is coming to the end of its useful life(media "warning" bit). If the tape drive is inactive(no tape motion commands) for 30 minutes the tape drive will rewind the tape back into the cartridge to keep the media out of the airflow in the drive. This will reduce some of the impact of customer environment on the media. This will lengthen the time the tape drive takes to start writing after 30 minutes of inactivity but will not effect the user application. If the tape drive is unable to determine a tape format on a write to the tape, from the beginning of the tape, the tape drive will format the tape, including the vendor area, during the write. This "Format-on-the-Fly" will make some tapes that previously could not be written to without errors be able to be written to without errors. The first use of the tape after this "Format-on-the-Fly" may take a few minutes longer as the vendor area of the tape is reconstructed. Decrease the cleaning interval where the tape drive will request cleaning from 75 tape motion hours to 25 tape motion hours. This was done to reduce debris build up on the tape drive heads.
19P4897 95P1870 24R1988 96P1771	19P4898 95P1871 24R1989 96P1772	2123	A170029C A1700D58	Increase the cleaning interval where the tape drive will request cleaning from 25 tape motion hours to 75 tape motion hours as it was prior to microcode level 2120. Increase the amount of time the tape drive is cleaning the drive head from 5 seconds to 10 seconds. This was done to reduce debris build up on the tape drive heads. This will reduce the number of cleanings on the IBM cleaning cartridge. The cleaning cartridges will now clean the drive twice as long and you will get half the number of cleanings you would have gotten with the cleaning cartridge prior to this microcode change. Correct for stuck tape when the eject button is pressed and the tape was in hibernation mode. Implement a Drive SELF-TEST Procedure. The details of the drive self test procedure on in the Drive SELF-TEST Procedure section of this README.
19P4897 95P1870 24R1988 96P1771	19P4898 95P1871 24R1989 96P1772	2124	A170029C A1700D58	Correct issues with unused(brand new) data tapes after the first write to the tape. The issue corrected was in calculating the position data was written on the tape after the first write to a brand new tape.
19P4897 95P1870 24R1988 96P1771	19P4898 95P1871 24R1989 96P1772	2142	A170029C A1700D58	Fast Eject from Media Preservation mode. If a user presses the eject button when the tape is in media preservation mode the tape will eject more rapidly then before(under 1 minute). The reload of the tape will take longer as the tape was ejected without rewinding and the reloading of the tape will cause the tape to be rewound. Improved Emergency Eject function to eject the tape in more failed situations. Improve the drive Internal Self Test(IST). Improve write error recovery retry.
19P4897 95P1870 24R1988 96P1771	19P4898 95P1871 24R1989 96P1772	2152	A170029C A1700D58	Correct Drive Self Test timeout during a load when X23 is loaded from Physical End Of Tape. Correct IST abort issues caused by Unload button. Improvement for stuck tape after tape load. Correct emergency tape eject if prevent media removal set.

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 80GB VXA-2 tape drive do the following AIX command:

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

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

• "Device Specific.(Z1)" showing the "Microcode Level":
• "Device Specific.(LI)" showing the "Microcode Load ID":

  Note: Write down the "Microcode Load ID" as you may need to refer to this later if you use the "Genucode" microcode download process.

 rmt1              10-19-00-1,0      SCSI Tape Drive (80000 MB)
 
       Manufacturer................EXABYTE
       Machine Type and Model......VXA-2
       Device Specific.(Z1)........1003
       Serial Number...............20100232
       Device Specific.(LI)........A170029C
       Part Number.................19P48972
       FRU Number..................19P48984
       EC Level....................H281412
       Device Specific.(Z0)........0180020283000130
       Device Specific.(Z3)........L1

With the microcode level 1005, and higher, the Manufacturer name changes from "EXABYTE" to "IBM".

 rmt1             10-19-00-1,0      SCSI Tape Drive (80000 MB)
 
       Manufacturer................IBM
       Machine Type and Model......VXA-2
       Device Specific.(Z1)........2152
       Serial Number...............20100332
       Device Specific.(LI)........A170029C
       Part Number.................19P48972
       FRU Number..................19P48984
       EC Level....................H281412
       Device Specific.(Z0)........0180020283000130
       Device Specific.(Z3)........L1

New Drive and FRU P/Ns are supported with the microcode level "2105". The following is the new VPD for the new P/Ns:

 rmt3             P1/Z1-A4  LVD SCSI Tape Drive (80000 MB)
 
      Manufacturer................IBM
      Machine Type and Model......VXA-2         H0
      Device Specific.(Z1)........2105
      Serial Number...............25164782
      Device Specific.(LI)........A1700D58
      Part Number.................24R1988
      FRU Number..................24R1989
      EC Level....................H81257
      Device Specific.(Z0)........0180020283000130
      Device Specific.(Z3)........L1

New Drive Vital Product Data with the microcode level "2152". The VPD has the H0 removed. The following is the new VPD for the new P/Ns:

 rmt3             P1/Z1-A4  LVD SCSI Tape Drive (80000 MB)
 
      Manufacturer................IBM
      Machine Type and Model......VXA-2
      Device Specific.(Z1)........2152
      Serial Number...............25164782
      Device Specific.(LI)........A1700D58
      Part Number.................24R1988
      FRU Number..................24R1989
      EC Level....................H81257
      Device Specific.(Z0)........0180020283000130
      Device Specific.(Z3)........L1

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 VXA.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 TapeVXA80GB-2152-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 VXA.bin file on the user system the microcode files will expanded into the /tmp/VXA_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/VXA_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 TapeVXA80GB-2152-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 TapeVXA80GB-2152-01.rpm
  This puts the following files in the /etc/microcode directory for system use:
  • VXA-2.A170029C.dsdata
  • VXA-2.A170029C.2152
  • VXA-2.A1700D58.dsdata
  • VXA-2.A1700D58.2152
  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 VXA.bin file to the eServer pSeries or RS/6000 to the /tmp directory.
• Do the following AIX commands to make the file executable:
  cd /tmp
  chmod +x VXA.bin
• To expand the VXA.bin file use the following command:
  ./VXA.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/VXA_web directory:
  • VXA-2.A170029C.dsdata
  • VXA-2.A170029C.2152
  • VXA-2.A1700D58.dsdata
  • VXA-2.A1700D58.2152

RPM file

• Download the TapeVXA80GB-2152-01.rpm file to the eServer pSeries or RS/6000 to the /tmp directory.
• To expand the TapeVXA80GB-2152-01.rpm file use the following commands:
  cd /tmp
  rpm -ihv --ignoreos TapeVXA80GB-2152-01.rpm
• This will put the following files in the /etc/microcode directory:
  • VXA-2.A170029C.dsdata
  • VXA-2.A170029C.2152
  • VXA-2.A1700D58.dsdata
  • VXA-2.A1700D58.2152

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/VXA_web
  or
  cd /etc/microcode
• Use the AIX command sum to verify the checksum of the microcode file:
  sum VXA*
• 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:
  

  06326   727 VXA-2.A170029C.2152
  03559     3 VXA-2.A170029C.dsdata
   
  47485   727 VXA-2.A1700D58.2152
  09133     3 VXA-2.A1700D58.dsdata
  

Updating the microcode in the drive

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

• AIX 5.1 diagnostics(or higher).
  or
• Genucode.

AIX diagnostics and Genucode use different naming conventions for the 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.
• Genucode requires the microcode file and the dsdata file to be in the /tmp directory.

Copy Dsdata and Microcode to appropriate directory

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

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/VXA_web
 
cp VXA-2.A170029C.dsdata /etc/microcode/.
 
cp VXA-2.A170029C.2152   /etc/microcode/.
 
cp VXA-2.A1700D58.dsdata /etc/microcode/.
 
cp VXA-2.A1700D58.2152   /etc/microcode/.

For Genucode

Do the following AIX commands:

cd /tmp/VXA_web
cp VXA-2.A170029C.2152 /tmp/VXA-2.2152.A170029C
cp VXA-2.A1700D58.2152 /tmp/VXA-2.2152.A1700D58
 
  Depending on the "Microcode Load ID", determined previously, copy the
  file with a matching "Microcode Load ID" to /tmp as the dsdata file.
 
cp VXA-2.A170029C.dsdata /tmp/dsdata
or
cp VXA-2.A1700D58.dsdata /tmp/dsdata

To use AIX Diagnostics

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

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 20 seconds, this will cause a drive reset.

To use Genucode

You now need to use the instructions in the Genucode package to complete the install of the microcode.
Once you have completed the instructions in the genucode package the drive will be at the current microcode level and the microcode update is complete.

Drive SELF-TEST Procedure

Description

The following procedure is designed to allow you to quickly perform a complete set of diagnostic tests on your VXA-2 tape drive, without impacting server operation. This 5 < minute test can also be used to verify good performance of individual VXA 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 7 seconds, until the green Ready LED starts flashing rapidly, then release the button. The Ready LED will continue flashing, indicating that the drive is waiting for a cartridge to be inserted.

Running the Self-Test:

• Start the self-test by inserting IBM Test Tape P/N 24R2135 into the drive. If an IBM Test Tape is not available, you can substitute a scratch (blank) VXA 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 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 24R2138).

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.