Quantum, the Quantum logo, and the DLTtape logo are trademarks of Quantum Corporation
registered in the U.S.A. and other countries. DLTtape, DLTSage, and Super DLTtape are
trademarks of Quantum Corporation.
Other company and product names used in this document are trademarks, registered trademarks, or
service marks of their respective owners.
Legal Disclaimers
The information contained in this document is the exclusive property of Quantum Corporation.
Quantum retains its copyright on the information contained herein in all cases and situations of
usage, including derivative works. The possessor agrees to safeguard this information and to
maintain it in confidence and not re-publish it in whole or in part without Quantum’s prior written
consent.
SDLT 600 Fibre Channel Interface Guide
Quantum reserves the right to make changes and improvements to its products, without incurring
any obligation to incorporate such changes or improvements in units previously sold or shipped.
Contact Information
You can request Quantum publications from your Quantum Sales Representative or order them
directly from Quantum.
Telephone numbers and street addresses change frequently; for the latest, up-to-date contact
information, visit:
www.quantum.com
Telephone numbers, street addresses, time zones, and other pertinent facts are listed in the
Support section of the web site.
ii
SDLT 600 Fibre Channel Interface Guide
Revision History
All revisions made to this document are listed below in chronological order.
Document ReleaseDateSummary of Changes
A01October 10,
2003
A02July 9, 2004Maintenance release. All functions and features of the V25
This reference guide is a comprehensive source of information about the Fibre Channel Protocol (FCP)
for SCSI used by the Super DLTtape™-generation (SDLT) tape drives. Implementation of the FCP
standard enables the transmission of standard SCSI command formats, data, and parameters, and the
receipt of SCSI status and sense information across a Fibre Channel network using the standard Fibre
Channel frame and sequence formats. The SDLT tape drive implementation of FCP operates with
Fibre Channel Class of Service 3 and operates across Fibre Channel fabrics and arbitrated loops.
This document is written for original equipment manufacturers (OEMs) that are integrating the
Quantum SDLT tape drive into a system or subsystem. Background knowledge of the SCSI-3, FCP,
SAM, SSC, SPC, and SPI standards is assumed.
This document’s primary audience is the OEM technical system integrators who are responsible for the
FCP interface. In addition, technically astute end-users can use this manual for installation and
operation of the tape drive, although that group is a secondary audience.
Related DocumentsSDLT 600 Fibre Channel Interface Guide
1.3Related Documents
•SDLT 600 SCSI Interface Guide (81-81200-01)
•SDLT 600 Product Manual (81-81184-01)
•Current standards documents available from www.t10.org:
Fibre Channel Protocol for SCSI (FCP)
SCSI Architecture Model (SAM)
SCSI Primary Commands (SPC)
SCSI Parallel Interface (SPI)
SCSI Stream Commands (SSC)
1.4Structure of this Manual
•Chapter 1, Introduction, is the chapter you are currently reading.
•Chapter 2, Fibre Channel Protocol and SCSI, provides an overview of SDLT tape drive-
specific information about transmitting SCSI commands using the Fibre Channel Protocol (FCP).
Background knowledge of the SCSI-3, FCP, SAM, SSC, SPC, and SPI standards is assumed.
•Chapter 3, SCSI Commands, describes in detail each command supported by SDLT tape drives
using FCP. The SCSI command system enables a Fibre Channel port acting as a SCSI initiator to
direct an SDLT tape drive located on another Fibre Channel port to perform a wide range of
operational and diagnostic functions. This chapter also provides Sense Key and Additional Sense
Code information for the REQUEST SENSE and SEND DIAGNOSTIC SCSI commands as well
as density codes for the MODE SELECT and MODE SENSE commands.
This manual uses the following conventions to designate specific elements:
Table 1-1. Typographical Conventions
ElementConventionExample
CommandsUppercase (unless case-
sensitive)
Hexadecimal NotationNumber followed by
lowercase h
Binary NotationNumber followed by
lowercase b
Decimal NotationNumber without suffix512
AcronymsUppercasePOST
AbbreviationsLowercase, except where
standard usage requires
uppercase
1.6For More Information
The web site http://www.dlttape.com includes information about the various DLTtape systems
available for purchase. To locate specific product-related support information or to register your tape
drive, visit http://www.quantum.com/AM/support/. Once you are registered, you can download a
variety of useful drivers, software programs, and diagnostic utilities.
TEST UNIT READY
25h
101b
Mb (megabits)
MB (megabytes)
For personalized information about Quantum’s reliable data protection products, call 1-800-624-5545
in the U.S.A. and Canada.
Quantum is committed to providing the best products and service. We encourage your comments,
suggestions, and corrections for this manual. Please send all comments on existing documentation to:
Quantum Technical Publications
4001 Discovery Dr.
Suite 1100
Boulder, Colorado USA 80303
This chapter presents the background information required to use this manual successfully.
Specifically, it covers the following topics:
•“Background Information About Fibre Channel” introduces the Fibre Channel architecture.
•“Implementation Details for SDLT 600 Tape Drives” lists the Fibre Channel features that SDLT
600 tape drives implement.
81-81202-01
REV A02
CHAPTER 2
Fibre Channel Protocol and SCSI
2.1Background Information About Fibre Channel
Fibre Channel is a high-speed serial architecture that allows either optical or electrical connections at
data rates of 1 Gb/second or 2 Gb/second. Fibre Channel supports point-to-point, fabric, and arbitrated
loop topologies. Implementation of the Fibre Channel Protocol (FCP) standard enables the
transmission of SCSI commands, data, and parameters, and the receipt of SCSI status and sense
information across the Fibre Channel connection.
2.1.1 Fibre Channel Interface Type
The SDLT 600 Fibre Channel tape drive supports the following features:
•Automatic speed negotiation, with transfer rates of:
100 megabytes per second (1 Gb/second)
200 megabytes per second (2 Gb/second)
•Automatic topology negotiation (the tape drive operates as an NL_Port or N_Port):
Arbitrated Loop: private loop, NL_Port to NL_Port(s)
Arbitrated Loop: public loop, NL_Port to NL_Port(s) and one FL_Port
Fabric attachment: N_Port to F_Port
Point-to-Point attachment: N_Port to N_Port
81-81202-01 REV A02July 20042-1
Background Information About Fibre ChannelSDLT 600 Fibre Channel Interface Guide
•FCP (SCSI-3 command set) for tape devices
•Class 3 level of service
•Basic and extended link services
•Task retry identification
•Hard assigned port addresses, when attached to a library. The library can assign a hard address to
the tape drive. If the library does not assign a hard address, the tape drive takes a soft address
initially.
2.1.2 Relationship Between Fibre Channel and SCSI
Small Computer System Interface (SCSI) is one of the industry’s most widely adopted I/O interfaces;
it is widely used in computing platforms from personal computers to mainframes to peripheral devices
of all types. Transmitting SCSI command-set information across a Fibre Channel connection makes
the large body of SCSI application and tape driver software available for use in the high-performance
Fibre Channel environment.
NOTE: Complete FCP and SCSI standards documents are available at
www.t10.org.
SDLT 600 tape drives conform to the SCSI-3 standard, with commands transported using the FCP-2
standard. This manual assumes you are familiar with the FCP, SAM, SPC, FC-FS, and SSC standards.
2.1.3 World-wide Names
Each SDLT 600 tape drive contains two unique, 64-bit world-wide names for Fabric Login: a node
name for the drive and one for the drive’s Fibre Channel port. The drive reports the world-wide names
to the host through the INQUIRY Command (12h). See “Device Identification Page (83h)” on
2.2Implementation Details for SDLT 600 Tape
Drives
This section introduces the Fibre Channel features SDLT 600 tape drives implement including task
management functions, persistent reservations, Basic and Extended Link Service, and unsolicited
control support.
2.2.1 Task Management
SDLT 600 tape drives support the following task management functions:
Table 2-1. Supported Task Management Functions
Task Management
Bit
FlagSDLT 600 Tape Drive Action
7ObsoleteNoneFCP Command Fields
6Clear ACANoneTask Management Function
5Target ResetThe initiator sends this task management
function to reset all logical units. When the
drive receives it, the drive clears all I/O
processes. The Target Reset task management
flag causes the drive to:
Response Code Setting in
FCP Response Payload
Invalid
Not Supported
Task Management Function
Complete
• Flush the contents of cache to tape
• Execute a soft reset.
The drive creates a Unit Attention condition
for all initiators after accepting and processing
the Target Reset. The Additional Sense Code is
set to DEVICE RESET FUNCTION
OCCURRED.
If a WRITE command is in progress and
STATUS has not been sent to the initiator when
the drive receives this task management
function, some or all of the data for this
command may be written to the medium.
4Reset LUNThis task management function causes the
drive to reset the selected unit.
Response Code Setting in
FCP Response Payload
Task Management Function
Complete
When the LUN is set to 0 and the drive
receives the Reset LUN task management
function, the drive is reset as described in
Target Reset above.
3ReservedNoneFCP Command Fields
Invalid
2Clear Task SetNoneTask Management Function
Not Supported
1Abort Task SetThis task management function causes the
drive to clear the current I/O process on the
Task Management Function
Complete
selected unit. Buffered (cached) write
operations are completed if possible. The
current settings of MODE SELECT parameters
and reservations are not affected. Commands,
data, and status for other initiators are not
affected.
This task management function can be sent to a
logical unit that is not currently performing an
operation for the initiator.
If a WRITE command is in progress and
STATUS has not been sent to the initiator when
the drive receives this task management
function, some or all of the data for this
command may be written to the medium.
SDLT 600 tape drives support the PERSISTENT RESERVE OUT and PERSISTENT RESERVE IN
commands. The PERSISTENT RESERVE OUT command allows a node connected to the SDLT 600
tape drive port to reserve the drive for data transfers. The node that issued the PERSISTENT
RESERVE OUT command must issue another PERSISTENT RESERVE OUT command to release
the drive before a different node can initiate a data transfer to the drive. Reservations in effect are not
released by reset or power-down conditions. The PERSISTENT RESERVE IN command obtains
information about persistent reservations and registrations active on an SDLT 600 tape drive. See
“PERSISTENT RESERVE OUT Command (5Fh)” on page 3-140 and “PERSISTENT RESERVE IN
Command (5Eh)” on page 3-133 for more information.
2.2.3 Link Service and Unsolicited Control Support
SDLT 600 tape drives provide Link Service and Unsolicited Control support as described in this
section.
Basic Link Service
The following table lists the Basic Link Service requests the drive supports. Refer to the FC-FS
specification for details.
The following table lists the ELS Loop Initialization commands the drive supports. The drive is
capable of being a loop initialization master. Refer to the FC-AL-2 specification for details.
Table 2-4. Supported Extended Link Service Loop Initialization Commands
Loop Initialization
Identifier
1101hLISMSelect Loop Master Based on 8-Byte Port Name
1102hLIFAFabric Assigned AL_PA Bit Map
1103hLIPAPreviously Acquired AL_PA Bit Map
1104hLIHAHard Assigned AL_PA Bit Map
1105hLISASoft Assigned AL_PA Bit Map
1106hLIRPReport AL_PA Position Map
1107hLILPLoop AL_PA Position Map
AbbreviationDescription
FC-4 Link Service Commands
The following table lists the FC-4 Link Service commands the drive supports. Refer to the FC-FS and
FCP-2 specifications for details.
Table 2-5. Supported FC-4 Link Service Commands
FC-4 CommandAbbreviationDescription
13hRECRead Exchange Concise
14hSRRSequence Retransmission Request
Unsolicited Control / Name Server Requests
The following table lists the Name Server Requests the drive supports. Refer to FC-GS for details.
Table 2-6. Supported Name Server Requests
Name Server RequestAbbreviationDescription
0217hRFT_IDRegister FC-4 Types
021FhRFF_IDRegister FC-4 Features – Port Identifier
This chapter describes the supported SCSI commands, options, and error recovery procedures
implemented in the Quantum SDLT tape drive. This chapter does not fully reiterate the entire ANSI
SCSI specification; for information of this nature, refer to the SCSI specification itself.
The web sites http://www.scsita.org and http://www.t10.org are also helpful sources of information.
81-81202-01
REV A02
CHAPTER 3
SCSI Commands
3.1Overview of SCSI Command and Status
Processing
The Quantum SDLT tape drive supports the SCSI-3 command set. The SDLT tape drive supports the
SCSI commands listed in Table 3-1.
Table 3-1. SCSI Commands Supported by SDLT Tape Drives
CommandOperation CodeSubsection
ERASE19hPage 3-7
INQUIRY12hPage 3-8
LOAD UNLOAD1BhPage 3-26
LOCATE2BhPage 3-28
LOG SELECT4ChPage 3-29
LOG SENSE4DhPage 3-37
MODE SELECT (6) / (10)15h / 55hPage 3-65
MODE SENSE (6) / (10)1Ah / 5AhPage 3-105
PERSISTENT RESERVE IN5EhPage 3-133
81-81202-01 REV A02July 20043-1
Overview of SCSI Command and Status ProcessingSDLT 600 Fibre Channel Interface Guide
Table 3-1. SCSI Commands Supported by SDLT Tape Drives (Continued)
NOTE: The RECEIVE DIAGNOSTIC RESULTS and SEND DIAGNOSTIC
DATA commands implement vendor-specific pages to test the drive
during the manufacturing process. Quantum recommends that initiators
specify only the non-page format variants of these commands (PF=0) for
all pages except page 40h.
81-81202-01 REV A02July 20043-3
Overview of SCSI Command and Status ProcessingSDLT 600 Fibre Channel Interface Guide
3.1.1 Unit Attention Condition
Queued Unit Attentions are implemented on the SDLT tape drive and are maintained separately for
each valid LUN for each initiator. Unit Attentions are created in each of the following circumstances:
•At power-on.
•Port logout or implicit logout.
•When the medium may have changed asynchronously.
•When another initiator changes the Mode parameters.
•When a firmware (microcode) update has completed.
•Task Management Target Reset.
Up to three Unit Attentions may be queued for each initiator. If an initiator does not clear its queued
Unit Attentions, any additional Unit Attention conditions are not reported.
3.1.2 Behavior at Power-On
The SDLT tape drive’s behavior at power-on consists of the following:
•Transceivers are turned on and auto speed negotiation occurs unless a speed jumper on the rear
panel of the drive is set, in which case the drive operates at the selected speed.
•Topology is initialized (loop, point-to-point, or fabric).
•In point-to-point mode, the drive is ready to send a FLOGI to determine if there is a fabric present.
•In public loop mode, the drive is ready to log into the fabric.
•In private loop mode, the drive is ready to accept a login request from a host.
•The drive rewinds the tape to Beginning of Tape (BOT).
•The drive goes through a calibration process at power-on and loading of media.
The Quantum SDLT tape drive contains a data cache that buffers blocks and filemarks until it writes
them to tape. This section describes what happens when the drive writes, or “flushes,” those blocks to
tape. A MODE SELECT parameter allows the data cache to be disabled (unbuffered mode). In this
mode, every WRITE command causes data to be written to the tape medium before the drive returns
the STATUS byte to the host.
NOTE: Unbuffered mode is NOT recommended due to the poor performance that
may result.
The drive writes the contents of the write data cache to the tape medium under the following
circumstances:
•When the initiator issues a WRITE FILEMARKS command with the Immediate bit set to 0.
•When data has been in the cache longer than the maximum time specified by the value of the
MODE SELECT command Write Delay Time parameter (the default is 10 seconds).
•When the drive receives a non-write-type media access command.
•When a RESET condition occurs.
3.2SCSI Command Descriptions
The SCSI command descriptions that make up the rest of this chapter contain detailed information
about each command the SDLT tape drive supports. The SCSI commands are presented in alphabetical
order. Fields common to many of the SCSI commands are not repeated for every command; instead
they are supported as shown in Table 3-2:
Table 3-2. Fields Common to Many SCSI Commands
Name of FieldHow Field is Supported in SCSI Commands
Logical Unit Number (LUN)LUN for the SDLT tape drive is 0.
ControlAll SCSI commands must have a Control byte, which is implemented as
described in SCSI Architecture Model – 3 (SAM–3).
ReservedReserved bits, fields, bytes, and code values are set aside for future
standardization and must be set to 0. If the drive receives a command that
contains non-zero bits in a reserved field or a reserved code value, the
drive terminates the command with a CHECK CONDITION status and
the Sense Key is set to ILLEGAL REQUEST.
Throughout this manual, multiple bytes that contain information about specific command parameters
are portrayed as shown in the example of the Parameter List Length field (bytes 7 to 8) of the LOG
SELECT command, shown as follows:
Bit
Byte
7 – 8
76543210
(Bytes 0 – 6)
(MSB)
Parameter List Length
(LSB)
This sample indicates that the most significant bit (MSB) of the field is bit 7 of byte 7; the least
significant bit is bit 0 of byte 8. The shorthand version of presentation is used in this manual to save
space.
This is an alternate, “shorthand” presentation for:
The ERASE command erases the data on the tape medium. The SDLT tape drive erases the data only if
the Long bit is set to 1 and the drive receives the ERASE command while it is at Beginning of Tape
(BOT). If the Long bit is set to 0, this command has no effect on the tape medium.
NOTE: The time required to completely erase a Super DLTtape II cartridge is
more than 3 hours.
Bit
Byte
0Operation Code (19h)
1ReservedImmedLong
2 – 4Reserved
5Control
76543210
Figure 3-1. ERASE Command Descriptor Block — Data Format
Table 3-3. ERASE Command Descriptor Block — Field Descriptions
FieldDescription
ImmedImmediate. If set to 0, the drive does not return status until the selected operation
has completed. If set to 1, the drive returns status as soon as it initiates the
operation.
LongMust be set to 1 to perform an erase operation. Issuing an ERASE command when
the tape is not at BOT is an ILLEGAL REQUEST. If set to 0, the drive performs no
operation—the ERASE command does not affect the tape.
The INQUIRY command allows the initiator to direct all attached devices to return information about
themselves. SDLT devices respond by providing a variety of information, including their World Wide
Name and other important characteristics. The SDLT tape drive identifies itself as a Sequential Access
Storage Device that implements the SCSI-3 protocol.
NOTE: The tape drive does not need to access its tape medium to respond to the
INQUIRY command.
The drive can provide different categories of data in response to an INQUIRY command:
•Standard Inquiry Data — contains basic data about the drive, including vendor-specific inquiry
data that precisely identifies the revision of SDLT tape drive subsystem components.
•Vital Product Data — comprises several pages of additional data. Each Vital Product Data page
requires a separate INQUIRY command from the initiator. To see a list of specific Vital Product
Data pages returned by this SDLT tape drive, refer to “Supported Vital Product Data Page (00h)”
on page 3-16.
An INQUIRY command is neither affected by—nor does it clear—a Unit Attention condition.
Bit
Byte
0Operation Code (12h)
1ReservedObsolete EVPD
2Page Code
3 – 4
5Control
76543210
(MSB)
Allocation Length
(LSB)
Figure 3-2. INQUIRY Command Descriptor Block — Data Format
Table 3-4. INQUIRY Command Descriptor Block — Field Descriptions
FieldDescription
EVPDEnable Vital Product Data. If set to 0, the drive returns the Standard Inquiry Data.
If EVPD is set to 1, the drive returns the Vital Product Data Page specified by
Page Code.
Page CodeSpecifies the Vital Product Data Page that the drive is to return when EVPD is set
to 1. Figure 3-5 on page 3-16 shows the Page Codes for the Vital Product Data
pages the drive supports.
Allocation
Length
Specifies the number of bytes of inquiry information the drive is allowed to return
to the initiator. The drive does not return Error status if the value in this field
truncates the requested information.
The following table contains field descriptions for the data the drive returns.
Table 3-5. Standard Inquiry Data Page — Field Descriptions
Field NameVa lu eDescription
Peripheral Qualifier0This field contains 000b if the command is directed to a
valid device. The field contains 011b if there is no device
at the selected LUN.
Peripheral Device Type1This field contains 01h if the LUN is 0h, 8h if the LUN
selects an attached loader, or 1Fh if no device is attached
to the selected LUN.
RMB1Removable Medium Bit. Always set to 1.
Version04hThe drive supports ANSI SCSI-3 per SPC-2.
NormACA0Normal ACA Supported. When set to 0, indicates that the
drive does not support setting the NACA bit to 1 in the
Control byte of the CDB. When set to 1, indicates that the
drive supports setting the NACA bit to 1.
HiSup1Hierarchical Support. When set to 0, indicates that the
drive does not support the hierarchical addressing model
to assign LUNs to logical units. When set to 1, indicates
that the drive does support the hierarchical addressing
model to assign LUNs to logical units.
Response Data Format2This Standard Inquiry Data is in the format described in
the Version field.
Additional Length---The drive uses this field to indicate the number of
additional bytes of INQUIRY Response Data available.
The value depends on the number of version descriptors
returned in the INQUIRY Response Data.
SCCS0SCC Supported. The drive does not contain an embedded
storage array controller component. Always set to 0.
ACC0Access Controls Coordinator. The drive does not contain
an access controls coordinator. Always set to 0.
ALUA00bAsymmetric Logical Unit Access. Not supported. Always
set to 0.
3PC0Third-party Copy. Not supported. Always set to 0.
BQue0Tagged (Basic) Command Queuing. Not supported.
Always set to 0.
EncServ0Enclosure Services. The drive does not contain an
embedded enclosure services component. Always set
to 0.
Table 3-5. Standard Inquiry Data Page — Field Descriptions (Continued)
Field NameVa lu eDescription
VS0Vendor Specific. Both VS bits are always set to 0.
MultiP0Multi Port. The drive is a single-port device that does not
implement multi-port requirements. Always set to 0.
MChnger0Medium Changer. The drive does not support attached
medium changer commands sent to the drive’s LUN.
Always set to 0.
Addr16016-bit Addressing. Restricted for Fibre Channel devices.
Always set to 0.
RelAdr0Relative Addressing. Not supported. Always set to 0.
WBus160Wide Bus 16. Restricted for Fibre Channel devices.
Always set to 0.
Sync0Synchronous Data Transfer. Restricted for Fibre Channel
devices. Always set to 0.
Linked0Linked Command Support. Not supported. Always set to
0.
CmdQue0Tagged Command Queuing. Not supported. Always set to
0.
Vendor IdentificationQUANTUMThe value in this field is left-aligned and set to
“QUANTUM”. The remainder of the field is filled with
space characters.
Product IdentificationSDLT600For the SDLT 600 tape drive, this field is set to
“SDLT600”, left-aligned, filled with space characters to
the end of the field.
Product Revision Level---Contains 4 bytes of ASCII data that provide the drive’s
firmware revision levels. The first 2 bytes are the version
number for servo code. The second 2 bytes are the
version number of the SCSI/read/write code. When a
firmware update is performed on the SDLT tape drive, the
second two bytes of the revision level change to reflect
that update.
Vendor Specific---See “Vendor Specific Inquiry Data Page” on page 3-14
for details about what types of vendor-specific
information are returned.
Clocking0Restricted for Fibre Channel devices. Always set to 0.
QAS0Quick Arbitrate Supported. Not supported.Restricted for
The following information precisely identifies the revision of SDLT tape drive subsystem components.
Note: Page content is subject to change at any time.
Bit
Byte
36Product FamilyReleased Firmware
37Firmware Major Version Number
38Firmware Minor Version Number
39EEPROM Format Major Version Number
40EEPROM Format Minor Version Number
41Firmware Personality
42Firmware Subpersonality
43Vendor Specific Subtype
44Controller Hardware Version Number
45Tape Drive EEPROM Version Number
46Tape Drive Hardware Version Number
47Media Loader Firmware Version Number
48Media Loader Hardware Version Number
76543210
49Media Loader Mechanical Version Number
50Media Loader Present Flag
51Library Present Flag
52 – 55Module Revision
Figure 3-4. Vendor Specific Inquiry Data Page — Data Format
NOTE: Refer also to “Subsystem Components Revision Page (C1h)” on
page 3-24 for information about an alternate method for accessing these
Table 3-6. Vendor Specific Inquiry Data Page — Field Descriptions
Field NameDescription
Product FamilyIndicates the data density of each of the SDLT tape drives as
follows:
Valu eDr i v e D en s it y
Ah110.0 / 220.0 GB
Bh160.0 / 320.0 GB
Ch300.0 / 600.0 GB
Released FirmwareDifferentiates between released and test versions of firmware.
When set to 1, indicates released code (Vxxx); when set to 0,
indicates field test code (Txxx). Released code has no minor
firmware version number (byte 38 is set to 0). For tracking
purposes, field test and engineering versions of code have nonzero minor firmware version numbers.
Version Number FieldsThese fields display the various version numbers in binary
format, instead of ASCII.
Firmware PersonalityNumeric indicator of firmware personality. Note that when set
to 4, indicates OEM family.
Firmware SubpersonalityIndicates the variant of the firmware personality. Always set to
1, indicating the primary firmware personality variant.
Vendor Specific SubtypeProduct identification.
Media Loader Present Flag When set to 0, indicates no loader present. Non-zero indicates
loader is present.
Library Present FlagWhen set to 0, indicates no library present. Non-zero indicates
library is present.
Module RevisionA 4-byte ASCII string representing the revision level of the tape
drive’s module (the controller PCBA attached to the drive).
Figure 3-6 shows the format of the Unit Serial Number page the drive returns.
Bit
Byte
0Peripheral QualifierPeripheral Device Type
1Page Code (80h)
2Reserved
3Page Length (10h)
4 – 19Serial Number
76543210
Figure 3-6. Unit Serial Number Page — Data Format
Table 3-7. Unit Serial Number Page — Field Descriptions
Field NameDescription
Serial NumberThe serial number given is the serial number of the module or the drive,
typically beginning with “MX”, indicating the site of manufacture. If the
drive serial number is valid, it is reported; otherwise, the module serial
number is reported. The serial number appears on the bar code label. The
drive returns the serial number in ASCII format.
Figure 3-7 shows the format of the Device Identification page the drive returns.
Bit
Byte
0Peripheral QualifierPeripheral Device Type
1Page Code (83h)
2Reserved
3Page Length
4 – nIdentification Descriptors
76543210
Figure 3-7. Device Identification Page — Data Format
Table 3-8. Device Identification Page — Field Descriptions
Field NameDescription
Peripheral
Qualifier
Peripheral
Device Type
Contains 000b if the command is directed to a valid device. Contains 011b if
there is no device at the selected LUN.
Contains 01h if the LUN is 0h, 8h if the LUN selects an attached library, or
1Fh if there is no device at the selected LUN.
Page CodeA value of 83h identifies this as the Device Identification page.
Page LengthIndicates the size of the returned Device Identification page.
Identification
Descriptors
The drive always returns the Vendor-unique Logical Unit Identifier and the
Logical Unit NAA Identifier. It may also return other identifiers. The
following identifiers are described in this section:
Table 3-9. Vendor-unique Logical Unit Identifier — Field Descriptions (Continued)
Field NameDescription
Identifier
Length
Specifies the length in bytes of the Identifier field. If the Allocation Length
field of the CDB is too small to transfer the entire identifier, the Identifier
Length value is not adjusted to reflect the truncation.
Vendor
Identification
Product
Identification
The value in this field is left-aligned and set to “QUANTUM”. The remainder
of the field is filled with space characters.
For the SDLT 600 drive, this field is set to “SDLT600”, left-aligned, and filled
with space characters to the end of the field.
Serial NumberThe serial number given is the serial number of the module or the drive,
typically beginning with “MX”, indicating the site of manufacture. If the drive
serial number is valid, it is reported; otherwise, the module serial number is
reported. The serial number appears on the bar code label. The drive returns the
serial number in ASCII format.
Figure 3-9 shows the format of the Logical Unit NAA Identifier.
Bit
Byte
0Protocol IdentifierCode Set (1)
1PIV (0)Rsv’dAssociation (0)Identifier Type (3h)
2Reserved
3Identifier Length (08h)
4 – 11
76543210
(MSB)
NAA Identifier (binary)
Figure 3-9. Logical Unit NAA Identifier — Data Format
Table 3-10. Logical Unit NAA Identifier — Field Descriptions
Field NameDescription
Protocol
Identifier
Set to 0.
(LSB)
Code SetIndicates the type of data found in the Identifier field. Set to 1h, indicating
binary data.
PIVProtocol Identifier Valid. Set to 0, indicating that the value returned in the
Protocol Identifier field should be ignored.
AssociationSet to 0, indicating that the Identifier is associated with the logical unit.
Identifier TypeType of identifier.
ValueDescription
3hNAA identifier
Identifier
Length
NAA IdentifierContains the Name Address Authority (NAA) identifier for the logical unit.
81-81202-01 REV A02July 20043-21
Specifies the length in bytes of the Identifier field. If the Allocation Length
field of the CDB is too small to transfer the entire identifier, the Identifier
Length value is not adjusted to reflect the truncation.
Figure 3-10 shows the format of the Port NAA Identifier.
Bit
Byte
0Protocol IdentifierCode Set (1)
1PIV (1)Rsv’dAssociation (1)Identifier Type (3)
2Reserved
3Identifier Length (08h)
4 – 11
76543210
(MSB)
NAA Identifier (binary)
Figure 3-10. Port NAA Identifier — Data Format
Table 3-11. Port NAA Identifier — Field Descriptions
Field NameDescription
Protocol
Identifier
When the PIV bit is set to 1, the drive returns 0 which indicates that the
protocol is Fibre Channel.
(LSB)
Code SetIndicates the type of data found in the Identifier field. Set to 1h, indicating
binary data.
PIVProtocol Identifier Valid. Set to 1, indicating that the value returned in the
Protocol Identifier field is valid.
AssociationSet to 1h, indicating that the Identifier is associated with the port.
Identifier TypeType of identifier.
ValueDescription
3hNAA identifier
Identifier
Length
NAA IdentifierContains the Name Address Authority (NAA) identifier for the port.
3-22July 200481-81202-01 REV A02
Specifies the length in bytes of the Identifier field. If the Allocation Length
field of the CDB is too small to transfer the entire identifier, the Identifier
Length value is not adjusted to reflect the truncation.
The following information precisely identifies the revision of SDLT tape drive subsystem components.
Note: Page content is subject to change at any time.
Bit
Byte
0Peripheral QualifierPeripheral Device Type
1Page Code (C1h)
2Reserved
3Page Length (39h)
4Product FamilyReleased Firmware
5Firmware Major Version Number
6Firmware Minor Version Number
7EEPROM Format Major Version Number
8EEPROM Format Minor Version Number
9Firmware Personality
10Firmware Subpersonality
11Vendor Specific Subtype
12Controller Hardware Version Number
76543210
13Tape Drive EEPROM Version Number
14Tape Drive Hardware Version Number
15Media Loader Firmware Version Number
16Media Loader Hardware Version Number
17Media Loader Mechanical Version Number
18Media Loader Present Flag
19Library Present Flag
20 – 23Module Revision
24 – 43Unit Serial Number
Figure 3-12. Subsystem Components Revision Page — Data Format
Table 3-13. Subsystem Components Revision Page — Field Descriptions
Field NameDescription
Product FamilyIndicates the data density of each of the SDLT tape drives as
follows:
Valu eD r i v e D en s it y
Ah110.0 / 220.0 GB
Bh160.0 / 320.0 GB
Ch300.0 / 600.0 GB
Released FirmwareDifferentiates between released and test versions of firmware.
When set to 1, indicates released code (Vxxx); when set to 0,
indicates field test code (Txxx). Released code has no minor
firmware version number (byte 38 is set to 0). For tracking
purposes, field test and engineering versions of code have nonzero minor firmware version numbers.
Version Number FieldsThese fields display the various version numbers in binary
format, instead of ASCII.
Firmware PersonalityNumeric indicator of firmware personality. Note that when set
to 4, indicates OEM family.
Firmware SubpersonalityIndicates the variant of the firmware personality. Always set to
1, indicating the primary firmware personality variant.
Vendor Specific SubtypeProduct identification.
Media Loader Present FlagWhen set to 0, indicates no loader present. Non-zero indicates
loader is present.
Library Present FlagWhen set to 0, indicates no library present. Non-zero indicates
library is present.
Module RevisionA 4-byte ASCII string representing the revision level of the tape
drive’s module (the controller PCBA attached to the drive).
Unit Serial NumberThe drive’s serial number; matches what is shown on the
The LOAD UNLOAD command instructs the SDLT tape drive to load or unload the tape inside the
data cartridge. If no data cartridge is in the drive, the LOAD UNLOAD command returns a CHECK
CONDITION status with the Sense Key set to NOT READY. Likewise, if the drive receives a LOAD
UNLOAD command with the Immediate bit set and then it receives another command that requires
tape motion or if it receives a TEST UNIT READY command, the drive returns a CHECK
CONDITION status with the Sense Key set to NOT READY.
Before executing the LOAD UNLOAD command, the drive writes any cached write data to the tape.
Bit
Byte
0Operation Code (1Bh)
1ReservedImmed
2 – 3Reserved
4ReservedHoldEOTReTenLoad
5Control
76543210
Figure 3-13. LOAD UNLOAD Command Descriptor Block — Data Format
Table 3-14. LOAD UNLOAD Command Descriptor Block — Field Descriptions
Field NameDescription
ImmedImmediate. When set to 1, the drive returns status as soon as the operation starts.
When set to 0, the drive returns status after the operation has completed.
HoldWhen set to 1, indicates that Enhanced Medium Auxiliary Memory (EMAM) is
accessible upon completion of the command but the medium is not repositioned
for access. When the Hold bit is set to 0 and the Load bit is set to 1, the medium
is positioned for access. When both the Hold and Load bits are set to 0, EMAM
is not accessible upon completion of the command.
EOTEnd of Tape. The drive ignores this bit unless both the EOT and Load bits are set
to 1, then the drive returns CHECK CONDITION status with Sense Key set to
ILLEGAL REQUEST.
ReTenRetension. Ignored. Retension operations are not needed.
LoadIf the Load bit is set to 1 and the medium is already loaded, the drive writes any
cached data to the tape, rewinds the tape, and returns a GOOD status. If the drive
unloaded the medium but the cartridge was not removed, a LOAD UNLOAD
command causes the drive to load the tape to Beginning of Partition (BOP) again
and make it ready for use.
If the Load bit is set to 0 and the medium is loaded, the drive writes any buffered
data and filemarks to the tape, rewinds the tape to BOM, and unloads the
medium back into the cartridge. At that point, the drive ejects the medium if not
in a library. If the drive is in a library, the drive does not eject the medium, but
waits for another command. If the medium is already unloaded, the drive takes
no action. The drive returns a GOOD status.
The LOCATE command performs high-speed positioning to a specified block address. Use the READ
POSITION command to obtain the block address associated with the current position on tape. Then
use the LOCATE command to position the tape at the same logical position for high-performance
restore operations of particular blocks of data.
Bit
Byte
0Operation Code (2Bh)
1ReservedBTCPImmed
2Reserved
3 – 6
7Reserved
8Partition
9Control
76543210
(MSB)
Logical Object Identifier
Figure 3-14. LOCATE Command Descriptor Block — Data Format
Table 3-15. LOCATE Command Descriptor Block — Field Descriptions
Field NameDescription
(LSB)
BTBlock Type. The drive ignores this bit.
CPChange Partition. The drive does not support multiple partitions.
Always set to 0.
ImmedImmediate. When set to 1, the drive returns status as soon as the
operation starts. When set to 0, the drive returns status after the
operation has completed.
Logical Object
Identifier
PartitionNot applicable; the drive ignores this bit. See CP field above.
3-28July 200481-81202-01 REV A02
Specifies the Logical Object Identifier to which the drive positions the
medium.
The LOG SELECT command allows the host to manage statistical information the SDLT tape drive
maintains about its own hardware parameters and about the installed tape medium. Read the
description of the “LOG SENSE Command (4Dh)” on page 3-37; it provides information about log
page format, parameters, and supported pages.
Bit
Byte
0Operation Code (4Ch)
1ReservedPCRSP
2PCReserved
3 – 6Reserved
7 – 8
9Control
76543210
(MSB)
Parameter List Length
Figure 3-15. LOG SELECT Command Descriptor Block — Data Format
Table 3-16. LOG SELECT Command Descriptor Block — Field Descriptions
Field NameDescription
PCRParameter Code Reset. If this bit is set to 1 and the Parameter List Length field
is set to 0, all accumulated values of page codes 2, 3, and 32 are set to 0 and all
threshold values are set to default. If PCR is set to 1 and the Parameter List
Length field is set to a non-zero value, the drive terminates the command with
CHECK CONDITION status, Sense Key set to ILLEGAL REQUEST, and
Additional Sense Code (ASC) set to INVALID FIELD IN CDB. (See the Note
under SP [Save Parameters] below.)
SPSave Parameters. When set to 1, indicates that after performing the specified
LOG SELECT operation the drive saves to nonvolatile memory all parameters
identified as saveable by the DS bit in the log page. When set to 0, specifies
that the drive does not save the parameters.
Note: If PCR and SP are both set to 1, the drive terminates the command with
a CHECK CONDITION status, Sense Key set to ILLEGAL REQUEST,
and Additional Sense Code set to INVALID FIELD IN CDB.
PCPage Control. Defines the type of parameter values to be selected:
CodeType of Parameter Value
00bCurrent Threshold Values
01bCurrent Cumulative Values
10bDefault Threshold Values
11bDefault Cumulative Values
When the PC field is set to 10b and the Parameter List Length field is set to 0,
all Current Threshold Values are reset to the Default Threshold Values.
When the PC field is set to 11b and the Parameter List Length field is set to 0,
all Current Cumulative Values are reset to the Default Cumulative Values. This
is equivalent to clearing all log pages that can be cleared.
Note: The drive ignores the PC field value if the PCR bit is set to 1.
Parameter
List Length
Specifies the length, in bytes, of the LOG SELECT parameter list to be
transferred from the initiator to the drive. A Parameter List Length of 0
indicates that no data is to be transferred. This condition is not considered an
error.
Each log page begins with a 4-byte header followed by n number of log parameter blocks—one block
for each parameter code. Each block, except for parameter code 05h, comprises 8 bytes. The parameter
block for page code 05h is 12 bytes.
Bit
Byte
0Page Code
1Reserved
2 – 3
4Log Parameter (First)
x + 3Length (x)
n – y + 1Log Parameter (Last)
nLength (y)
76543210
(MSB)
Page Length (n – 3)
Log Parameters
.
.
Figure 3-16. LOG SELECT Log Page — Data Format
(LSB)
Table 3-18. LOG SELECT Log Page Header — Field Descriptions
Field NameDescription
Page CodeSpecifies the log page to which this LOG SELECT command is directed.
Page LengthSpecifies the total number of bytes contained in this log page, not including the
Table 3-19. LOG SELECT Log Parameters — Field Descriptions (Continued)
Field NameDescription
8003hTotal servo tracking errors
9000h-
Without substantial delay errors by channel
9007h
9080h9087h
Write only: Possible delay errors assignable to specific
channels
Read only: Raw sub-block read errors by channel
Note: Many of these errors are write, not read, errors and are
not to be included in read error-rate calculations. If
these errors are used to try to identify bad channels, the
bad channel may be on either the writing or reading
drive.
Note: Parameter codes 00h, 01h, and 04h always have a value of 0.
Parameter value for 05h is eight bytes; the Parameter Length field is
set to 8.
DUDisable Update. This bit is not defined for LOG SELECT; the drive ignores
any value in DU.
DSDisable Save. Not supported. DS and Target Save Disable (TSD) must be set
to 1. If DS or TSD or both are set to 0, the drive terminates the command
with CHECK CONDITION status, Sense Key set to ILLEGAL REQUEST,
and Additional Sense Code set to INVALID FIELD IN PARAMETER
LIST.
TSDTarget Save Disable. Not supported. TSD and DS must be set to 1. If TSD or
DS or both are set to 0, the drive terminates the command with CHECK
CONDITION status, Sense Key set to ILLEGAL REQUEST, and
Additional Sense Code set to INVALID FIELD IN PARAMETER LIST.
ETCEnable Threshold Comparison. When set to 1, the drive performs a
comparison with threshold values once the cumulative value is updated.
Comparison criteria are defined in Threshold Met Criteria (TMC). If the
comparison is met and the RLEC bit of MODE SELECT / SENSE Control
Page 0Ah is set to 1, the drive generates a UNIT ATTENTION for all
initiators. The drive sets the Additional Sense Code to THRESHOLD
CONDITION MET. If the RLEC bit is 0 and the comparison is met, the
drive does not generate a UNIT ATTENTION.
TMCThreshold Met Criteria. Once the criteria specified in this field are met, the
ETC bit is 1, and the RLEC bit in the MODE SENSE / SELECT Control
Page is set to 1, the drive generates a UNIT ATTENTION for all initiators.
The host issues a LOG SENSE command to initialize host-resident software that allows determination
of:
•The log pages the drive uses
•The parameter codes and length of each parameter.
The following conditions constitute errors in the parameter block that cause the drive to return
CHECK CONDITION status with Sense Data set to ILLEGAL REQUEST and Additional Sense Code
set to INVALID FIELD IN PARAMETER LIST:
•The drive receives a page header with unsupported page codes.
•An incorrect log page length is specified in the page header.
•An illegal parameter code is contained in a valid page code.
•Parameter codes for a supported page are not sent in ascending order.
•The LP bit is set to 1 in the parameter control byte.
•The DS bit is set to 0 in the parameter control byte.
•The TSD bit is set to 0 in the parameter control byte.
The LOG SENSE command allows the host to retrieve statistical information the SDLT tape drive
maintains about its own hardware parameters or about the installed tape medium. This command
complements the LOG SELECT command.
Bit
Byte
0 Operation Code (4Dh)
1ReservedPPCSP (0)
2PCPage Code
3 – 4Reserved
5 – 6
7 – 8
9Control
76543210
(MSB)
Parameter Pointer
(MSB)
Allocation Length
Figure 3-18. LOG SENSE Command Descriptor Block — Data Format
(LSB)
(LSB)
81-81202-01 REV A02July 20043-37
LOG SENSE Command (4Dh)SDLT 600 Fibre Channel Interface Guide
Table 3-20. LOG SENSE Command Descriptor Block — Field Descriptions
Field NameDescription
PPCParameter Pointer Control. When set to 0, indicates that the parameter data
requested from the drive starts with the parameter code specified in the
Parameter Pointer field (bytes 5 – 6) and returns the number of bytes specified
in the Allocation Length field (bytes 7 – 8) in ascending order of parameter
codes from the specified log page. When set to 1, the drive returns only the
parameters that have changed since the last time the page was read.
SPSave Parameters. Not supported. Must be set to 0. If the Save Parameters bit is
set to 1, the drive terminates the command with CHECK CONDITION status,
Sense Key set to ILLEGAL REQUEST, and Additional Sense Code set to
INVALID FIELD IN CDB.
PCPage Control. This field defines the type of parameter values to be returned:
CodeType of Parameter Values
00bThreshold Values
01bCumulative Values
10bDefault Threshold Values
11bDefault Cumulative Values
• The Default Threshold Values are the maximum values that each parameter
can attain.
• The Current Cumulative values are the values computed since the last reset
of the drive by power-cycle, or FCP target reset.
• The Default Cumulative values are the values to which each parameter is
initialized at a reset condition. Default values are 0.
• By default, Current Threshold Values are set to Default Threshold Values.
Page CodeThe Page Code field identifies the log page the initiator requested. If the drive
does not support the specified page, the drive terminates the command with
CHECK CONDITION status, Sense Key set to ILLEGAL REQUEST, and
Additional Sense Code set to INVALID FIELD IN CDB. The drive supports the
following pages:
Table 3-20. LOG SENSE Command Descriptor Block — Field Descriptions (Continued)
Field NameDescription
0ChSequential Access Device Log PagePage 3-47
0DhTemperature Log PagePage 3-49
2EhTapeAlert Log PagePage 3-51
32hRead / Write Compression Ratio Log PagePage 3-55
33hDevice Wellness Log PagePage 3-59
3EhDevice Status Log PagePage 3-62
Parameter
Pointer
Allocation
Length
The Parameter Pointer field allows the host to specify at which parameter within
a log page the requested data should begin. For example, if a page supports
parameters 0 through 5, and the Parameter Pointer contains 3, the drive returns
only parameters 3, 4, and 5 to the host. Similarly, if a page supports parameters
1, 3, and 6, and the Parameter Pointer contains 2, the drive returns only
parameters 3 and 6 to the host.
If the Parameter Pointer is larger than the highest numbered parameter on the
page, the drive terminates the command with CHECK CONDITION status,
Sense Key set to ILLEGAL REQUEST, and Additional Sense Code set to
INVALID FIELD IN CDB.
Note that the drive always returns parameters within a page in ascending order
according to the parameter code.
If the drive does not support a parameter code within a page, it does not return
any data associated with that parameter.
Specifies the maximum number of bytes that the host allocated for returning
data. The host uses this field to limit the size of data transfers to its own internal
buffer size.
3.8.1 Error Summary in LOG SENSE Command Descriptor
Block
The following conditions constitute errors the drive detects relating to the LOG SENSE CDB. The
drive terminates the command with CHECK CONDITION status, Sense Key set to ILLEGAL
REQUEST, and Additional Sense Code set to INVALID FIELD IN CDB.
Error conditions occur when:
•The drive does not support the requested page.
•The parameter pointer is larger than the highest numbered parameter on the page.
•The SP bit is set to 1.
81-81202-01 REV A02July 20043-39
LOG SENSE Command (4Dh)SDLT 600 Fibre Channel Interface Guide
3.8.2 Supported Pages Log Page (Page 00h)
When the host requests Page 00h, the drive returns the 4-byte page header followed by the pages
supported in ascending order, one byte for each.
Bit
Byte
0Page Code (00h)
1Reserved
2 – 3
4Supported Pages Log Page (00h)
5Write Error Log Page (02h)
6Read Error Log Page (03h)
7Last n Error Events Log Page (07h)
8Sequential Access Device Log Page (0Ch)
9Temperature Log Page (0Dh)
10TapeAlert Log Page (2Eh)
11Read / Write Compression Ratio Log Page (32h)
12Device Wellness Log Page (33h)
76543210
(MSB)
Page Length (0Ah)
(LSB)
13Device Status Log Page (3Eh)
Figure 3-19. Supported Pages LOG SENSE Page — Data Format
Table 3-22. Log Parameters for Read / Write Error LOG SENSE Page —
Field Descriptions (Continued)
Field NameDescription
8002hTotal dropout error count
8003hTotal servo tracking errors
9000h-
Without substantial delay errors by channel
9007h
9080h9087h
Write only: Possible delay errors assignable to specific
channels
Read only: Raw sub-block read errors by channel
Note: Many of these errors are write, not read, errors and
are not to be included in read error-rate calculations.
If these errors are used to try to identify bad
channels, the bad channel may be on either the
writing or reading drive.
Note: Parameter codes 00h, 01h, and 04h always return a value of 0.
DUDisable Update. When set to 0, indicates that the drive updates all log
parameter values. When set to 1, indicates that the drive does not update
the log parameter values except in response to a LOG SELECT command.
The drive sets this bit to 1 when accumulated values reach maximum. The
drive also returns this bit set to 1 if the host set the bit in the last LOG
SELECT command. Default is 0.
Note that for parameter types other than threshold and cumulative values,
this bit is always set to 0.
DSDisable Save. Not supported. Always set to 1.
TSDTarget Save Disable. Not supported. Always set to 1.
ETCEnable Threshold Comparison. When set to 1, indicates that the drive
performs comparison to threshold. When set to 0, indicates that the drive
does not perform the comparison. The Control Mode Page of the MODE
SELECT command sets this bit set to 1. Default is 0.
81-81202-01 REV A02July 20043-43
LOG SENSE Command (4Dh)SDLT 600 Fibre Channel Interface Guide
Table 3-22. Log Parameters for Read / Write Error LOG SENSE Page —
Field Descriptions (Continued)
Field NameDescription
TMCThreshold Met Criteria. This field is valid only if the host sets the ETC bit
to 1. This field determines the basis for comparison. The host specifies this
field using the LOG SELECT command. If the result of comparison is true
(cumulative = threshold) and the MODE SELECT / SENSE Control Mode
Page RLEC bit is set to 1, the drive generates a UNIT ATTENTION for all
initiators. In that case, the drive sets the Sense Key to UNIT
ATTENTION, the Additional Sense Code to LOG EXCEPTION, and the
Additional Sense Code Qualifier to THRESHOLD CONDITION MET. If
the RLEC bit in Control Mode Page is 0, the drive does not generate a
UNIT ATTENTION.
Note that comparison is performed in real time. A LOG SENSE command
need not be issued to get the CHECK CONDITION status. Once ETC is
selected and the RLEC bit in Control Mode Page is set to 1, the drive
issues a CHECK CONDITION status based on the criteria defined in the
TMC bits if the criteria is met in real time. The CHECK CONDITION
status does not identify for which parameter code the criterion is met. The
host must issue a LOG SENSE command to read the counters to determine
for which parameter code the criterion has been met.
The criteria for comparison are:
CodeBasis of Comparison
00bEvery update of the cumulative value
01bCumulative value equal to threshold value
10bCumulative value not equal to threshold value
11bCumulative value greater than threshold value
LBINList Binary. Not used.
LPList Parameter. The drive treats the parameter codes as data counters.
Always set to 0.
Parameter LengthSpecifies the number of bytes in the parameter value. All parameters are 4
bytes in length except parameter 0005h, which is 8 bytes in length.
Parameter ValueIndicates the actual value of this log parameter.
This page returns one parameter at a time that contains the ASCII text for the specified event log. The
Parameter Number field in the CDB specifies the log event to return. The log events in EEPROM are
numbered from 0 to 255, after which the number wraps back to 0. A maximum of 32 events are stored
at a given time. The log event returned is the first one whose parameter code is equal to or greater than
the parameter number specified in the CDB.
Bit
Byte
0Page Code (07h)
1Reserved
2 – 3
76543210
(MSB)
Page Length
Figure 3-22. Last n Error Events LOG SENSE Page — Header Format
(LSB)
81-81202-01 REV A02July 20043-45
LOG SENSE Command (4Dh)SDLT 600 Fibre Channel Interface Guide
Table 3-23. Last n Error Events LOG SENSE Header — Field Descriptions
Field NameDescription
Page CodeEchoes the page code specified in the LOG SENSE CDB.
Page LengthSpecifies the total number of bytes contained in this log page, excluding
the 4 bytes that make up the header.
Bit
Byte
76543210
(MSB)
0 – 1
Parameter Code
(LSB)
1
2
DUDSTSDETCTMCLBINLP
3Parameter Length
(MSB)
4 – n
ASCII String for Event n
(LSB)
1.The byte 2 fields are collectively referred to as the Parameter Control Byte. For definitions of the bits that
compose the Control Byte (the byte 2 in the above figure), refer to “Read (Page 03h) / Write (Page 02h) Error
Log Page” on page 3-41.
Figure 3-23. Log Parameters Format for Last n Error Events LOG SENSE Page
Table 3-24. Log Parameters for Last n Error Events LOG SENSE Page — Field Descriptions
Field NameDescription
Parameter CodeParameter Code values are assigned from 0 to 63 (decimal), where 0 is
the oldest event stored and the highest Parameter Code returned is the
most recent event.
ASCII String for
Event n
The text of the parameter includes a “Packet #” that is a value from 0 to
255. The drive assigns this internal number when the packet is written to
EEPROM. A value of 0 is normally the oldest packet, but packet
numbers wrap back to 0 after reaching 255.
This page provides a standardized way to report the device temperature.
Bit
Byte
0Page Code (0Dh)
1Reserved
2 – 3
76543210
(MSB)
Page Length
Figure 3-26. Temperature LOG SENSE Page — Header Format
Table 3-27. Temperature LOG SENSE Header — Field Descriptions
Field NameDescription
Page CodeEchoes the page code specified in the LOG SENSE CDB.
Page LengthSpecifies the number of bytes available and depends on the parameters
requested.
(LSB)
Bit
Byte
0 – 1
2DUDSTSDETCTMCLBINLP
3Parameter Length (02h)
4 – 5
76543210
(MSB)
Parameter Code (Temperature)
(LSB)
(MSB)
Parameter Value
(LSB)
Figure 3-27. Log Parameters Format for Temperature Page
81-81202-01 REV A02July 20043-49
LOG SENSE Command (4Dh)SDLT 600 Fibre Channel Interface Guide
Table 3-28. Temperature LOG SENSE Parameters — Field Descriptions
Field NameDescription
Parameter CodeParameter codes supported for the Temperature page are as follows:
CodeDescription
0000hCurrent operating temperature (degrees Celsius).
0001hReference temperature (degrees Celsius). This is the maximum
reported sensor temperature at which the tape drive is capable of
operating continuously without experiencing degradation beyond
the limits, specified in the Product Manual for this product.
DUDisable Update. Always set to 0.
DSDisable Save. Not supported. Always set to 1.
TSDTarget Save Disable. Not supported. Always set to 0.
ETCEnable Threshold Comparison. Threshold checking is not supported on this page.
Always set to 0.
TMCThreshold Met Criteria. Ignored. Always set to 0.
LBINList Binary. Always set to 1.
LPList Parameter. The drive treats the parameter codes as data counters. Always set
to 1.
Parameter
Length
Specifies the number of bytes in the parameter value. All parameters are 2 bytes in
length.
Parameter ValueIndicates the actual value of this log parameter.
This page returns results of the SDLT tape drive’s ongoing self-diagnosis, so that the drive’s behavior
can be monitored and high reliability assured. The host typically reads the TapeAlert page from the
drive at the beginning of each READ or WRITE activity, after any fatal errors occur during a READ or
WRITE, at the end of any data cartridge when the READ or WRITE activity continues onto another
data cartridge, and at the end of each READ or WRITE activity. The drive sets or clears the flags when
the failure or corrective action occurs.
Bit
Byte
0Page Code (2Eh)
1Reserved
2 – 3
76543210
(MSB)
Page Length
Figure 3-28. TapeAlert LOG SENSE Page — Header Format
Table 3-29. TapeAlert Page LOG SENSE Header — Field Descriptions
Field NameDescription
Page CodeEchoes the page code specified in the LOG SENSE CDB.
Page LengthSpecifies the total number of bytes contained in this log page, excluding the
4 bytes that make up the header.
(LSB)
81-81202-01 REV A02July 20043-51
LOG SENSE Command (4Dh)SDLT 600 Fibre Channel Interface Guide
Bit
Byte
76543210
(MSB)
0 – 1
1
2
DUDSTSDETCTMCLBINLP
Parameter Code
3Parameter Length (1)
4Value of TapeAlert Flag (Flag is set when bit 0 is set to 1; bits 1–7 are reserved)
1.The byte 2 fields are collectively referred to as the Parameter Control Byte.
Figure 3-29. TapeAlert LOG SENSE Page — Parameters Format
Table 3-30. TapeAlert Page LOG SENSE Parameters — Field Descriptions
Field NameDescription
Parameter CodeContains the Flag code. See Table 3-31 on page 3-53 for the
supported flags, level of severity, and the flag definitions.
(LSB)
Parameter LengthAlways set to 1.
Value of TapeAlert FlagIf bit 0 is set to 1, indicates that TapeAlert has sensed a problem. See
Table 3-31 on page 3-53 for the supported flags and their definitions.
If bit 0 is set to 0, indicates that TapeAlert did not sense a problem
and therefore did not set the flag.
WarningThe temperature inside the drive exceeds the allowable
specifications.
Note: The drive issues this warning 3 degrees C
below the maximum temperature threshold so
that you can provide additional cooling before
potential damage occurs.
38 Predictive
Failure
CriticalA hardware failure of the drive is predicted. Call the
tape drive supplier help line to arrange for a
replacement.
51 Tape Directory
Invalid at Unload
1.Severity levels are Informational, Wa r n i n g , and Critical. Informational flags provide a status-type
message, Warning flags indicate that there is the possibility of loss of data, and Critical flags indicate
the possibility of loss of data and that user intervention, a service call, or both may be required.
WarningA WRITE error prevented the directory from being
This page begins with a 4-byte header followed by the log parameter blocks of 6 or 8 bytes, depending
on the parameter code selected.
Bit
Byte
0Page Code (32h)
1Reserved
2 – 3
76543210
(MSB)
Additional Length
Figure 3-30. Read / Write Compression Ratio LOG SENSE Page — Header Format
Table 3-32. Read / Write Compression Ratio LOG SENSE Header — Field Descriptions
Field NameDescription
Page CodeEchoes the page code specified in the LOG SENSE CDB.
Additional LengthSpecifies the number of bytes available and depends on the parameters
requested.
(LSB)
Bit
Byte
0 –1
2DUDSTSDETCTMCLBINLP
3Parameter Length (02h)
4 – 5
76543210
(MSB)
Parameter Code
(LSB)
(MSB)
Compression Ratio x 100
(LSB)
Figure 3-31. Log Parameters Format for Read / Write Compression Ratio LOG SENSE Page
(Parameter Codes 00h and 01h)
81-81202-01 REV A02July 20043-55
LOG SENSE Command (4Dh)SDLT 600 Fibre Channel Interface Guide
Table 3-33. Log Parameters for Read / Write Compression Ratio LOG SENSE Page — Field
Descriptions (Parameter Codes 00h and 01h)
Field NameDescription
Parameter
Code
DUDisable Update. Always set to 0.
DSDisable Save. Not supported. Always set to 1.
TSDTarget Save Disable. Not supported. Always set to 1.
ETCEnable Threshold Comparison. Not supported. Always set to 0.
TMCThreshold Met Criteria. Always set to 0.
LBINList Binary. Not used.
LPList Parameter. The drive treats the parameter codes as data counters. Always
Parameter codes supported for the Read / Write Compression Ratio Page are
as follows (for codes 00h and 01h only; codes 02h through 09h are detailed
separately):
CodeDescription
00hREAD Compression Ratio x 100
01hWRITE Compression Ratio x 100
set to 0.
Bit
Byte
0 – 1
2DUDSTSDETCTMCLBINLP
3Parameter Length (04h)
4 – 7
76543210
(MSB)
Parameter Code
(LSB)
(MSB)
Counter Value
(LSB)
Figure 3-32. Log Parameters Format for Read / Write Compression Ratio LOG SENSE Page
Table 3-34. Log Parameters for Read / Write Compression Ratio LOG SENSE Page — Field
Descriptions (Parameter Codes 02h through 09h)
Field NameDescription
Parameter CodeParameter codes supported for the Read / Write Compression Ratio Page
(codes 02h through 09h) are as follows:
CodeDescription
02hMB Transferred to Host
03hBytes Transferred to Host
04hMB Read from Tape
05hBytes Read from Tape
06hMB Transferred from Host
07hBytes Transferred from Host
08hMB Written to Tape
09hBytes Written to Tape
DUDisable Update. Always set to 0.
DSDisable Save. Not supported. Always set to 1.
TSDTarget Save Disable. Not supported. Always set to 1.
ETCEnable Threshold Comparison. Not supported. Always set to 0.
TMCThreshold Met Criteria. Always set to 0.
LBINList Binary. Not used.
LPList Parameter. The drive treats the parameter codes as data counters.
Always set to 0.
81-81202-01 REV A02July 20043-57
LOG SENSE Command (4Dh)SDLT 600 Fibre Channel Interface Guide
Table 3-34. Log Parameters for Read / Write Compression Ratio LOG SENSE Page — Field
Descriptions (Parameter Codes 02h through 09h) (Continued)
Field NameDescription
Counter ValueParameter codes 02h through 09h provide a count of the number of bytes
transferred since the last time the counters were reset with a LOG SELECT
command or reset condition.
Parameter Codes 02h and 03h
the drive to the initiator. Parameter code 02h reports the number of full
megabytes transferred; parameter code 03h reports the number of bytes less
than a full megabyte transferred. Multiplying the counter returned for
parameter code 02h by 1,048,576 and then adding the value of the counter
returned by parameter code 03h results in the actual total bytes transferred
to the initiator.
Parameter Codes 04h and 05h
the drive to the buffer. Parameter code 04h reports the number of full
megabytes transferred; parameter code 05h reports the number of bytes less
than a full megabyte that have been transferred. Multiplying the counter
returned for parameter code 04h by 1,048,576 and then adding the value of
the counter returned by parameter code 05h results in the actual total bytes
transferred from tape to the buffer.
Parameter Codes 06h and 07h
the initiator to the buffer. Parameter code 06h reports the number of full
megabytes transferred; parameter code 07h reports the number of bytes less
than a full megabyte that have been transferred. Multiplying the counter
returned for parameter code 06h by 1,048,576 and then adding the value of
the counter returned by parameter code 07h results in the actual total bytes
transferred from the initiator to the buffer.
Parameter Codes 08h and 09h
drive. Parameter code 08h reports the number of full megabytes transferred;
parameter code 09h reports the number of bytes less than a full megabyte
that have been transferred. Multiplying the counter returned for parameter
code 08h by 1,048,576 and then adding the value of the counter returned by
parameter code 09h results in the actual total bytes written to the drive.
The Device Wellness Page returns information about any CHECK CONDITION status related to
Sense Keys 03h, 04h, 09h, and 0Bh that the SDLT tape drive has logged. This page can contain up to
16 entries (parameter code 0000h to 000Fh). Note that parameter code 0000h contains the oldest log
information while parameter code 000Fh contains the most recent log information.
This page begins with a 4-byte header followed by the log parameter blocks, as shown in Figure 3-33.
Bit
Byte
0Page Code (33h)
1Reserved
2 – 3
76543210
(MSB)
Page Length
Figure 3-33. Device Wellness LOG SENSE Page — Header Format
Table 3-35. Device Wellness LOG SENSE Header — Field Descriptions
Field NameDescription
Page CodeEchoes the page code specified in the LOG SENSE CDB.
Page LengthSpecifies the number of bytes available and depends on the parameters
requested.
(LSB)
81-81202-01 REV A02July 20043-59
LOG SENSE Command (4Dh)SDLT 600 Fibre Channel Interface Guide
Bit
Byte
76543210
0 – 1Parameter Code
2DU DSTSDETCTMCLBINLP
3Parameter Length (0Ch)
(MSB)
4 – 7
Time Stamp
(LSB)
(MSB)
8 – 11
Media ID
(LSB)
12Sense Key
13Additional Sense Code
14Additional Sense Code Qualifier
15Additional Error Information
Figure 3-34. Log Parameters Format for Device Wellness LOG SENSE Page (Parameter Codes
Table 3-36. Log Parameters for Device Wellness LOG SENSE Page — Field Descriptions
Field NameDescription
Parameter CodeParameter codes 0000h through 000Fh are supported, providing 16 log
entries for error information capture.
DUDisable Update. Always set to 0.
DSDisable Save. Not supported. Always set to 1.
TSDTarget Save Disable. Not supported. Always set to 1.
ETCEnable Threshold Comparison. Not supported. Always set to 0.
TMCThreshold Met Criteria. Always set to 0.
LBINList Binary. Not used.
LPList Parameter. When set to 0, indicates that the parameter is a data
counter. Data counters are associated with one or more events. The tape
drive updates the data counter whenever one of these events occurs by
incrementing the counter value. When a data counter reaches its
maximum value, the drive does not increment it further. If a data counter
is at or reaches its maximum value during the successful execution of a
command and if the RLEC bit on the Control Mode page is set to 1, the
drive terminates the command with a CHECK CONDITION status, Sense
Key set to RECOVERED ERROR, and Additional Sense Code set to
LOG COUNTER AT MAXIMUM.
When set to 1, indicates that the parameter is a list parameter.
Time StampPower-on hours when CHECK CONDITION status occurred. This is the
number of power-on hours since the last time the drive was powered on,
not total number of hours during the lifetime of the drive.
The time stamp counter is updated once per hour. If the drive is powered
down before the hourly update occurs, the update does not occur until a
full hour after power is re-applied.
Media IDInternal media identifier being used when CHECK CONDITION status
occurred. A value of 0 indicates no media or unknown media when the
event occurred. Note that this is not a legitimate method of tracing media.
Sense KeyThe Sense Keys are described in Table 3-126 on page 3-215.
Additional
The Additional Sense Codes are described in Table 3-127 on page 3-216.
Sense Code
Additional Sense
Code Qualifier
Additional Error
The Additional Sense Code Qualifiers are described in Table 3-127 on
page 3-216.
Not used.
Information
81-81202-01 REV A02July 20043-61
LOG SENSE Command (4Dh)SDLT 600 Fibre Channel Interface Guide
3.8.10 Device Status Log Page (3Eh)
This page describes the current status of the drive.
Bit
Byte
0Page Code (3Eh)
1Reserved
2 – 3
76543210
(MSB)
Page Length
Figure 3-35. Device Status LOG SENSE Page — Header Format
Table 3-37. Device Status LOG SENSE Header — Field Descriptions
Field NameDescription
Page CodeEchoes the page code specified in the LOG SENSE CDB.
Page LengthSpecifies the number of bytes available and depends on the parameters
requested.
(LSB)
Bit
Byte
0 – 1Parameter Code
2DUDSTSDETCTMCLBINLP
3Parameter Length (04h)
4 – 7
76543210
(MSB)
Parameter Value
(LSB)
Figure 3-36. Log Parameters Format for Device Status LOG SENSE Page
The MODE SELECT commands enable the host to configure the SDLT tape drive. Before configuring
the drive, the host should issue a MODE SENSE command to the drive to obtain a report of the current
configuration and determine which parameters are configurable. The host interprets this information
and then may issue MODE SELECT to set the drive to the host’s preferred configuration. The host
passes the Mode Parameter List (described in “Mode Parameter List” on page 3-67) to the drive.
Operating parameters for the drive are contained in several pages. The following table lists the MODE
SELECT pages supported and the location of the sections in this manual detailing each page:
Page CodeDescriptionRefer to
01hRead / Write Error Recovery PagePage 3-74
02hDisconnect / Reconnect PagePage 3-76
0AhControl Mode PagePage 3-78
0FhData Compression PagePage 3-80
10hDevice Configuration PagePage 3-82
11hMedium Partition PagePage 3-85
18hFibre Channel Logical Unit Control PagePage 3-87
19hFibre Channel Port Control PagePage 3-88
1ChTapeAlert PagePage 3-90
25hVendor Specific Configuration PagePage 3-93
3ChDisaster Recovery Control PagePage 3-95
3EhEEPROM Vendor Specific PagePage 3-96
Except for the EEPROM Vendor Specific Page (page 3Eh), the drive always powers on with its default
configurations set. This is also true if the drive receives an FCP target reset.
NOTE: See “Changeable Parameters Within MODE SELECT” on page 3-103 for
a list of changeable parameters within MODE SELECT. See “EEPROM
Vendor Specific Page (3Eh)” on page 3-132 for additional information
Figure 3-38. MODE SELECT (6) Command Descriptor Block — Data Format
Bit
Byte
0Operation Code (55h)
1ReservedPFReservedSP (0)
2 – 6Reserved
7 – 8
76543210
(MSB)
Parameter List Length
(LSB)
9Control
Figure 3-39. MODE SELECT (10) Command Descriptor Block — Data Format
NOTE: The drive returns a CHECK CONDITION status with Sense Key set to
ILLEGAL REQUEST if it receives an unsupported page code or a page
field with values not supported or not changeable. In such cases, the drive
does not change any parameters as a result of a command.
PFPage Format. Indicates that the data the host sent after the MODE SELECT
header and block descriptors complies with the definition of pages in the SCSI-3
specification. If the Page Format bit is set to 0, only a Mode Parameter Header
and Mode Parameter Block Descriptor can be included in the mode parameter
data. If any other data is included in the mode parameter data, the drive
terminates the command with CHECK CONDITION status,
ILLEGAL REQUEST, and Additional Sense Code set to INVALID FIELD IN
.
CDB
Sense Key set to
SP
Save Parameters. Not supported. Must be set to 0. If set to 1,
terminates the command with CHECK CONDITION status,
ILLEGAL REQUEST, and Additional Sense Code set to INVALID FIELD IN
.
CDB
3.9.1 Mode Parameter List
Figure 3-40 shows the format of the Mode Parameter List that the host passes to the drive.
Bit
Byte
0 – 3Mode Parameter Header
4 – 11Mode Parameter Block Descriptor (Optional)
4 – n
or
12 – n
Figure 3-40. MODE SELECT (6) Mode Parameter List — Data Format
Figure 3-41. MODE SELECT (10) Mode Parameter List — Data Format
Table 3-41. MODE SELECT Mode Parameter List — Field Descriptions
Field NameDescription
Mode Parameter
Header
Mode Parameter
Block Descriptor
Page(s)The Page Code or Codes of the pages that are a part of this MODE
Four bytes in length for MODE SELECT (6) or 8 bytes in length for
MODE SELECT (10). Contains information about the remainder of the
Parameter List and is always present.
Eight bytes in length. Allows the host to set the drive’s Logical Block
Size and Density Code to be written from BOT.
SELECT command.
3-68July 200481-81202-01 REV A02
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.