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. 3. 4. 5. Double-click the self-extracting executable file to launch the installer. The InstallShield Wizard screen is displayed. Click Next. Read the program license agreement and click Yes if you agree to and accept the terms of the license agreement. Read the readme file for any last-minute changes to the documentation, then click Next. The Select Features screen is displayed. 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

Installation

(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 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. 7. 8. 9. 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. 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. On the Ready to start installation process screen, click Next. If you need to review or change installation settings, click Back. When installation is complete, the InstallShield wizard displays its final screen. Select Start HP L&TT or Run LTT InstallCheck if you would like the wizard to start L&TT or the Installation Check test. Click Finish to close the InstallShield wizard.

Installing L&TT for NetWare
NetWare installation prerequisites
Download link Install time (typical) Reboot requirements Software dependencies/prerequisites http://www.hp.com/support/tapetools Less than 2 minutes None Device should be recognized by the 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. None
To install the NetWare version of L&TT: 1. 2. Download the L&TT for NetWare file to a temporary directory. 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.
Installing L&TT for HP-UX, Tru64, and Linux
HP-UX installation prerequisites
Download link Install time (typical) Reboot requirements Software dependencies/prerequisites http://www.hp.com/support/tapetools Less than 3 minutes None 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 None.
Tru64 installation prerequisites
Download link Install time (typical) Reboot requirements http://www.hp.com/support/tapetools Less than 3 minutes A reboot occurs only if hardware manager failed to recognize the connected device. 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. None
Software dependencies/prerequisites
Linux installation prerequisites
Download link Install time (typical) Reboot requirements Software dependencies/prerequisites http://www.hp.com/support/tapetools Less than 3 minutes None Device should be recognized by proc/SCSI subsystem. Device drivers for the connected tape devices/libraries or default device driver should be present. To install L&TT, you must first uninstall any previous versions.

Accessing firmware revision and release note information via the Web (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. To view the latest firmware revisions for devices on your system, or for all devices, click the Firmware tab, and then select the appropriate option. To view release note information, click the product ID of the firmware file whose information you want to view, and then click Details. 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.
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.
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. 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.
Accessing information about local firmware files
You can access the release notes for firmware files in the local firmware from both the GUI and the CLI.
Accessing release notes for local firmware files (GUI)
To view the firmware release notes for the firmware files in the local firmware folder, in the Local Firmware Files tab select one of the firmware files and click Release Notes.
Figure 19 Linking to release notes for local firmware files

Accessing details for local firmware files (CSI)
To view firmware details, use the localfrmlist command, which will list the firmware files in the local firmware directory.

Firmware management

Figure 20 Local firmware list produced by the localfrmlist command
To view the details of a firmware file, use the details command with the number of the firmware file from the Local firmware list. For example details 2, will list the details for the DAT160 firmware file in Figure 20.
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. 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. 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.

Running the tests (CSI)

To select and run a test manually: 1. On the Main screen, enter the number corresponding to the device that you want to test. The device information screen opens.
On the device information screen, enter the test command. The Test screen displays the currently selected test with a description, and lists the available devices to be tested.
Figure 27 Information screen for the currently selected test
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 opens again and updates the currently selected test. 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. If any options are available for the selected test, enter the testoptions command to review and set the desired options for that test. In the Test Options screen, enter the command description <OptionNum> to see the description for that option in the next screen. Enter the start command to start the test.
NOTE: On HP-UX and Linux, if multiple drives are selected, the tests will run in parallel.
Viewing test results (CSI)
When the test is complete, a dialog shows preliminary results of the test. Press any key to go to the test results viewer screen. Test results are displayed in a tree format for each tape drive. 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: 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.)
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.

Aborting a test (CSI)

Selected L&TT tests can be stopped with Ctrl-A before they complete. Check the test description to see whether the test can be aborted. When running a test that can be aborted, the status line displays the message Press 'Ctrl-A' to abort the test.
Figure 28 Command line for a test that can be aborted
After you press Ctrl-A, L&TT displays a message that the abort command has been received and that it is trying to abort the test. It can take some time for the message to be displayed and ultimately to abort the test.

NOTE: If the drive to be tested in part of an autoloader or library, the autoloader or library should be in random mode prior to running the test. DDS Assessment tests performed: NOTE: L&TT versions 4.8 and above have two versions of the DDS Assessment test. L&TT will offer the test applicable to your tape drive. Original test Review event log entries (that 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 Newer test Requires that cartridge be already loaded or in the process of loading when the test is started. Looks at the drive history (runs device analysis and looks for at DDS report information). Checks whether the drive is requesting cleaning. Write 1GB of data for DAT72 and below and 2GB of data for DAT160 and above and then measures the write margin. Read 1GB of data for DAT72 and below and 2GB of data for DAT160 and above and then measures the read margin 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 Test names LTO Drive Assessment test SDLT Drive Assessment Test DDS Drive Assessment Test Options LTO Assessment test options: For the LTO test, the following four options are available: Enable Passive Test (defaults to TRUE) analyzes drive history (runs device analysis and looks at LTO Reports information) Allow Overwrite (defaults to FALSE) set to TRUE to avoid the popup warning about erasing data on the test tape Ignore Cleaning Requests (defaults to FALSE) when TRUE the test will not check whether the drive is requesting cleaning Amount of Media to Test (default is four wraps) select Entire Tape to test all of the tape Number of Iterations (default is one) the number of times to run the write portion of the test SDLT Assessment test options: Media Test (defaults to FALSE) writes and reads, looking for tape errors, including servo errors Allow Overwrite (defaults to FALSE) set to TRUE to avoid the popup warning about erasing data on the test tape DDS Assessment test options:
NOTE: L&TT versions 4.8 and above have two versions of the DDS Assessment test. L&TT will offer the test applicable to your tape drive. Original test Allow Overwrite (defaults to FALSE) set to TRUE to avoid the popup warning about erasing data on the test tape Newer test Enable Passive Test (defaults to TRUE) analyzes drive history (runs device analysis and looks at DDS Reports information) Allow overwrite (defaults to FALSE) set to TRUE to avoid the popup warning about erasing data on the tape. Ignore Cleaning Requests (defaults to FALSE) when TRUE the test will not check whether the drive is requesting cleaning Amount of Media to Test (defaults to 1GB for DAT72 and below and 2GB for DAT160 and above) select Entire tape to test all of the tape. Number of Iteration (default is one) the number of times to run the write portion of the test. When to run Run this test if you suspect a drive has failed. You should run the Media Test option if you are 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. 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 Assessment test with the Media Test option enabled is 20 minutes, but it can take longer with a bad tape. Requires a good tape that will be overwritten as part of test. The LTO and DDS Drive Assessment test can be stopped before it completes. To abort the test from the GUI, click Abort Test. To abort the test from the CSI, use the Ctrl-A key combination. The test will not run with a tape that has been partitioned. DLT 4000/7000/8000 DLT1/VS80/VS160 SDLT 220/320/600 LTO1 (Ultrium 215 and 230), LTO2 (Ultrium 448 and 460) drives, and LTO3 drives (Ultrium 920 and 960) DDS3, DDS4, and DAT72 (pre- and post-merger HP drives only) Original test

This test can only be run if the drive used has recently passed the DDS Drive Assessment test, which will ensure that any failures can be specifically attributed to the media. CAUTION: This test is destructive (if the Test Type option is Overwrite) and will overwrite data on the media that is present in your device.
NOTE: For instructions on how to perform this test, see Running the tests (GUI) on page 77, Running the tests (CSI) on page 80, or Running tests (CLF) on page 155.

Options

There are two recommended options to control the behavior of the test: Test Type (default is Read Only) To run the Read Only (data quality assessment) test, set the Test Type option to Read Only. To run the Overwrite (media assessment) test, set the Test Type option to Overwrite. Amount of Media to Test The default amount of data read varies by drive/tape generation (1 GB of data for DAT72 and 2 GB of data for DAT160 / DAT320) and is enough for a valid read margin calculation to be performed. The data read is sampled across the data on the media between BOD (beginning of data) and EOD (end of data). The larger the value for this option, the greater amount of data is read at each sample. This is done to enable an effective test to be performed in a reasonably short period of time approximately 8 minutes using the default value. To fully check all of the data written on the media, set the Amount of Media to Test option to Entire Tape, but note that this will take more time. The following test options allow the test to be run outside of the standard operation parameters. However, do not use these options unless advised to do so by HP Support: Check WORM integrity (default True) When this option is set to True, the Read Only test can be run on a WORM cartridge, which checks the integrity of the WORM media and verifies that no one has tampered with the WORM cartridge. This test does not allow writing to a WORM cartridge. Ignore cleaning requests (default False) If the tape drive to be tested is requesting cleaning, clean the drive before running the test. However, if a cleaning cartridge is not available, you can bypass this check by setting this option to True. In that case, the test will report that non-standard test options were used so the results of the test cannot be guaranteed.
Allow Unqualified Drives (default False) Normally, this test can only be run if the drive has recently passed the DDS Drive Assessment Test, ensuring that the drive is in good condition. This option is used to bypass this check, which is not recommended because any failures cannot necessarily be attributed to the media. When to run Run this test with the Test Type option set to Read Only (default) when you want to check that the data on tape is of a high quality. Run this test with the Test Type option set to Overwrite when you want to check that the media itself is in good condition. Test times vary greatly depending on drive type, media quality, and options selected. With the default test options, the average time is approximately 8 minutes for a healthy drive with a good tape. This test will overwrite all data on the media if the Test Type option is Overwrite. If the drive to be tested is part of an autoloader, the autoloader should be in random mode prior to running the test. DAT72, DAT160, and DAT320 (pre and post-merger HP drives only).

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) on page 77 or Running the tests (CSI) on page 80.
When cartridges have been manually removed, use this test script to initialize the library. Depending on the library, this test may take over 30 minutes. Test will not overwrite any data on the media. All libraries supported by L&TT.

Installation Check test

Description The Installation Check is not executed in the same way as other L&TT tests. 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 on page 177. 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) on page 77 or Running the tests (CSI) on page 80.
Run L&TT in Installcheck mode when you want to verify the correct configuration of supported devices. When L&TT is run in Installcheck mode, the Installation Check wizard opens. 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 HP SDLT 320 drive HP VS80 drive DDS tape drives

Library Exerciser test

CAUTION: When run on the MSL, ESL, and EML series libraries, this test does NOT overwrite data. However, on other libraries, this test may overwrite data depending on how the test options are configured.
This is a general-purpose test of the library. The test exercises the library robotics by moving media to and from all of the selected elements in the library. There are two versions of this test, depending on the library model. For more information, see Using the Library Exerciser Test on page 122. NOTE: For instructions on how to perform this test, see Running the tests (GUI) on page 77 or Running the tests (CSI) on page 80.

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. < 10 minutes, using default test options Test will overwrite all data on the media. This test can be stopped before it completes. To abort the test from the GUI, click Abort Test. To abort the test from the CSI, use the Ctrl-A key combination. 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.
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; in that case it is better not to 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. < 1 minute None 4X, 8X, and 14X MO drives
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 Read Media IDs test on page 111 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 bar code 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) on page 77 or Running the tests (CSI) on page 80.

true performance, run the test with this option unselected. You can enable this option only when Read After Write and Fixed Block Mode are selected. 6. Click Start to perform the test. Progress of the test is displayed under the Progress column for the corresponding drives. The numbers indicate the percentage of test completion. A dialog box will appear to inform you when the test is complete. Click the Drive Performance Results tab to view the results of the test. In the Drive Performance Results tab, all the operations corresponding to each of the individual drives are displayed under the corresponding tree nodes.
Figure 32 Drive Performance Results tab
For Linux, HP-UX, Solaris, OpenVMS, and MAC OS X, the devperf command is available for libraries and tape drives. In the case of a library, the test can only be run on the drives associated with the selected library. If multiple drives are selected, the test will be run in parallel on all of the drives. For Tru64, the devperf command is only available for tape drives and the test can only be run on one drive at a time. 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 you select a device. 2. The Device Performance Tool screen shows the drives on which test can be run. For a library, only the drives associated with the library are selectable.
Figure 33 Device Performance Tool screen
To see the test options for devperf, use the command testoptions in the Device Performance Tool screen. The testoptions are applicable to all devices selected for the test.
Figure 34 Test Options screen
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. Compare after Read This option checks the integrity of the data but will reduce the transfer rate of the test. Performance is not reported when this option is selected. To measure true performance, run the test with this option unselected. This option is only valid when the readback option is enabled in the test.

Using the Library Exerciser test
There are two versions of the Library Exerciser test depending on the model of the library or autoloader being tested. The latest version of the Library Exerciser test is used on the MSL2024, MSL4048, MSL8048, MSL8096, EML, ESL 9000, and MSL 5000/6000 libraries, and the 1/8 G2 tape autoloader. Other library models use a previous version of the Library Exerciser test (see Using the original version on page 123).

Using the new version

By default, the new version of the Library Exerciser test verifies that the device robotics can access every drive, storage, and mail slot element in the library or autoloader by physically performing media moves to each location. Optionally, a subset of elements can be selected to focus the test on a specific area of the library or autoloader. NOTE: This test can take a long time on very large libraries. If a shorter test is desired, use the test options to select a subset of elements to test. The test requires at least one piece of media in the storage and mail slot elements that are selected for test. By default, the test attempts to verify media compatibility, so if multiple tape technologies or generations are present in the library, one cartridge of each applicable type should be present. The MSL2024 and MSL4048 libraries, and 1/8 G2 tape autoloader also require at least one empty element in the selected storage and mail slot range. The following options are available for this test: Perform inventory at start of test By default, this option is set to False because the inventory operation can take a long time on large libraries. If the inventory information needs to be updated, setting this option to True causes an Initialize Element Status command to be issued to the library at the start of the test. Test loop count (all operations except inventory) Allows multiple loops of the test to be run. The inventory operation (if selected) only runs prior to the first loop. The default value is 1. Test drive range (all, x-y, or none) Specify the range of drives to be tested. Specify all to test all drive elements. Specify none to skip all drive elements. Specify a single number (5, for example) or a range (2-5, for example) to test specific drive elements (numbering starts at 1). Test Import/Export range (all, x-y, or none) Specify the range of import/export (mail slot) elements to be tested. Specify all to test all import/export elements. Specify none to skip all import/export elements. Specify a single number (5, for example) or a range (2-5, for example) to test specific import/export elements (numbering starts at 1). Test slot range (all, x-y, or none) Specify the range of slot (storage) elements to be tested. Specify all to test all storage elements. Specify none to skip all storage elements. Specify a single number (5, for example) or a range (2-5, for example) to test specific storage elements (numbering starts at 1). Ignore barcode labels and media types when selecting tapes To ensure that attempted moves are made only to elements that are compatible with the selected media, the test attempts to use bar code label and/or Read Element Status information from the library to determine media types by default. If bar code labels are missing or incorrect, it may be necessary for this option to be set to True to allow the test to run. This option should only be set to True if all of the media in the selected range is compatible with all of the elements in the selected range. If this

directory

format
Converting a support ticket to XML (CLF)
Description L&TT can be run from the command line to convert a support ticket to XML format. For more information about using reports and support tickets, see Reports and support tickets on page 131. The converted support ticket is the same as if it was originally created in XML format. hp_ltt -f xmlticket file=<ticket filename>[instname=<instance name>] [dirpath=<absolute path directory>] file Specify the path and name of the support ticket to be converted. The support ticket can have either a.lzt or.ltd file extension. L&TT will automatically extract the.ltd files out of the.lzt file, and create.xml files with the same names as the.ltd files. The detail level will be everything. Specify a name for this instance of L&TT. This parameter is optional for the first instance of L&TT and required for all other instances of L&TT. If this parameter is supplied, the log files from this instance will be created in a logs_<instance name> folder in the logs folder of the L&TT installation directory or directory specified by dirpath. Specify the absolute path for the temporary directory used by L&TT for its runtime files. This parameter is optional when L&TT is run from the system installation directory and required when L&TT is run from removable media, such as a USB flash drive or CD. When running L&TT from the system installation directory, if dirpath is specified and instname is not specified, the L&TT runtime files will be created in the dirpath directory. Otherwise, if dirpath is specified, the L&TT runtime files will be created in <dirpath>/logs_<instance name>.

Getting usage help (CLF)

Description L&TT can write a help file containing usage information for the command line functionality. When hp_ltt help is executed, L&TT creates the help file, ltt_usage.txt, in the L&TT installation directory. hp_ltt -help

Return values

When an operation is performed from the command line, L&TT returns a value indicating success or failure. Depending on the operation performed, the value returned has different meanings. When L&TT is run from a script, a return value greater than 0 indicates an error condition. Return values are as follows:

Enter Maximum emailsize 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. Check for updates on web This option is only available for Windows, Linux, and HP-UX. 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 version 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 furnctionality on page 168 Current password entered (CSI only) 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.
Using the Internet update functionality
The Windows, Linux, and HP-UX versions 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. In the CSI, go to the Main screen and type the command download to manually check for and download updates. NOTE: L&TT will only check for updates on the Web once in a 24-hour period.
Finding customer advisories and notifications
You can find a list of advisories and notifications for HP StorageWorks products by clicking the Help > Customer Advisories menu item. A link to the Customer Advisories/Notifications dialog is also available at the bottom of the device identity pages. If an advisory has been issued in the past three months for the device, the customer advisories button text will change to New Customer Advisories and the button will be highlighted.
Figure 50 Customer Advisories/Notifications dialog
The advisories for the selected Device Family are listed from most recent to oldest. Select an advisory to view and click Get Details from Web, which will open the advisory in a web browser. If this system is not connected to the Internet, use the Selected Item URL to access the advisory from another system.

HP StorageWorks Library and Tape Tools version 4.12 release notes
Part Number: 5697-0885 First edition: March 2011
Legal and notice information Copyright 2011 Hewlett-Packard Development Company, L.P.

Version:

Description
This release includes an updated version of HP StorageWorks Library and Tape Tools (L&TT). Update recommendation Supersedes Recommended. All earlier versions of L&TT.

Devices supported

Virtual libraries and D2D backup devices Same as L&TT 4.10. Tape libraries and autoloaders Same as L&TT 4.10. Tape drives Same as L&TT 4.10. Other backup devices Same as L&TT 4.10. See the QuickSpecs for a full list of supported devices.

Operating systems

Table 1 L&TT operating system support Operating system OS variant
Windows 7 (x86, x86_64) Windows Vista SP2 (x64, x86, x86_64) Windows 2008 R2 (x86, IA64, x86_64) Windows 2003 and Windows 2003 R2 (x86, x64, ia64) Editions Windows Windows 2000 Server SP4, Advanced Server, and Datacenter Server Windows XP (x86, x64, ia64) Editions Windows NT Windows ME Windows 98 Windows 95 HP-UX 11i v3 (PA-RISC,IPF) HP-UX HP-UX 11i v2 (PA-RISC,IPF) Current
Last supported version of L&TT
Current Current Current Current Current Current L&TT 4.2 L&TT 3.5 SR4a L&TT 3.5 SR4a L&TT 3.5 SR4a Current

Operating system

OS variant
HP-UX 11i (PA-RISC) HP-UX 11.0 (PA-RISC) RedHat EL 6.0 (x86, x86_64, IA64) RedHat EL 5.0 (x86, x86_64, IA64) (Updates 3, 4, and 5) RedHat EL 4.0 (x86, x86_64, IA64) (Updates 7 and 8) RH EL 3.0 (x86, x86_64, ia64) RedHat AS 2.1 (ia64) RedHat 9.0 RedHat 8.0 RedHat 7.3
Current L&TT 4.2 SR1 Current Current Current Current L&TT 4.2 Current L&TT 4.2 L&TT 4.2 L&TT 4.2 L&TT 4.2 L&TT 4.2 Current Current Current Current Not supported Current Current Current Current Current Current Current Current Current L&TT 4.2 SR1
RedHat 7.2 RedHat 7.1 RedHat 7.0 SuSE SLES 11 SP1 (x86, IA64, x86_64) SuSE SLES 11 (x86, IA64, x86_64) SuSE SLES 10 SP3 (x86, IA64, x86_64) SuSE SLES 9 (x86, x86_64) Fedora Linux Debian Linux OpenVMS 8.4 (Alpha/IPF) OpenVMS 8.3-1 (Alpha/IPF)
OpenVMS OpenVMS 8.2 (Alpha) OpenVMS 7.32 (Alpha) Solaris Sun Solaris 10.0 (x86, SPARC, AMD64) Mac 10.6 (x86) Standalone drives, L&TT CSI only Mac Mac 10.5 (x86) Standalone drives, L&TT CSI only Mac 10.4 (PPC, x86) Standalone drives, L&TT CSI only Netware Netware (5.1, 6.0, 6.5)

Tru64 5.x

L&TT 4.4

Languages

English

Enhancements and fixes

Virtual libraries (including D2D backup devices) No change. Tape drives Improved LTO drive assessment test is more accurate, a little faster, and requires only one tape. For more information, see the user guide. Improved polling detection in LTO tickets. Up to approximately 20 simultaneous polling hosts can now be detected. This would have overrun the previous algorithm. LTO ticket now shows real time in the history logs, such as the SCSI command history and event log, as long as the device driver (hplto.sys) or library has set the drive time. This feature requires specific drive firmware being released in the next few months. This applies to some LTO 4 and LTO 5 drives only. LTO device analysis output now shows the number of rules and sub-rules checked, along with textual categories of rule and sub-rule. LTO ticket SAS interface health section now shows error counts. LTO ticket FC interface health section now shows (decoded) warnings and alarms. Improved the LTO ticket decoding of ADI/AMI log and moved it to the report section (from the classic ticket section). Fixed a case where 8 Gb FC is reported as 4 Gb in LTO support ticket. Fixed errors in the LTO 5 support ticket SCSI command history catalog. Tape libraries and autoloaders EML/ESL-e Interface Manager support ticket now shows host mapping tables. Operating system specific Windows Additional backup applications are detected when L&TT starts. For more information, see the user guide. OpenVMS-specific features Added support to run L&TT on both ODS2 and ODS5 file systems. Added listtest function to show the tests supported by a specific device. Improved overall usability based on customer feedback. Mac-specific features Added support for the system performance test. Added support for MAC 10.6 (x86) Generic to tool

Additional backup applications are detected on start up along with messaging on shutting down their services before running LTT. Test options button is grayed out if there are no options. All supported tests for a specific device type can now be listed in CLF (command line) mode. CLF output is now displayed on the terminal window, except on Mac. Improved error reporting for CLF mode. CSI (non-Windows) interface has improved text output removed unnecessary wraparound. Issue fixed with scan of USB 3.0. Documentation User guide is now structured around the user mode: Windows, non-Windows, CLF. Added description of the updated LTO drive assessment test. Provided more examples for CLF mode.
Known issues and limitations
Virtual libraries and D2D
L&TT support for the most recent releases of D2D emulated drives is broken for all emulated LTO drive types, due to a change within the drive emulation behavior and therefore cannot be worked around with previous versions of L&TT. A fix is planned for L&TT 4.13. L&TT support is limited to what can be done with emulated devices. Please use the relevant Command View GUI for access to the support information for the physical device.

Tape libraries

When using L&TT on Linux, firmware downloads to an MSL2024 library may fail. If this happens, the firmware does get downloaded to the unit, but L&TT does not properly reflect the status of the unit when the download completes. In a library with mixed drive technologies, drive firmware cannot be downloaded from the library firmware download screen. Each drive must be selected individually for download. If a device is in a Not Ready state, L&TT may not be able to perform all diagnostic functions. Most devices are only very briefly in this state, but some libraries can take a significant amount of time after power on or after a firmware download before becoming ready. If this problem is encountered, wait until the device is in a ready state and then use L&TT.

Autoloaders

DAT72x6 After using the L&TT front panel and then closing L&TT, the autoloader is left locked. This is expected product behavior. The workaround is to eject the magazine to unlock. DDS2/3/4 autoloaders do not function in L&TT with the option switch value set to return the standalone drive ID. This option causes an unsupported product response. L&TT works with the switch in the default position. This is expected product behavior.

Tape drives

USB devices hot plugging a device (such as a USB memory stick) on the same USB bus as a tape drive can cause a bus reset and therefore any test in progress on that drive may abort or fail.
DLT 8000 Firmware upgrade appears to fail with some non-HP HBAs though it does upgrade correctly. Using firmware upgrade tape works also.
Operating system specific
Windows Device scan can fail intermittently with 'Unexpected Win32 error encountered during I/O scanning: 2' error message. Work-around is to re-scan. HP-UX Running the LTO Drive Assessment test on multiple drives concurrently can cause a core dump. The exact number is not known but is in the region of 8 or more. Linux in CLF (command line) mode LTO Drive Assessment test output scrolls off the screen at the end of the test. Test results can still be found in the ResultLog.ltt files. Mac Device performance tests are limited to approximately 220 MB/s. The Get files from web feature is not supported so L&TT cannot check for the availability of the latest firmware. OpenVMS The Get files from web feature is not supported so L&TT cannot check for the availability of the latest firmware. VMware L&TT does not run on VMware, even if it supported on the native OS. VMware only provides generic drivers which do not provide the functionality needed by L&TT.

Generic to tool

There is some inconsistency between the reporting of data capacity and volume between tests. Some tests report based on power of 10 whereas others report based on power of 2. L&TT is transitioning to power of 10 based reporting to match industry specifications. If L&TT is unable to automatically verify successful completion of a firmware update and is then re-selected from the previous scan, L&TT may exit with an exception. This is because the operating system has performed its own re-scan and logically moved the device after its update. In this case, perform an L&TT re-scan to locate the device. In these cases, the firmware update was usually successful.

Prerequisites

Windows Device drivers for the connected tape devices/libraries or default device driver should be present. HP-UX 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. 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. Linux Device should be recognized by proc/SCSI subsystem. Device drivers for the connected tape devices/libraries or default device driver should be present.

HP OpenVMS L&TT requires the following patches or higher to run successfully: V7.32 Alpha VMS732_FIBRE_SCSI-V0800 VMS732_UPDATE-V0500 VMS82A_FIBRE_SCSI-V0100 VMS82A_UPDATE-V0200 VMS821_FIBRE_SCSI-V0100 VMS821_UPDATE-V0200

V8.2 Alpha

V8.2 Itanium
Solaris The device should be shown in the cfgadm al and prtconf v command output. The device driver for connected tape drives and libraries or the default device driver should be present.
Installation instructions
Download L&TT from http://www.hp.com/support/tapetools

Windows

The Windows version of L&TT uses the InstallShield application. 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. Known issues When downloading the L&TT application from the Web to your local system, 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. To install the current Windows version of L&TT:
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. 3. 4. 5.

Double-click the self-extracting executable file to launch the installer. The InstallShield Wizard screen is displayed. Click Next. Read the program license agreement and click Yes if you agree to and accept the terms of the license agreement. Read the readme file for any last-minute changes to the documentation, then click Next. The Select Features screen is displayed. Select the desired components to install and click Next. In most cases, the default settings of this screen are adequate. 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 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. 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. 7. 8. 9.

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. 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. On the Ready to start installation process screen, click Next. If you need to review or change installation settings, click Back. When installation is complete, the InstallShield wizard displays its final screen. Select Start HP L&TT or Run LTT InstallCheck if you would like the wizard to start L&TT or the installation check. Click Finish to close the InstallShield wizard.

HP-UX and Linux

Uninstalling previous versions
Before installing L&TT on Linux, you must first uninstall any previous versions. To determine if L&TT is already installed, use the following command: rpm -qa | grep ltt To remove a previous version of L&TT, use the following command: rpm -e ltt
Installing the latest version
To install L&TT for HP-UX or Linux: 1. 2. Log in as root. 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 4. Un-tar the L&TT tar file: tar -xvf hp_ltt<xx>.tar 5. Run the install script in the /tmp directory:./install_hpltt NOTE: For Linux, the L&TT installer verifies that the operating system you are installing on is supported. If the Linux distribution or release is unsupported, the install script displays a message indicating an installation failure and lists the supported operating systems. 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

HP OpenVMS

To install L&TT on HP OpenVMS: 1. Download or copy the L&TT.zipexe file to a temporary directory.
Navigate to the directory you copied the install file to and enter the following commands: run hp-axpvms-ltt-v<xx>-1.zipexe (where <xx> is the version number) (alpha platforms) product install ltt The installation procedure creates the directory structure opt.ltt in sys$sysdevice:[vms$common] and installs all the required files for L&TT.

Solaris

To install the L&TT package: 1. 2. Login as root. Navigate to the temporary directory: cd /tmp 3. Download or copy hp_ltt<xx>.tar (where <xx> is the version number) to this directory. If you are copying the file from a different directory, enter the following command, substituting the directory in which the file currently resides for <directory name>: cp /<directory name>/hp_ltt<xx>.tar /tmp 4. Un-tar the L&TT tar file: tar xvf hp_ltt<xx>.tar 5. Run the installation script in the /tmp directory:./install_hpltt 6. After the software is successfully installed, enter the following commands to remove the temporary files from the installation process: cd /tmp rm rf install_hpltt rm rf HPLTT<xx> (where <xx> is the version number)

1. 2. 3. 4. 5. 6. Log in to the Mac GUI using root or full system privileges. Download or copy the install file to a temporary location. The install file is hpltt_<xx>_mac.dmg (where <xx> is the version number). Double-click the downloaded file. This action will mount the image. Double-click the hp_ltt<xx>.mpkg icon. Follow the screen instructions. On completion, click the finish button.

Effective date

March 2011