HP C737990900 Product manual

the SCSI
interface
hp ultrium drives
technical reference manual
generation 2 SCSI and FC drives
volume 3: the SCSI interface
Part Number: C7379–90900 Volume 3
Edition 4, February 2003

2
Notice
The information contained in this
document is subject to change
without notice.
Hewlett-Packard 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 direct, indirect,
special, incidental or consequential
damages in connection with the
furnishing, performance, or use of
this document.
Revision History
This document contains proprietary
information which is protected by
copyright. All rights reserved. No
part of this document may be
photocopied, reproduced or
translated to another language
without the prior written consent of
Hewlett-Packard.
© Copyright 2000–2003 by
Hewlett-Packard Limited
Version Date Changes
Edition 1 Nov. 2000 All
Edition 2 Mar. 2001 Addition of Read and Write attribute commands and Drive Error Codes
Edition 3 May 2002 Inclusion of the Request Block Address command and the Control mode
page, together with numerous small changes
Edition 4 Feb 2003 Generation 2 SCSI and FC drive version
This document is frequently revised and updated. To find out if there is a
later version, please ask your HP OEM Representative.

3
The Purpose of this Manual
This is one of five volumes that document HP Ultrium drives. This volume
provides background information for driver and application developers. The
following products are covered. Capacities are when the drive is using data
compression with a compression ratio of 2:1, where applicable:
■HP Ultrium Generation 2 Full-Height SCSI Internal Drive
■HP Ultrium Generation 2 Full Height FC Internal Drive
Note Throughout this manual frequent reference is made to SCSI
commands. For more information on SCSI commands for
HP Ultrium drives see volume 3, the SCSI Interface, of the
HP Ultrium Technical Reference Manual. Ordering details are
given below.
Related Documents
The following documents provide additional information:
Documents Specific to HP Ultrium Drives
■Hardware Integration Guide, volume 1 of the HP Ultrium Technical
Reference Manual
■The SCSI Interface, volume 3 of the HP Ultrium Technical Reference
Manual
■Specifications, volume 4 of the HP Ultrium Technical Reference Manual
■HP Ultrium Configuration Guide, volume 5 of the HP Ultrium Technical
Reference Manual
■Background to Ultrium Drives, volume 6 of the HP Ultrium Technical
Reference Manual
Please contact your HP supplier for copies.
■The features and benefits of HP Ultrium drives are discussed in the
HP Ultrium Technology White Paper.
■For a general backgrounder on LTO technology and licensing, go to
http://www.lto-technology.com.

4
Documentation Map
The following will help you locate information in the 6-volume Technical
Reference Manual:
Drives—general
Installation and Configuration
Operation
SCSI Drives FC Drives
Connectors 1HW Integration: ch. 7 1HW Integration: ch. 4
Controller architecture 6Background: ch. 4
Front Panel LEDs 1HW Integration: ch. 6 1HW Integration: ch. 3
Mechanism and hardware 6Background: ch. 3
Specifications 4Specs
SCSI Drives FC Drives
Connectors 1HW Integration: ch. 7 1HW Integration: ch. 4
Determining the configuration 2SW Integration: ch. 2 2SW Integration: ch. 2
External drives (SCSI only) 1HW Integration: ch. 5n/a
In Libraries 1HW Integration: ch. 1
In Servers (SCSI only) 1HW Integration: ch. 4n/a
In Tape Arrays (SCSI only) 1HW Integration: ch. 3n/a
Modes of Usage (SCSI only) 1HW Integration: ch. 8n/a
Optimizing performance (SCSI only) 1HW Integration: ch. 8n/a
2SW Integration: ch. 4
UNIX configuration 5UNIX Config
SCSI Drives FC Drives
External drives (SCSI only) 1HW Integration: ch. 5n/a
In Libraries 1HW Integration: ch. 1
In Servers (SCSI only) 1HW Integration: ch. 4n/a
In Tape Arrays (SCSI only) 1HW Integration: ch. 3n/a

5
Cartridges
Interface
Maintenance and Troubleshooting
SCSI Drives FC Drives
Cartridge Memory (LTO-CM) 2SW Integration: ch. 5
6HW Integration: ch. 5
Cartridges 1HW Integration: ch. 9 1HW Integration: ch. 5
Features 6HW Integration: ch. 5
Managing the use of cartridges 2SW Integration: ch. 1
Use of cartridges 2SW Integration: ch. 3
SCSI Drives FC Drives
SCSI Guide 3SCSI
Commands 3SCSI: ch. 4
Error codes 1HW Integration: ch. 10 1HW Integration: ch. 6
Implementation 3SCSI: ch. 1
Interpreting sense data 2SW Integration: ch. 3
Messages 3SCSI: ch. 2
Mode pages
—see the MODE SENSE command 3SCSI: ch. 4
Pre-execution checks 3SCSI: ch. 3
Responding to Sense Keys and ASC/Q 2SW Integration: ch. 6
Sense Keys and ASC/Q
—see REQUEST SENSE command 3SCSI: ch. 4
SCSI Drives FC Drives
Cleaning 2SW Integration: ch. 5
2SW Integration: ch. 7
External drives (SCSI only) 1HW Integration: ch. 5n/a
In Libraries 1HW Integration: ch. 1
In Servers (SCSI only) 1HW Integration: ch. 4n/a
In Tape Arrays (SCSI only) 1HW Integration: ch. 3n/a
Monitoring drive and tape condition 2SW Integration: ch. 7
Software troubleshooting techniques 2SW Integration: ch. 1

6
Dealing with Errors
Ultrium Features
SCSI Drives FC Drives
Error Codes 1HW Integration: ch. 10 1HW Integration: ch. 6
Handling errors 2SW Integration: ch. 5
How error correction works 6Background: ch. 4
Logs—see the LOG SENSE command 3SCSI: ch. 4
Recovering from write and read errors 2SW Integration: ch. 7
Software response to error correction 2SW Integration: ch. 3
Software response to logs 2SW Integration: ch. 3
TapeAlert log 2SW Integration: ch. 7
SCSI Drives FC Drives
Adaptive Tape Speed (ATS) 6Background: ch. 1
Autoload 1 HW Integration: ch. 2
Automation Control Interface (ACI) 1 HW Integration: ch. 2
6 Background: ch. 1
Cartridge Memory (LTO-CM)s 1 HW Integration: ch. 2
2SW Integration: ch. 5
6HW Integration: ch. 5
Data Compression, how it works 6Background: ch. 5
Data Compression, managing 2SW Integration: ch. 5
Design principles 6Background: ch. 1
OBDR and CD-ROM emulation 6Background: ch. 1
2SW Integration: ch. 7
Performance optimization 1HW Integration: ch. 8n/a
2SW Integration: ch. 1
Performance, factors affecting 2SW Integration: ch. 4
Software design 2SW Integration: ch. 1
Supporting Ultrium features 2SW Integration: ch. 5
Ultrium Format 6Background: ch. 2

7
General Documents and Standardization
■Small Computer System Interface (SCSI-1), ANSI X3.131-1986. This is the
ANSI authorized standard for SCSI implementation, available through
ANSI
■Enhanced Small Computer System Interface (SCSI-2), ANSI X3T9.2-1993
Rev. 10L, available through ANSI
Copies of General Documents can be obtained from:
ANSI 11 West 42nd Street
New York, NY 10036-8002
USA
ISO CP 56
CH-1211 Geneva 20
Switzerland
ECMA 114 Rue du Rhône
CH-1204 Geneva
Switzerland
Tel: [phone]
Web URL: http://www.ecma.ch
Global Engineering Documents 2805 McGaw
Irvine, CA 92714
USA
Tel: [phone] or 714 261 1455

8

Contents 9
The Purpose of this Manual 3
Related Documents 3
Documents Specific to HP Ultrium Drives 3
Documentation Map 4
General Documents and Standardization 7
1Interface Implementation 13
The SCSI Interface 13
Supported Messages 14
Supported Commands 14
SCSI Features 15
Design Approach 15
Power-On 15
Reset Strategy 15
Abort Handling 16
Bus Parity Errors (Parallel SCSI only) 18
Disconnect Strategy (Parallel SCSI only) 19
Multi-Initiator Support 19
Fibre Channel Operation 20
Fibre Channel Addressing 20
Names 20
Addresses 21
HP’s Implementation of Names and Addresses 21
Implications for Libraries 22
Field Replaceable Units 23
Descriptions of Signals (Parallel SCSI only) 23
contents
Contents

10 Contents
2Messages 25
Message Out Support (Parallel SCSI only) 25
Message In Support (Parallel SCSI only) 26
Extended Message Support 27
Status 29
3Commands—Introduction 31
Summary 31
Command Details 32
Pre-Execution Checks 32
Bad LUN Check 32
Deferred Error Check 33
Diagnostic Status Check 33
Fixed Bit Check 34
Flag Link Check 34
Illegal Command Check 34
Illegal Field/Request Check 34
Media Access Check 35
Media Information Check 36
Media Write Check 37
Parameter List Check 37
Reservation Check 37
Unit Attention Check 38
Command Descriptor Block 38
4Commands 41
ERASE 19h 42
INQUIRY 12h 44
INQUIRY Data Pages 45
Vital Product Data Pages 49
Supported Vital Product Data Pages Page 49
Unit Serial Number Page 50
Device Identification Page 51
Defined Identifiers 52
Drive Component Revision Levels Pages 53
LOAD/UNLOAD 1Bh 55

Contents 11
Contents
LOCATE 2Bh 58
LOG SELECT 4Ch 60
LOG SENSE 4Dh 62
Log Page Format 63
Supported Log Pages Page 64
Write Error Counters Log Page 65
Read Error Counters Log Page 66
Sequential Access Device Log Page 66
TapeAlert Log Page 67
Tape Usage Log Page 69
Tape Capacity Log Page 69
Data Compression Log Page 70
Performance Data Log Page 70
MODE SELECT 15h/55h 72
Mode Parameter Pages 74
Mode Page Representation 74
Mode Data Format 74
Mode Block Descriptor 77
Read-Write Error Recovery Mode Page 78
Disconnect-Reconnect Page 79
SCSI Drives 79
FC Drives 80
Control Mode Page 81
Data Compression Characteristics Page 82
Device Configuration Page 83
Medium Partitions Mode Page 85
Fibre Channel Logical Unit Control Mode Page 86
Fibre Channel Port Control Mode Page 87
Information Exceptions Mode Page 89
MODE SENSE 1Ah/5Ah 91
PREVENT/ALLOW MEDIUM REMOVAL 1Eh 94
READ 08h 95
READ ATTRIBUTE 8Ch 99
MAM Attribute Data 103
Attribute ID Values 104
Device Common Attributes 104
Medium Common Attributes 106

12 Contents
Host Common Attributes 107
READ BLOCK LIMITS 05h 110
READ BUFFER 3Ch 111
READ POSITION 34h 115
RECEIVE DIAGNOSTICS RESULTS 1Ch 119
RELEASE UNIT 17h/57h 121
REPORT DENSITY SUPPORT 44h 123
REPORT LUNS A0h 126
REQUEST SENSE 03h 128
Request Sense Data 129
Sense Data Management 131
Current Sense 132
UNIT ATTENTION Sense 132
DEFERRED ERROR Sense 133
Sense Keys 135
Additional Sense Codes 136
Error Codes 140
RESERVE UNIT 16h/56h 141
REWIND 01h 144
SEND DIAGNOSTIC 1Dh 145
Standard Self-Test 147
SPACE 11h 148
TEST UNIT READY 00h 151
VERIFY 13h 152
WRITE 0Ah 154
WRITE ATTRIBUTE 8Dh 157
WRITE BUFFER 3Bh 160
WRITE FILEMARKS 10h 164
Glossary 165
Index 169

Interface Implementation 13
Interface Implementation
HP Ultrium drives use SCSI-3 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 and of commands in
Chapter 3 and Chapter 4.
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 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
■Ultra3 wide SCSI
■Conformance to the following SCSI standards:
—SAM-2 T10/1157-D rev.23
—SPI-3 ANSI NCITS.336:2000
—SPC-2 ANSI NCITS.351:2001
—SSC ANSI NCITS.335:2000
1

14 Interface Implementation
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)
■RESTORE POINTERS
■SAVE DATA POINTER
■Extended Message: PARALLEL PROTOCOL REQUEST
■Extended Message: SYNCHRONOUS DATA TRANSFER REQUEST
■Extended Message: WIDE DATA TRANSFER REQUEST
For implementation details on these messages, see Chapter 2, “Messages”
Supported Commands
The following commands are supported by the drives. They include all
Mandatory and Extended commands and most Optional commands.
19h ERASE 57h/17hRELEASE UNIT
12h INQUIRY 03h REQUEST SENSE
1Bh LOAD/UNLOAD 44h REPORT DENSITY SUPPORT
2Bh LOCATE A0h REPORT LUNS
4Ch LOG SELECT 56h/16hRESERVE UNIT
4Dh LOG SENSE 01h REWIND
15h/55h MODE SELECT 1Dh SEND DIAGNOSTIC
1Ah/5AhMODE SENSE 11h SPACE
1Eh PREVENT/ALLOW MEDIUM REMOVAL 00h TEST UNIT READY
08h READ 13h VERIFY
05h READ BLOCK LIMITS 0Ah WRITE

Interface Implementation 15
Interface Implementation
For implementation details on these commands, see Chapter 3, “Commands—
Introduction” and Chapter 4, “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 SCSI-3 specification and supports
all features required by that standard. However, since most tape drive support
software has been written using the SCSI-2 standard, this document is based
on SCSI- 2 and uses SCSI-2 terminology. Since SCSI-2 is virtually a compliant
subset of SCSI-3, this is not inconsistent. However, where SCSI-3 makes an
option in SCSI-2 a requirement, the SCSI-3 requirement is always used. Also,
all required SCSI-3 extensions are supported by the drive.
Power-On
The drive will respond to TEST UNIT READY, INQUIRY, REPORT LUNS and
REQUEST SENSE commands within 5 seconds of power on. The first command
other than Inquiry or Request Sense from any initiator will get a CHECK
CONDITION status with UNIT ATTENTION sense data for the power on. After
this, any medium access command will be reported with a sense key of NOT
READY and additional sense of 3E00h (LUN has not self-configured yet).
Medium access commands will be reported with additional sense of 0401h
(drive in process of becoming ready).
Reset Strategy
Soft Resets On receiving a reset through the Host Interface (SCSI or FC), the Host Interface
is returned to a known base state. If the reset command is received over the
Automation Controller Interface serial port, the SCSI and ACI interfaces are
returned to known base states. The baud rate for the port will be returned to its
3Ch READ BUFFER 3Bh WRITE BUFFER
34h READ POSITION 10h WRITE FILEMARKS
1Ch RECEIVE DIAGNOSTIC RESULTS

16 Interface Implementation
default setting. The known base state is defined in the SCSI-3 specification and
includes the following:
■The current I/O process is aborted.
■Any queued I/O processes from other initiators are removed.
■All reservations are cleared.
■All mode values are reset to their defaults.
■Synchronous/Wide negotiations are cleared (SCSI drives only).
■A UNIT ATTENTION condition is set.
■Any buffered writes are flushed to tape.
■The logical position is undefined.
The drive will be able to respond to TEST UNIT READY, INQUIRY, REQUEST
SENSE and REPORT LUNS within 250 ms of the reset line being released. The
first command other than these from any initiator will get a CHECK
CONDITION status with UNIT ATTENTION sense data for the reset. However,
other commands may not be processed until the internal state of the drive has
been reset. Any commands which cannot be processed will be accepted and
queued until the drive is ready to process them.
Hard Resets 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
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, then the bus is set to bus free and the processing
below is carried out.
If an abort condition is detected during status phase, the bus is set to bus free.
If a command, other than TEST UNIT READY, INQUIRY and REQUEST SENSE, is
received after the abort but before the drive is ready to process the command,
the drive will disconnect and wait until the abort processing has completed
before executing the command. A TEST UNIT READY command will report with

Interface Implementation 17
Interface Implementation
GOOD status immediately. A REQUEST SENSE command will give NO SENSE.
An INQUIRY command will return the required data and give GOOD status.
Command Abort Processing
ERASE Long erase is aborted as quickly as possible without corrupting tape format.
Short erase completes.
INQUIRY None
LOAD/UNLOAD Load completes and logically positions tape at BOT. Unload is aborted
leaving logical position at BOT unless operation is past the “point of no
return” in which case the tape is ejected.
LOCATE The logical position is set back to that at the start of the operation unless the
operation is past its “point of no return”, in which case the operation
completes.
LOG SELECT If data transfer is complete, command is completed, otherwise, no action is
taken
LOG SENSE None
MODE SELECT If data transfer is complete, command is completed, otherwise, no action is
taken.
MODE SENSE None
PREVENT/ALLOW
MEDIUM REMOVAL The command completes.
READ The current position is set to the first record boundary at or after the start of
the current data burst.
READ BLOCK LIMITS None
READ BUFFER None
READ POSITION None
RECEIVE DIAGNOSTICS
RESULTS None
RELEASE UNIT The command completes.
REQUEST SENSE None

18 Interface Implementation
Bus Parity Errors (Parallel SCSI only)
On detecting a bus parity error during a Command or Data Out phase or
receiving an Initiator detected error message during a Data In or Status phase,
the drive attempts to retry the bus phase. A Restore Pointers message is sent to
the initiator and the transfer is repeated. Only one retry is attempted. If the
retry fails or the restore pointers message is rejected, then the drive goes to
status phase and attempts to report CHECK CONDITION status. If this fails with
an initiator detected error message, the drive goes to bus free. The sense key is
set to ABORTED COMMAND with additional sense of 4A00h (command phase
error) or 4B00h (data phase error).
If an Initiator Detected Error or Message Parity Error message is received
during Message In phase, the initiator has detected an error in the message.
The drive will go to Message In and resend the message that was in error. If the
subsequent message is rejected with an Initiator Detected Error, then the drive
goes to Status phase and sends CHECK CONDITION status. The sense key is set
RESERVE UNIT The command completes.
REWIND The command completes.
SEND DIAGNOSTIC Vendor Unique
SPACE The logical position is set back to that at the start of the operation unless the
operation has passed its “point of no return”, in which case the operation
completes.
TEST UNIT READY None
WRITE The data up to first record boundary in the current burst is written to tape.
Any subsequent data is discarded. If there is no record boundary in the
current burst, the record is truncated to the amount of data transferred and
written to tape.
WRITE BUFFER If data transfer is complete, command is completed, otherwise, no action is
taken.
WRITE FILEMARKS The command completes.
VERIFY The logical position is set to the next record boundary after the point where
the verify was aborted.
Command Abort Processing

Interface Implementation 19
Interface Implementation
to ABORTED COMMAND with additional sense of 4800h (Initiator Detected
Error).
If the subsequent message is rejected with an Message Parity Error, then the
drive goes to Status phase and sends CHECK CONDITION status. The sense key
is set to ABORTED COMMAND with additional sense of 4300h (message
error).
On detecting a bus parity error during a Message Out phase, the drive will
handshake in all message bytes until ATN is deasserted. It will then stay in
Message Out phase to indicate to the initiator that the whole Message Out
phase should be resent.
Disconnect Strategy (Parallel SCSI only)
The disconnect strategy used by the drive is based on the assumption of
maximizing bus utilization for large sequential data transfers from a large data
buffer. The drive will disconnect whenever it believes that it will provide better
bus utilization. This may be between command and data phases, between
bursts of data or before sending status. However, the drive will guarantee that
it will send 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.
Multi-Initiator Support
All drives will support at least two initiators on the same bus. If more initiators
are supported, all features are supported for the supported number of
initiators.
The drive supports untagged queueing when operating with multiple initiators.
If a command from one initiator is being processed when a command, other
than TEST UNIT READY, INQUIRY, REPORT LUNS and REQUEST SENSE, is
received from a second initiator, then the drive will disconnect and the new
command is queued. Commands other than these from different initiators are
always executed in strict order of receipt. If the queue is full or disconnect
privilege is not granted in the new command, the drive will report BUSY status.
TEST UNIT READY, INQUIRY, REPORT LUNS and REQUEST SENSE commands are
always processed immediately, irrespective of whether a command from
another initiator is being processed.
The drive will maintain sense data for the supported number of initiators. If an
additional initiator connects to the drive, the drive will erase all sense data for

20 Interface Implementation
the initiator that least recently connected before processing the command for
the new initiator. See “Sense Data Management” on page 131 for more
details.
Fibre Channel Operation
Note This applies only to Fibre Channel drives.
The following sections have information specific to Fibre Channel operation:
■“Fibre Channel Logical Unit Control Mode Page” on page 86
■“Fibre Channel Port Control Mode Page” on page 87
■“Vital Product Data Pages” on page 49
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 typically used for identifying the
device to operating systems, since addresses are assigned dynamically. There
at least eight different name formats distinguished by the Network Address
Authority (NAA). Only one is used on HP Ultrium drives. This is the IEEE
Registered Name (NNA=5) and has the following format:
This name is made up of three fields:
■NAA Identifier (4 bits). “5” indicates a IEEE Registered Name.
■IEEE Company ID (24 bits). Assigned by IEEE to the company.
■Vendor Specified ID (36 bits). Assigned by the company.