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
Page 11
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
Page 13
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
Page 15
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
Page 17
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
Page 19
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 21
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
Page 23
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
Page 25
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
Page 27
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
Page 29
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,
Page 31
The Status bytes that the drive returns are as follows:
00hGOOD: The drive has successfully completed the command.
02hCHECK CONDITION: Any error, exception, or abnormal condition that causes sense data
to be set returns
CHECK CONDITION. The REQUEST SENSE command should be sent
following this status to determine the nature of the error.
04h CONDITION MET: Never returned by an HP LTO Ultrium tape drive.
08hBUSY: The drive is unable to execute the command at this time. Try again later. The drive
tries to avoid using this status code during normal operation. It can sometimes be used
after commands have been aborted, during power-on and if there are multiple selecting
initiators.
10h INTERMEDIATE: Never returned by an HP LTO Ultrium tape drive.
14h INTERMEDIATE CND: Never returned by an HP LTO Ultrium tape drive.
18hRESERVATION CONFLICT: The drive is reserved by another party. See the Reservation
check.
22h COMAND TERMINATED: Never returned by an HP LTO Ultrium tape drive.
28h QUEUE FULL
40hABORTED COMMAND
This section describes the format of SAS response frames returned by HP LTO Ultrium tape drives.
Response frames provide a way for the drive to report the outcome of all SCSI commands and task
management functions:
76543210
0–9Reserved (0)
10Reserved (0)DATAPRES
11Status
12–15Reserved (0)
16(MSB)
19(LSB)
20(MSB)
23(LSB)
24
23+
m
24+
m
23+
m+n
Sense Data Length (n bytes)
Response Data Length (m bytes)
Response Data (if any)
Sense Data (if any)
DATAPRESSpecifies the format and content of the Status, Sense Data Length, Response
Data Length, Response Data, and Sense Data fields:
Code NameDescription
NO_DATA
00b
RESPONSE_DATA
01b
SENSE_DATA
10b
11b Reserved
StatusThe Status byte is valid for all response frames, unless the
set to
RESPONSE_DATA. It indicates the outcome of the SCSI command:
Neither response data nor sense data are present
Response data is present
Sense data is present
DATAPRES field is
The drive has successfully completed the
command.
Any error, exception, or abnormal condition that
causes sense data to be set returns
CONDITION
should be sent following this status to determine
the nature of the error.
Never returned by an HP LTO Ultrium tape drive.
. The REQUEST SENSE command
CHECK
Page 34
08h
10h
14h
18h
22h
28h
30h
40h
Response DataIf the
fields are not valid; the drive is reporting a response to a task management
function or to an invalid request as indicated by the response code:
Code Description
00h Task management function complete
02h Invalid frame
04h Task managements function not supported
05h Task management function failed
08h Task management function succeeded
09h Incorrect Logical Unit Number
0Ah Overlapped tag attempted
All other codes are reserved.
a
Only valid when responding to a TASK frame.
b
Returned when a command/task management function or task
management function/task management function tag conflicts.
BUSY
The drive is unable to execute the command at this
time. Try again later. The drive tries to avoid using
this status code during normal operation. It can
sometimes be used after commands have been
aborted, during power-on and if there are multiple
selecting initiators.
INTERMEDIATE
INTERMEDIATE CND
RESERVATION
CONFLICT
COMMAND
TERMINATED
TASK SET FULL
Never returned by an HP LTO Ultrium tape drive.
Never returned by an HP LTO Ultrium tape drive.
The drive is reserved by another party. See the
Reservation check.
Never returned by an HP LTO Ultrium tape drive.
The drive cannot accept another task at the
moment because the internal limit has been
reached. Try again later.
ACA ACTIVE
Typically not returned by an HP LTO Ultrium drive
but may be in some circumstances; for example,
on a Fibre Channel drive, if Host A sends Logical
Unit Reset then Task Aborted would be sent to an
outstanding Rewind on Host B.
TASK ABORTED
DATAPRES field is set to RESPONSE_DATA, the Status and Sense Data
Never returned by an HP LTO Ultrium tape drive.
a
a
a
a
a
b
Task management functions
This section includes all SCSI task management functions, both supported and unsupported.
Task Management functions provide an initiator and a target in the SAS domain with a means of
managing specific operations or tasks. The supported functions are listed in this chapter.
Response frames and task management functions34
HP restricted
Page 35
In the following table, all the supported task management functions use the Logical Unit Number
field, and
ABORT TASK (01h) and QUERY TASK (80h) also use the Tag of Task to Be Managed field.
CodeTask Management
Function
ABORT TASK
01h
ABORT TASK SET
02h
CLEAR TASK SET
04h
LOGICAL UNIT RESET
08h
Reserved
20h
CLEAR ACA
40h
QUERY TASK
80h
others
Reserved
Description
Performs the ABORT TASK task management function with:
L = Logical Unit Number field
Q = Tag of Task to Be Managed field
Performs the ABORT TASK SET task management function with:
L = Logical Unit Number field
Performs the CLEAR TASK SET task management function with:
L = Logical Unit Number field
Performs the LOGICAL UNIT RESET task management function with:
L = Logical Unit Number field
Not supported
Performs the QUERY TASK task management function with:
L = Logical Unit Number field
Q = Tag of Task to Be Managed field
TEST UNIT READY
REWIND
REQUEST SENSE
READ BLOCK LIMITS
READ
READ 6 (CD-ROM)
WRITE
SET CAPACITY
WRITE FILEMARKS
SPACE
INQUIRY
VERIFY
MODE SELECT
RESERVE UNIT
RELEASE UNIT
ERASE
MODE SENSE
LOAD/UNLOAD
START/STOP UNIT (CD-ROM)
RECEIVE DIAG RESULTS
SEND DIAGNOSTIC
PREVENT MEDIUM REMOVAL
READ BUFFER
READ TOC (CD-ROM)
REPORT DENSITY SUPPORT
LOG SELECT
LOG SENSE
MODE SELECT (10)
RESERVE UNIT (10)
RELEASE UNIT (10)
MODE SENSE (10)
PERSISTENT RESERVE IN
PERSISTENT RESERVE OUT
READ ATTRIBUTE
WRITE ATTRIBUTE
REPORT LUNS
SECURITY PROTOCOL IN
REPORT DEVICE IDENTIFIER
REPORT TARGET PORT GROUPS
REPORT SUPPORTED OPCODES
REPORT SUPPORTED TASK MGMNT FNS
READ LOGGED-IN HOST TABLE
Enh FW UPGRADE REPORT IMAGE INFO
SET DEVICE ID
Enh FW UPGRADE DOWNLOAD FW SEG
Enh FW UPGRADE REBOOT
READ MEDIA SERIAL NUMBER
SECURITY PROTOCOL OUT
SAS-specific Vendor-Unique ENABLE TLRS
Command details
The command descriptions in Chapter 5 are listed in alphabetical order of command name. Each
command is described briefly. This is followed by a list of pre-execution checks which are described
below. The Command Descriptor Block (CDB) is then given, with details of the various parameter
bits and fields.
NOTE: In compliance with the SCSI specification, the drive terminates a command with a CHECK
CONDITION
code is received which is not zero.
Before executing a command, the drive makes a number of checks. They fall into three categories:
• Checks on the command sent by the host. These ensure that no reserved or fixed fields have
been set to illegal values. They check the syntax of commands, in other words the cross
dependency of fields. For example, the Flag bit must not be set if the Link bit is not set.
• Checks to ensure that there are no outstanding
posted for the host that has sent the command.
• Checks on media access abilities. These are performed for commands requiring access to the
cartridge. A command is rejected if it attempts to access the cartridge when no cartridge is
present or the cartridge is unloaded.
The checks are described below in alphabetical order. The usual order of execution is Illegal Field,
Fixed Bit, Flag Link, Bad LUN, Reservation, Deferred Error, Unit Attention, Media Access, Media
Write, Diagnostic Status, Humidity, Parameter List.
Bad LUN check
SAS drives only: For all commands except INQUIRY 12h, this checks that the LUN specified by the
host is zero. The LUN is taken from the
block.
status and sets the sense key to ILLEGAL REQUEST when a reserved bit, byte, field or
UNIT ATTENTION or DEFERRED ERROR events
COMMAND frame that encapsulates the command descriptor
• If the LUN is unsupported, and the host command is not
reported to the host with a sense key of
unit not supported).
• If the LUN is unsupported, and the host command is
replaced with a sense key of
supported). This new sense data is returned to the host. Once the command has completed
successfully, the sense data is cleared.
Deferred Error check
A deferred error is generated when a command with immediate report fails after the report has
been returned. The check looks to see if a deferred error exists for the host which sent the command,
in other words, a deferred error for which
such an error exists, then the drive reports
set to
DEFERRED ERROR (which was generated when some previous command failed).
Note that if a
the
DEFERRED ERROR condition will be reported first. This is because the operation leading to the
deferred error must have been older than that leading to the unit attention. The drive reports the
conditions in the order in which they arose.
Commands—introduction38
UNIT ATTENTION condition and a DEFERRED ERROR condition both exist for an initiator,
REQUEST SENSE, CHECK CONDITION is
ILLEGAL REQUEST, and additional sense of 2500h (logical
REQUEST SENSE, the original sense data is
ILLEGAL REQUEST, and additional sense of 2500h (logical unit not
CHECK CONDITION status has not yet been reported. If
CHECK CONDITION. The sense data for the command is
HP restricted
Page 39
Diagnostic Status check
This ensures that the drive is in a fit state to access the media. It does this by checking that there is
no
DIAGNOSTIC FAIL status within the drive.
If the drive has failed diagnostics,
ERROR
and additional sense of 400Xh (diagnostic failure on component X).
Fixed Bit check
For the READ, VERIFY and WRITE commands, a Fixed bit set to 1 indicates that the length parameter
of the command is for fixed block mode. If fixed block mode is selected then the block size in the
Mode Select block descriptor must not be zero. Otherwise
sense data is set as described for the
Flag Link check
This check ensures that the host has not set the Flag bit in the control byte of the command without
setting the Link bit as well. If the test fails then
ILLEGAL REQUEST and additional sense of 2400h (invalid field in CDB). The Flag field is identified as
the bad field.
Illegal Command check
If the drive does not recognize the opcode of the command that it has been sent, it will do one of
the following:
• Report
additional sense code will be set to 2000h (invalid command opcode).
• Report an invalid field in the command descriptor block. The sense key will be set to
REQUEST
pointer in the sense data will be zero.
CHECK CONDITION status. The sense key will be set to ILLEGAL REQUEST and the
, the additional sense code will be set to 2400h (invalid field in CDB) and the field
CHECK CONDITION is reported with a sense key of HARDWARE
CHECK CONDITION is reported and the
ILLEGAL FIELD check.
CHECK CONDITION is reported with a sense key of
ILLEGAL
Illegal Field/Request check
Checks are performed to ensure the host has not set any of the following in the command descriptor
block:
• a fixed field
• a reserved field
• the control field
• two or more fields to logically conflicting values
If a field has been set to an illegal value:
• C
HECK CONDITION status is reported to the host with a sense key of ILLEGAL REQUEST and
additional sense of 2400h “invalid field in CDB”.
• The sense key specific bit is set and the sense key specific bytes will be a field pointer.
• The command/data bit is set, indicating that the illegal parameter was in the command.
NOTE: Command descriptor blocks are scanned from left (bit 7) to right (bit 0), and down (from
byte 0 to byte n). The field pointer will be set to point to the first bit of the first illegal field
encountered using this scanning route. In some cases, where multiple fixed fields are contiguous, the
field pointer might be set to point to the first bit of the first fixed field in the group of fixed fields,
whereas the actual illegality may lie in a later bit.
Media Access check
This checks if the drive is able to perform media access commands. If the media is inaccessible then
CHECK CONDITION status is reported with a sense key of NOT READY. The additional sense will be
set to one of the codes associated with the
NOT READY key.
Media Information check
During power-on and following a SCSI reset, knowledge of the whereabouts of the cartridge is
unavailable. It is not possible to execute commands which assume that this knowledge is available
until the drive has recovered from the power-on or reset.
The test checks whether the drive knows if a cartridge is physically present in the drive.
Commands—introduction40
HP restricted
Page 41
If information about the tape cartridge is not available, the test fails with CHECK CONDITION, a
sense key of
NOT READY, and additional sense of 3E00 (logical unit has not self-configured yet).
Media Write check
This checks whether the media is write-protected. If it is, CHECK CONDITION is reported with a sense
key of
DATA PROTECT and additional sense of 2700h (write-protected).
Parameter List check
For LOG SELECT, MODE SELECT and some diagnostic commands, the associated data sent to the
drive is in the form of parameter lists. These are described under the command names in the next
chapter. Checks are performed to test the following:
• Fixed and reserved fields have not been modified. Fixed fields are indicated by a number in
round brackets following the field name.
• A field has been set to an invalid value.
• The syntax of the page of parameters has been violated—for example, where a particular value
in one field imposes limitations on the valid range for another field.
If a field has been set to an illegal value,
of
ILLEGAL REQUEST and additional sense of 2600h (invalid field in parameter list).
The drive scans the data in the Command Description Block from “left” (bit 7) to “right”, and “down”
(from byte 0 to byte n). It sets the field pointers to the first bit of the first bad field encountered. If the
bad field is contained in a contiguous group of fixed fields, the pointers indicate the first bit of the
first field in the group, even though the error may be in a later field in the group.
NOTE: With MODE SELECT, the drive checks the integrity of the whole parameter list before acting
on any parameters, so all the mode parameters need to be correct before any of them are
implemented.
Reservation check
This checks to see if the drive has been reserved for use by a host, and if it has, whether the host is
the same host that sent the command being executed.
If the drive has been reserved for some other host then
See the
(page 207) commands.
PERSISTENT RESERVE OUT (page 134), RELEASE UNIT (page 173) and RESERVE UNIT
Unit Attention check
This checks if a UNIT ATTENTION condition exists for the host which sent the command. If it does, the
drive reports
data will be set according to the unit attention condition which exists. See Unit Attention Sense in
the description of the
CHECK CONDITION status with a sense key of UNIT ATTENTION. The remaining sense
CHECK CONDITION is reported to the host with a sense key
A SCSI command descriptor block (CDB) is a sequence of 6, 10, 12 or 16 bytes sent by a host to a
SCSI target with the bus in command phase. The CDB tells the drive what action should be
performed. The final byte is known as the Control byte.
Vendor Unique (0)Reserved (0)NACA(0) Flag (0) Link (0)
There are a number of fields in a CDB which are common to all commands. These are shown in the
following table.
Multi-Byte Parameter
Group Code
and
Operation
Code
ReservedA reserved field should always be set to zero. The drive checks reserved fields,
Multi-Byte
Parameter
ControlThe control field is mainly concerned with the use of linked commands. These are
Vendor-Unique This field is ignored by the firmware
NACA0 The Normal ACA flag is 0, indicating that it is not supported.
Flag0
Link0 Linked commands are not supported.
The operation code uniquely identifies the command. The top three bits of the
operation code are known as the group code and these define the length of the
command descriptor block:
Group 0
Group 1
Group 2
Group 3
Group 4
Group 5
Group 6
Group 7
and if one is non-zero then it will reject the command with
A multi-byte parameter field in a command is “big-endian”, that is, bit 7 of the first
byte of this field is the most significant.
not supported by the LTO SCSI Command Set, so a
generated if this field is set to anything other than zero.
The Enhanced FIRMWARE UPGRADE DOWNLOAD FIRMWARE SEGMENT command allows the
application client to download a firmware image, via an internal cache buffer, to the Secondary
Image bank. No image should be considered written to the flash until this command, sent with
LAST=1, returns
Pre-execution checks
Unit AttentionIllegal FieldReservationDeferred Error
Command descriptor block
0Operation Code (A4h)
1Reserved (0)Service Action (1Fh)
2HP LTO VU MI Opcode (05h)
3(MSB)
5(LSB)
6(MSB)
8(LSB)
9Reserved (0)
10Reserved (0)Last
11Control
GOOD status.
76543210
Segment Offset
Segment Length
CDB fields
Segment OffsetThe offset within the bank at which this segment will be stored. The
application client must set this to zero for the first download segment
command. (It is possible to re-start the firmware download process many
times by setting Segment Offset to zero).
The field has the following restrictions:
• It must be a multiple of 4 bytes.
• It must reside within the bank size (1.91 MB).
The application client is starting a firmware download process.
0
Segment LengthThe length in bytes allocated of the segment transferred.
Commands44
HP restricted
Page 45
Last0
The segment will be copied to the internal cache buffer at the specified
offset.
It is assumed that the last byte of the image is Segment Offset + Segment
1
Length. Then the whole image is validated, and if correct, transferred from
the cache buffer to flash. Status will not be returned until the firmware has
been successfully written to the Secondary Image bank.
The Enhanced FIRMWARE UPGRADE REBOOT command causes the drive to reset and boot from the
Primary Image bank. Status will be returned before reboot takes place. Before the reboot, all
buffered write data is written to tape, and the tape is unloaded, or unthreaded depending on
configuration settings.
Pre-execution checks
Unit AttentionIllegal FieldReservationDeferred Error
Command descriptor block
76543210
0Operation Code (A4h)
1Reserved (0)Service Action (1Fh)
2HP LTO VU MI Opcode (06h)
3Reserved (0)Swap
4
10
11Control
Reserved (0)
CDB fields
Swap
Segment Length
Commands46
The drive resets and reboots the currently running firmware, so the
0
association of Primary and Secondary Images will remain unchanged.
Enabled Automation Ports will be disabled, and the library controller needs
to re-enable them.
The drive swap which banks are associated with the Primary and Secondary
1
Images before resetting the drive. Use this to reboot the drive with the
firmware most recently downloaded to the Secondary Image.
Regardless of the value of the Swap field, the reboot command should not
cause the drive to be offline for more than about 7 seconds.
HP restricted
Page 47
Enhanced FIRMWARE UPGRADE REPORT IMAGE INFO A3h (1Fh)
Description
The Enhanced FIRMWARE UPGRADE REPORT IMAGE INFO command returns a number of image
descriptors to the application client up to the size specified in the Allocation Length field.
Pre-execution checks
Unit AttentionIllegal FieldReservationDeferred Error
Command descriptor block
76543210
0Operation Code (A3h)
1Reserved (0)Service Action (1Fh)
2HP LTO VU MI Opcode (05h)
3
5
6(MSB)
7(LSB)
8
10
11Control
Reserved (0)
Allocation Length
Reserved (0)
CDB fields
Allocation LengthThe drive will return up to this number of bytes, truncating any parameter
data as required.
Returned data
76543210
0Firmware Image Info Version
1Reserved (0)
2(MSB)
3(LSB)
4(MSB)
The version of the following descriptors. Currently at version 1.
Version
Firmware Image Info
Length
The total length in bytes of the descriptors that follow. Version 1 descriptors
are 28 bytes in length, for a dual bank drive this field will be 56.
Firmware image descriptor (version 1)
76543210
0Bank ID
1Reserved (0)StatusRsvd (0) Primary
2
Reserved (0)
3
4(MSB)
7(LSB)
8(MSB)
15(LSB)
16(MSB)
Publication Revision
Firmware Revision
Image Build Time
19(LSB)
20(MSB)
23(LSB)
24(MSB)
27(LSB)
Image Size
Bank Size
Status000b
001b–101b
011
100b–111b
The image in good (no errors)
Reserved
The bank does not contain an image.
Reserved
PrimaryThis field will be set if this is the Primary Image bank.
Publication RevisionAs reported in bytes 32–35 of the standard
INQUIRY data.
Firmware RevisionAs reported in bytes 30–48 of VPD page C0h.
Image Build TimeThe time (UTC-based) at which this firmware image was built.
Image SizeThe size of the stored image in bytes
Bank SizeThe size of the bank in bytes
Commands48
HP restricted
Page 49
ERASE 19h
The ERASE command is used to erase data on tape from the current logical position. The Long bit is
used to decide whether the ‘old’ data is physically overwritten or not.
FC and SCSI drives only: E
will not overwrite or erase user data on tape.
Pre-execution checks
Illegal FieldReservationDeferred ErrorUnit Attention
Media AccessMedia WriteDiagnostic Status
Immed 0 The drive reports status after the command has completed.
The drive reports status when it starts the command (after any pre-execution
1
checks and prerequisite unloads have completed).
LongThe Long bit controls the distance to be erased.
0 The current position becomes the end of logical data.
1 End of Data is written, followed by Data Set Separators to the end of the tape.
RASE commands (short or long) to a drive containing a WORM cartridge
NOTE: Short erase is only used to truncate data at the current logical position. It cannot be used to
create a “hole” in the tape into which data can subsequently be written “in place”. This will merely
cause the drive to streamfail. The logical tape position is unaffected by this command. A
CONDITION
logically positioned past EOT immediately before the erase.
for Early Warning EOM (drive error code 2C98h) will only be given if the tape is
CHECK CONDITION HARDWARE ERROR
CHECK CONDITION DATA PROTECT
HP restricted
5100h (erase failure)
300Ch (WORM medium
—overwrite attempted)
Page 50
INQUIRY 12h
INQUIRY tells the drive to return information about the basic operating parameters to the host. These
parameters cannot be changed. The drive returns Inquiry data to the host in a data-in phase.
NOTE: This command is immune from most of the pre-execution checks that other commands must
pass (for example, it can be executed while the unit is reserved for another host). U
deferred error conditions are preserved and reported on subsequent commands.
Pre-execution checks
Only the Illegal Field Check is performed before the command is executed.
nit attention and
If the EVPD bit is clear, the page code must be zero, otherwise
If the EVPD bit is set, the page code must be one of the supported page codes for Inquiry data.
Otherwise
LUNThis field is ignored.
EVPDEnable Vital Product Data
01Normal inquiry data is returned.
A page of vital product data is returned.
Commands50
HP restricted
Page 51
Page Code
Allocation
Length
If the EVPD bit is zero the Page Code field must be zero.
If the EVPD bit is set to 1, the drive returns the Inquiry page in this Page Code
field:
Supported Vital Product Pages page
00h
Unit Serial Number page
80h
Device Identification page
83h
Management Network Address page
85h
Extended Inquiry Data page
86h
Mode Page Policy page
87h
SCSI Ports page
88h
Sequential Access Device Capabilities page
B0h
Manufacturer-assigned Serial Number page
B1h
TapeAlert Supported Flags page
B2h
Firmware Revision Levels page
C0h
Hardware Revision Levels page
C1h
PCA Revision Levels page
C2h
Mechanism Revision Levels page
C3h
Head Assembly Revision Levels page
C4h
ACI page
C5h
HP Alternative Inquiry page (variant specific)
CCh
HP Unique Inquiry page (variant specific)
D0h
The maximum amount of data (in bytes) that should be returned. If more than
this is available, the amount returned is truncated to allocation length. No
error is reported.
INQUIRY data pages
Returned data:
INQUIRY returns its standard data if the EVPD bit is zero, or returns a page of data as specified by
the Page Code field when EVPD is one.
Standard Inquiry Data format (LUN0)
This is the data returned by the drive in response to an Inquiry command with its EVPD bit set to
zero. The data also depends on the value of the LUN field in the Inquiry CDB, the LUN value in the
identify message and the configuration of the drive.
Note that the data below is for the standard distribution firmware.
7654 3 2 1 0
0Peripheral Qualifier (000b)Peripheral Device Type (01h)
1RMB (1)Reserved (0)
2Version Number (5)
3ObsoleteNACA(0) HiSup(0)Response Data Format (2)
The Standard Inquiry Data is based on the SCSI 3 standard for Standard Inquiry Data.
For the LUN to which the drive is attached, the Peripheral Qualifier field is set to 000b, the
Peripheral Device Type field is set to 01h, the Removable Medium (RMB) flag is set to 1 and the
Device-type modifier is set to 0.
Commands52
HP restricted
Page 53
Inquiry Data fields
Peripheral Qualifier000b
There is a device on the logical unit selected, so the LUN field in
the identify message was 0.
011b
The LUN field in the identify message has specified an
unsupported logical unit. This means any LUN other than 0.
Peripheral Device
Type
01h
05h
1Fh
Sequential Access Device
CD Device (reported when in OBDR mode)
No Device (the Peripheral Qualifier will be 011b in this case)
RMB1The Removable Medium bit is one, indicating that the tape can be
removed.
Device-Type
0This is a six-bit user defined code, set to zero.
Modifier
Version Number5Indicating that the drive complies with the SPC-3 standard.
NACA0The Normal ACA flag is 0, indicating that it is not supported.
HiSup0The Hierarchical Support flag is 0, indicating that the hierarchical
addressing model is not supported.
Response Data
2The Inquiry Data format complies with the SCSI-3 standard.
Format
Additional LengthThe length in bytes of the length of the rest of the Inquiry data.
5BhThere are 91 (5Bh) more bytes of Inquiry data.
SCCS0No storage array controller component is embedded in the drive.
ACC0No Access Controls Coordinator may be addressed through this
LUN.
TPGS01bTarget Port Group Support. Only implicit asymmetric logical unit
access is supported.
3PC0Third-Party Copy commands are not supported.
Protect0Protection information is not supported.
BQueBasic Queuing flag
0The flag is zero for SCSI and SAS drives, with CmdQue = 1.
1The flag is 1 for Fibre Channel drives, with CmdQue = 0.
EncSvr0The drive does not support Enclosure Services command.
VS0Vendor-Specific field—not currently used
MultiP1The drives has multiple ports.
MChngr0The drive is not embedded within or attached to a medium
transport element.
Adr16, WBus16,
Sync
0FC and SAS drives: These features are not applicable.
1SCSI drives: These features are supported.
Linked0The drive does not support linked commands.
1SCSI and SAS drives: With BQue = 0. For SAS, the full queuing
model is supported.
Vendor
Identification
Product
Identification
A vendor-specific, 8-byte string of ASCII characters, left justified and padded
with space characters “HP”.
A left-justified, vendor-specific, 16-byte string field of ASCII characters with
space character padding on the right. The string consists of two parts:
• First half (bytes 16–23): “Ultrium”
• Second half (bytes 24–31): “<generation>-<interface type>”
The following string has been defined:
All LTO-4 drives: “Ultrium 4-SCSI”
Product Revision
Level
A vendor-specific string of four ASCII characters: “PdsV”:
• P specifies the product (for LTO4 drives, “H” for FC, “B” for SCSI, “A” for
SAS).
• d denotes the major release level.
• s is the minor release level.
• V is a unique identifier for each variant of code.
WORM VersionThe version of WORM supported.
WORM1The drive supports the LTO WORM specification.
OBDR string“$DR-10” if the drive supports Tape Disaster Recovery.
Clocking0For FC and SAS drives.
3For SCSI drives, indicating that the drive supports both ST and DT
transfers.
QAS0The drive does not support Quick Arbitration and Selection.
IUSInformation Units
0FC and SAS drives: Not applicable
1SCSI drives: Supported
Version Descriptor These fields can be used to identify up to eight standards to which the drive
The Unit Serial Number page contains a single value which is a 10-byte ASCII string. The string,
with the Vendor Identification and Product Identification fields in the standard Inquiry data, uniquely
identifies the drive.
2 The Identification Descriptor contains only ASCII data.
2.
1 The Identifier field is associated with the port that received the request.
2 The Identifier field is associated with the SCSI target device that contains the
addressed logical unit.
3Reserved
1 Vendor ID followed by the product identification field from the standard inquiry
data and the serial number field from the Serial Number Inquiry page.
3 FC drives: Identification descriptor is the 64-bit IEEE Registered World Wide
Name (in NAA identifier format).
4 Relative Port identifier
5 Target Port Group identifier
Logical Unit Identifier
76543210
0Protocol Identifier (0)Code Set (1)
1PIV (0)Rsvd (0)Association (0)Identifier Type (3)
2Reserved (0)
3Identifier Length (8)
4(MSB)
11(LSB)
SSC Device Logical Unit Name (IEEE Registered Name)
76543210
0Protocol IdentifierCode Set (2)
1PIV (1)Rsvd (0)Association (2)Identifier Type (1)
2Reserved (0)
3Identifier Length (34)
4(MSB)
11(LSB)
12(MSB)
27(LSB)
28(MSB)
37(LSB)
Device Name
(IEEE Registered Name)
Vendor ID
Product Identification
Serial Number
Management Network Address VPD page
The Management Network Addresses page provides a list of network addresses of management
services associated with a SCSI target device, target port, or logical unit.
SimSup1The drive supports the Simple Task attribute.
Mode Page Policy VPD page
The Mode Page Policy VPD page enables an application client to find what mode page policy is in
effect for supported mode pages. One descriptor is returned for each mode page, or group of
mode pages, that have a specific page policy in effect.
The SCSI Ports VPD page provides a means of retrieving identification descriptors for all SCSI ports
in a SCSI target device or SCSI target/initiator device.
The following SCSI Port Identification Descriptors (one per port enabled) are returned for SAS
devices:
7 6 5 4 3 2 1 0
0–1 Reserved (0)
2
3
4–9Reserved (0)
10
11
12Protocol Identifier (6)Code Set (1)
13PIV (1)Rsvd (0)Association (1)Identifier Type (3)
14Reserved (0)
15Identifier Length (08h)
16
23
Port Identifier0001h The addressed port is port A.
Protocol Identifier00hFibre Channel
Code Set1The Identification Descriptor is a binary field.
PIV1The Protocol Identifier field is valid. The PIV flag is set to one for an
Association1The Identifier field is associated with the port that received the request.
Identifier Type1The subsequent fields contain the Vendor ID followed by the product
Port Name (IEEE Registered Name—see page 16)
0002h The addressed port is port B.
01hSCSI
06hSAS
Target Port Descriptor Length (0Ch)
2The Identification Descriptor contains only ASCII data.
association value of 1 or 2.
identification field from the standard inquiry data and the serial
number field from the Serial Number Inquiry Page.
3The subsequent field is the Fibre Channel 64-bit Name Identifier.
Port Identifier
Sequential Access Device Capabilities page
This page provides the application client with a means of determining which features are supported
by the Device Server.
WORM1The Device Server supports Write Once Read Many (WORM) operation.
Manufacturer-assigned Serial Number page
The Manufacturer-assigned Serial Number page provides the application client with a method of
determining the device serial number as originally assigned by the manufacturer. The same will
returned in the Unit Serial Number page unless an automation controller has provided a new serial
number; however this page will always reflect the original serial number.
The Drive Component Revision Levels pages contain details of the revisions of each of the major sub
assemblies of the drive. For any given product, if these pages are the same then the drive has been
built with the same components and with the same manufacturing process.
Component A 12-character entry to identify the component that the revision is for.
VersionA 7-character version code with a three-digit major revision number, a period and a
The LOAD/UNLOAD command allows the host to specify that a tape cartridge present in the drive is
either made ready for data transfer (“loaded”) or disabled for data transfer (if Prevent Media
Removal is set). It can also cause the cartridge to be ejected from the drive (“unloaded”).
Pre-execution checks
Illegal FieldReservationDeferred Error
Unit AttentionDiagnostic StatusMedia Information
If an unload is to be performed, the drive checks if the tape is currently being loaded. If it is, CHECK
CONDITION
ready).
If a load is to be performed, the drive checks to ensure that a tape cartridge is present. If not, it
reports
not present). If the media is currently being unloaded or ejected, it reports
sense key of
is reported with a sense key of NOT READY and additional sense of 0401h (becoming
CHECK CONDITION with a sense key of NOT READY and additional sense of 3A00h (medium
CHECK CONDITION with
NOT READY and additional sense of 0400h (cause not reportable).
76543210
CDB fields
Immed0 The drive reports status after the command has completed.
The drive reports status when it starts the command (after any pre-execution
1
checks and prerequisite unloads have completed).
Hold0 A normal load/unload will be performed.
A load will cause the cartridge to be pulled in and seated in the drive, but the
tape will not be threaded.
1
An unload will cause the tape to be unthreaded, but the cartridge will not be
ejected.
In Hold position, the Cartridge Memory is accessible.
ReTenThis field is ignored.
Load0 The drive performs an unload operation.
1 The drive performs a load operation.
Commands68
HP restricted
Page 69
Load/Unload specific status
Following a successful LOAD command, CHECK CONDITION is posted to all initiators other than the
initiator of the
2800h (not ready to ready transition). There is an exception to this: if a load occurs when the tape
is already loaded, no
Once
UNIT ATTENTION is cleared, unsolicited positional sense is set. The sense key will be NO
SENSE
with additional sense of 0004h (BOT detected).
If an unformatted tape is inserted, the drive loads it and it behaves as if it is a blank tape.
LOAD command. The sense key is set to UNIT ATTENTION, with additional sense of
UNIT ATTENTION sense is generated.
If a cartridge with no Cartridge Memory or a failed Cartridge Memory is loaded,
CONDITION is returned with a sense key of MEDIUM ERROR, with additional sense of 5200h
CHECK
(cartridge fault).
Loading a cartridge
The drive loads an Ultrium 4, Ultrium 3 or Ultrium 2 tape automatically when it is inserted, without
any host interaction. If the load is successful, media access commands are permissible (see the
Media Access check).
If the tape is already loaded when a Load request is received, the tape is positioned at the
beginning of the tape (as though a
with additional sense of 2800h (not ready to ready transition) is not generated for other hosts.
If the tape is in the process of being loaded when the Load request is received, the drive will wait for
the load to complete and, assuming the load was successful, take one of the following actions:
• If the Load was issued by the current host (that is, a previous immediate-reported load) and
completed successfully,
GOOD status is reported. No further action is taken.
• If the Load was issued by some other host (or was an autoload) and completed successfully,
CHECK CONDITION is reported, with a sense key of UNIT ATTENTION and additional sense of
2800h (not ready to ready transition).
• If the Load was issued by the current host and failed,
deferred error condition will exist for the current host.
• If the Load was issued by some other host and failed, the load will be re-attempted on behalf of
the current host.
REWIND had been sent). Unlike a “full” load, UNIT ATTENTION
CHECK CONDITION is reported, since a
Unloading a cartridge
If an unload is requested and there is a tape present in the drive (either loaded, loading or
unloading):
1. Any buffered data is written to tape.
2. The tape is rewound to the physical BOM (beginning of media).
3. If medium removal is prevented,
REQUEST
4. G
and additional sense of 5302h (medium removal prevented).
OOD status is reported if the tape unloaded successfully. Otherwise, another unload operation
is initiated on behalf of the host that issued the unload request.
Following an unload, any media access commands will be rejected by the Media Access check.
CHECK CONDITION is reported with a sense key of ILLEGAL
HP restricted
Page 70
• If an unload request is received while the tape is in the process of unloading (for example, as a
result of pressing the eject button), it will be queued until the unload is complete.
• If an unload request is received while there is no tape present, or if a tape is present but not
loaded and medium removal is prevented,
GOOD status is reported.
It is possible to unload and eject the cartridge by pressing the Eject button on the front panel.
Commands70
HP restricted
Page 71
LOCATE 2Bh/92h
The LOCATE command moves the current logical position to the position specified by the command.
The new position is specified by the offset from start of the media in terms of blocks. The first block
(that is, BOT) is block address 0.
Any unwritten data is written to tape before the command is executed.
Pre-execution checks
Illegal FieldReservationDeferred Error
Unit AttentionMedia AccessDiagnostic Status
BTBlock address Type. This field is not supported and should always be set to zero
indicating that the Block Address field represents the count of all blocks and filemarks
between the beginning of the media and the current logical position.
CPChange Partition. This field is not supported and should be set to zero.
Immed0The drive only reports status after the Locate command has completed.
The drive reports status when it starts the command and continues with the
1
positioning in the background.
BAM0This field is not supported.
Block
Address
The Block Address specifies the number of blocks and filemarks between BOM and the
position to be located.
Partition Not supported.
Dest
type
00b Specifies that the Logical Identifier field is a logical object identifier.
01b Specifies that the Logical Identifier field is a logical file identifier.
Other values are not supported.
Logical
Identifier
The specific block on tape to locate. It can be a generic block, either a record or a
filemark (Dest Type = 00b) or a specific filemark on tape (Dest Type = 01b).
Locate specific status
EventStatusKeyAdditional Sense
EOD encountered
EOM encountered
Failed to read
data—media error or
non-fatal drive error
Early Warning EOM
encountered
Data format corrupt
CHECK CONDN BLANK CHECK
CHECK CONDN MEDIUM ERROR
0005h (EOD encountered).
0002h (EOT encountered). EOM bit
set.
CHECK CONDN HARDWARE ERROR
3B00h (sequential positioning error)
Early warning end of medium information is not reported for Locate
commands
CHECK CONDN MEDIUM ERROR
3001h (can’t read media, unknown
format)
Commands72
HP restricted
Page 73
LOG SELECT 4Ch
The Log Select command causes log data on the drive to be reset to its default value or to be set to
an initiator specific value.
The following are valid combinations of values for the PCR (Parameter Code Reset), Parameter List
Length and PC (Page Control) fields
Parameter List Length
PCRParameter List
Length
1001b or 11b All the logs on the drive that can be reset are reset to their
1000b or 10b No action is taken and
0>001b or 11b Data is sent from the host and is written to the indicated logs,
Otherwise
additional sense of 2400h (Invalid Field in CDB).
PCR0Parameter Code Reset. The function performed is defined by the PC field.
SP0The Save Page (SP) flag is not supported and must be set to 0.
PCThe Page Control field defines the type of parameter values to be selected:
CHECK CONDITION status is returned, the sense key is set to ILLEGAL REQUEST with
00b
No operation is performed. The Parameter List Length must be zero. If it is not,
or
check condition invalid field in CDB is set.
10b
01b The drive will clear logs as specified by the parameter data.
11b The drive will clear all of its internal logs.
0No data is to be transferred. This is not considered an error.
>0 Specifies how many bytes of parameter data are to be sent. The data transferred
will consist of zero or more 4-byte log page headers with the page length in
those headers set to zero. For each log page header received, the drive clears
the associated log.
Commands74
HP restricted
Page 75
LOG SENSE 4Dh
LOG SENSE allows the host to read the drive’s logs. A single log is returned with each invocation of
LOG SENSE.
Pre-execution checks
Illegal FieldDeferred ErrorUnit Attention
The Page Code must match one of the supported log page codes. If it does not, then CHECK
status is reported. Sense data will be as described in the Illegal Field Checks.
76543210
Reserved (0)
Parameter Pointer
Allocation Length
CDB fields
PCThe Page Control field defines the type of log parameter to be returned:
00b Current Threshold Values—any parameters in the log that are counters
contain the maximum value that they can count to.
01b Current Cumulative Values—any parameters in the log that are counters
contain their current counts.
NOTE: Counts are reset to their default cumulative values (see below)
following a power-on, reset or bus device reset. Media related counts are
also reset following a load.
10b Default Threshold Values—same as the Current Threshold Values
11b Default Cumulative Values—any parameters in the log that are counters
contain the initial values of those counters (set at power-on, reset, bus
device reset and, in the case of media logs, load).
The PC field has no effect on the data returned when the selected log contains
event or trace codes rather than counts.
Page CodeThe Page Code field identifies which log page is being requested by the host. See
Parameter
Pointer
Allocation
Length
Log page format
All log pages except Page 0 consist of a page code header followed by a number of parameters.
The page header has the following format:
76543210
0Page Code
1Reserved (0)
2(MSB)
3(LSB)
The Page Code specifies which Log page is being returned. The Page Length indicates the number
of additional bytes in the parameters.
page 77 for the list of valid page codes.
0All parameters are returned.
nParameter data of a specified log page is returned in ascending order
beginning from this code. If this code is larger than the largest parameter in
the page, the drive will return
CHECK CONDITION with additional sense of
2400h (Invalid Field In CDB).
The Allocation Length field specifies the maximum number of bytes of data that
should be returned to the host. The drive will return the entire log or Allocation
Length bytes, whichever is the lesser.
Page Length
For the
Log Select command only, the four bytes shown above are sent for each log page to be
cleared. The Page Length field should be set to zero.
For the
Log Sense command one or more parameters is sent. See the actual page descriptions above
for more information. Note that all the parameters for a particular page must be sent. Each
parameter has the following format:
Parameter CodeA two-byte value that uniquely identifies the parameter within the log.
DU, TSD, ETC, TMC
and LP
Commands76
0 Must be zero. For a full description of these fields refer to the SCSI-2
standard.
HP restricted
Page 77
DS1 Must be 1, indicating that drive will maintain the saving of data itself.
Note that the host must set the SP bit to 1 in a
otherwise a
Parameter LengthThe length of Parameter Bytes in bytes.
Parameter BytesThe actual parameter data.
Supported Log Pages page
This SCSI log may be recovered using a Log Sense command with the PC field set to anything and
the Page Code field set to 00h. The page lists the page codes of other logs supported by the drive.
It can neither be reset nor written.
The Write Error Counters log is page 02h. The Page Length is 38h. There are seven parameters, 0
through 6. All fields are four bytes long.
All these counters are updated when the data set is physically written. They relate to the current tape
and are cleared when the tape is unloaded.
Parm. DefinitionDescription
0Errors corrected without substantial delay Total number of errors corrected without delay
1Errors corrected with possible delaysTotal number of errors corrected using retries
2TotalSum of parameters 3 and 6
3Total errors correctedThe number of data sets that needed to be
4Total times error correction processedNumber of CCQ sets rewritten
5Total data sets processedThe total number of data sets written
6Total uncorrected errorsThe number of data sets that could not be
This data can be reset to zero, but not written.
Read Error Counters log page
The Read Error Counters log is page 03h. The Page Length is 38h. There are seven parameters, 0
through 6. All fields are four bytes long.
rewritten
written
All these counters are updated when the data set is physically read. They relate to the current tape
and are cleared when the tape is unloaded.
Parm. DefinitionDescription
0Errors corrected without substantial delay Total number of errors corrected without delay
1Errors corrected with possible delaysTotal number of errors corrected using retries
2TotalSum of parameters 3 and 6
3Total errors correctedThe number of data sets that were corrected
after a read retry
4Total times error correction processedNumber of times C2 correction is invoked
5Total bytes processedThe total number of data sets read
6Total uncorrected errorsThe number of data sets that could not be read
after retries
This data can be reset to zero, but not written.
Commands78
HP restricted
Page 79
Sequential Access Device log page
The Sequential Access Device Log page is page 0Ch. The Page Length is 40h. Five parameters are
supported, all eight bytes long. With the exception of 0100h (cleaning required), they are updated
when a data set is logically written and cleared at the start of tape load; the values of each
parameter relate to the current tape.
Parm. Description
0001h The number of data bytes received from application clients during write command
operations. This is the number of bytes transferred over SCSI, before compression.
0002h The number of data bytes written to the media as a result of write command operations,
not counting the overhead from ECC and formatting. This is the number of data bytes
transferred to media, after compression.
0003h The number of data bytes read from the media during read command operations, not
counting the overhead from ECC and formatting. This is the number of data bytes
transferred from media with compression.
0004h The number of data bytes transferred to the initiator or initiators during read command
operations. This is the number of bytes transferred over SCSI, after decompression.
0100h Cleaning required, a non-volatile cleaning indication.
A non-zero value of parameter 0100H (cleaning required) relates to the drive It indicates that a
condition requiring cleaning has been detected and a subsequent cleaning cycle has not yet been
completed. The parameter is updated asynchronously. It persists across hard resets and power
cycles, and is cleared when a cleaning cycle is performed.
Temperature log page
The Temperature Log page is page 0Dh. The following parameters are supported:
Parm. Description
0hThe current temperature of the drive in ºC (binary value). If the temperature is less than 0, 0
is reported. If the temperature sensor is not functioning properly, FFh is reported.
1hThe maximum temperature in ºC (binary value) at which the drive can operate continuously
without degrading reliability and operation. This parameter is not supported so FFh is
returned.
PAMRPrevent/Allow Medium Removal bit
HIUHost Initiated Unload bit
MAccIf set, the MAM is accessible. MPrsnt must be set as well.
CmprCompress bit. If set, the DTD currently has data compression enabled.
WrtPWrite Protect bit. If set, the media in the DTD is physically write-protected. Only
valid if MPrsnt is set.
Commands80
Parameter Code (0000h)
HP restricted
Page 81
CRqstClean Requested bit
CRqrdCleaning Required. If set, head cleaning must be performed before normal data
operations are possible. This takes priority over CRqst, and both may be set at the
same time.
DInitDTD Initialized. When set, the data returned by the VHF parameter data is valid.
InXtnIn Transition. If 0, the DTD is in the state reflected by the rest of byte 5 and is not
attempting to leave this state. This bit must be 0 if RRqst is set.
RAARobotic Access Allowed. If set, robotic media access to the DTD is allowed.
MPrsntMedia Present bit (hardware sensor)
MStdMedia Seated. If set, the tape is mechanically seated, that it physical loading is
complete. Otherwise the tape is still threading.
MThrdMedia Threaded
DAccData Accessible. If set, the DTD has finished processing a load operation. The bit is
cleared to 0 at the beginning of the next unload operation.
Tape Motion
Status
RRqstRecovery Requested. Set to 1 as long as a recovery procedure is available. In these
IntfCInterface Changed. If set, the interface status has changed since the last time this
TAFCIf set, at least one TapeAlert Flag had Changed since the last time the TapeAlert
00h
01h
02h
03h
04h
05h
06h
07h
08h
09h–7Fh
80h–FFh
circumstances, InXtn must be 0.
page was retrieved. It is cleared to 0 when the page is retrieved for the initiator.
flags were retrieved.
No tape motion
Cleaning operation in progress
Tape being loaded
Tape being unloaded
Tape in motion
Reading
Writing
Locating
Rewinding
Reserved
Vendor unique
CurrTopCurrent Topology. Ignored when the PIC bit is set to zero.
0 The DT device primary port is currently operating in arbitrated loop mode.
1 The DT device primary port is currently operating in point-to-point mode.
Current SpeedThe bit rate at which the DT device primary port is currently operating. The
field is ignored when the PIC bit is set to zero. Valid values are:
000b
001b
010b
011b
100b–111b
1 Gbps
2 Gbps
4 Gbps
8 Gbps
reserved
LCLogin Complete
0 A login has not successfully completed through the PRLI phase on the DT
device primary port.
1 At least one initiator port has completed process login (PRLI) with the DT
device on the DT device primary port.
Conflict0 There is no AL_PA conflict.
1 Another device has the required Hard AL_PA, or no AL_PA is available for
the DT device primary port.
Signal0 A signal is not detected.
1 A signal is detected at the DT device primary port.
synchronized, or has not successfully completed the most recent Loop
Initialization Process.
1 The FC_Port state machine is in the
primary port is operating in point-to-point topology, or the most recent
Loop Initialization Process has completed successfully
Current N_Port IDThe 24-bit N_Port ID that is assigned to the DT device primary port. The field is
ignored when the PIC bit is set to zero.
Current FC_AL Loop IDThe loop identifier that is assigned to the DT device primary port. The field is
ignored when the PIC bit is set to zero or when the CurrTop bit is set to one.
TapeAlert Response log page
The TapeAlert Response log page is page 12h. There is only 1 parameter, which contains 64 flags.
For a list of supported flags, see the ”TapeAlert log page” on page 87.
7 6543 210
0Page Code (12h)
1Reserved 90)
2(MSB)
3(LSB)
4(MSB)
5(LSB)
6DU (1)DS (1)TSD (1)ETC (0)TMC (0)LBIN (1)LP (1)
7Parameter Length (08h)
8Flag 01hFlag 02h Flag 03h Flag 04h Flag 05h Flag 06h Flag 07h Flag 08h
9Flag 09hFlag 0Ah Flag 0Bh Flag 0Ch Flag 0Dh Flag 0Eh Flag 0Fh Flag 10h
10Flag 11hFlag 12h Flag 13h Flag 14h Flag 15h Flag 16h Flag 17h Flag 18h
11Flag 19h Flag 1Ah Flag 1Bh Flag 1Ch Flag 1Dh Flag 1Eh Flag 1Fh Flag 20h
12Flag 21hFlag 22h Flag 23h Flag 24h Flag 25h Flag 26h Flag 27h Flag 28h
13Flag 29h Flag 2Ah Flag 2Bh Flag 2Ch Flag 2Dh Flag 2Eh Flag 2FH Flag 30h
14Flag 31hFlag 32h Flag 33h Flag 34h Flag 35h Flag 36h Flag 37h Flag 38h
15Flag 39h Flag 3Ah Flag 3Bh Flag 3Ch Flag 3Dh Flag 3Eh Flag 3Fh Flag 40h
ACTIVE state and is not
ACTIVE state and the DT device
Page Length (000Ch)
Parameter Code (0000h)
Each flag is either zero to indicate the corresponding condition is deactivated or one to indicate
that the corresponding condition has been activated.
Flags are not cleared when the log is read. The log is cleared at power-on or on a reset condition.
Specific flags may be cleared when corrective action has removed the condition that caused the flag
to be activated.
Commands84
HP restricted
Page 85
Requested Recovery log page
The Requested Recovery log page is 13h. One parameter is supported:
Parameter CodeThe relative port identifier
PHY IdentifierThe same value as the Parameter Code
Negotiated
Physical Link Rate89
Invalid DWORD
1.5 Gbps
3.0 Gbps
Number of invalid DWORDS received outside of PHY reset sequences.
Count
Running Disparity
Error Count
Commands86
Number of DWORDS containing running disparity errors received outside the
PHY reset sequences.
HP restricted
Page 87
Loss of DWORD
synchronization
PHY Reset Problem
Count
NOTE: The counters are the only fields affected by a LOG SELECT command or the value of the PC
field in the
LOG SENSE command.
TapeAlert log page
NOTE: Reading the TapeAlert log clears the flags, as stipulated in the TapeAlert specification.
The TapeAlert log page is page 2Eh. There are 64 parameters numbered from 1 through 64. Only
parameters 1–18, 20–23, 29–39 and 55–60 have definitions for tape drives without attached
loaders. The remaining parameters are always zero.
The Parameter Control Byte value for each parameter is 40h.
All parameters are one byte long. Each parameter is either zero to indicate the corresponding
condition has not occurred or one to indicate that the corresponding condition has occurred. All log
parameters are cleared when the log is read. The Log is also cleared at power on, on a reset
condition and by a
removed the condition that caused the flag to be set.
Number of times the PHY restarted the link reset sequence because it lost
DWORD synchronization.
Number of times the PHY did not obtain DWORD synchronization during the
final SAS speed negotiation window.
Log Select command. Specific flags may be cleared when corrective action has
The supported parameters are as follows. The Set column indicates if the flag can be set by drives.
The other flags are supported but never set.
15Memory Chip in Cartridge FailureWarning
16Forced EjectCritical
17Read-Only FormatWarning
18Tape Directory CorruptedWarning
19Nearing Media LifeInformation
20Clean NowCritical
21Clean PeriodicWarning
22Expired Cleaning MediaCritical
23Invalid Cleaning CartridgeCritical
24Retension RequestedWarning
25Dual-port Interface ErrorWarning
26Cooling Fan FailureWarning
27Power Supply FailureWarning
28Power ConsumptionWarning
29Drive MaintenanceWarning
30Hardware ACritical
31Hardware BCritical
32InterfaceWarning
33Eject MediaCritical
34Download FaultWarning
35Drive HumidityWarning
36Drive TemperatureWarning
37Drive VoltageWarning
38Predictive FailureCritical
39Diagnostics RequiredWarning
50Lost StatisticsWarning
51Tape Directory Invalid at UnloadWarning
52Tape System Area Write FailureCritical
53Tape System Area Read FailureCritical
54No Start of DataCritical
55Loading FailureCritical
56Unrecoverable load FailureCritical
57Automation Interface FailureCritical
58Firmware FailureWarning
59WORM medium — integrity check failedWarning
60WORM medium — overwrite attemptedWarning
Commands88
HP restricted
Page 89
Tape Usage log page
The Tape Usage log page code is 30h. There are nine parameters. These are all read directly from
the LTO-CM Tape Usage Log.
This data relates to the current tape and can be neither reset nor written.
Parm. DescriptionLengthUpdated When
1Thread Count4Tape threaded
2Total Data Sets Written8Data set physically written
3Total Write Retries4Data set physically written
4Total Unrecovered Write Errors2Data set physically written
5Total Suspended Writes2Data set physically written
6Total Fatal Suspended Writes2Data set physically written
7Total Data Sets Read8Data set physically written
8Total Read Retries4Data set physically written
9Total Unrecovered Read Errors2Data set physically written
Tape Capacity log page
The Tape Capacity log page code is 31h. The Page Length is 20h. There are four parameters, 1
through 4. Parameters 2 and 4 are not supported and are returned as zero. All parameters are 4
bytes long. All parameters are in megabytes (1,048,576 bytes) and assume no compression. This
data relates to the current tape and can be neither reset nor written.
The supported parameters are as follows:
Parm. DescriptionLengthUpdated When
1Main Partition Remaining Capacity4Data set physically written
2Alternate Partition Remaining Capacity4n/a
3Main Partition Maximum Capacity4If Set Capacity succeeds
4Alternate Partition Maximum Capacity4n/a
Data Compression log page
The Data Compression log page code is 32h and the page length is 4Ch. There are ten
parameters, 0 through 9. Parameters 0 and 1 are two bytes long. Parameters 2 through 9 are each
4 bytes long.
The supported fields are listed below. Parameters 2 through 9 occur as pairs that represent a large
number of bytes transferred. The first four-byte parameter represents the number of whole megabytes
transferred, rounded to the nearest megabyte. The second four-byte parameter represents the
difference between this number of megabytes and the actual number of bytes. This may be a signed
quantity.
This data relates to the current tape and is cleared at the start of tape load. It may not be written.
Parameter DescriptionLengthUpdated When
0Read compression ratio X 1002Data set logically read
1Write compression ratio X 1002Data set logically written
2Megabytes transferred to host4Data set logically read
3Bytes transferred to host4Data set logically read
4Megabytes read from tape4Data set logically read
5Bytes read from tape4Data set logically read
6Megabytes transferred from host4Data set logically written
7Bytes transferred from host4Data set logically written
8Megabytes written to tape4Data set logically written
9Bytes written to tape4Data set logically written
Device Wellness Log page
The Device Wellness Log page has page code 33h and consists of a FIFO parameter code list of
the last 16 drive error conditions caused by various sense keys.
However, to enable connectivity to the peripheral management tools only, the page structure has
been implemented, but all parameter values returned by the drive will be zero.
The Performance Data log page is 34h. This log is intended to report data of interest to a
user/application on how efficiently the drive is being used.
Parameter DescriptionLength Updated
0Repositions per 100 MB2After each 100 MB has been physically written
1Data rate into buffer2After each data set has been logically written
2Maximum data rate2After each data set has been logically written
3Current data rate2After each data set has been logically written
4Native data rate2Fixed
The Parameter Control Byte is 60h for all the parameters.
All the parameters relate to the current tape. They are all cleared at the start of tape load, except
Parameter 4, which is never cleared. All data will be reset when the log page is reset. The
parameters are as follows.
Repositions per
100 MB
Data rate into
buffer
Maximum data
rate
Current data
rate
Native data rate The native rate (that is, without using compression) at which the drive writes data
Number of tape direction changes per 100 MB written. The higher the figure the
more wear occurs.
Rate at which data is entering the buffer (after data compression), given in units
of 100 KB/s. This is the true ‘tape’ data rate.
Given the compressibility of the data that has been sent to the drive, this is the
maximum data rate that could be achieved, given in units of 100 KB/s. The
figure is calculated based on the compressibility of each dataset received, and
datasets that have a compressibility greater than the compression bandwidth of
the drive will be ‘capped’.
Rate at which data is being accepted by the drive before compression, given in
units of 100 KB/s.
to tape, given in units of 100 KB/s:
DriveValue Native Data Rate
LTO 404B0h 120 MB/s NOTE: These figures are for native
Device Status log page
The Device Status log page is 3Eh, with a page length of 28h. PCB = Parameter Control Byte.
Parameter DescriptionLength UpdatedPCB
0Device Type4Obsolete. Set to all zeros.40h
1Device Status Bits4Used to provide remote status of selected
media types and will vary when
earlier format media is loaded
40h
monitoring points on the drive. See below for
the format.
2Total Number of Loads4Number of loads/unloads over the life of the
60h
device.
3Cleaning Cartridge
Status
4Accumulated number of uses of the last
cleaning cartridge. Updated after the tape is
40h
loaded and a cleaning event attempted. If
there is no value, FFFFFFFFh is returned.
4Product Number4Unique number that identifies the product40h
Device Status Bits
The parameter has the following format:
76543210
0Reserved (0)CRQCRECT
1Reserved (0)TemperatureDevice Status
2Reserved (0)Medium Status
5Reserved (0)
CRQCleaning Required flag
CRCleaning Requested flag
ECTExhausted Cleaning Tape flag
Temperature00b
Field not supported
Temperature OK
01b
Temperature degraded
10b
Temperature failed
11b
Device StatusThe overall status of the drive:
Field not supported
00b
Device status OK
01b
Device status degraded
10b
Device status failed
11b
Medium Status The overall status of the tape cartridge:
Field not supported
00b
Medium status OK
01b
Medium status degraded
10b
Medium status failed
11b
Commands92
HP restricted
Page 93
MODE SELECT 15h/55h
MODE SELECT is used to send configuration data to the drive. Both 6-byte and 10-byte versions of
the command are supported.
The Mode Select parameter list is transferred from the host to the drive during the data-out phase. It
contains zero or more bytes of information. If any information is sent, it should consist of a Mode
Parameter Header followed by zero or more mode select pages. Internal parameters are set
according to the values specified in the header and pages. Fields in the parameter list are checked
and the operation will terminate if an error is found.
NOTE: The drive does not check that the parameter list is correct before modifying internal
parameters. The list is checked as the operation proceeds, so if there is an error in the list, all
parameters up to that point will be set to their new values, but the parameter in error and later
parameters will not be updated.
NOTE: Failure to flush write-behind data will be reported as a Deferred Error.
The parameter list length must be such that only “entire” parts of a parameter list are sent. It is illegal
to send a partial mode parameter header, a partial mode block descriptor or a partial mode page.
If this happens, then
The additional sense is set to 1A00h (parameter list length error).
CHECK CONDITION status is reported. The sense key is set to ILLEGAL REQUEST.
Extra checks may be performed on the data, see the descriptions for the parameter list for more
details.
MODE SELECT parameter data is not SCSI-2 mode page compatible. Only
the parameter header and block descriptor may be sent.
1The parameter data is SCSI-2 mode-page compatible.
SPSave Pages
0This bit is not supported and must be zero.
Parame ter List
Length
0No data is transferred.
>0 The length in bytes of the
MODE SELECT parameter list to be transferred.
Specific status
Following a successful Mode Select command, Unit Attention status is posted to all initiators other
than the initiator of the Mode Select command. The sense key is set to
sense is set to 2A01h (mode parameters changed).
UNIT ATTENTION. Additional
Mode parameter pages
Mode data is recovered from the drive by means of a MODE SENSE command. After modification, it
is returned to the drive via a
SENSE
and return whatever MODE SELECT data suits them into the drive.
Mode page representation
Certain conventions are used in the following Mode Parameter pages in order to describe the nature
of the parameters. Most parameters are given by name, followed by a number in brackets. The
brackets have the following meanings:
Square brackets [ ] Square brackets indicate that the parameter may be modified. The number
inside the brackets is the default value for the field—in other words, the
power-up or reset value.
• M
• M
• M
• M
Commands94
MODE SELECT command. In real-life, many hosts do not use MODE
ODE SELECT may modify this value by sending the page with a new value
in the field.
ODE SENSE (current values) will return the current value of the parameter.
ODE SENSE (default values) will return the value in brackets [].
ODE SENSE (changeable values) will return a value of all ones.
HP restricted
Page 95
Round brackets ( ) Round brackets indicate that the parameter is fixed. The number inside the
Mode data format
Mode data consists of a 4-byte header, optionally followed by block descriptor and Mode
Parameter pages:
76543210
1(MSB)
3(LSB)
4(MSB)
11(LSB)
12(MSB)
n(LSB)
Mode parameter pages
HP LTO Ultrium drives support the following pages:
brackets is the fixed value for the field.
• M
ODE SELECT must set the parameter to this value, otherwise CHECK
CONDITION
will be reported with a sense key of ILLEGAL REQUEST.
• MODE SENSE (default values) will return the fixed value.
• M
ODE SENSE (changeable values) will return a value of all zeros.
Mode Parameter Header
Mode Block Descriptor
Mode Parameter Pages
• 01h “Read-Write Error Recovery mode page” on page 98
• 02h “Disconnect-Reconnect page” on page 99
• 0Ah “Control mode page” on page 102
• 0Fh “Data Compression Characteristics page” on page 103
• 10h “Device Configuration page” on page 104
• 11h “Medium Partitions mode page” on page 106
• 18h FC drives: “Protocol-Specific Logical Unit mode page (FC drives)” on page 107
• 18h SCSI drives:“Protocol-Specific Logical Unit mode page (SCSI drives)” on page 108
• 18hSAS drives: “Protocol-Specific Logical Unit mode page (SAS drives)” on page 108
• 19h FC drives: “Protocol-Specific Port mode page (FC drives)” on page 108
• 19h SCSI drives:“Protocol-Specific Port mode page (SCSI drives)” on page 112
• 19h SAS drives“Protocol-Specific Port mode page (SAS drives)” on page 116
• 1Ah “Power Condition mode page” on page 119
• 1Ch “Information Exceptions mode page” on page 120
• 1Dh “Medium Configuration mode page” on page 121
• 3Bh “Serial Number Override vendor-unique mode page” on page 122
Mode Data Length field must be zero.
Mode Data Length field is set to the number of bytes of data
available to return excluding itself (in other words, the number of
actual bytes available is mode data length + 1 for 6-byte
SENSE
or +2 for 10-byte MODE SENSE).
MODE
NOTE: The actual amount returned may be truncated to the
allocation length for the command.
HP restricted
Page 97
Medium Type00h The usual medium type when the drive is in normal tape drive mode.
01h WORM media is loaded.
80h The tape drive is in CD-ROM emulation mode for OBDR.
WPWrite Protect. Ignored for
0M
ODE SENSE: The tape is write-enabled
1M
ODE SENSE: The tape is write-protected
Buffered Mode0The drive will not report
MODE SELECT.
GOOD status on Write and Write Filemarks
commands until all data (blocks and filemarks) has been successfully
written to tape.
1The drive will report
GOOD status for Write and Write Filemarks commands
as soon as all the data or marks specified in the command have been
transferred to the data buffer. Data for multiple commands from different
initiators may be buffered. This is the default value.
NOTE: It is strongly recommended that this field is set to 1, otherwise
there will be significant performance penalties. A method of flushing the
buffer to tape without changing logical position is available with the
Write Filemarks command.
2The drive will report
GOOD status for Write and Write Filemarks commands
as soon as all the data or marks specified in the command have been
transferred to the data buffer and all buffered data from different
initiators has been successfully written to the tape.
Speed0The Speed field is not used and should be zero.
Block Descriptor
Length
Only the values 0 and 8 are valid. Any value other than 0 or 8,
CONDITION
status is reported. See the Parameter List check for details of the
CHECK
sense data generated.
0No block descriptor is being transferred.
8The Mode Parameter header must be followed by the 8-byte block
descriptor described in the next section.
Mode block descriptor
The format of the Mode Parameter block descriptor is as follows:
0 This parameter is not supported and should be zero.
HP restricted
Page 100
Maximum Burst
Size
EMDP0 Enable Modify Data Pointers is not facilitated by the drive. The drive will
FAAThis bit, together with FAB and FAC, indicate whether the drive will use
FAB1 The drive will use fairness when arbitrating to send FCP_XFER_RDY
FAC1 The drive will use fairness when arbitrating to send an FCP_RSP frame.
NOTE: If the host does not grant disconnect privilege in its IDENTIFY message these parameters
become meaningless. The drive will stay connected on the bus for the duration of an operation or
until the host sends a mid-operation
SCSI drives
>0 The maximum amount of data that will be transferred during a data-in or
data-out phase before disconnecting. This field is in units of 512 bytes.
The maximum burst size that the drive supports is 127 (7Fh) blocks of
512 bytes, that is, 64 KB less 512 bytes.
0 The drive may send bursts of any size. This is the default value.
always have continually increasing and contiguous data relative offset
values for FCP_DATA.
fairness arbitration to send frames to the initiator.
0 The drive will not use fairness when arbitrating to send FCP_DATA frames.
1 The drive will use fairness when arbitrating to send FCP_DATA frames.
frames.
IDENTIFY granting disconnect privilege.
The Disconnect-Reconnect page has the following format for SCSI drives:
7 6 543210
0PS (0)Rsvd (0)Page Code {02h}
1Additional Page Length {0Eh}
2Buffer Full Ratio (0)
3Buffer Empty Ratio (0)
4(MSB)
5(LSB)
6(MSB)
Bus Inactivity Limit (0)
Disconnect Time Limit [0]
7(LSB)
8(MSB)
9(LSB)
10(MSB)
11(LSB)
Connect Time Limit (0)
Maximum Burst Size [0]
12Reserved (0)DTDC (0)
13–15Reserved (0)
Commands100
HP restricted
Loading...
+ 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.