1. Manuals
  2. Brands
  3. HP Manuals
  4. Storage
  5. LTO Ultrium
  6. Technical reference manual

HP LTO Ultrium Technical Reference Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
HP LTO Ultrium tape drives technical reference
manual
Volume 1: hardware integration
LTO5 drives
Abstract
This is one of five volumes that document HP LTO Ultrium 5 tape drives (Fibre Channel and SAS). This volume
provides hardware integration information. See
Chapter 12
on page 153 for details of the other guides.
Part Number: EH890 90900 volume 1
Fourth edition: March 2010

Advertisement

Table of Contents
loading

Related Manuals for HP LTO Ultrium

Summary of Contents for HP LTO Ultrium

  • Page 1 Volume 1: hardware integration LTO5 drives Abstract This is one of five volumes that document HP LTO Ultrium 5 tape drives (Fibre Channel and SAS). This volume provides hardware integration information. See Chapter 12 on page 153 for details of the other guides.
  • Page 2 © Copyright 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.

  • Page 3: Table Of Contents

    Replacing the front panel ......................28 Parts needed ........................28 Replacing the front panel on an full-height LTO Ultrium drive ............. 28 Replacing the front panel on a half-height LTO Ultrium drive ............. 29 4 Rear panel and connectors ..............31 Rear panel components—full-height drives ..................
  • Page 4 Connecting the drive ......................51 SAS connector ......................51 Backup software ......................... 51 Installing in a tape array ......................52 Appropriate HP rack-mount systems ..................52 Airflow requirements ......................52 Full-height drives: ......................52 Half-height drives: ......................52 Identifying the drive ......................52...
  • Page 5 Modes of usage ......................... 52 Attaching to SAS ........................ 52 Connecting to a Fibre Channel router or by SAS to a server or router ........53 Fibre Channel connection ..................... 53 Server SAS connection ....................53 Replacing a drive ....................... 53 Installing in a library .........................
  • Page 6 Certificate manager (from A400h) .................... 150 Cryptographic algorithms (from A800h) ..................150 12 Support and other resources ............153 Related documents ........................153 Documents specific to HP LTO Ultrium drives ................. 153 Documentation map ......................153 Drives—general ......................153 Installation and configuration ..................153 Operation .........................
  • Page 7 Glossary ..................159 Index ....................165 Volume 1: hardware integration...
  • Page 8 Figures Rear panel components for a full-height Fibre Channel drive ......... 32 Rear panel components for a full-height SAS drive ............33 Rear panel components for a half-height FC drive ............34 Rear panel components for a half-height SAS drive ............34 ADI-LED connector schematic ..................
  • Page 9 Tables AL_PA and Loop ID look-up table ................35 Volume 1: hardware integration...

  • Page 11: Physical Dimensions

    • Half-height drives: 2.4 0.5 lb-in (0.24 0.30 Nm) • HP recommends 0.3 mm mounting clearance around all covers for isolation mounting movement. Full-height drives The recommended screw length depends on the thickness of the rails or enclosure into which the drive...

  • Page 12: Full-Height Drives: Bottom Panel

    Full-height drives: bottom panel Full-height drives: side panel Half-height drives Mounting Points Maximum Screw Penetration Side 3 mm Bottom 2.1 mm Physical dimensions...

  • Page 13: Half-Height Drives: Bottom Panel

    Half-height drives: bottom panel Half-height drives: side panel FC drives: SAS drives: Volume 1: hardware integration...
  • Page 14 Physical dimensions...

  • Page 15: Electrical And Environmental Requirements

    Maximum Current 3.6A <3.7A 0.50A <3.0A See also details in Chapter 2, “Electrical Requirements” in Specifications, Volume 4 of the HP LTO Ultrium Technical Reference Manual. The drive is specified to operate at 5V 5% and 12V 10%. Voltage and current requirements...

  • Page 16: Half-Height Drives

    Half-height FC drive power consumption figures are currently provisional. Final power consumption figures will be available in a future edition of this document. Airflow requirements HP LTO Ultrium drives require forced airflow to ensure that components never exceed critical temperatures. Full-height drives Airflow should be from front to back.

  • Page 17: Half-Height Drives

    40°C maximum temperature ambient environment, equating to <65°C at 40°C ambient. Airflow and cooling HP LTO Ultrium drives require forced airflow that satisfies the following conditions: • For full-height internal drives, the airflow at 35°C ambient air operation should be at least 6 cubic feet per minute (0.17 cubic meters per minute or 10.19 cubic meters per hour) through the product.

  • Page 18: Optional Fan Plate

    45°C and ensure reliable operation. The airflow does not require filtering if the air contamination specifications are met. See “Climatics” in Chapter 4, “Environmental Specification” in Specifications, Volume 4 of the HP LTO Ultrium Technical Reference Manual.
  • Page 19 The “Max temperature since cartridge loaded” value is ASCII encoded in bytes 22 29 of the incoming data. Example SCSI trace: SendDiagnostic |1D 11 00 00 08 00 |00008|00|00| Data Out |93 00 00 04 00 00 20 2A | ReceiveDiagResults |1C 01 93 01 00 00 |0009C|00|00| Data In |93 00 00 98 30 30 30 30 31 41 31 32 20 30 30 30 |...
  • Page 20 Electrical and environmental requirements...

  • Page 21: Front Panel And Leds

    3 Front panel and LEDs HP LTO Ultrium 5 products have three front panel designs: • System, for use in servers, rack mounts and other non-automation applications—see “Front panel features” below • Automation, for use when the drive is embedded in automation applications—see “Front panel...

  • Page 22: Half-Height Drives

    NOTE: Only full-height drives have a reset switch. Half-height drives 1. LEDs 2. Eject button Usual meaning of LEDs The five LEDs, Ready, Drive Error, Tape Error, Clean and Encryption usually have the following meanings: Ready Green. Indicates power and activity: Power off or self-test failure Powered on and ready for use, but no activity Flashing...

  • Page 23: Led Patterns

    Clean Orange. Indicates whether the drive needs cleaning. Cleaning not required Cleaning cartridge being used. The Ready LED flashes. Flashing Cleaning needed. The LED continues to flash if the drive is power cycled, and will only go out after a supported cleaning tape has been used.
  • Page 24 Tape Error FLASHING. (Other LEDs may be Unload the tape cartridge. Make sure that it on or flashing.) is a valid format: an LTO Ultrium data cartridge or LTO Ultrium Universal cleaning The drive believes the current tape or the tape cartridge.

  • Page 25: Half-Height Drives

    LEDs Cause Action required Tape ejects immediately and Tape Error Write-protect the cartridge by sliding the red FLASHES. (Other LEDs may be on or flashing.) switch on the cartridge. The tape can be loaded and the data read. Once the data is The tape cartridge memory (CM) may be recovered, discard the cartridge.
  • Page 26 LEDs Cause Action required Ready ON. None. This is normal. The drive is ready for operation. Ready FLASHING. None. The drive is carrying out a normal activity If the drive is upgrading firmware, do not (read, write). reset or power cycle it. If you need to exit OBDR mode, power cycle or reset the drive.

  • Page 27: During Firmware Upgrade

    Tape Error FLASHING. (Other LEDs may be Unload the tape cartridge. Make sure on or flashing.) that it is a valid format: an LTO Ultrium data cartridge or LTO Ultrium Universal The drive believes the current tape or the cleaning cartridge.

  • Page 28: Replacing The Front Panel

    • Small bladed screwdriver (125x5 slotted or smaller) Replacing the front panel on an full-height LTO Ultrium drive Use the screwdriver to release the tabs at the top of the chassis and underneath. Pull the front panel towards you and away from the drive.

  • Page 29: Replacing The Front Panel On A Half-Height Lto Ultrium Drive

    Replacing the front panel on a half-height LTO Ultrium drive Use the screwdriver to release the tab on the right side of the chassis (next to the red warranty sticker). Swing the front panel out slowly, pulling it gently to the left, so that the lugs release on the left side of the chassis.
  • Page 30 Front panel and LEDs...

  • Page 31: Rear Panel And Connectors

    4 Rear panel and connectors The rear panel contains the connector interface that allows the tape drive to communicate with a tape library or host computer system. The panel includes the following connectors: • Either: Two SFP duplex-LC optical fibre connectors (full-height drives have two, though only one might be connected;...

  • Page 32: Rear Panel Components-Full-Height Drives

    Rear panel components—full-height drives Figure 1 Rear panel components for a full-height Fibre Channel drive 1. Diagnostic serial port (4 pin) 2. iADT Ethernet (10 pin) 3. External fan support (6 pin) 4. Port A optical connector (standard) 5. Port B optical connector (optional) 6.

  • Page 33: Rear Panel Components For A Full-Height Sas Drive

    Figure 2 Rear panel components for a full-height SAS drive 1. Diagnostic serial port (4 pin) 2. External fan support (6 pin) 3. iADT Ethernet (10 pin) 4. SAS SFF 8482 connector 5. Automation and remote LEDs (16-pin) 6. Diagnostic serial port (4 pin) 7.

  • Page 34: Rear Panel Components-Half-Height Drives

    Rear panel components—half-height drives Figure 3 Rear panel components for a half-height FC drive 1. Automation and remote LEDs (16-pin) 2. Alternate serial port (4 pin) 3. Diagnostic serial port (4 pin) 4. External fan support (6 pin) 5. Power 6.

  • Page 35: Leds (Full-Height Fibre Channel Drives Only)

    LEDs (full-height Fibre Channel drives only) The rear panel has two LEDs, one each for Fibre Channel Port 0 and Port 1. Power-on self-test failure If the Fibre Channel firmware encounters a Power-On Self-Test failure, the drive will not initialize the FC ports and so will not respond over the FC interface.

  • Page 36: Connectors

    AL_PA Loop AL_PA Loop AL_PA Loop AL_PA Loop AL_PA Loop AL_PA Loop Connectors Fibre Channel connector Full-height FC drives are equipped with two SFP duplex-LC short-wave 8 Gb/s fibre connectors. The drives are capable of switched fabric attach, public loop or private loop and operate at 8 Gb/s, 4 Gb/s or 2 Gb/s after auto-speed negotiation.

  • Page 37: Automation And Remote Led Connector

    Automation and remote LED connector The combined Automation and Remote LED Connector is a 16-pin wafer surface-mount right-angle connector. 10 pins are used for the ACI/ADI interface and 6 pins for the remote LEDs. Connector pins ACI operation When used for ACI communications, the pins of the ACI connector are as follows: Function RS-422 Receive (+ side of the differential RS-422 line) ACI_RX+...

  • Page 38: Remote Leds

    For details of ACI commands, see Chapter 5 “Supporting LTO Ultrium Features” of the Software Integration Guide, Volume 2 of the HP LTO Ultrium Technical Reference Manual. ADI operation When used for ADI communications, the pins of the ADI connector are as follows:...

  • Page 39: Automation And Remote Led Connector Schematic

    Pin 13 Port 2 Status LED output Pin 14 Host controlled (Beacon) LED output Pin 15 Encryption LED output Pin 16 5V supply Automation and remote LED connector schematic Figure 5 ADI-LED connector schematic Notes: • The maximum LED current supported is 25 mA. •...

  • Page 40: Iadt (Ethernet) Port

    39 is used for all LED ports. Diagnostic Serial Port connector For products with two serial ports the same connector pin-out is used on both ports. The serial ports are identical to those on previous HP LTO products. Rear panel and connectors...

  • Page 41: Fan Control Connector

    A four-wire fan is required. NOTE: If you intend to plug a fan into this connector to provide the necessary airflow through the drive, consult your HP Technical Support Representative for details of the fan specification required. Volume 1: hardware integration...
  • Page 42 Rear panel and connectors...

  • Page 43: Cartridges

    NOTE: HP LTO Ultrium 5 tape drives are not compatible with LTO Ultrium 1 or 2 media, which will be rejected as unsupported. The Tape Error LED will light. HP recommends HP LTO Ultrium cartridges as follows: •...

  • Page 44: Cartridge Life

    Conditions in use Only use LTO Ultrium cartridges in temperatures within the tape drive’s operating range from 10°C to 40°C (50°F to 104°F) and 20 to 80% relative humidity (non-condensing). If you expose cartridges to temperatures outside the operating limits, stabilize them before you use them. To do this, leave the cartridges in the operating environment for 24 hours.

  • Page 45: Conditions In Storage

    Conditions in storage LTO Ultrium cartridges will preserve the integrity of stored data for up to 30 years if proper storage conditions are observed. • For short-term storage, keep cartridges at temperatures between 16°C and 32°C (61°F and 90°F) with a relative humidity between 20% and 80%.

  • Page 46: Lto Cartridge Memory Issues

    • Host Common Section—updated by the host’s software application every time it uses the media. For example: software application vendor’s name and version, media text label, date last written • Media Vendor Unique Section—optional information written by the media vendor for their own purposes.

  • Page 47: Planning Your System Configuration

    This is automatically managed by the drive to keep the drive running at best performance. When using LTO Ultrium 5 cartridges, the drive is able to keep streaming between 47 and 140 MB/s (native), Volume 1: hardware integration...

  • Page 48: Performance Checklist

    They do not attempt to explain how to configure individual systems. For a more detailed discussion, including information about tools that allow you to test performance, refer to our white papers on www.hp.com. (Select the product first and look at the Information Library.) •...

  • Page 49: Installing And Replacing Drives

    5 of the HP LTO Ultrium Technical Reference Manual. Installing in a server Full details of how to install an internal LTO Ultrium tape drive into a server drive bay is given in the Getting Started Guide. Identifying the model The model name is on the front panel and the product and serial numbers are on a label on the top of the drive.

  • Page 50: Requirements

    • Full-height drives require one industry standard 5¼-inch, full-height bay. HP recommends 0.3 mm mounting clearance around all covers for isolation mounting movement. For many servers, no mounting tray or rails are required. Devices simply slide into the computer’s chassis and are fixed with screws. Other servers have built-in trays or rails. Yet others require a special mounting tray or rails to fix the drive into the empty bay.

  • Page 51: Connecting The Drive

    SAS drive is hot pluggable but the connector location is not as defined in SFF8482. NOTE: HP LTO5 SAS tape drives do not have a normal power connector and must be powered via the SAS connector. The rear connections of an SAS drive are as follows: •...

  • Page 52: Installing In A Tape Array

    Airflow requirements As long as the tape array is fully populated, it will provide adequate airflow for HP LTO Ultrium drives. If you have unused bays in the tape array, you must install the blanking plates provided with the tape array.

  • Page 53: Connecting To A Fibre Channel Router Or By Sas To A Server Or Router

    If you are using your tape drive on a fibre channel (FC) network, you will need a FC/SAS router. If you are attaching your tape drive to a SAN environment supplied by HP, refer to your SAN solution collateral or configuration guides for further details.

  • Page 54: Installing Standalone Drives

    • Diagnostic serial port connector The proprietary serial HP LTO diagnostic port. To access this port via RS232 requires an HP LTO Diagnostic Interface Card. Diagnostic information from the drive can be accessed by connecting to the serial communications port on a computer. Contact HP for further details on this diagnostic port and its function.

  • Page 55: Moving Drives

    Moving drives If there is a tape in the drive, unload it before powering down and moving the drive. When the drive is powered down, there is no physical lock on the tape reels. If you leave a tape threaded in the drive with the power off, the reels could rotate, causing a loop of tape to occur in the tape path.
  • Page 56 Installing and replacing drives...

  • Page 57: Operating The Drive

    8 Operating the drive Power-on self-test When powered-on, the tape drive will run its hardware self-test: • In a server, internal drives are powered on when you switch on your computer. • In a tape array, removable drives are powered on when you switch on your tape array and computer.

  • Page 58: Loading A Cartridge

    2. Drive door 3. Cartridge label area NOTE: Use HP LTO Ultrium cartridges. Insert the cartridge into the slot in front of the drive with the arrow uppermost and facing the drive door. Apply gentle pressure on the rear of the cartridge until the drive takes the cartridge and loads The Ready LED flashes green while the drive performs its load sequence.

  • Page 59: Unloading A Cartridge

    70 for details. CAUTION: It is essential to use only LTO Ultrium Universal cleaning cartridges C7978A (Orange) with HP LTO Ultrium tape drives as other format cleaning cartridges will not load and run. Use of HP cleaning media will ensure your tape drive is fully protected.

  • Page 60: Resetting Drives In A Library

    If the cleaning cartridge ejects or returns to the ready-to-eject position immediately with the Tape Error LED on, it has expired or it is not an LTO Ultrium cleaning cartridge (or is an older unsupported LTO Ultrium cleaning cartridge). In this case, discard the cleaning cartridge and repeat the operation with a new one.

  • Page 61: Troubleshooting

    9 Troubleshooting Emergency unload (forced eject) If a cartridge fails to eject using the normal unload procedure, press and hold the Eject button for 5 seconds. This instructs the drive mechanics to perform an emergency unload. Wait for the cartridge to be ejected.

  • Page 62: Diagnosing The Problem

    Diagnosing the problem The first step in problem-solving is establishing whether the problem lies with the cartridge, the drive, the host computer and its connections, or with the way the system is being operated. NOTE: If the drive is installed in a library, refer to troubleshooting information provided with the tape library, the host or the backup software if the problem seems to lie in one of these areas.

  • Page 63: Problems With The Drive And Cartridge

    Check the drive is installed properly. Refer to our World Wide Web tape drive. site (www.hp.com/go/connect) for details of backup applications that support HP LTO Ultrium tape drives. Load any service packs as necessary. Some applications require drivers to Check the correct drivers are installed. Consult the backup applica- be loaded.

  • Page 64: The Cartridge Will Not Eject

    Possible Cause Potential Solution The cartridge is not compatible with Check you are using LTO Ultrium 3, 4 or 5 media. LTO Ultrium your tape drive. 5 drives do not accept LTO Ultrium1 or 2, or other non-LTO Ultri- um media.

  • Page 65: The Computer No Longer Recognizes The Drive In A Tape Array

    If the data cartridge can be read, back up the data to another cartridge and then discard the damaged one. The cleaning cartridge is ejec- Make sure that you are using an approved LTO Ultrium Universal cleaning ted immediately after loading. cartridge and that the cleaning cartridge is not expired.
  • Page 66 Troubleshooting...

  • Page 67: 10 Special Features For Automation

    • LTO Cartridge Memory (LTO-CM) or Cartridge Memory is EEPROM memory that is embedded in every LTO Ultrium tape cartridge. It is non-volatile and is contactless in that it is read by RF coupling rather than electrical contact. For suggestions of how to make use of cartridge memory in libraries, see “Using Cartridge Memory...

  • Page 68: Front Panel For Automation Use

    Front panel for automation use Full-height drives 1. Eject button 2. Access hole for emergency reset switch 3. Holes for optical sensors 4. LEDs The automation front panel has the following features: • There is an eject button for manually ejecting a cartridge. Press this for approximately ten seconds to start a “forced eject”...

  • Page 69: Front Panel For Use In Autoloaders

    Front panel for use in autoloaders A special front panel is available for autoloader applications. The front panel fits within the drive form factor in height and width: 1. Access to Eject button 2. Access hole for emergency reset switch 3.

  • Page 70: Half-Height Drives

    The bezel is 4.1 mm thick. Automation interface The HP LTO-5 tape drive supports connection to an automation device via the serial ADI port or via an Ethernet port. The ADI port supports the HP proprietary ACI protocol for connection to legacy libraries and the sADT protocol.

  • Page 71: Automation Control Interface (Aci)

    It provides a rich and extensible functionality to allow automation manufactures to add value in their application of it. The interface is a serial bus with additional control lines, designed to connect the LTO Ultrium tape drive to an automation controller in a tape library. Each tape drive position has a separate automation controller.

  • Page 72: Internet Automation Device Interface (Iadt)

    ADI Mode, so the tape drive behavior may change after transitioning between the two modes. HP recommends that the drive is used in either exclusively ACI or ADI modes of operation. Avoid mixing operation of the two modes.
  • Page 73 Public Key Infrastructure (PKI) credentials used by the HP LTO-5 drives consist of three classes of X.509 certificates: root certification authority (CA), device, and management host. If the drive has not received a root CA certificate and a device certificate, then SSL/TLS connections (such as iADT-TLS) will not be accepted.

  • Page 74: Fan Interface

    Fan interface The HP Ultrium LTO5 drive has the capability to control an external fan. The purpose of this is to provide the necessary airflow through the drive to keep the internal temperatures within normal parameters. For details of the Fan Connector, see “Fan control...

  • Page 75: Cartridge Positions During Load And Unload

    Cartridge positions during load and unload The following diagrams show the positions of importance during load and unload. Figure 11 Full-height drives: load and unload positions Figure 12 Half-height drives: load and unload positions NOTE: Drives for library use the automation front panel, which has no door. The illustration shows a standalone drive.

  • Page 76: Load Scenarios

    Load Point 1 If Autoload is set (Autoload field = 0), the drive will start to load the cartridge when it reaches this point. If Autoload is not set (Autoload field = 1 or 2), the library must insert the cartridge into the drive to a position between Load Point 1 and Load Point 2.

  • Page 77: Load/Unload Forces

    The host sends a Move Medium command to the robotics. The picker takes the cartridge from the tape drive and places it in its storage slot. Unload scenario 2: Library controlled The host sends an Unload command to the drive. The drive rewinds and unthreads the tape.

  • Page 78: Current Libraries - Barcodes

    However, because Cartridge Memory has space that can be written by applications, it can hold details of the contents and nature of the tape. This obviates the need for this information to be held by the application. HP is working with other industry leaders, both hardware and software, on an Industry Common Implementation Guide.

  • Page 79: 11 Drive Error Codes

    The following error codes may be reported in bytes 16 and 17 of the Request Sense data and also reported in ACI Get Error Info RDATA, bytes 3 and 4. See the REQUEST SENSE command in Chapter 4 of the Host Interface Guide, Volume 3 of the HP LTO Ultrium Technical Reference Manual. Generic module (from 0000h)
  • Page 80 Code Description 040Ah Invalid command length . 040Bh Byte buffer framing error. 040Ch Byte buffer overrun error. 040Dh Command active abort rejected. 040Eh Invalid response acknowledgement. 040Fh Transmission time-out. 0410h Did not receive ETX. 0411h Cancel command packet timer error. 0412h Custom byte error.
  • Page 81 Code Description 0428h ACI Control queue is empty. 0429h ACI Response queue is empty. 042Ah ACI Response packet was NAKed. 042Bh ACI attempted to execute an unsupported PPL command. 042Ch ACI has detected a command with a parameter out of range. 042Dh ACI attempted to execute a PPL command before the previous command completed.
  • Page 82 Code Description ACI too busy because of comms resync. Used in tracepoints to identify cause of 0443h AC_BUSY_CMD_REJECTED error. ACI too busy because upgrading. Used in tracepoints to identify cause of 0444h AC_BUSY_CMD_REJECTED error. ACI too busy because out of memory. Used in tracepoints to identify cause of 0445h AC_BUSY_CMD_REJECTED error.

  • Page 83: Buffer Manager (From 0800H)

    Code Description 045Dh A function will send a response when it has finished. ACI self-test failure — ACI should not be executing a direct Command while performing 0480h the self-test. ACI self-test failure — ACI should not be executing a slow Command while performing 0481h the self-test.

  • Page 84: Diagnostic Control (From 1800H)

    Diagnostic control (from 1800h) Code Description 1800h No errors. 1801h Invalid command. 1802h Invalid parameters. 1803h Drive not ready. 1804h Command failed. 1805h Command aborted. 1806h Too few parameters. 1807h Too many parameters. 1808h Command denied. 1809h Operation code not supported in diagnostic CDB command. 180Ah Page code not supported in diagnostic CDB command.
  • Page 85 Code Description 1845h Power-on self-test failed the Firmware Image Checksum. 1846h Power-on self-test failed the CRAM Data Bus test. 1847h Power-on self-test failed the CRAM Address Bus test. 1848h Power-on self-test failed the SCSI ASIC Register test. 1849h Power-on self-test failed the SCSI ASIC Buffer Data Bus test. 184Ah Power-on self-test failed the SCSI ASIC Buffer Address Bus test.
  • Page 86 Code Description 1862h A field is invalid in a diagnostic CDB command. 1863h POST failed. The image checksum is invalid. 1864h POST failed. The checksum is incomplete. 1865h Invalid length/address in READ/WRITE MEMORY command. The Drive Configuration Table returned permission denied in response to a Write CM/EEP- 1866h ROM operation.

  • Page 87: Drive Control (From 1C00H)

    Tried to load a writable cartridge with an unusable Cartridge Memory. 1C0Bh The write-protect tab setting was changed during a load. 1C0Ch A non-HP cleaning cartridge has been inserted in the drive. 1C0Dh Cannot determine the manufacturer of the cleaning cartridge. 1C0Eh No DRAM space reserved to hold the firmware image.

  • Page 88: Drive Monitor (From 2000H)

    Code Description 1C18h Expected a cleaning cartridge but got something else on load. 1C19h Cartridge Memory is unusable and failed to read the FID. 1C1Ah Firmware upgrade image information is unavailable. 1C1Bh Could not find firmware information in the new image. 1C1Ch A tape load has failed.

  • Page 89: Front Panel Interface (From 2800H)

    Code Description 2408h Aborted an active command. 2409h Aborted a command before it became active. 240Ah Tried to abort a command that was not queued. 240Bh Invalid state requested of the EII State Manager. 240Ch The EII tried to process a firmware upgrade type that is not supported. 240Dh The EII state manager could not handle an abort request.
  • Page 90 Code Description 2C04h Firmware bug. 2C05h Parameter list length error. 2C06h Already prevented. 2C07h Not prevented. 2C08h Too many hosts. 2C09h 32-bit overflow. 2C0Ah Invalid space code. 2C0Bh Bad inquiry page. 2C0Ch Not the reserver. 2C0Dh Not reserved. 2C0Eh Third-party bad. 2C0Fh Third-party host.
  • Page 91 Code Description 2C22h Inf host interface ARM POST — FC diagnostic CC1 2C23h Inf host interface ARM POST — FC diagnostic counters. 2C24h Inf host interface ARM POST — FC diagnostic FIFO test. 2C25h Inf host interface ARM POST — FC diagnostic interface. 2C26h Inf host interface ARM POST —...
  • Page 92 Code Description 2C40h Buffer manager check buffer CRCs mismatch. 2C41h Buffer manager check CRC passed. 2C50h Illegal SCSI command. The hardware or firmware does not recognize the CDB. 2C51h The SCSI Macro command was aborted because the drive was selected first. 2C52h ATN was pulled by the initiator.
  • Page 93 Code Description 2C6Bh There is no tape in the drive. 2C6Ch Loading a tape. 2C6Dh Media changed. A tape is present in the drive but not loaded. 2C6Eh Cleaning the tape heads. 2C6Fh Received a PON or SCSI reset. 2C70h A mode change (LVD/SE) occurred on the SCSI bus.
  • Page 94 Code Description 2C88h The Log Sense PC Code is in error. 2C89h Log Select: error in the parameter header. 2C8Ah Restart the Logical Pipeline after a format error. 2C8Eh The Buffer Manager has been interrupted with an error. 2C8Fh Check the cables. The Host Interface has exhausted all of the retries for a data phase. 2C90h Log Select parameter list length error.
  • Page 95 Code Description 2CA5h ILI long has been detected but a read error was encountered during the residue flush. 2CA6h An init command is required; a tape has been loaded but not threaded. 2CA7h ILI long has been detected but flushing the residue timed out. 2CA8h LTO 1 drives only: The CD-ROM El Torito identifier is corrupt.
  • Page 96 Code Description 2CC2h MAM not accessible for some indeterminate reason. 2CC3h SCSI sequencer was asked to reconnect during invalid nexus. SCSI sequencer received a hiRetryDataBurst which failed. 2CC4h 2CC5h INQUIRY data too long. 2CC6h REQUEST SENSE data too long. 2CC7h Invalid LUN for storing INQUIRY data in the mini-buffer.
  • Page 97 Code Description 2CE0h Bad state—firmware defect. 2CE1h Bad configuration—firmware defect. 2CE2h The Host Interface ASIC has not responded to a mail-box operation within 10 ms. 2CE3h Got an internal firmware reboot. 2CE4h SCSI Bus Reset signal asserted by host. 2CE5h Bus Device Reset message sent by host.
  • Page 98 Code Description Drive control has set drDriveStatus to DR_FW_UPGRADE. 2D09h 2D0Ah Immediate LOAD/UNLOAD in progress. 2D0Bh Reported when an Immediate command is executing and a subsequent command is received. 2D0Ch I_T nexus loss occurred. 2D0Dh The maximum number of surrogate logical units have been defined. 2D0Eh The supplied surrogate inquiry page is incorrect.

  • Page 99: Logical Formatter (From 3000H)

    Logical formatter (from 3000h) Code Description 3000h No error. Synonymous with GOOD status. 3001h Operation of the Logical Formatter has been aborted. 3002h Busy. A Logical Formatter process has received a operation request while in a transient state. The value of a parameter received with a Logical Formatter operation request falls outside 3003h its valid range.
  • Page 100 Code Description 302Eh The Logical Formatter has encountered a decompression error. 302Fh The Logical Formatter has encountered EOD. 3030h The Logical Formatter failed to write a filemark — aborted. 3031h The Logical Formatter failed to write a filemark — data path not empty. 3032h The Logical Formatter failed to write a filemark —...
  • Page 101 Code Description 3311h Logical Formatter compressor reset. 3312h Logical Formatter stall timer ID confusion. 3320h Logical Formatter packer overrun. 3321h Logical Formatter non-empty packed segment. 3322h Logical Formatter packer missed EOR. 3323h Logical Formatter unpacker overrun. 3324h Logical Formatter packer aligned EOR. 3325h Logical Formatter packer data in packer.
  • Page 102 Code Description 3354h Encrypt UnpackerLite error detected. 3355h Crypt GCM tag error detectd. 3356h Crypt EoR alignment error. 3357h Crypt EoR before tag error detected. 3358h Crypt If_data_valid error detected. 3359h Crypt EoR found error detected. 335Ah LF post-key wrap failure. 335Bh LF post-key unwrap failure.

  • Page 103: Logical Media (From 3400H)

    Logical media (from 3400h) Code Description 3400h Cache overflow. A dataset has been received when the cache is already full. 3401h A dataset has been located in the cache where it should not be. 3402h A tag dataset has been located in the cache where it should not be. 3403h Attempted to unlock a dataset which is not locked.

  • Page 104: Logical Pipeline Control (From 3800H)

    Code Description 341Ch Linked-list ‘next’ pointer is invalid. 341Dh CRAM transfer started but not finished. 341Eh Allocated insufficient CRAM. 341Fh Dataset is available in LM but the drive is not positioned to append. 3420h Datasets in LM, Flush WITH_EOD required before the current operation 3421h LM flushed but EOD is required before the current operation.

  • Page 105: Non-Volatile Data Manager (From 4000H)

    Error Description 3C02h Unsupported command error. 3C03h Bad parameter error. 3D01h Undefined data object error. 3E0Eh Cleaning cartridge could not be threaded. 3E01h Wait for signal. 3E02h Object create failed. 3E03h Object execute failed. 3E04h Cartridge memory LPOS values suspect. 3E05h Notify client list full.
  • Page 106 Error Description 4011h PCA EEPROM missing. 4012h PCA EEPROM void. 4013h PCA EEPROM corrupt. 4014h PCA table invalid. 4015h A failure occurred while trying to update the Read ERT log in the PCA EEPROM. 4016h A failure occurred while trying to update the Write ERT log in the PCA EEPROM. 4017h A failure occurred while trying to update the Write Fault Counters log in the PCA EEPROM.
  • Page 107 Error Description 4042h CM EEPROM void. 4043h The CM could not be written before an unload causing probable corruption in the CM. 4044h An invalid protected page table was found. 4045h A CRC error was discovered over the unprotected page table. 4046h CM initialized.
  • Page 108 Error Description 40A1h The last updated mechanism sub-page has a CRC error. The data is invalid. 40A2h There has been a failure executing self-test. This failure is logged in the Fault Log. 40A3h Cartridge Memory TapeAlert CRC error. 40A4h Cartridge Memory EOD page CRC error. 40A5h Cartridge Memory suspend append CRC error.
  • Page 109 Error Description The persistent storage area for the device ID has never been written to and is therefore not 40BBh initialized. The persistent storage area for the device ID only supports storage for 2 LUNs—more has 40BCh been requested. A request to access an area of CM which is out of bounds has occurred. The access was 40BDh disallowed.

  • Page 110: Operating System (From 4400H)

    Error Description 40D4h The PCA2 EEPROM is not supported on this platform. 40D5h An unknown KMS security parameter was asked for. The KMS security parameter was encrypted, however the encrypted record size ends up 40D6h being too large for storage The Initialization check of the KMS security table showed a bad CRC on the directory entries.

  • Page 111: Physical Pipeline Control (From 5000H)

    Error Description 4C0Ch The physical formatter Read Chain Controller DS0 is stuck. 4C0Dh The physical formatter Read Chain Controller DS1 is stuck. 4C0Eh Physical formatter WP update. 4C0Fh Format other than LTO1 or LTO2. 4C10h SDRAM error has been detected. 4C11h The number of CCPs presented has fallen below the warning threshold.
  • Page 112 Error Description 5086h PF reported a streamfail. 5087h The error-rate test reached the C1 threshold. 5088h Unknown notification. An unexpected mechanism control. 5089h Data miscompare. 508Ah The drive has gone 4 metres since last dataset was reported. 508Bh The speed requested for ERT s out of valid range. 508Ch The notify for 4m give-up point is missing.

  • Page 113: Physical Side Error Recovery (From 5400H)

    Error Description 50A4h The value of TapeWritePassValue CurrentWrap and SDL sheet has been set. 50A5h Shows the value that the Max ATS has been set. An error code of 7501h (Loss of LPOS) has been detected, causing a reduction in the servo 50A6h MR bias.
  • Page 114 Error Description 5810h Wrong number of parameters. 5820h Could not set Prometheus 0 to default values. 5821h Could not set Prometheus 1 to default values. 5822h Could not set Prometheus 2 to default values. 5823h Could not set Prometheus 3 to default values. 5824h A valid Mod level was not received from the PCA EEPROM.

  • Page 115: System Architecture (From 6400H)

    Error Description An invalid control word was found while parsing the Cal table to program a ASIC. Param 5861h 1 = control word, Param 2 = an integer value unique to each ASIC. 5870h Could not write to Amundsen’s WEQ Control register. 5871h Illegal WEQ setup requested.

  • Page 116: Trace Logger (From 6C00H)

    Trace logger (from 6C00h) Error Description 6C00h TraceLogger initialization failed. BMM returned no good. 6C01h The last Live Trace entry has been reached. Not an error. 6C02h The drive has insufficient resources to set more Live Traces. 6C03h A flush has started and the initiator must wait to receive the SDL signal diTraceLogFlushed. 6C04h An operation has started but the caller must wait for the callback function to be executed.
  • Page 117 Error Description 7412h A shuttle tape command cannot be executed at this time. 7413h A Set Cartridge Type command cannot be executed at this time. 7414h A Set Mechanism Type command cannot be executed at this time. 7415h A Set Tension command cannot be executed at this time. 7416h A Set Speed command cannot be executed at this time.
  • Page 118 Error Description 742Dh The Set Gen command is not allowed now. The format cannot be changed at this time. A Forced Eject command is not allowed at this time. Most likely another operation is in pro- 742Eh gress. 742Fh Debug ERROR code. 7430h Sensors are in a state that indicate that the sensors or Callisto is not working correctly.
  • Page 119 Error Description 7457h Timed out waiting for DSP to complete the head-cleaning command. 7458h Head-cleaning engagement time-out. 7459h Head-cleaning parking time-out. 745Ah Head-cleaning cycling time-out. 745Bh The state of the sensor read at initialization are illegal. The results make no sense. 745Ch Timed out waiting to restore DSP after a head-cleaning command.
  • Page 120 Error Description 7476h No scope data available from DSP 7477h DSP failed to complete the command during the initialization process. 7478h Unable to send DSP tuning parameters. 7479h DSP failed to boot properly. 747Ah Time-out on sending the Clear DSP Fault log. 747Bh Time-out on completing the Clear DSP Fault log.
  • Page 121 Error Description 7493h While threading, the LM voltage was increased from 0.25V to 0.5V. 7494h While threading, the LM voltage was increased from 0.5V to 0.75V. 7495h While threading, the LM voltage was increased from 0.75V to 1.0V. Load command failed and no CM was detected, therefore it is likely there is no cartridge 749Ah present.
  • Page 122 Error Description 74CEh Time-out waiting for radii estimate. 74CFh Radii estimation process failed. 74D0h Recover tape time-out error. 74D1h Invalid cartridge type. 74D2h Cal reel driver offset time-out. 74D3h Time-out waiting for the specified event. 74D4h Front-reel motor hall sensor fault. 74D5h Back-reel motor hall sensor fault.
  • Page 123 Error Description 7503h Write fault: tape motion start-up operations are incomplete so writing is not allowed. 7504h Write fault: DSP is not tracking properly on the tape, writing is not allowed. 7505h Write fault: the current tape speed is too low so writing is not allowed. 7508h Write fault: ATS clock frequency clipped, or DSP in idle mode.
  • Page 124 Error Description 760Dh Wait Until Event command invalid parameter. 760Eh Convert LPOS command invalid parameter. 760Fh Shuttle command invalid parameter. 7610h Get DSP fault log invalid parameter. 7611h Set General Command Invalid parameter. 7612h Set TestMode command parameter is out of range or is invalid. 7613h EEPROM servo table command parameter is out of range or is invalid.
  • Page 125 Error Description 7634h The tape thickness is too great to be handled properly by the servo system. An ATS speed change operation (AdjustSpeed) timed out waiting for tape to reach target 7635h speed. 7636h An ATS speed change operation (AdjustSpeed) was attempted while the tape was not moving. While trying to park the pin, LP2 was seen, but LP1 was not seen after rotating the grabber 7637h CCW.
  • Page 126 Error Description 7650h Unable to detach leader block during recover tape operation when reverse threaded. 7651h Unable to detach leader block during recover tape operation when forward threaded. 7652h Unable to identify cartridge type during recover-tape operation. 7653h The tape thickness reported by the Cartridge Memory is too large or too small. 7654h The tape thickness reported by the CM is invalid and cannot be used.
  • Page 127 Error Description 766Bh Recovery process is using a secondary head set to perform a sensor calibration operation. 766Ch Recovery process is using a secondary head set to perform an azimuth calibration operation. 766Dh Servo calibration cannot be done now because it is too close to BOT. 766Eh Timed out waiting for half moon to approach head during a thread.
  • Page 128 Error Description The thread operation is being retried because the pin detect sensor indicates parked when 7686h not parked. 7687h The threading recovery could not get the tape stopped in a reasonable time period. 7688h Timed out waiting for a regrab to complete before threading. 7689h Timed out trying to read the media manufacturer’s information.
  • Page 129 Error Description Time-out during ReadDspFaultLog. 76A3h 76A4h Time-out during ClearDspFaultLog. Unable to send a DspWriteDataMem command. 76A5h 76A6h Dsp failed to complete a WriteDataMem command. 76A7h Unable to send DSP sample rate parameters. 76A8h A threading fault has occurred. 76A9h An unthreading fault has occurred.
  • Page 130 Error Description 76C0h The write-protect sensor does not match the specified low state. EEPROM values unavailable. Invalid table revision. Default servo tuning values are being 76C1h used instead. 76C2h EEPROM values unavailable. Invalid table revision. Default values are being used instead. 76C3h The drive is not in the correct state to allow the power mode to be changed.
  • Page 131 Error Description The specified scope trigger position is too large compared to the specified number of data 76F4h packets in the trace. 76F5h The length of the buffer must be larger than zero and an even number. 76F6h The specified source number is not valid. 76F7h The specified scope buffer format parameter is not valid.

  • Page 132: Exception Handler (From 7800H)

    Error Description 7710h DSP fault: unable to find a top servo band. 7711h DSP fault: unable to lock to track 0 on a top servo band. 7712h DSP fault: unable to verify band ID on a top servo band. 7713h 771Fh DSP faults: spare.

  • Page 133: Spi Interface (From 7C00H)

    Error Description 7803h An assert has been called. Parameter 1 shows the PC. SPI interface (from 7C00h) Error Description 7C01h Buffer overflow. 7C02h Time-out error. 7C10h EEPROM write did not complete. It is still in progress. 7C11h Flash write did not complete. Cartridge Memory (from 8000h) Error Description...

  • Page 134: Fault Log Manager Section (From 8400H)

    Error Description 8011h Error bit set. 8012h Type of transponder not recognized. 8013h RF channel already opened. 8014h RF channel already closed. 8015h EOT polled to. Fault log manager section (from 8400h) Error Description 8400h Log not yet implemented. 8401h No more entries to extract.

  • Page 135: Infrastructure Section (From 8800H)

    Error Description 848Ch The command set cannot be changed while it is being read. 848Dh The data structure that contains status has an illegal value. 848Eh The specified snapshot LogSize is too small. Infrastructure section (from 8800h) Error Description 8800h Inf OnEvent: EventSet the event list is full, so the event has not been set.

  • Page 136: Critical Section (From 8C00H)

    Critical section (from 8C00h) Error Description 8C00h End section not begun. CRSEndCritIntSect was ended without CRSBegIntSect. Begin section ints off. CRSBegCritIntSect found ints already off. 8C01h SCSI module (from 9400h) Error Description 9401h Power-on reset Unit Attention. 9402h Firmware reboot after upgrade Unit Attention. 9403h SCSI bus reset Unit Attention.
  • Page 137 Error Description 9418h Invalid group code. 9419h Truncated mode page. 941Ah Invalid field mode data. 941Bh BOT encountered on space to record. 941Ch BOT encountered on to space to filemark. 941Dh Firmware bug. 941Eh Echo buffer overwritten. 941Fh REPORT DENSITY media not present. 9420h Overlapped command.
  • Page 138 Error Description 9436h Early Warning EOM encountered. 9437h Invalid field in Write buffer descriptor. 9438h Prediction threshold exceeded false failure. 9439h Prediction threshold exceeded failure. 943Ah Echo buffer invalid. 943Bh LUN not configured. 943Ch Invalid field in PR Out data. 943Dh PR Out parameter list length error in CDB.
  • Page 139 Error Description 9455h No default WWN. Used by the WWN module. 9456h No current WWN. Used by the WWN module. 9457h WWN not changed. 9458h No default value for the WWN. Used by the WWN module. Library check condition surrogate SCSI command. Used in surrogate SCSI to cause the siS- 9459h etScsiStatus to set task SCSI status to 2.
  • Page 140 Error Description 9470h Invalid Product ID. 9471h Medium removal prevented. 9472h Forward task to drive. Not a reportable error code. Logout in bad state. The Bridging Manager received notification of an ADT port Logout while 9473h waiting for TMF response to abort synchronizing PAMR command. Not reserved.
  • Page 141 Error Description 948Ah Decrypt key fail limit reached. Exhaustive search attack prevention. 948Bh Stored HAT count in NV is greater than Max HAT Retries. 948Ch Stored default Map ID for this port is invalid. Write command allocation length error. If encryption mode is set to encrypt, only 8 MB record 948Dh size is allowed.
  • Page 142 Error Description 94A7h The parameter data of a SET PREVENT MEDIUM REMOVAL command was truncated. The device server does not have sufficient recourses to process all the initiators in the para- 94A8h meter list. 94A9h SET PREVENT MEDIUM REMOVAL command not allowed when SMC LUN enabled. SET PREVENT MEDIUM REMOVAL command not allowed when an NPIV is not associated 94AAh with the SMC logical unit.

  • Page 143: Automation/Drive Interface (From 9800H)

    Error Description 94C0h A cartridge is not loaded but it has been detected in the drive. 94C1h An Automation Device Attribute Descriptor header was truncated. 94C2h The Automation Device Attribute value was truncated. 94C3h The AER Control deescriptor was truncated. The status indicates that the specified symbolic name is the same as the current symbolic 94C4h name.
  • Page 144 Error Description The ADT Port interface received a SCSI operation from a device server with an invalid Context 9810h 9811h Unable to generate a frame because it exceeds the maximum payload size. 9812h The ADT Port interface received more SCSI data than is permitted within a burst. 9813h The ADI Port interface has received a Data IU with an offset outside the current burst.

  • Page 145: Management Api (From 9C00H)

    Error Description 982Dh Invalid field in SCSI IU. 982Eh More data transferred than requested. 982Fh Task management function failed. 9830h Service delivery failed. 9831h Invalid LUN in task management IU. 9832h Failed to transmit SCSI command or Task Management Function IU. 9833h Received zero length SCSI data IU.

  • Page 146: Servo (From A000H)

    Error Description 9C08h Failure during socket write. 9C09h MgmtArm rejected the maConfigNetworkIF options. 9C0Ah Requested self-test passed. 9C0Bh Requested self-test failed. 9C0Ch Fatal condition caused the Management ARM to fail. 9C0Dh Could not queue the message, the Mailbox is full. 9C0Eh Could not allocate memory to copy an ADT frame.
  • Page 147 Error Description A008h The acceleration phase of the seek did not complete within the allotted time. A009h The deceleration phase of the seek did not complete within the allotted time. A00Ah Settle window criterion was not met at the end of the deceleration phase of the seek. A00Bh Hand-off to the tracking phase of the seek did not complete within the allotted time.
  • Page 148 Error Description The specified servo scope trigger position is too large compared with the specified number A026h of data packets in the trace. A027h The specified servo scope source address was not found in the address array. A028h The specified servo scope source bit size was not found in the size array. A029h A Measure Servo Heads command did not complete within the allotted time.
  • Page 149 Error Description A041h Live statistics servo command already in progress. A042h Seek command already in progress. A043h Report TSBs servo command already in progress. A044h Define Scope Sources servo command already in progress. A045h Configure Oscillator servo command already in progress. A046h Define Signal Nodes servo command already in progress.

  • Page 150: Certificate Manager (From A400H)

    Error Description A068h Target VI gain for use at seek destination could not be determined. A069h A defect scan is already in progress. Certificate manager (from A400h) Error Description A Root CA certificate already exists and authentication is not possible without a Management A401h Host certificate.
  • Page 151 Error Description A810h Encryption argument error. A811h Encryption failure. A812h OpenSSL initialization failure. A813h OpenSSL d2i conversion failure. A814h Buffer is too small. Volume 1: hardware integration...
  • Page 152 Drive error codes...

  • Page 153: 12 Support And Other Resources

    Manual Please contact your HP supplier for copies. • The features and benefits of HP LTO Ultrium drives are discussed in the HP LTO Ultrium Technology White Paper. • For a general background to LTO technology and licensing, go to http://www.lto-technology.com.

  • Page 154: Operation

    FC Drives SAS Drives External drives 1 HW Integration: ch. 5 In libraries 1 HW Integration: ch. 1 In servers 1 HW Integration: ch. 4 In tape arrays 1 HW Integration: ch. 3 Linux configuration 5 UNIX, Linux, OpenVMS Configuration Modes of usage 1 HW Integration: ch.

  • Page 155: Maintenance And Troubleshooting

    FC Drives SAS Drives Commands 3 Host Interface: ch. 5 Error codes 1 HW Integration: ch. 6 1 HW Integration: ch. 10 Implementation 3 Host Interface: ch. 1 Interpreting sense data 2 SW Integration: ch. 3 Messages 3 Host Interface: ch. 2 Mode pages —see the MODE 3 Host Interface: ch.

  • Page 156: Lto Ultrium Features

    1 HW Integration: ch. 8 Performance optimization 2 SW Integration: ch. 1 Performance, factors affecting 2 SW Integration: ch. 4 Software design 2 SW Integration: ch. 1 Supporting LTO Ultrium features 2 SW Integration: ch. 5 Support and other resources...

  • Page 157: General Documents And Standardization

    General documents and standardization http://www.t10.org/t10_main.htm for INCITS SCSI Primary Commands—3 (SPC-3), SCSI Streaming Commands (SSC-3) and other specifications Copies of documents of other standards bodies can be obtained from: INCITS 11 West 42nd Street New York, NY 10036-8002 USA CP 56 CH-1211 Geneva 20 Switzerland ECMA...
  • Page 158 Support and other resources...
  • Page 159 Glossary AL_PA Arbitrated Loop Physical Address. A 1-byte value used in the arbitrated loop topology used to identify L_ports. This value will then also become the last byte of the address identifier for each public L_port on the loop. The AL_PA can be set through an ACI Set Drive Configuration command.
  • Page 160 compression A procedure in which data is transformed by the removal of redundant information in order to reduce the number of bits required to represent the data. compression ratio A measure of how much compression has occurred, defined as the ratio of the amount of uncompressed data to the amount of compressed data into which it is transformed.
  • Page 161 topology. It allows for an active intelligent interconnection scheme, called a fabric, to connect devices. All a Fibre Channel port has to do is to manage a simple point-to-point connection between itself and the fabric. Several common ULPs (Upper Level Protocols) including IP and SCSI can be used with Fibre Channel, merging high-speed I/O and network functionality in a single connectivity technology.
  • Page 162 online The drive is online when a tape is loaded. The host has access to all command operations, including those that access the tape, set configurations and run diagnostic tests. point-to-point A Fibre Channel topology in which two points communicate directly. port An access point in a device to which a link attaches.
  • Page 163 TapeAlert A set of 64 flags is held in the TapeAlert log that indicate faults or predicted faults with the drive or the media. By reading this log, host software can inform the user of existing or impending conditions, and can, for example, advise the user to change the tape.
  • Page 164 Glossary...
  • Page 165 Index cartridge memory, 45, 67, ACI, 67, 69, access via ACI, connector, 31, error codes, connector pins, problems with, controlling loads, cartridges, error codes, jammed, reset, life, addresses, fibre channel, loading, ADI, not ejected, pin layout, positions during load and unload, ADT, problems with, airflow,...
  • Page 166 direct fabric attach, FC_SW, DLT cartridges, FCP, documents, related, fibre channel, drive addressing, arbitrated loop, not recognized, 62, fabric loop attach, Drive Error LED, generic service, drive monitor error codes, ports, drives switched fabric, control error codes, fibre channel connector, error codes, filemarks, filtering,...
  • Page 167 installing drives online, in libraries, operating drives, internal, operating system error codes, internal drives optimizing performance, reset switch, ISO, physical formatter error codes, physical pipeline control error codes, L_port, pins labeling cartridges, ACI connector, LEDs, ADI connector, front panel, point-to-point, rear panel, port LEDs, libraries,...
  • Page 168 self-test failure, serial numbers external drives, internal drives, server installing drive in, Servo, error codes, software, backup, SPI interface error codes, storage area network, storing cartridges, switched fabric, system architecture error codes, system configurations, system performance, tape arrays airflow, installing drives, replacing a drive, Tape Error LED, tape libraries see libraries,...

This manual is also suitable for:

Lto ultrium 5

Table of Contents