Library and Tape Tools v4.0 SR2 User Guide (March 2006)

HP StorageWorks
Library and Tape Tools User Guide
Product Version: 4.0 SR2
HP StorageWorks Library and Tape Tools (L&TT) is a comprehensive application that provides functions for identifying,
testing, updating, and troubleshooting a wide variety of data storage hardware and media.
*56975890*
Part number: 5697–5890
Fifteenth edition: (March 2006)
Legal and notice information
© Copyright 2002-2006 Hewlett-Packard Development Company, L.P.
Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or
for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied,
reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information contained in
this document is subject to change without notice.
Compaq Computer Corporation is a wholly-owned subsidiary of Hewlett-Packard Company.
Microsoft®, MS-DOS®, MS Windows®, Windows®, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information is
provided “as is” without warranty of any kind and is subject to change without notice. The warranties for Hewlett-Packard Company
products are set forth in the express limited warranty statements for such products. Nothing herein should be construed as
constituting an additional warranty.
Contents
About this guide
. . . . . . . . . . . . . . . . . . . . . . . . .
Intended audience . . . . . . .
Prerequisites . . . . . . . . .
Document conventions and symbols
HP technical support . . . . . .
Subscription service . . . . . .
Other HP web sites . . . . . .
. . .
. . .
. .
. . .
. . .
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software features . . . . . . .
Supported products and operating
Finding additional information . .
Getting support . . . . . . . .
. . . .
systems
. . . .
. . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing L&TT for Windows . . . . . . . . .
Upgrading from a previous version of L&TT
Windows installation prerequisites . . . .
Installation procedure . . . . . . . . .
Installing L&TT for NetWare . . . . . . . . .
NetWare installation prerequisites . . . .
Installation procedure . . . . . . . . .
Installing L&TT for HP-UX, Tru64, and Linux . .
HP-UX installation prerequisites . . . . .
Tru64 installation prerequisites . . . . . .
Linux installation prerequisites . . . . . .
Installation procedure . . . . . . . . .
Uninstalling previous versions . . . .
Installing the latest version . . . . . .
Installing L&TT for HP OpenVMS . . . . . . .
OpenVMS installation prerequisites . . . .
Installation procedure . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3 Getting Started with L&TT . . . . . . . . . . . . . . . . . . . . .
Starting L&TT (GUI) . . . . . . . . . . . .
Using the Scan Mode Selection feature . . . .
Scan mode . . . . . . . . . . . . . .
Using the Saved/Manual Scan screen
Using the Skip-Scan feature . . . . .
Additional device scan considerations
I/O mode . . . . . . . . . . . . . .
Skip this dialog in the future . . . . . . .
Application window layout . . . . . . . . .
Using the Device Information screen . . . . .
Standalone devices . . . . . . . . . .
Library and autoloader products . . . . .
Using the Firmware Management screen . . .
Using the Tests screen . . . . . . . . . . .
Using the Support Ticket Generation screen . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Library and Tape Tools User Guide
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
11
11
11
12
12
13
13
15
15
15
16
16
17
17
17
18
18
20
20
20
21
21
21
22
22
22
22
23
23
24
25
25
25
26
27
27
28
28
29
29
31
31
32
34
35
36
3
Starting L&TT (CSI) . . . . . . . . .
Navigating the screens . . . . . . .
Using the Scan Mode Selection screen
Using the Saved/Manual Scan screen
Using the Skip-Scan feature . . .
Using the Device Information screen .
Standalone devices . . . . . .
Library and autoloader products .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4 Firmware Management . . . . . . . . . . . . . . . . . . . . . .
Accessing firmware revision and release note information (GUI)
Acquiring firmware files (GUI) . . . . . . . . . . . . . .
Using the Get Files from Web functionality (GUI) . . . .
Accessing the Get Files from Web dialog box . . .
Selecting and downloading updated firmware files .
Viewing firmware revision history . . . . . . . . .
Uploading firmware to devices (GUI) . . . . . . . . . . .
Advanced options (GUI) . . . . . . . . . . . . . . . .
Acquiring firmware files (CSI) . . . . . . . . . . . . . .
Using the Get Files from Web functionality (CSI) . . . .
Uploading firmware to devices (CSI) . . . . . . . . . . .
Advanced options (CSI) . . . . . . . . . . . . . . . . .
Using a firmware update (FUP) tape . . . . . . . . . . .
Performing the update . . . . . . . . . . . . . . .
SDLT . . . . . . . . . . . . . . . . . . . . .
DLT VS80/DLT1 . . . . . . . . . . . . . . . .
DLT 4000/7000/8000 . . . . . . . . . . . . .
Ultrium . . . . . . . . . . . . . . . . . . . .
HP DDS/DAT . . . . . . . . . . . . . . . . .
Compaq/Sony AIT & DDS . . . . . . . . . . .
Converting a firmware update tape to a data tape . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5 Tests and Utility functions . . . . . . . . . . . . . . . . . . . . .
Running the tests (GUI) . . . . . . . . . . . . . .
Viewing test results . . . . . . . . . . . . . .
Running the tests (CSI) . . . . . . . . . . . . . .
Viewing test results (CSI) . . . . . . . . . . .
Test descriptions . . . . . . . . . . . . . . . . .
Performance tests . . . . . . . . . . . . . .
Diagnostic tests . . . . . . . . . . . . . . .
Acceptance test . . . . . . . . . . . . .
Assessment test . . . . . . . . . . . . .
Autoloader Exerciser test . . . . . . . . .
Connectivity test . . . . . . . . . . . . .
Data Compression test . . . . . . . . . .
Device Analysis test . . . . . . . . . . .
Device Self-Test . . . . . . . . . . . . .
DLT SRAM Check test (short and long versions)
ESL Vendor ID test . . . . . . . . . . . .
Firmware Tape Creator (FUP tape) test . . .
Full Sweep test . . . . . . . . . . . . .
Initialize Element Status test . . . . . . . .
Installation Check test . . . . . . . . . .
Library Exerciser test . . . . . . . . . . .
LTO Cooling Check test . . . . . . . . . .
LTO Firmware to Data Tape Creator . . . .
LTO Stuck Tape test . . . . . . . . . . . .
Media Analysis test . . . . . . . . . . .
Media Erase test . . . . . . . . . . . . .
4
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
36
37
38
39
39
40
40
41
43
43
44
44
44
45
46
46
47
48
48
49
49
50
50
50
51
52
53
54
54
55
57
58
58
58
58
59
59
59
60
61
64
64
64
65
65
65
66
66
67
67
68
68
69
69
69
70
70
Media Validation test . . . . . . . . . . . . . .
MO Media Validation test . . . . . . . . . . .
Read/Write Stress test . . . . . . . . . . . . .
Read/Write test . . . . . . . . . . . . . . . .
Restore Factory Default Settings . . . . . . . . .
SDLT Read Media IDs test . . . . . . . . . . . .
SDLT Tape Edge Damage (TED) test . . . . . . . .
Using the Drive Performance Test . . . . . . . . . . . . .
Using the System Performance Test . . . . . . . . . . . .
Performing the System Performance Restore Pre-Test (GUI)
Performing the System Performance Backup Pre-Test . . .
Performing the System Performance Pre-Tests (CSI) . . . .
Using the Device Analysis Test . . . . . . . . . . . . . .
Using the Read/Write Test . . . . . . . . . . . . . . .
Using the Media Analysis Test . . . . . . . . . . . . . .
Using the Library Exerciser Test . . . . . . . . . . . . .
Using the utility functions . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6 Reports and Support Tickets . . . . . . . . . . . . . . . . . . . .
Using a report or support ticket (Windows) . .
Using the Support screen . . . . . . . .
Support ticket size management . . .
Viewing a report or support ticket . . . .
Setting the detail level . . . . . . .
Other functionality . . . . . . . . .
Viewing embedded data . . . . . .
Saving a report or support ticket . . . . .
Sending a report or support ticket by e-mail
Comparing reports or support tickets . . .
Interpreting a report . . . . . . . . . .
Understanding the margin ratings . .
Things to look for . . . . . . . . .
Device-specific report analysis . . . . . .
LTO drives . . . . . . . . . . . .
LTO media . . . . . . . . . . . .
Generating and viewing a support ticket (CSI) .
Support ticket size management . . . . .
Support ticket compression . . . . .
Splitting of support tickets (CSI) . . .
Sending a support ticket by e-mail (CSI) . .
Common information reported for all products .
Using the event log . . . . . . . . . . . .
Generating an event log (Windows) . . .
Generating an event log (CSI) . . . . . .
7 Additional Functionality
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . .
Setting software preferences . . . . . .
Available options . . . . . . . .
Using the Internet update functionality .
Using passwords . . . . . . . . . .
Setting passwords . . . . . . . .
Using the Front Panel function . . . . .
Using the Move Media function . . . .
Possible Move Media error situations
Performing manual product identification
Using the Quiet Mode feature . . . . .
Using the Installation Check feature . . .
Using L&TT in restricted mode . . . . .
Using the Tool Status Report . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Library and Tape Tools User Guide
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
71
71
72
72
73
74
75
76
79
79
80
81
83
84
84
85
86
87
88
88
89
90
90
91
92
92
93
94
95
95
96
97
97
98
99
100
100
100
101
101
102
102
102
105
106
107
109
110
110
111
112
113
114
115
116
118
119
5
8 Advanced Installation Topics
Other changes to the system (GUI) . .
Reboot criteria . . . . . . . . . . .
Running L&TT from a CD-ROM . . . .
Files installed on the system . . . . .
Other changes to the system (CSI)
.
.
.
.
.
. . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9 Frequently Asked Questions . . . . . . . . . . . . . . . . . . . .
121
121
121
121
122
122
123
General questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Why should I run L&TT tests? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Where can I find information about media compatibility with my hardware? . . . . . . . . . . 123
Where can I find information about hardware and software compatibility? . . . . . . . . . . . 124
Where can I find information about drive cleaning requirements? . . . . . . . . . . . . . . . 124
Windows questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
How do I run L&TT from a CD-ROM? . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
How do I shut down the application in the taskbar? . . . . . . . . . . . . . . . . . . . . . 125
When installing L&TT for Windows, should I uninstall my previous version first? . . . . . . . . . 125
Why can’t I uninstall L&TT or install a new version? . . . . . . . . . . . . . . . . . . . . . 125
How do I erase an LTO FUP tape? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
How do I configure e-mail to send support tickets? . . . . . . . . . . . . . . . . . . . . . 126
Does L&TT use any system resources in the background? . . . . . . . . . . . . . . . . . . . 126
I am using an authenticated proxy at my site. How do I configure L&TT to connect to the HP website to
download firmware updates? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
L&TT starts in “restricted” mode and most functionality is unavailable. What is happening? . . . . 127
Why doesn’t L&TT for Windows “see” devices that are connected to a computer running HP-UX? . 127
Why doesn’t L&TT for Windows “see” my USB drives? . . . . . . . . . . . . . . . . . . . . 127
CSI questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
How do I set the password? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Why does my display not show any text or only a single line of text on my HP-UX system? . . . . 128
Why doesn’t L&TT for HP-UX “see” some of my devices? . . . . . . . . . . . . . . . . . . . 128
Why am I unable to download firmware/script files using the download option in the CSI (HP-UX,
Linux)? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Why doesn’t L&TT for Tru64 “see” some of my devices? . . . . . . . . . . . . . . . . . . . 128
Why doesn’t L&TT for Linux see some of my devices? . . . . . . . . . . . . . . . . . . . . 129
Why doesn’t L&TT for Windows “see” devices that are connected to a computer running HP-UX? . 129
How do I disconnect a SCSI device in Tru64? . . . . . . . . . . . . . . . . . . . . . . . 130
How do I connect/disconnect a SCSI device in Linux without rebooting? . . . . . . . . . . . . 130
Why doesn’t L&TT for OpenVMS “see” my media changer? . . . . . . . . . . . . . . . . . 130
Why am I getting Error activating image PTHREAD$RTL while running L&TT on OVMS 7.3-1? . . . 130
10 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting L&TT . . . . . . . . . . . . . . . .
Troubleshooting devices . . . . . . . . . . . . . . .
Using L&TT to troubleshoot tape devices . . . . . .
Are you performing regular maintenance? . . .
Is the drive connected properly? . . . . . . .
Is the drive working as expected? . . . . . .
Is the drive firmware up to date? . . . . . . .
Is the drive performing as expected? . . . . .
Is the media in good condition? . . . . . . .
Known issues . . . . . . . . . . . . . . . . .
Device access issues (RSM on Windows) . . .
Device performance issues . . . . . . . . .
Firmware issues with Ultrium drives . . . . . .
Additional interactive device troubleshooting content
Troubleshooting third-party software . . . . . . . . .
Backup failed . . . . . . . . . . . . . . . . .
6
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
131
131
131
131
132
132
132
133
133
133
133
133
134
135
135
135
135
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Library and Tape Tools User Guide
137
7
Figures
1 L&TT splash screen . . . . . . . . . . . . . . . .
2 Saved/Manual Scan screen . . . . . . . . . . . .
3 L&TT main screen . . . . . . . . . . . . . . . . .
4 Device Information screen showing a standalone device
5 Device Information screen showing a library . . . . .
6 Firmware Management screen . . . . . . . . . . .
7 Tests screen . . . . . . . . . . . . . . . . . . .
8 Support Ticket Generation screen . . . . . . . . . .
9 Command Help screen accessed from the Main screen .
10 Scan Mode Selection screen . . . . . . . . . . .
11 Saved/Manual Scan screen (CSI) . . . . . . . . .
12 CSI Main screen . . . . . . . . . . . . . . . . .
13 Device Information screen for a standalone device . .
14 Device Information screen for a library . . . . . . .
15 Get Files from Web dialog box—Firmware tab . . . .
16 Firmware Update screen . . . . . . . . . . . . .
17 Factory Firmware Overrides dialog box . . . . . . .
18 Drive Performance screen . . . . . . . . . . . . .
19 Device Performance Tool screen . . . . . . . . . .
20 Restore Pre-Test tab of the System Performance screen .
21 Backup Pre-Test tab of the System Performance screen .
22 Backup Pre-Test screen (CSI) . . . . . . . . . . . .
23 Restore Pre-Test screen (CSI) . . . . . . . . . . . .
24 Support screen . . . . . . . . . . . . . . . . .
25 Example report . . . . . . . . . . . . . . . . .
26 Support ticket with embedded data . . . . . . . . .
27 E-mail support ticket dialog box . . . . . . . . . .
28 Support ticket comparison results . . . . . . . . . .
29 L&TT Preferences dialog box (default settings shown) .
30 L&TT preferences dialog box (CSI version) . . . . . .
31 Front panel screen . . . . . . . . . . . . . . . .
32 Move Media screen . . . . . . . . . . . . . . .
33 Installation Check wizard . . . . . . . . . . . . .
34 Tool Status Report screen (GUI) . . . . . . . . . .
35 Tool Status Report screen (CSI) . . . . . . . . . . .
8
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
26
27
29
31
32
34
35
36
37
38
38
39
40
41
45
46
47
76
78
79
81
82
83
89
91
92
93
95
106
107
111
112
117
119
120
Tables
1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 L&TT installation directory locations . . . . . . . . . . . . . . . . . . . . . . . . . .
Library and Tape Tools User Guide
12
122
9
10
About this guide
This user guide provides information to help you:
• Understand features and functionality of L&TT
• Effectively use the full functionality of L&TT to obtain maximum performance from your storage
hardware, and to test, diagnose, and resolve hardware issues
“About this Guide” topics include:
• Overview
• Conventions
• Getting Help
Intended audience
This book is intended for:
•
•
•
•
Users who want to use L&TT to conveniently update firmware in their storage hardware
Users who need to test, diagnose, and resolve storage hardware issues
Support technicians
Call center personnel
Prerequisites
Before you attempt to use L&TT, you should have a basic understanding of the following technologies:
• Storage hardware functionality and operation
• SCSI operation
Library and Tape Tools User Guide
11
Document conventions and symbols
Table 1 Document conventions
Convention
Element
Blue text: Table 1
Cross-reference links and e-mail addresses
Blue, underlined text: http://
www.hp.com
Web site addresses
Bold text
• Keys that are pressed
• Text typed into a GUI element, such as a box
• GUI elements that are clicked or selected, such as
menu and list items, buttons, tabs, and check boxes
Italic text
Text emphasis
Monospace text
•
•
•
•
Monospace, italic text
• Code variables
• Command variables
Monospace, bold text
Emphasized monospace text
File and directory names
System output
Code
Commands, their arguments, and argument values
WARNING!
Indicates that failure to follow directions could result in bodily harm or death.
CAUTION:
Indicates that failure to follow directions could result in damage to equipment or data.
IMPORTANT:
Provides clarifying information or specific instructions.
NOTE:
Provides additional information.
TIP:
Provides helpful hints and shortcuts.
HP technical support
Telephone numbers for worldwide technical support are listed on the HP support web site:
http://www.hp.com/support/.
Collect the following information before calling:
• Technical support registration number (if applicable)
12
About this guide
•
•
•
•
•
Product serial numbers
Product model names and numbers
Error messages
Operating system type and revision level
Detailed questions
For continuous quality improvement, calls may be recorded or monitored.
Subscription service
HP strongly recommends that customers register online using the Subscriber’s choice web site:
http://www.hp.com/go/e-updates.
Subscribing to this service provides you with e-mail updates on the latest product enhancements, newest
driver versions, and firmware documentation updates as well as instant access to numerous other product
resources.
After subscribing, locate your products by selecting Business support and then Storage under Product
Category.
Other HP web sites
For additional information, see the following HP web sites:
•
•
•
•
•
•
http://www.hp.com
http://www.hp.com/go/storage
http://www.hp.com/service_locator
http://www.docs.hp.com
http://www.hp.com/support/tapetools
http://www.hp.com/support/lttcompatibility
Library and Tape Tools User Guide
13
14
About this guide
1 Introduction
HP StorageWorks Library and Tape Tools (L&TT) is a collection of storage hardware management and
diagnostic tools for Nearline Tape, Nearline Tape Automation, and Nearline Archival products. L&TT
assembles these tools into a single, convenient program.
Software features
L&TT offers the following features:
• Installation Check—L&TT guides you through a basic installation check of your product. The
software assists the user in choosing an appropriate HBA and SCSI ID(s), ensuring that the device
is detected by the system, and verifying key device functionality.
• Device Identification—L&TT clearly identifies the storage products connected to the system, along
with key information on product configuration and status.
• Troubleshooting Tests—L&TT provides various tests to verify product functionality or to isolate
product issues. Tests include device self-tests, read/write tests on drives, exerciser tests for
autoloaders and libraries, and specific device utilities.
• Firmware Upgrades—L&TT provides a convenient way of updating product firmware, enabling
users with an Internet connection to take advantage of ongoing enhancements. The software can
be configured to check the Web automatically for firmware updates for connected devices, or
users can manually check the Web for updates if the automatic update feature is not desired.
If updated firmware is available, the program notifies the user, and the updates can easily be
copied to the system. With libraries, users can upgrade the library and the embedded drive
firmware in the same operation.
• Support Ticket Generation—If you experience a problem with a storage product, L&TT can
generate a support ticket that includes essential information for troubleshooting the problem.
As an alternative to phone support, you can e-mail the support ticket to a support center for
assistance. This information streamlines the support process and enables the support staff to
better serve you if a support call is made later.
When a support ticket for a device is generated, L&TT performs a Device Analysis test on the
device. The support ticket contains generic information about a device, as well as the results of
the Device Analysis test. The Device Analysis test can be performed by itself, but HP recommends
generating a support ticket because the resulting data is presented in a more useful format.
• Automatic Notification of Web Updates—If a connection to the Internet is present and web
updates are enabled in the tool preferences, L&TT automatically informs you of the following
updates, if available, each time the program is started:
• New versions of L&TT
• New firmware files for connected devices
• New device-specific functionality for connected devices
Supported products and operating systems
For a complete listing of compatible products, refer to the specifications page at
http://www.hp.com/support/lttcompatibility.
The level of functionality that L&TT offers for each device varies depending on features of the device,
and the degree of device integration into L&TT.
Library and Tape Tools User Guide
15
Finding additional information
The HP web site provides the current version of L&TT for download, and general information about the
tool. Access the web site at:
http://www.hp.com/support/tapetools
Getting support
E-mail support is available from ltt_team@hp.com. You can expect a response within 24 hours (usually
sooner) during a normal business week.
Use this address to obtain support for L&TT to report bugs, to provide feedback on this manual, to report
any issues with the L&TT web site, or to provide enhancement suggestions. HP appreciates feedback on
how to make improvements for future versions of L&TT.
NOTE:
This address is intended to provide support for L&TT software. This address is not for assistance in
troubleshooting hardware products. Refer to the documentation that comes with your hardware for
support options for that product.
16
Introduction
2 Installation
This chapter outlines the procedure for installing L&TT on a Microsoft® Windows®, Novell NetWare,
HP-UX, HP Tru64, Linux, or HP OpenVMS platform. The Windows version of L&TT uses a graphical user
interface (GUI). All other versions of the program use a command screen interface (CSI).
The information in this chapter and in subsequent chapters is presented for both the GUI and CSI versions
of L&TT. When using an electronic version of this documentation, click the appropriate link at the
beginning of the chapter to quickly jump to the section of documentation that applies to your operating
system (OS) or user interface.
Select your OS:
Windows
Netware
HP-UX, Tru64, and Linux
HP OpenVMS
Installing L&TT for Windows
The Windows version of L&TT uses the InstallShield application. InstallShield lets you choose the
installation directory and select other options. It also sets up shortcuts to launch the application in the
Start menu and on the desktop. The Start menu shortcuts also provide access to the online help, the
readme file, the report viewer, and the L&TT Installation Check feature.
Upgrading from a previous version of L&TT
Beginning with version 4.0, the L&TT installer automatically uninstalls any previous versions before
installing the current version, so it is not necessary to manually uninstall your previous version.
Library and Tape Tools User Guide
17
Windows installation prerequisites
Item
Description
Download link
http://www.hp.com/support/tapetools
Install time
(typical)
1-5 minutes
Reboot
requirements
A reboot is required only if your system requires ASPI or an upgrade to the currently
installed version. On systems that require ASPI, if the installer detects a previously installed
version of ASPI older than v4.57, it will install a more recent version of ASPI, which will
require a reboot.
On Windows NT and 2000, ASPI is not installed as part of the operating system. If
a reboot is unacceptable, do not select the checkbox for this option in the installation
process. If you choose not to install ASPI, you must use the Miniport driver (Miniport I/O
mode) to scan for devices.
Issues may arise, however, when using the Miniport I/O mode with devices that use
non-standard OS drivers, or are “claimed” by other applications or the OS. When using
the Miniport I/O mode when a device is claimed, it may be necessary to shut down
any running backup/storage application services to make the device accessible to L&TT.
Alternatively, using the ASPI I/O mode may make the device accessible without requiring
any further action.
Software
dependencies/
prerequisites
Device drivers for the connected tape devices/libraries or default device driver should
be present.
NOTE:
L&TT can be run from the CD ROM.
Known issues
When downloading the L&TT application from the web to your local system, make sure you
name the download folder to something other than HP StorageWorks Library and Tape
Tools or the installation will fail if you attempt to install from that folder. The failure error
will indicate that a different instance of the installer is already running.
Also, do not rename the L&TT installation file. Renaming the file may create a conflict
that prevents L&TT from installing.
Installation procedure
To install the current Windows version of L&TT:
1.
Download or copy the self-extracting executable file to a temporary location.
IMPORTANT:
Do not rename this file. Renaming the file may create a conflict that prevents L&TT from installing.
2. Double-click the self-extracting executable file to launch the installer. The InstallShield Wizard
screen is displayed.
3. Click Next. Read the program license agreement and click Yes if you agree to and accept
the terms of the license agreement.
4. Read the readme file for any last-minute changes to the documentation, then click Next. The
Select Features screen is displayed.
5. Select the desired components to install and click Next.
In most cases, the default settings of this screen are adequate. Windows NT 4.0®, Windows
2000, and Windows XP users have the option to install Advanced SCSI Programming Interface
(ASPI) support. HP does not recommend installing ASPI support unless you have a good reason
to do so.
ASPI support is beneficial when installed storage applications cannot be shut down, and those
applications have locked access to the device through the Miniport driver. If ASPI is installed, it is
generally not necessary to shut down these applications to access devices through L&TT (although
18
Installation
the applications should not be accessing the devices while L&TT is running). ASPI lets you run
L&TT on a locked device without rebooting, but a reboot is required after installing ASPI. The
benefit of using ASPI is not realized the first time L&TT is run, but it is realized on subsequent runs.
One drawback of ASPI is that USB drives are not supported. If you have USB drives, you must
use the Miniport driver.
Beginning with version 4.0, L&TT supports Microsoft Storport technology. Storport is a new
storage driver model created by Microsoft for Windows Server 2003 and future Windows®
operating systems. Storport offers a higher performance architecture and better Fibre Channel
compatibility in Windows systems. If Storport drivers are installed, L&TT automatically uses
Storport when you select Miniport I/O.
NOTE:
ASPI is not officially supported by Windows Server 2003. However, in most cases, it will function
properly. If ASPI is installed with Windows Server 2003, L&TT can make use of it if the ASPI I/O
mode is selected. However, HP recommends that you use the default NT MiniPort I/O option
with Windows Server 2003.
6. Select a destination location to install the program. You can accept the default location or click
Browse to install to a different location. After choosing the destination location, click Next.
7. Indicate the program directory in which you want the setup program to create program icons
and click Next. The program directory is created in the Programs directory of the Start menu.
8. On the Ready to start installation process screen, click Next. If you need to review or change
installation settings, click Back.
9. When installation is complete, click Finish to close the InstallShield wizard.
Library and Tape Tools User Guide
19
Installing L&TT for NetWare
NetWare installation prerequisites
Item
Description
Download link
http://www.hp.com/support/tapetools
Install time
(typical)
Less than 2 minutes
Reboot
requirements
None
Software
dependencies/
prerequisites
• Device should be recognized by NWPA subsystem.
• Device drivers for the connected tape devices/libraries or default device driver should
be present.
• L&TT on NetWare currently does not support clustering configurations.
Known issues
None
Installation procedure
To install the NetWare version of L&TT:
1. Download the L&TT for NetWare file to a temporary directory.
2. From a client workstation, use any standard unzip utility* to extract the file to the SYS:System\
directory on the NetWare server. Make sure that the option to create a directory is enabled
in the archiving software.
NOTE:
* The unzip NLM that comes with later versions of NetWare has not been tested and should not be
used to unzip the archive.
20
Installation
Installing L&TT for HP-UX, Tru64, and Linux
HP-UX installation prerequisites
Item
Description
Download link
http://www.hp.com/support/tapetools
Install time
(typical)
Less than 3 minutes
Reboot
requirements
None
Software
dependencies/
prerequisites
• Devices do not need to be claimed by the operating system with ioscan for L&TT to
access them.
• The sctl driver must be installed for L&TT to access the device you want to test. L&TT
builds its own pass-through SCSI device files using the sctl driver, so that driver must be
installed; however, L&TT does not need the operating system to list any of the devices as
CLAIMED. They may be listed that way (if the appropriate driver is installed), but they
don’t need to be for L&TT to fully access them (beginning with L&TT v3.3).
• Devices must NOT be listed as NO HARDWARE in ioscan. If the device you want to
test with L&TT is listed as NO HARDWARE in ioscan, the communication path between
the host and the device is not working and must be fixed before L&TT will be able
to communicate with the device.
Known issues
To install L&TT 4.0, you must first uninstall any previous versions.
Tru64 installation prerequisites
Item
Description
Download link
http://www.hp.com/support/tapetools
Install time
(typical)
Less than 3 minutes
Reboot
requirements
A reboot occurs only if hardware manager failed to recognize the connected device.
Software
dependencies/
prerequisites
• Device should be recognized by Hardware Manager and SCU subsystem.
• Device drivers for the connected tape devices/libraries or default device driver should
be present.
• L&TT on Tru64 UNIX currently does not support clustering configurations.
Known issues
None
Library and Tape Tools User Guide
21
Linux installation prerequisites
Item
Description
Download link
http://www.hp.com/support/tapetools
Install time
(typical)
Less than 3 minutes
Reboot
requirements
None
Software
dependencies/
prerequisites
• Device should be recognized by proc/SCSI subsystem.
• Device drivers for the connected tape devices/libraries or default device driver should
be present.
Known issues
To install L&TT 4.0, you must first uninstall any previous versions.
Installation procedure
Uninstalling previous versions
Before installing version 4.0 of L&TT on Linux or HP-UX, you must first uninstall any previous versions.
L&TT for HP-UX uses swlist to determine if the tool is already installed. To remove a previous version
of L&TT, use the following command:
swremove HP_LTT<xx>
where <xx> is the version number.
Installing the latest version
To install L&TT for HP-UX, Tru64, or Linux:
1. Log in as root.
2. Navigate to the temporary directory:
cd /tmp
3. Download or copy the L&TT tar file, hp_ltt<xx>.tar (where <xx> is the version number) to
this directory. If you are copying the file from a different location, enter the following (substitute
the directory in which the file currently resides for <directory name>):
cp /<directory name>/hp_ltt<xx>.tar /tmp
NOTE:
The Tru64 tar filename uses the letter “o” in place of zeroes. For L&TT 4.0, the filename is
hp_ltt4ooo.tar.
4. Untar the L&TT tar file:
tar -xvf hp_ltt<xx>.tar
5.
Run the install script in the /tmp directory:
./install_hpltt
6. After the software is successfully installed, enter the following commands to remove the
/tmp/ltt directory and its contents:
cd /tmp
rm -rf ltt
rm -rf install_hpltt
22
Installation
Installing L&TT for HP OpenVMS
OpenVMS installation prerequisites
Item
Description
Download link
http://www.hp.com/support/tapetools
Install time
(typical)
Less than 4 minutes
Reboot
requirements
None
Software
dependencies/
prerequisites
Installation of the initial release of L&TT v3.5 was supported on OpenVMS v7.3-2 only. If
you attempted to install on v7.3-1 you would either get pthread errors, or be informed of the
incompatibility when attempting to install on OpenVMS v7.3-1. This problem was solved to
support both OpenVMS versions with the HotFix 1 release to v3.5 initially, but has since
been incorporated into release v3.5 SR1. It is recommended that you update to the SR1 or
later release to avoid this problem. Furthermore, if you are using OpenVMS v7.3-1, you
must install the VMS731_UPDATE V5.0 (or later) patch for L&TT to work correctly.
The Terminfo database must be installed and the Terminfo environment set up prior to
installing L&TT, otherwise L&TT will not install properly. The Terminfo database was
automatically installed during the L&TT installation beginning with a silent roll to the v3.5
release, but has since been incorporated into release v3.5 SR1. It is recommended that
you update to the SR1 or later release to avoid Terminfo problems.
• If you are using GNV, use this procedure to set up the environment variable:
1. Set the Term to vt100 using the following command at the bash prompt:
"export TERM=vt100"
2. Set the TERMINFO environment variable to indicate the directory path
of the Terminfo database. If the Terminfo database is installed at
/usr/local/share/terminfo, use the following command to set the
TERMINFO variable:
"export TERMINFO=/usr/local/share/terminfo"
• If you are using DCL, use the following procedure to set up the environment variable.
1. Set the Term to vt100 using the following command:
"set term /dev=vt100"
2. If the Terminfo database is installed at sys$device:[usr.local.share.terminfo], use the following command to create a logical name USR:
"define usrsys$device:[usr]"
NOTE:
DCL is the abbreviation for DIGITAL Command Language which is the default
command interpreter for OpenVMS. GNV was developed to provide a UNIX-like
environment on OpenVMS to make it easier for UNIX users to use OpenVMS. GNV
is a separate installation that the user must install explicitly.
Known issues
None
Library and Tape Tools User Guide
23
Installation procedure
NOTE:
L&TT is supported on HP OpenVMS v7.3–1 and 7.3–2.
1.
Download or copy the install file hp-axpvms-ltt-v<xx>-1.pcsi (where <xx> is the version
number) to a temporary directory.
2. Navigate to the directory you copied the install file to and enter the following command to
install L&TT:
product install
The installation procedure creates the directory structure opt.ltt in sys$sysdevice:[vms$common] and installs all the required files for L&TT.
3. Set the term to vt100 using the following command:
set term /dev=vt100
4. Define the logical name USR so that it points to the directory sys$sysdevice:[vms$common.opt.ltt.misc.usr] using the following command:
define usr sys$sysdevice:[vms$common.opt.ltt.misc.usr]
24
Installation
3 Getting Started with L&TT
This chapter describes how to start L&TT and the basic operation of the software. This chapter is divided
into two sections: one for using L&TT in a GUI environment (Windows) and one for using L&TT in a
CSI environment (NetWare, HP-UX, Tru64, Linux, and OpenVMS). To quickly jump to the appropriate
section, click one of the following links:
Windows
NetWare, HP-UX, Tru64, Linux, OpenVMS
Starting L&TT (GUI)
To start L&TT, do one of the following:
• Double-click the L&TT icon on the desktop (if present).
• Click Start > Programs > HP StorageWorks Library and Tape Tools > HP L&TT.
Using the Scan Mode Selection feature
When L&TT is started, the splash screen is displayed. The splash screen gives you the opportunity to
exit the application before any SCSI bus activity occurs. This feature lets you exit the application if it
was started unintentionally. This prevents the program from interfering with any backup or other storage
applications that may currently be running.
Library and Tape Tools User Guide
25
Figure 1 L&TT splash screen
The splash screen also lets you select the initial scan mode and the SCSI I/O mode (if more than one
option is available).
Scan mode
When L&TT starts, it performs a device scan to identify all the devices connected to the computer, either
directly or through a SAN. In large SAN environments, a full scan can take a long time. The first time
L&TT is run, it must perform a full hardware scan (Hardware Scan option), and the Saved/Manual
Scan option is disabled. The results of the full hardware scan are automatically saved, so the next time
L&TT is started, the Saved/Manual Scan option is available.
NOTE:
If you previously selected the Skip this dialog in the future checkbox on the splash screen, L&TT performs
a full hardware scan. To re-enable the splash screen and change the scan option, select Preferences from
the Options menu. Check the Display splash screen at startup option and restart L&TT.
Beginning with L&TT version 3.3, the Skip-Scan feature was introduced allowing you to scan a single
device rather than the entire subsystem. With the release of L&TT 3.5, the Skip-Scan functionality evolved
into the Saved/Manual Scan screen, which allows you to select multiple devices to be scanned. In
addition, device selections are automatically saved and can be reused in a later session.
To access the Saved/Manual Scan screen, select the Saved/Manual Scan option and click Continue
on the splash screen.
26
Getting Started with L&TT
Figure 2 Saved/Manual Scan screen
Using the Saved/Manual Scan screen
The left panel of the Saved/Manual Scan screen displays the devices that were detected in the last saved
scan. If this list is incomplete (for example, if new hardware has been added since the last scan), click
Scan Hardware Now to rescan the system for new devices. If you want to manually add a device to the
list of devices to be scanned without performing a full hardware scan, click Enter Address Manually.
Use the Select All, Remove All, Select, and Remove buttons to select devices. Selected devices are
displayed in the right panel of the screen, and only selected devices will be scanned and identified by
L&TT. Devices that are skipped will not be displayed in the Device List on the L&TT Main screen.
After selecting all of the devices that you want L&TT to scan and identify, click Continue to perform the
scan and proceed to the L&TT main screen. L&TT saves the list of selected devices, so the next time you
start L&TT and display the Saved/Manual Scan screen, L&TT displays all of the previously selected
devices in the right panel.
Using the Skip-Scan feature
The Saved/Manual Scan screen, introduced with L&TT version 3.5, is the preferred interface for
determining how L&TT scans for devices at startup. However, the older Skip-Scan feature is documented
here for users of L&TT versions 3.3 and 3.4. When enabled, the Skip-Scan feature causes L&TT to scan
for the specified device only, rather than the entire bus.
Library and Tape Tools User Guide
27
To use the Skip-Scan feature on Windows:
1. Click Start > Run, and then enter the following into the Run dialog box:
C:\Program Files\HP StorageWorks Library and Tape Tools\HP_LTT.exe —o skipscan
The Skip-Scan dialog box is displayed when L&TT opens.
2. Enter the hardware address of the device you want to scan.
• For NT Miniport I/O mode, the path is in the form <Port Number>/<Bus Number>.<Device
Target ID>.<Device LUN>.
• For ASPI I/O mode, the path is in the form <Bus Number>.<Device Target ID>.<Device LUN>.
Additional device scan considerations
After the initial scan is complete and saved, future full system hardware scans become unnecessary in
most cases. Exceptions are as follows and apply to Windows in NT Miniport I/O mode of operation:
• After the hardware configuration has been changed
• After power cycling more than one of the tape drives on the system
• After updating firmware in more than one of the tape drives on the system
You must perform a hardware scan after any of these actions have occurred. To perform a hardware
scan, exit and restart L&TT. On the splash screen, select the hardware scan option rather than saved
scan. If you do not do this, the Windows operating system might get out of sync with the L&TT saved scan
because Windows device rediscovery assigns new logical device names to the devices.
Also, if you power cycle or update firmware in a device while using a saved scan, the device may not be
accessible until it is rediscovered by Windows. If you are running L&TT v3.5 (or later) and select the
device before it is rediscovered, L&TT generates an error. Previous to v3.5, the device would not have
been identified in the scan, but because the scan is now saved, the device is displayed. After Windows
has rediscovered the device, the device can be selected without causing an error.
If you are running in saved scan mode and want to rescan the bus for devices, clicking the Rescan button
on the Scan tab of L&TT does not initiate a hardware scan. You must exit and restart L&TT, and then
choose the hardware scan option on the splash screen to execute a hardware scan.
I/O mode
L&TT selects the input/output (I/O) mode that is most appropriate for the system it is running on.
However, this initial screen allows for manual selection of the I/O mode in certain cases. L&TT currently
operates in the following two I/O modes:
• NT Miniport—uses an interface that is native to Windows NT 4.0, 2000, XP, and Windows
Server 2003. This is the preferred I/O mode on systems where it is available because it does not
require the installation of the ASPI interface. However, there are some limitations to the Windows
NT Miniport I/O mode related to using devices that are “claimed” by other applications, or
that are used with non-standard OS drivers. In those cases, selecting the ASPI I/O mode can
make a device accessible.
Beginning with version 4.0, L&TT supports Microsoft Storport technology. Storport is a new
storage driver model created by Microsoft for Windows Server 2003 and future Windows®
operating systems. Storport offers a higher performance architecture and better Fibre Channel
compatibility in Windows systems. If Storport drivers are installed, L&TT automatically uses
Storport when you select NT Miniport.
• ASPI—uses an optional I/O programming interface that is available on all versions of Windows.
This I/O mode can be used with any Windows operating system. It may require the installation or
update of additional OS components, possibly requiring a reboot of the system during installation.
28
Getting Started with L&TT
NOTE:
ASPI is not officially supported by Windows Server 2003. However, in most cases, it will function
properly. If ASPI is installed with Windows Server 2003, L&TT can make use of it if the ASPI I/O
mode is selected. However, HP recommends that you use the default NT MiniPort I/O option with
Windows Server 2003.
Skip this dialog in the future
If this checkbox is selected when you click Continue, the splash screen is not displayed on subsequent
uses of L&TT. The program will continue to use the settings that you selected the last time the splash
screen was viewed.
To re-enable the splash screen, select Preferences from the Options menu. Check the Display splash
screen at startup option and restart L&TT.
Application window layout
After the I/O mode is selected, click Continue on the splash screen. The L&TT main screen is displayed.
Figure 3 L&TT main screen
The three sections of the L&TT main screen are:
1.
Taskbar—This section contains buttons that provide quick access to the main functions of L&TT
and to the online help system.
Library and Tape Tools User Guide
29
NOTE:
Above the Taskbar is the standard Windows menu bar that provides alternate navigation to tool
functions, as well as access to a number of other features.
2. Device List—This is a multi-function window that offers several options on the following tabs:
• Scan—This option provides either a summary status or detailed information (depending on
whether Show Details or Hide Details is selected) about the bus scanning process.
If a problem is encountered during the scan, this information may help in determining the
cause. When the scan completes successfully, the device list automatically switches to the
By Product tab.
The Scan tab also lets you rescan the bus. If any devices have been hot-swapped or powered
on after the OS has booted, in most cases, the rescan feature can discover those devices
without requiring a reboot of the system.
CAUTION:
Swapping SCSI devices, including connecting and disconnecting cables and/or terminators, can
cause the system to hang or crash.
CAUTION:
On Windows NT 4.0, 2000, XP, and Windows Server 2003, changing devices at a specific
SCSI address can cause unpredictable behavior. Parts of the operating system may not detect
that the device or device type has changed.
• By Product—This option shows a list of all the products connected to the system. The list is
grouped into the following four categories:
• Libraries and autoloaders
• Drives
• Enclosures and processors
• Other devices
The three number fields listed after the device represent the device address. Each field in the
address is separated by a period: the first field represents the HBA channel, the second field
represents the SCSI ID, and the third field represents the LUN.
NOTE:
When using the Miniport I/O mode, the HBA channel field is shown as “A/B,” where A is the
channel and B is the subchannel.
• By Connection—This option shows all products connected to the system, grouped by the
HBA they are connected to. This view makes it easy to see which devices are connected
to the same bus as the device in question, and may help in understanding system I/O
performance issues.
• Instructions—This window contains brief instructions on how to use the selected screen.
This view can be disabled in the software preferences.
3. Device Information screen—All the main functions of the program are displayed in this window.
The content of this window depends on the device and tool function selected.
30
Getting Started with L&TT
Using the Device Information screen
When you select a product from the Device List, the Device Information screen displays information
relevant to the device. The Device List also changes to display instructions on this page (if the instructions
preference is enabled). If another tool function is currently active, then clicking the Identity button on
the toolbar opens the Device Information screen.
The Device Information screen provides an overview of the selected hardware device and its current
configuration and status.
Standalone devices
The Device Information screen, showing a standalone device, contains a single tab labeled Drive
Information. The Device Information screen has four main sections.
Figure 4 Device Information screen showing a standalone device
Library and Tape Tools User Guide
31
1.
This provides a visual representation of the selected product (the images are in grayscale).
2.
This provides the following general information on the product:
• Product ID (Inquiry String)
• Drive Technology (DDS/DLT/SDLT/VS/LTO)
• Mech Serial # (Drive serial number)
• Firmware Revision
• SCSI Target ID
• SCSI LUN
3.
If a data cartridge was inserted in the drive when the identity tool was selected (or when
the current screen was refreshed), information regarding cartridge type, capacity, and write
protect status is shown here.
4.
Click this button to display a list of media that is compatible with the product.
Library and autoloader products
When a library or autoloader is selected in the Device List, the Device Information screen displays two
tabs: one for library information and one for the drives contained within the library.
Figure 5 Device Information screen showing a library
1.
This provides a visual representation of the selected product (the images are in grayscale).
2.
As with a standalone drive, this area provides the relevant information on the selected library
product.
3.
This provides a cartridge (media) inventory for all the drives and slots. The current status
(full or empty) of all the storage elements and the barcode number (if barcode reading is
available) is displayed here.
32
Getting Started with L&TT
To see information for the drives within the library, select the Drive Information tab. This tab displays a
screen very similar to the one for standalone products, with the addition of the Selected Drive dropdown
menu.
Because a library can contain multiple drives, you can select and view information for each drive using
the Selected Drive dropdown menu. All of the drives in the library are available in the dropdown menu.
Selecting individual drives within a library from the By Product/By Connection device list displays the
drive as though it were a standalone product. The recommended method of diagnosing embedded drives
is to first select the library they belong to, and then select the specific drive within each tool window.
NOTE:
Selecting individual drives within a library from the By Product/By Connection device list displays the
drive as though it were a standalone product. The recommended method of diagnosing embedded drives
is to first select the library they belong to, and then select the specific drive within each tool window.
Library and Tape Tools User Guide
33
Using the Firmware Management screen
The firmware management functionality of L&TT allows easy upgrades to the storage product firmware. To
access the Firmware Management screen, click the device you want to update in the device list, then
click the Firmware button on the main toolbar.
Figure 6 Firmware Management screen
For detailed information about the firmware management functionality of L&TT, see Firmware
Management.
34
Getting Started with L&TT
Using the Tests screen
L&TT provides several standard and advanced tests that can be used to check the performance of or to
diagnose issues with storage hardware. To access the Tests screen, click the device you want to test in the
device list, then click the Tests button on the main toolbar.
Figure 7 Tests screen
For detailed information about the Tests screen, as well as information about how to perform the tests and
interpret test results, see Tests and Utility Functions.
Library and Tape Tools User Guide
35
Using the Support Ticket Generation screen
L&TT can automatically generate a support ticket based on information that the program determines
about the system. The information in this support ticket can then be used to diagnose storage hardware
issues. L&TT can automatically e-mail the support ticket to the HP help desk to assist the help desk
technician in resolving issues.
To access the Support Ticket Generation screen, click the device you want to generate the support ticket
for in the device list, and then click Support on the main toolbar.
Figure 8 Support Ticket Generation screen
For detailed information about generating and using support tickets, see Reports and Support Tickets. For
specific information about the various options found on the Support screen, see Using the Support screen.
Starting L&TT (CSI)
To start L&TT:
• For HP-UX, Tru64, and Linux:
Log on as root and execute the following commands:
cd /opt/ltt
./hp_ltt
• For Novell NetWare
From the server console, execute the following command:
hp_ltt\hp_ltt
36
Getting Started with L&TT
• For HP OpenVMS:
Run hp_ltt.exe found in the sys$sysdevice:[vms$common.opt.ltt] directory.
Navigating the screens
The top line of each screen displays the current screen name in hierarchical format. Each level of screens
is separated by the “>” character. On each screen, some of the available commands take you to a
lower level in the hierarchy. To move back to the previous level, use the up command. To exit L&TT, use
the exit command.
On most of the screens, entering a blank command (pressing Enter without typing any other text) displays
a Command Help screen. This screen contains a list of valid commands that can be executed on the
original screen from which the Command Help screen was accessed.
Figure 9 Command Help screen accessed from the Main screen
It is possible to enter a command directly from the Command Help screen. To do this, type either the
number of the command or the name of the command and press Enter. Entering the number of the
command only works on the Command Help screen. From any other screen, you must type the full name
of the command. To exit the Command Help screen, enter a blank command (press Enter).
Some commands require an argument. For example, the select command requires a number that
corresponds to the device you want to select in the device list. To select the first device in the list, the
syntax is:
select 1
If you enter a command with an invalid or missing argument, an error message is displayed.
Library and Tape Tools User Guide
37
Using the Scan Mode Selection screen
When the CSI version of L&TT is started, the Scan Mode Selection screen is displayed.
Figure 10 Scan Mode Selection screen
When L&TT starts, it performs a device scan to identify all the devices connected to the computer, either
directly or through a SAN. In large SAN environments, this scan can take a long time.
The first time L&TT is run, it must perform a full hardware scan (Hardware Scan option), and the
Saved/Manual Scan option is disabled. The results of the full hardware scan are automatically saved,
so the next time L&TT is started, the Saved/Manual Scan option is available.
If you select Saved/Manual Scan, the Saved/Manual Scan screen is displayed.
Figure 11 Saved/Manual Scan screen (CSI)
38
Getting Started with L&TT
Using the Saved/Manual Scan screen
The Saved/Manual Scan screen lets you select the devices that you want L&TT to scan and identify. This
can save time in a large SAN environment if you are using L&TT to test a single device. Any devices
that are not selected will not be scanned, and they will not be displayed in the Device List on the L&TT
Main screen.
The following command options are available:
•
•
•
•
•
•
•
•
•
select—The indicated device or devices will be scanned.
selectAll—All devices will be scanned.
clear—The indicated device or devices will not be scanned.
unselectAll—Clears all devices. No devices will be scanned.
enterHWAddrManual—Lets you manually enter the hardware address of a device to be
scanned.
hardwarescan—Performs a full hardware scan. Use this option to update the list of available
devices on the Saved/Manual Scan screen.
continue—Starts the indicated scan and proceeds to the Main screen.
up—Exits the current command level.
exit—Exits L&TT.
When the scan is complete, the Main screen is displayed.
Figure 12 CSI Main screen
Using the Skip-Scan feature
The Saved/Manual Scan screen, introduced with L&TT version 3.5, is the preferred interface for
determining how L&TT scans for devices at startup. However, the older Skip-Scan feature is documented
here for users of L&TT versions 3.3 and 3.4. When enabled, the Skip-Scan feature causes L&TT to scan
for the specified device only, rather than the entire bus.
To use the Skip-Scan feature on HP-UX, Linux, NetWare, or Tru64 UNIX:
1. Execute the following commands to launch L&TT with the Skip-Scan feature enabled:
• For HP-UX, Tru64 UNIX, and Linux, log on as root and execute the following commands:
cd /opt/ltt
Library and Tape Tools User Guide
39
./hp_ltt —oskipscan
• For Novell NetWare, execute the following command from the server console:
hp_ltt\hp_ltt —oskipscan
2. At the prompt, enter the hardware address of the device that you want to scan.
Using the Device Information screen
When you first select a product from the Main screen, the Device Information screen is displayed,
showing information relevant to the device.
The main purpose of the Device Information screen is to provide an overview of the configuration and
status of the selected hardware device.
From the Main screen, type the following command to access the Device Information screen:
select <n> (where <n> is the number of the device to be examined)
NOTE:
Alternatively, you can omit the select command and only enter the device number.
Standalone devices
Figure 13 Device Information screen for a standalone device
The following general information is displayed:
•
•
•
•
•
•
•
40
Product ID (inquiry string)
Drive technology
Mech. serial # (drive serial number)
Firmware revision
SCSI target ID )
SCSI LUN
OBDR capability (if present)
Getting Started with L&TT
If a data cartridge was inserted in the drive when the Device Information screen was displayed,
information regarding cartridge type, capacity, and write-protect status is shown.
To see a list of compatible media that can be used with this device, use the cartridge command.
Library and autoloader products
Figure 14 Device Information screen for a library
NOTE:
Selecting individual drives within a library from the device list displays the drive as though it were a
standalone product. Embedded drives are best diagnosed by selecting the library they belong to, and
then selecting the specific drive within each tool window.
From the Device Information screen for a library device, use the cartridge command to display the
slot inventory of the library. The cartridge command shows which slots and drives currently have
cartridges loaded, and the cartridge barcode if available and applicable.
Library and Tape Tools User Guide
41
42
Getting Started with L&TT
4 Firmware Management
The Firmware Management functionality of L&TT provides a convenient way to easily upgrade the
firmware of connected devices. Library firmware and firmware of drives within the libraries can be
upgraded as well.
L&TT uses special firmware files that associate the firmware with a particular product. This feature prevents
the user from downloading the wrong image and ensures that the downloaded firmware is the same or a
newer revision than the current device firmware.
CAUTION:
Do not use L&TT to update firmware on a tape library or devices within a tape library that is managed
with HP StorageWorks Command View for Tape Libraries Software (Command View TL). Firmware
update operations for these devices must be performed using Command View TL, as documented in the
HP StorageWorks Interface Manager and Command View for Tape Libraries Software user guide. If
L&TT is used to update firmware on a managed library, the management station will be out of sync with
the actual firmware revision number and will report a firmware mismatch. Furthermore, if you attempt to
use L&TT to update firmware on a partitioned library, L&TT reports an invalid command error.
Accessing firmware revision and release note information
(GUI)
To verify that you have the latest firmware revision for a device, or to learn about the changes between
your current revision and the latest revision, use the Get Files from Web feature of L&TT.
To Access firmware revision and release note information from the L&TT application (Windows):
1. In the L&TT main screen, click File > Get Files From Web, or click the Firmware button on the menu
bar, select the Local Firmware Files tab, and then click Get Firmware From Web. The Get Files
From Web window opens.
2. To view the latest firmware revisions for devices on your system, or for all devices, click the Firmware
tab (if not already displayed), and then click the appropriate radio button.
3. To view release note information, click the product ID of the firmware file whose information you
want to view, and then click the Details button. If release notes are available, they are displayed
in the File Details window.
To access firmware revision and release note information from the L&TT application (HP-UX and Linux):
NOTE:
The download function is not supported with NetWare, OpenVMS, or Tru64 UNIX.
1. On the L&TT main screen, enter download.
A required file from the HP FTP site is downloaded, and the Download Tool screen opens. The status
area at the bottom of the screen displays the progress of the download.
2. In the Download Tool area, enter 5 at the command prompt. The Selector screen displays the various
firmware files. Review the list and note the latest firmware revision for your product.
3. To review release note information, enter the number of the file whose release note information you
want to view. Use the ^U or ^D commands to page up or down through the screens to find the
desired product and firmware file. Not all firmware files have release note information available.
Library and Tape Tools User Guide
43
Acquiring firmware files (GUI)
L&TT firmware files are stored in the Firmware directory. This directory is a subdirectory of the
HP Library & Tape Tools installation directory. Before upgrading any firmware, you must first
acquire the firmware image file or files and copy them to the Firmware directory. Firmware files can
be obtained in three ways:
1.
Select the device in the device listing and click Firmware on the main toolbar. On the Firmware
screen, click the Local Files tab, and then click the Get Files from Web button at the bottom of the
tab. The downloaded files are automatically placed in the Firmware directory.
2. From the L&TT menu, select Get Files From Web from the File menu. The software links to the
L&TT firmware FTP site and allows the selected firmware files to be copied to your system.
Downloaded files are automatically placed in the Firmware directory. This option is explained
in detail in the following section.
3. Go to http://www.hp.com/support, choose the product family, then click software updates
and drivers. The latest firmware file is available in L&TT format. For some products (such as
standalone drives), firmware is available as a single file. For other products (such as tape
libraries), the firmware is available in a self-extracting bundle that includes library and drive
firmware.
CAUTION:
Do not use the Get Files From Web functionality within L&TT without an Internet connection. Doing
so can cause the system to lock up until it has timed out in the operating system. This timeout value
is operating system-specific.
NOTE:
If Check for Updates on Web is enabled in the tool preferences, L&TT automatically informs the
user when new firmware is available for any of the connected storage products. L&TT performs this check
each time it is started (but not more than once per 24-hour period).
Using the Get Files from Web functionality (GUI)
The Windows version of L&TT offers comprehensive firmware management functionality that finds and
downloads firmware from the HP website. This functionality obtains the most up-to-date information
about all available firmware files directly from the HP website. It then compares this data set against
the list of devices connected to the system and the current firmware revisions present in those devices.
Depending on the selected filter options on the top of the screen, different subsets of firmware files are
presented. Firmware files that are needed to bring the connected devices up to the latest firmware
revisions are automatically selected.
Accessing the Get Files from Web dialog box
You can access the Get Files from Web dialog box in two ways:
• Select Get Files from Web from the File menu
• Click the Get Firmware button on the Firmware Update screen
The Get Files from Web dialog box is displayed. Click the Firmware (New Files Available) tab if it is
not already selected.
44
Firmware Management
Figure 15 Get Files from Web dialog box—Firmware tab
Selecting and downloading updated firmware files
The Get Files from Web dialog box has four filter options:
• For devices on this system—These two options only show firmware files matching devices that are
currently connected to the system.
• Show latest firmware only shows the most recent firmware revision for each device.
• Show all firmware shows all firmware revisions for each of these firmware files.
• For all supported devices—These two options show firmware files for all devices supported by LTT,
even if not currently connected to the system.
• Show latest firmware only shows the most recent firmware revision for each device.
• Show all firmware shows all firmware revisions for each of these firmware files.
Select the appropriate option, and then verify that the correct firmware files are selected. To download
the selected files, click Download. The files are automatically downloaded to the current firmware
directory on the local system. You can now use the firmware update functionality of L&TT to upload the
latest firmware to your devices.
Library and Tape Tools User Guide
45
Viewing firmware revision history
In addition to downloading firmware files, the Get Files from Web dialog box provides revision history
detail for firmware files. To view the firmware revision history of a device, select a device and click Details.
Uploading firmware to devices (GUI)
Before attempting to update any firmware files, you must first acquire the latest firmware files and ensure
that they are placed in the Firmware directory. If you have not yet done this, see Acquiring firmware
files (GUI).
To upload firmware to a device:
1. Click the device to update in the device list.
2. Click Firmware on the main toolbar.
3. On the Update Firmware tab, click the checkbox to select each device for which you want to
update firmware. If firmware is currently available for that device, it is shown in the Firmware
File dropdown box in the File Selection section of the screen.
Figure 16 Firmware Update screen
NOTE:
With several products, after the firmware file is selected, a message is displayed to inform you
of certain requirements such as important prerequisites for updating with the new firmware, or
noteworthy functional changes (such as a new LED sequence). Be sure to read any such messages
and take any appropriate actions.
4. Click the Start Update button at the bottom of the screen to begin the update.
46
Firmware Management
CAUTION:
Make sure that no other programs attempt to access the device while the firmware is being updated.
Do not interrupt the firmware update. If the firmware update is interrupted, the device may not
operate and require physical repair.
When the firmware update is complete, the Firmware Update window opens, explaining what
may happen related to the Windows plug-and-play implementation. It also explains how to make
the drive visible to L&TT and the Windows operating system, so that it will operate properly.
If the device is not visible to L&TT and/or the operating system after you have successfully
updated the firmware, follow the process indicated in the Firmware Update window to ensure
the updated device is fully visible to and usable by the system. Make sure you follow this entire
procedure before calling HP customer support. If you have followed the procedure, and your
device is still not accessible, call HP customer support for assistance.
L&TT creates a log of all firmware update activity. To view this log, click the Firmware Update Results tab.
Set the Current Detail Level setting to the appropriate level. The default is Normal. The firmware
log is displayed in a standard tree-view format. If you want to clear the log, click the Clear Log button.
Advanced options (GUI)
It is sometimes necessary to disable L&TT safeguards to perform more advanced operations. These
operations (options) are only available after the necessary password has been entered. To obtain this
password, contact HP support. After a password has been entered, the Options button on the Update
Firmware tab becomes available. When you click this button, the Factory Firmware Overrides dialog box
is displayed (this dialog box varies slightly between drives and libraries):
Figure 17 Factory Firmware Overrides dialog box
The Factory Firmware Overrides dialog box presents the following three options:
• Allow firmware downgrading—By default, L&TT does not show files with older revision
levels as selectable. On the Local Firmware Files tab, the comment field displays the message
“downgrade password required.” In most cases, you should use the latest firmware. However, if
software incompatibilities or other customer limitations require the use of older firmware revisions,
this checkbox lets you downgrade to older firmware revisions.
• Allow selection of any [drive or library] firmware file—This option allows
mapping of the device firmware to a product, irrespective of the device’s product ID. There are a
few cases in which the product ID does not match the desired firmware file (and the ID may also
need to be updated). One case is when a library is being updated from one drive technology
to another. Another case is when the device has a firmware revision string format that differs
Library and Tape Tools User Guide
47
from that in the firmware file, and the tool cannot determine whether it is newer or older. If
incompatible firmware is sent to a device, an error message is displayed.
• Update [drive or library] product ID—This writes the product ID from the firmware
file to the drive.
NOTE:
A number of products may not support updating the product ID, so use this feature only when you know
the device supports it. The most common use of this feature is when updating drive technologies in
optical libraries.
Acquiring firmware files (CSI)
L&TT firmware files are stored in the firmware directory, which is a subdirectory of the HP Library &
Tape Tools installation directory. Before upgrading any firmware, you must first acquire the firmware
image file or files and copy them to the firmware directory.
To download the latest firmware files:
1.
Go to http://www.hp.com/support, choose your region, and then select storage for the product
category.
2. Select the product family, and then the particular product.
3. In the I would like to box, click download drivers and software.
4. Select the product and operating system, and then click the download button in the firmware
section. The download file may be a single file (standalone drives) or a self-extracting bundle
that includes both automation and standalone drive firmware.
5. Download the file or files to the firmware directory. If it is a self-extracting bundle, extract the
contents to the firmware directory.
Using the Get Files from Web functionality (CSI)
NOTE:
Downloading firmware files from the Web using the L&TT application is not supported with NetWare,
OpenVMS, or Tru64 UNIX.
The CSI version (HP-UX and Linux) of L&TT can also find and download firmware from the HP website.
This functionality obtains the most up-to-date information about all available firmware files directly from
the HP website. It then compares this data set against the list of devices connected to the system and the
current firmware revisions present in those devices.
To use the Get Files from Web functionality:
1.
From the Main screen, enter the download command. The Download Tool screen displays a
list of download options.
2. Enter the number of the desired option. If a download option is selected, the Selector screen
displays a list of available firmware files to download.
3. Enter the number of the desired firmware file to download. The file is downloaded to the
firmware directory.
48
Firmware Management
Uploading firmware to devices (CSI)
To upload firmware to one or more devices:
1.
From the Main screen, type the number corresponding to the device to be updated and press
Enter to display the Device Information screen.
2. From the Device Information screen, enter the firmware command to display the Firmware
Update screen. Devices that are available for update are listed on this screen.
3. Type the corresponding number of the device you want to update and press Enter to mark
the device selected. If there are multiple devices, repeat this step for each device that you
want to update.
4. When all the required devices are selected, enter the start command to begin the update
process.
CAUTION:
Make sure that no other programs attempt to access the device while the firmware is being updated.
Do not interrupt the firmware update. If the firmware update is interrupted, the device may not operate
and require physical repair.
L&TT creates a log of all firmware update activity. To view this log, enter the review command from
the Firmware Update screen.
Advanced options (CSI)
Sometimes it is necessary to disable L&TT safeguards to perform more advanced operations. These
operations (options) are only available after the necessary password has been entered. To obtain this
password, contact HP support. To view the Options screen, from the Firmware Update screen, enter the
options command.
Before any of the options can be changed, the current password must be set. To set the password:
1.
Type the number that corresponds to the password option and press Enter. L&TT prompts you to
enter a value for Current password entered.
2. Type the password and press Enter. If the correct password is entered, the remaining options
on this screen become available.
NOTE:
All of the options are visible regardless of whether a proper password is entered or not. However, the
options are not available for selection without the proper password. After a proper password has
been entered, it is not required to re-enter it later.
The following options are available:
• Allow firmware downgrading—By default, L&TT does not allow firmware downgrading. In
most cases, you should use the latest firmware. However, if software incompatibilities or other
customer limitations require the use of older firmware revisions, this option lets you downgrade
to older firmware revisions.
• Allow any firmware file for [drives or libraries]—This option allows
mapping of the device firmware to a product irrespective of the device’s product ID. There are a
few cases in which the product ID does not match the desired firmware file (and the ID may also
need to be updated). One case is when a library is being updated from one drive technology
to another. Another case is when the device has a firmware revision string format that differs
Library and Tape Tools User Guide
49
from that in the firmware file, and the tool cannot determine whether it is newer or older. If
incompatible firmware is sent to a device, an error message is displayed.
• Allow Product ID updates on [drives or libraries]—This writes the product ID
from the firmware file to the drive.
• Current password entered—This option lets you enter the factory password. The currently
entered password is displayed to the right of the option. If no password has been entered,
Not Set is displayed.
NOTE:
A number of products may not support updating the product ID, so use this feature only when you know
the device supports it. The most common use of this feature is when updating drive technologies in
optical libraries.
Using a firmware update (FUP) tape
The preferred method for updating drive firmware is by using the L&TT application. Firmware can be
updated on both Windows and non-Windows platforms. However, there are some cases where L&TT
is not available, or otherwise cannot be used (for example, with an unsupported operating system). In
these cases, a firmware update (FUP) tape can be created and used for the purpose of updating drive
firmware. In most cases, FUP tapes can be created by HP and supplied to end users, or be created
by the end users themselves.
When using L&TT to update firmware, there are protections in place to ensure that only the correct
firmware is downloaded to the drive. There is no such protection mechanism with a FUP tape, so care
must be taken to use the FUP tape only with the drive it is intended for.
Performing the update
The procedure for using a FUP tape varies depending on the drive type, and in some cases, whether
or not the drive is in an autoloader or library. Click the appropriate drive type below to get the details
associated with using a FUP tape for that drive.
•
•
•
•
•
•
SDLT
DLT VS80/DLT1
DLT 4000/7000/8000
Ultrium
HP DDS/DAT
Compaq/Sony AIT & DDS
SDLT
Standalone SDLT drives
There is no hard coded limit as to how many times a given SDLT FUP tape can be used to update the
firmware in a particular SDLT drive type. To update the firmware in an SDLT drive using a FUP tape, you
first have to put the drive in FUP tape mode. This is accomplished as follows:
1. Unload any tape currently in the SDLT drive.
2. With no tape in the drive, push and hold the eject button. After approximately five seconds, the left
LED begins to flash.
3. Release the eject button, and then push it again. The middle LED will also start flashing.
4. Release the eject button. The drive is now ready to accept the FUP tape.
5. Insert the FUP tape into the drive. It does not matter if the tape is write protected or write enabled.
50
Firmware Management
CAUTION:
Do not power cycle or reset the drive. Make sure that no software attempts to access the
drive during the firmware update process. Otherwise the drive may be damaged and
need to be returned to HP for replacement.
NOTE:
If the drive is not put into FUP tape mode before you insert the FUP tape, it will not be
recognized as a FUP tape. If the FUP tape is not write protected, you will be able to write
over the FUP tape (but not append to it).
6. When the firmware update process is complete, the drive ejects the FUP tape and performs a self test.
7. Store, return, or dispose of the FUP tape as required. To convert the FUP back into a data tape, see
Converting a firmware update tape to a data tape.
Libraries and autoloaders
Use of FUP tapes in STK libraries works just like it does for standalone drives, so see the description
above for that information.
For HP libraries:
1. Ensure the target drive is empty. If a tape is in the target drive, use the front panel display to return
the tape to a storage slot.
2. Load the FUP tape into an empty slot.
3. From the main menu on the front panel, choose Administration, and then Upgrade Firmware to
access the Upgrade Drive Firmware menu.
4. Use the [-] or [+] key to select the slot containing the FUP tape. Select [OK].
5. Monitor the front panel for status during the upgrade. The tape will return to the original slot when
the procedure is complete.
6. Remove the FUP tape from the library, and then power cycle the library.
DLT VS80/DLT1
Standalone VS80/DLT1 drives
There is no hard coded limit as to how many times a given DLT VS80/DLT1 FUP tape can be used
to update the firmware in a particular DLT VS80/DLT1 drive type. To update the firmware in a DLT
VS80/DLT1 drive using a FUP tape, you first have to put the drive in FUP tape mode. To do this:
1. Unload any tape currently in the DLT VS80/DLT1 drive.
2. With no tape in the drive, push and hold the eject button. After approximately five seconds, the left
and right LEDs light.
3. Continue to hold the eject button depressed until all the LEDs go out.
4. Immediately release the eject button. The middle LED will light.
5. Push and release the eject button. All LEDs will start flashing. The drive is now ready to accept the
FUP tape.
6. Insert the FUP tape into the drive. It does not matter if the tape is write protected or write enabled.
Library and Tape Tools User Guide
51
CAUTION:
Do not power cycle or reset the drive. Make sure that no software attempts to access the
drive during the firmware update process. Otherwise the drive may be damaged and
need to be returned to HP for replacement.
NOTE:
If the drive is not put into FUP tape mode before you insert the FUP tape, it will not be
recognized as a FUP tape. If the FUP tape is not write protected, you will be able to write
over the FUP tape (but not append to it).
7. When the firmware update process is complete, the drive ejects the FUP tape and performs a self test.
8. Store, return, or dispose of the FUP tape as required. To convert the FUP back into a data tape, see
Converting a firmware update tape to a data tape.
Libraries and autoloaders
Use of FUP tapes in STK libraries works just like it does for standalone drives, so see the description
above for that information.
For HP libraries:
1. Make sure that the target drive is empty. If a tape is in the target drive, use the front panel display
to return the tape to a storage slot.
2. Load the FUP tape into an empty slot.
3. From the main menu on the front panel, choose Administration, and then Upgrade Firmware to
access the Upgrade Drive Firmware menu.
4. Use the [-] or [+] key to select the slot containing the FUP tape. Select [OK].
5. Monitor the front panel for status during the upgrade. The tape will return to the original slot when
the procedure is complete.
6. Remove the FUP tape from the library, and then power cycle the library.
DLT 4000/7000/8000
Standalone VS80/DLT1 drives
There is no hard coded limit as to how many times a given DLT 4000/7000/8000 FUP tape can be used
to update the firmware in a particular DLT 4000/7000/8000 drive type. To update the firmware in a DLT
4000/7000/8000 drive using a FUP tape, you first have to put the drive in FUP tape mode. To do this:
1. Unload any tape currently in the DLT 4000/7000/8000 drive, and then lower the operator handle.
2. With no tape in the drive, push and hold the unload button. After approximately five seconds,
the Write Protect LED begins to flash.
3. Release the unload button and immediately press it again. The Tape In Use LED will now also flash.
4. Release the unload button. The drive is now ready to accept the FUP tape.
5. Lift the operator handle, insert the FUP tape into the drive, and then lower the operator handle. It
does not matter if the tape is write protected or write enabled.
52
Firmware Management
CAUTION:
Do not power cycle or reset the drive. Make sure that no software attempts to access the
drive during the firmware update process. Otherwise the drive may be damaged and
need to be returned to HP for replacement.
NOTE:
If the drive is not put into FUP tape mode before you insert the FUP tape, it will not be
recognized as a FUP tape. If the FUP tape is not write protected, you will be able to write
over the FUP tape (but not append to it).
6. When the firmware update process is complete, the drive ejects the FUP tape and performs a self
test. Lift the operator handle and remove the FUP tape.
7. Store, return, or dispose of the FUP tape as required. To convert the FUP back into a data tape, see
Converting a firmware update tape to a data tape.
Libraries and autoloaders
Use of FUP tapes in STK libraries works just like it does for standalone drives, so see the description
above for that information.
For HP libraries:
1. Make sure that the target drive is empty. If a tape is in the target drive, use the front panel display
to return the tape to a storage slot.
2. Load the FUP tape into an empty slot.
3. From the main menu on the front panel, choose Administration, and then Upgrade Firmware to
access the Upgrade Drive Firmware menu.
4. Use the [-] or [+] key to select the slot containing the FUP tape. Select [OK].
5. Monitor the front panel for status during the upgrade. The tape will return to the original slot when
the procedure is complete.
6. Remove the FUP tape from the library, and then power cycle the library.
Ultrium
Standalone Ultrium drives
There is no hard-coded limit as to how many times a given Ultrium FUP tape can be used to update the
firmware in a particular Ultrium drive type. To update an Ultrium drive with a FUP tape, insert the tape
into the Ultrium drive. It does not matter if the tape is write protected or write enabled. HP Ultrium drives
automatically recognize a valid FUP tape when inserted and begin updating the firmware. When the
firmware update process has completed, the tape is ejected, and the drive executes a self test.
CAUTION:
Do not power cycle or reset the drive. Make sure that no software attempts to access the drive during
the firmware update process. Otherwise the drive may be damaged and need to be returned to HP
for replacement.
NOTE:
Ultrium FUP tapes can be converted back to data tapes via the LTO Firmware to Data Tape Creator
test. See that test description for details.
Library and Tape Tools User Guide
53
Libraries and autoloaders
Use of FUP tapes in STK libraries works just like it does for standalone drives, so see the description
above for that information.
For HP libraries:
1. Make sure that the target drive is empty. If a tape is in the target drive, use the front panel display
to return the tape to a storage slot.
2. Load the FUP tape into an empty slot.
3. From the main menu on the front panel, choose Administration, and then Upgrade Firmware to
access the Upgrade Drive Firmware menu.
4. Use the [-] or [+] key to select the slot containing the FUP tape. Select [OK].
5. Monitor the front panel for status during the upgrade. The tape will return to the original slot when
the procedure is complete.
6. Remove the FUP tape from the library, and then power cycle the library.
HP DDS/DAT
Standalone DDS/DAT drives
DDS FUP tapes that are created using the firmware tape creator test can be used 1000 times. Drives that
can be updated via an FUP tape are HP DDS4 (C5683A) and HP DAT72 (C7438A). Updating drive
firmware via FUP tape is not supported on other HP DDS/DAT drives.
To update DDS/DAT drive firmware with a FUP tape, ensure that the tape is write enabled, and then
insert it into the DDS/DAT drive. HP DDS/DAT drives automatically recognize a valid FUP tape when
inserted, and begin updating the firmware. When the firmware update process has completed, the
tape is ejected, and the drive executes a self test.
CAUTION:
Do not power cycle or reset the drive. Make sure that no software attempts to access the drive during
the firmware update process. Otherwise the drive may be damaged and need to be returned to HP
for replacement.
NOTE:
DDS/DAT FUP tapes cannot be converted back to data tapes. After a FUP tape is created, it can only be
used as a FUP tape and cannot be written to again.
Libraries and autoloaders
Updating DDS/DAT autoloaders using a FUP tape is not currently supported.
Compaq/Sony AIT & DDS
Standalone DDS/DAT drives
There is no hard-coded limit as to how many times a given Compaq/Sony AIT/DDS FUP tape can
be used to update the firmware in a particular drive type. To update AIT/DDS drive firmware with a
FUP tape, ensure that the tape is write protected, and then insert it into the AIT/DDS drive. The drive
automatically recognizes a valid FUP tape when inserted, and begins updating the firmware. When the
firmware update process has completed, the tape is ejected, and the drive executes a self test.
54
Firmware Management
CAUTION:
Do not power cycle or reset the drive. Make sure that no software attempts to access the drive during
the firmware update process. Otherwise the drive may be damaged and need to be returned to HP
for replacement.
NOTE:
DDS/DAT FUP tapes cannot be converted back to data tapes. After a FUP tape is created, it can only be
used as a FUP tape and cannot be written to again.
Libraries and autoloaders
The process for updating drive/autoloader firmware via FUP tape is the same as documented above for
standalone AIT/DDS drives.
Converting a firmware update tape to a data tape
In many cases, FUP tapes can be converted back to a regular data tape. The method of doing this
varies depending on the drive type.
• DLT 4K/7K/8K, SDLT, and VS80/DLT1 tapes can be converted back to data tapes by making
sure they are write-enabled, inserting them into a drive, and then writing to them.
• LTO drives require the LTO Firmware to Data Tape Creator test to convert a FUP tape back to a
data tape.
• HP StorageWorks and Surestore DDS, AIT, and Compaq/Sony DDS drives cannot convert FUP
tapes back to data tapes.
Library and Tape Tools User Guide
55
56
Firmware Management
5 Tests and Utility functions
L&TT provides numerous tests for analyzing storage hardware. These tests are grouped into two
categories: diagnostic tests and performance tests. The performance tests are built into the program, but
several of the diagnostic tests are SCSI script-based. A SCSI script is a sequence of SCSI commands
sent to a device, usually for the purpose of testing the device’s functionality. SCSI scripts can also be
used to perform non-diagnostic utility functions, such as rewinding a tape, recalibrating a tape head, or
exercising a tape-moving robot arm.
L&TT uses the following types of SCSI scripts:
• Script-based tests are tests based on scripts that are stored in the scripts directory in the L&TT
installation directory. The script-based test files can have the *.tst, *.plg, *.pmg *.smd,
or *.rul extension.
• SCSI utility scripts provide access to generic SCSI operations. These scripts are accessed by
selecting Run Script... from the Utilities menu and have the *.scc or *.cps extension. For more
information, see Using the utility functions (GUI).
NOTE:
Each script file contains information that tells L&TT which devices it is designed to support. When a
device is selected, the Tests screen displays only tests that are applicable to that particular device.
NOTE:
All scripts have a digital signature and cannot be altered. If they are altered in a text editor, L&TT
displays an error message stating that the digital signature is not correct.
Library and Tape Tools User Guide
57
Running the tests (GUI)
To select and run a test manually:
1. In the device listing (either the By Product or By Connection tab), click the device to test.
2. Click Test on the main toolbar. The Tests screen is displayed and the Test Execution tab is
selected by default.
3. Click the checkbox to the left of the device name that you want to test. The Test Group dropdown
box is enabled, listing all the tests available for the selected device.
4. In the Test Group dropdown box, select the test to perform. A description of the selected test is
displayed in the Description text box.
5. If any options are available for the selected test, the Options button is enabled. Click the Options
button to review and set the desired options.
6. Click the Start Test button to start the test.
Viewing test results
After the test has completed, click the Test Results tab to view the results. The results of the test are
displayed in the Test text box. A more detailed Test Operation Log is displayed in the bottom section of
the screen. The information is presented as a report in a standard tree-view format. Click the “+” or “–”
signs to expand or collapse a section of the report. Select an option in the Current Detail Level dropdown
box to display more or less information in the Test Operation Log.
Running the tests (CSI)
To select and run a test manually:
1.
2.
3.
4.
5.
6.
On the Main screen, enter the number corresponding to the device that you want to test. The
Device Information screen is displayed.
On the Device Information screen, enter the test command. The Test screen is displayed. The
Test screen displays the currently selected test and lists the available devices to be tested.
To select a different test, enter the picktest command. On the Selector screen, enter the
number of the test you want to perform. The Test screen is redisplayed and the currently selected
test is updated.
To select or deselect devices to be tested, enter the corresponding device number to toggle the
selected status of the device. To deselect all devices, enter the clear command.
Enter the start command to start the test.
When the test is complete, a dialog is displayed showing preliminary results of the test. Press
any key to return to the Test screen.
Viewing test results (CSI)
To view detailed test results, enter the review command. Test results are displayed in a hierarchical
format.
Use the detail command without any arguments to view the current detail level of the report. Use the
detail command with a numeric argument to set the detail level. The available detail level arguments
are as follows:
•
•
•
•
•
58
1 — highlights only
2 — normal
3 — more details
4 — everything
5 — factory only (requires a factory password. To enter a password, use the options command.)
Tests and Utility functions
If necessary, use Ctrl+U and Ctrl+D to scroll up and down through the results. Use the find and page
commands to quickly locate information in the report.
Test descriptions
This section lists the available tests.
CAUTION:
Some tests are destructive to data on the media. When a test is destructive to data, this is indicated in the
test description. To prevent data loss, use media that is either new or that contains unimportant data that
can be erased. Do not attempt to perform a test unless you are thoroughly familiar with its usage, or
have been instructed to do so by HP support personnel.
• PerformanceTests
• DiagnosticTests
Performance tests
• Drive Performance Test writes data to a tape drive and calculates the performance of that drive
independently from the disk file system. Use this test in conjunction with the System Performance
Test to identify any system bottlenecks. Use a blank tape when performing this test because this
test is destructive to data on the tape. The test can also measure tape drive read performance. This
test is available for all tape drives. For more information, see Using the Drive Performance Test.
• System Performance Test has two modes: The backup pre-test measures the read performance of
the disk file system (simulating a backup), and the restore pre-test measures the write performance
of the disk file system (simulating a restore). Use these tests in conjunction with the Drive
Performance Test to identify any system bottlenecks. The backup pre-test is read-only and is safe to
run on any part of your file system. The restore pre-test creates data in the specified directory
and can also be used to create test data for general backup testing. For more information, see
Using the System Performance Test.
Diagnostic tests
NOTE:
L&TT tests are constantly being updated to improve test coverage and problem diagnosis. As new device
issues are discovered, changes are made to the tests to properly diagnose those issues. Prior to L&TT
v3.5 SR1, updates to some tests and test scripts were occasionally made available for download from the
L&TT website using the Get Files from Web function. Subsequent to the release of L&TT v3.5 SR1, test
script updates are now only distributed with updates to L&TT or with a hot fix distribution. To ensure
that you have the latest available test scripts, keep your version of L&TT up to date and download
updates and hot fixes when they are made available.
Library and Tape Tools User Guide
59
NOTE:
The tests in this section are listed alphabetically. Click the hyperlink to view the test description.
Acceptance test
Assessment test
Autoloader Exerciser test
Connectivity test
Data Compression test
Device Analysis test
Firmware Tape Creator
Full Sweep test
Initialize Element Status test
Installation Check test
Library Exerciser test
LTO Cooling Check test
Device Self-Test
LTO Firmware to Data Tape
Creator test
LTO Stuck Tape test
Media Analysis test
DLT SRAM Check test
ESL Vendor ID test
Media Erase test
Media Validation test
MO Media Validation test
Read/Write Stress test
Read/Write test
Restore Factory Default Settings
test
SDLT Read Media IDs test
SDLT Tape Edge Damage test
Acceptance test
Beginning with L&TT v3.5 SR1, the Acceptance tests have been replaced with the Assessment tests. If
you are using any diagnostic tools or documentation that recommend running the Acceptance test, you
should run the Assessment test instead.
60
Tests and Utility functions
Assessment test
CAUTION:
This test is destructive and will overwrite data on the media that is present in your product.
Library and Tape Tools User Guide
61
Description
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
NOTE:
In versions of L&TT prior to 3.5 SR1, this test was called the Device Acceptance test.
NOTE:
In the L&TT test menu, the Assessment test may be prefixed with the device type. For
example: SDLT Assessment test.
The Assessment test determines if the drive or autoloader is Fit for Purpose (FFP). A device
that is determined to be FFP performs according to its specification. If a device fails the
Assessment test, it should be replaced. If it passes, the problem is likely not with the health
of that device. If a device is returned, the results of this test are compared to repair data to
ensure accuracy and enable test improvements to be developed.
NOTE:
If the test is being run on an autoloader and it is configured in circular or stacker
mode (dependent on the particular autoloader), when an unload command is
received from the host (such as is issued with the Assessment test), the autoloader
moves the next available cartridge into the drive. If the magazine is not loaded with
data cartridges and cleaning cartridges in the correct order to meet the needs of
the test, the test will fail. HP recommends using the single cartridge process when
running the Assessment test on an autoloader.
DLT, DLT1, VS80, VS160, and SDLT Assessment tests performed:
• SCSI interconnect test
• Review event log entries (which were present prior to running this test)
• Load the test tape
• Quick write/read test
• Soft unload/load test (DLT assessment test only)
• Minimum block size test
• Diagnostic self test (built-in drive function)
• Read/write tests, using various data patterns
• Bit error rate test
• Review new event log entries added during the test
• Unload the test tape
LTO Assessment tests performed:
NOTE:
There was a problem with a log sorting routine for LTO in the Device Analysis scripts
and Acceptance test in the L&TT v3.5 initial release. The misleading results could
make drives appear faulty when they are good, and vice-versa. HP recommends that
you install L&TT v3.5 SR1 or later to avoid this problem.
•
•
•
•
•
•
•
•
62
Initial preparation
Review event log entries (which were present prior to running this test)
SCSI parity check (LTO 1 drives only)
Cartridge load
Quick read/write test
Cartridge unload
SCSI parity check
Review new events
Tests and Utility functions
Description
(cont’d)
DDS Assessment tests performed:
NOTE:
The DDS acceptance script was inadvertently excluded from the original L&TT v3.5
build. HP recommends that you install L&TT v3.5 SR1 or later to ensure that you have
the DDS Drive Assessment test.
• Review event log entries (which were present prior to running this test)
• Check life data in the serial EEPROM and the fault log
• Load check
• Perform a clean and write test
• Unload check
• MRS switch test
• Read check
• Review new events
1/8 Autoloader Assessment tests performed:
• Review robotics error log entries
• Run appropriate drive assessment test on the drive
• Check for new robotics error log entries
• Perform 12 to 24 drive loads and unloads (depending on drive type)
• Check for new robotics error log entries
Options
Options are available for the SDLT Assessment test and the LTO Assessment test.
SDLT Assessment test options:
If you want to test for tape edge damage on an SDLT 110/220 drive, enable the Media
Test option (False by default). Tape edge damage has been shown to be caused by
certain older SDLT 110/220 drives.
If you enable this option, it will not run the standard Assessment test, but rather a specific
test to analyze the tape by looking at data accumulated by the drive during writing. The
objective of the test is to identify any tapes that may have edge damage. Beginning with
L&TT v3.5, at the conclusion of the media test, L&TT may ask you to disable the Media
Test option and rerun the Assessment test, dependent on the results of that test. This test
option was formerly called the Drive/media Interaction test.
LTO Assessment test options:
For the LTO test, the following four options are available:
• Enable Device Analysis: True by default
• Enable SCSI Controller Test: True by default
• Enable Write/Read Test: True by default
• Ignore Cleaning Requests: False by default
When to run
Run this test if you suspect a drive has failed. You should run the Media Test option if
running an SDLT 220 drive and you suspect the drive may be damaging media, or if
directed to do so by an HP tool or support person.
Average
duration
Test times vary greatly depending on drive type, media quality, and options selected.
Average time for a healthy drive with good tape can range from 10 to 20 minutes. A
marginal drive (or drive with marginal tape) may take substantially longer. Average
duration for the SDLT Acceptance test Media Test option is 15 minutes, but it can take
longer with a bad tape.
Other notes
Requires good tape that will be overwritten as part of test.
Available for
•
•
•
•
•
•
•
DLT 4000/7000/8000
DLT1/VS80/VS160
SDLT 220/320/600
Ultrium-1, Ultrium-2, Ultrium-2/Ultrium-3 Half-Height drives (448)
LTO1 (Ultrium 215 and 230), LTO 2 (Ultrium 460) drives, and LTO3 drives (Ultrium 960)
DDS3, DDS4, and DAT72 (pre- and post-merger HP drives only)
1/8 Autoloader
Library and Tape Tools User Guide
63
Autoloader Exerciser test
Description
Checks the mechanics of your DDS autoloader.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test when you want to verify that the mechanics of your DDS autoloader are
working properly.
Average
duration
~10 minutes
Other notes
Test will not overwrite any data on the media.
Available for
DDS autoloaders
Connectivity test
Description
Writes data to the internal buffers in your product to verify that the physical connection
between your host and the storage device is operational. No media is required.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test when there is a question about the integrity of the bus connection from the
device to the host computer.
Average
duration
< 1 minute
Other notes
Test will not overwrite any data on the media present in the drive.
Available for
AIT, DDS, DLT, LTO, VS80/VS160, MO, STK 9840 drives and MSL libraries
Data Compression test
CAUTION:
This test is destructive and will overwrite data on the media that is present in your product.
Description
Tests the hardware compression capability of your tape drive. The test writes a data
pattern of known compressibility to tape. The test then rewinds the tape and reads the file
just written. The read and write hardware compression ratios are calculated to ascertain
that the hardware compression is enabled and working. The compression ratios are
displayed and should be approximately 2:1. This test is useful if tape capacity or hardware
compression is in doubt.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test when you want to verify that data compression is working properly.
Average
duration
< 10 minutes
Other notes
Test will overwrite all data on the media.
Available for
All tape products (drive and automation) supported by L&TT
64
Tests and Utility functions
Device Analysis test
Description
The Device Analysis test runs a device-specific script that carries out a detailed examination
of the device. The test examines all available logs from the device to look for any known
issues, customer use issues, and common error patterns. The test also provides summary
information and presents suggestions as to the cause of certain errors and any remedial
actions the user should take. This option is particularly useful if you suspect that there may
be a problem with the device. For more information, see Using the Device Analysis Test.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test when you want to verify that basic functions of the device are operating
properly and have not logged any critical errors, and to verify that firmware is up-to-date.
Average
duration
< 1 minute
Other notes
Test does not change the configuration of the drive or media.
Available for
All devices supported by L&TT.
Device Self-Test
Description
This test executes the internal self-test of the device and reports any failures. This test is
useful in confirming that the device itself is operating properly. Not all devices support
an internal self-test.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test as a quick check of the integrity of the device.
Average
duration
< 1 minute
Other notes
Test will not overwrite any data on the media, should there be any present in the drive.
Available for
AIT, DDS, DLT, SDLT, VS80/VS160 or DLT1, LTO autoloaders and drives, ESL, MSL, C7200,
C7145, C5177, C1194F, C5151, C5173, C6280, SSL 1016 and STK libraries, STK
9840 drives, MO drives & libraries, and A6356A Fibre Channel management card
DLT SRAM Check test (short and long versions)
CAUTION:
These tests are destructive and will overwrite data on the media that is present in your product.
Library and Tape Tools User Guide
65
Description
These tests check DLT 8000 drive logs for evidence of SRAM chip corruption, and they
perform a read/write test to check the drive for susceptibility to SRAM corruption problems.
The tests are destructive to data on the cartridge in the drive. These tests are only available
for DLT drives.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run the short version of the test when you suspect the drive may be responsible for CRC
errors and want to do a quick test to verify. Run the long version to perform a more
extensive analysis.
Average
duration
~20 minutes (short version), or up to 1.5 hours (long version)
Other notes
You must have a write enabled tape in the drive and the drive must be ready before starting
this test, or it will fail. Test will overwrite all data on the media.
Available for
DLT 8000
ESL Vendor ID test
Description
Toggles the Vendor ID in an ESL library between HP and Compaq.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test to change the vendor ID, which may be required for some applications to
work properly.
Average
duration
< 1 minute
Other notes
Test requires firmware version 3.40 or later.
Available for
ESL libraries
Firmware Tape Creator (FUP tape) test
Description
Lets you create a firmware update (FUP) tape on your drive. A FUP tape is a tape that is
created when a firmware file for a particular drive type is written onto a blank tape.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test when you want to create a firmware update (FUP) tape to update drive
firmware.
Average
duration
< 2 minutes
Other notes
This utility expects to find a firmware image file (firmware.frm) in your firmware
directory. You must create this file yourself by obtaining the correct firmware file for your
device, renaming it to firmware.frm, and copying the file to your firmware directory.
Available for
DAT72 (C7438A), DDS4 (C5683A), DLT 4000/7000/8000, LTO, SDLT, VS80/160 or
DLT1
66
Tests and Utility functions
Full Sweep test
Description
This test script moves the robotics through the full range of motion to help prevent reliability
issues with the brush tracks. This test is available for the C7200 and C7145 library models.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test if the results of a Device Analysis test recommend that you run this test. This
recommendation is based on reviewing library log data for certain critical errors, including
those related to issues with the brush tracks.
Average
duration
Up to 2.5 hours, depending on whether the long or short test is selected.
Other notes
Test will not overwrite any data on the media. Data from this test is logged into the library
for future use by support personnel.
Available for
C7145 and C7200 libraries.
Initialize Element Status test
Description
This test script executes an initialize element status command on the library,
which instructs the library to perform an inventory of all its elements.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
When cartridges have been manually removed, use this test script to initialize the library.
Average
duration
Depending on the library, this test may take over 30 minutes.
Other notes
Test will not overwrite any data on the media.
Available for
All libraries supported by L&TT.
Library and Tape Tools User Guide
67
Installation Check test
Description
The Installation Check is not executed in the same way that the other L&TT tests are. Rather,
it is run automatically when L&TT starts in Installcheck mode. Installcheck mode is a feature
of the Windows version of L&TT. For information on starting L&TT in Installcheck mode,
see Using the Installation Check feature.
When run in Installcheck mode, L&TT checks the installation of selected devices. L&TT
performs several tests on each selected device to determine if the device is configured
optimally. In addition, L&TT performs connectivity and configuration tests on all supported
devices that are configured on the system. These tests cannot be overridden. All of the tests
performed during the installation check can also be run manually with L&TT. L&TT displays
the results of each test and any recommendations.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run L&TT in Installcheck mode when you want to verify the correct configuration of
supported devices.
Average
duration
Other notes
When L&TT is run in Installcheck mode, the Installation Check wizard is displayed. After
the selected tests are complete and the results are displayed, the wizard closes, which
also closes L&TT. If you want to restart L&TT, launch it as you normally would (without the
mode=installcheck argument if you are starting it from the command line).
Available for
The installation check feature is currently supported on the following devices:
• HP Ultrium drive (L&TT 3.4 and later)
• HP SDLT 320 drive (L&TT 3.5 and later)
• HP VS80 drive (L&TT 3.5 and later)
Library Exerciser test
CAUTION:
This test is destructive and will overwrite data on the media that is present in your product.
Description
This is a general-purpose test of the library. It includes tests for moving cartridges within
the library, loading cartridges into each one of the drives, and performing a short test of
the drive while the cartridge is loaded. Test options include test time limits, slot and drive
ranges, drive type selection, barcode checking, cartridge memory checking (in the case of
LTO drives within the library), options for drive, and cartridge loading, and test coverage.
For more information about test options, see Using the Library Exerciser Test.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test to verify that the library is functioning properly.
Average
duration
Highly dependent on the library being tested and options selected.
Other notes
Test can overwrite data on the media, depending on which test options are selected.
Available for
Not all libraries are supported by the Library Exerciser test. If the test is not displayed in the
drop-down list of tests, then the selected device is not supported.
68
Tests and Utility functions
LTO Cooling Check test
Description
This test monitors the temperature sensors of an LTO drive while writing data to ensure that
the drive is cooling properly when installed in a server.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test if you suspect thermal problems with your LTO drive.
Average
duration
Other notes
Available for
LTO drives
LTO Firmware to Data Tape Creator
CAUTION:
This test is destructive and will overwrite data on the media that is present in your product.
Description
This test script converts a previously created firmware upgrade tape back to a normal
data tape on your Ultrium drive.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test script when you want to convert an Ultrium FUP tape back to a data tape.
Average
duration
< 2 minutes
Other notes
Test will overwrite all data on the media.
Available for
LTO drives only
LTO Stuck Tape test
Description
This test tries to determine if the cartridge in the drive is physically stuck, or if it can be
unloaded and recovered.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test only if you suspect that the cartridge is stuck.
Average
duration
Other notes
Available for
Standalone LTO drives only
Library and Tape Tools User Guide
69
Media Analysis test
Description
This test determines if the drive can read the data on any media currently in the drive.
The test is helpful in determining the quality of the media. However, the results are also
dependent on the drive’s ability to read the media, and therefore the error rate measured
is a combination of the drive’s ability to read and the quality of the media. If the drive’s
health is not known, the Read/Write Test (used with known good media) can be used first.
For more information, see Using the Media Analysis Test.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test when you want to verify the integrity of the data on a particular piece of
media, as read by a particular drive.
Average
duration
< 5 minutes, using default test options
Other notes
Test is non-destructive and will not overwrite any data on the media. Supports several test
options to limit the data (size, time, and so on) or verify the entire tape (whole tape option).
Available for
LTO, DDS, AIT, DLT, SDLT, VS80/160 or DLT1, and STK 9840 drives
Media Erase test
CAUTION:
This test is destructive and will overwrite data on the media that is present in your product.
Description
This test converts a DDS or LTO data tape into a blank tape. This test has the following
three options:
• Quick erase—This option, which takes approximately one minute to complete,
removes the tape directory and writes EOD at the start of the tape, but it does not
overwrite the data on the remainder of the tape.
• Full erase—This option, which takes between two to four hours to complete, erases
the tape directory and also overwrites all data on the tape.
• Secure erase—This option, which takes between 10 to 20 hours to complete,
performs a full erase followed by a rewind. It repeats this four more times for a total
of five full erases.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test script when you want to erase a tape that has been previously written.
Average
duration
Quick erase takes about one minute. Full erase takes from 2 to 4 hours. Secure erase
takes between 10 to 25 hours.
Other notes
Any data on tape will no longer be accessible after this test.
Available for
DDS, Ultrium 1 and 2
70
Tests and Utility functions
Media Validation test
Description
This test reads data on the tape cartridge, magneto-optical (MO), or ultra-density optical
(UDO) media in your storage device. No writes are performed so data contents of media
are not changed in any way. Supports several test options for MO and UDO media (data
limit options, starting block, block size, failure threshold, and so on), but none for tape.
The test also runs a self test and cleaning check, and prompts for cleaning cartridge if
it deems necessary (tape only).
NOTE:
For some devices, the Media Validation test has been superseded with the Media
Analysis test.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test when you suspect a problem with your media.
Average
duration
< 5 minutes using default test options, but dependent on the amount of data on the media.
Can take longer if media is full.
Other notes
Test requires that a minimum amount of data is already written on the media, otherwise the
test will fail. The amount of data varies depending on drive technologies and options (in
the case of MO media).
Available for
AIT, DDS, DLT, SDLT, VS80/160 or DLT1, LTO, and STK 9840 tape drives, MO and UDO
optical drives.
MO Media Validation test
Description
This test validates magneto-optical (MO) or ultra-density optical (UDO) media and reports
any errors or blank spaces present in the media, if any. This is a non-destructive test and is
available for all MO and UDO devices.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test when you suspect a problem with your MO or UDO media.
Average
duration
< 5 minutes using default test options, but dependent on the amount of data on the media.
Can take longer if media is full.
Other notes
Test requires that a minimum amount of data is already written on the media, otherwise the
test will fail. The amount of data varies depending on drive technologies and options.
Available for
MO and UDO optical drives
Library and Tape Tools User Guide
71
Read/Write Stress test
CAUTION:
This test is destructive and will overwrite data on the media that is present in your product.
Description
This test performs a self-test on the LTO drive, then an extensive write-read media test, and
a load/unload test and cleaning tape check. Test options allow the user to select some
options for amount of data written and read, whether a load/unload test is performed, and
whether a cleaning tape check is performed.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
Options
• Enable 32GB Test (default is on)—When used together with the Enable 4GB
Test option, tests 36GB. This option can be disabled if a shorter duration test is
desired.
• Enable Load/Unload Test (default is off)—Used to test the load/unload function
in standalone drives. This option must be off for automation products, or if you want to
run unattended as the unload and load takes place towards the middle of the test.
• Enable 4GB Test (default is on)—When used together with the Enable 32GB
Test option, tests 36GB.
• Ignore Cleaning Requests (default is off)—If this option is on, the test initially
requests a cleaning, and it also requests one during the testing if it determines one
is needed. When this option is off, the drive never requests a cleaning during the
entire test.
When to run
This is a very extensive test and would not normally be run except as directed by HP
support engineers.
Average
duration
> 4 hours
Other notes
Test will overwrite all data on the media.
Available for
LTO drives only
Read/Write test
CAUTION:
This test is destructive and will overwrite data on the media that is present in your product.
72
Tests and Utility functions
Description
This test performs a self-test on the drive device, then a write-read media test to verify the
ability to read and write data to and from the removable media in your storage device. This
test also checks error rates and fails if allowable limits are exceeded. Test options allow the
user to select the amount of data or length of test time, the amount of data transferred per
command, and the data pattern. For more information, see Using the Read/Write Test.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test to verify the integrity of a particular piece of media, as written and read by a
particular drive, and to verify the ability of the drive to read and write data independent of
the storage application.
Average
duration
< 10 minutes, using default test options
Other notes
Test will overwrite all data on the media.
Available for
All devices supported by L&TT
Restore Factory Default Settings
Description
Checks current configuration parameters of an MO drive and identifies any that differ from
factory defaults. If any differences are detected, the test can reset to factory defaults.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Device Analysis test results will recommend running this test if abnormal (not default)
settings are detected. Abnormal settings do not necessarily mean there is a need to set
them to default values. For example, the user may want certain drive settings to be different
from the default values, so in that case it is better to not run this test. However, you may
also want to try restoring defaults when you suspect configuration parameters that could be
adversely impacting operation may have been changed.
Average
duration
< 1 minute
Other notes
None
Available for
4X, 8X, and 14X MO drives
Library and Tape Tools User Guide
73
SDLT Read Media IDs test
Description
This is a non-destructive test that loads each tape in the library into a drive and reads the
media ID. At the conclusion of the test, click the Test Results tab to see the media ID, slot
number, and barcode of each piece of media in the library. Normal usage for the Read
SDLT Media IDs test is in conjunction with the SDLT Tape Edge Damage test to identify the
location of tapes in a library with tape edge damage.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
After the SDLT Tape Edge Damage Test has identified that one or more tapes in the library
need to be replaced.
Average
duration
45 to 50 seconds per tape (typical)
Other notes
This test assumes that the SDLT tapes have the proper barcode labels with S as the 7th
character, that the SDLT drives have the latest firmware, and that the library is configured
to show all barcode labels. Otherwise, the tapes may not be recognized with this test. If
the Ignore barcode labels when selecting tapes option is set to True, then
the barcodes are ignored. If this option is set to False, then the barcodes are required as
described above. The default setting for this option is False.
Additionally, the library must be configured to automatically unload the tape when it is
being moved from a drive. For MSL libraries, the Unload Mode option (under the Library
Options screen) must be set to implicit. For ESL9000 libraries, the Auto Drive Unload
option (under operator/configure options) must be enabled.
Available for
ESL9000 and MSL libraries with SDLT 230, SDLT 320, or SDLT 600 drives
74
Tests and Utility functions
SDLT Tape Edge Damage (TED) test
Description
This is a non-destructive test that determines if any SDLT cartridges with tape edge damage
are present in an ESL9000 or MSL library. If the test passes, there are no tapes in the
library with TED symptoms. If it fails, evidence of tapes with TED has been found and a
message is displayed indicating that the user should run the SDLT Read Media IDs test test
to locate the specific tapes with TED in the library. The message also instructs the user to
contact HP support to identify if any of the drives have the potential to cause tape edge
damage, and to have them replaced if any are identified.
If the TED test fails, do the following:
1. Click the Test Results tab to view the analysis results.
2. Record the IDs of any tapes identified for replacement. Note that one or more IDs
may be listed more than once because the same tape may be identified as needing
replacement in more than one drive in the library.
3. Run the Read SDLT Media IDs test. This test provides a list of each tape in the
library along with its location and barcode information. Match the IDs you recorded
previously to the list to identify which tapes to replace.
NOTE:
For instructions on how to perform this test, see Running the tests (GUI) or Running
the tests (CSI).
When to run
Run this test whenever you suspect symptoms of tape edge damage, or as directed by HP
support personnel.
Average
duration
< 1 minute (see SDLT Read Media IDs test for duration of that test)
Other notes
• This test assumes that the SDLT tapes have the proper barcode labels with S as the 7th
character, that the SDLT drives have the latest firmware, and that the library is configured
to show all barcode labels. Otherwise, the tapes may not be recognized with this test.
• If this test is run on a library with no SDLT 220 or SDLT 320 drives, it will not fail, nor
will it check anything. It will return “There were no errors identified” in this case.
• Although primarily intended for libraries, this test is also supported on SDLT 220 and
320 standalone drives. For standalone drive testing, run Device Analysis on the drive to
get the media ID of the currently loaded tape.
Available for
ESL 9000 and MSL libraries with SDLT 230, SDLT 320, or SDLT 600 drives; and SDLT 230,
SDLT 320, or SDLT 600 standalone drives
Library and Tape Tools User Guide
75
Using the Drive Performance Test
The Drive Performance test writes and reads data to/from the specified tape drive and calculates
performance data for that drive. The results of the test are shown on the Drive Performance Results
tab and also written to the event log.
To start the Drive Performance test (Windows version):
CAUTION:
This test is destructive to data on the tape. To avoid loss of data, use a blank tape when performing
this test.
NOTE:
In the following procedure, a suggested starting value is given for most parameters. These are not
necessarily default values, but they are general values that will result in a simple, representative test. Use
them as a starting point, and modify them according to your needs.
NOTE:
The Drive Performance test is unavailable with ASPI I/O mode. You must use NT Miniport I/O mode to
perform this test.
1. In the device listing (either the By Product or By Connection tab), click the drive to test.
2. Click Dev Perf on the main toolbar. The Drive Performance screen is displayed and the Tape
Drive Performance tab is selected by default.
Figure 18 Drive Performance screen
76
Tests and Utility functions
3. In the Test Logic section of the screen, use the drop down boxes to select a data type for each
of the four tests. The Drive Performance test is actually a series of four write/read subtests
(labeled Step 1-4 on the Drive Performance screen) that measure performance using different
types of data that you can specify.
The following data types can be selected:
• Zeros
• 1.6:1 Compression
• 2:1 Compression (suggested starting value)
• 3:1 Compression
• 4:1 Compression
You must specify a data type for Step 1, but you can choose not to perform Steps 2 through 4
by selecting No Test in the corresponding dropdown box (suggested starting value for steps 2
through 4 is No Test).
4. Specify the following additional parameters:
• Block Mode—choose one of the following (suggested starting value is Fixed):
• Fixed—the test uses a fixed block size (length) that can be specified in the Block Size
dropdown box.
• Variable—the test uses a different mode of data transfer. When this option is selected,
the Block Size dropdown box is disabled.
• Block Size—if Block Mode is set to Fixed, then specify the size of the data blocks used
in the test. Data blocks can be from 16K to 256K (suggested starting value is 64K). This
dropdown box is disabled if Block Mode is set to Variable.
• I/O Size—the maximum amount of data to be transferred by a single read/write
operation. This length is typically a multiple of the Block Size and ranges from the specified
Block Size to 1MB (suggested starting value is 1MB).
• Test Size—the maximum amount of data written/read by the test. Valid choices range
from 1GB to 15GB. Larger values increase the time required to perform the test, but they
produce more accurate test results (suggested starting value is 4GB).
• File Mark Mode—instructs the test to write a filemark at the specified interval (1MB to
1GB). You can also instruct the test not to write any filemarks (suggested starting value is
No filemarks).
• Read After Write—when enabled, data is written to the tape and then the tape is read
back. When disabled, only write performance is measured. The test evaluates two sets of
metrics when enabled, and one when disabled (suggested starting value is disabled).
• Rate Limiting—if rate limiting is enabled, the I/O rate is limited to the specified value
(suggested starting value is disabled).
5. Click Start to perform the test. Progress of the test is displayed in the status bar to the right of the
Start button, and a dialog box will inform you when the test is complete.
6. Click the Drive Performance Results tab to view the results of the test.
To start the Drive Performance test (CSI version):
1.
Use the select command to select the device to be tested.
select <n> (where <n> is the number of the device to be examined)
NOTE:
The devperf command is not available until a device is selected.
2. From the Main screen, enter the devperf command to display the Device Performance Tool
screen. The Device Performance Tool screen displays several test options with their default
settings.
Library and Tape Tools User Guide
77
Figure 19 Device Performance Tool screen
3. If necessary, change the settings for one or more options. To change the settings, enter the
number that corresponds with the option that you want to change. Enter the new value at the
prompt. The five available options for this test are:
• Blocksize—specify the blocksize, in bytes, to be written to the tape. Typical values are
32768 (32KB), 65536 (64KB). The default is 65536.
• Repetitions—specify how many write/read operations to perform. The default is 4096.
• Readback—specify whether to enable the readback test after writing data to the device.
This option measures read performance in addition to write performance in MB/sec. This
option is disabled by default.
• Count—specify how many blocks to write to the tape device per write operation. The
default is 16.
• Pattern—specify the data pattern to be written to tape. Enter 2 for 2:1 compression ratio
or 3 for 3.1:1 compression ratio. The default is 2.
4. Use the start command to start the test.
78
Tests and Utility functions
Using the System Performance Test
The System Performance Test has two modes: The backup pre-test measures the read performance of the
disk file system (simulating a backup), and the restore pre-test measures the write performance of the
disk file system (simulating a restore). Use these tests in conjunction with the Drive Performance Test to
identify any system bottlenecks. The backup pre-test is read-only and is safe to run on any part of your
file system. The restore pre-test creates data in the specified directory and can also be used to create
test data for general backup testing.
Performing the System Performance Restore Pre-Test (GUI)
NOTE:
In the following procedure, a suggested starting value is given for most parameters. These are not
necessarily default values, but they are general values that will result in a simple, representative test. Use
them as a starting point, and modify them according to your needs.
1. Click Sys Perf on the main toolbar. The System Performance screen is displayed.
2. Click the Restore Pre-Test tab.
Figure 20 Restore Pre-Test tab of the System Performance screen
3. Specify the following parameters:
• Test Path—enter the destination directory (or use the Browse button to browse to the
directory) that the test will write data to. This should be a directory on the backup server
being tested. Make sure that the path is on the restore destination disk to measure the real
data rate. Use a directory name that you can find easily such as C:\Test so that you
can easily delete the data later.
• Test Data Type—select the type of data pattern to be written. Choose from the following
options:
• Fixed Byte
Library and Tape Tools User Guide
79
•
•
•
•
• Incrementing
• Random
• Uncompressible Data
• 2:1 Compression Ratio (suggested starting value)
• 3:1 Compression Ratio
• 4:1 Compression Ratio
File Size—use the two dropdown boxes to specify a range of possible file sizes for the
test data (suggested starting value is to use the default value).
File Tree Depth—specify the number of levels of subdirectories the program will create
from the specified directory (suggested starting value is 5).
File Tree Breadth—specify the number of directories to be created within each
subdirectory (suggested starting value is 5).
Files Per Directory—specify the number of files to be created within each
subdirectory (suggested starting value is 50).
NOTE:
The gauges in the Disc Capacity section of the screen show the amount of disk space required for
the System Performance test using the current settings, and the amount of space available in the
indicated filesystem. If the required space exceeds the available space, the Test Size gauge displays
OVERFLOW, and you will be unable to start the test.
4. Click Start to perform the test. Progress of the test is displayed in the status bar to the right of the
Start button, and a dialog box will inform you when the test is complete.
5. Click the System Performance Results tab to view the test results.
Performing the System Performance Backup Pre-Test
This test reads data from up to four separate locations on the file system. The reads are concurrent and
simulate up to four concurrent backup data streams. The performance of these reads is measured and
reported in the System Performance Results tab. Use this test to measure the performance of the file system
to be used for backup. Use this test in conjunction with the Drive Performance Test to identify performance
bottlenecks in the system. This test is read-only and can be safely run on backup source data.
NOTE:
In the following procedure, a suggested starting value is given for each parameter. These are not
necessarily default values, but they are general values that will result in a simple, representative test. Use
them as a starting point, and modify them according to your needs.
1. Click Sys Perf on the main toolbar. The System Performance screen is displayed.
2. Click the Backup Pre-Test tab.
80
Tests and Utility functions
Figure 21 Backup Pre-Test tab of the System Performance screen
3. Specify the following parameters:
• Read Size—enter the maximum block size (in bytes) to transfer (suggested starting value
is 512K).
• Directory Traverse Method—specify one of the following options (suggested starting
value is depth):
• Specify Depth to have the test read as far down the directory structure as possible
before moving laterally to the next directory.
• Specify Breadth to read all directories at the same level before moving down to the
next subdirectory level.
• Stop After—specify a time limit for the test, or select “All Readers Complete” to continue
testing until the test is complete (suggested starting value is 5 minutes).
• Reader [1-4]—enter up to four target directories (use the Browse button to browse to
each directory) that the test will read data from. For each Reader, you must have first
performed a Restore Pre-Test. Use the same directory or directories that you specified
in the Restore Pre-Test(s).
The number of readers to use depends on your backup application. If the application uses
concurrent read streams, then select multiple readers. To guarantee an accurate measure of
the access rate of the real data, point each reader at the data that each stream will back up.
• Read Files—specifies whether the files must be read back from the tape after the write
completes (suggested starting value is to select this option).
4. Click Start to perform the test. A dialog box will inform you when the test is complete.
5. Click the System Performance Results tab to view the test results.
Performing the System Performance Pre-Tests (CSI)
To start the CSI version of the System Performance Pre-Test:
Library and Tape Tools User Guide
81
NOTE:
The System Performance Pre-Tests (backup and restore) are not available for NetWare.
1. From the Main screen, enter the sysperf command to display the System Performance screen:
2. Enter one of the following commands (depending on which pre-test you want to run):
• backup—runs the Backup Pre-Test
• restore—runs the Restore Pre-Test
3. If necessary, change the settings for one or more options. To change the settings, enter the
number that corresponds with the option that you want to change. Enter the new value at
the prompt.
Figure 22 Backup Pre-Test screen (CSI)
The two options available for the Backup Pre-Test are:
• Blocksize—specify the blocksize, in bytes, to be read. Typical values are 32768 (32KB),
65536 (64KB). The default is 65536.
• Path—specify the path to the directory to be read from.
82
Tests and Utility functions
Figure 23 Restore Pre-Test screen (CSI)
The following options are available for the Restore Pre-Test:
• Filesize—specify the size, in bytes, of the test files to be created.
• Number of Files—specify the number of files to be created.
• Directory path—specify the path of the directory where the test files will be written. This
should be a directory on the backup server being tested. Make sure that the path is on the
restore destination disk to measure the real data rate. Use a directory name that you can find
easily such as C:\Test so that you can easily delete the data later.
• Pattern—specify one of the following data patterns:
• Fixed byte
• Incrementing byte
• Random data
• 1.6:1 compressible data
• 2:1 compressible data (suggested starting value)
• 3.1:1 compressible data
• 4.3:1 compressible data
4. Use the start command to start the test.
Using the Device Analysis Test
The Device Analysis test can be executed manually through the Tests screen or automatically whenever
a support ticket is generated. The Device Analysis test is unique among all the tests offered by L&TT.
In addition to performing SCSI operations directly on a device, the Device Analysis test uses a set
of predefined, device-specific rules to analyze device logs and configurations. If any known issues
are discovered during the analysis, the user is notified of the problem and the program suggests an
appropriate course of action.
The Device Analysis test automates failure analysis of a device by determining whether a known or
unknown problem with a device exists, if the problem can be resolved in the field through maintenance or
simple repair, and whether a device needs to be returned or serviced.
Library and Tape Tools User Guide
83
Using the Read/Write Test
The Read/Write test writes and reads data from tape and checks for accuracy. In addition to verifying
that the data read back matches the data written, the read/write error rates are also checked. The test
fails if the error rates exceed allowable limits. This test can be used to verify the ability of the drive to
read and write data independent of the storage application. This test is available for all tape drives.
CAUTION:
Use a blank tape when performing this test because this test is destructive to data on the tape.
The following options are available for this test:
• Test Time Limit—specify the time limit in minutes. Enter 0 for no time limit.
• Data Limit Type—specify one of the following options to limit the amount of data
written/read in each phase:
• Time—limits the amount of data tested based on the time specified in Data Time Limit.
• Size—limits the amount of data tested based on the size specified in Data Size Limit.
• Whole tape—limits the amount of data tested based on the size of the tape.
• Data Size Limit—specify the size limit in megabytes of data to be written/read in each
phase.
• Data Time Limit—specify the time limit, in minutes, for each phase of the test.
• Block Size—specify the block size, in kilobytes, to be used in the test.
• Transfer Size Limit—specify the maximum data transfer limit, in kilobytes, per command.
• Block Transfer Type—specify whether to use a fixed or variable block length.
• Data Pattern Type—indicates the type of data pattern used in the test. Specify one of the
following data pattern types:
• Pattern File—uses a preset pattern
• Random—generates random patterns
• User defined—uses a user-defined string
• Data Pattern—specify a string value to use as a data pattern if the Data Pattern Type is
set to “User Defined.”
Using the Media Analysis Test
The Media Analysis test reads data from the media and calculates the error rate. If the error rate
exceeds the maximum allowable threshold, the test will require a cleaning cartridge and a second tape
to determine if the problem is with the drive or the tape. No data is written to tape and the test is not
destructive to data. This test is useful if the user suspects that a backup failed because of a bad tape.
This test is available for all tape drives.
The following options are available for this test:
• Test Time Limit—specify the time limit in minutes. Enter 0 for no time limit.
• Data Limit Type—specify one of the following options to limit the amount of data read
in each phase:
• Time—limits the amount of data read based on the time specified in Data Time Limit.
• Size—limits the amount of data read based on the size specified in Data Size Limit.
• Whole tape—limits the amount of data read based on the size of the tape.
• Amount of data read in each phase—specify the size limit in megabytes of data to be
read in each phase.
• Time allowed for each data test phase—specify the time limit, in minutes, for each
phase of the test.
• Transfer Size Limit—specify the maximum data transfer limit, in kilobytes, per command.
84
Tests and Utility functions
Using the Library Exerciser Test
The Library Exerciser test takes a test cartridge from a mail slot and performs random slot-to-slot moves.
The test then moves the test cartridge into every available drive and performs a short drive test. This test is
intended to exercise the robotics and robot drive hardware.
NOTE:
Not all libraries are supported by the Library Exerciser test. If the test is not displayed in the drop-down
list of tests, then the selected device is not supported.
The following options are available for this test:
• Test Time Limit—specify the time limit in minutes. Enter 0 for no time limit. The default
setting is 0.
• Move Command Timeout—specify the maximum time allotted, in seconds, for each move
command before failure. The default is 600 seconds.
• Active Slot Range—specify a range of slots to be tested. Enter a range of slot numbers
separated with a dash (for example: 2-5), or enter all to specify all slots. The default is all.
• Active Drive Range—specify a range of drives to be tested. Enter a range of drives
separated with a dash (for example: 2-5), or enter all to specify all drives. The default is all.
• Drive Type Option—specify the type of drives to be tested (in libraries that have mixed drive
types). Enter the type of drive (for example: LTO or DLT), or enter all to test all drive types. The
default is “all.”
• Check Inventory Mode—specify whether to perform an active inventory check at beginning
of the test. The active inventory check can take a long time to perform. The default is on.
• Barcode Mode—specify how barcodes are handled. Choose one of the following options:
• Show all—shows all barcodes
• Show suspect—shows only suspect barcodes (default)
• Off—does not show barcodes
• Slot-to-Slot Moves—select one of the following options for the slot-to-slot test:
• All—moves all cartridges
• Random—moves randomly selected cartridges (default)
• Off—no cartridges are moved
• Random Coverage—when Slot-to-Slot Moves is set to Random, specify the percentage of units
covered during random test. The default is 20%.
• Drive Load Mode—specify whether or not to perform the Drive Load test. The default setting
is on.
• Drive Test Option—if the Drive Load test is enabled, specify one of the following options:
• Off
• Data loop back (default)
• Read-only
• Read/write
• Cartridge Load Test—specify one of the following options for the Cartridge Load test:
• Off (default)
• Single drive
• Multiple drives
• All drives
• CM Integrity Mode—specify whether to enable the CM integrity check option for LTO drives.
The default setting is on.
Library and Tape Tools User Guide
85
Using the utility functions
Utility functions execute the SCSI utility scripts (files with a .scc extension) stored in the scripts
directory. These scripts send various SCSI commands to the selected device, but they generally do
not return any results.
Many of the utility functions are device-specific and intended only to remedy specific problems that may
occur with a particular device.
CAUTION:
Using a script improperly or when it is not required can cause harm—possibly rendering a device
inoperable. Do not attempt to use these utility functions unless you are very familiar with SCSI operation,
or you have been advised to do so by a technical support representative or a Device Analysis script.
To use a utility function with the Windows version of L&TT:
1. Select Run Script... from the Utilities menu to display the Run Script dialog.
2. In the Devices section, click the check box next to the device on which you want to run the script.
The device logical name is now assigned.
3. Click Browse to select a script file to execute. The utility scripts are located in the scripts
directory and have an .scc extension.
4. Select a script and click Open to return to the Run Script dialog.
5. Click Run Script.
When the script has completed, relevant information is displayed in the Script Output and Script
Execution Log text boxes.
To use a utility function from the CSI:
1.
2.
3.
4.
5.
6.
7.
86
On the Main screen, enter the number corresponding to the device that you want to test. The
Device Information screen is displayed.
Enter the runscript command to display the Run Script screen.
Enter 1 to specify the script path.
Enter the path, including the filename of the script. The utility scripts are located in the scripts
directory and have an .scc extension.
Enter the start command to execute the script.
Enter any additional information required by the script.
Use the up or exit commands as necessary to exit the tool when the test is complete.
Tests and Utility functions
6 Reports and Support Tickets
A major feature of L&TT is the ability to generate reports and support tickets. In the event of a hardware
problem, a report or support ticket can provide vital information to help diagnose and resolve the
problem. Reports and support tickets can be generated on all operating systems supported by L&TT.
Much of the information stored within a device related to operational characteristics is used by various
L&TT tests to analyze the health of the device. However, not all information can be used in this automated
fashion. Some information requires review by qualified HP personnel to fully diagnose the situation. For
this reason, a report or support ticket should be generated and e-mailed for further analysis when
requested.
When a report or support ticket is generated, L&TT collects configuration information and executes
a Device Analysis test on the selected device. This information can then be viewed, saved, printed,
compared to another report or support ticket, or e-mailed. A report or support ticket is saved as a log file
having the .ltt extension, along with one or more associated sub-tickets having the .dat extension. By
default, these files are saved to the logs directory.
While support tickets contain highly technical data that is intended primarily for HP support personnel and
developers, in contrast, L&TT reports take much of this technical information and present it in a much more
user-friendly way. You can think of a report as an enhanced, user-friendly support ticket. Currently, reports
are only available for LTO drives, but support tickets for other devices are continually being upgraded to
the new report format and will eventually replace support tickets. However, the “classic” support ticket will
always be available when the report is viewed with the detail level set to Everything or Factory only.
NOTE:
As of L&TT version 4.0 SR1, reports are only available for LTO drives. Support for other hardware will
be added with later releases of L&TT.
The report viewer is built into the L&TT application and is used to view both support tickets and reports.
The viewer enables viewing of detailed device information and general information on the system it
is connected to. This information is displayed in a standard tree view format. The user (or support
technician) can change the detail level of the support ticket or report, browse through the information,
and expand or collapse specific sections of the support ticket or report as required.
Keep the following information in mind when generating and viewing support tickets and reports:
• In the event of a device failure (or suspected failure), it is important to generate a report or
support ticket for that device as soon as possible. Doing so increases the chance that relevant
failure data is captured in the report or support ticket.
• If L&TT is used to generate a support ticket on a library that is managed by HP StorageWorks
Command View for Tape Libraries Software (Command View TL), it will not include the IM and
IFC logs. Support tickets should be generated using the Command View TL GUI or CLI, as
documented in the HP StorageWorks Interface Manager and Command View for Tape Libraries
Software user guide, to ensure that all log data is captured. If the library is partitioned, be
careful when interpreting support tickets because the values in the logs are based on the actual
physical library, not the partitioned library, so drive and slot numbers do not directly match those
numbers reported by the backup application.
• Regardless of the selected detail level, the log file always contains all of the information collected
from the product. The report viewer filters and parses this information, depending on the detail
level.
L&TT reports and support tickets are saved in a proprietary format and require the report viewer.
However, with the Windows version of L&TT, a report or support ticket can be converted to
HTML format using the currently selected detail level. The HTML version can easily be printed or
viewed by other users without the report viewer.
Library and Tape Tools User Guide
87
After a report or support ticket has been exported to HTML, the detail level within the HTML file
cannot be changed. Make sure that the detail level is set to the desired level before generating
the HTML report.
• When generating a report or support ticket for standalone devices, HP recommends that you keep
the media in the drive in which it was present when the failure occurred. This allows error rate
and other information relevant to that cartridge to be examined. When media is removed, many
devices automatically clear this information. For tape automation products, it is generally better to
have the drives empty of media to force the library drive/media log to be updated.
• The Windows version of L&TT is the preferred platform for working with reports and support
tickets. Comparing or printing reports and support tickets is only supported with the Windows
platform. E-mailing reports and support tickets is supported on all L&TT-supported operating
systems with the exception of NetWare. You should view reports and support tickets with the
Windows version of L&TT to provide unrestricted analysis.
• In the Windows version of L&TT, right-clicking any of the text in the report viewer displays a
context menu with more options. A quick way to see the entire support ticket or report is to set the
detail level to Everything or Factory only, right-click the top entry, then select Expand All.
Using a report or support ticket (Windows)
The functionality of reports and support tickets is essentially the same. The main difference is that reports
have an enhanced format that presents much more useful information to the average user. Support
tickets contain log data and other information that is primarily intended for HP support personnel and
developers. The procedure for accessing reports and support tickets is the same (with the exception of
the Health button, which is explained below). However, reports are not yet available for all supported
devices. If a report is available for the selected device, it will be generated. Otherwise, a support
ticket will be generated.
Reports and support tickets can be generated in two ways:
• Both reports and support tickets can be generated from the Support screen. The Support screen
gives you the option of viewing, saving, or e-mailing the report or support ticket.
To access the Support screen:
1. Select a device in the device list (By Product or By Connection tab).
2. Click the Support button on the main toolbar to display the Support screen.
• Reports can be generated using the Health button. This is the preferred method for quickly
generating and displaying a report.
1. Select a device in the device list (By Product or By Connection tab).
2. Click the Health button on the main toolbar. The report is generated and automatically displayed
in the report viewer using the Normal detail level.
NOTE:
If the report format is not yet available for the device selected in step 1, the Health button
will be greyed out. In this case, use the Support screen to generate a support ticket.
Using the Support screen
Reports and support tickets can both be generated from the Support screen. If the report format is
available for the selected device, a report will be generated. Otherwise, a support ticket will be
generated.
88
Reports and Support Tickets
Figure 24 Support screen
To generate a report or support ticket, you must first extract the device data. Click Extract Device Data to
generate the report or support ticket. After extracting the device data for the first time, the Extract Device
Data button text changes to Refresh Device Data. You should refresh the device data whenever a change
is made to the device that can affect the support ticket, such as running a test or loading/unloading a
cartridge.
After extracting (or refreshing) the device data, the following three options become available:
• View Support Ticket—Click this button to view the report or support ticket in the report
viewer. The report or support ticket can later be saved or sent via e-mail. For more information,
see Viewing a support ticket.
• Save Support Ticket—Click this button to save the report or support ticket. For more
information, see Saving a report or support ticket.
• Send Support Ticket by E-mail—Click this button to send the report or support ticket via
e-mail to an HP support center (or other destination). Clicking this button opens a form that allows
you to provide all the necessary information. Complete the form and click the Send button to
send the e-mail. Using this option does not save a copy of the support ticket locally, so you are
advised to click Save Support Ticket to save a copy for future reference. For more information, see
Sending a report or support ticket by e-mail.
NOTE:
When sending a report or support ticket by e-mail, L&TT provides the option to compress the support
ticket.
In addition to the above options, the bottom section of the Support screen provides resources for finding
support on the Web. Click any of the buttons in the Support Resources on the Web section of the screen
to open a browser window and view the corresponding web site.
Support ticket size management
Two primary changes were introduced with L&TT v3.4 regarding support ticket size management. These
changes were made primarily to eliminate problems associated with e-mailing very large files:
Library and Tape Tools User Guide
89
• Compression of support tickets.
• Support for splitting large support tickets into smaller, more manageable chunks (Windows only).
L&TT v3.5 added support for splitting support tickets for non-Windows platforms. With L&TT 4.0,
all support tickets, regardless of size, are split into two or more files.
The information above also applies to L&TT reports.
Report and support ticket compression
L&TT supports compression of support tickets on both Windows and CSI platforms. By default,
compression is enabled on Windows, and disabled on CSI. In both cases, the compression ratio averages
5:1 when enabled. Compressed reports and support tickets cannot be saved in L&TT. However, when
a compressed report or support ticket is e-mailed, it can be extracted from the e-mail and saved. The
compressed file has an .ltt.lzo extension rather than the usual .ltt extension. Compressed report
and support ticket files are not viewable on CSI platforms. Regardless of platform, compressed support
tickets are created during the send e-mail process only.
The E-mail Support Ticket dialog box has a check box that lets you disable support ticket compression on
Windows. Compression can be later re-enabled if desired through the same dialog box.
Splitting of reports and support tickets (Windows)
All reports and support tickets are split into two or more smaller files to prevent problems when e-mailing
excessively large files. When a report or support ticket is saved, a file with an .ltt extension is created,
and one or more additional files are also created. Each of these additional files has a .dat extension
and represents a sub-ticket. When you open the ticket (with the .ltt extension) in the usual way for
viewing, the additional sub-ticket files are accessible via hyperlinks. When you click the hyperlink, the
respective sub-ticket is loaded into memory and can then be expanded for detailed viewing.
NOTE:
All files created with a report or support ticket must be included when the ticket is sent for analysis. If
the report or support ticket is e-mailed from within L&TT, the additional .dat files are automatically
included in the e-mail. If the report or support ticket is sent using another e-mail application, you must
attach all of the associated .dat files to the e-mail. Otherwise, HP support personnel will not have the
information they need to do a proper analysis.
NOTE:
If the .ltt and .dat files associated with a split report or support ticket exceed the 10 MB default
value for maximum e-mail size, L&TT automatically generates separate messages to keep the size below
the threshold. The maximum e-mail size limit only pertains to e-mails sent from within L&TT. The default
value for maximum e-mail size is 10 MB, but it can be changed using the Preferences dialog box.
Viewing a report or support ticket
After a report or support ticket is generated, it is displayed in the report viewer. This viewer is built
into the L&TT program. Information is displayed in a standard tree-view format. Click the “+” and “–”
signs to expand and collapse sections of the support ticket. Use the standard navigation keys (Home,
End, Page Up, Page Down, and the arrow keys), the Windows scroll bars, and the mouse to navigate
through the document.
To print the report or support ticket, select File > Print from the menu bar within the report viewer.
Setting the detail level
Reports and support tickets can display information in several different levels of detail, depending on
the setting displayed in the Current Detail Level dropdown box. The following detail level settings are
available:
90
Reports and Support Tickets
•
•
•
•
•
Highlights only (not used with reports)
Normal
More details
Everything (the highest level the end user can view)
Factory only (requires a factory password. Contact HP support to obtain a factory password)
Figure 25 Example report
Other functionality
Right-click any node (line) in the support ticket viewer to display a context menu that exposes additional
functionality. Depending on the node that was clicked, the following items may or not be available
(unavailable items are greyed out):
• Expand All—Selecting this item expands all subitems in the node.
• Event Explanation—Selecting this item opens the Event window that displays additional
information about the event. You can view the data in either ASCII or hexadecimal format.
•
•
•
•
•
). See Viewing
This feature is available for items preceded with the blue information icon (
embedded data for more information.
Event Data—Selecting this item opens the Event Data window that displays L&TT-specific
information about the event.
Copy—Selecting this item copies the current line to the Windows clipboard.
Reference Data—Selecting this item opens the Reference Data window that displays reference
information pertinent to the current line such as valid ranges and applicable values.
Find Sub-Tree—This item allows you to search for a particular sub-tree.
Copy Sub-Tree—This item copies the current sub-tree to the Windows clipboard.
Library and Tape Tools User Guide
91
Viewing embedded data
When viewing a support ticket for an interface controller in an Enterprise Tape Library having an Interface
Manager card with firmware revision I160 or higher, the support ticket only displays a Data node that
contains an HTML report page compressed into a zip file. This HTML report page contains all the data
previously displayed through the report viewer for the Interface Controller support ticket and more. The
Data node is preceded with the blue information icon (
), as shown in Figure 26.
Figure 26 Support ticket with embedded data
To view the embedded data:
1. Double-click the Data node to open the Event viewer.
2. Select Hex to view and save the file as a binary file.
3. Click Save As and save the file with a .zip extension.
4. Extract report.htm from the .zip file and open it in a browser window.
NOTE:
If you are using Internet Explorer, depending on security settings, you may see a message
stating that Internet Explorer has blocked ActiveX content. In this case, click the security alert
at the top of the browser window and select Allow Blocked Content from the context menu.
Saving a report or support ticket
When you save a report or support ticket, L&TT generates a subfolder in the logs directory. By default,
the name of this subfolder is st_<date>_<time>_<serial number>, although you can specify
another name if desired. L&TT saves the files sticket_header.ltt and VidPid_UID.dat in the
newly created subfolder. Both of these files together comprise the report or support ticket, and they must
be kept together in the same subfolder to be viewed properly. The report or support ticket can later be
92
Reports and Support Tickets
viewed or sent via e-mail. To view a saved report or support ticket, open the sticket_header.ltt file
using Windows Explorer, or use the Load command on the File menu.
Sending a report or support ticket by e-mail
From the Support screen, click Send Support Ticket by E-mail to generate the support ticket and
immediately send it via e-mail to an HP support center (or other destination). When you click Send
Support Ticket by E-mail, the E-mail Support Ticket dialog box is displayed.
Figure 27 E-mail support ticket dialog box
Before L&TT can e-mail a report or support ticket, you must either have a MAPI-compliant e-mail program
(such as Microsoft Outlook or Outlook Express), or you must set up an e-mail account through the
Windows Control Panel or Internet Explorer. For more information about setting up an e-mail account, see
How do I configure e-mail to send support tickets
The E-mail Support Ticket dialog box is divided into three steps:
1.
In Step 1, indicate whether this is a new support request or an existing case.
Library and Tape Tools User Guide
93
• If this is a new support request, select the Send to support provider to request
support by e-mail option (this option is the default). Enter the product number and
product serial number in the appropriate fields.
• If this is an ongoing support case, select the Send to support provider in
reference to an open case option and enter the case reference number in the
appropriate field.
2. In Step 2, enter the destination e-mail address. Use the dropdown box to select from a list of HP
support providers, or enter the e-mail address manually. If you are using a version of L&TT prior
to v3.5, do not use the regional e-mail addresses; these addresses are no longer monitored.
Beginning with v3.5, two valid e-mail addresses are offered, both for the North American region:
• LTT North America Support Call Center lttna@hp.com (for all North America except 3rd
party outsourcer use)
• LTT North America Support Call Center lttna20@hp.com (for 3rd party outsourcer use)
NOTE:
Customer support personnel typically provide an e-mail address to users who are e-mailing a
support ticket as a result of a support call request. In this case, the user should enter the e-mail
address exactly as provided by the support person. In the European region this will usually be
provided in the form: <xxx>@cases.brussels.hp.com where <xxx> is the actual assigned case
number. This associates the support case number with the support ticket, making resolution and
tracking more manageable.
3. In Step 3, specify the following additional information:
• Contact information—Enter your company name, contact name, contact phone, and contact
e-mail address.
• Attach Result Log—Select this option to attach the support ticket to the e-mail for analysis
by HP service personnel.
• Attach additional Event Log (only if requested)—Select this option if you have been requested
by HP service personnel to send the event log.
• Compress the support ticket—Select this option to compress the support ticket. This option is
selected by default.
• Problem description—Enter a detailed description of the problem you are having.
When you have completed the form, click Send.
NOTE:
L&TT defaults to 10 MB for maximum size for any e-mail. If your e-mail setup will not permit e-mail files
as large as 10 MB, click L&TT Options > Preferences, click the check box for maximum e-mail size, and
then enter a smaller number. If you attempt to e-mail a support ticket using L&TT that is larger than the
maximum e-mail size, L&TT breaks the e-mail into smaller, separate e-mails so that they do not exceed
the maximum size limit. When a support ticket is broken down into sub-tickets, the master file has an
.ltt extension, and the sub-tickets have a .dat extension. The recipient of these e-mails must save all
of the sub-ticket components to the same directory. When sending a large support ticket by e-mail, be
sure to send all of the components or else the support ticket will be unreadable.
Comparing reports or support tickets
L&TT can compare two reports or two support tickets and generate a report of the differences. To do this:
1. Generate or open the first report or support ticket to be compared.
2. In the report viewer, select File > Compare. The Open dialog box is displayed.
3. Select the report or support ticket to which you want to compare and click Open. The comparison
results are displayed in a separate window.
94
Reports and Support Tickets
Figure 28 Support ticket comparison results
Interpreting a report
The information displayed in the report will vary greatly depending on the device being analyzed and
the detail selected. The following report sections may or may not be displayed for any particular device:
• Identity—This section identifies both the drive and the interfaces.
• Health—This section contains a summary of whether the drive is Fit For Purpose (FFP). If there are
any issues identified, then they are explained and corrective action suggested. The Health section
also highlights remaining margin relating to the remaining life of the drive/media.
• Configuration—This section allows you to check the configuration settings of the drive or interface.
The items in this section are usually set by the backup application or HBA.
• Environment—This section displays any known information about the environment in which the
device is operating (such as temperature).
• Performance—This section displays information regarding the recent performance of the device,
such as recent native transfer rates, compression ratios, and so forth.
• Usage—This section shows usage information for the device since it was new.
• History—This section displays any significant events that have happened (and have been
recorded by the device).
For a more detailed explanation of device-specific information displayed in each section, see
Device-specific analysis.
Understanding the margin ratings
When a report is generated, several tests are performed to measure drive performance for every aspect
of operation. Each function that is tested is assigned a margin rating. Margin is expressed as a
percentage where 0% is no margin, but the device should still work. 100% is full margin, or production
quality. A working drive will have positive margin, whereas negative margin indicates a likely issue.
The percentages are also mapped to simple wording as follows:
Library and Tape Tools User Guide
95
< 0%
Warning
>= 0% and < 25%
Fair
>= 25% and < 50%
Good
>= 50%
Great
Corrective action should be considered if the margin does not meet the levels of confidence that the data
requires. For example, a nightly backup probably doesn’t need the same level that a ten year archive
does. In general, corrective action is only required if Warning is shown, but Fair suggests possible future
issues, and corrective action could prevent such issues from occurring.
Corrective action could take the form of:
• Cleaning the drive
• Trying another tape (look at the tape history to see if other drives have had similar issues)
• Checking the environment. Temperature extremes can have an effect. Contamination can be a
significant issue
If in doubt, run the L&TT Drive Assessment test with a trusted (or new) tape. This is the test approved by
HP support to give the most accurate assessment of drive health. If a drive passes this test, it is considered
to be good. If it fails (and the tape is good), then HP support will exchange the drive.
Things to look for
After generating the report, look for the following trouble indicators:
• Device Analysis Rules—These are device-specific items that L&TT tests. These rules are displayed
in the Drive Health section under Device Analysis. This is the first place to look for health
information and advice on corrective action.
• Drive health varying with different tapes—In this case, the tapes are most likely causing the
variation.
• Tape health varying with different drives—In this case, the drives are most likely causing the
variation.
• A drop of margin over time—Rapid drops can indicate contamination.
• Tapes nearing the end of their working life—Older tapes are less reliable and may need to be
replaced.
• Drives nearing the end of their normal working life—This is unlikely because the estimated
lifespan of HP drives is very high.
96
Reports and Support Tickets
Device-specific report analysis
This section explains device-specific report data. Currently, the report format is only available for LTO
drives and media. As support for the report format is added to other devices, the information will be
added to this section.
Click the relevant link to jump to that section:
• LTO drives
• LTO media
LTO drives
The report groups information into the following standardized sections, and wherever possible, identifies
the drive and media as separate devices.
•
•
•
•
•
•
•
Identity
Health
Configuration
Environment
Performance
Usage
History
Identity
This section shows the identification of both the drive and the interfaces. The Format entry also indicates
compatibility.
Health
This section is split into two main sections: Device Analysis and Write/Read margin data.
• The Device Analysis section shows the output of the device rules. This is the first place to look for
health information and advice on corrective action.
• The Write/Read margin data section shows the write and read margin of the last five tapes
(current and previous four tapes).
• The summary line (top line of this section) shows the average and worst margin values found in
the available history. The Current tape and four Previous tape lines show margin information
for the last five tapes used. If there is a margin warning for one tape, then that suggests a
suspect tape. Cross check with the cartridge history below or try the tape in another drive. If
there is a margin warning for all tapes then the drive itself is suspect. Try cleaning the drive
and run the Drive Assessment test to check the drive.
• The Head life, Reposition life, and Load/unload life lines show life figures for the drive.
Configuration
This section shows configuration information for the drive and its associated interface controller.
• In the Drive section, useful configuration information is listed which can assist with troubleshooting
potential drive problems. For example, the report records the current data compression setting of
the drive, and whether the backup application has prevented media removal.
• In the Interface section, verify that the negotiated burst rate is as expected. This value should
match the data shown for the interface controller in the Drive Identity section (the name of the
controller generally indicates the maximum speed that the interface can handle).
Library and Tape Tools User Guide
97
Environment
This section shows temperature data for the drive. Verify that all temperatures shown are within normal
limits.
Performance
This section shows burst performance figures for the drive, and estimated native performance figures
for the last four tapes.
• Maximum data rates show the highest rate that the data compression engine has seen. Figures
are high because of buffering. These values show the maximum possible rates with very high
compression ratios.
• Average data rates before compression are what the host has seen. Average rates after
compression are the native rates for the tape.
• Write and read compression ratios are calculated over the same data. These figures are reset on
tape load, in which case Unknown is shown.
• Performance figures from previous tapes are estimated from the amount of data transferred and
the time spent pulling tape. If less than 60 seconds of tape pulling have occurred, then Not
enough data is displayed because the estimate is likely to be inaccurate.
Usage
This section shows usage data for the drive since it was new, as well as the amount of data transferred
over the current and previous four tapes.
The Tape pulled item is expressed in full volume equivalents as that is closest to a customer model. HP
media documentation also uses this unit.
History
This section displays drive logs that show what the drive has been doing. The event log shows high-level
information on commands received, internal processing, and any errors returned to the host (including
tape alert information). The data displayed here is limited in depth. The times shown are relative
to the last power on.
LTO media
This section displays information on the currently loaded tape (header displays loaded tape), or the tape
that was loaded last (header displays ejected tape). If you are using genuine HP media, more information
is displayed in this section than would be with non-HP media.
This section has several sections and sub-sections:
• The Identity section shows the identity of the media. Note that the Barcode item is not used
by all products.
• The Health section is split into three sections:
• The Data on tape section shows margin measurements for the data on the tape. Data on tape
is written in wraps where each wrap is a pass up or down the tape. Each generation of LTO
has a different number of wraps. Each wrap has a measure of margin revealing any bad
spots on the tape. The summary line (top line of the section) highlights the worst margin found
and should be used for a measure of minimum quality of the whole tape. The last used wrap
usually displays partially written. Only fully written wraps can be measured for margin.
To the right of the margin indicator for each wrap is a text-based bar chart that graphically
shows the margin rating. The zero in the middle represents 0% margin, and the carat (^)
represents the actual margin of the wrap. This is helpful to visualize margin across the tape
if a bad area covers more than one wrap.
• The Drive measurements section shows data from the error rate counters of the drives the
cartridge was used in. The summary line shows the worst margin found in the available
history. If there is a margin warning for one drive but good margin for the other drives, then
98
Reports and Support Tickets
•
•
•
•
that suggests a suspect drive. Try cleaning the drive and run the Drive Assessment test to check
it. If there is a margin warning for all drives, then the cartridge itself is suspect. Cross check
this information with the Drive History section of the report.
• The Write/read life and Load/unload life items show cartridge life estimates based on usage
and published expected life figures with HP drives. Because HP drives are tuned to work with
genuine HP media, HP media can be expected to have a longer usage life.
The Configuration section shows whether the cartridge is write protected and WORM enabled.
Note that WORM is only supported with LTO3 and later drives.
The Environment section shows data for the current and previous drive environment. Watch
for warnings even in previous drives. This information can be useful to track down system hot
spots or cooling issues.
The Performance section shows performance data for the cartridge in the current drive, as well
as the previous two drives. Performance figures from previous drives are estimated from the
amount of data transferred and the time spent pulling tape. If less than 60 seconds of tape
pulling have occurred, then the message Not enough data is displayed because the estimate
is likely to be inaccurate.
The Usage section includes how much of the cartridge capacity has been used (all figures native)
and usage over the available history of previous drives. The total write/read data volume and
load count since new are also shown.
Generating and viewing a support ticket (CSI)
To generate and view a report or support ticket in the CSI environment:
1.
From the Main screen, select the device for which to create a report or support ticket. The
Device Information screen is displayed.
2. Enter the support command to access the Support screen. Alternatively, if the report format
is available for the selected device, then you can use the health command to access the
Support screen.
NOTE:
The functionality of the Support screen is the same, regardless of which command you used to
access it.
3. From the Support screen, enter the extract command (or the refresh command).
After extracting a report or support ticket for a device for the first time, the extract command
is replaced with the refresh command. You should refresh the device data whenever a
change is made to the device that can affect the support ticket, such as running a test or
loading/unloading a cartridge.
4. After extracting (or refreshing) a report or support ticket, do one of the following:
• Enter the view command to view the support ticket.
• Enter the save [<arg>] command to save the report or support ticket.
L&TT saves the report or support ticket files in a newly created subfolder (as described
below). These files must be kept together in the same subfolder to be viewed properly.
The report or support ticket can later be viewed (using the load command from the Main
screen) or sent via e-mail.
• If no argument is specified, L&TT generates a subfolder in the logs directory in which
the report or support ticket files will be saved. By default, the name of this subfolder is
st_<date>_<time>_<serial number>, although you can specify another name
on a subsequent screen if desired. L&TT saves the following files in the newly created
subfolder.
• sticket_header.ltt
• VidPid_UID.dat
• If you specify an argument with a path and filename, as in this example:
/opt/temp/abc.ltt
Library and Tape Tools User Guide
99
then L&TT creates the /opt/temp/abc/ directory and saves the following two files there:
• abc_header.ltt
• VidPid_UID.dat
• If you specify an argument with only a filename, as in this example:
abc.ltt
then L&TT creates the /opt/ltt/logs/abc/ directory and saves the following two
files there:
• abc_header.ltt
• VidPid_UID.dat
• Enter the send command to send the report or support ticket by e-mail. See Sending a
support ticket by e-mail (CSI) for more information.
When viewing the support ticket, use Ctrl+U and Ctrl+D to scroll up and down through the results. You
can also use the find and page commands to quickly locate information.
Support ticket size management
Two primary changes were introduced with L&TT v3.4 regarding support ticket size management. These
changes were made primarily to eliminate problems associated with e-mailing very large files:
• Compression of support tickets.
• Support for splitting large support tickets into smaller, more manageable chunks (Windows only).
L&TT v3.5 added support for splitting support tickets for non-Windows platforms. With L&TT 4.0,
all support tickets are split into two or more files.
Support ticket compression
Compression of support tickets is now supported on both Windows and CSI platforms. By default,
compression is enabled on Windows, and disabled on CSI. In both cases, the compression ratio
averages 5:1 when enabled. Compressed support tickets cannot be saved in L&TT. However, when a
compressed support ticket is e-mailed, it can be extracted from the e-mail and saved. The compressed
file has an .ltt.lzo extension rather than the usual .ltt extension. Compressed support ticket files
are not viewable on CSI platforms. Regardless of platform, compressed support tickets are created
during the send e-mail process only.
By default, support ticket compression is disabled on CSI platforms. To enable compression, use option
12 from the Send screen. This same screen can also later be used to disable compression if desired.
Splitting of support tickets (CSI)
With the introduction of L&TT 4.0, all support tickets are split into two or more smaller files to prevent
problems when e-mailing excessively large files. When a support ticket is saved, a file with an .ltt
extension is created, and several additional files are also created. Each of these additional files has a
.dat extension and represents a sub-ticket.
You will not be able to view the additional support ticket information contained in the sub-tickets through
the Support Ticket Viewer on CSI platforms. However, you can transfer the .ltt file and all associated
.dat files to a Windows platform machine and view all the data there. For more information about
viewing a support ticket on the Windows platform, see Splitting of support tickets (Windows).
NOTE:
All files created with a support ticket must be included when the ticket is sent for analysis. If the ticket is
e-mailed from within L&TT, the additional .dat files are automatically included in the e-mail. If the
support ticket is sent using another e-mail application, you must attach all of the associated .dat
files to the e-mail. Otherwise, HP support personnel will not have the information they need to do a
proper analysis.
100
Reports and Support Tickets
NOTE:
If the .ltt and .dat files associated with a split support ticket exceed the 10 MB default value for
maximum e-mail size, L&TT automatically generates separate messages to keep the size below the
threshold. The maximum e-mail size limit only pertains to e-mails sent from within L&TT. The default
value for maximum e-mail size is 10 MB, but it can be changed using the Preferences dialog box.
Sending a support ticket by e-mail (CSI)
To generate a support ticket and send it via e-mail:
1.
From the Main screen, select the device for which to create a support ticket. The Device
Information screen is displayed.
2. Enter the support command to access the Support screen.
3. From the Support screen, enter the send command to display the Send Support Ticket screen.
The Send Support Ticket screen displays a list of several parameters that must be entered before
the support ticket can be sent. The screen displays the current values for each parameter.
4. Enter the number of the first parameter, and then enter the parameter data at the prompt.
5. Repeat step 4 for each remaining parameter and option. When entering the e-mail address,
if you are using a version of L&TT prior to v3.5, do not use the regional e-mail addresses;
these addresses are no longer monitored. Beginning with v3.5, two valid e-mail addresses are
offered, both for the North American region:
• LTT North America Support Call Center lttna@hp.com (for all North America except 3rd
party outsourcer use)
• LTT North America Support Call Center lttna20@hp.com (for 3rd party outsourcer use)
NOTE:
Customer support personnel typically provide an e-mail address to users who are e-mailing a
support ticket as a result of a support call request. In this case, the user should enter the e-mail
address exactly as provided by the support person. In the European region this will usually be
provided in the form: <xxx>@cases.brussels.hp.com where <xxx> is the actual assigned case
number. This associates the support case number with the support ticket, making resolution and
tracking more manageable.
6. When all the required parameters and options have been specified, enter the send command to
generate and send the support ticket.
Common information reported for all products
NOTE:
For standalone devices (such as DDS drives), HP recommends that you generate a report or support ticket
when the drive still contains the media with which the drive may have failed. This allows error rate and
other information relevant to that cartridge to be examined. When media is removed, many products
automatically clear this information. However, for most SureStore tape libraries it is better to have the
drives empty; this forces the library drive/media log to be updated.
The following information is included in the support ticket regardless of what products are being analyzed:
• System information provides basic host system information such as operating system, processor
type, system name, physical memory size, and the current version of L&TT being used. This
information also includes a snapshot of the SCSI bus configuration determined by the I/O scan,
showing connected devices listed physically and logically.
Library and Tape Tools User Guide
101
• L&TT history provides a brief history of the L&TT functions the user has accessed such as whether
ASPI was installed, how many times L&TT has been run, and which functions have been used.
Using the event log
L&TT can generate a detailed event log that captures all L&TT diagnostic interaction, all SCSI commands
sent and received by the program, and any software interactions or issues. The information it contains is
intended for use by L&TT programmers as a tool for debugging software issues within the program itself.
Generating an event log (Windows)
To generate an event log (Windows):
1.
2.
3.
4.
5.
6.
7.
8.
Run L&TT and select Options > Preferences.
Check the Add I/O history to event log option and click OK.
Exit and restart L&TT.
Replicate the problem encountered.
Navigate to the logs directory in the L&TT installation directory. Locate the Eventlog.ltt file.
Attach the Eventlog.ltt file to an e-mail and send it to the L&TT team for diagnosis.
Return to L&TT and select Options > Preferences.
Uncheck the Add I/O history to event log option and click OK.
CAUTION:
This option should not be left enabled because it can potentially use hundreds of megabytes of
disk space.
NOTE:
In the log directory you may also see other event log entries such as EventLog_backup1.ltt,
EventLog_backup2.ltt, EventLog_backup3.ltt, and so on. The versions of the event log are numbered in
historical order.
Because the event log stores a SCSI trace of the interaction between the product and the L&TT software, it
can be used as a simple SCSI analyzer. To do this, select the Add I/O history to event log
option (as described in steps 1 and 2 previously) and make sure that you view the event log at the
“factory only” detail level.
In escalations or integration situations, this can sometimes eliminate the need for a SCSI analyzer. All
SCSI commands and responses can be found in the event log if the Add I/O history to event
log option is enabled.
NOTE:
The event log can only capture I/O traffic from L&TT. It cannot be used to analyze traffic from other
applications or the OS.
Generating an event log (CSI)
To generate an event log (CSI):
1.
2.
3.
4.
102
From the Main screen, enter preferences.
Enter 4 at the command prompt, and then check the check box.
Enter 5 at the command prompt, and then enter the value 128.
Exit and restart L&TT.
Reports and Support Tickets
5. Replicate the problem encountered.
6. Navigate to the logs directory in the L&TT installation directory. Locate the Eventlog.ltt file.
7. Attach the Eventlog.ltt file to an e-mail and send it to the L&TT team for diagnosis.
CAUTION:
This option should not be left enabled because it can potentially use hundreds of megabytes of disk space.
NOTE:
In the log directory you may also see other event log entries such as EventLog_backup1.ltt,
EventLog_backup2.ltt, EventLog_backup3.ltt, and so on. The versions of the event log are numbered in
historical order.
NOTE:
The event log can only capture I/O traffic from L&TT. It cannot be used to analyze traffic from other
applications or the OS.
Library and Tape Tools User Guide
103
104
Reports and Support Tickets
7 Additional Functionality
This chapter describes additional features of the program that are not covered elsewhere in this guide.
•
•
•
•
•
•
•
•
•
•
Setting software preferences
Using the Internet update functionality
Using passwords
Using the Front Panel function
Using the Move Media function
Performing manual product identification
Using the Quiet Mode feature
Using the Installation Check feature
Using L&TT in restricted mode
Using the Tool Status Report
Library and Tape Tools User Guide
105
Setting software preferences
L&TT has many user-definable preferences that control various elements of the program. To access
the L&TT preferences:
To set the preferences in the Windows version of L&TT, select Options > Preferences. The
preferences dialog is displayed.
Figure 29 L&TT Preferences dialog box (default settings shown)
To set the preferences in the CSI version of L&TT, from the Main screen, use the preferences
command to display the Preferences screen.
106
Additional Functionality
Figure 30 L&TT preferences dialog box (CSI version)
Available options
The following list describes the available options. Some options are not available with CSI versions of
L&TT.
• Show Scan Details (Windows only)—Enabling this option causes L&TT to show the SCSI
bus scanning process in the Device List screen when the program is first started. This option is
disabled by default.
• Show Instructions (Windows only)—Enabling this option causes L&TT to display
instructions in the Device List screen. These instructions provide information corresponding to the
function displayed in the Main screen. More experienced users may want to disable this option.
• Firmware File Path—This is the location where L&TT stores and accesses firmware files
on your local system. When using the “Get Firmware From Web” feature, firmware files are
automatically downloaded to this directory.
• Log File Path—This is the location where L&TT stores and accesses log files on your local
system. The logs that are stored here are the support and event logs.
• Script File Path—This is the location where L&TT stores and accesses device analysis rules
files. This is also the default location for SCSI scripts.
NOTE:
For all of the previous three options, the default location of the directory is the L&TT Installation
directory.
• Display splash screen at startup (Windows only)—Enabling this option causes
the L&TT splash screen to be displayed when the program is started. From the splash screen, you
can select the I/O mode and other options.
• Check for updates on the Web (Windows only)—When this option is enabled, L&TT
uses an available Internet connection to look for product updates such as firmware upgrades,
new device analysis rules, and new versions of L&TT. The software performs this check once
every 24 hours. This functionality is only available if you have an Internet connection. For more
information, see Using the Internet update functionality later in this chapter.
• Display dialogs for I/O pending more than 2 minutes (Windows
only)—When this option is enabled, L&TT displays a status update dialog box during long
SCSI operations.
Library and Tape Tools User Guide
107
• Add I/O history to Event Log—Enabling this option causes L&TT to log all SCSI
commands that are sent or received into a log file. This option requires a large amount of disk
space and should only be used when requested by L&TT development personnel to aid in
the debugging of a potential issue with L&TT. For more information, see Using the event log
(Windows).
• Check for redundant devices after scan—Checks for redundant devices in the
current configuration. This option is enabled by default.
• Data Phase Limit for I/O History—When the Add I/O History to Event Log
option is enabled, this option limits the amount of data recorded to the log file for each SCSI
command to the number of bytes specified. The default is 128 bytes. To specify a data phase limit,
enter any positive number in this field. If you do not want to specify a limit, enter unlimited.
• Current password entered—This option lets you enter the factory password. The currently
entered password is displayed to the right of the option. If no password has been entered,
Not Set is displayed.
• Enter Maximum E-Mail size—This option lets you specify a maximum size (in megabytes)
for support tickets. If the support ticket exceeds this size, it will be broken up into smaller subtickets.
108
Additional Functionality
Using the Internet update functionality
The Windows version of L&TT can automatically notify the user of the following conditions each time
the program is started:
• A new version of L&TT has been released
• A new version of firmware is available for a connected storage device
• A new version of device analysis rules is available for a connected storage device
This notification only occurs if the user has the Check for updates on web option enabled in the
preferences dialog (this option is enabled by default).
If the Check for updates on web option is not enabled, select Get Files from Web from the File
menu to manually check for and download updates.
NOTE:
L&TT will only check for updates on the Web once in a 24-hour period.
Library and Tape Tools User Guide
109
Using passwords
A number of tool features are available only when enabled with a password. The password is intended
to prevent inexperienced users from accessing functionality that may be particularly harmful to their
system if used improperly. These features include:
• Firmware Downgrade lets you downgrade firmware revisions. The device product ID and revision
string sequence must match.
• Override/Update Product ID allows selection of any firmware file (which matches the same device
type) and updating of the product ID string (for devices which support this capability).
• Manual Product Identification allows overriding of the tool mapping to associate a specific device
(independent of Product ID) to a specific device family supported by the tool. This is most
often used when the Product ID (SCSI Inquiry) string is incorrect because it has been changed,
corrupted, or the device is running on boot code.
• Factory Details lets you select factory details anywhere that it is an option. The most common
use is in viewing additional device details in the support ticket.
• Advanced Scripting disables signature checking and allows you to select unsupported devices
and run scripts on them.
• View Event Log lets you load (and view) an event log.
There are two types of passwords that are used with L&TT. Temporary passwords enable users to
downgrade firmware, override/update product ID, and override device mapping. Support personnel
passwords (for internal HP use only) enable all of the above options. To obtain a password, contact
your support provider or call center.
Setting passwords
To set the password in the Windows version of L&TT:
1. Select Options > Enable Factory Overrides. The Factory Password dialog box is displayed.
2. Enter the password and click OK. Assuming the password is valid, you are now able to access
the password-protected functions of L&TT.
To set the password in the CSI version of L&TT:
1. From the Main screen, enter the preferences command. The Preferences screen is displayed.
2. Enter the number that corresponds to the password option. L&TT prompts you for the current
password.
3. Enter the password. If the password is valid, then L&TT returns you to the Preferences screen. You
are now able to access the password-protected functions of L&TT.
110
Additional Functionality
Using the Front Panel function
L&TT provides remote control of the front panel of selected library devices. L&TT reads the contents of the
front panel at regular intervals and displays the contents of the L&TT window either in graphic or text
form. In addition, L&TT displays a representation of the library’s front panel buttons. Clicking a button
simulates the user pressing the corresponding button on the library’s front panel.
To access this functionality, select the library in the device list and click Frontpanel on the main toolbar.
The Front Panel screen is displayed.
Figure 31 Front panel screen
Library and Tape Tools User Guide
111
Using the Move Media function
Most supported libraries and autoloaders support a set of commands for moving media from one location
to another within the device. Whenever possible, L&TT takes advantage of this functionality to provide a
convenient way to move media within a library or autoloader. This functionality is supported in both the
GUI and CSI versions of L&TT.
With the Windows version of L&TT, the Move Media functionality is incorporated into the Front
Panel screen. To access this functionality:
1.
Select a supported library or autoloader from the device list and click Frontpanel on the main
toolbar (the Frontpanel button is grayed out if both the Move Media and Front Panel functions
are not supported for the selected device).
2. On the Front Panel screen, click the Move Media tab (this tab is not available if the Move Media
function is not supported for the selected device). The Move Media screen is displayed.
Figure 32 Move Media screen
The Move Media screen is divided into two sections showing all available source and destination drives,
slots, and mailslots. To move media from one location to another, selected the desired source and
destination locations and click Perform Move.
NOTE:
Only one item can be moved at a time, so it is not possible to select multiple source or destination
locations. The Perform Move button is grayed out until a valid source and destination have been selected.
With the CSI version of L&TT, from the Device Information screen for a supported library or autoloader,
use the movemedia command to access the Move Media screen. This screen is identical to the Cartridge
Inventory screen accessed with the inventory command with the exception of the screen name shown
in the top line. Use the standard keyboard commands (Ctrl+U, Ctrl+D) to scroll through the list. To
perform the move, use the move command.
move <source> <destination>
112
Additional Functionality
The values used for <source> and <destination> are a combination of the letter s for slot, d for drive,
or m for mailslot, and the number of the device. For example, to move media from Slot 4 to Slot 3,
enter the following command:
move s4 s3
To move media from Drive 1 to Mailslot 3, enter the following command:
move d1 m3
Possible Move Media error situations
The following errors may be encountered when attempting to move media through L&TT:
NOTE:
These errors are less common with the Windows version of L&TT because the user interface reduces the
number of possible error situations.
1.
2.
3.
4.
5.
The source is empty.
The destination is full.
The picker is full with some other media.
The source and destination are the same.
Invalid arguments were provided (for example, the slot number is too high or no mail slots
on the system).
6. Slot to slot is not supported with this device (you must move slot to drive or drive to slot).
7. The command was acceptable, but there was a SCSI error performing the move. L&TT provides
the SCSI error message along with the sense data.
Library and Tape Tools User Guide
113
Performing manual product identification
This feature (which requires a password) allows an arbitrary device to be mapped as a specific device
family within L&TT. This feature is most commonly used when the product ID (SCSI inquiry) string does not
match the string expected by L&TT. The string may have been changed or corrupted, or the product is
operating in “boot code” mode.
To manually identify a device:
1. Select a product in the device list.
2. Select Manual Product Identification from the Function menu.
3. Choose the product family that best matches the selected device.
NOTE:
For L&TT versions prior to 2.7 SR2a, manual product identification (previously called override mapping)
was performed by right-clicking the device in the device list and choosing the appropriate product family.
When manual product identification is enabled, L&TT automatically operates in restricted mode. In this
mode, the firmware update options are preselected to enable selection of firmware for any product ID
and also set the update product ID option. To update the product ID, select the proper firmware
file and click the Start Update button.
114
Additional Functionality
Using the Quiet Mode feature
Depending on the quiet mode argument specified, warning and error dialog boxes may not be displayed
in quiet mode. Quiet mode has two possible arguments:
• Warning—When the warning argument is specified, L&TT does not display any warning dialogs.
L&TT assumes a Yes response to all warning dialogs and proceeds with execution.
• Error—When the error argument is specified, L&TT does not display warning or error dialogs.
L&TT assumes a Yes response to all warning and error dialogs and proceeds with execution.
CAUTION:
HP does not recommend using quiet mode unless you are thoroughly familiar and experienced with
L&TT. Quiet mode makes using L&TT more convenient by suppressing warning, error, and confirmation
dialogs. However, these same warning, error, and confirmation dialogs are intended to provide an extra
level of security to prevent you from accidentally doing something that you did not intend to do. Using
quiet mode sacrifices this extra level of security for convenience.
NOTE:
Quiet Mode is only supported in the Windows version of L&TT.
To launch the Windows version of L&TT with quiet mode enabled, click Start > Run and enter one of
the following into the Run dialog box:
C:\Program Files\HP StorageWorks Library and Tape Tools\HP_LTT.exe -o quietmode=error
— or —
C:\Program Files\HP StorageWorks Library and Tape Tools\HP_LTT.exe -o quietmode=warning
Library and Tape Tools User Guide
115
Using the Installation Check feature
Installcheck mode is a feature of the Windows version of L&TT. When run in Installcheck mode, L&TT
can be used to check the installation of selected devices. L&TT performs several tests on each selected
device to determine if the device is configured optimally. In addition, L&TT performs connectivity and
configuration tests on all supported devices that are configured on the system. These tests cannot be
overridden. All of the tests performed during the installation check can also be run manually with L&TT.
L&TT displays the results of each test and any recommendations.
The installation check feature is currently supported on the following devices:
• HP Ultrium drive (L&TT 3.4 and later)
• HP SDLT 320 drive (L&TT 3.5 and later)
• HP VS80 drive (L&TT 3.5 and later)
The installation check feature can be run from the Start menu, or launched from a command prompt
using the mode=installcheck argument.
To launch L&TT in installcheck mode:
1.
Do one of the following:
• If using version 3.5 SR2 or later, select Start > Programs > HP StorageWorks Library and
Tape Tools > HP L&TT Installation Check.
• If using a version of L&TT prior to 3.5 SR2 but at least 3.4, click Start > Run and enter the
following into the Run dialog box:
C:\Program Files\HP StorageWorks Library and Tape Tools\HP_LTT.exe -o mode=installcheck
NOTE:
Be sure to include the quotation marks as indicated.
The Installation Check wizard is displayed.
116
Additional Functionality
Figure 33 Installation Check wizard
2. Select the device on which to run the installation check and click Start Verification to display the
next screen of the Installation Check wizard.
3. Select any optional tests that you want L&TT to perform. Some tests may not be available for
your configuration.
4. Click Continue Verification to begin the installation check. The third screen of the Installation
Check wizard indicates the progress of the installation check. Selected tests are executed
sequentially, and the progress of each test is displayed.
The final screen of the Installation Check wizard displays the results of the selected tests and
any recommendations.
NOTE:
If you need to stop the installation check, click Abort Installation Check. The test is aborted after
completing the current phase of the test.
5.
Click OK to close the Installation Check wizard. Closing the wizard also closes L&TT. If you want
to restart L&TT, launch it as you normally would, without the mode=installcheck argument.
Library and Tape Tools User Guide
117
Using L&TT in restricted mode
When running in restricted mode, only a few of L&TT features are available. Running in restricted mode is
not a user option. Rather, L&TT automatically runs in restricted mode when it recognizes an otherwise
supported device that has a problem with firmware and requires a firmware upgrade. There are two
basic scenarios:
• L&TT recognizes the device, but the device is in “brain dead” mode. This usually indicates that the
device firmware is corrupt and the device is responding via boot code only.
• L&TT recognizes the device by means of the product ID code, but L&TT does not recognize
the personality codes of the device.
If one of these scenarios exist, then L&TT displays a message stating that it is running in restricted mode
when it is started. The functionality of L&TT is restricted as follows:
• All features are disabled except for firmware update and support ticket.
• The support ticket shows basic information only and excludes device details.
• For firmware upgrades, L&TT enforces the Allow all files to be selected option, and
the Options button is unavailable because all options are preset.
To exit restricted mode, exit and restart L&TT. L&TT will continue to start in restricted mode until the
problem with the offending device is resolved, or the device is disconnected.
118
Additional Functionality
Using the Tool Status Report
The Tool Status Report (TSR) is a feature of L&TT that is used to help understand and debug problems with
the L&TT tool. Contents of the TSR include configuration information, stack trace, other system information,
and so on. It is automatically generated any time the L&TT application is unexpectedly shut down, but
can also be manually generated if necessary to get more information about system configuration.
The only difference in the contents of manually-generated and automatically-generated reports is that the
manually generated report contains no stack trace (at the time of generation) or register values. The
TSR feature is supported on Windows and non-Windows platforms.
In the event that L&TT shuts down unexpectedly, you will be prompted with the option to send a TSR to
the L&TT support team.
To manually generate a TSR from the Windows version of L&TT:
1.
Select Tool Status Report from the Help menu to display the Tool Status Report screen.
Figure 34 Tool Status Report screen (GUI)
2. Follow the steps outlined on the Tool Status Report screen.
3. Click one of the following buttons:
• Send as E-Mail—Click this button to send the TSR in an email. Use the default address
(ltt_team@hp.com) to send the TSR to the L&TT support team, or change the email address
Library and Tape Tools User Guide
119
as needed. This option does not show you the TSR, so if you want to view it, click Preview
before clicking Send as E-Mail.
NOTE:
Before L&TT can email a TSR, you must either have a MAPI-compliant e-mail program (such
as Microsoft Outlook or Outlook Express), or you must set up an e-mail account through the
Windows Control Panel or Internet Explorer. For more information about setting up an e-mail
account, see How do I configure e-mail to send support tickets
• Preview—Click this button to view the TSR in a text editor.
• Cancel—Click this button to close the Tool Status Report screen and return to the L&TT Main
screen.
To manually generate a TSR from the CSI version of L&TT:
1.
From the Main screen (and certain other screens), enter the report command to display the
Tool Status Report screen.
Figure 35 Tool Status Report screen (CSI)
2. From the Tool Status Report screen, enter one of the following commands:
• preview—displays the TSR in a text editor.
• send-email—prompts you for an email address (ltt_team@hp.com is the default) and
sends the TSR to the specified email address.
• up—exits the current command level.
• exit—exits L&TT.
120
Additional Functionality
8 Advanced Installation Topics
This chapter contains the following sections:
•
•
•
•
Other changes to the system (GUI)
Reboot criteria
Running L&TT from a CD-ROM
Files installed on the system
Other changes to the system (GUI)
The L&TT installation adds the following keys to the Windows registry:
HKEY_LOCAL_MACHINE\Software\Hewlett-Packard\HP Library & Tape Tools
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
Reboot criteria
A reboot is required only if your system requires ASPI or an upgrade to the currently installed version. On
systems that require ASPI, if the installer detects a previously-installed version of ASPI older than v4.57, it
will install a more recent version of ASPI requiring a reboot.
On Windows NT and 2000, ASPI is not installed as part of the operating system. If a reboot is
unacceptable, do not select the checkbox for this option in the installation process. If you choose not to
install ASPI, then you must use the Miniport driver (Miniport I/O mode) to scan for devices.
Issues may arise, however, when using the Miniport I/O mode with devices that use non-standard OS
drivers, or are “claimed” by other applications or the OS. When using the Miniport I/O mode when a
device is claimed, it may be necessary to shut down any running backup/storage application services
to make the device accessible to L&TT. Alternatively, using the ASPI I/O mode may make the device
accessible without requiring any further action.
Running L&TT from a CD-ROM
It is possible to create a version of L&TT that can run directly from a CD-ROM without the need for
installation or alteration of registry settings. This feature is most useful on Windows NT and Windows
2000. On other Windows platforms, it requires WINASPI to be installed.
To create a version of L&TT that can run from a CD-ROM drive:
1.
Fully install L&TT to your computer. If desired, also install any desired firmware files into the
firmware subdirectory.
2. Remove the logs directory from the L&TT install directory.
3. Write the contents of the L&TT install directory to the root directory of the CD-ROM and close the
CD-ROM.
4. Put this CD-ROM into any Windows system and run HP_LTT.exe from the root directory.
Library and Tape Tools User Guide
121
Files installed on the system
During installation, L&TT files are installed in the following directories:
Table 2 L&TT installation directory locations
Operating System
Directory Location
HP-UX, Linux, and
Tru64
/opt/ltt (main executable is hp_ltt)
Netware
SYS:System\hpltt (main executable is
hp_ltt.nlm)
Windows
C:\Program Files\HP Library
& Tape Tools (main executable is
hp_ltt.exe)
Several sub-directories are created under the main installation directory. These sub-directories are as
follows:
• Catalogs—This is the location where the message strings for the software are kept. The end-user
version has only the catalogs for the latest version of code. With the support personnel
installation, catalogs are included for previous versions (back to version 2.5), so support tickets
generated by these versions can be viewed.
• Firmware—This is the default directory where firmware files are kept. When L&TT is first installed,
this directory is usually empty (unless specific firmware images were bundled - such as the 2.7
SR2 release that includes firmware for DDS3 write recalibration). The name and location of the
firmware directory can be changed from Options > Preferences.
• Logs—This is the default directory where L&TT saves event logs and support tickets. This directory
is also used to store any script-generated files such as baseline files, results files, and so on.
• Misc—This directory is used to hold test data files and L&TT history for the specific devices on the
system. These files are used by L&TT itself and not intended for direct viewing.
• Scripts—This directory contains all the device analysis rules, add-on tests, and SCSI script files.
For more information, see Tests and Utility Functions.
With Windows installations, in addition to the files installed in the main installation directory, some files
are installed outside of the main installation directory. If ASPI installation is selected or required, the
following files are added/updated (assuming that the Windows system directory is C:\WINNT):
• C:\WINNT\System\winaspi.dll
• C:\WINNT\System32\wnaspi32.dll
• C:\WINNT\System32\drivers\aspi32.sys
Other changes to the system (CSI)
The same information that the Windows version of L&TT stores in the Windows registry is stored as a text
file for the Unix versions. This text file is located in the following directory:
• HPUX & Tru64:
/.lttreg
• Linux:
/root/.lttreg
122
Advanced Installation Topics
9 Frequently Asked Questions
This chapter addresses several of the most common questions regarding L&TT software.
Click the appropriate link:
• General questions
• Windows questions
• CSI questions
General questions
•
•
•
•
Why should I run L&TT tests?
Where can I find information about media compatibility with my hardware?
Where can I find information about hardware and software compatibility?
Where can I find information about drive cleaning requirements?
Why should I run L&TT tests?
HP StorageWorks L&TT tests are specifically designed to ensure proper diagnosis of user problems with
tape and optical devices. The tests check internal drive registers for logged data from normal operations,
and perform other data-gathering operations. This helps to pinpoint the user problem and prevents a
drive swap that won’t resolve the issue.
Where can I find information about media compatibility with my hardware?
The links in this section provide information about media compatibility with various hardware.
NOTE:
You must be connected to the Internet to view these links.
NOTE:
The recommended media for each type of drive is its native media. For example, DDS-1 media is
recommended for DDS-1 drives, DDS-2 media for DDS-2 drives, and so on.
To access the One Stop Compatibility chart for tape and optical media, see http://www.hp.com/
go/storagemedia.
The following links provide device-specific information about media compatibility:
• http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=lpg50457&l
ocale=en_US&taskId=101&prodSeriesId=63890&prodTypeId=12169
• http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=lpg50259&l
ocale=en_US&taskId=101&prodSeriesId=34643&prodTypeId=12169
• http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=lpg50082&l
ocale=en_US
• http://www.hp.com/products1/storage/products/storagemedia/ait_data_cartridge/
compatibility.html
The following links provide device-specific information about cleaning cartridge compatibility:
Library and Tape Tools User Guide
123
• DDS (Standard DDS cleaning cartridge is supported)
• http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=lpg50259&l
ocale=en_US&taskId=101&prodSeriesId=34643&prodTypeId=12169
• http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=lpg50082&l
ocale=en_US
• http://www.hp.com/products1/storage/products/storagemedia/ait_data_cartridge/
compatibility.html
Where can I find information about hardware and software compatibility?
The links in this section provide information about hardware and software compatibility.
NOTE:
You must be connected to the Internet to view these links.
• http://www.hp.com/products1/storage/compatibility/tapebackup/index.html
• http://www.hp.com/products1/storage/compatibility/tapebackup/software/index.html
• http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?obje
ctID=lpg50459#N1000C
• http://www.hp.com/products1/storage/compatibility/index.html
• http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=lpg51129
For general information about tape product compatibility, see http://h18000.www1.hp.com/products/
storageworks/tapecompatibility.html.
Where can I find information about drive cleaning requirements?
The links in this section provide information about cleaning requirements for various drives.
NOTE:
You must be connected to the Internet to view these links.
• http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?l
ocale=en_US&taskId=125&prodSeriesId=214836&prodTypeId=12169&objectID=lpg50357
• http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?l
ocale=en_US&taskId=125&prodSeriesId=34643&prodTypeId=12169&obje
ctID=lpg50258#P21_2364
• http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?l
ocale=en_US&taskId=125&prodSeriesId=34648&prodTypeId=12169&objectID=lpg50093
• http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?l
ocale=en_US&taskId=125&prodSeriesId=316234&prodTypeId=12169&obje
ctID=lpg50113#N1004C
To access the combined tape cleaning matrix for all tape drive types, see http://h20000.www2.hp.com/
bizsupport/TechSupport/Document.jsp?objectID=c00065867. In case of any conflicting information, this
matrix is the final reference.
Windows questions
• How do I run L&TT from a CD-ROM?
• How do I shut down the application in the taskbar?
124
Frequently Asked Questions
•
•
•
•
•
•
When installing L&TT for Windows, should I uninstall my previous version first?
Why can’t I uninstall L&TT or install a new version?
How do I erase an LTO FUP tape?
How do I configure e-mail to send support tickets
Does L&TT use any system resources in the background?
I am using an authenticated proxy at my site. How do I configure L&TT to connect to the HP
website to download firmware updates?
• L&TT starts in “restricted” mode and most functionality is unavailable. What is happening?
• Why doesn’t L&TT for Windows “see” devices that are connected to a computer running HP-UX?
• Why doesn't L&TT for Windows “see” my USB drives?
How do I run L&TT from a CD-ROM?
It is possible to create a version of L&TT that can run directly from a CD-ROM without the need for
installation or alteration of registry settings. This feature is most useful on Windows NT and Windows
2000. On other Windows platforms, it requires WINASPI to be installed.
To create a version of L&TT that can run from a CD-ROM drive:
1.
Fully install L&TT to your computer. If desired, also install any desired firmware files into the
firmware subdirectory.
2. Remove the logs directory from the L&TT install directory.
3. Write the contents of the L&TT install directory to the root directory of the CD-ROM and close the
CD-ROM.
4. Put this CD-ROM into any Windows system and run HP_LTT.exe from the root directory.
How do I shut down the application in the taskbar?
Under certain circumstances, L&TT may not completely shut down. To completely terminate the application:
1.
2.
3.
4.
Press Ctrl+Alt+Del.
Click Task Manager.
Click the Processes tab.
Select the process named HP_LTT.exe and click End Process.
When installing L&TT for Windows, should I uninstall my previous version first?
Beginning with version 4.0, the L&TT installer automatically uninstalls any previous versions before
installing the current version, so it is not necessary to manually uninstall your previous version.
Why can’t I uninstall L&TT or install a new version?
Some users may have problems uninstalling L&TT or installing a new version after installing or uninstalling
a previous version. This is caused by remnants of program information that remain in the Windows
registry.
The L&TT team has created a utility to manually remove any remains from previous installations. To obtain
this utility, download and execute hp_ltt_install_support.exe from the HP Support web site. The utility
completely removes any remains of previous installations quickly and safely.
After running this utility, rerun the latest L&TT installation package.
How do I erase an LTO FUP tape?
For LTO, run the LTO Firmware to Data Tape Creator test. See LTO Firmware to Data Tape Creator test
for more information.
Library and Tape Tools User Guide
125
NOTE:
FUP tapes other than LTO do not need to be erased.
How do I configure e-mail to send support tickets?
To successfully send a support ticket via e-mail directly from L&TT, you must have a MAPI-compliant e-mail
client set up for outgoing e-mail. Even if e-mail software (such as Outlook or Outlook Express) is not
installed, you can configure a simple e-mail account using the Internet Connection Wizard that comes
with Internet Explorer. To access the Internet Connection Wizard:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Launch Internet Explorer. If this is the first time to launch Internet Explorer on this machine, the
Internet Connection Wizard is displayed automatically. Follow the instructions until you reach the
step that asks whether an Internet e-mail account should be set up. Answer Yes and skip to Step
5. If this is not the first time to launch Internet Explorer on this machine, proceed with Step 2.
Select Internet Options from the Tools menu.
Select the Connections tab.
Click Setup at the top of the dialog to start the Internet Connection Wizard.
Enter a display name (this is the From name in the e-mail) and click Next.
Enter the return e-mail address and click Next. If there are no e-mail accounts on this system
that will be monitored, use your regular e-mail address at which you can be contacted by
the recipient of the support ticket.
Enter bogus as the address for the incoming mail server.
In the SMTP mail server field, enter the address of any SMTP mail server within the firewall of
your organization that accepts SMTP send requests and click Next. If you do not know which
address to use, contact your local system administator or check the mail account settings on
your regular e-mail account.
If your SMTP server requires a login to send e-mail (most sites only require a login for incoming
mail), you must provide proper account information. Otherwise, you can enter bogus in both
fields. Click Next.
Your e-mail is now configured for outgoing mail delivery.
Does L&TT use any system resources in the background?
L&TT is an application, not a service. No part of the application uses any system resources unless
the application is manually launched by the user.
I am using an authenticated proxy at my site. How do I configure L&TT to
connect to the HP website to download firmware updates?
L&TT uses the same connection properties as Internet Explorer. If you are unable to download from L&TT,
you can manually download the latest version of the firmware from the ftp site and place it in the firmware
directory found in the L&TT program directory.
You can access the L&TT firmware FTP site at:
ftp.hp.com/pub/information_storage/software/ltt/firmware.
The firmware files are named using the following convention:
LTT_<product ID>_<firmware version>.frm
For example:
LTT_A5617A_0200.frm
126
Frequently Asked Questions
L&TT starts in “restricted” mode and most functionality is unavailable. What is
happening?
L&TT automatically runs in restricted mode when it recognizes an otherwise supported device that has a
problem with firmware and requires a firmware upgrade. There are two basic scenarios:
• L&TT recognizes the device, but the device is in brain dead mode. This usually indicates that the
device firmware is corrupt and the device is responding via boot code only.
• L&TT recognizes the device by means of the product ID code, but L&TT does not recognize
the personality codes of the device.
If one of these scenarios exist, then L&TT displays a message stating that it is running in restricted mode
when it is started. The functionality of L&TT is restricted as follows:
• All features are disabled except for firmware update and support ticket.
• The support ticket shows basic information only and excludes device details.
• For firmware upgrades, L&TT enforces the Allow all files to be selected option, and
the Options button is unavailable because all options are preset.
To exit restricted mode, exit and restart L&TT. L&TT will continue to start in restricted mode until the
problem with the offending device is resolved, or the device is disconnected.
Why doesn’t L&TT for Windows “see” devices that are connected to a computer
running HP-UX?
L&TT does not support a client-server model such as the HP-UX Support Tools Manager. You cannot use
L&TT on a Windows workstation to view devices that are connected to a computer running HP-UX.
Why doesn’t L&TT for Windows “see” my USB drives?
The ASPI driver does not support USB drives. Make sure that you are using the Miniport driver.
CSI questions
•
•
•
•
•
•
•
•
•
•
•
How do I set the password?
Why does my display not show any text or only a single line of text on my HP-UX system?
Why doesn’t L&TT for HP-UX “see” some of my devices?
Why am I unable to download firmware/script files using the download option in the CSI
(HP-UX, Linux)?
Why doesn’t L&TT for Tru64 “see” some of my devices?
Why doesn&#39;t L&TT for Linux see some of my devices?
Why doesn’t L&TT for Windows “see” devices that are connected to a computer running HP-UX?
How do I disconnect a SCSI device in Tru64?
How do I connect/disconnect a SCSI device in Linux without rebooting?
Why doesn’t L&TT for OpenVMS “see” my media changer?
Why am I getting Error activating image PTHREAD$RTL while running L&TT on OVMS 7.3-1?
How do I set the password?
With a few exceptions, you may at any time enter the options command to display the Options dialog.
The password may be set from this dialog.
Notable exceptions:
Library and Tape Tools User Guide
127
• You may not enter the Options dialog when you are already in the Options dialog.
• You may not enter the Options dialog when you are past the first screen in either the Firmware
dialog or the Test dialog.
For instructions on setting the password, see Setting passwords.
Why does my display not show any text or only a single line of text on my
HP-UX system?
Display problems can happen for two reasons:
• If TERM, COLS, and ROWS are set incorrectly there can be problems. Execute the following
command:
/opt/ltt/hp_ltt -o displaytest
Follow the prompts to let L&TT analyze your settings.
• If the patch level of the host machine is too low, curses may not function properly (10.20 systems
only). Be sure to apply patch B6378DA or higher.
Why doesn’t L&TT for HP-UX “see” some of my devices?
Several things can prevent L&TT from seeing a device in HP-UX:
• If a device shows up in an I/O scan as NO_HW, this means that the device was previously
visible to the system, but currently is not. This could be because the device was unplugged
from the SCSI bus or powered down.
• L&TT does not support the NIO bus type. If your system has an HSC or PCI bus, connect your
device to that bus. If your system does not have an HSC or PCI bus, unfortunately, L&TT will
not work for you.
• The device is connected to an unsupported HBA. Connect the device to an HBA with a supported
driver. L&TT supports HBAs with the following drivers:
• c720
• c8xx
• fcpdev
• fcpmux
• If a device shows up in the I/O scan as unclaimed, you may have to install or enable the tape
driver kernel module using the SAM tool.
Why am I unable to download firmware/script files using the download option
in the CSI (HP-UX, Linux)?
If your network is protected by a firewall and web proxy, you must first specify the proxy server name and
port name using the Preferences screen.
Why doesn’t L&TT for Tru64 “see” some of my devices?
Whenever you connect or remove a device, you must reconfigure the CAM and hardware manager
layers. Furthermore, Tru64 does not support hot swapping of SCSI devices. To reconfigure the CAM
and hardware manager layers:
1. Close L&TT.
2. Use the following command to check for stale devices:
/sbin/hwmgr show scsi -full | grep stale
3. Remove any stale devices. If you are not sure whether a device is stale or not, remove it anyway.
Devices can be rediscovered later. Use the following command to remove a device:
/sbin/hwmgr -delete scsi -did <SCSI ID>
128
Frequently Asked Questions
4. Rescan the SCSI bus.
/sbin/hwmgr scan scsi
5.
Rescan the CAM layer.
/sbin/scu scan edt
6. Run the following commands to verify the SCSI devices:
/sbin/hwmgr show scsi
/sbin/scu show edt
7. Restart L&TT.
Why doesn’t L&TT for Linux see some of my devices?
To detect a surrogate SCSI device, you must configure the modules.conf file for the new device you
have connected. After modifying this file, reboot the computer so that the new device is recognized
by the scsi/sg layer. Linux does not support hot swapping of SCSI devices. To reconfigure the
modules.conf file:
1. Login as root.
2. Edit the following file:
vi /etc/modules.conf
3. Add the following line as appropriate:
add options scsi_mod max_scsi_luns=128
4. Reboot the computer.
Why doesn’t L&TT for Windows “see” devices that are connected to a computer
running HP-UX?
L&TT does not support a client-server model such as the HP-UX Support Tools Manager. You cannot use
L&TT on a Windows workstation to view devices that are connected to a computer running HP-UX.
Library and Tape Tools User Guide
129
How do I disconnect a SCSI device in Tru64?
1.
Locate the SCSI device in hardware manager:
/sbin/hwmgr -show scsi
2. Use the following command to delete the SCSI device.
/sbin/hwmgr -del scsi -did <SCSI ID>
3. Disconnect the device.
4. Make sure that you have removed the corresponding SCSI cable from the HBA.
How do I connect/disconnect a SCSI device in Linux without rebooting?
• To add a new device, connect the device and run the following command:
echo "scsi add-single-device <hostid> <busid> <targetid> <lunid>"
>/proc/scsi/scsi
• To remove a device, run the following command and disconnect the device.
echo "scsi remove-single-device <hostid> <busid> <targetid> <lunid>"
>/proc/scsi/scsi
Why doesn’t L&TT for OpenVMS “see” my media changer?
OpenVMS does not automatically recognize media changer devices. Media changer devices must
be associated with the GKDRIVER (generic SCSI driver). To associate media changer devices with
GKDRIVER, use the following command in OpenVMS:
SYSMAN IO CONNECT <devicename> /DRIVER=SYS$GKDRIVER /NOADAPTER
The form for <device name> is G<x><z><uuu> where:
• <x> indicates whether the media changer is connected to a SCSI or Fibre Channel HBA.
• Use “K” for SCSI.
• Use “G” for Fibre Channel.
• <z> is the HBA identifier (A-Z).
• <uuu> is the SCSI target ID and LUN ID combined.
For example, with a media changer having SCSI target ID 4, LUN ID 0, and connected to the second
SCSI HBA, the device name is GKB400.
•
•
•
•
•
“G” indicates that this device is associated with the generic SCSI driver (GKDRIVER).
“K” indicates that the device is connected through a SCSI interface.
“B” is the second SCSI HBA (HBAs typically have names from A to Z).
“4” is the SCSI target ID.
“00” is the SCSI LUN ID.
Why am I getting Error activating image PTHREAD$RTL while running L&TT
on OVMS 7.3-1?
L&TT on an OVMS 7.3-1 system requires the VMS731_UPDATE V5.0 patch (or a later version) for
proper execution.
130
Frequently Asked Questions
10 Troubleshooting
This chapter is divided into the following sections:
• Troubleshooting L&TT
• Troubleshooting devices
• Troubleshooting third-party software
Troubleshooting L&TT
If you believe that you have encountered a software issue with the L&TT program itself, send an e-mail to
LTT_team@hp.com. Please be sure, as much as possible, that it is an L&TT issue rather than a product
issue. When sending the e-mail, include the following:
• A description of the issue
• What was being done. How it failed. Symptoms.
• Try to include the exact wording of any error messages received. This makes it much easier for
the developers to find in the code.
• The configuration of the system
• System type, OS type and variant, patch status
• HBA type, drivers used, revisions
• Device type, firmware revisions
• Connectivity—FC/SCSI, SAN, or direct connect
• Key L&TT logging data
• The event log (with I/O history enabled). The I/O history enabled event log contains critical
information that HP programmers can use to debug problems with the application itself. In
the event of a device detection issue, support ticket generation issue, firmware update issue,
or other problem, see Using the event log (Windows) for instructions on how to enable I/O
history in the event log. Restart L&TT and perform the operation that failed previously. The
event log will capture critical I/O information.
• A TSR (Tool Status Report). See Using the Tool Status Report.
Be prepared to provide additional information if requested by the L&TT support team. You can also send
comments, feedback, suggestions, and questions to LTT_team@hp.com.
Troubleshooting devices
Click the appropriate link:
• Using L&TT to troubleshoot tape devices
• Known issues
• Additional interactive device troubleshooting content
Using L&TT to troubleshoot tape devices
HP requests that customers perform diagnostics on their drive before requesting a replacement. This
section tells you how, why and when to run these diagnostics to the extent that you can identify and
potentially fix your problems without the need to contact HP support. If it is determined that your tape
drive is not functioning correctly and does need to be exchanged, then the accompanying failure
information enables you to get a faster response from HP support.
Library and Tape Tools User Guide
131
This section starts from the most common questions you may have concerning the health of your tape
drive. You can work through each of them in turn or pick one that is most appropriate to your problem.
Additional pointers are provided if the problem is not found to be with your tape drive. This section
currently only covers standalone drives.
Click the appropriate link:
•
•
•
•
•
•
Are you performing regular maintenance?
Is the drive connected properly?
Is the drive working as expected?
Is the drive firmware up to date?
Is the drive performing as expected?
Is the media in good condition?
Are you performing regular maintenance?
The health of your tape drive and media are highly influenced by the way they are treated. Good
maintenance will help prevent many problems.
• Maintenance
• Keep firmware up-to-date
• Use drive in a clean and controlled environment
• Clean drive when indicated to do so
• Periodic health checks
• Run L&TT Drive Assessment test
• Run L&TT Media Analysis test on tapes holding key data
• Follow good practice
• Take care of your media
• Make frequent backups
• Make redundant backups for critical data
Is the drive connected properly?
If your application does not recognize your drive, do the following:
• Check all physical connections and cable integrity.
• Verify that the proper HBA and tape drivers are installed.
• Verify that the operating system and backup application are configured properly.
If the problem persists, try the following:
• Run L&TT in installcheck mode. Installcheck mode performs several checks to determine if your
hardware is connected properly. See Using the Installation Check feature.
• Run the Assessment test for your drive. If the drive passes the Assessment test, then you should
look elsewhere for the problem. If the drive fails, the test may provide enough information to help
you resolve the problem. Otherwise, contact HP support. See Assessment test.
Is the drive working as expected?
If you suspect that your drive is not working properly, run the Assessment test for your drive. If the drive
passes the Assessment test, then it is considered to be working well with the tape you provided. If the
drive fails the Assessment test, the problem might be caused by:
• Poor media, in which case you should run the test again with a different tape
• Dirty heads, in which case you should try using a cleaning tape
If the drive still fails after trying both of the above then the issue is most likely with the drive. In this case,
contact HP support and have the results of the test ready.
132
Troubleshooting
For more information about the Assessment test, see Assessment test.
Is the drive firmware up to date?
It is important to keep the drive firmware up to date. Firmware updates include improvements to resolve
known field issues. For more information about using L&TT to update firmware, see Uploading firmware
to devices (GUI) or Uploading firmware to devices (CSI).
Is the drive performing as expected?
If you believe that your drive is not performing to specification, L&TT has three tests to measure
performance:
• Drive Performance test—measures the transfer rate of the drive, HBA, and cabling. See Using
the Drive Performance Test.
• System Performance test—actually consists of two separate tests:
• Backup Performance test—measures the data source transfer rate from the disks or network
for backup.
• Restore Performance test—measures the data restore transfer rate to the disks or across the
network for restores.
For more information about using these tests, see Using the System Performance Test.
These tests measure the actual transfer rates, enabling you to determine if a performance problem
exists, and if so, whether the problem is with the drive or the system. In most cases, system performance
is the limiting factor. For detailed information about finding and fixing performance issues, see
http://www.hp.com/support/pat.
Is the media in good condition?
If you suspect a problem with media, L&TT provides several tests that check media integrity. Click the
following links for detailed information about each test:
•
•
•
•
•
Media Analysis test
Media Validation test
MO Media Validation test
SDLT Read Media IDs test
SDLT Tape Edge Damage test
If the media fails one or more of the above tests, and the drive is considered to be in good condition
(see Is the drive working as expected?), then it is likely that your media is bad. In this case, you have
a number of options:
• If the data is still available on your system, make a backup of that data to another tape.
• Perform the Media Analysis test in a different drive. It is possible that the drive that wrote the data
was also suspect, but a different drive might be able to read the data.
• Contact HP support for assistance.
Known issues
Click the appropriate link:
• Device access issues (RSM on Windows)
• Device performance issues
• Firmware issues with Ultrium drives
Device access issues (RSM on Windows)
On many operating systems, most backup applications require exclusive access to tape devices to avoid
interference between multiple processes accessing the same device. While there are differences between
Library and Tape Tools User Guide
133
operating systems regarding how services and applications run, how they are monitored, and which error
messages are displayed by L&TT when a conflict is detected, the basic issue remains the same: devices
may show as inaccessible in L&TT if they are still claimed by another process.
As a result, you cannot run L&TT and a backup application at the same time. If a backup application
is still running, L&TT is unable to gain access to the tape drives, and functionality in L&TT is restricted.
Similarly, if L&TT is running and a backup application tries to execute a scheduled job, the job
may fail because it cannot access the drive. It should be noted that backup applications refers
to service processes, drivers, or typical backup software applications. The Windows Removable
Storage Management service (RSM) is an example of a process that blocks access to tape libraries
and drives; it must be disabled or shut down before using L&TT. The L&TT splash screen contains
a reminder of this. For more information on RSM, including how to disable and re-enable it, see
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c00023443.
On large SANs, it is often impossible to entirely close all software applications while trying to run L&TT
on a single drive. In these situations, use the SAN awareness features to bypass conflicts on all other
devices, and focus on a single robotics controller or tape drive. However, even in this scenario, this single
device must be released from control of any other software via appropriate means.
On the Windows platform, there are two I/O modes available: NT Miniport I/O mode and ASPI I/O
mode. The ASPI I/O mode has the ability to circumvent these exclusivity restrictions because it does not
honor the security system built into the server variants of Windows, related to mutual exclusivity. This is
also the reason that Microsoft views ASPI as a deprecated I/O model that should only be used when
necessary. If you use ASPI to circumvent the exclusive access restriction, take extreme care to understand
any interference that may occur, and interpret results accordingly.
Device performance issues
Click the appropriate link:
• Poor performance with HP DLT VS80 and CA Brightstor v11 on Windows
• Poor performance on Windows 2003 Server systems with EBS installations
Poor performance with HP DLT VS80 and CA Brightstor v11 on Windows
If backups are very slow, and the hardware and media are known to be good, try the following to
improve backup performance:
• Stop the CA Brightstor Tape Engine service and locate the following registry folder using
Regedt32.exe:
HKLM/Software/Computer Associates/Brightstor ARCserve Backup/Base/
TapeEngine/DEVICE#/
• Look at the Info value for the device# that corresponds with your DLT drive, then ADD DWORD
value:
data type=Reg_Dword
valuename=DefaultBlockFactor
data=7, HEX
• Restart the CA Brightstor Tape Engine service. File backup should now be much faster.
Poor performance on Windows 2003 Server systems with EBS installations
Many of the ISV Backup Applications supported by HP request or require that the RSM service be
disabled. When the Windows 2003 server is rebooted, even though RSM is disabled, it continues to
initiate the Test Unit Ready (TUR) SCSI command indefinitely on all connected removable devices. This
can cause issues with performance in an environment with many shared tape devices. See the Microsoft
Knowledge Base Article 842411 at http://support.microsoft.com/default.aspx?scid=kb;en-us;842411 for
instructions on how to work around this problem.
134
Troubleshooting
Firmware issues with Ultrium drives
Changes in Ultrium firmware packages made for L&TT v3.5 may cause firmware downloads to fail, hang,
or report a wrong personality error if running L&TT v3.4. To avoid this, upgrade to L&TT v3.5 or later and
use the tool’s ability to retrieve firmware from the web to get the correct firmware version.
Additional interactive device troubleshooting content
The following links provide additional interactive troubleshooting content for various storage devices.
NOTE:
You must be connected to the Internet to view these links.
•
•
•
•
http://hp.com/support/ultrium215troubleshooting
http://hp.com/support/ultrium230troubleshooting
http://hp.com/support/ultrium460troubleshooting
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?obje
ctID=c00057819&locale=en_US
• http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&obje
ctID=c00048372
• http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?obje
ctID=c00192945&locale=en_US
Troubleshooting third-party software
Click the appropriate link:
• Backup failed
Backup failed
If a backup application reports that a backup failed and you suspect that the problem lies with the
tape device or media, follow the troubleshooting procedures outlined in Using L&TT to troubleshoot
tape devices.
If the issue is found to be with the tape device or media, take the appropriate corrective action. If the
device is healthy and the media is good, then the issue is likely to be with another component in the
system, or with the configuration of the backup application. Refer to the documentation shipped with the
backup application to verify correct configuration.
Library and Tape Tools User Guide
135
136
Troubleshooting
Index
A
Acceptance test
See Assessment test
add I/O history to event log option, 102, 108
additional information, finding, 16
allow firmware downgrading option, 47
allow selection of any firmware file option, 47
ASPI
described, 28
support, 18
Assessment test, 61
attach additional event log option, 94
attach result log option, 94
audience, 11
Autoloader Exerciser test, 64
B
brain dead mode, 118
By Connection tab, 30
By Product tab, 30
C
cartridge command, 41
cautions
changing devices, 30
exclusive use of device by L&TT, 47
improper script usage, 86
interrupting firmware update, 49
swapping SCSI devices, 30
tests destructive to data, 59
changing devices, caution, 30
check for updates on the web option, 44, 107,
109
clear command, 58
Command Help screen (CSI), 37
commands
cartridge, 41
clear, 58
detail, 58
exit, 37
find, 100
firmware, 49
load, 99
options, 49
page, 58, 100
picktest, 58
preferences, 106, 110
review, 49, 58
save, 99
select, 37, 40
start, 49, 58
test, 58
view, 99
compatibility matrix, 15
Connectivity test, 64
conventions
document, 12
text symbols, 12
current password entered option, 108
D
Data Compression test, 64
data phase limit for I/O history option, 108
detail command, 58
Device Analysis Test
described, 83
using, 83
Device Analysis test, 65
Device Information screen
CSI, 40
GUI, 31
Device Information screen (CSI), 40, 41
device list (GUI), 30
Device Performance screen (CSI), 78
Device Self-Test, 65
display dialogs for I/O pending more than 2
minutes option, 107
display splash screen at startup option, 107
DLT SRAM Check test, 65
document
conventions, 12
Drive Information tab, 33
Drive Performance screen (GUI), 76
drive performance test, 59, 76
Library and Tape Tools User Guide
137
E
email setup, 93, 126
Email Support Ticket dialog box (GUI), 93
emailing, support ticket, 89, 93
erasing an LTO FUP tape, 125
ESL Vendor ID test, 66
event log
as a SCSI analyzer, 102
described, 102
using, 102
exclusive use of device by L&TT, caution, 47
exit command, 37
F
Factory Firmware Overrides dialog box (GUI),
47
factory password, obtaining, 91
features, 15
files installed on the system, 122
find command, 100
firmware
accessing revision and release note
information, 43
acquiring (CSI), 48
advanced options (GUI), 47
allow downgrading, 47
allow selection of any file, 47
directory, 44
downloading, 44, 44, 48
files, acquiring, 44
selecting files, 45
update activity log, 47
update product ID option, 48
uploading to devices, 46
uploading to devices (CSI), 49
viewing revision history, 46
firmware command, 49
firmware file path option, 107
Firmware Management screen, GUI, 34
Firmware Tape Creator test, 66
Firmware Update screen (GUI), 46
Front Panel function, 111
Front Panel screen (GUI), 111
Full Sweep test, 67
G
Get Files from Web dialog box-firmware tab
(GUI), 45
138
Get Files from Web functionality
CSI, 48
GUI, 44
H
help
obtaining, 12
HP
storage web site, 13
Subscriber’s choice web site, 13
technical support, 12
HP-UX
installing L&TT, 22
starting L&TT, 36
Support Tools Manager, 129
I
I/O mode
ASPI, 18, 28, 121
Miniport, 18, 28, 30, 121
icons, GUI and CSI, 17
improper script usage, caution, 86
Initialize Element Status test, 67
installation
ASPI, 18
directories created, 122
files installed, 122
HP-UX, 22
Linux, 22
NetWare, 20
problems installing or uninstalling, 125
reboot criteria, 18, 121
Tru64, 22
uninstalling L&TT, 17, 125
upgrading from previous version, 17, 125
Windows, 17
Installation Check feature, 116
Installation Check test, 68
Installation Check wizard, 117
installcheck mode, 116
Instructions tab, 30
Internet Connection Wizard, 126
Internet Explorer, 126
Internet update functionality, using, 109
interrupting firmware update, caution, 49
L
L&TT
display problems, 128
features, 15
main screen layout (GUI), 29
problems seeing devices, 128, 128, 129,
129
running from a CD-ROM, 121, 125
safeguards, disabling, 49
splash screen, 25
starting
for HP-UX, 36
for NetWare, 36
for Tru64, 36
starting for Windows, 25
supported operating systems, 15
supported products, 15
terminating, 125
uninstall utility, 125
use of system resources, 126
using with an authenticated proxy, 126
Library Exerciser test, 68
library exerciser test, 85
Linux
disconnecting a SCSI device, 130
installing L&TT, 22
starting L&TT, 36
load command, 99
log directory, 87
log file, 87
log file path option, 107
LTO Cooling Check test, 69
LTO Firmware to Data Tape Creator test, 69
LTO FUP tape
erasing, 125
LTO Stuck Tape test, 69
M
Main screen (CSI), 39
manual product identification feature, 114
MAPI-compliant email programs, 93
Media Analysis test, 70
media analysis test, 84
Media Erase test, 70
Media Validation test, 71
Miniport, 28, 30
driver, 18, 121
I/O mode, 18, 121
MO Media Validation test, 71
Move Media function, 112
Move Media screen (GUI), 112
N
navigation, screen, 37
NetWare
installing L&TT, 20
starting L&TT, 36
O
OpenVMS
using with media changers, 130
options command, 49
Options screen (CSI), 49
P
page command, 58, 100
password
entering, 49
features that require one, 110
obtaining, 47, 49, 91
setting, 110, 128
using, 110
picktest command, 58
preferences
available options, 107
setting, 106
preferences command, 106, 110
Preferences dialog box
CSI, 107
GUI, 106
Q
Quiet Mode feature, 115
R
Read/Write Stress test, 72
Read/Write test, 72
read/write test, 84
reports
example screen, 91
overview, 87
Restore Factory Default Settings test, 73
restricted mode, 118, 127
review command, 49, 58
S
save command, 99
Saved/Manual Scan screen, 27
Saved/Manual Scan screen (CSI), 38
scan mode
CSI, 38
GUI, 26
Scan Mode Selection feature, GUI, 25
Scan Mode Selection screen, CSI, 38
Scan tab, 30
Library and Tape Tools User Guide
139
screens
Command Help (CSI), 37
Device Information (CSI), 40, 40, 41
Device Information (GUI), 31, 31, 32
device list (GUI), 30
Device Performance (CSI), 78
Drive Performance (GUI), 76
Email Support Ticket dialog box (GUI), 93
example report, 91
Factory Firmware Overrides dialog box
(GUI), 47
Firmware Management (GUI), 34
Firmware Update (GUI), 46
Front Panel (GUI), 111
Get Files from Web dialog box-firmware tab
(GUI), 45
L&TT main screen (GUI), 29
Main (GUI), 29
Move Media (GUI), 112
navigating, 37
Options (CSI), 49
Preferences (CSI), 107
Preferences (GUI), 106
Saved/Manual Scan, 27, 38
Scan Mode Selection (CSI), 38
splash screen, 26
Support Ticket Generation (GUI), 36
System Performance Backup Pre-Test (CSI),
82
System Performance Backup Pre-Test (GUI),
81
System Performance Restore Pre-Test (CSI), 83
System Performance Restore Pre-Test (GUI),
79
Tests (GUI), 35
script file path option, 107
scripts directory, 86
SCSI analyzer, 102
SCSI scripts, 57
SDLT Read Media IDs test, 74
SDLT Tape Edge Damage test, 75
select command, 37, 40
show instructions option, 107
show scan details option, 107
skip this dialog in the future, 29
Skip-Scan feature
CSI, 39
GUI, 27
Skip-Scan feature, described, 26
140
splash screen, 25
start command, 49, 58
Subscriber’s choice, HP, 13
support resources, 16
support ticket
comparing, 94
compressing, 94
converting to HTML, 88
detail level, 87, 90
email setup, 93, 126
emailing, 89, 93
event data, viewing, 91
event explanation, viewing, 91
generating, 87, 100
information reported, 101
log file, 87
other functionality, 91
overview, 87
reference data, viewing, 91
saving, 89
viewer, 87
viewing, 89, 90, 100
Support Ticket Generation screen (GUI), 36
swapping SCSI devices, caution, 30
symbols in text, 12
System Performance Backup Pre-Test, 80
System Performance Backup Pre-Test screen
(CSI), 82
System Performance Backup Pre-Test screen
(GUI), 81
System Performance Restore Pre-Test, 79
System Performance Restore Pre-Test screen
(CSI), 83
System Performance Restore Pre-Test screen
(GUI), 79
System Performance Test, 79
T
tabs
By Connection, 30
By Product, 30
Drive Information, 33
Instructions, 30
Scan, 30
taskbar, 29
technical support
HP, 12
test command, 58
tests
Assessment, 61
Autoloader Exerciser, 64
Connectivity, 64
Data Compression, 64
descriptions, 59
destructive to media, caution, 59
Device Analysis, 65, 83
Device Self-Test, 65
diagnostic, 60
DLT SRAM Check, 65
drive performance, 59, 76
ESL Vendor ID, 66
Firmware Tape Creator, 66
Full Sweep, 67
Initialize Element Status, 67
Installation Check, 68
Library Exerciser, 68
library exerciser, 85
LTO Cooling Check, 69
LTO Firmware to Data Tape Creator, 69
LTO Stuck Tape, 69
Media Analysis, 70
media analysis, 84
Media Erase, 70
Media Validation, 71
MO Media Validation, 71
overview, 57
Read/Write, 72
read/write, 84
Read/Write Stress, 72
Restore Factory Default Settings, 73
running (CSI), 58
running (GUI), 58
SDLT Read Media IDs, 74
SDLT Tape Edge Damage, 75
System Performance, 79
system performance, 59
viewing (CSI), 58
viewing (GUI), 58
Tests screen (GUI), 35
text symbols, 12
Tool Status Report
CSI, 120
GUI, 119
Tru64
disconnecting a SCSI device, 130
installing L&TT, 22
starting L&TT, 36
U
uninstall utility, 125
update product ID option, 48
upgrading from previous version, 17, 125
utility functions, 57
described, 86
using, 86
V
view command, 99
W
web sites
HP documentation, 13
HP storage, 13
HP Subscriber’s choice, 13
websites
HP support, 44, 48
L&TT tapetools, 16
Windows
ASPI support, 18
installing L&TT, 17
Internet Explorer, 126
reboot criteria, 18, 121
starting L&TT, 25
Library and Tape Tools User Guide
141
Download PDF
Similar pages