Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or
for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied,
reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information is provided
“as is” without warranty of any kind and 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. HP shall not be liable for technical or editorial errors or omissions contained herein.
Printing history
VersionEditionDateChanges
LTO 4Edition 1June 2007LTO4 FC, SCSI and SAS version
This document is frequently revised and updated. To find out if there is a later version, please ask your HP OEM Representative.
In libraries
In servers
In tape arrays
Linux configuration
Modes of usage
OpenVMS configuration
Optimizing performance
UNIX configuration
Operation
External drives
In libraries
In servers
In tape arrays
Cartridges
FC DrivesSCSI DrivesSAS Drives
1 HW Integration: ch. 1
n/a1 HW Integration: ch. 4
n/a1 HW Integration: ch. 3n/a
5 UNIX, Linux, OpenVMS Configuration
n/a1 HW Integration: ch. 8n/a
5 UNIX, Linux, OpenVMS Configuration
n/a1 HW Integration: ch. 8n/a
2 SW Integration: ch. 4
5 UNIX, Linux, OpenVMS Configuration
FC DrivesSCSI DrivesSAS Drives
n/a1 HW Integration: ch. 5
1 HW Integration: ch. 1
n/a1 HW Integration: ch. 4
n/a1 HW Integration: ch. 3n/a
Cartridge Memory (LTO-CM)
Cartridges
Managing the use of cartridges
Use of cartridges
Interface
FC, SCSI and SAS host interface guide
Commands
Error codes
Implementation
Interpreting sense data
Messages
Mode pages
—see the MODE SENSE command
10
FC DrivesSCSI DrivesSAS Drives
2 SW Integration: ch. 5
1 HW Integration: ch. 51 HW Integration: ch. 9
2 SW Integration: ch. 1
2 SW Integration: ch. 3
FC DrivesSCSI DrivesSAS Drives
3 Host Interface
3 Host Interface: ch. 5
1 HW Integration: ch. 61 HW Integration: ch. 10
3 Host Interface: ch. 1
2 SW Integration: ch. 3
3 Host Interface: ch. 2
3 Host Interface: ch. 5
HP restricted
Pre-execution checks
Responding to sense keys and ASC/Q
Sense keys and ASC/Q
—see REQUEST SENSE command
Task management functions
Maintenance and troubleshooting
Cleaning
External drives
In libraries
In servers
In tape arrays)
Monitoring drive and tape condition
Software troubleshooting techniques
Dealing with errors
FC DrivesSCSI DrivesSAS Drives
3 Host Interface: ch. 4
2 SW Integration: ch. 6
3 Host Interface: ch. 5
n/a3 Host Interface: ch. 3
FC DrivesSCSI DrivesSAS Drives
2 SW Integration: ch. 5
2 SW Integration: ch. 7
n/a1 HW Integration: ch. 5
1 HW Integration: ch. 1
n/a1 HW Integration: ch. 4
n/a1 HW Integration: ch. 3n/a
2 SW Integration: ch. 7
2 SW Integration: ch. 1
Error codes
Handling errors
Logs—see the LOG SENSE command
Recovering from write and read errors
Software response to error correction
Software response to logs
TapeAlert log
LTO Ultrium features
Autoload
Automation Control Interface (ACI)
Cartridge Memory (LTO-CM)
Data compression, managing
OBDR and CD-ROM emulation
Performance, factors affecting
Software design
Supporting LTO Ultrium features
General documents and standardization
See 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:
2 SW Integration: ch. 1
2 SW Integration: ch. 4
2 SW Integration: ch. 1
2 SW Integration: ch. 5
INCITS
ISO
ECMA
Global Engineering
Documents
11 West 42nd Street
New York,
NY 10036-8002
USA
CP 56
CH-1211 Geneva 20
Switzerland
114 Rue du Rhône
CH-1204 Geneva
Switzerland
2805 McGaw
Irvine, CA 92714
USA
Tel: +41 22 849 6000
Web URL: http://www.ecma.ch
Tel: 800 854 7179 or 714 261 1455
12
HP restricted
1Interface Implementation
HP LTO Ultrium drives use Fibre Channel, parallel SCSI or Serial Attached SCSI (SAS) as the
interface to connect to the host system.
This chapter gives an overview of how the interface operates.
Full details of the messages are given in Chapter 2, of SAS response frames and task management
functions in Chapter 3, and of commands in Chapter 4 and Chapter 5.
The Fibre Channel interface
Fibre Channel is an industry standard, approved by the American National Standards Institute
(ANSI). You are recommended to read the ANSI standard documents in conjunction with this
manual. The ANSI specifications define the interface in general while this document describes the
HP LTO Ultrium implementation.
The Fibre Channel implementation provides a drive with a standard set of features and functions.
These include the following:
• Implementation of all mandatory and most optional commands of the Sequential Access
command set
• 4 Gbps serial transfers with auto-negotiation to 2 Gbps and 1 Gbps speeds
• Dual port capability
• Conformance to the following SCSI standards:
•FC-PI ANSI INCITS 352-2002
• FC-FS ANSI INCITS 373-2003
• FC-FLA ANSI INCITS TR-20-1998
• FC-AL-2 ANSI INCITS 332-1999
• FCP-2 ANSI INCITS 350-2003
• FC-TAPE ANSI INCITS TR-24-1999
• In addition to the standards listed above the following generic SCSI standards apply.
• SAM-2 ANSI INCITS 366-2003
• SPI-4 ANSI INCITS 362-2002
• SPC-3 ANSI INCITS 408-2005
•SSC-2 ANSI INCITS 380-2003
Supported task management functions
The following task management functions are supported by the drives:
For implementation details on these, see Chapter 3, “Response frames and task management
functions”.
The SCSI interface
The Small Computer System Interface (SCSI) is an industry standard, approved by the American
National Standards Institute (ANSI). You are recommended to read the ANSI standard document in
conjunction with this manual. The ANSI specification defines the interface in general while this
document describes the HP LTO Ultrium implementation.
The SCSI implementation provides a drive with a standard set of features and functions. These
include the following:
• Synchronous data transfers
• Asynchronous data transfers
• Implementation of all mandatory and most optional commands of the Sequential Access
command set
• LVD (Low-Voltage differential) SCSI connection
• Ultra-320 wide SCSI
• Conformance to the following SCSI standards:
• SAM-2 ANSI INCITS 366-2003
• SPI-4 ANSI INCITS 362-2002
• SPC-3 ANSI INCITS 408-2005
• SSC-2 ANSI INCITS 380-2003
Supported messages
The following messages are supported by the drives:
• ABORT
• BUS DEVICE RESET
• COMMAND COMPLETE
• DISCONNECT
• IDENTIFY
• IGNORE WIDE RESIDUE
• INITIATOR DETECTED ERROR
• MESSAGE PARITY ERROR
• MESSAGE REJECT
• NO-OP (no operation)
• PARALLEL PROTOCOL REQUEST (PPR)
• RESTORE POINTERS
• SAVE DATA POINTER
• Extended Message: PARALLEL PROTOCOL REQUEST
• SYNCHRONOUS DATA TRANSFER REQUEST
• WIDE DATA TRANSFER REQUEST
Interface Implementation14
HP restricted
For implementation details on these messages, see Chapter 2, “Messages”
The SAS interface
Serial Attached SCSI (SAS) is an industry standard, approved by the American National Standards
Institute (ANSI). You are recommended to read the ANSI standard documents in conjunction with
this manual. The ANSI specifications defines the interface in general while this document describes
the HP LTO Ultrium implementation.
The SAS implementation provides a drive with a standard set of features and functions. These
include the following:
• Implementation of all mandatory and most optional commands of the Sequential Access
command set
• SAS1.1 compliant interface
• 3 Gbps serial transfers
• Dual port capability
• Conformance to the following SCSI standards:
• SAM-2 ANSI INCITS 366-2003
•SAS1.1 T10/1601-D revision 10
• SPC-3 ANSI INCITS 408-2005
• SSC-2 ANSI INCITS 380-2003
Supported task management functions
The following task management functions are supported by the drives:
• ABORT TASK
• ABORT TASK SET
• CLEAR TASK SET
• LOGICAL UNIT RESET
• QUERY TASK
For implementation details on these, see Chapter 3, “Response frames and task management
functions”
Supported commands
The following commands are supported by the drives. They include all Mandatory and Extended
commands and most Optional commands.
A4h (1Fh) Enh.
A4h (1Fh) Enh. FW UPGRADE REBOOT57h/17h RELEASE UNIT
A3h (1Fh) Enh. FW UPGRADE REPORT IMAGE INFO03hREQUEST SENSE
C2hENABLE TLRS(SAS drives only)44hREPORT DENSITY SUPPORT
19hERASEA3h (05h) REPORT DEVICE IDENTIFIER
12h
LOG SENSE
MODE SELECT
MODE SENSE
PERSISTENT RESERVE IN
PERSISTENT RESERVE OUT
PREVENT/ALLOW MEDIUM REMOVAL
READ
READ 6 (CD-ROM mode)
READ 10 (CD-ROM mode)
READ ATTRIBUTE
READ BLOCK LIMITS
READ BUFFER
READ CAPACITY (CD-ROM mode)
READ LOGGED-IN HOST TABLE (FC and SAS only)
READ MEDIA SERIAL NUMBER
READ POSITION
READ TOC (CD-ROM mode)
A3h (0Ch)
A3h (0Ch)
A3h (0Dh)
56h/16h
01h
A2h
B5h
2Bh
1Dh
0Bh
A4h (06h)
11h
91h
1Bh
00h
13h
0Ah
8Dh
3Bh
10h
REPORT TARGET PORT GROUPS
REPORT SUPPORTED OP CODES
REPORT SUPPORTED TASK
MNGMNT FUNCTNS
RESERVE UNIT
REWIND
SECURITY PROTOCOL IN
SECURITY PROTOCOL OUT
SEEK (CD-ROM mode)
SEND DIAGNOSTIC
SET CAPACITY
SET DEVICE IDENTIFIER
SPACE (6)
SPACE (16)
START/STOP UNIT (CD-ROM mode)
TEST UNIT READY
VERIFY
WRITE
WRITE ATTRIBUTE
WRITE BUFFER
WRITE FILEMARKS
For implementation details on these commands, see Chapter 4, “Commands—introduction” and
Chapter 5, “Commands”.
SCSI features
Design approach
The features supported by the drive are based on standards, both official and de facto. The drive is
fully compliant with the current SCSI standards: SPC3, SSC2, SAM2, and the relevant transport
protocol (such as SPI4 for SCSI drives, SAS1.1 for SAS drives). All mandatory commands and
features are supported, as well as some that are optional. In addition, some features from older
standards are still supported for backwards compatibility.
Power-on
The drive will respond to INQUIRY, TEST UNIT READY, REPORT LUNS and REQUEST SENSE commands
within 250 ms of power on for SCSI and SAS drives. For FC drives, the response time depends on
whether the drive is standalone or operating within a library. Standalone could take up to 3
seconds, and if the drive is in a library, there would be an additional library initialization time on
top of this.
Interface Implementation16
HP restricted
The first command received from an initiator (other than INQUIRY, REQUEST SENSE and REPORT LUNS)
will result in
Once the drive has completed its self-test and set-up procedures, it will attempt to reload any tape
that is already present in the drive. It may take some time to recover the tape, especially if it was
positioned near EOM when power was cycled. During tape recovery, medium access commands
will result in a sense key of
becoming ready).
Reset strategy
The drive supports reset as follows:
• The current I/O process is aborted
• Any queued I/O processes from other initiators are removed
• SCSI drives only: All negotiated settings are cleared
• Mode parameters that do not relate to ADI and port enablement are cleared to their default
values
• Any reservations are cleared (but not persistent reservations)
• Any buffered writes are flushed to tape
• The logical position becomes undefined, unless Rewind-On-Reset has been configured in which
case the drive will rewind to BOM
• A
UNIT ATTENTION condition is set, based on the type of reset
CHECK CONDITION status, with UNIT ATTENTION sense data reported for the power on.
NOT READY, with additional sense of 0401h (drive in process of
SCSI drives will respond to
250 ms of the reset line being released. The first command from any initiator (other than
REQUEST SENSE and REPORT LUNS) will result in CHECK CONDITION status with UNIT ATTENTION
sense data for the reset.
NOTE: SCSI drives: All commands will receive BUSY status until the drive has completed its internal
reset.
The Reset button on the front panel and the ACI_RESET_L line on the Automation Controller Interface
are both connected to the Power-Up Reset interrupt on the processor. The effect is equivalent to
power-cycling the drive. The contents of the tape and cartridge memory may not be consistent after
the action and any data in the drive buffer will be lost.
Abort handling
SCSI drives
If an abort condition is detected before a command phase completes, the bus is set to bus free and
the command is not executed.
If an abort condition is detected between the end of the command phase and the start of the status
phase, the bus is set to bus free and the processing below is carried out as listed in Table 1.
If an abort condition is detected during status phase, the bus is set to bus free.
INQUIRY, TEST UNIT READY, REPORT LUNS and REQUEST SENSE within
If a command (other than INQUIRY for standard data or REQUEST SENSE) is received after the abort
but before the drive is ready to process the command, the behavior depends on whether
Disconnects are allowed.
• If disconnects are allowed, the drive will disconnect and wait until the abort processing has
completed before executing the command.
• For SCSI drives, if disconnects are not allowed, a
BUSY response will be returned.
All interfaces
If an abort condition is detected, it will be processed as listed in Table 1.
Table 1 Abort processing
CommandAbort Processing
ERASELong erase is aborted as quickly as possible without corrupting the
tape format. Short erase completes.
INQUIRYNone
LOAD/UNLOADLoad completes and logically positions the tape at BOT.
Unload is aborted leaving the logical position at BOT unless the
operation is past the “point of no return” in which case the tape is
ejected.
LOCATEThe logical position is set back to that at the start of the operation.
LOG SELECTIf data transfer is complete, the command is completed, otherwise
no action is taken
LOG SENSENone
MODE SELECTIf data transfer is complete, the command is completed, otherwise
no action is taken.
MODE SENSENone
PREVENT/ALLOW
MEDIUM REMOVAL
READThe logical position is set to that at the start of the operation.
READ BLOCK LIMITSNone
READ BUFFERNone
READ POSITIONNone
RECEIVE DIAGNOSTICS
RESULTS
RELEASE UNITThe command completes.
REQUEST SENSESense data is discarded.
RESERVE UNITThe command completes.
REWINDThe command completes.
SEND DIAGNOSTICIf data transfer is complete, the command is completed, otherwise
The command completes.
None
no action is taken
Interface Implementation18
HP restricted
CommandAbort Processing
SPACEThe logical position is set back to that at the start of the operation.
TEST UNIT READYNone
WRITEThe logical position is set back to that at the start of the operation.
WRITE BUFFERIf data transfer is complete, the command is completed, otherwise
no action is taken.
WRITE FILEMARKSThe logical position is set back to that at the start of the operation
VERIFYThe logical position is set back to that at the start of the operation
LUN identification (SCSI only)
Identify messages are used to identify the LUN being addressed by the initiator, and to identify
which LUN is reselecting the initiator. The old LUN field in the CDB from the SCSI-2 standards is
obsolete and should not be used (set to 0).
Bus parity or CRC errors (SCSI only)
If the drive detects a bus parity error in a message out or command phase, it will still accept the
command, which will then return
Detection of a parity error during the data out phase also causes the drive to return
CONDITION
mode or 4700h if not.
If Information Units is enabled (SCSI only), the drive will drop the bus on detecting a CRC error
during a LQ_IU. If the CRC error occurs during the Information Units command phase or data out
phase, the drive will return
(Information Unit CRC error detected).
. Additional sense is set to 4701h (data phase CRC error detected) if the bus is in DT
CHECK CONDITION. Additional sense is 4700h (SCSI parity error).
CHECK CONDITION with a CRC error. Additional sense is set to 4703h
CHECK
On detecting an Initiator Detected error, the drive will return
sense of 4800h (initiator detected error message received). The exception is when Information Units
mode is enabled (SCSI only), when one of the following occurs:
• If an IDE message is received during a LQ_IU, the drive drops the bus and retries the LQ_IU pair.
• If the message is received during Status IU, the drive retries the LQ_Status pair.
• If the message is received during Data IU, the drive sends a LQ_Status with
and additional sense of 4800h.
Disconnect strategy (SCSI only)
The disconnect strategy used by the drive is based on maximizing the use of the bus for large
sequential data transfers from a large data buffer. The drive will disconnect whenever it believes that
it will provide better bus use. This may be between command and data phases, between bursts of
data or before sending status. However, the drive will guarantee that it sends the configured
maximum burst size or the remaining data in the transfer in any single data phase burst if the
maximum burst size has been set to a value other than zero.
The following diagram gives an overview of the drive’s disconnect strategy:
CDB arrives
Yes
REQUEST SENSE from
an initiator in CA or
INQUIRY with EVPD=0
No
Disconnect
priv granted
Yes
DisconnectSend data
No
Reselect
Data transfer
required?
No
No
Yes
ReselectExecute cmd
Transfer data &
execute cmd
Previous cmd
still in progress?
Yes
Send status
Cmd complete
Send status
Cmd complete
Link error handling (SAS drives)
In normal operation, random errors will occasionally be encountered on the link between the
initiator and the tape drive. A single bit error may result in a frame with a bad CRC value, or in a
communication failure if the error corrupts one of the special “primitive” messages used to manage
the link. The SAS standard provides an optional mechanism to retry most link errors; this mechanism
is known as Transport Layer Retries. See ”Protocol-Specific Logical Unit mode page (SAS drives)” on
Interface Implementation20
Send BUSY
status
Cmd complete
HP restricted
page 108. By default the tape drive has retries disabled; an initiator which is also capable of
handling retries must enable them in the tape drive typically during the discovery phase.
The following table indicates the drive behavior both with and without transport layer retries
enabled, for a variety of possible error scenarios:
Error TypeBehavior
Transport Layer Retries DisabledTransport Layer Retries Enabled
Data frame CRC error on
writes
The drive sends NAK.
The initiator aborts the command using
the ABORT task management
functions.
The drive sends NAK.
The initiator restarts data
transfer with the Changing
Data Ptr bit set for the first
resent frame.
Data frame CRC error on
reads
The initiator sends NAK.
The drive aborts the command with a
sense key of
ABORTED COMMAND and
additional sense of 4B04h (NAK
The initiator sends NAK, drive
restarts transfer from start of
burst with Changing Data Ptr
bit set for 1st resent frame
received).
XFER_RDY frame CRC
error
The initiator sends NAK.
The drive aborts the command with a
sense key of
ABORTED COMMAND and
additional sense of 4B04h (NAK
The initiator sends NAK.
The drive re-issues
XFER_RDY
with the Retransmit bit set and a
fresh TPTT value.
received).
Response frame CRC
error
The initiator sends NAK.
The drive re-sends the response frame
with the Retransmit bit set
The initiator sends NAK.
The drive re-sends the response
frame with the Retransmit bit
set.
Loss of ACK for a write
data frame
Loss of ACK for read
data frame
The initiator times out the operation
and sends an
ABORT task management
function.
The drive times out the operation and
aborts the command with a sense key
of
ABORTED COMMAND and
additional sense of 4B03 (ACK/NAK
Timeout).
The drive completes the
operation (since all data was
received successfully) and sends
GOOD status.
The drive times out the
operation, then restarts the
transfer from the start of the
burst with the Changing Data
Ptr bit set for the first resent
frame.
All drives are design to operate within a multi-initiator environment. The maximum number of
concurrently connected initiators is:
• FC drives: 255, shared across both ports
• SCSI drives: 15
• SAS drives: 32, shared across both ports
Sense Data, Unit Attention and Deferred Errors are maintained for each initiator. Mode Parameters
are common to all initiators.
The untagged queuing model implemented by the drives guarantees that all commands are
executed in strict order of receipt. Certain non-media access type commands, such as
READY
, INQUIRY, REQUEST SENSE and REPORT LUNS, are implicitly allowed to queue-jump other
media access type commands, such as
Transport Layer Retries DisabledTransport Layer Retries Enabled
The drive times out the operation and
aborts the command with a sense key
of
ABORTED COMMAND and
additional sense of 4B03 (ACK/NAK
Timeout).
The drive times out the operation, then
re-sends the response frame with the
Retransmit bit set.
REWIND.
The drive times out the
operation, then re-issues
XFER_RDY with the Retransmit bit
set and a fresh TPTT value.
The drive times out the
operation, then re-sends the
response frame with the
Retransmit bit set.
TEST UNIT
The SCSI drive supports the full command queuing model with a queue depth of 1 (SCSI drives,
necessary for connectivity purposes) or 4 (FC drives). See “Standard Inquiry Data format (LUN0)”
on page 51 for details of the BQue and CmdQue bits which define this support.
Fibre Channel operation
The following sections have information specific to Fibre Channel operation:
• “Protocol-Specific Logical Unit mode page (FC drives)” on page 107
• “Protocol-Specific Port mode page (FC drives)” on page 108
• “Vital Product Data pages” on page 55
Fibre Channel addressing
Before describing HP’s implementation of Fibre Channel addressing, the concepts of Names and
Addresses need to be clarified.
Names
Names are 64-bit identifiers assigned permanently to the tape drive during manufacture. They are
commonly referred to as World Wide Names since they must be guaranteed unique. The names are
Interface Implementation22
HP restricted
typically used for identifying the device to operating systems, since addresses are assigned
dynamically. One of the principal uses for WWNs in Storage Area Networks is to enable the
division of fabrics into separate zones for security, load balancing, redundancy or manageability
purposes.
There are at least eight different name formats distinguished by the Network Address Authority
(NAA). Only one is used on HP LTO Ultrium drives. This is the IEEE Registered Name (NNA=5) and
has the following format:
• IEEE Company ID (24 bits). Assigned by IEEE to the company.
• Vendor Specified ID (36 bits). Assigned by the company.
Addresses
Each Fibre Channel port also has a Port Address which is assigned during loop initialization
and/or Fabric Login. This is a 24-bit value in the following format:
2316
The AL_PA is the Arbitrated Loop Physical Address. This is normally assigned dynamically during
loop initialization.
If the drive is on a loop that is not attached to a fabric (in other words, when it is on a private link),
the top two bytes will be zero. If the loop is attached to a fabric, the top two bytes are assigned
when it logs into the fabric.
byte 0
31
NAA=5
24
byte 1byte 2byte 3
2316
IEEE Company ID (24 bits)
Vendor Specified ID (36 bits)
byte 1byte 2byte 3
Domain
Addess
15
Area
Addess
7
8
Port or AL_PA
Addess
7
15
8
0
VSID
0
Together, the three bytes provide a unique address on the Fibre Channel fabric that is used for frame
addressing. It forms the equivalent of the Target ID or Initiator ID in SCSI.
HP’s implementation of names and addresses
The HP implementation uses three adjacent IEEE Registered Names:
• The first (last bits = 00) is used as the Port A World Wide Name.
• The second (last bits = 01) is used as the Port B World Wide Name.
• The third name (last bits = 10) is used for the Device World Wide Name.
(These are assigned during manufacture from HP’s pool of names, although only the first will
actually be stored in the drive NV-RAM).
Port A
IEEE Registered Name
(last bits = 00)
Port Address A
Port B
IEEE Registered Name
(last bits = 01)
Port Address B
On LTO 4 drives there are two further WWNs, the SCSI Device WWN (typically set equal to the
Node WWN) and the ADC Device WWN (last bits = 11)
The values of the names can be obtained using the Device Identification Vital Product Information
Page (part of the
Implications for libraries
• Normally a standalone drive will operate using its own factory-programmed ‘hard’ names.
• The drive knows it is in a library or other ‘managed’ environment since one of the signal lines on
the Automation Interface) will be tied down. In this guide, the term “Automation Interface” covers
both ACI (Automation Control Interface) and ADI (Automation/Drive Interface).
In this case, the drive will not go on the FC loop or connect to the fabric until it is told to. The
library can optionally download new soft names (Port A, Port B and Node Name) into the drive
at this point. The drive will then use this as the origin of its names. The library manufacturer
would be responsible for obtaining this IEEE Registered Name. It would be a property of the
library, not the drive.
• If the library wants to ‘warm swap’ drives, it can. It just ‘turns off’ the drive with the soft name
using the ACI and then turns on the spare drive, downloading the same name to it.
• If a drive is removed from the library, it will not have the ACI signal tied low and so will revert to
its original hard name. It should forget the soft name in this case.
• If the library controller breaks, the drive will time out the ACI interface in ~10 seconds. The drive
still knows it is in a library since the ACI signal is still tied low, so in this case it will use the soft
name last downloaded. This will allow drive access without confusing the host.
INQUIRY command).
Device
or Node
IEEE Registered Name
(last bits = 10)
Field replaceable units
An FRU code identifies which part of the hardware is considered to have failed. These codes turn up
in sense data byte 14 and as the sense code qualifier for sense codes 4400h (internal target
failure) and 40XX (diagnostic failure).
Interface Implementation24
HP restricted
Although there are no actual Field Replaceable Units on HP LTO Ultrium drives, the following
sub-assemblies can be replaced at Repair Centres:
• Drive PCA• Head Assembly
• Mechanism• Front Panel
CD-ROM emulation (SCSI and SAS drives only)
The One Button Disaster Recovery (OBDR) functionality in HP LTO Ultrium drives enables them to
emulate CD-ROM devices in specific circumstances (also known as being in “Disaster Recovery”
mode). The drive can then act as a boot device for PCs that support booting off CD-ROM.
A CD-ROM capable drive can be switched into CD-ROM mode by powering on with the eject
button held down. The drive then alters its behavior as follows:
• The front panel lights flash a “warbling” sequence.
• CD-ROM commands are executed (as opposed to tape drive mode when they would be
rejected). Commands specific to CD-ROM mode are
the case of SCSI commands 08h (
interpreted as CD-ROM commands 08h (
READ), 1Bh (LOAD/UNLOAD) and 2Bh (LOCATE), these are
READ 6), 1Bh (START/STOP) and 2Bh (SEEK) respectively.
• Writing is disabled.
• Normal
INQUIRY data is modified to add a field indicating that the drive supports CD emulation
and to switch the peripheral device type field to indicate a CD-ROM drive.
• The mode header and mode block descriptor are modified.
• A CD-Emulation mode page is added.
• Mode data changes to reflect CD-ROM medium type and block size.
• Status reporting by the media access check is altered.
• The drive’s sense data when the media is not ready for access always indicates “loading”.
READ 10, READ TOC and READ CAPACITY. In
If a tape is inserted while the drive is in CD-ROM mode, the drive assumes that it will contain an
image of a CD offset 20 blocks into the tape. It reads the first 250 kilobytes of this image into buffer
space reserved for CD-caching. It then looks for a special message (“
SPECIFICATION
”) at the 8th byte of the 18th record of the image. If the drive fails to find this
EL TORITO
message, it ejects the tape and waits in CD-ROM mode for a properly-written CD-image tape to be
inserted.
The drive will remain in CD-emulation mode until one of the following occurs:
• A
MODE SELECT command switches it back to tape drive mode using the CD-emulation mode
page.
• SCSI drives only: A SCSI bus reset occurs following the reading of at least 100 blocks of
CD-ROM data by a host.
• SAS drives only: A Logical Unit Reset task management function or a HARD_RESET primitive
sequence is received, following the reading of at least 100 blocks of CD-ROM data by a host.
• The user power-cycles the drive or resets it using the forced-eject mechanism.
NOTE: If the drive exits CD-ROM mode through either of the first two of these, the tape will remain
at the last logical position when in CD-ROM mode.
Interface Implementation26
HP restricted
2Messages
Message Out support (SCSI only)
NameCode Support
Abort06hAn abort condition is generated (see “Abort handling” on
page 17).
Bus Device Reset0Ch A reset condition is generated (see “Reset strategy” on page 17).
Extended Message01h See “Extended Message Support” below.
Identify80h+ The Identify Out message is sent by the initiator to identify the
Logical Unit to be accessed and to set Disconnect Privilege.
Initiator Detected
Error
Message Parity
Error
Message Reject07hThis message is sent when the initiator does not support a
No Operation08h This message has no effect and is ignored.
05h The initiator has detected an error in the data being sent in a
Command, Data or Status phase. The drive will send a restore
data pointers message to retry the data transfer. (See “Message
In support (SCSI only)” below for details).
If the message is received immediately after an Identify message
or after the Command Complete message has been sent, the
drive will go Bus Free.
09h The initiator has detected a parity error in a message. The drive
will retry the message. (See “Message In support (SCSI only)”
below for details).
If the message is received immediately after an Identify message
or after the Command Complete message has been sent, the
drive will go Bus Free.
message sent by the drive or that the message is inappropriate. If
the message being rejected is Disconnect, Synchronous Data
Transfer Request or Wide Data Transfer Request, the operation
continues without those features. For all other messages, the
message is treated as an Abort message.
If the message is received during a Command, Data or Status
phase, immediately after an Identify message or after the
Command Complete message has been sent, the drive will go
Bus Free.
NameCode Support
Command Complete00hThis message is sent by the drive at the end of the status phase
Disconnect04hThis message is sent by the drive to indicate that it is about to
Extended Message01hSee “Extended Message Support” below.
Identify8XhThe Identify In message is sent to the initiator during reconnect
Ignore Wide Residue23hThis message is sent by the drive to the host to indicate that a
Message Reject07hThis message is sent to the initiator when the message received
Restore Pointers03hThis message causes the initiator to reset its data transfer
Save Data Pointers02hThis message instructs the initiator to save its current data
to indicate that a command is complete. Once the message is
sent, the drive releases the bus and goes to Bus Free.
disconnect from the bus and go to Bus Free. During a Data
phase, it is always pre-ceded by a Save Data Pointers
message. If a Message Reject message is received in response
to this message, then the disconnect is prevented.
to indicate which Logical Unit is reconnecting.
byte on a wide bus is not valid.
This is supported whenever a wide transfer is active. It should
be sent at the end of the data phase. The standard action of
the drive is to send this message between the data phase and
the status phase with no disconnect.
by the drive is unsupported or inappropriate.
pointers to the values they held when the last save data
pointers message was sent. It will be sent when a parity error is
detected on the bus or when an Initiator Detected Error
message is received in order to retry the data phase.
transfer pointers for use with a subsequent Restore pointers
message. This message will always be sent before a
Disconnect message during data phases.
Messages28
HP restricted
Extended Message support (SCSI only)
NameCode Support
Synchronous Data
Transfer Request
Wide Data Transfer03hThe drive can initiate a Wide data transfer negotiation. If the
01hThe drive can initiate a Synchronous data transfer negotiation. If
the message is received after selection and before the command
phase, it will then go to message-in phase and respond with a
valid response to complete the negotiation.
message is received after selection and before the command
phase, it will then go to message-in phase and respond with a
valid response to complete the negotiation.
Note that SDTR negotiated parameters will become
asynchronous after a WDTR.
04hThe drive will never initiate a Parallel Protocol Request transfer
negotiation but will expect the initiator to do so.
If the message is received after selection and before the
command phase, it will then go to message-in phase and
respond with a valid response to complete the negotiation.
Req/Ack OffsetThis has a maximum value of 255.
Transfer Width
Exponent
PComp_EnPrecompensation enable bit. Supported.
RTIRetain Training Information bit. Supported.
Rd_Strm0Read streaming and read flow control enable bit. Not supported, so the
Wr_Flow0Write flow control enable bit. Not supported; the drive will always return
Hold_MCS0Hold Margin Control Settings bit. Not supported; the drive will always
QAS_Req0QAS enable request bit. Not supported; the drive will always return zero.
DT_ReqThis bit determines whether DT mode has been requested, in other words,
IU-ReqInformation units enabled request bit. Supported.
08h Transfer period of 6.25 ns, Paced Information Unit transfers
09h Transfer period of 12.5 ns (FAST-80). Only valid when DT transfers have
been requested
0Ch Transfer period of 50 ns (FAST-20) — LVD/SE drives only
19h Transfer period of 100 ns (FAST-10)
32h Transfer period of 200 ns (FAST-5)
For ST transfers, this can be either 0 (Narrow) or 1 (Wide).
For DT transfers, it must be set to 1.
drive will always return zero.
zero.
return zero.
packetized data transfers. Supported.
Status
Messages30
A Status byte is sent from the drive to the host during the Status phase at the end of each command
as specified in the SCSI specification, unless the command has been cleared by an
by a
BUS DEVICE RESET message, or by a hard reset.
HP restricted
ABORT message,
Loading...
+ 224 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.