Oracle welcomes your comments and suggestions for improving this book. Contact us at STP_FEEDBACK_US@ORACLE.COM.
Please include the title, part number,issuedate,andrevision.
This software and related documentation are providedunderalicenseagreement containing restrictions on use and disclosure and are
protected by intellectual property laws. Except as expressly permitted in your license agreementorallowedbylaw, you may not use, copy,
reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any
means. Reverse engineering, disassembly, or decompilation of this software, unless requiredbylawforinteroperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free.Ifyoufindanyerrors, please report
them to us in writing.
If this is software or related software documentation that is deliveredtotheU.S.GovernmentoranyonelicensingitonbehalfoftheU.S.
Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data deliveredtoU.S.Government
customers are "commercial computer software" or "commercialtechnicaldata"pursuanttotheapplicableFederalAcquisition Regulation and
agency-specific supplemental regulations. As such, the use, duplication, disclosure,modification,andadaptationshallbesubjecttothe
restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government
contract, the additional rights set forth in FAR52.227-19,Commercial Computer Software License (December 2007). Oracle USA, Inc., 500
Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in avarietyofinformationmanagementapplications.Itisnotdevelopedorintendedfor
use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software or
hardware in dangerous applications, then you shall be responsibletotakeallappropriate fail-safe, backup, redundancy, and other measures to
ensure the safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software orhardware in
dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Oracle and Java areregistered trademarks of Oracle and/or its
affiliates. Other names may be trademarks of their respective owners.
AMD, Opteron, the AMD logo, and theAMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel and Intel
Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open Company, Ltd.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties.
Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content,
products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to
or use of third-party content, products, or services.
TABLE D-2SSA Data Format...................................................................................................... 281
14 T10000: Interface Reference ManualAugust 2016
Page 15
The Fibre Channel Interface Reference Manual is intended for independent software
vendors (ISVs) plus operating system designers and developers implementing Fibre
Channel on Oracle’s StorageTek T10000 Tape Drive.
This manual is also intended for solutions delivery engineers, systems engineers;
plus hardware, software, and service representatives.
This manual describes information about the StorageTek T10000A, T10000B, T10000C,
and T10000D Tape Drives. Unless otherwise specified, this information pertains to all
models of the T10000. Where information changes, the following is used to identify
them:
• 2FC = T10000A with a 2 Gb interface
• 4FC = T10000A or T10000B or T10000C with a 4 Gb interface
• 16FC = T10000D
• T10000A or T10000B or T10000C or T10000D
• FC = Fibre Channel
Access to Oracle Support
Preface
Oracle customers have access to electronic support through My Oracle Support. For
information, visit http://www.oracle.com/support/contact.html or visit http://
www.oracle.com/accessibility/support.html if you are hearing impaired.
August 2016Preface 15
Page 16
Access to Oracle Support
16 T10000: Interface Reference ManualAugust 2016
Page 17
What’ s New
Information added about the T10000D tape drive.
Information added about the T10000D tape drive support of the T10 Protection
Information feature.
August 2016What’s New 17
18 T10000: Interface Reference ManualAugust 2016
Page 18
Page 19
General Information
This chapter contains an overview about the Fibre Channel specifications for Oracle’s
StorageTek T10000 Tape Drive, which conforms to the:
• American National Standards Institute (ANSI)
• National Committee for Information Technology Standards (NCITS)
TABLE 1-1 lists the documents that help define this implementation.
TABLE 1-1 Fibre Channel Reference Documentation
SpecificationRevision
Fibre Channel Physical and Signaling InterfaceFC-PH X3.230: 1994
Fibre Channel Physical and Signaling Interface 2ndGeneration FC-PH-2 X3.297: 1997
Fibre Channel Physical and Signaling Interface 3rdGenerationFC-PH-3 X3.303:1998
* Indicates specific reference for that implementation of the Fibre Channel interface.
Overview
• Serial connection
• Copper (electrical) or fiber (optical) transmissions
• Multiple protocols (such as SCSI, IP, HIPPI, IPI-3)
• Information transparent
• 100 – 1600 MB data transfer rates
• Scalable for data rates, distance, media, and protocols
In 1994, the Fibre Channel Physical and Signaling Interface (FC–PH), or
ANSI X3.230–1994, was completed, differing from every other architecture at the
time. This specification married the strengths of channels, including high throughput
and low overhead, with the strengths of networks, including flexibility, long distance
capability, and high connectivity.
20 T10000: Interface Reference ManualAugust 2016
Page 21
See TABLE 1-2 for a description of the Fibre Channel layers.
TABLE 1-2 Fibre Channel Layers
ULPsSCSIIPIIPSBCCSHIPPI
FC-4 • Upper Level Protocol Mapping
• Mapping of ULP functions and constructs
FC-3 Common Services
FC-2 Link Service
• Login and Logout services
• Basic and Extended Link services
Signaling Protocol
• Frames, Sequences, and Exchanges
• N_Ports, F_Ports, and Topologies
• Classes of Service (1, 2, and 3)
• Buffer-to-Buffer/end-to-end flow control
Overview
FC-AL Arbitrated Loop Functions
• Ordered sets for loop arbitration
• Loop Initialization
• Physical address assignments
FC-1 Transmission Protocol
• Encoding and Decoding
• Link management
• Error monitoring
FC-0 Physical Interface
• Transmitters, receivers, and Bandwidth
Media
• Cables and Connectors
August 2016General Information 21
Page 22
Tape Drive Description
Tape Drive Description
Size:The T10000 tape drive is a small, modular, high-performance tape drive
designed for high-capacity storage of data. The drive is:
• Height = 8.89 cm (3.5 in.)
• Width = 14.6 cm (5.75 in.)
• Depth = 42.5 cm (16.75 in.)
Capacity:The T10000 uses a technology called partial response, maximum likelihood
(PRML) to provide the high-density data format that allows the tape drive to
record and store up to:
• T10000A = 500 gigabytes (GB) of uncompressed data.
• T10000B = 1 terabyte (TB) of uncompressed data.
• T10000C = 5 terabytes (TB) of uncompressed data.
• T10000D = 8 terabytes (TB) of uncompressed data.
Media:The new tape cartridge for this drive uses a single-reel hub for high capacity;
the supply reel is inside the cartridge and the take-up reel is inside the tape
drive.
Interface:The host connections to the T10000 are fiber-optic to provide a high rate of data
transfer, such as Fibre Channel and FICON.
Configurations:The T10000 supports two configurations: library and stand-alone,
for a variety of operating system platforms:
• Enterprise mainframes (z/OS and OS/390)
• Open system platforms (Windows, UNIX, and Linux)
FIGURE 1-1 on page 23 shows a rear view of the T10000A and T10000B tape drive.
FIGURE 1-2 on page 23 shows a rear view of the T10000C tape drive.
FIGURE 1-3 on page 24 shows a rear view of the T10000D tape drive.
22 T10000: Interface Reference ManualAugust 2016
Page 23
FIGURE 1-1 T10000A and T10000B Tape Drive Rear View
1. Drive status LED5. Ethernet port
Tape Drive Description
2. Recessed switch (service only)6. Encryption status LED
3. Tape transport interface (TTI) connector 7. Power supply connector
4. Fibre Channel, LC interface ports (2) A & B
FIGURE 1-2 T10000C Tape Drive Rear View
1. Drive status LED5. Fibre Channel, LC interface ports (2) A & B
2. Tape transport interface (TTI) connector 6. RJ-45 Ethernet connector
3. Recessed switch (service only) 7. Encryption status LED
4. Power supply connector
August 2016General Information 23
Page 24
Tape Drive Description
FIGURE 1-3 T10000D Tape Drive Rear View
1. Tape transport interface (TTI) connector 4. Fibre Channel, LC interface ports (2) A & B
This chapter describes how StorageTek tape drives operate using a Fibre Channel
(FC) interface.
Connections
The T10000 tape drives support various connections:
• 2FC = Direct N_Port, Arbitrated Loop, and a Fabric
• 4FC = Direct N_Port, Arbitrated Loop, and a Fabric
• 8FC = Direct N_Port, Arbitrated Loop, and a Fabric
2
Operations
Note – This document is defined by the requirements in FC-Tape
Revision 1.17. As updates occur to the FC-Tape document, this
document will be updated accordingly.
• 16FC = Direct N_Port, and a Fabric
Arbitrated Loop
An arbitrated loop provides multiple connections for devices that share a single loop,
but only provides point-to-point connections between an initiator and target during
communications.
Note – Both public loops and private loops are supported.
As with SCSI protocol, when devices want to communicate on the bus, they must
arbitrate and win the connection before communications can begin. The same goes
with the arbitrated loop. Once a device is powered-on and initialized on the loop, it
must arbitrate and win to be able to communicate with other devices on the loop.
Fabric Attachment
Fabric, or F_Ports, provide “direct” attachments to the tape drives. The Fabric
receives frames from a source N_Port and routes them to a destination N_Port whose
address identifier is specified within the frame.
August 2016Operations 29
Page 30
Direct N_Port Attachment
Direct N_Port Attachment
The T10000 tape drives support direct attachment to a host through a host bus
adapter (HBA) that creates an N-Port. The HBA sends and receives to and from the
tape drive.
Addressing
StorageTek tape drives use: Port name, Node name, and Port ID for login validation.
The StorageTek registration ID is 24 bits consisting of:
• 00104F (hex)
TABLE 2-1 indicates the Institute of Electrical and Electronics Engineers (IEEE)
registered format for Name Address Authority (NAA), company ID, and vendor
specific identifier for a total of 64 bits.
TABLE 2-1 Addressing Scheme
Most Significant Bit Least Significant Bit
6360 5936 3500
NAAIEEE Company IDVendor Specific Identifier
“0101” (b)00 10 4F (hex)(to be assigned)
All ports validate the logins by comparing Port Name, Node Name, and Port ID. All
three identifiers must match or this indicates the configuration has changed and
requires a Logout (LOGO).
Note – A LOGO terminates all open Exchanges between SCSI
initiator and target.
30 T10000: Interface Reference ManualAugust 2016
Page 31
SCSI Features
The following sections describe the SCSI features supported by the tape drives.
Auto Contingent Allegiance
StorageTek tape drives do not support Auto Contingent Allegiance (ACA).
Asynchronous Event Notification
StorageTek tape drives do not support asynchronous event notification (AEN).
Command Linking
StorageTek tape drives do not support Command Linking. The Link and Flag bits of
the Command Descriptor Block must be set to zero.
Status Byte
SCSI Features
The target returns a status byte to the initiator at the completion of each command
during the Status phase unless the command is cleared or interrupted. The tape
drives support five status byte codes:
• Busy
• Check Condition
• Good
• Reservation Conflict
• Task Set Full
August 2016Operations 31
Page 32
Status Byte
Busy
Busy (08) status occurs when the target:
• Is busy performing another operation
• Cannot accept a command
The normal initiator recovery from a Busy status is to reissue the command.
Check Condition
Check Condition (02) status occurs when any error, unit exception, or abnormal
condition that generates sense data occurs.
Check Condition status occurs when one of the following conditions exist:
• Issuing an invalid command or parameter
• Issuing a motion command to a device that is not ready
• Issuing a write-type command to a file-protected cartridge
• Issuing a forward motion command to a device at the physical end-of-tape
• Issuing a backspace operation to a device at the beginning-of-tape
• Detecting a deferred check condition
• Exceeding the retry operations for an interface error
• Detecting any error condition that prevents successful completion of an operation
Good
Good (00) status indicates that the device successfully completed the command.
Reservation Conflict
Reservation Conflict (18) status is returned whenever a SCSI initiator attempts an
operation that violates another initiator’s Logical Unit Reservation.
Task Set Full
Task Set Full (28) status is returned when the logical unit receives a command and
does not have enough resources to process it.
32 T10000: Interface Reference ManualAugust 2016
Page 33
Device Reservations
Device Reservations
The T10000 tape drives support the Reserve/Release management method and also
the Persistent Reservations management method. These methods are defined in the
ANSI SCSI-3 Primary Commands (SPC-2) standard.
• See TABLE 2-2 for the reservation restrictions placed on commands for the
Reserve/Release management method.
• See TABLE 2-3 on page 35 for the reservation restrictions placed on the Persistent
Reservations management method.
Each method lists the type of restriction for the command being performed:
Conflict
Command will not be performed and the drive will terminate the command with
Reservation Conflict status.
Allowed
Command will be allowed to execute to normal completion.
TABLE 2-2 Reserve/Release Management Method
CommandAction when Reserved by a different Initiator
This chapter defines the SCSI-3 commands for the StorageTek T10000 Tape Drive with
a Fibre Channel interface.
StorageTek uses the SCSI-3 command set to transfer commands and data over Fibre
Channel. The following describes how StorageTek implements these SCSI commands:
• A single command may transfer one or more logical blocks of data.
• The target may disconnect from the arbitrated loop to allow activity by other SCSI
devices while a device prepares to transfer data.
• On completion of normal commands (successful or unsuccessful), the target
returns a Status Byte to the initiator. Because most error and exception conditions
cannot be adequately described with a single status byte, a Check Condition status
code indicates that additional information is available in the FCP Response
Information Unit (IU).
• An initiator should never attempt to send a second command to a device until the
command in progress ends. The second command terminates with a Check
Condition status (Command Overrun).
Commands
TABLE 3-1 lists the supported commands and references the appropriate page.
The initiator sends commands to the target using Command Descriptor Blocks
(CDBs). The CDBs contain a format that includes:
• Operation code
• Command parameters
• Control byte
For some commands, a list of parameters accompanies the request during subsequent
FCP_DATA Information Units.
For all commands, if there is an invalid parameter in the Command Descriptor Block,
then the device terminates the command without altering the medium or executing
the command.
Notes:
• The CDB Field in Byte 1, Bits 7-5, which was the LUN Field is now
reserved. The drive will ignore this field.
• RSVD indicates that “bit” is reserved.
Implementation Requirements
August 2016 Commands 39
Page 40
Command Descriptor Block
Command Descriptor Block
Initiators use three types of CDBs to communicate commands to the targets:
• 6–Byte commands (TABLE 3-2)
• 10–Byte commands (TABLE 3-3)
• 12-Byte commands (TABLE 3-4)
• 16-Byte commands (TABLE 3-5)
The first byte in the command descriptor block contains an operation code.
The control byte is the last byte of every Command Descriptor Block and has the
following structure:
TABLE 3-6 Control Byte
Bit
Byte
5/9/11/
76543210
Vendor-specificReservedFlagLink
15
Parameter Value
Vendor-specificThese bits provide specific information about the device
(shall be zero).
Flag bitThe flag bit causes an interrupt in the initiator between linked
commands allowing the device to respond with Intermediate
status (shall be zero).
Link bitThe link bit allows the initiator to “link” or continue I/O
process and allows devices that support command linking to
indicate to the initiator the command was accepted by
returning Intermediate status to the initiator (shall be zero).
42 T10000: Interface Reference ManualAugust 2016
Page 43
Erase Command
The Erase command erases the remainder of the tape starting at the current, logical
position. Any buffered write data and filemarks are written on the tape before the
erase operation starts.
Note – At the completion of the Erase command, the tape is
positioned at the physical end-of-volume (PEOV) if the data
security erase (DSE) configuration option is set to full.
TABLE 3-7 Erase Command
Erase Command
Bit
Byte
0Operation Code (19h)
1ReservedImmedLong
2
thru
4
5Control Byte
ParameterValue
Immed: Immediate0 = Return status when erase is completed
Long: Long0 = Ignored, no erase performed
76543210
(MSB)
Reserved
1 = Return status when erase is started
1 = Erase to the physical end-of-volume starting at the current
logical position.
Note – Issuing a Test Unit Ready command after an Erase
command with the Immed bit set returns Busy status until the
erase is complete.
(LSB)
August 2016 Commands 43
Page 44
Generate Recommended Access Order Command
Generate Recommended Access Order Command
The Generate Recommended Access Order (GRAO) command generates a
recommended access order for the User Data Segments that are sent by the command
as parameter data. The GRAO command is defined by an operation code and Service
Action. The GRAO parameter list is processed before status for the command is
returned. After the GRAO command completes the Receive Recommended Access
Order (RRAO) command can be used to receive the results in the form of a
Recommended Access Order (RAO) list.
TABLE 3-8 Generate Recommended Access Order Command
Bit
Byte
0Operation Code(A4H)
1ReservedService Action (11h)
2Reserved
3Reserved
4
thru
5
6
thru
9
10Reserved
11Control Byte
ParameterValue
RAO Process: Method used to
generate RAO list
76543210
Reserved
(MSB)
Parameter List Length
000b = List of user data segments not reordered, estimated
locate times from current position to first logical block
RAO Process
UDS_Type
(LSB)
001b = List of user data segments not reordered, estimated
locate times from current position to first logical block and
then from last logical block in previous user data segment to
first logical object in this user data segment.
010b = List of user data segments is reordered into the
recommended access order, estimated locate times from
current position to first logical block in the reordered list and
then from last logical block in previous user data segment to
first logical object of this user data segment.
000b = List of user data segments not reordered, estimated
locate times from beginning of partition 0 to the position to
first logical block in each user data segment.
44 T10000: Interface Reference ManualAugust 2016
Page 45
ParameterValue
Generate Recommended Access Order Command
UDS Type: Format of the User Data
000b = User Data Segment
Segment descriptor to be used in the
resulting RAO list
Parameter List Length: Length in
00000000h = Clear RAO list
bytes of GRAO list transferred from
initiator.
TABLE 3-9 Generate Recommended Access Order Parameter List
Bit
Byte
76543210
0
thru
Reserved
3
4
thru
(MSB)
Additional Data (n-7)
7
User Data Segment Descriptor List
(MSB)
User Data Segment descriptor (first)
x
(LSB)
(LSB)
y
thru
n
...
(MSB)
User Data Segment descriptor (last)
UDS Descriptor List Length: Number of bytes to follow
User Data Segment Descriptor List: List of UDS's to be processed
(LSB)
August 2016 Commands 45
Page 46
Generate Recommended Access Order Command
TABLE 3-10 GRAO - User Data Segment descriptor
Bit
Byte
0
thru
76543210
(MSB)
Descriptor Length (1Eh)
1
2Reserved
3Reserved
4Reserved
5
thru
(MSB)
UDS Name
14
15Partition Number
16
thru
(MSB)
Beginning Logical Object Identifier
23
24
thru
(MSB)
Ending Logical Object Identifier
31
Descriptor Length: number of bytes to follow
UDS Name: Host specified name for User Data Segment
(LSB)
(LSB)
(LSB)
(LSB)
Partition Number: Number of partition in which User Data Segment is located.
Beginning Logical Object Identifier: Logical object identifier of first logical object in
User Data Segment
Ending Logical Object Identifier: Logical object identifier of last logical object in User
Data Segment
46 T10000: Interface Reference ManualAugust 2016
Page 47
Format Medium Command
The Format Medium command is used partition the medium. The command must be
issued only after positioning the tape to beginning of partition 0.
TABLE 3-11 Format Medium Command
Format Medium Command
Bit
Byte
0Operation Code (04h)
1ReservedVerifyImmed
2Reserved
3
thru
4
5Control Byte
ParameterValue
Verify: Verify that format was
successful
Immed: Immediate0 = Return status after format completes
Format0h = Use default partition (non partitioned tape)
Transfer Length0000h = No data is transferred for format medium command
76543210
Format
Transfer Length
0 = Not supported
2h = Partition tape according to mode page 11h
August 2016 Commands 47
Page 48
Inquiry Command
Inquiry Command
The Inquiry command returns information about the type and capabilities of a SCSI
device.
TABLE 3-12 Inquiry Command
Bit
Byte
76543210
0Operation Code (12h)
1ReservedCmdDtEVPD
2Page Code
3
thru
(MSB)
Allocation Length
4
5Control Byte
Parameter Value
CmdDt: Command support Data0 = Do not return command support data
EVPD: Enable Vital Product Data0 = Return normal inquiry data
1 = Return Vital Product Data
Page CodeEVPD page to return
Allocation LengthSpecifies the maximum length of inquiry data to return
Notes:
• The Inquiry command returns 74 bytes of data. If the allocation length is less
than 74 bytes, the data is truncated.
(LSB)
• The Inquiry command returns check condition status only when the requested
data cannot be returned. This command will not clear any pending unit
attention conditions.
48 T10000: Interface Reference ManualAugust 2016
Page 49
Inquiry Data Format
The Inquiry data format contains 74 bytes shown in TABLE 3-13.
TABLE 3-13 Inquiry Data Format
Inquiry Command
Bit
Byte
76543210
0Peripheral QualifierPeripheral Device Type
1RMBReserved
2ECMA Version
3AERCRSVDNormACAHiSupResponse Data Format
4Additional Length (n - 4)
5SCCSACCTPGS3PCReservedProtect
6BQueEncServVSMultiPMChngrReserved
7RelAdrReservedLinkedRSVDCmdQueVS
8
thru
(MSB)
Vendor Identification
15
16
thru
(MSB)
Product Identification
31
32
thru
(MSB)
Product Revision Level
39
(LSB)
(LSB)
(LSB)
40
thru
53
(MSB)
Vendor Specific
(LSB)
54Key Management (KM)
55ReservedEncryptLibAttVolSafeDCMPCSL
56
thru
57
58
thru
73
August 2016 Commands 49
(MSB)
(MSB)
Reserved
Version Descriptor 1 to 8 (2 bytes each)
(LSB)
(LSB)
Page 50
Inquiry Command
ParameterValue
Peripheral Qualifier000b = Peripheral device is connected to this logical unit
011b = Not capable of supporting a device on this logical unit
Peripheral Device Type01h = Device is a sequential access device (tape drive)
1Fh = Device does not exist or is offline
RMB: Removable Medium Bit1 = Medium is removable
ECMA Version
05h = Complies with ANSI INCITS 408-2005 (SPC-3)
European Computer Manufacturers
Association
AERC: Asynchronous Event
0 = Not supported
Reporting Capability
NormACA: Normal Auto Contingent
0 = Not supported
Allegiance
HiSup: Hierarchical Support0 = Not supported
Response Data Format02 = Inquiry data is in ANSI SPC–2 format
Additional Length45h = 69 additional bytes of data follows
SCCS: SCSI Controller Command
0 = Not supported
Support
ACC: Access Controls Coordinator0 = Not supported
TPGS: Target Port Group Support01b = Supports only implicit asymmetric logical unit access
3PC: Third-Party Copy0 = Not supported
Protect0 = The logical unit does not support protection information.
1 = The logical unit supports protection information.
BQue: Basic Queuing0 = Not Supported
EncServ: Enclosure Services0 = Not supported
VS: Vendor Specific0 = Not supported
MultiP: Multi-Port1 = Supports two ports
MChngr: Medium Changer0 = Not supported
RelAdr: Relative Address0 = Not supported
Linked: Linked commands0 = Not supported
CmdQue: Command Queuing0 = Not supported
Vendor IdentificationSTK = StorageTek, Sun Microsystems (ASCII)
Product Identification:
Device type in ASCII
T10000A = Drive is a T10000A
T10000B = Drive is a T10000B
T10000C = Drive is a T10000C
T10000D = Drive is a T10000D
50 T10000: Interface Reference ManualAugust 2016
Page 51
ParameterValue
Inquiry Command
Product Revision:
8 byte ASCII field
For example: 4XX1YY where XX=02 and YY=03 (402103)
indicates:
• Model number for T10000D = 4,
• Major Revision = 02,
• Released code = 1,
• Minor release = 03
These 6 characters will be left justified with blank fill as
needed.
This field will change with each drive firmware release.
VS: Vendor SpecificVendor Specific
0 = Not supported
Key Management (KM)0 = None
1 = Key Management Station (KMS) Version 1
2 = Key Management System (KMS) Version 2
4 = Data Path Key Management (DPKM) Spin/Spout
Encrypt: EncryptionEncryption:
0 = Not encrypting drive
1 = Encrypting drive
LibAtt: Library AttachLibrary Attachment:
0 = Drive is not attached to a library
1 = Drive is attached to a library
VolSafe: VolSafe available1 = VolSafe enabled
A Sun StorageTek write once, read many (WORM) technology
to designated tape cartridges.
DCMP: Data Compression0 = Data compression is disabled
1 = Data compression is enabled
CSL:
0 = CSL is not installed
Cartridge Scratch Loader installed
Version DescriptorStandards supported by this device:
• 0000h = Empty
• 0077h = SAM-3_ANSI_INCITS.402:2005
• 0314h = SPC-3_ANSI_INCITS.408:2005
• 0403h = SSC-3 T10/1611-D Revision 04a
• 0A11h = FCP-3_ANSI_INCITS.416:2006
August 2016 Commands 51
Page 52
Inquiry Command
Vital Product Data Pages
There are three vital product data pages that contain specific information:
Vital Product Data (VPD)
Page Code = 00h returns a list of the supported VPD pages.
TABLE 3-15 Device Serial Number Page
Bit
Byte
76543210
0Peripheral QualifierPeripheral Device Type
1Page Code (80h)
2Reserved
3Page Length (0Ch)
4
thru
15
(MSB)
Serial Number (ASCII)
(LSB)
Page Code = 80h returns the tape drive serial number in ASCII.
52 T10000: Interface Reference ManualAugust 2016
Page 53
.
TABLE 3-16 Device Identification Page
Inquiry Command
Bit
Byte
76543210
0Peripheral QualifierPeripheral Device Type
1Page Code (83h)
2Reserved
3Page Length (28h)
Node Name Identifier
4ReservedCode Set (1)
5ReservedAssociation (0)Identifier Type (3)
6Reserved
7Identifier Length (08h)
8
thru
(MSB)
Node Identifier (binary)
15
Port Name Identifier
16ReservedCode Set (1)
17ReservedAssociation (1)Identifier Type (3)
18Reserved
(LSB)
19Identifier Length (08h)
20
thru
(MSB)
Port Identifier (binary)
27
Port Number Identifier
28ReservedCode Set (1)
29ReservedAssociation (1)Identifier Type (4)
30Reserved
31Identifier Length (04h)
32
thru
(MSB)
Port Identifier (binary)
35
Target Port Group
36ReservedCode Set (1)
37ReservedAssociation (1)Identifier Type (5)
38Reserved
39Identifier Length (04h)
(LSB)
(LSB)
August 2016 Commands 53
Page 54
Inquiry Command
TABLE 3-16 Device Identification Page (Continued)
Bit
Byte
40
thru
76543210
(MSB)
Target Port Group Identifier (binary)
41
ParameterValue
Page Code83h returns four identifying numbers.
• World Wide Name (WWN) for the tape drive
• WWN for the port that accepted the Inquiry command
• Port Number (1 or 2) for that port
• Target Port Group Descriptor
Code Set1h = Identifier field contains binary values
Association00b = Identifier is for the device
01b = Identifier is for a port
Identifier Type3h = Identifier field contains a 64 bit IEEE registeredformat
address, also known as a World Wide Name.
4h = Identifier field contains a 4 byte port number
(LSB)
Identifier LengthLength in bytes of the WWN or Port Number Identifier
Node IdentifierContains the device WWN
Port IdentifierContains WWN for the current port
Port Number
Number for the current port
01h = Command accepted by device port A
02h = Command accepted by device port B
Target Port GroupContains the primary Target Port Group
54 T10000: Interface Reference ManualAugust 2016
Page 55
TABLE 3-17 Management Network Addresses Page
Inquiry Command
Bit
Byte
76543210
0Peripheral Qualifier (000b)Peripheral Device Type (01h)
1Page Code (85h)
2
3
Page Length (1Eh)
4RSVDAssociationService Type
5Reserved
6
thru
(MSB)
Network Address Length
7
8
thru
(MSB)
Network Address
33
Parameter Value
Peripheral Qualifier000b = Peripheral Device is connected to this Logical Unit
Peripheral Device Type01h = Device is a sequential-access device (tape drive)
Association2h = Network address is associated with this SCSI target
device
(LSB)
(LSB)
Service Type00h = Service type is unspecified
Network Address
The URL of the accessing drive
management port
For example, TELNET://123.345.123.123/
Field is an ASCII string terminated with one or more null
(00h) characters. If management port is not connected to an
active network, field will be filled with 00h.
0Peripheral Qualifier (000b)Peripheral Device Type (01h)
1Page Code (B0h)
2
thru
Page Length (02h)
3
4ReservedWORM
5Reserved
Parameter Value
Peripheral Qualifier000b = Peripheral Device is connected to this Logical Unit
Peripheral Device Type01h = Device is a sequential-access device (tape drive)
WORM1 = Device supports write once, read many (WORM) modes of
operation (VolSafe)
56 T10000: Interface Reference ManualAugust 2016
Page 57
Load Display Command
The Load Display command (vendor specific) displays ASCII messages on the virtual
operator panel for that device. This command transfers 17 bytes of data to the
display. The data transferred contains one byte of display control data and two, eightbyte ASCII messages.
TABLE 3-19 Load Display Command
Load Display Command
Bit
Byte
0Operation Code (06h)
1Reserved
2Reserved
3Reserved
4Transfer Length (11h)
5Control Byte
76543210
Load Display Data Format
TABLE 3-20 Load Display Data Bytes
Bit
Byte
0OverlayAltBlinkL/HReserved
1
thru
8
9
thru
16
76543210
(MSB)
(ASCII) Message 1
(MSB)
(ASCII) Message 2
(LSB)
(LSB)
Notes:
• Messages in bytes 1–8 and 9–16 use the ASCII printable character set.
• Non-printable characters are displayed as blanks.
• The format control byte controls the way the device displays the remaining 16
bytes.
August 2016 Commands 57
Page 58
Load Display Command
ParameterValue
Overlay: New message overlay000 = Display the message in bytes 1–8 or 9–16 until the next
command that initiates tape motion or the next Load Display
Command.
001 = Maintain the message in bytes 1–8 until the cartridge is
unloaded. If the drive does not contain a cartridge when the
Load Display Command is received, the message will not be
changed.
010 = Maintain the message in bytes 1–8 and turn on the
Attention light until the drive is next loaded. If the drive is
loaded when the Load Display Command is received, the
command is ignored.
011 = Physically access the tape drive without changing the
message display.
111 = Display the message in bytes 1–8 until the tape drive is
unloaded, then display the message in bytes 9–16 until the
tape drive is loaded again. If the tape drive is not loaded
when the Load Display Command is issued, only the message
in bytes 9–16 are displayed.
Alt: Alternate message0 = The device displays only the message specified in bit 2.
1 = The device alternately displays both messages specified in
bytes 1–8 and 9–16. Each message is displayed for about two
seconds, with 0.5 seconds between messages. Bits 2 and 3 are
ignored.
Blink: Blinking message0 = The message specified by the setting of bit 2 does not
blink.
1 = The message specified by the setting of bit 2 flashes on and
off.
The Load/Unload command loads or unloads tape from the device. Any buffered
write data and filemarks are written on the tape before an unload starts.
Caution – If the drive is in Buffered Mode and a previous
command terminated with Check Condition status (such as
buffered data unwritten to tape and the condition was not cleared
or otherwise recovered), the drive will discard any unwritten
buffered data and filemarks before this operation starts.
TABLE 3-21 Load/Unload Command
Load/Unload Command
Bit
Byte
0Operation Code (1Bh)
1ReservedImmed
2
thru
3
4ReservedHoldEOTRetenLoad
5Control Byte
Parameter Value
Immed: Immediate0 = Return status when load or unload is complete
HoldNot supported
EOT: End-Of-Tape0 = Tape is unloaded from BOT
Reten: Retention0 = Do not retention the tape
Load0 = Unload the tape
76543210
(MSB)
Reserved
1 = Return status when load or unload is started
0 = Normal load/unload
1 = Retention tape (ignored)
1 = Load the tape
(LSB)
Notes:
• After a load or unload operation with the Immediate bit set, a Test Unit
Ready command returns Busy status while the Load/Unload command is
still in progress.
• After a successful load operation, Good status is returned. The next
command returns a sense key of unit attention.
• If a Load command is issued when a tape is already loaded, the Load
command is ignored.
• If the drive is installed in a library, a load command to an unloaded drive is
rejected.
August 2016 Commands 59
Page 60
Locate Command
• When the drive needs cleaning, an unload will return Check Condition status
with a Sense Key of 0h and an ASC/ASCQ of 0017h indicating the tape drive
requires cleaning.
Locate Command
The Locate command requests the tape drive to position the tape to a specified block
address. Any buffered write data and filemarks are written on the tape before this
operation starts.
Parameter PointerReturn data starting at this parameter code
Allocation LengthMaximum length of parameter data to transfer
64 T10000: Interface Reference ManualAugust 2016
Page 65
Log Sense Page Format
Each log page begins with a four–byte page header followed by variable–length log
parameters.
TABLE 3-27 Log Sense Page Format
Log Sense Command
Bit
Byte
76543210
0ReservedPage Code
1Reserved
2
thru
(MSB)
Page Length (n-3)
3
Log Parameter(s)
4Log Parameter (First)
x + 3(Length = x)
.
.
.
n-y+1Log Parameter (Last)
n(Length = y)
Note – The page length reflects the absolute length of the page, and is not adjusted
because of the allocation length or the parameter pointer fields.
Log Sense Parameter Format
TABLE 3-28 Log Sense Parameter Format
(LSB)
Bit
Byte
0
thru
1
76543210
(MSB)
Parameter Code
(LSB)
2DUDSTSDETCTMCRSVDLP
3Parameter Length (n-3)
4
thru
n
August 2016 Commands 65
(MSB)
Parameter Value
(LSB)
Page 66
Log Sense Command
Parameter Value
Parameter CodeIdentifies the log parameter being transferred
DU: Disable Update0 = Drive updates log parameter value
DS: Disable Save1 = saving the log is not supported
TSD: Target Save Disable0 = Target provides a target defined method for saving log
parameters
1 = Target does not provide a target defined method for saving
the log parameters
ETC: Enable Threshold Comparison0 = Comparison is not performed
1 = Comparison is performed
TMC: Threshold Met Criteria00b = Every update
01b = Cumulative value equal threshold value
10b = Cumulative value not equal threshold value
11b = Cumulative value greater than threshold value
LP: List Parameter0 = Log parameter is a data counter.
Log Sense Supported Pages
The Log Sense supported pages report which pages the tape drive supports.
TABLE 3-29 lists pages for the T10000A or T10000B tape drives while TABLE 3-30
on page 67 lists the pages for the T10000C or T10000D tape drives.
TABLE 3-29 Log Sense Supported Pages (T10000A or T10000B only)
Bit
Byte
0ReservedPage Code (00h)
1Reserved
2
thru
3
4Supported Log Pages (00h)
5Write Error Counter Page (02h)
6Read Error Counter Page (03h)
7Non-medium Error Page (06h)
8Sequential Access Device Page (0Ch)
76543210
(MSB)
Page Length (08h)
(LSB)
9Tape Alert Page (2Eh)
10Vendor Unique Drive Statistics Page (3Ah)
11Vendor Unique Port Statistics Page (3Bh)
66 T10000: Interface Reference ManualAugust 2016
Page 67
TABLE 3-30 Log Sense Supported Pages (T10000C only)
Bit
Log Sense Command
Byte
76543210
0ReservedPage Code (00h)
1Reserved
2
thru
(MSB)
Page Length (08h)
3
4Supported Log Pages (00h)
5Write Error Counter Page (02h)
6Read Error Counter Page (03h)
7Non-medium Error Page (06h)
8Sequential Access Device Page (0Ch)
9Tape Alert Page (2Eh)
10Vendor Unique Port Statistics Page (3Bh)
11Vendor Unique Drive Statistics Page (3Ch)
TABLE 3-31 Log Sense Supported Pages (T10000D only)
Bit
(LSB)
Byte
76543210
0ReservedPage Code (00h)
1Reserved
2
thru
(MSB)
Page Length (08h)
3
4Supported Log Pages (00h)
5Write Error Counter Page (02h)
6Read Error Counter Page (03h)
7Non-medium Error Page (06h)
8Sequential Access Device Page (0Ch)
9Tape Alert Page (2Eh)
10Vendor Unique Port Statistics Page (3Bh)
11Vendor Unique Drive Statistics Page (3Dh)
(LSB)
August 2016 Commands 67
Page 68
Log Sense Command
Log Page 3C Subpage 01
The Log Page 3C Subpage 01 is used to check the status of a completed Media
Validation on a T10000C Tape Drive.
TABLE 3-32 Data Returned for Log Page 3C Subpage 01
Parameter CodeDescriptionSize in bytes
0101hPercent Complete4
0102hReserved4
0103hHLU ID Completed8
0104hPartition Completed4
0105hPerm4
0106hElapsed Time4
0107hStart HLU ID8
0108hStart Partition4
68 T10000: Interface Reference ManualAugust 2016
Page 69
Log page 3D Subpage 01
The Log Page 3D Subpage 01 is used to check the status of a completed Media
Validation on a T10000D Tape Drive.
TABLE 3-33 Data Returned for Log Page 3D Subpage 01
Parameter CodeDescriptionSize in bytes
0101hPercent Complete4
0102hReserved4
0103hHLU ID Completed8
0104hPartition Completed4
0105hPerm4
0106hElapsed Time4
0107hStart HLU ID8
0108hStart Partition4
Log Sense Command
August 2016 Commands 69
Page 70
Log Sense Command
Write Error Counter Page
The Write Error Counter page (02h) reports write statistical errors. Each parameter is
a counter incriminated by the target each time a corresponding event occurs.
TABLE 3-34 Write Error Counter Page Codes
Parameter
CodeDescription
Length
(bytes)
Default
Threshold
0000hErrors corrected without substantial delays4FFFFFFFF
0001hErrors corrected with possible delays4FFFFFFFF
0002hTotal number of re-writes4FFFFFFFF
0003hNumber of records with a recovered data check
4FFFFFFFF
while writing
0004hAlways 04FFFFFFFF
0005hNumber of non–compressed bytes transferred from
the initiator
8FFFFFFFF
FFFFFFFF
0006hTotal number of uncorrected errors4FFFFFFFF
70 T10000: Interface Reference ManualAugust 2016
Page 71
Read Error Counter Page
The Read Error Counter page (03h) reports statistical errors for read operations. Each
parameter is a counter that the target increments when an event occurs.
TABLE 3-35 Read Error Counter Page Codes
Log Sense Command
Parameter
CodeDescription
Length
(bytes)
0000hErrors corrected without substantial delays4FFFFFFFF
0001hErrors corrected with possible delays4FFFFFFFF
0002hTotal number of re-reads4FFFFFFFF
0003hNumber of records with a recovered data check
4FFFFFFFF
while reading
0004hNumber of times a record was retried before recovery
4FFFFFFFF
either passed or failed
0005hNumber of non–compressed bytes transferred to
8FFFFFFFF
the initiator
0006hTotal number of uncorrected errors4FFFFFFFF
Non-Medium Error Page
The Non-Medium Error page (06h) reports a count of recoverable errors other than
read/write failures.
TABLE 3-36 Non-Medium Error Page Codes
Parameter
CodeDescription
Length
(bytes)
Default
Threshold
FFFFFFFF
Default
Threshold
0000hNon-medium error count4FFFFFFFF
August 2016 Commands 71
Page 72
Log Sense Command
Sequential Access Device Page
The Sequential Access Device page (0Ch) returns counts of data bytes transferred to
and from tape and information about cleaning in binary format.
TABLE 3-37 Sequential Access Device Page Codes
Parameter
CodeDescription
0000hNumber of bytes received from the initiator
(write command)
0001hNumber of data bytes written on tape8FFFFFFFF
0002hNumber of bytes read from tape8FFFFFFFF
0003hNumber of bytes read by the initiator8FFFFFFFF
0100hCleaning
000 = No cleaning required
001 = Cleaning required
8000hNumber of 4k bytes left on tape from the current position4N/A
Length
(bytes)
8FFFFFFFF
4N/A
TapeAlert Page
The TapeAlert Log Sense page (2Eh) is read from a tape drive at the following times,
as a minimum:
• At the beginning of a write/read job, after the media is loaded.
Default
Threshold
FFFFFFFF
FFFFFFFF
FFFFFFFF
FFFFFFFF
• Immediately after a fatal error during the write/read job.
• At the end of each tape when the write/read job spans multiple tapes.
• At the end of a write/read job, when the tape has been unloaded.
Each flag will be cleared to zero in the following circumstances:
• At drive power on.
• When the TapeAlert Log page is read.
• When specified corrective action has been taken (such as using a cleaning
cartridge).
• On a reset.
Note – The entire TapeAlert page should be read to obtain all the
information.
When a flag is cleared by reading the TapeAlert page, a flag cannot be set again until
the error condition is removed (for example, the specific corrective action has been
taken).
A Log Select Reset for the TapeAlert page does not reset the TapeAlert flags. It is
rejected with Illegal Request.
72 T10000: Interface Reference ManualAugust 2016
Page 73
Log Sense Command
TapeAlert Flags
TABLE 3-38 TapeAlert Flags
CodeFlag NameDescription
0001hRead WarningDrive has difficulty reading1
0002hWrite WarningDrive has difficulty writing1
Length
(bytes)
0003hHard ErrorWrite or read hard error has occurred
(flags 4, 5, 6)
0004hMediaUnrecoverable read, write, or positioning
error caused by faulty media
0005hRead FailureHard read error, hardware or media1
0006hWrite FailureHard write error, hardware or media1
0007hMedia LifeMedia has exceeded the life pass count1
0008hNot Data GradeNot supported1
0009hWrite ProtectWrite command was issued to a write-
protected tape
000AhNo RemovalA manual unload or Unload command was
issued while the drive was in prevent
removal state – not supported
000BhCleaning MediaThe tape in the drive is a cleaning cartridge1
000ChUnsupported FormatUnrecognized format1
000DhRecoverable Snapped TapeSnapped tape – not supported1
000EhUnrecoverable Snapped TapeNot supported1
000FhMemory Chip in Cartridge Failure The RFID chip cannot be read or written to.1
1
1
1
1
0010hForced EjectA manual eject was performed before a
1
reposition to BOT was commanded.
Not supported
0011hRead Only FormatNot supported1
0012hTape Directory CorruptedMIR corrupted1
0013hNearing Media LifeThe tape is nearing the end of its
1
calculated life
0014hClean NowThe drive has determined it needs cleaning.1
0015hClean PeriodicCleaning counter has reached threshold,
1
cleaning LED is on
0016hExpired Cleaning MediaThe last cleaning cartridge inserted was used
1
up – not supported
0017hInvalid Cleaning MediaNot supported1
0018hRetention RequestedNot supported1
0019hDual port interface errorNot supported1
August 2016 Commands 73
Page 74
Log Sense Command
TABLE 3-38 TapeAlert Flags (Continued)
CodeFlag NameDescription
001AhCooling fan failureNot supported1
001BhPower supply failureNot supported1
001ChPower consumptionNot supported1
Length
(bytes)
001DhDrive MaintenancePreventive maintenance of the drive is
required
001EhHardware ADrive has a hardware fault1
001FhHardware BHardware not read/write related – not
supported
0020hInterfaceHaving problems with the interface, SCSI
parity errors detected
0021hEject MediaEject the media and retry, load failure not
tape snap
0022hDownload FailMicrocode update failed1
0023hDrive HumidityNot supported1
0024hDrive TemperatureTemperature inside the tape drive is above
specified range
0025hDrive VoltageNot supported1
0026hPredictive FailureA hardware failure of the drive is predicted1
0027hDiagnostics RequiredDump available1
0028h
thru
Reserved for CSL
002Eh
1
1
1
1
1
002Fh
thru
Reserved
0031h
0032hLost StatisticsMedia statistics lost some time in the past.1
0033hTape Directory Invalid at UnloadThe tape directory on the tape cartridge just
1
unloaded has been corrupted.
0034hTape System Area Write FailThe tape just unloaded could not write its
1
system area successfully.
0035hTape System Area Read FailThe tape system area could not be read
1
successfully at load time.
0036hNo Start of DataThe start of data could not be found on tape.1
0037hLoading failureThe operation has failed because the media
1
could not be loaded and threaded.
0038hUnrecoverable Unload failureThe operation has failed because the media
1
could not be unloaded.
0039hAutomation Interface failureNot supported.1
74 T10000: Interface Reference ManualAugust 2016
Page 75
TABLE 3-38 TapeAlert Flags (Continued)
CodeFlag NameDescription
Log Sense Command
Length
(bytes)
003AhFirmware failureThe tape drive has reset itself due to a
detected firmware fault.
003Bh
thru
Reserved
0040h
1
August 2016 Commands 75
Page 76
Log Sense Command
Tape Capacity Log Page
The Tape Capacity page (31h) reports the remaining capacity and the maximum
capacity of the tape partitions. The values are in megabytes (1048576 bytes).
The T10000C returns parameters 0001h - 0004h. The T10000D returns parameters
0001h - 0014h.
TABLE 3-39 Tape Capacity Page Codes
CodeDescription
0001hPartition 0 Remaining Capacity4
0002hPartition 1 Remaining Capacity4
0003hPartition 0 Maximum Capacity4
0004hPartition 1 Maximum Capacity4
0005hPartition 2 Remaining Capacity4
0006hPartition 3 Remaining Capacity4
0007hPartition 2 Maximum Capacity4
Length
(bytes)
0008hPartition 3 Maximum Capacity4
0009hPartition 4 Remaining Capacity4
000AhPartition 5 Remaining Capacity4
000BhPartition 4 Maximum Capacity4
000ChPartition 5 Maximum Capacity4
000DhPartition 6 Remaining Capacity4
000EhPartition 7 Remaining Capacity4
000FhPartition 6 Maximum Capacity4
0010hPartition 7 Maximum Capacity4
0011hPartition 8 Remaining Capacity4
0012hPartition 9 Remaining Capacity4
0013hPartition 8 Maximum Capacity4
0014hPartition 9 Maximum Capacity4
A tape partitioned using the partition sizes as specified for the T10000C in the mode
select page 11h above will return maximum capacity values of 22E7h and 414FF5h for
partitions 0 and 1 respectively. A non partitioned tape (only default partition 0) will
return capacity values in parameters 0001h and 0003h.
Partition 0 Maximum Capacity non partitioned tape
T10000A tape = 000746A5h
T10000B tape = 000E8D4Ah
T10000C tape = 0048C273h
T10000D tape = 00746A52h
76 T10000: Interface Reference ManualAugust 2016
Page 77
Vendor Unique Drive Statistics Page
The T10000A and T10000B Vendor Unique Drive Statistics page (3Ah) reports a
variety of vendor unique drive statistics.
TABLE 3-40 T10000A and T10000B Vendor Drive Statistics Page Codes
Log Sense Command
Parameter
CodeDescription
Length
(Bytes)
Default
Threshold
0100hRead forward data checks4FFFFFFFF
0101hWrite data checks4FFFFFFFF
0102hRead data checks without hardware4FFFFFFFF
0103hWrite data checks without hardware4FFFFFFFF
0104hRead recovery retry count4FFFFFFFF
0105hRead transient conditions4FFFFFFFF
0106hWrite transient conditions4FFFFFFFF
0107hServo temporaries4FFFFFFFF
0108hServo transients4FFFFFFFF
0109hCorrections 2t4FFFFFFFF
010AhMatrices with PW1 and PW24FFFFFFFF
010BhMatrices with PWs4FFFFFFFF
010ChProgressive write for servo off track4FFFFFFFF
010DhProgressive write type 14FFFFFFFF
010EhProgressive write type 24FFFFFFFF
010FhSelected channel VR
2
bit insertions4FFFFFFFF
0110hMatrix check diagnostic only4FFFFFFFF
0111hData check diagnostic only4FFFFFFFF
0112hWrite recovery retry count4FFFFFFFF
0200hRead data request time-outs4FFFFFFFF
0201hWrite data request time-outs4FFFFFFFF
0202hData transfer errors4FFFFFFFF
0203hTemporary drive errors4FFFFFFFF
0204hPermanent errors logged4FFFFFFFF
0300hChannel read bytes processed8FFFFFFFF
FFFFFFFF
Notes:
• The device write byte count will include file marks and pad bytes. These additional bytes will
not be included in the device read byte count.
• Parameters 0400 – 0402 will not be reset by a Log Select command.
1100hServo general purpose counter head 016all FF's
1101hServo general purpose counter head 116all FF's
1200hServo vote out head 032all FF's
1201hServo vote out head 132all FF's
1202hServo no data available head 032all FF's
1203hServo no data available head 132all FF's
1310hPES histogram head 0 A128all FF's
1311hPES histogram head 0 B128all FF's
1320hPES histogram head 1 A128all FF’s
1321hPES histogram head 1 B128all FF’s
1400hOld VR2blocks128all FF's
1401hLow Viterbi metric 0128all FF's
1402hLow Viterbi metric 1128all FF's
1403hLow Viterbi metric 2128all FF's
1404hInner ECC correction128all FF's
1405hData valid128all FF's
1406hOuter ECC correction128all FF's
Notes:
• The device write byte count will include file marks and pad bytes. These additional bytes will
not be included in the device read byte count.
• Parameters 0400 – 0402 will not be reset by a Log Select command.
August 2016 Commands 79
Page 80
Log Sense Command
Vendor Unique Port Statistics Page
The Vendor Unique Port Statistics page (3Bh) reports error counts and small formfactor plug (SFP) information for each Fibre Channel port on the drive.
TABLE 3-41 Vendor Port Statistics Page Codes
Parameter
CodeDescription
Length
(Bytes)
Default
Threshold
0100hPort A link failure count4FFFFFFFF
0101hPort A loss of sync count4FFFFFFFF
0102hPort A loss of signal count4FFFFFFFF
0103hPort A prim seq errors count4FFFFFFFF
0104hPort A invalid transmit word count4FFFFFFFF
0105hPort A invalid CRC count4FFFFFFFF
0110hPort A SFP missing4FFFFFFFF
0111hPort A SFP loss of signal4FFFFFFFF
0112hPort A SFP fault4FFFFFFFF
0120hPort A SCSI command count8FFFFFFFF
FFFFFFFF
0121hPort A SRR count4FFFFFFFF
0200hPort B link failure count4FFFFFFFF
0201hPort B loss of sync count4FFFFFFFF
0202hPort B loss of signal count4FFFFFFFF
0203hPort B prim seq error count4FFFFFFFF
0204hPort B invalid transmit word count4FFFFFFFF
0205hPort B invalid CRC count4FFFFFFFF
0210hPort B SFP missing4FFFFFFFF
0211hPort B SFP loss of signal4FFFFFFFF
0212hPort B SFP fault4FFFFFFFF
0220hPort B SCSI command count8FFFFFFFF
FFFFFFFF
0221hPort B SRR count4FFFFFFFF
1100hPort A SFP ID block128all 00's
1110hPort A SFP monitor block128all 00's
1200hPort B SFP ID block128all 00's
1210hPort B SFP monitor block128all 00's
80 T10000: Interface Reference ManualAugust 2016
Page 81
Vendor Unique Drive Statistics Page
The T10000C Vendor Unique Drive Statistics page (3Ch) reports a variety of vendor
unique drive statistics.
1100hServo General Purpose Counter Head 0 (SGPCT0)16all FF's
1101hServo General Purpose Counter Head 1 (SGPCT1)16all FF's
1200hServo Vote Out Head 0 (SVO0)32all FF's
1201hServo Vote Out Head 1 (SVO1)32all FF's
1202hServo Off-Track Type Head 0 (SOTT0)32all FF's
1203hServo Off-Track Type Head 1 (SOTT1)32all FF's
1310hPES Histogram Head 0 A (PESH0)128all FF's
1311hPES Histogram Head 0 B (PESH0)128all FF's
1320hPES Histogram Head 1 A (PESH 1)128all FF's
1321hPES Histogram Head 1 B (PESH 1)128all FF's
1400hOld VR2 Blocks (VOLD)128all FF's
1402hChannel FR2 Corrections (CFC)128all FF's
1404hBlock CRC Error (CBC)128all FF's
1405hPRML Block Errors Reverse BLKERRr128all FF's
1406hPRML Block Errors Forward BLKERRf128all FF's
1500hChannel Viterbi Averages Rev128all FF's
1501hChannel Viterbi Averages Fwd128all FF's
1502hChannel Viterbi Divisor Rev128all FF's
1503hChannel Viterbi Divisor Fwd128all FF's
1504hMatrix Channel Dead Reverse128all FF's
1505hMatrix Channel Dead Forward4all FF's
2405hExp Block Count Rev Chan 0-154all FF's
2406hExp Block Count Rev Chan 16-314all FF's
2407hExp Block Count Fwd Chan 0-154all FF's
2408hExp Block Count Fwd Chan 16-314all FF's
2500hMIR Matrix Count on Write4all FF's
2501hMIR Matrix Count on Read (see notes)4all FF's
2502h-251FhEngineering Use Only4 each (120 total)all FF's
Notes:
• The device write byte count will include file marks and pad bytes. These
additional bytes will not be included in the device read byte count.
86 T10000: Interface Reference ManualAugust 2016
Page 87
Log Sense Command
• Parameters 0400-0402, 0407-0408, and 2501 will not be reset by a Log Select
command.
August 2016 Commands 87
Page 88
Log Sense Command
Volume Statistics Log Page
The Volume Statistics page (17h) reports parameters associated with utilization of the
tape cartridge and medium. Only parameter 0203h used native capacity of partitions
is supported.
TABLE 3-44 Volume Statistics Log Page
Bit
Byte
0DSSPF
76543210
Page Code (17h)
1Subpage Code
2
thru
(MSB)
Page Length (n-3)
3
Volume Statistics log parameter(s)
4Volume Statistics log parameter (first)
nVolume Statistics log parameter (last)
Parameter Value
DS: Disable Save1 = Log parameters are not saved.
SPF: Subpage Format0 = Only subpage 00h supported
Subpage code00h = Subpage 0
Page lengthLength of parameter data to follow
(LSB)
Volume statistics log parameters
First log parameter in numerical order by parameter code
(first)
Volume statistics log parameters
Last log parameter in numerical order by parameter code
(last)
88 T10000: Interface Reference ManualAugust 2016
Page 89
Log Sense Command
Volume Statistics Log Parameter 0203h reports the used native capacity in MB (10
bytes) for each partition on the tape. The parameter uses the Volume Statistics Partition
Record Descriptor format shown in TABLE 3-45.
TABLE 3-45 Volume Statistics Partition Record Log Parameter Format
Bit
Byte
0
thru
76543210
(MSB)
Parameter code
1
2DUDS
TSD(0b)ETC
TMC
3Parameter length (n-3)
Volume statistics partition record descriptor(s)
4Volume statistics partition record descriptor (first)
.
.
.
nVolume statistics partition record descriptor (last)
6
(LSB)
Format and
linking(11b)
Parameter Value
Parameter codeDefines volume statistics data parameter
0203h = Used native capacity of partitions in MB (106bytes)
DU: Disable update0 = Drive updates log parameter value
DS: Disable save1 = saving the log is not supported
TSD: Target save0 = Target provides a defined method of saving log
parameters
ETC: Enable threshold comparison0 = Comparison not performed
TMC: Threshold met criteria00b = Every update of cumulative value
Format and linking11b = binary format list
Parameter lengthNumber of bytes in the volume statistics partition record
descriptors
August 2016 Commands 89
Page 90
Log Sense Command
The value of the log parameter for each partition is reported in the format shown in
TABLE 3-46.
TABLE 3-46 Volume Statistics Partition Record Descriptor Format
Bit
Byte
76543210
0Partition record descriptor length (n)
1Reserved
2
thru
3
4
thru
n
Parameter Value
(MSB)
(MSB)
Partition number
Partition record data counter
(LSB)
(LSB)
Partition record descriptor length7 = Number of byte that follow
Partition NumberNumber of partition that the following counter is associated.
Partition record data counterValue of data counter associated with parameter code and
partition
90 T10000: Interface Reference ManualAugust 2016
Page 91
Mode Select Command
The Mode Select command specifies options and parameters for a device. StorageTek
recommends the host system perform a Mode Sense command before each Mode
Select command to determine the current settings and to avoid any unwanted
alterations to other Mode Select fields.
The Mode Sense command determines which fields can be changed by the Mode
Select command and what the default values are for these fields.
The tape drives support both 6- and 10-byte commands.
TABLE 3-47 Mode Select (10)—6 Byte Command
Mode Select Command
Bit
Byte
76543210
0Operation Code (15h)
1ReservedPFReservedSP
2
thru
(MSB)
Reserved
3
4Parameter List Length
5Control Byte
TABLE 3-48 Mode Select (10)—10 Byte Command
Bit
Byte
76543210
0Operation Code (55h)
1ReservedPFReservedSP
2
thru
(MSB)
Reserved
6
7
thru
(MSB)
Parameter List Length
8
(LSB)
(LSB)
(LSB)
9Control Byte
Mode Select data consists of a header, an optional block descriptor, and optional page
formatted data:
August 2016 Commands 91
Page 92
Mode Select Command
Parameter Value
PF: Page Format0 = Vendor specific format (same as PF = 1)
1 = Page formatted data follows block descriptor, or header
SP: Save Parameters0 = Not supported
Parameter List LengthContains the total number of bytes in the header, block
descriptor, and all pages.
If this length is 0, no mode select data is sent and the
command is ignored.
If this length results in the truncation of the header, block
descriptor, or any page, the command is rejected.
Mode select data can be sent as:
• Header only
• Header and page formatted data
• Header and block descriptor
• Header, block descriptor, and page formatted data
Pages can be sent in any order. If any page formatted data is
sent, the PF bit is set in the command.
Mode Select Header Data
TABLE 3-49 Mode Select (6) Header Data
Bit
Byte
0
thru
1
2N/ABuffered ModeSpeed Code
3Block Descriptor Length
76543210
(MSB)
Reserved
(LSB)
92 T10000: Interface Reference ManualAugust 2016
Page 93
TABLE 3-50 Mode Select (10) Header Data
Mode Select Command
Bit
Byte
0
thru
76543210
(MSB)
Reserved
2
30Buffered ModeSpeed Code
4
thru
(MSB)
Reserved
5
6
thru
(MSB)
Block Descriptor Length
7
Page data may follow header if 00 is returned for block descriptor length.
Parameter Value
N/ANot applicable or not defined
Buffered Mode000b = Return status after data is on tape
001b = Return status when data is in the buffer
Speed Code0h = Use default speed
(LSB)
(LSB)
(LSB)
1h = Lowest speed
2h = Next lowest speed
3h = Medium speed
4h = Next highest speed
5h = Highest speed
Block Descriptor Length00 = No Block Descriptor
08 = Block Descriptor follows
Page data follows header if 00 is returned for block descriptor
length.
August 2016 Commands 93
Page 94
Mode Select Command
Mode Select Block Descriptor Data
TABLE 3-51 Mode Select Block Descriptor Data
Bit
Byte
76543210
0Density Code
1
thru
(MSB)
Block Count
3
4Reserved
5
thru
(MSB)
Block Length
7
Parameter Value
Density Code00h = Default density
4Ah = T10000A default density
4Bh = T10000B default density
4Ch = T10000C default density
4Dh = T10000D default density
7Fh = Do not change density
(LSB)
(LSB)
Block CountMust be 0
Block LengthVariable block mode length is 0
Fixed block mode length 1 to 2,097,152 bytes
Note – 2,097,156 bytes is now the upper limit in fixed block
mode when the DIV mode is enabled.
See “Control Data Protection Mode Page” on page 97
94 T10000: Interface Reference ManualAugust 2016
Page 95
Read/Write Error Recovery Page
TABLE 3-52 Mode Select Read/Write Error Page
Mode Select Command
Bit
Byte
76543210
0PSSFP (0)Page Code (01h)
1Page Length (0Ah)
2ReservedTBRSVDERRPERDTEDCR
3Read Retry Count
4
thru
(MSB)
Reserved
7
8Write Retry Count
9
thru
(MSB)
Reserved
11
Parameter Value
PS: Parameters Savable0 = Not supported
SPF: SubPage Format0 = Mode page format
TB: Transfer Block0 = Unrecoverable data block not transferred
ERR: Enable Early Recovery0 = Normal error recovery
(LSB)
(LSB)
PER: Post Error0 = Normal mode
DTE: Disable Transfer on Error0 = Normal mode
DCR: Disable Correction0 = Always use error correction codes
Read Retry CountExtent of error recovery during read operations
Count ignored, always maximum recovery
WriteRetry CountExtent of error recovery during the write operations
0h5 minutes (same as default)
1h – 13h10 seconds
14h – 3Bh1 minute
3Ch – 63h3 minutes
64h – 77h5 minutes
78h – C7h6 minutes
C8h – FFh10 minutes
64hDefault value (5 minutes)
August 2016 Commands 95
Page 96
Mode Select Command
Disconnect–Reconnect Page
TABLE 3-53 Mode Select Disconnect–Reconnect Page
Bit
Byte
76543210
0PSSPF (0)Page Code (02h)
1Page Length (0Eh)
2Buffer full ratio
3Buffer empty ratio
4
thru
(MSB)
Bus inactivity limit
5
6
thru
(MSB)
Disconnect time limit
7
8
thru
(MSB)
Connect time limit
9
10
thru
(MSB)
Maximum burst size
11
12EMDPFARdFAWrtFAStatDImmDTDC
13Reserved
(LSB)
(LSB)
(LSB)
(LSB)
14
thru
(MSB)
First burst size
15
ParameterValue
PS: Parameters Savable0 = Not supported
SPF: SubPage Format0 = Mode page format
Buffer Full Ratio0 = Not supported
Buffer Empty Ratio0 = Not supported
Bus Inactivity Limit0 = Not supported
Disconnect Time Limit0 = Not supported
Connect Time Limit0 = Not supported
Maximum Burst Size0 = No limit
EMDP: Enable Modify Data Pointers0 = Modify data pointers is disabled
DTDC: Data transfer disconnect control0 = Target chooses
First Burst Size0 = No limit
Control Data Protection Mode Page
This Mode Select page returns information about the current Data Integrity
Validation (DIV) mode.
The Mode Select Block Descriptor Data, Block Length field now has 2,097,156 for the
upper limit in fixed block mode when the DIV mode is enabled.
TABLE 3-54 Mode Select Control Data Protection Mode Page
Bit
Mode Select Command
Byte
76543210
0PSSPF (1)Page Code (0Ah)
1Subpage Code (F0h)
2
thru
(MSB)
Page Length (n-3)
3
4Logical Block Protection Information Method
5ReservedLogical Block Protection Information Length
6LBP_WLBP_RRBDPReserved
7T10 PI ExponentReserved
nReserved
ParameterValue
PS: Parameters Savable0 = Not supported
SPF: SubPage Format1 = SubPage mode format
Subpage codeF0h = Control Data Protection mode page
Logical Block ProtectionSee TABLE 3-55.
(LSB)
• Information Method
• Information Length
August 2016 Commands 97
Page 98
Mode Select Command
ParameterValue
LBP_W
Logical Blocks Protected during
LBP_R:
Logical Blocks Protected Read
RBDP:
Recover Buffered Data Protected
0 = Protection Information is not included with the data
transferred when writing.
1 = Protection Information is included with the data transferred
when writing.
Notes:
• If the Logical Block Protection Method field is set to zero,
the LBP_W bit is set to zero.
• If Logical Block Protection Method field is set to a non-zero,
then one or more of LBP_W or LBP_R bits must be set to a
non-zero.
0 = Protection Information is not included with the data
transferred when reading.
1 = Protection Information is included with the data transferred
when reading.
Notes:
If the Logical Block Protection Method field is set to zero, the
LBP_R bit is set to zero.
If the Logical Block Protection Method field is set to a non-zero
then one or more of LBP_W or LBP_R bits must be set to a nonzero.
0 = Protection Information is not included with the data
transferred by the Recover Buffered Data command.
1 = Protection Information is included with the data transferred
by the Recover Buffered Data command. (This bit is Ignored).
Notes:
• If the Logical Block Protection Method field is set to zero,
the RBDP bit is set to zero.
• If Logical Block Protection Method field is set to a non-zero
then this bit is ignored.
98 T10000: Interface Reference ManualAugust 2016
Page 99
ParameterValue
Mode Select Command
LBP_W
Logical Blocks Protected during
LBP_R:
Logical Blocks Protected Read
RBDP:
Recover Buffered Data Protected
0 = Protection Information is not included with the data
transferred when writing.
1 = Protection Information is included with the data transferred
when writing.
Notes:
• If the Logical Block Protection Method field is set to zero,
the LBP_W bit is set to zero.
• If Logical Block Protection Method field is set to a non-zero,
then one or more of LBP_W or LBP_R bits must be set to a
non-zero.
0 = Protection Information is not included with the data
transferred when reading.
1 = Protection Information is included with the data transferred
when reading.
Notes:
If the Logical Block Protection Method field is set to zero, the
LBP_R bit is set to zero.
If the Logical Block Protection Method field is set to a non-zero
then one or more of LBP_W or LBP_R bits must be set to a nonzero.
0 = Protection Information is not included with the data
transferred by the Recover Buffered Data command.
1 = Protection Information is included with the data transferred
by the Recover Buffered Data command. (This bit is Ignored).
Notes:
• If the Logical Block Protection Method field is set to zero,
the RBDP bit is set to zero.
• If Logical Block Protection Method field is set to a non-zero
then this bit is ignored.
August 2016 Commands 99
Page 100
Mode Select Command
ParameterValue
T10 PI Exponent:
(T10000D)
This field determines the size of each user data field (in bytes)
when T10 PI protected mode is selected.
0h = 1 bytes
1h=2
2h=4
3h=8
4h=16
5h=32
6h=64
7h = 128
8h = 256
9h = 512
Ah = 1,024
Bh = 2,048
Ch = 4,096
Dh = 8,192
Eh = 16,384
Fh = 32,768
T10000D only supports exponent values 9h through Fh.
TABLE 3-55 Protection Information Method
Method (Byte 4)
Description
Length (Byte 5)Drives Supported
00hDo not use logical block protection.00hT10000 All
01hReed-Solomon CRC, See ECMA-3191,
CRC appended on any byte boundary
04hT10000C and
T10000D
02h - EFhReserved––
F0hVendor Unique SB-2,
CRC appended on modulo 4 byte
04hT10000A
T10000B
boundary
F1hVendor Unique Intel CRC32C,
CRC appended on any byte boundary
F2hVendor Unique T10 PI
04hT10000C and
T10000D
08hT10000D
PI appended on each user data field
F3h - FFhReserved––
1. European Computer Manufacturers Association “Data Interchange on 12.7 mm 384-Track magnetic Tape
Cartridges,” ECMA-319 Standard, 2001.
100 T10000: Interface Reference ManualAugust 2016
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.