HP LTO5 Tape Drive
 
HP LTO2 Tape Drive
 
HP LTO6 Tape Drive
 
Sun StorageTek Crypto Key Management System
 
HP LTO3 Tape Drive
 
Oracle Key Manager
 
HP LTO4 Tape Drive
 
HP LTO4 Tape Drive
 
HP LTO1 Tape Drive
 
Sun StorageTek SL500 Modular Library System
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: TAPE-CAP VCAP
 

In this Document

Goal

Solution

References

Applies to:

Goal

How to Pull Drive Dumps Using HP LTT on Solaris 10 or Linux.

How to retrieve a Drive Dump from a HP LTO Drive with the HP LTT Tool.

Solution

DISPATCH INSTRUCTIONS
- WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED:
Familiar with the HP LTO tape drive.

- TIME ESTIMATE: 30 minutes

- TASK COMPLEXITY: 0

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:
- PROBLEM OVERVIEW:
HP LTO tape drive is experiencing undetermined errors.  Need to acquire log information to determine what the problem is.

- WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE
RESOLUTION ACTIVITY?:
Work to the tape drive having issues should be stopped.

- WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE:
--- Instructions for the Reader ---
Refer to the attached document for specific steps to be taken when using Solaris 10.

Refer to the attached document for specific steps to be taken when using the HP LTT Windows Drive Dump Procedure.

if the customer has a HP LTO5 or higher drive they can retrieve the drive dumps from the service Ethernet port. Refer to the Knowledge document below for further information:

HP LTO - How To Retrieve Drive Dumps From HP LTO Drives Over the Service Ethernet Port with the HP LTT Tool (Doc ID 2006130.1)

--- Troubleshooting Details ---
For help with LTT 4.10, refer to the HP LTT 4.10 User's Guide attached to this document.

HP LTT 4.15 for Windows 7:

This procedure was done with the 4.15 version of the HP LTT tool on Windows 7.

To generate and retrieve a dump off of the HP LTO tapes drives with the HP LTT tool please follow the following procedure:

Note: Always run the HP LTT tool as Administrator

1. Click continue to scan for available devices

Note: If you have run the tool previously you will get a saved scan window where you will need to choose the devices that you’d like to use the HP LTT tool against. If this is the first time you’ve run the HP LTT tool you will not get the saved scan screen.

2. You should now get the main HP LTT tool screen in which most of the tabs or buttons at the top will be greyed out and unusable.

3. Select the drive that you want to generate and retrieve the dump from and all of the tabs or buttons at the top of the tool should now become usable.

4. Verify on that screen that the S/N of the drive is the one that you had a failure on and want to get the drive dump from.

5. Click on the “Support” tab and you will see the support screen from where you will generate and retrieve the dump.

6. Click on the “Extract Device Data” button and the tool will go out and generate and retrieve the dump data from the drive.

7. Click on the “Save Support Ticket” button to save the dump data off to a dump file.

Note: Please save the dump file off with the default file extension of “.lzt”

8. Take the “.lzt” dump file and attach it to the SR so that an Oracle support representative can analyze it.

HP LTT 4.10 for Solaris 10

How to pull a dump from a HP LTO drive using HP’s LTT 4.10 command line on Solaris 10:

You must first do a scan on the system to save them into the “saved_scan.txt” in the default install dir of the LTT tool.  As long as no system changes are made (IE no drives added or removed from the system) then you should never have to do the scan again.  The syntax of the command is “hp_ltt –f scan”.  No other options are needed.  You should do a “cat saved_scan.txt” to verify that the drives are seen by the LTT tool.

Once the drives are seen you must use the ticket option to get the support ticket or dump off of the drive.  You have to get the path of the drive correct or it will not pull the dump from the drive successfully.  This exact path is in the “saved_can.txt” file.  No other options are needed and this will save the drive dump in the default “logs” dir of the LTT tool. 

Note: 
Below is an example of the command used that successfully pulled a dump in the correct .lzt format from a drive.

bash-3.00# hp_ltt -f ticket p=/pci@1e,600000/pci@0/pci@2/SUNW,qlc@0,1/fp@0,0:::0.1115392.0[st@w500104f000acb624,0-/dev/rmt/0]:HP:Ultrium 4-SCSI:H58S

And then here is an example of the file that was placed in the logs dir.

bash-3.00# ls
Database_config.cfg
EventLog_backup_1.ltt
EventLog.ltt
prl.txt
st_HPUltrium_4-SCSI_20100824_113715_HU18031635.lzt
toolactivity.log

At this point the customer should just grab the .lzt file and e-mail to the engineer that asked them to get the dump off of the drive.

root@adc07osbmed404 ltt]# ./hp_ltt -f scan dirpath=/tmp/                                                  dirpath=<absolute directory path>.

HP LTT Started.. Please Wait until it completes..

---------------------------------------------------------------

Library & TapeTools - Commandline parameter version

Wed Feb  6 14:45:33 2013

---------------------------------------------------------------

User passed options: -f scan dirpath=/tmp/ 

---------------------------------------------------------------

1-0[scsi_adapter]:::

0.0.0[0-/dev/sg0]:SEAGATE:ST914603SSUN146G:0B70

0.1.0[0-/dev/sg1]:SEAGATE:ST914603SSUN146G:0B70

0.2.0[0-/dev/sg2]:SEAGATE:ST930003SSUN300G:0B70

0.3.0[0-/dev/sg3]:SEAGATE:ST930003SSUN300G:0B70

0.4.0[0-/dev/sg4]:SEAGATE:ST930003SSUN300G:0B70

0.5.0[0-/dev/sg5]:SEAGATE:ST930003SSUN300G:0B70

0.6.0[0-/dev/sg6]:SEAGATE:ST930003SSUN300G:0B70

0.7.0[0-/dev/sg7]:SEAGATE:ST930003SSUN300G:0B70

2-7[scsi_adapter]:::

70.0.0[7-/dev/sg8]:HP:Ultrium 4-SCSI:H64S

70.1.0[7-/dev/sg9]:HP:Ultrium 4-SCSI:H64S

70.2.0[7-/dev/sg10]:HP:Ultrium 4-SCSI:H64S

70.3.0[7-/dev/sg11]:HP:Ultrium 4-SCSI:H64S

70.4.0[7-/dev/sg12]:HP:Ultrium 4-SCSI:H64S

70.5.0[7-/dev/sg13]:HP:Ultrium 4-SCSI:H64S

70.6.0[7-/dev/sg14]:HP:Ultrium 4-SCSI:H64S

70.7.0[7-/dev/sg15]:HP:Ultrium 4-SCSI:H64S

3-8[scsi_adapter]:::

80.0.0[8-/dev/sg16]:HP:Ultrium 4-SCSI:H64S

80.1.0[8-/dev/sg17]:HP:Ultrium 4-SCSI:H64S

80.2.0[8-/dev/sg18]:HP:Ultrium 4-SCSI:H64S

80.3.0[8-/dev/sg19]:HP:Ultrium 4-SCSI:H64S

80.4.0[8-/dev/sg20]:HP:Ultrium 4-SCSI:H64S

80.5.0[8-/dev/sg21]:HP:Ultrium 4-SCSI:H64S

4-9[scsi_adapter]:::

If you use udev rules you can look for sg by symlink of wwnn:

[root@adc07osbmed404 ltt]# ls -l /dev/sg/by-id/scsi-tape-3500104f000afe8e3

lrwxrwxrwx 1 root root 9 Oct 29 15:46 /dev/sg/by-id/scsi-tape-3500104f000afe8e3 -> ../../sg8

If you don't you can use sg_map and sg_inq:

[root@adc07osbmed404 tmp]# sg_map -x -i

/dev/sg0  0 0 0 0  0  /dev/sda  SEAGATE   ST914603SSUN146G  0B70

/dev/sg1  0 0 1 0  0  /dev/sdb  SEAGATE   ST914603SSUN146G  0B70

/dev/sg2  0 0 2 0  0  /dev/sdc  SEAGATE   ST930003SSUN300G  0B70

/dev/sg3  0 0 3 0  0  /dev/sdd  SEAGATE   ST930003SSUN300G  0B70

/dev/sg4  0 0 4 0  0  /dev/sde  SEAGATE   ST930003SSUN300G  0B70

/dev/sg5  0 0 5 0  0  /dev/sdf  SEAGATE   ST930003SSUN300G  0B70

/dev/sg6  0 0 6 0  0  /dev/sdg  SEAGATE   ST930003SSUN300G  0B70

/dev/sg7  0 0 7 0  0  /dev/sdh  SEAGATE   ST930003SSUN300G  0B70

/dev/sg8  7 0 0 0  1  /dev/nst0  HP        Ultrium 4-SCSI    H64S

/dev/sg9  7 0 1 0  1  /dev/nst1  HP        Ultrium 4-SCSI    H64S

/dev/sg10  7 0 2 0  1  /dev/nst2  HP        Ultrium 4-SCSI    H64S

/dev/sg11  7 0 3 0  1  /dev/nst3  HP        Ultrium 4-SCSI    H64S

/dev/sg12  7 0 4 0  1  /dev/nst4  HP        Ultrium 4-SCSI    H64S

/dev/sg13  7 0 5 0  1  /dev/nst5  HP        Ultrium 4-SCSI    H64S

/dev/sg14  7 0 6 0  1  /dev/nst6  HP        Ultrium 4-SCSI    H64S

/dev/sg15  7 0 7 0  1  /dev/nst7  HP        Ultrium 4-SCSI    H64S

/dev/sg16  8 0 0 0  1  /dev/nst8  HP        Ultrium 4-SCSI    H64S

/dev/sg17  8 0 1 0  1  /dev/nst9  HP        Ultrium 4-SCSI    H64S

/dev/sg18  8 0 2 0  1  /dev/nst10  HP        Ultrium 4-SCSI    H64S

/dev/sg19  8 0 3 0  1  /dev/nst11  HP        Ultrium 4-SCSI    H64S

/dev/sg20  8 0 4 0  1  /dev/nst12  HP        Ultrium 4-SCSI    H64S

/dev/sg21  8 0 5 0  1  /dev/nst13  HP        Ultrium 4-SCSI    H64S

/dev/sg22  9 0 0 0  5  /dev/scd0  TEAC      DV-W28SS-R        1.0C

You have new mail in /var/spool/mail/root

[root@adc07osbmed404 tmp]# sg_inq /dev/sg8 

standard INQUIRY:

  PQual=0  Device_type=1  RMB=1  version=0x05  [SPC-3]

  [AERC=0]  [TrmTsk=0]  NormACA=0  HiSUP=0  Resp_data_format=2

  SCCS=0  ACC=0  TPGS=1  3PC=0  Protect=0  BQue=1

  EncServ=0  MultiP=1 (VS=0)  [MChngr=0]  [ACKREQQ=0]  Addr16=0

  [RelAdr=0]  WBus16=0  Sync=0  Linked=0  [TranDis=0]  CmdQue=0

  [SPI: Clocking=0x0  QAS=0  IUS=0]

    length=96 (0x60)   Peripheral device type: tape

 Vendor identification: HP      

 Product identification: Ultrium 4-SCSI  

 Product revision level: H64S

 Unit serial number: HU1108F9AJ

[root@adc07osbmed404 tmp]# 

Once you have the path: Copy in the device bits from your scan.. start of line to first : .

[root@adc07osbmed404 ltt]# ./hp_ltt -f ticket p=70.0.0[7-/dev/sg8] dirpath=/tmp/ltt_dump/

HP LTT Started.. Please Wait until it completes..

---------------------------------------------------------------

Library & TapeTools - Commandline parameter version

Wed Feb  6 14:56:51 2013

---------------------------------------------------------------

User passed options: -f ticket p=70.0.0[7-/dev/sg8] dirpath=/tmp/ltt_dump/ 

---------------------------------------------------------------

 Support Ticket is Generated successfully and stored in the directory path:

/tmp/ltt_dump/

You have new mail in /var/spool/mail/root

[root@adc07osbmed404 ltt]# cd /tmp/ltt_dump/

[root@adc07osbmed404 ltt_dump]# ls

EventLog.ltt  misc  prl.txt  st_HPUltrium_4-SCSI_20130206_145657_HU1108F9AJ.lzt  toolactivity.log

[root@adc07osbmed404 ltt_dump]# ls -lart

total 308

-rw-r--r-- 1 root root    222 Feb  6 14:56 toolactivity.log

drwxrwxrwt 6 root root    180 Feb  6 14:56 ..

-rw-r--r-- 1 root root   2673 Feb  6 14:56 prl.txt

-rw-r--r-- 1 root root 280576 Feb  6 14:56 st_HPUltrium_4-SCSI_20130206_145657_HU1108F9AJ.lzt

drwxr--r-- 2 root root     40 Feb  6 14:56 misc

-rw-r--r-- 1 root root  13272 Feb  6 14:56 EventLog.ltt

drwxr--r-- 3 root root    140 Feb  6 14:56 .

[root@adc07osbmed404 ltt_dump]# cd ../

[root@adc07osbmed404 tmp]# tar zcvf ltt_dump.tar.gz ltt_dump

ltt_dump/

ltt_dump/st_HPUltrium_4-SCSI_20130206_145657_HU1108F9AJ.lzt

ltt_dump/prl.txt

ltt_dump/misc/

ltt_dump/EventLog.ltt

ltt_dump/toolactivity.log

[root@adc07osbmed404 tmp]# 

OBTAIN CUSTOMER ACCEPTANCE
- WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:
Work can be restarted on the drive that had the error information taken.

PARTS NOTE: na

REFERENCE INFORMATION:
Refer to attached documents.

This solution has no attachment