LTO - Procedures for Pulling Drive Traces/Dumps from LTO Drives

Asset ID:	1-71-1013260.1
Update Date:	2018-05-25
Keywords:

Solution Type Technical Instruction Sure

Solution 1013260.1 : LTO - Procedures for Pulling Drive Traces/Dumps from LTO Drives

Applies to:

Sun StorageTek SL3000 Modular Library System - Version All Versions to All Versions [Release All Releases]
IBM LTO6 Tape Drive - Version All Versions and later
IBM LTO7 Tape Drive - Version All Versions and later
HP LTO6 Tape Drive - Version All Versions and later
HP LTO4 Tape Drive - Version Not Applicable and later
All Platforms

Goal

Description
Procedures for Pulling Drive Traces/Dumps from LTO Drives

Solution

Steps to Follow:
Pulling Drive Traces/Dumps from LTO Drives

LTO drives are made by IBM, Quantum/Seagate and HP. Each of these manufacturers has their own tool they have provided for pulling information from drives. These all consist of something similar to pulling a drive dump from a 9840/9940.

HP LTO uses HP LTT (Library and Tape Tool).

Download the LTT tool from the following KB: HP LTO - Where to Find and Download the HP LTO Library and Tape Test Diagnostic Tool (Doc ID 1014570.1)

The LTT application can be acquired from a L1 or L2 Tape Technical Support Center Representative.

Refer to ( Doc. 1185771.1 ) for using HP LTT with Solaris 10.

HP LTO Tape Drive - Accessing HP LTO Library and Tape Test Diagnostic Tool (Doc ID 1014570.1)

NOTE: Download the latest version of the HP Library and Tape Tool from the HP site along with the add-on download of diagnostic scripts also available from the HP site. Older versions may not have the correct diagnostic tests for newer code versions and will not provide necessary information for problem determination.

Quantum's diagnostic tool is called "StorageCare Sage x Talk". This tool is available on the Quantum web site. Seagate /Certance Tape is now called Quantum. Go to Diagnostic Tools for utility to pull dumps on the Quantum drives. It runs on a variety of platforms. To pull the trace information use the "Retrieve Information" button and then check the "Cartridge Memory", "EEPROM Data" and the "Trace Buffer" options.

IBM has ITDT for it's diagnostic tool which is a Drive Firmware Download and Dump Tool utility to pull dumps from the drive.

Contact Oracle Tape Technical Support to acquire the ITDT tool.

Download the required tool version from the Tape Support website: IBM ITDT tools are listed under the "Reference" -> "Tape Product Tools" -> "OEM Drives" section on TapeSupport (https://tapesupport.us.oracle.com/Procedures/tools_main.php#OEM Drives).

Note: For the Windows versions of IBM ITDT tools, MOS won't allow you to post an ".exe" or ".msi" file so we had to add a ".txt" file extension to the end of them so please make sure the customer is aware that after they download the file from MOS they will have to take the ".txt" file extension off.

How to Run Diagnostics Using ITDT on IBM LTO Tape Drive:ATR:1387799.1:2 (Doc ID 1387799.1)

This tool comes in two flavors, refer to the website for further information:

-Older drives (v1.2)

-(v4.x+) for newer drives.

IBM Note: When an error code 3 or 4 is displayed on the drive front panel, a dump already exists. Function code 4 will overwrite this dump, causing the error information to be lost. If there is another error code besides a 3 or a 4 or no error code, then you will need to initiate a dump and then read the dump to save it.

ALL DRIVES NOTE:

Now, a few important things to remember about these utilities. They cannot be read by Oracle, to do any analysis or troubleshooting. The traces these drives take can only be analyzed by the manufacturers and are to be used only when there is an issue at a site where this data is requested from engineering or Tape Technical Support. Also, if you are requested to pull these traces for a particular problem then they must be pulled from the drives immediately following the problem that is occurring before any other action or commands are directed to that drive. The drive buffers that store the data for the trace are quite small and will be overwritten if the data is not collected immediately.

If a drive dump is requested then a detailed description of the problem being experienced, system and application logs showing the error(s) and any other requested information must also be sent in with the dumps. The dumps are not magic and will not tell what every problem is. They can only show what was sent to the drive just prior to when the dump is taken and the response of the drive. This may or may not show an error.

Attachments

This solution has no attachment