HP Library and Tape Tools User Guide Product version: 4.16 Abstract HP 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.
© Copyright 2002, 2013 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.
Contents 1 Introduction...............................................................................................9 Software features......................................................................................................................9 What's new...........................................................................................................................10 What's new in L&TT 4.16................................................................................................
Report and support ticket compression.............................................................................46 Viewing a report or support ticket........................................................................................46 Setting the detail level....................................................................................................46 Other functionality.........................................................................................................
Generating an XML support ticket........................................................................................80 Generating an event log.....................................................................................................81 Viewing an event log..........................................................................................................81 4 Accessing HP library LTO-5 and LTO-6 drives over Ethernet............................
MO Media Validation test.................................................................................................127 Move test........................................................................................................................127 Read/Write Stress test......................................................................................................128 Read/Write test...............................................................................................................
Running the device independent utilities...................................................................................169 System Config utility.........................................................................................................171 Running plugins....................................................................................................................171 Using the quiet mode feature............................................................................................
Why doesn't L&TT for HP-UX see all the devices connected to a SAN environment?...................190 Why am I unable to download firmware/script files using the download option in the CSI (HP-UX, Linux)?............................................................................................................................191 Why doesn't L&TT for Tru64 see some of my devices?...........................................................191 Why doesn't L&TT for Linux see some of my devices?..................
1 Introduction HP Library and Tape Tools (L&TT) is a collection of storage hardware management and diagnostic tools for HP tape mechanisms, tape automation, magneto-optical and archival products. L&TT assembles these tools into a single, convenient program. IMPORTANT: This user guide is intended for L&TT version 4.5 and later. Certain features from previous versions of L&TT are no longer supported with this version and are therefore not documented here.
What's new New features and enhancements in L&TT: • “What's new in L&TT 4.16” (page 10) • “What's new in L&TT 4.15” (page 11) • “What's new in L&TT 4.14” (page 12) • “What's new in L&TT 4.13” (page 13) • “What's new in L&TT 4.12” (page 14) Known issues and limitations in the current release: • “Known issues and limitations in L&TT 4.16” (page 16) What's new in L&TT 4.16 L&TT 4.
• ◦ Red Hat Enterprise Linux 6.4 support added. ◦ SuSE 11 SP3 support added. Generic to tool ◦ Ethernet access is now available for LTO-6 drives. ◦ The Ethernet IP address can now be entered manually for library drives. ◦ Included more “Factory” level content in the “Everything” level. What's new in L&TT 4.15 L&TT 4.15 is an incremental release, which incorporated enhancements and fixes from L&TT 4.14 SR1 and L&TT 4.14 SR2, and targets: • LTO-6 support.
◦ Added the LTO Data Assessment Test, which is aimed at checking the quality of the data on tape. (L&TT 4.14 SR2) ◦ LTO support ticket device analysis rules now lists all the polling hosts it can detect rather than just the first one. (L&TT 4.14 SR1) ◦ LTO support ticket and Drive Assessment Test now includes off-track margin assessment. (L&TT 4.14 SR1) ◦ Stronger messaging to update LTO firmware to encourage adoption of significant reliability improvements to the drive. (L&TT 4.
• ◦ Drive type (generation) is now shown in the front panel window making it easier to select the correct drive for the media being moved. Media type is already shown. ◦ Debug tickets from the ESL G3 libraries are made more obvious that their content is reduced. Tape drives ◦ Increased sensitivity to the performance of the LTO read channel allows for more accurate assessment of drive and tape read health. This is reflected in the read margin output (the actual values are factory-only view).
• Virtual libraries (including D2D backup devices): no change • Tape drives • • ◦ The LTO drive assessment test now checks the firmware version as new firmware is available to improve the performance of marginal drives. ◦ The support ticket highlights when an LTO drive assessment test has failed in the past seven days. ◦ The support ticket shows whether barcode labels are correct for the cartridge type. Messages indicate cartridges without barcode labels that were loaded anyway.
• ◦ 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.
• ◦ 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 in L&TT 4.
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 causes an ‘unsupport product' response. L&TT works fine with the switch in default position. This is expected product behavior.
Finding additional information The HP website provides the current version of L&TT for download, and general information about the tool. Access the website at: http://www.hp.
2 Installing and using L&TT on Windows Installing L&TT 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.
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.
Using the graphical user interface Starting L&TT To start L&TT, log on as administrator and do one of the following: • Double-click the L&TT icon on the desktop (if present). • Click Start > Programs > HP Library and Tape Tools > HP L&TT. Using the Scan Mode selection feature When L&TT starts, the Startup screen opens. The Startup screen gives you the opportunity to exit the application if it was started unintentionally and before any SCSI bus activity occurs.
The Startup screen 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).
Figure 2 Saved/Manual Scan screen Additional device scan considerations After the initial scan is complete and saved, future full system hardware scans become unnecessary in most cases.
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 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.
• Data Protector Express • HP Data Protector Figure 3 List of backup applications and services Application window layout After the I/O mode is selected, click Continue on the Startup screen. The L&TT main screen opens. Figure 4 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.
NOTE: Above the Taskbar is the standard Windows menu bar that provides alternate navigation to tool functions, as well as access to other features. 2. Device list — This is a multi-function window that offers several options on the following tabs: • Scan — 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.
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, as shown in Figure 5 (page 27). Figure 5 Device information screen 1. A visual representation of the selected product (the images are in grayscale). 2.
Figure 6 Compatible data cartridges screen 5. TapeAssure service status for the selected drive. TapeAssure is supported for LTO-3 and later generation LTO tape drives. 6. Click this button to find any customer advisories for the product. When a recent advisory is available, the button will have blue highlights, as shown in Figure 5 (page 27). For reliable operation, HP recommends that users read product advisories when they are available.
Figure 7 Device information screen showing a library 1. 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, bar code number (if bar code reading is available), and media type are displayed here.
Figure 8 Firmware Management screen For detailed information about the firmware management functionality of L&TT, see (page 34). Using the Test 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 Tests on the main toolbar.
Figure 9 Test 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 (page 99). Using the Utility screen L&TT provides several basic utilities that can be used to perform functions on a storage device or media in the device. To access the utilities screen, click the device you want to test in the device list, then click Utility on the main toolbar.
Figure 10 Utilities screen For detailed information about the utilities screen, as well as information about how to run the utilities, see Tests and utility functions (page 99). 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.
Figure 11 Support Ticket generation screen For detailed information about generating and using support tickets, see Reports and support tickets (page 148). For specific information about the various options found on the support screen, see Using the Support screen (page 44). Accessing troubleshooting help The Troubleshoot button on the L&TT toolbar links to guided troubleshooting help on the HP StorageWorks website. The Troubleshoot button is enabled in all screens, even when a device is not selected.
Many of the utility functions are device-specific and intended only to remedy specific problems that may occur with a particular device. The SCSI utility scripts (files with a .scc extension) are stored in the scripts directory. CAUTION: Using a script improperly or when it is not required can cause harm—possibly rendering a device inoperable.
To access firmware revision and release note information from the L&TT application (HP-UX and Linux): NOTE: 1. 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. 2. 3. In the Download Tool area, enter 5 at the command prompt.
1. 2. 3. 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.
Figure 14 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.
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 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).
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 Start Update at the bottom of the screen to begin the update. CAUTION: Make sure that no other programs attempt to access the device while the firmware is being updated.
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.
Figure 17 Test/Utility results To email the results to a support provider, click Email Results. Fill in the information fields in the Email Test Results dialog and click Send.
Figure 18 Email Test Results dialog Aborting a test Selected L&TT tests can be stopped before they complete. Check the test description to see whether the test can be aborted. NOTE: 42 Some tests can take several minutes to stop after they are aborted.
For tests that can be aborted, the Start Test button changes to Abort Test. Figure 19 Abort Test button After the Abort Test button is clicked, L&TT will attempt to abort the test, which can take 10 – 20 seconds or more. Once the abort button has been clicked, the button is greyed out and cannot be clicked again.
supported by L&TT. For more information on reports and support tickets, see Reports and support tickets (page 148) The use of reports and support tickets is essentially the same. The main difference is that reports have an enhanced format that presents 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.
Figure 20 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.
Report and support ticket compression When you save or e-mail a support ticket, L&TT generates a single, compressed support ticket file. The support ticket includes the master support ticket file, sticket_header
Figure 21 Example report Other functionality Right-click any line in the support ticket viewer to display a context menu that exposes additional functionality. Depending on the line that was clicked, the following items may or not be available (unavailable items are greyed out): • Expand All—Expands all subitems. • Event Explanation—Opens the Event window that displays additional information about the event. You can view the data in either ASCII or hexadecimal format.
• Reference Data—Opens the Reference Data window that displays reference information pertinent to the current line such as valid ranges and applicable values. • Find Sub-Tree—Search for a particular sub-tree. • Copy Sub-Tree—Copies the current sub-tree to the Windows clipboard.
• Double-click Data. L&TT generates an HTML version of the support ticket in the same directory as the support ticket file and attempts to display the ticket using Internet Explorer. If Internet Explorer is not displayed on the system, a Windows error message is displayed. NOTE: If you are using Internet Explorer, depending on security settings, you may see a message stating that Internet Explorer has blocked ActiveX content.
Saving a report or support ticket When you save a support ticket, L&TT generates a single, tarred, zipped support ticket with the .lzt file type in the logs directory. The support ticket is named st__
NOTE: For legacy 3.x large libraries, including SureStore 2/20, SureStore 4/40, SureStore 6/60, SureStore 6/140, SureStore 10/100, SureStore 1/9, and the MSL5000 and MSL6000 series libraries, the tarred support ticket contains a single compressed .dat file. To view the saved support ticket, open the .lzt file using Windows Explorer, or use the Load command on the L&TT File menu. TIP: To view or e-mail the individual files, rename the .lzt file so it has a .
Figure 24 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.
1. 2. In Step 1, indicate whether this is a new support request or an existing case. • If this is a new support request, select Send to support provider to request support by e-mail. Enter the product number and product serial number in the appropriate fields. • If this is an ongoing support case, select Send to support provider in reference to an open case and enter the case reference number in the appropriate field. In Step 2, enter the destination e-mail address.
Figure 25 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).
production quality. A working drive will have positive margin, whereas negative margin indicates an issue. The percentages are also mapped to simple wording as follows: < 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.
• 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.
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.
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. Loading or opening support tickets L&TT versions 4.2 and later support opening the following support ticket file types: • .lzt — tarred support ticket • .
Figure 26 Save as XML file menu item 4. Enter the file name. By default, L&TT saves the support ticket in the logs folder with the name SupportTicket.xml. To generate an XML support ticket from a saved support, open the saved ticket in the Report Viewer and follow the directions above to generate the XML support ticket.
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.
3 Installing and using L&TT on non-Windows systems Installation Installing L&TT for NetWare NetWare installation prerequisites 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 the NWPA subsystem. • Device drivers for the connected tape devices/libraries or default device driver should be present.
Software dependencies/prerequisites • Known issues 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.
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.tar (where 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 ): cp //hp_ltt.
To remove a previous version of L&TT, use the following command: $ product remove ltt Installation procedure NOTE: L&TT is supported from OpenVMS v7.3-2 onwards and is supported on both ODS-3 and ODS-5 file systems. 1. 2. 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 to install L&TT: $ run hp-axpvms-ltt-v-1.
6.
• For Novell NetWare From the server console, execute the following command: hp_ltt\hp_ltt • For HP OpenVMS: Log on as system or an ALL privileged user and execute the command @LTT$ROOT:[000000]start_ltt.com • For Mac OS: Bring up the terminal. Change the working directory to /usr/local/HP/LTT and initialize L&TT by running the command ./hp_ltt. Alternatively running the command hp_ltt would also initialize L&TT from any working directory.
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. Using the Scan Mode Selection screen When the CSI version of L&TT is started, the Scan Mode Selection screen opens.
Figure 29 Saved/Manual Scan screen To have L&TT rescan the system for new hardware devices, use the rescan command. Using the Saved/Manual Scan screen Use the Saved/Manual Scan screen to 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.
Using the device information screen When you first select a product from the Main screen, the device information screen opens, 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.
Library and autoloader products Figure 32 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.
Accessing details for local firmware files To view firmware details, use the localfrmlist command, which will list the firmware files in the local firmware directory. Figure 33 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 33 (page 71).
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.
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.
Figure 34 Test selector screen • To select a test, enter the number associated with the test. The Test screen opens. • To select a different device, enter the up command. The drive information screen opens. NOTE: On Mac, to go to the previous screen, enter the back command instead of the up command. 3. 74 The Test screen displays the currently selected test with a description, and lists the available devices to be tested.
Figure 35 Information screen for the currently selected test 4. 5. • To select a different device, enter the corresponding device number to toggle the selected status of the device. To deselect all devices, enter the clear command. • To select a different test, enter the up 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.
Aborting a test 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 36 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.
Figure 37 Command line when L&TT is aborting a test Using the SCSI script utilities L&TT includes SCSI utility scripts, which can be accessed from the Utilities > Run Script menu. 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. The SCSI utility scripts (files with a .
Using 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.
Support ticket compression When you save or e-mail a support ticket, L&TT generates a single, compressed support ticket file. The support ticket includes the master support ticket file, sticket_header
To load a support ticket from the CSI: • In the main screen, enter load . Support tickets generated in Command View for MSL Libraries (CV-MSL) do not contain device analysis data. When L&TT opens a support ticket generated in CV-MSL, it runs the device analysis and displays the results. When L&TT opens a support ticket generated in an older version of L&TT, L&TT 4.
Generating an 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. To generate an event log: 1. From the Main screen, enter preferences. 2. Enter 4 at the command prompt, and select the check box. 3.
4 Accessing HP library LTO-5 and LTO-6 drives over Ethernet HP LTO-5 and LTO-6 library tape drives support drive diagnostics via the Ethernet interface using the Internet Diagnostics Tool Interface (iDTI) protocol. L&TT 4.14 and newer releases now support this feature with the Ethernet mode. With Ethernet mode, you can perform most diagnostics from a laptop (with L&TT installed) that is connected to the drive or library with an Ethernet cable.
Figure 39 Ethernet ports on switch in the ESL-e and EML-e libraries For the ESL G3 library, connect to the service port, as shown in Figure 40 (page 84).
Figure 40 ESL G3 service port 84 Accessing HP library LTO-5 and LTO-6 drives over Ethernet
Connecting to the Ethernet port 85
For the 1/8 G2 Tape Autoloader and MSL2024, MSL4048, MSL6480, MSL8048, and MSL8096 tape libraries, connect to the Ethernet port on the tape drive, as shown in Figure 41 (page 86). Figure 41 Ethernet port on LTO-5 tape drive in the 1/8 G2 Tape Autoloader and MSL libraries NOTE: The 1/8 G2 Tape Autoloader and MSL libraries also have an Ethernet port, which is used for the remote management interface. L&TT does not use this port, L&TT uses the port on the tape drive.
5 Command line functionality Overview Certain key functions of L&TT are available through the command line, allowing you to sequence operations using scripts. Command line functionality (CLF) is different from the command line user interface (CSI version) in that it has no user interface, and therefore no user interaction.
Running L&TT commands from removable media You can run L&TT commands from removable media, such as a USB flash drive or CD. See Running L&TT from computers without L&TT installed (page 178) for instructions to install L&TT on the removable media. Use the dirpath option in the commands to specify a directory for the L&TT runtime files. Command line functions This section lists the basic functions that can be performed using the CLF.
Running tests (CLF) Performing a firmware update Generating a report or support ticket Converting a support ticket to XML Configuring L&TT (CLF) Description You can set the L&TT password and configure I/O history and I/O mode settings from the command line. Any one parameter or a combination of parameters can be entered. This information is device independent.
This file is overwritten each time a scan is performed. The output is written in the following format: ::: The device path varies depending on the operating system. The device path is specified with the p= parameter when running a ticket, test, or firmware upload. The password and iohistory parameters are optional. I/O mode cannot be set while doing the scan; it must be set before performing the scan.
Example hp_ltt -f listtest p=2.3.0[2-4/0/4/1/0.3.0] Results in the following: Running tests (CLF) Description L&TT can be launched from the command line to perform various tests. L&TT runs the test specified by the testname parameter on the device specified by the device path (p) parameter. These two parameters are required; all other parameters are optional.
the saved_scan.txt file in the L&TT root directory. Examine this file to determine the proper format. This parameter is required. testname Enter the test name to perform.
Examples To run the Connectivity Test on a drive at device path 2/0.4.0 on Windows: hp_ltt -f test p=2/0.4.0 testname="Connectivity Test" To run the previous test with I/O history enabled: hp_ltt -f test p=2/0.4.0 testname="Connectivity Test" iohistory=enable To run the previous test with a test option that causes the test to be run three times: hp_ltt -f test p=2/0.4.0 testname="Connectivity Test" testopt=”Looping Value:3” To run the LTO Drive Assessment Test on a drive at path 2/0.4.
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 /logs_.
to enable firmware downgrades. For more information, see Advanced options (CSI) (page 72). overrideproductid Optional. Specify yes or no. The default value is no. When set to yes, this option allows mapping of the device firmware to a product irrespective of the device's product ID. You must also enter a valid factory password using the password parameter to enable firmware downgrades. For more information, see Advanced options (CSI) (page 72). instname Specify a name for this instance of L&TT.
This parameter is optional. If no format is specified, the L&TT format support ticket will be generated. instname 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_ folder in the logs folder of the L&TT installation directory or directory specified by dirpath.
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 /logs_. filename Examples Specify the name of the XML file that is created after conversion.
2 Firmware file corrupt or missing 3 Product ID mismatch, config code mismatch, permission mismatch 4 Update finished with check condition 5 Update complete; manual intervention required 6 Generic firmware update failure Report/support ticket 0 Success 1 Abnormal exit/operation failure 2 Invalid target directory; unable to create directory 3 Ticket generation failure (data acquisition/parse/decode problem) 4 File permission issue; unable to write to file Using the trace file When an oper
6 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.
NOTE: L&TT tests are constantly 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. Test script updates are 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 from www.hp.com/support/TapeTools.
DLT, DLT1, VS80, VS160, and SDLT Assessment tests performed: • SCSI interconnect test • Review event log entries (that 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 Assessmen
• 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.
• 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 pop-up 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.
In L&TT 4.12 the LTO drive assessment test was improved to be more accurate and consistent while also making a pass/fail decision with a single tape. This section describes the operation of the test so you can understand how it works and gain confidence in its assessment of the drive. The test contains four main sections: • Analyze the drive logs. The test pulls over 60 logs from the drives and analyzes them with about 20 rules and 130 sub-rules.
Figure 44 Multiple tests for each tape speed The error rate tests for each direction cover different parts of the tape and are run at different speeds, as shown in (page 105). This allows the test to characterize the drive for each direction, testing each set of heads. Figure 45 Multiple tests run in each direction The pass/fail criteria are the same as for the support ticket — the drive must be able to write high quality data using no more than 20% additional tape to do so.
tape) ||_ Channel variation: 0.0% Channel variation margin: 100.0% ||_ Offtrack count: 0 CCQ rewrite percent: 0.1% ||_ 3.8 m/sec. tape speed:Effective capacity:94.6% Margin: 98.5% (3.0/3.0 GB written using 128.1 meters tape) ||_ Channel variation: 0.0% Channel variation margin: 100.0% ||_ Offtrack count: 0 CCQ rewrite percent: 0.1% ||_ 4.2 m/sec. tape speed:Effective capacity:94.6% Margin: 98.4% (3.0/3.0 GB written using 128.1 meters tape) ||_ Channel variation: 0.0% Channel variation margin: 100.
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) (page 40) or Running the tests (CSI) (page 73). Command line syntax The Connectivity test is available from the command line. For more information, see Running tests (CLF) (page 91).
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 DAT320 Encryption test Description This test checks that the encryption capabilities of the DAT320 drive are working correctly.
Command line syntax The Device Analysis test is available from the command line. For more information, see Running tests (CLF) (page 91). Test name: Device Analysis Options: None 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.
DDS Cooling Test Description This test monitors the temperature sensors of a DAT320 drive while writing data for approximately 30 minutes, 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) (page 40) or Running the tests (CSI) (page 73) When to run Run this test if you suspect thermal problems with your DAT 320 drive. Other notes This test can be stopped before it completes.
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.
DLT SRAM Check test (short and long versions) CAUTION: product. These tests are destructive and will overwrite data on the media that is present in your 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.
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) (page 40) or Running the tests (CSI) (page 73). 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.
Description 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 (page 114). NOTE: For instructions on how to perform this test, see Running the tests (GUI) (page 40) or Running the tests (CSI) (page 73).
(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).
• • Barcode Mode— Specify how bar codes are handled.
these will be come the test tapes for that test run. There is one tape per drive type. For example if the library has multiple LTO2 tape drives and multiple LTO4 tape drives, the test will use two test tapes — one for the LTO2 tape drives and one for the LTO4 tape drives. In this example, the empty test slot will be the first empty slot found starting with slot 10.
Library Read Write test Description The Library Read Write test automates the testing of the drives and tapes in a tape library. This test assumes that the library robotics are working properly. To test the library robotics, use the Library Exercisor test (page 113) or the Move test (page 127). NOTE: For instructions on how to perform this test, see Running the tests (GUI) (page 40) or Running the tests (CSI) (page 73).
Options • Allow overwrite (default: FALSE) — Set to TRUE to enable test options which write to the tape. Specifically, if MB to write is greater than 0 or Run LTO drive assessment test is TRUE, the test will only run if Allow overwrite is also true. • Starting slot (defaults to 1) — Specifies the number of the slot where the test will start checking for compatible tapes. NOTE: Slot and drive numbering is one-based (the first slot is 1), which is consistent with L&TT.
◦ the test tape will be written during the assessment test. The choices are Default and Entire tape. NOTE: If Run LTO drive assessment test is TRUE and Drive type is not LTO, the test will exit. • Continue on drive errors (default: TRUE) — Specifies whether the test should continue when an unexpected drive error occurs. This check does not include some expected drive errors, such as when a drive reaches EOD before reading the specified amount of data.
labels, and keep correct inventory. The test will fail immediately upon the first robotics error. • No tapes in the selected drives. If there are tapes in any of the selected drives, the test will move the tapes back to their source slots at the beginning of the test. A working library should know the source slots for each tape, as long as the library has not been rebooted or power-cycled since the tape was loaded into the drive.
TIP: To keep log information about a tape that has been discarded from the library, copy or rename the log file before running the Library Read Write test. The test determines which tapes to use based on the test option settings for Starting slot, Number of test tapes, Drive type, Ignore barcode labels, and whether or not the tapes will be written (see Allow overwrite).
Options • Test time in minutes — The default is to read all the data on the tape. If the tape is fully written, this parameter can be set to read for only a set number of minutes. • Allow Suspect Drive — The default is that the test will exit as incomplete if the drive has not passed the LTO Drive Assessment test with greater than 95% margin within the last 30 power-on days.
NOTE: For instructions on how to perform this test, see Running the tests (GUI) (page 40), Running the tests (CSI) (page 73), or Running tests (CLF) (page 91). Options HP recommends using the default options, which will perform a Read Only (Backup Assessment) test and attempt to read two wraps of data from the tape. Use the Allow Overwrite and Amount of Media to Test options to modify the default behavior of the test.
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) (page 40) or Running the tests (CSI) (page 73). When to run Run this test only if you suspect that the cartridge is stuck.
Options • 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.
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) (page 40) or Running the tests (CSI) (page 73).
Options • Loop count — Specify the number of times the test sequence should be repeated. Each test sequence consists of two moves — one from the specified source to the specified destination followed by a second move back to the original source location. • Source address type — Specify one of the following source element address types: ◦ Storage slot — The source address is a storage slot number (starting at 1). ◦ Drive — The source address is a drive number (starting at 1).
Read/Write test CAUTION: product. Description This test is destructive and will overwrite data on the media that is present in your 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.
Options • 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.
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) (page 40) or Running the tests (CSI) (page 73). When to run Device Analysis test results will recommend running this test if abnormal (not default) settings are detected.
Other notes • This test assumes ◦ The SDLT tapes have the proper bar code labels with S as the 7th character ◦ The SDLT drives have the latest firmware ◦ The library is configured to show all bar code labels Otherwise, the tapes may not be recognized with this test. Available for • 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.
1. 2. In the device listing (the By Product or By Connection tab), select the library or drive to test. Click Dev Perf on the main toolbar. The Drive Performance screen opens with the Tape Drive Performance tab selected. For libraries, the Drive Performance Test tab shows the library and its associated drives. For a stand alone drive, only a single drive will be shown. Figure 46 Drive Performance screen 3. Select the tape drives for the Drive Performance test.
5. 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 menu. ◦ Variable— The test uses a different mode of data transfer. When this option is selected, the Block Size menu is disabled. • Block Size—If Block Mode is set to Fixed, specify the size of the data blocks used in the test.
Figure 47 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.
Figure 48 Device Performance Tool screen 3. 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.
4. 5. 6. 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.
Figure 50 Restore Performance Test tab of the System Performance screen 3. Specify the following parameters: • Test Path— Enter the destination directory to which the test will write data. 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.
• 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).
Figure 51 Backup Performance 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.
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). • Measure Reader 1 compression ratio — When this box is checked, the compression ratio of the files selected by Reader 1 is measured.
The two options available for the Backup Performance 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. Figure 53 Restore Performance Test screen (CSI) The following options are available for the Restore Performance Test: 4. 142 • Filesize—Specify the size, in bytes, of the test files to be created.
Device-specific utility descriptions L&TT provides three types of utilities: • Device-specific utilities are accessed from the Utility screen and operated like the tests. This section describes the device-specific utilities. See Running the tests (GUI) (page 40) for information on running the device-specific utilities. • Device connection independent utilities are accessed from the Utilities→Run Utilities menu.
Available for This utility is available for MSL2024, MSL4048, MSL8048, MSL8096, ESL E-Series, and the 1/8 G2 Tape Autoloader. NOTE: EML support for the Compare Statistics utility was removed in L&TT 4.5. DAT autoloader firmware tape creator Description Lets you create a firmware update (FUP) tape for your DAT72x10 autoloader, using the DAT72x10 to create the tape. A FUP tape is a tape that is created when a firmware file for a particular drive type is written onto a blank tape.
Firmware Tape Creator (FUP tape) utility 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 utility, see Running the tests (GUI) (page 40) or Running the tests (CSI) (page 73). When to run Run this utility when you want to create a firmware update (FUP) tape to update drive firmware.
After the running the utility, power cycle the drive and then use L&TT to rescan for devices. Available for LTO drives only LTO Firmware to Data Tape Creator CAUTION: product. This utility is destructive and will overwrite data on the media that is present in your Description This utility converts a previously created firmware upgrade tape back to a normal data tape on your Ultrium drive.
When to run Run this utility when you want to erase a tape that has been written previously. 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. The test will not run with a tape that has been partitioned.
7 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.
is set to the desired level before generating the HTML report because the detail level within the HTML file cannot be changed. • 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.
• The system information – if the ticket was pulled using L&TT, but not if generated from Command View TL. • The library • The drives The decode is arranged hierarchically in the above order and is easy to navigate. To reduce the load time for large library tickets, the sub-ticket data is not pulled in from the ticket file until the device is clicked in the viewer. When pulling tickets from a library, select the library first and then pull the ticket.
Figure 54 Support ticket System Configuration section When troubleshooting, check for: • Tool version — the version of L&TT that the ticket was pulled with. The raw data doesn’t change much over time but HP recommends using the latest version of L&TT for both pulling and viewing tickets. • Active services, such as Windows RSM or the Insight Management agents.
In most cases additional categories between Drive and Interface cleanly separate drive issues from interface issues, which can have similar symptoms and make it difficult to find the cause of a symptom. L&TT assesses the values reported by the drive and expresses them, when appropriate, as margin: • Great – The value is about as good as it can be. No action need be taken. • Good – The value is not as good as represented by ‘great’ but still has sufficient margin. No action need be taken.
Figure 56 Support ticket Drive health section • Device Analysis - These are the ‘rules’ which are run against the drive logs and highlight any concerns and recommend actions. L&TT typically tests over 20 rules and 130 subrules, covering everything from firmware version to read/write health to host polling. Some notes and errors are not currently covered in the rules so also check the notes and errors elsewhere in the ticket.
• Any output from the device analysis rules. This should be the first place to look. • Any highlighted items. Drive configuration The Drive Configuration section shows how the drive was configured at the time the ticket was pulled, along with the interface configuration, depending on the interface type. Figure 57 Support ticket Drive Configuration section When troubleshooting, check for: • Media removal - if prevented, it will not be possible to eject a tape, which could appear to be a ‘stuck tape’.
• The margin assessment, rather than the reported temperature • Over temperature (or under) will be highlighted Drive performance The Drive Performance section shows performance-related measurements for the drive base on the current and up to four previous tapes. Figure 59 Support ticket Drive Performance section • Estimated native data rate – this is the rate after compression and so should be compared with the native data rate of the drive (which is shown in this section) rather than the host rate.
Figure 60 Support ticket Drive Usage section • Tape Pulled – expressed in full volume equivalents (FVEs), which is the equivalent of writing to or reading from a full tape once. A full volume write followed by a read will give two full volume equivalents. • Duty cycle – the average duty cycle over the life of the drive. This value cannot be reset. For more dynamic duty cycle reporting please use TapeAssure. • Native data volume – this is the amount of data after compression read or written to tape.
Cartridge identity The Cartridge Identity section shows information specific to the last cartridge loaded – either currently loaded or ejected. Figure 62 Support ticket Cartridge Identity section Cartridge health The Cartridge Health section shows the health of the current or last loaded tape. Figure 63 Support ticket Cartridge Health section • Data on tape – covers how much extra tape was used to write high quality data to tape.
Figure 64 Support ticket Cartridge Configuration section When troubleshooting, check for: • Write protected. Not an issue if set, but may cause backups to fail. • (EOD) Validity – can also show backup in progress, if the ticket was pulled during a backup (or the cartridge memory didn’t update correctly). This will be highlighted if not set to valid. Cartridge environment The Cartridge Environment section shows the temperature margins for the tape for the recent drives it was loaded in.
Figure 67 Support ticket Cartridge Usage section Cartridge history The Cartridge History section shows anything specific for this tape that was identified from the history logs of the drive. The section is still in development and not fully populated. Classic support ticket The Classic Support Ticket section is the original, basic decode of the support ticket before the above categories were introduced.
8 Additional functionality This chapter describes additional features of the program that are not covered elsewhere in this guide.
Figure 68 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.
Figure 69 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.
24 hours. This functionality is only available if you have an Internet connection. For more information, see Using the Internet update furnctionality (page 163) later in this chapter. • Display dialogs for I/Os pending more than 2 minutes (Windows only) — When this option is enabled, L&TT displays a status update dialog box during long SCSI operations. • Check for redundant devices after scan—Checks for redundant devices in the current configuration. This option is enabled by default.
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 Storage 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.
Figure 70 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.
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.
Figure 71 Front panel 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.
Figure 72 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.
1. 2. 3. 4. 5. 6. 7. 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). Slot to slot is not supported with this device (you must move slot to drive or drive to slot). 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.
1. Select Run Utilities from the Utilities menu to display the Run Utilities dialog. Figure 73 Run Utilities dialog 2. 3. Select the utility from the Utility drop-down list. Click the Options button to set any utility options. The device independent utilities do not require a tape device to be connected to the system running L&TT. To run a device connection independent utility from the command line interface: 1. On the main screen, enter the command utils. 2.
System Config utility The System Config utility checks the local host configuration. The System Config utility extracts the local host configuration and checks the configuration for any known issues that could keep L&TT from interacting with the device and/or prevent the backup applications from working properly. NOTE: The System Config utility is only supported in Windows, HP-UX 11.11, and HP-UX 11.23. On Windows, the utility checks: • The state of the Removable Storage Manager (RSM) service.
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.
Figure 75 Installation Check wizard 2. 3. 4. Select the device on which to run the installation check and click Start Verification to display the next screen of the Installation Check wizard. Select any optional tests that you want L&TT to perform. Some tests may not be available for your configuration. Click Continue Verification to begin the installation check. The third screen of the Installation Check wizard indicates the progress of the installation check.
Figure 76 Installation Check wizard results 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. Managing the TapeAssure service The TapeAssure service can be managed from L&TT versions 4.11 and later. The TapeAssure service management functionality is available from the TapeAssure menu.
◦ Management IP/URL and port ◦ List of monitored drives • Start service — Click to start the TapeAssure service • Stop service — Click to stop the TapeAssure service • Configuration — Opens the TapeAssure configuration file for viewing and editing • Pending Ticket Storage — Provides access to the tickets pending transmission to the Command View TL management station. The tickets are viewed with the L&TT viewer and are stored in the TktStorage folder.
Figure 78 Tool Status Report screen (GUI) 2. 3. Follow the steps outlined on the Tool Status Report screen. Click one of the following buttons: • Send as E-Mail—Click this button to send the TSR in an e-mail. Use the default address (ltt.team@hp.com) to send the TSR to the L&TT support team, or change the e-mail address 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.
Figure 79 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 e-mail address (ltt.team@hp.com is the default) and sends the TSR to the specified e-mail address. • up—Exits the current command level. • exit—Exits L&TT.
9 Advanced installation topics This chapter contains the following sections: • Other changes to the system (GUI) • Reboot criteria • Running L&TT from computers without L&TT installed • 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 i
1. 2. 3. 4. (Linux) Fully install L&TT onto a computer. If desired, also install any necessary firmware files into the firmware subdirectory. Remove the logs directory from the L&TT install directory. Write the contents of the L&TT install directory (/opt/ltt) to the root directory of a CD or USB flash drive. Close the CD. Insert the CD or USB flash drive into any Linux system and mount the CD or USB flash drive. From the mount path run hp_ltt as you would on any other Linux system.
1. Navigate to the L&TT installation directory on the remote computer. Figure 82 HP L&TT installation directory on a remote computer 2. Execute HP_LTT.exe 1. 2. 3. (Linux) To run L&TT from a remote directory: Verify that the Linux version on the remote computer is compatible with the installed binary. Start the NFS service on both computers. On the machine where L&TT is installed edit the /etc/exports file: Add the line /opt/ltt *(rw,sync,no_root_squash) 4. 5. Restart the NFS service.
• 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 (page 99).
10 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 TIP: Find the latest version of the frequently asked questions, including translated versions, at www.hp.com/support/lttfaq.
To access the One Stop Compatibility chart for tape and optical media, see http://www.hp.com/ go/storagemedia.
How do I use L&TT to find my drive serial number? • With the Windows version, select the device and click Identity on the toolbar. The device information screen displays the serial number. • With the CSI version, from the Main screen, enter select , where n is the number of the device. The device information screen displays the serial number.
Is my non-LTO tape OK? To check a non-LTO tape, use the Media Validation test. See Media Validation test (page 126) or MO Media Validation test (page 127). Was my backup successful (LTO only)? To determine whether a backup to LTO tape was successful: 1. Perform the backup as you normally would. 2. Generate a support ticket for the drive to which the backup was performed. 3. Locate the Loaded Tape > Cartridge Health section of the support ticket and examine the margins.
2. Run the Device Performance test on the drive. Select one test set with your choice of compression ratio. This will fill the tape and measure both capacity and performance. See Using the Drive Performance test (page 132). How do I send a support ticket? • Use the e-mail support ticket option if possible. See Sending a report or support ticket by e-mail (page 51) or Sending a support ticket by e-mail (CSI) (page 79). • If the above option is not possible, save the ticket to a single directory.
• Does L&TT use any system resources in the background? • 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.
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. Launch Internet Explorer.
L&TT starts in restricted mode and most functionality is unavailable. What is happening? L&TT automatically runs in restricted mode when it recognizes a 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.
How do I set the password? With a few exceptions, you may enter the options command at any time to display the Options dialog. The password may be set from this dialog. Exceptions: • 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 (page 166).
large number of devices and disks, HP recommends setting maxfiles larger than 2048 , depending on the SAN size. Use the commands kmtune or kctune to configure maxfiles. 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.
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 3. 4. Disconnect the device. Make sure that you have removed the corresponding SCSI cable from the HBA.
11 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.
This section starts with 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.
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. Run the test again with a different tape. • Dirty heads. Use a cleaning tape. If the drive still fails after trying both of the above then the issue is most likely with the drive.
Known issues Click the appropriate link: • Device access issues (RSM on Windows) • Device performance issues • Firmware issues with Ultrium drives • “Drive access issues with Ethernet I/O mode” (page 197) 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.
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.
and a suggested action to resolve the issue. In some cases there will be suggested links to other support documents as well as recommendations on when and how to L&TT. If you find symptoms and issues that aren't included in the guide, use the feedback button at the bottom of the FireFly screen to send the information to HP. We appreciate your feedback and used to continually update and improve the utility.
12 Support and other resources 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, provide feedback on this manual, report any issues with the L&TT website, or offer enhancement suggestions. HP appreciates feedback on how to improve future versions of L&TT. NOTE: This address is intended to provide support for L&TT software.
Table 2 Document conventions (continued) Convention Element 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 • File and directory names • System output • Code • Commands, their arguments, and argument values Monospace, italic text • Code variables • Command variables Monospace, bold text WARNING! CAUTION: IMPORTANT: NOTE:
A Operating system support Table 3 L&TT operating system support Operating system OS variant Last supported version of L&TT Windows Windows 2012 Current Windows 8 Current Windows 7 (x86, x86_64) Current Windows 7 SP1 (x86, x86_64) Windows Vista SP2 (x 64, x86, x86_64) Current Windows 2008 R2 (x86, IA64, x86_64) Current Windows 2008 R2 SP1 (x86, IA64, x86_64) HP-UX Linux Windows 2003 and Windows 2003 R2 (x86, x64, ia64) Editions Current Windows 2000 Server SP4, Advanced Server, and Datacen
Table 3 L&TT operating system support (continued) Operating system OS variant Last supported version of L&TT SuSE SLES 11 (x86, IA64, x86_64) Current SuSE SLES 11 SP2 (x86, IA64, x86_64) SuSE SLES 11 SP3 (x86, IA64, x86_64) SuSE SLES 10 SP3 (x86, IA64, x86_64) Current SuSE SLES 10 SP2 (x86, x86_64 OpenVMS Solaris SuSE SLES 9 (x86, x86_64) Current Fedora Linux Not supported Debian Linux Current OpenVMS 8.4 (Alpha/IPF) Current OpenVMS 8.3-1 (IPF) Current OpenVMS 8.
B Discontinued products The following products were supported in earlier versions of L&TT, but are not supported in the current version. Table 4 Discontinued products Product family Product Last supported version of L&TT DDS DDS-1 L&TT 3.
C 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.
Libraries and autoloaders Use of FUP tapes in STK libraries works just as it does for standalone drives. 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.
4. 5. 6. Use the [-] or [+] key to select the slot containing the FUP tape. Select [OK]. Monitor the front panel for status during the upgrade. The tape will return to the original slot when the procedure is complete. 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 on the number of 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.
Ultrium Standalone Ultrium drives There is no hard-coded limit on the number of 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.
DAT72x10 autoloader The FUP tape will update both the autoloader and drive firmware. To create a FUP tape for a DAT72x10 autoloader: 1. Place the drive firmware and autoloader firmware files in the firmware folder. 2. Rename the drive firmware file firmware1.frm. 3. Rename the autoloader firmware file firmware2.frm. 4. In L&TT, select the autoloader (not the drive) and choose the DAT AL Firmware Tape Creator test. To upgrade firmware using the FUP tape: 1. Move the FUP tape to a slot in the autoloader. 2.
Index brain dead mode, 175 By Connection tab, 26 By Product tab, 26 options, 72 page, 75, 78 preferences, 161, 166 review, 72, 75 save, 78 select, 66, 69 start, 72, 75 test, 73 testoptions, 75 view, 78 Compare Statistics utility, 143 compatibility matrix, 17 Connectivity test, 107 conventions document, 199 text symbols, 200 current password entered option, 163 customer advisories and notifications finding, 164 C D cartridge command, 69 cautions changing devices, 26 exclusive use of device by L&TT, 39 i
Ethernet I/O mode, 24 Ethernet access mode, 82 event log as a SCSI analyzer, 60 described, 59, 81 using, 59, 81 exclusive use of device by L&TT, caution, 39 exit command, 66 F Factory Firmware Overrides dialog box (GUI), 39 factory password, obtaining, 46 features, 9 files installed on the system, 180 find command, 78 firmware accessing revision and release note information, 34 acquiring (CSI), 71 advanced options (GUI), 39 allow downgrading, 40 allow selection of any file, 40 directory, 35 downloading, 36
log directory, 43, 78 log file, 43, 78 log file path option, 162 LTO Cooling Check test, 122 LTO Data Assessment test, 122 LTO Encryption test, 125 LTO Firmware to Data Tape Creator test, 146 LTO FUP tape erasing, 187 LTO Media Assessment test, 123 LTO Stuck Tape test, 125 LTO6 EEPROM download utility, 145 M Main screen (CSI), 68 manual product identification feature, 169 MAPI-compliant email programs, 52 Media Analysis test, 125 Media Validation test, 126 Miniport, 24, 26 driver, 19, 178 I/O mode, 19, 178
System Performance Restore Performance Test (GUI), 138 Test (GUI), 30 Utility (GUI), 31 script file path option, 162 scripts directory, 33 CSI, 77 SCSI analyzer, 60 SCSI scripts, 99 SDLT Tape Edge Damage test, 131 select command, 66, 69 show instructions option, 162 show scan details option, 162 skip this dialog in the future, 24 Skip-Scan feature, described, 22 start command, 72, 75 Startup screen, 21 support resources, 199 support ticket comparing, 53 converting to HTML, 149 detail level, 46, 148 e-mailin
upgrading from previous version, 19, 187 utilities Compare Statistics, 143 DAT autoloader firmware tape creator, 144 descriptions, 143 destructive to media, caution, 143 Device Configuration, 144 Firmware Tape Creator, 145 Force Tape Eject utility, 145 LTO Firmware to Data Tape Creator, 146 LTO6 EEPROM download, 145 re-initialize LTFS tape, 147 Read Media IDs, 146 running (CSI), 73 tape erase, 146 utility functions, 99 Utility screen (GUI), 31 utility scripts described, 33 using, 33 using from CSI, 77 V vi
