Asset ID: |
1-71-1185771.1 |
Update Date: | 2012-09-14 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1185771.1
:
How to Collect Statistical and Error Logs from HP LTO Tape Drive Using HP LTT:ATR:1185771.1:1
Related Items |
- HP LTO5 Tape Drive
- HP LTO2 Tape Drive
- HP LTO3 Tape Drive
- Sun StorageTek Crypto Key Management System
- HP LTO4 Tape Drive
- Oracle Key Manager
- HP LTO1 Tape Drive
|
Related Categories |
- PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: TAPE-CAP VCAP
|
In this Document
Applies to:
HP LTO1 Tape Drive - Version Not Applicable and later
HP LTO3 Tape Drive - Version Not Applicable and later
HP LTO4 Tape Drive - Version Not Applicable and later
HP LTO5 Tape Drive - Version Not Applicable and later
HP LTO2 Tape Drive - Version Not Applicable and later
Information in this document applies to any platform.
Checked for relevance on 14-Sept-2012.
Goal
How to Pull Drive Dumps Using HP LTT on Solaris 10.
Fix
DISPATCH INSTRUCTIONS
- WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED:
Familiar with the HP LTO tape drive.
- TIME ESTIMATE: 30 minutes
- TASK COMPLEXITY: 1
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.
--- 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.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.
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.
Attachments
This solution has no attachment