Working Project

Draft T10/BSR INCITS 513

Revision 37
17 May 2014

Information technology -
SCSI Primary Commands - 4 (SPC-4)

This is an internal working document of T10, a Technical Committee of Accredited Standards Committee
INCITS (InterNational Committee for Information Technology Standards). As such this is not a completed
standard and has not been approved. The contents may be modified by the T10 Technical Committee. The
contents are actively being modified by T10. This document is made available for review and comment only.

Permission is granted to members of INCITS, its technical committees, and their associated task groups to
reproduce this document for the purposes of INCITS standardization activities without further permission,
provided this notice is included. All other rights are reserved. Any duplication of this document for commercial
or for-profit use is strictly prohibited.

T10 Technical Editor: Ralph O. Weber

Western Digital Corp.
18484 Preston Road
Suite 102 PMB 178
Dallas, TX 75252
USA

Telephone: 214-912-1373
Email: Ralph dot Weber at WDC dot com

Reference number
ISO/IEC 14776-454 : 20xx
ANSI INCITS 513-20xx

Printed 9:34 PM Saturday 17 May 2014

Points of Contact:

T10 Chair T10 Vice-Chair

John B. Lohmeyer William Martin
LSI Corp. Samsung Semiconductor Inc. (SSI)
4420 Arrows West Drive 7213 Marblethorpe Drive
Colorado Springs, CO 80907-3444 Roseville, CA 95747-5925
Tel: 719-533-7560 Tel: 916-765-6875
Email: lohmeyer at t10 dot org Email: bill dot martin at ssi dot samsung dot com

INCITS Secretariat
INCITS Secretariat Telephone: 202-737-8888
1101 K Street NW, Suite 610 Facsimile: 202-638-4922
Washington, DC 20005-7031 Email: [email protected]

T10 Web Site http://www.t10.org

T10 Reflector To subscribe send e-mail to [email protected] with ‘subscribe’ in message body
To unsubscribe send e-mail to [email protected] with ‘unsubscribe’ in message body
Internet address for distribution via T10 reflector: [email protected]

Purchase INCITS Standards

http://www.incits.org/standards-information/purchase-standards
 ANSI (r)
INCITS 513-20xx

American National Standards

for Information Systems -

SCSI Primary Commands - 4 (SPC-4)

Secretariat
InterNational Committee for Information Technology Standards

Approved mm dd yy

American National Standards Institute, Inc.

Abstract

This standard defines the device model for all SCSI devices. This standard defines the SCSI commands that
are basic to every device model and the SCSI commands that may apply to any device model.
American Approval of an American National Standard requires verification by ANSI that the
requirements for due process, consensus, and other criteria for approval have been
National met by the standards developer. Consensus is established when, in the judgment of
Standard the ANSI Board of Standards Review, substantial agreement has been reached by
directly and materially affected interests. Substantial agreement means much more
than a simple majority, but not necessarily unanimity. Consensus requires that all
views and objections be considered and that effort be made toward their resolution.

The use of American National Standards is completely voluntary; their existence

does not in any respect preclude anyone, whether he or she has approved the
standards or not, from manufacturing, marketing, purchasing, or using products,
processes, or procedures not confirming to the standards.

The American National Standards Institute does not develop standards and will in no
circumstances give interpretation on any American National Standard in the name of
the American National Standards Institute. Requests for interpretations should be
addressed to the secretariat or sponsor whose name appears on the title page of this
standard.

CAUTION NOTICE: This American National Standard may be revised or withdrawn

at any time. The procedures of the American National Standards Institute require that
action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers
of American National Standards may receive current information on all standards by
calling or writing the American National Standards Institute.

CAUTION: The developers of this standard have requested that holders of patents that may be required
for the implementation of the standard, disclose such patents to the publisher. However, neither the
developers nor the publisher have undertaken a patent search in order to identify which, if any, patents
may apply to this standard.

As of the date of publication of this standard, following calls for the identification of patents that may be
required for the implementation of the standard, notice of one or more claims has been received.

By publication of this standard, no position is taken with respect to the validity of this claim or of any rights
in connection therewith. The known patent holder(s) has (have), however, filed a statement of willingness
to grant a license under these rights on reasonable and nondiscriminatory terms and conditions to appli-
cants desiring to obtain such a license. Details may be obtained from the publisher.

No further patent search is conducted by the developer or the publisher in respect to any standard it
processes. No representation is made or implied that licenses are not required to avoid infringement in
the use of this standard.

Published by
American National Standards Institute
25 West 43rd Street 4th floor
New York, New York 10036-7422

No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise,
without prior written permission of ITI, 1101 K Street NW, Suite 610, Washington, DC 20005-7031.

All rights reserved.

Printed in the United States of America

17 May 2014 T10/BSR INCITS 513 Revision 37

Contents
Page

Foreword ...........................................................................................................................................................xl

Introduction ..................................................................................................................................................... xlv

SCSI standards family.................................................................................................................................... xlvi

1 Scope ............................................................................................................................................................. 1

2 Normative references..................................................................................................................................... 1
2.1 General ................................................................................................................................................. 1
2.2 Approved references ............................................................................................................................ 2
2.3 References under development............................................................................................................ 4
2.4 CFA references..................................................................................................................................... 5
2.5 IETF references .................................................................................................................................... 5
2.6 NIST references.................................................................................................................................... 6
2.7 USB Implementers Forum references .................................................................................................. 6

3 Definitions, symbols, abbreviations, and conventions.................................................................................... 7

3.1 Definitions ............................................................................................................................................. 7
3.2 Abbreviations and symbols................................................................................................................. 25
3.2.1 Abbreviations ................................................................................................................................... 25
3.2.2 Symbols ........................................................................................................................................... 27
3.2.3 Mathematical operators ................................................................................................................... 28
3.3 Keywords ............................................................................................................................................ 28
3.4 Conventions........................................................................................................................................ 29
3.5 Numeric and character conventions ................................................................................................... 30
3.5.1 Numeric conventions ....................................................................................................................... 30
3.5.2 Units of measure.............................................................................................................................. 31
3.5.3 Byte encoded character strings conventions ................................................................................... 32
3.6 Bit and byte ordering........................................................................................................................... 32
3.7 Notation conventions .......................................................................................................................... 34
3.7.1 Notation for procedure calls............................................................................................................. 34
3.7.2 Notation for state diagrams.............................................................................................................. 35
3.7.3 Notation for flowcharts ..................................................................................................................... 36
3.7.4 Notation for UML figures.................................................................................................................. 37
3.7.4.1 Introduction ................................................................................................................................... 37
3.7.4.2 Class notation ............................................................................................................................... 38
3.7.4.3 Class association relationships notation....................................................................................... 38
3.7.4.4 Class aggregation relationships notation...................................................................................... 39
3.7.4.5 Class generalization relationships notation .................................................................................. 41
3.7.4.6 Class dependency relationships notation ..................................................................................... 42
3.7.4.7 Object notation.............................................................................................................................. 42
3.7.5 Notation for EXTENDED COPY command segment descriptors .................................................... 43

4 General concepts ......................................................................................................................................... 44

4.1 Introduction ......................................................................................................................................... 44
4.2 Command Descriptor Block ................................................................................................................ 44
4.2.1 CDB usage and structure ................................................................................................................ 44
4.2.2 Fixed length CDB formats................................................................................................................ 45
4.2.2.1 Formats for 6-byte CDBs .............................................................................................................. 45
4.2.2.1.1 Generic 6-byte CDB format ....................................................................................................... 45

Working Draft SCSI Primary Commands - 4 (SPC-4) v

T10/BSR INCITS 513 Revision 37 17 May 2014

4.2.2.1.2 Typical 6-byte CDB format......................................................................................................... 45

4.2.2.2 Formats for 10-byte CDBs ............................................................................................................ 46
4.2.2.2.1 Generic 10-byte CDB format ..................................................................................................... 46
4.2.2.2.2 Typical 10-byte CDB format....................................................................................................... 47
4.2.2.3 Formats for 12-byte CDBs ............................................................................................................ 48
4.2.2.3.1 Generic 12-byte CDB format ..................................................................................................... 48
4.2.2.3.2 Typical 12-byte CDB format....................................................................................................... 49
4.2.2.3.3 MAINTENANCE IN CDB format ................................................................................................ 50
4.2.2.3.4 MAINTENANCE OUT CDB format ............................................................................................ 50
4.2.2.3.5 SERVICE ACTION IN(12) CDB format...................................................................................... 51
4.2.2.3.6 SERVICE ACTION OUT(12) CDB format.................................................................................. 51
4.2.2.4 Formats for 16-byte CDBs ............................................................................................................ 52
4.2.2.4.1 Generic 16-byte CDB format ..................................................................................................... 52
4.2.2.4.2 Typical 16-byte CDB format, if eight-byte LBAs not supported ................................................. 53
4.2.2.4.3 Typical 16-byte CDB format with eight-byte LBAs supported.................................................... 54
4.2.2.4.4 SERVICE ACTION IN(16) CDB format...................................................................................... 55
4.2.2.4.5 SERVICE ACTION OUT(16) CDB format.................................................................................. 55
4.2.2.4.6 SERVICE ACTION BIDIRECTIONAL CDB format .................................................................... 56
4.2.3 Variable length CDB formats ........................................................................................................... 57
4.2.3.1 Generic variable length CDB format ............................................................................................. 57
4.2.3.2 Typical 32-byte variable length CDB format ................................................................................. 58
4.2.4 Extended CDBs ............................................................................................................................... 59
4.2.4.1 XCDB model ................................................................................................................................. 59
4.2.4.2 The XCDB format ......................................................................................................................... 59
4.2.5 Common CDB fields ........................................................................................................................ 61
4.2.5.1 Operation code ............................................................................................................................. 61
4.2.5.2 Service action ............................................................................................................................... 61
4.2.5.3 Logical block address ................................................................................................................... 61
4.2.5.4 Transfer length.............................................................................................................................. 62
4.2.5.5 Parameter list length..................................................................................................................... 62
4.2.5.6 Allocation length ........................................................................................................................... 62
4.3 Data field requirements....................................................................................................................... 62
4.3.1 ASCII data field requirements.......................................................................................................... 62
4.3.2 Null data field termination and zero padding requirements ............................................................. 63
4.3.3 Variable type data field requirements .............................................................................................. 63
4.3.4 Port identifier field requirements ...................................................................................................... 64
4.4 Secure random numbers .................................................................................................................... 64
4.5 Sense data.......................................................................................................................................... 64
4.5.1 Sense data introduction ................................................................................................................... 64
4.5.2 Descriptor format sense data........................................................................................................... 66
4.5.2.1 Descriptor format sense data overview ........................................................................................ 66
4.5.2.2 Information sense data descriptor ................................................................................................ 69
4.5.2.3 Command-specific information sense data descriptor.................................................................. 70
4.5.2.4 Sense key specific sense data descriptor..................................................................................... 70
4.5.2.4.1 Sense key specific sense data descriptor overview .................................................................. 70
4.5.2.4.2 Field pointer sense key specific information .............................................................................. 71
4.5.2.4.3 Actual retry count sense key specific information...................................................................... 72
4.5.2.4.4 Progress indication sense key specific information ................................................................... 72
4.5.2.4.5 Segment pointer sense key specific information ....................................................................... 73
4.5.2.4.6 Unit attention condition queue overflow sense key specific information.................................... 73
4.5.2.5 Field replaceable unit sense data descriptor ................................................................................ 74
4.5.2.6 Another progress indication sense data descriptor....................................................................... 74
4.5.2.7 Forwarded sense data .................................................................................................................. 75
4.5.2.8 Vendor specific sense data descriptors ........................................................................................ 76

vi Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

4.5.3 Fixed format sense data .................................................................................................................. 77

4.5.4 Returning a value in the INFORMATION field in the sense data.......................................................... 78
4.5.5 Returning a value in the COMMAND-SPECIFIC INFORMATION field in the sense data ........................... 79
4.5.6 Current information .......................................................................................................................... 80
4.5.7 Deferred errors ................................................................................................................................ 80
4.5.8 Sense key and additional sense code definitions ............................................................................ 81

5 Model common to all device types ............................................................................................................. 102

5.1 Introduction to the model common to all device types...................................................................... 102
5.1.1 Overview........................................................................................................................................ 102
5.1.2 Important commands for all SCSI device servers.......................................................................... 102
5.1.2.1 Commands implemented by all SCSI device servers................................................................. 102
5.1.2.2 Commands recommended for all SCSI device servers .............................................................. 102
5.1.2.3 Using the INQUIRY command.................................................................................................... 102
5.1.2.4 Using the REPORT LUNS command ......................................................................................... 103
5.1.2.5 Using the TEST UNIT READY command................................................................................... 103
5.1.2.6 Using the REQUEST SENSE command .................................................................................... 103
5.1.3 Implicit head of queue.................................................................................................................... 103
5.2 Device clocks and timestamps ......................................................................................................... 103
5.3 Device specific background functions............................................................................................... 104
5.3.1 Introduction .................................................................................................................................... 104
5.3.2 Suspending and resuming device specific background functions ................................................. 105
5.4 Downloading and activating microcode ............................................................................................ 106
5.4.1 Downloading microcode ................................................................................................................ 106
5.4.2 Activating microcode...................................................................................................................... 110
5.5 Error history ...................................................................................................................................... 111
5.5.1 Error history overview .................................................................................................................... 111
5.5.2 Retrieving error history with the READ BUFFER command.......................................................... 112
5.5.3 Adding application client error history with the WRITE BUFFER command.................................. 114
5.5.4 Clearing error history with the WRITE BUFFER command ........................................................... 114
5.6 Identifying information....................................................................................................................... 115
5.7 Medium auxiliary memory................................................................................................................. 115
5.8 Parameter rounding .......................................................................................................................... 116
5.9 Parsing variable length parameter lists and parameter data ............................................................ 117
5.10 Pollable condition information......................................................................................................... 118
5.10.1 Information that does not represent an exception condition ........................................................ 118
5.10.2 REQUEST SENSE pollable sense data ...................................................................................... 118
5.10.2.1 Making information available for the REQUESE SENSE command ........................................ 118
5.10.2.2 Selecting pollable sense data to return..................................................................................... 118
5.10.2.3 Returning one or more progress indications............................................................................. 118
5.10.3 Log parameter pollable device condition information .................................................................. 119
5.11 Power management........................................................................................................................ 119
5.11.1 Power management overview ..................................................................................................... 119
5.11.2 Power consumption management ............................................................................................... 119
5.11.3 Power conditions management ................................................................................................... 120
5.11.4 Active power condition................................................................................................................. 121
5.11.5 Idle power conditions ................................................................................................................... 122
5.11.6 Standby power conditions............................................................................................................ 122
5.11.7 Power condition pollable sense data ........................................................................................... 123
5.11.8 Power condition state machine.................................................................................................... 123
5.11.8.1 Power condition state machine overview.................................................................................. 123
5.11.8.2 PC0:Powered_On state ............................................................................................................ 125
5.11.8.2.1 PC0:Powered_On state description....................................................................................... 125
5.11.8.2.2 Transition PC0:Powered_On to PC4:Active_Wait ................................................................. 125

Working Draft SCSI Primary Commands - 4 (SPC-4) vii

T10/BSR INCITS 513 Revision 37 17 May 2014

5.11.8.3 PC1:Active state ....................................................................................................................... 125

5.11.8.3.1 PC1:Active state description.................................................................................................. 125
5.11.8.3.2 Transition PC1:Active to PC5:Wait_Idle ................................................................................ 126
5.11.8.3.3 Transition PC1:Active to PC6:Wait_Standby......................................................................... 126
5.11.8.4 PC2:Idle state ........................................................................................................................... 126
5.11.8.4.1 PC2:Idle state description...................................................................................................... 126
5.11.8.4.2 Transition PC2:Idle to PC4:Active_Wait ................................................................................ 126
5.11.8.4.3 Transition PC2:Idle to PC5:Wait_Idle .................................................................................... 127
5.11.8.4.4 Transition PC2:Idle to PC6:Wait_Standby............................................................................. 127
5.11.8.5 PC3:Standby state.................................................................................................................... 127
5.11.8.5.1 PC3:Standby state description .............................................................................................. 127
5.11.8.5.2 Transition PC3:Standby to PC4:Active_Wait......................................................................... 127
5.11.8.5.3 Transition PC3:Standby to PC6:Wait_Standby ..................................................................... 128
5.11.8.6 PC4:Active_Wait state .............................................................................................................. 128
5.11.8.6.1 PC4:Active_Wait state description......................................................................................... 128
5.11.8.6.2 Transition PC4:Active_Wait to PC1:Active ............................................................................ 129
5.11.8.7 PC5:Wait_Idle state .................................................................................................................. 129
5.11.8.7.1 PC5:Wait_Idle state description............................................................................................. 129
5.11.8.7.2 Transition PC5:Wait_Idle to PC2:Idle .................................................................................... 129
5.11.8.8 PC6:Wait_Standby state........................................................................................................... 129
5.11.8.8.1 PC6:Wait_Standby state description ..................................................................................... 129
5.11.8.8.2 Transition PC6:Wait_Standby to PC3:Standby ..................................................................... 130
5.12 Reservations................................................................................................................................... 130
5.12.1 Persistent Reservations overview................................................................................................ 130
5.12.2 Third party persistent reservations .............................................................................................. 135
5.12.3 Exceptions to SPC-2 RESERVE and RELEASE behavior .......................................................... 135
5.12.4 Persistent reservations interactions with IKEv2-SCSI SA creation.............................................. 136
5.12.5 Preserving persistent reservations and registrations................................................................... 136
5.12.5.1 Requirements for preserving persistent reservations and registrations.................................... 136
5.12.5.2 Preserving persistent reservations and registrations through power loss ................................ 136
5.12.5.3 Nonvolatile memory considerations for preserving persistent reservations and registrations .. 137
5.12.5.4 Loss of persistent reservation information ................................................................................ 137
5.12.5.4.1 Loss of persistent reservation information overview.............................................................. 137
5.12.5.4.2 Recoverable loss of persistent reservation information ......................................................... 137
5.12.5.4.3 Unrecoverable loss of persistent reservation information overview....................................... 138
5.12.6 Finding persistent reservations and reservation keys.................................................................. 138
5.12.6.1 Summary of commands for finding persistent reservations and reservation keys.................... 138
5.12.6.2 Reporting reservation keys ....................................................................................................... 138
5.12.6.3 Reporting the persistent reservation......................................................................................... 139
5.12.6.4 Reporting full status .................................................................................................................. 139
5.12.7 Registering................................................................................................................................... 139
5.12.8 Registering and moving the reservation ...................................................................................... 143
5.12.9 Reserving..................................................................................................................................... 144
5.12.10 Persistent reservation holder ..................................................................................................... 145
5.12.11 Releasing persistent reservations and removing registrations .................................................. 146
5.12.11.1 Releasing persistent reservations, removing registrations, and lost reservation information . 146
5.12.11.2 Service actions that release persistent reservations and remove registrations...................... 146
5.12.11.2.1 Service actions that release persistent reservations and remove registrations overview.... 146
5.12.11.2.2 Releasing............................................................................................................................. 147
5.12.11.2.3 Unregistering ....................................................................................................................... 148
5.12.11.2.4 Preempting .......................................................................................................................... 149
5.12.11.2.4.1 Commands that preempt reservations.............................................................................. 149
5.12.11.2.4.2 Failed persistent reservation preempt .............................................................................. 151
5.12.11.2.4.3 Preempting persistent reservations and registration handling.......................................... 151

viii Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.12.11.2.5 Removing registrations ........................................................................................................ 152

5.12.11.2.6 Preempting and aborting ..................................................................................................... 153
5.12.11.2.7 Clearing ............................................................................................................................... 154
5.12.11.3 Replacing lost reservations..................................................................................................... 154
5.13 Security features............................................................................................................................. 155
5.13.1 Security goals and threat model .................................................................................................. 155
5.13.1.1 Introduction ............................................................................................................................... 155
5.13.1.2 Security goals ........................................................................................................................... 155
5.13.1.3 Threat model............................................................................................................................. 156
5.13.1.4 Types of attacks........................................................................................................................ 157
5.13.1.5 SCSI security considerations.................................................................................................... 157
5.13.2 Security associations ................................................................................................................... 158
5.13.2.1 Principles of SAs....................................................................................................................... 158
5.13.2.2 SA parameters.......................................................................................................................... 159
5.13.2.3 Creating an SA ......................................................................................................................... 162
5.13.3 Key derivation functions............................................................................................................... 162
5.13.3.1 KDFs overview.......................................................................................................................... 162
5.13.3.2 IKEv2-based iterative KDF ....................................................................................................... 163
5.13.3.3 HMAC-based KDFs .................................................................................................................. 163
5.13.3.4 AES-XCBC-PRF-128 IKEv2-based iterative KDF .................................................................... 165
5.13.4 Using IKEv2-SCSI to create an SA.............................................................................................. 166
5.13.4.1 Overview................................................................................................................................... 166
5.13.4.2 IKEv2-SCSI Protocol summary................................................................................................. 169
5.13.4.3 IKEv2-SCSI Authentication....................................................................................................... 172
5.13.4.3.1 Overview................................................................................................................................ 172
5.13.4.3.2 Pre-shared key authentication ............................................................................................... 173
5.13.4.3.3 Digital signature authentication.............................................................................................. 174
5.13.4.3.3.1 Overview............................................................................................................................. 174
5.13.4.3.3.2 Certificates and digital signature authentication ................................................................. 174
5.13.4.3.3.3 Example of certificate use for digital signature authentication............................................ 175
5.13.4.3.3.4 Handling of the Certificate Request payload and the Certificate payload........................... 175
5.13.4.3.4 Constraints on skipping the Authentication step.................................................................... 175
5.13.4.4 Summary of IKEv2-SCSI shared keys nomenclature and shared key sizes ............................ 177
5.13.4.5 Device Server Capabilities step................................................................................................ 178
5.13.4.6 IKEv2-SCSI Key Exchange step............................................................................................... 180
5.13.4.6.1 Overview................................................................................................................................ 180
5.13.4.6.2 Key Exchange step SECURITY PROTOCOL OUT command .............................................. 180
5.13.4.6.3 Key Exchange step SECURITY PROTOCOL IN command .................................................. 181
5.13.4.6.4 Key Exchange step completion ............................................................................................. 182
5.13.4.6.5 After the Key Exchange step ................................................................................................. 182
5.13.4.7 IKEv2-SCSI Authentication step ............................................................................................... 182
5.13.4.7.1 Overview................................................................................................................................ 182
5.13.4.7.2 Authentication step SECURITY PROTOCOL OUT command .............................................. 183
5.13.4.7.3 Authentication step SECURITY PROTOCOL IN command .................................................. 184
5.13.4.8 Generating shared keys............................................................................................................ 185
5.13.4.8.1 Overview................................................................................................................................ 185
5.13.4.8.2 Generating shared keys when the Authentication step is skipped ........................................ 186
5.13.4.8.3 Generating shared keys when the Authentication step is processed .................................... 186
5.13.4.8.4 Initializing shared key generation .......................................................................................... 186
5.13.4.8.4.1 Initializing for SA creation shared key generation............................................................... 186
5.13.4.8.4.2 Initializing for generation of shared keys used by the created SA ...................................... 187
5.13.4.8.5 Generating shared keys used for SA management............................................................... 187
5.13.4.8.6 Generating shared keys for use by the created SA ............................................................... 188
5.13.4.9 IKEv2-SCSI SA generation....................................................................................................... 189

Working Draft SCSI Primary Commands - 4 (SPC-4) ix

T10/BSR INCITS 513 Revision 37 17 May 2014

5.13.4.10 Abandoning an IKEv2-SCSI CCS........................................................................................... 190

5.13.4.11 Deleting an IKEv2-SCSI SA.................................................................................................... 192
5.13.5 Security progress indication......................................................................................................... 192
5.13.6 Command security....................................................................................................................... 193
5.13.6.1 Overview................................................................................................................................... 193
5.13.6.2 Secure CDB Originator class.................................................................................................... 193
5.13.6.3 Secure CDB Processor class ................................................................................................... 193
5.13.6.4 Enforcement Manager class ..................................................................................................... 193
5.13.6.5 Security Manager class ............................................................................................................ 194
5.13.6.6 The relationship between SAs and command security............................................................. 195
5.13.6.7 Capability-based command security technique ........................................................................ 195
5.13.6.7.1 Overview................................................................................................................................ 195
5.13.6.7.2 Security Manager class ......................................................................................................... 198
5.13.6.7.3 CbCS Management Device Server class .............................................................................. 199
5.13.6.7.3.1 CbCS Management Device Server class overview ............................................................ 199
5.13.6.7.3.2 Decision Database attribute................................................................................................ 199
5.13.6.7.4 CbCS Management Application Client class ......................................................................... 199
5.13.6.7.5 Secure CDB Originator class................................................................................................. 199
5.13.6.7.6 Secure CDB Processor class ................................................................................................ 200
5.13.6.7.7 Enforcement Manager class .................................................................................................. 200
5.13.6.7.8 CbCS methods ...................................................................................................................... 201
5.13.6.7.8.1 Overview............................................................................................................................. 201
5.13.6.7.8.2 The BASIC CbCS method .................................................................................................. 201
5.13.6.7.8.3 The CAPKEY CbCS method .............................................................................................. 202
5.13.6.7.9 CbCS trust assumptions ........................................................................................................ 202
5.13.6.7.10 CbCS security tokens .......................................................................................................... 203
5.13.6.7.11 CbCS shared keys............................................................................................................... 204
5.13.6.7.11.1 Overview........................................................................................................................... 204
5.13.6.7.11.2 CbCS shared key identifiers ............................................................................................. 205
5.13.6.7.11.3 Specifying which CbCS shared key to change ................................................................. 206
5.13.6.7.11.4 Updating a CbCS master key ........................................................................................... 206
5.13.6.7.11.5 Changing a CbCS working keys ....................................................................................... 206
5.13.6.7.12 CbCS credentials................................................................................................................. 207
5.13.6.7.12.1 Overview........................................................................................................................... 207
5.13.6.7.12.2 CbCS capability key computations for the secure CDB originator.................................... 207
5.13.6.7.12.3 CbCS capability key computations for general use .......................................................... 207
5.13.6.7.13 CbCS capability descriptors................................................................................................. 208
5.13.6.7.13.1 Overview........................................................................................................................... 208
5.13.6.7.13.2 CbCS extension descriptor validation............................................................................... 209
5.13.6.7.13.3 CAPKEY CbCS method capability integrity validation...................................................... 209
5.13.6.7.14 Association between commands and permission bits ......................................................... 210
5.13.6.7.15 CbCS parameters ................................................................................................................ 213
5.13.6.7.15.1 Overview........................................................................................................................... 213
5.13.6.7.16 CbCS extension descriptor format....................................................................................... 215
5.13.7 ESP-SCSI encapsulations for parameter data ............................................................................ 216
5.13.7.1 Overview................................................................................................................................... 216
5.13.7.2 ESP-SCSI required inputs ........................................................................................................ 216
5.13.7.3 ESP-SCSI data format before encryption and after decryption ................................................ 217
5.13.7.4 ESP-SCSI outbound data descriptors ...................................................................................... 218
5.13.7.4.1 Overview................................................................................................................................ 218
5.13.7.4.2 ESP-SCSI CDBs or Data-Out Buffer parameter lists including a descriptor length............... 218
5.13.7.4.2.1 Initialization vector absent .................................................................................................. 218
5.13.7.4.2.2 Initialization vector present ................................................................................................. 220
5.13.7.4.3 ESP-SCSI Data-Out Buffer parameter lists for externally specified descriptor length........... 222

x Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.13.7.4.3.1 Initialization vector absent .................................................................................................. 222

5.13.7.4.3.2 Initialization vector present ................................................................................................. 223
5.13.7.5 ESP-SCSI Data-In Buffer parameter data descriptors.............................................................. 223
5.13.7.5.1 Overview................................................................................................................................ 223
5.13.7.5.2 ESP-SCSI Data-In Buffer parameter data including a descriptor length ............................... 225
5.13.7.5.2.1 Initialization vector absent .................................................................................................. 225
5.13.7.5.2.2 Initialization vector present ................................................................................................. 227
5.13.7.5.3 ESP-SCSI Data-In Buffer parameter data for externally specified descriptor length............. 228
5.13.7.5.3.1 Initialization vector absent .................................................................................................. 228
5.13.7.5.3.2 Initialization vector present ................................................................................................. 229
5.13.8 Security algorithm codes ............................................................................................................. 230
5.14 Self-test operations......................................................................................................................... 231
5.14.1 Self-test types .............................................................................................................................. 231
5.14.2 Default self-test............................................................................................................................ 232
5.14.3 The short self-test and extended self-test.................................................................................... 232
5.14.4 Self-test modes............................................................................................................................ 233
5.14.4.1 Self-test modes overview.......................................................................................................... 233
5.14.4.2 Foreground mode ..................................................................................................................... 233
5.14.4.3 Background mode..................................................................................................................... 233
5.14.4.4 Features common to foreground and background self-test modes .......................................... 235
5.15 Target port group asymmetric access states.................................................................................. 237
5.15.1 Target port group access overview.............................................................................................. 237
5.15.2 Asymmetric logical unit access.................................................................................................... 237
5.15.2.1 Introduction to asymmetric logical unit access ......................................................................... 237
5.15.2.2 Explicit and implicit asymmetric logical unit access.................................................................. 238
5.15.2.3 Discovery of asymmetric logical unit access behavior.............................................................. 239
5.15.2.4 Target port asymmetric access states ...................................................................................... 239
5.15.2.4.1 Target port asymmetric access states overview.................................................................... 239
5.15.2.4.2 Active/optimized state............................................................................................................ 239
5.15.2.4.3 Active/non-optimized state..................................................................................................... 239
5.15.2.4.4 Standby state......................................................................................................................... 240
5.15.2.4.5 Unavailable state ................................................................................................................... 240
5.15.2.4.6 Offline state............................................................................................................................ 241
5.15.2.4.7 Logical block dependent state ............................................................................................... 241
5.15.2.5 Transitions between target port asymmetric access states ...................................................... 241
5.15.2.6 Preference indicator.................................................................................................................. 243
5.15.2.7 Target port asymmetric access state reporting......................................................................... 243
5.15.2.8 Implicit asymmetric logical units access management ............................................................. 243
5.15.2.9 Explicit asymmetric logical units access management ............................................................. 244
5.15.2.10 Behavior after power on, hard reset, logical unit reset, and I_T nexus loss ........................... 244
5.15.2.11 Behavior of target ports that are not accessible from the service delivery subsystem ........... 244
5.15.3 Symmetric logical unit access...................................................................................................... 244
5.16 Third-party copies ........................................................................................................................... 245
5.16.1 General considerations for third-party copies .............................................................................. 245
5.16.2 Copy manager model .................................................................................................................. 245
5.16.3 Third-party copy commands ........................................................................................................ 248
5.16.4 Third-party copy command usage ............................................................................................... 249
5.16.4.1 Prior to sending a third-party copy command ........................................................................... 249
5.16.4.2 List identifiers for third-party copy commands .......................................................................... 250
5.16.4.3 Third-party copy commands and operations ............................................................................ 250
5.16.4.4 Monitoring progress of and retrieving results from third-party copy commands ....................... 251
5.16.4.5 Held data .................................................................................................................................. 252
5.16.4.6 Aborting third-party copy commands and copy operations....................................................... 253
5.16.4.7 The COPY OPERATION ABORT command ............................................................................ 254

Working Draft SCSI Primary Commands - 4 (SPC-4) xi

T10/BSR INCITS 513 Revision 37 17 May 2014

5.16.5 Responses to the conditions that result from SCSI events.......................................................... 254
5.16.6 RODs and ROD tokens ............................................................................................................... 254
5.16.6.1 RODs and ROD related tokens overview ................................................................................. 254
5.16.6.2 ROD types ................................................................................................................................ 256
5.16.6.2.1 ROD types overview .............................................................................................................. 256
5.16.6.2.2 Access upon reference type RODs ....................................................................................... 256
5.16.6.2.3 Point in time copy RODs........................................................................................................ 257
5.16.6.2.3.1 Point in time copy RODs overview ..................................................................................... 257
5.16.6.2.3.2 Point in time copy – default type RODs .............................................................................. 257
5.16.6.2.3.3 Point in time copy – change vulnerable type RODs ........................................................... 257
5.16.6.2.3.4 Point in time copy – persistent type RODs ......................................................................... 257
5.16.6.2.3.5 Point in time copy – any type RODs ................................................................................... 258
5.16.6.3 Populating a ROD or ROD token.............................................................................................. 258
5.16.6.4 ROD token format..................................................................................................................... 260
5.16.6.5 Generic ROD tokens................................................................................................................. 262
5.16.6.5.1 Generic ROD token format .................................................................................................... 262
5.16.6.5.2 Validating generic ROD tokens.............................................................................................. 264
5.16.6.5.2.1 Overview of validating generic ROD tokens ....................................................................... 264
5.16.6.5.2.2 Inexact validation of generic ROD tokens........................................................................... 265
5.16.6.5.2.3 Validation errors for generic ROD tokens ........................................................................... 265
5.16.6.6 ROD token usage ..................................................................................................................... 267
5.16.6.7 ROD token lifetime.................................................................................................................... 268
5.16.7 The EXTENDED COPY command .............................................................................................. 269
5.16.7.1 EXTENDED COPY parameter list ............................................................................................ 269
5.16.7.2 EXTENDED COPY command processing................................................................................ 269
5.16.7.3 EXTENDED COPY command errors detected before segment descriptor processing starts .. 274
5.16.7.4 EXTENDED COPY command errors detected during processing of segment descriptors ...... 274
5.16.7.5 EXTENDED COPY considerations for RODs and ROD tokens ............................................... 277
5.16.7.5.1 EXTENDED COPY command CSCD ROD identifiers........................................................... 277
5.16.7.5.2 Populating an EXTENDED COPY command ROD ............................................................... 277
5.16.7.6 EXTENDED COPY command use of RODs when the peripheral device type is 00h
(i.e., block device) .................................................................................................................... 278
5.16.7.7 EXTENDED COPY command interactions with aliases ........................................................... 279

6 Commands for all device types .................................................................................................................. 280

6.1 Summary of commands for all device types ..................................................................................... 280
6.2 CHANGE ALIASES command.......................................................................................................... 282
6.2.1 CHANGE ALIASES command introduction ................................................................................... 282
6.2.2 Alias entry format........................................................................................................................... 284
6.2.3 Alias designation validation ........................................................................................................... 285
6.2.4 Alias entry protocol independent designations .............................................................................. 285
6.2.4.1 Alias entry protocol independent designations overview ............................................................ 285
6.2.4.2 NULL DESIGNATION alias format ............................................................................................. 286
6.3 COPY OPERATION ABORT command ........................................................................................... 286
6.4 EXTENDED COPY(LID4) command ................................................................................................ 287
6.4.1 EXTENDED COPY(LID4) command introduction.......................................................................... 287
6.4.2 EXTENDED COPY(LID4) parameter data..................................................................................... 288
6.4.3 Shared EXTENDED COPY parameter list fields ........................................................................... 290
6.4.3.1 STR bit ......................................................................................................................................... 290
6.4.3.2 LIST IDENTIFIER field and LIST ID USAGE field ................................................................................ 291
6.4.3.3 PRIORITY field............................................................................................................................... 293
6.4.3.4 CSCD DESCRIPTOR LIST LENGTH field and CSCD descriptor list .................................................... 293
6.4.3.5 SEGMENT DESCRIPTOR LIST LENGTH field and segment descriptor list .......................................... 293
6.4.3.6 INLINE DATA LENGTH field and inline data ..................................................................................... 294

xii Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4.4 Descriptor type codes .................................................................................................................... 294

6.4.5 CSCD descriptors .......................................................................................................................... 295
6.4.5.1 CSCD descriptors introduction ................................................................................................... 295
6.4.5.2 The CSCD descriptor extension ................................................................................................. 298
6.4.5.3 Device type specific CSCD descriptor parameters for block device types ................................. 298
6.4.5.4 Device type specific CSCD descriptor parameters for sequential-access device types............. 299
6.4.5.5 Device type specific CSCD descriptor parameters for processor device types.......................... 300
6.4.5.6 Identification Descriptor CSCD descriptor format ....................................................................... 301
6.4.5.7 Alias CSCD descriptor format..................................................................................................... 302
6.4.5.8 IP Copy Service CSCD descriptor .............................................................................................. 303
6.4.5.9 ROD CSCD descriptor................................................................................................................ 305
6.4.6 Segment descriptors...................................................................................................................... 310
6.4.6.1 Segment descriptors introduction ............................................................................................... 310
6.4.6.2 Block device to stream device functions..................................................................................... 314
6.4.6.3 Stream device to block device functions..................................................................................... 315
6.4.6.4 Block device to block device functions ....................................................................................... 317
6.4.6.5 Stream device to stream device functions .................................................................................. 319
6.4.6.6 Inline data to stream device function .......................................................................................... 321
6.4.6.7 Embedded data to stream device function ................................................................................. 322
6.4.6.8 Stream device to discard functions............................................................................................. 324
6.4.6.9 Verify CSCD function.................................................................................................................. 325
6.4.6.10 Block device with offset to stream device function ................................................................... 327
6.4.6.11 Stream device to block device with offset function ................................................................... 329
6.4.6.12 Block device with offset to block device with offset function..................................................... 331
6.4.6.13 Write filemarks function ............................................................................................................ 332
6.4.6.14 Space function .......................................................................................................................... 333
6.4.6.15 Locate function ......................................................................................................................... 334
6.4.6.16 Tape device image copy function ............................................................................................. 335
6.4.6.17 Register persistent reservation key function............................................................................. 336
6.4.6.18 Third party persistent reservations source I_T nexus function ................................................. 337
6.4.6.19 Block device image copy function............................................................................................. 339
6.4.6.20 Populate a ROD from one or more block ranges function ........................................................ 341
6.4.6.21 Populate a ROD from one block range function ....................................................................... 343
6.5 EXTENDED COPY(LID1) command ................................................................................................ 344
6.6 INQUIRY command .......................................................................................................................... 347
6.6.1 INQUIRY command introduction ................................................................................................... 347
6.6.2 Standard INQUIRY data ................................................................................................................ 348
6.6.3 SCSI Parallel Interface specific INQUIRY data ............................................................................. 366
6.7 LOG SELECT command .................................................................................................................. 368
6.7.1 Introduction .................................................................................................................................... 368
6.7.2 Processing LOG SELECT when the parameter list length is zero................................................. 370
6.8 LOG SENSE command .................................................................................................................... 373
6.9 MANAGEMENT PROTOCOL IN command ..................................................................................... 375
6.9.1 MANAGEMENT PROTOCOL IN command description ................................................................ 375
6.9.2 Management protocol information description............................................................................... 376
6.9.2.1 Overview..................................................................................................................................... 376
6.9.2.2 CDB description.......................................................................................................................... 376
6.9.2.3 Supported management protocols list description...................................................................... 377
6.10 MANAGEMENT PROTOCOL OUT command ............................................................................... 378
6.11 MODE SELECT(6) command......................................................................................................... 379
6.12 MODE SELECT(10) command....................................................................................................... 381
6.13 MODE SENSE(6) command........................................................................................................... 382
6.13.1 MODE SENSE(6) command introduction .................................................................................... 382
6.13.2 Current values ............................................................................................................................. 384

Working Draft SCSI Primary Commands - 4 (SPC-4) xiii

T10/BSR INCITS 513 Revision 37 17 May 2014

6.13.3 Changeable values ...................................................................................................................... 384

6.13.4 Default values .............................................................................................................................. 384
6.13.5 Saved values ............................................................................................................................... 384
6.13.6 Initial responses........................................................................................................................... 385
6.14 MODE SENSE(10) command......................................................................................................... 385
6.15 PERSISTENT RESERVE IN command.......................................................................................... 386
6.15.1 PERSISTENT RESERVE IN command introduction ................................................................... 386
6.15.2 READ KEYS service action ......................................................................................................... 387
6.15.3 READ RESERVATION service action ......................................................................................... 388
6.15.3.1 READ RESERVATION service action operation ...................................................................... 388
6.15.3.2 Persistent reservations scope................................................................................................... 390
6.15.3.3 Persistent reservations type ..................................................................................................... 391
6.15.4 REPORT CAPABILITIES service action...................................................................................... 392
6.15.5 READ FULL STATUS service action........................................................................................... 396
6.16 PERSISTENT RESERVE OUT command...................................................................................... 398
6.16.1 PERSISTENT RESERVE OUT command introduction ............................................................... 398
6.16.2 PERSISTENT RESERVE OUT service actions and parameter list formats................................ 400
6.16.3 Basic PERSISTENT RESERVE OUT parameter list................................................................... 403
6.16.4 Parameter list for the PERSISTENT RESERVE OUT command with REGISTER AND MOVE
service action .............................................................................................................................. 406
6.17 READ ATTRIBUTE command ........................................................................................................ 408
6.17.1 READ ATTRIBUTE command introduction ................................................................................. 408
6.17.2 ATTRIBUTE VALUES service action........................................................................................... 411
6.17.3 ATTRIBUTE LIST service action ................................................................................................. 412
6.17.4 LOGICAL VOLUME LIST service action ..................................................................................... 412
6.17.5 PARTITION LIST service action .................................................................................................. 413
6.17.6 SUPPORTED ATTRIBUTES service action ................................................................................ 414
6.18 READ BUFFER command.............................................................................................................. 414
6.18.1 READ BUFFER command introduction ....................................................................................... 414
6.18.2 Vendor specific mode (01h)......................................................................................................... 416
6.18.3 Data mode (02h).......................................................................................................................... 416
6.18.4 Descriptor mode (03h) ................................................................................................................. 416
6.18.5 Read data from echo buffer mode (0Ah) ..................................................................................... 417
6.18.6 Echo buffer descriptor mode (0Bh).............................................................................................. 418
6.18.7 Error history mode (1Ch) ............................................................................................................. 418
6.18.7.1 Error history overview ............................................................................................................... 418
6.18.7.2 Error history directory ............................................................................................................... 420
6.18.7.3 Error history data buffer ............................................................................................................ 422
6.18.7.4 Clear error history I_T nexus .................................................................................................... 422
6.18.7.5 Clear error history I_T nexus and release snapshot................................................................. 422
6.19 READ MEDIA SERIAL NUMBER command .................................................................................. 423
6.20 RECEIVE COPY DATA(LID4) command ....................................................................................... 424
6.21 RECEIVE COPY DATA(LID1) command ....................................................................................... 427
6.22 RECEIVE COPY OPERATING PARAMETERS command ............................................................ 429
6.23 RECEIVE COPY FAILURE DETAILS(LID1) command.................................................................. 432
6.24 RECEIVE COPY STATUS(LID4) command................................................................................... 435
6.25 RECEIVE COPY STATUS(LID1) command................................................................................... 439
6.26 RECEIVE CREDENTIAL command ............................................................................................... 441
6.26.1 RECEIVE CREDENTIAL command description .......................................................................... 441
6.26.1.1 Overview................................................................................................................................... 441
6.26.1.2 CbCS logical unit credential request descriptor........................................................................ 443
6.26.1.3 CbCS logical unit and volume credential request descriptor .................................................... 443
6.26.2 RECEIVE CREDENTIAL parameter data.................................................................................... 444
6.26.2.1 RECEIVE CREDENTIAL parameter data encryption ............................................................... 444

xiv Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.26.2.2 RECEIVE CREDENTIAL decrypted parameter data ................................................................ 444

6.26.2.3 CbCS capability descriptor ....................................................................................................... 446
6.26.2.3.1 Overview................................................................................................................................ 446
6.26.2.3.2 Logical unit designation descriptor format ............................................................................. 449
6.26.2.3.3 Volume designation descriptors............................................................................................. 449
6.27 RECEIVE DIAGNOSTIC RESULTS command .............................................................................. 450
6.28 RECEIVE ROD TOKEN INFORMATION command....................................................................... 451
6.29 REMOVE I_T NEXUS command.................................................................................................... 453
6.30 REPORT ALIASES command ........................................................................................................ 456
6.31 REPORT ALL ROD TOKENS command........................................................................................ 458
6.32 REPORT IDENTIFYING INFORMATION command ...................................................................... 459
6.32.1 REPORT IDENTIFYING INFORMATION command overview.................................................... 459
6.32.2 Peripheral device identifying information parameter data............................................................ 461
6.32.3 Identifying information supported parameter data ....................................................................... 461
6.33 REPORT LUNS command ............................................................................................................. 463
6.34 REPORT PRIORITY command ...................................................................................................... 466
6.35 REPORT SUPPORTED OPERATION CODES command............................................................. 468
6.35.1 REPORT SUPPORTED OPERATION CODES command introduction ...................................... 468
6.35.2 All_commands parameter data format......................................................................................... 470
6.35.3 One_command parameter data format........................................................................................ 472
6.35.4 Command timeouts descriptor..................................................................................................... 473
6.35.4.1 Overview................................................................................................................................... 473
6.35.4.2 WRITE BUFFER command timeouts descriptor COMMAND SPECIFIC field usage...................... 474
6.36 REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS command ..................................... 475
6.37 REPORT TARGET PORT GROUPS command............................................................................. 479
6.38 REPORT TIMESTAMP command .................................................................................................. 484
6.39 REQUEST SENSE command ........................................................................................................ 485
6.40 SECURITY PROTOCOL IN command ........................................................................................... 488
6.41 SECURITY PROTOCOL OUT command ....................................................................................... 490
6.42 SEND DIAGNOSTIC command...................................................................................................... 492
6.43 SET IDENTIFYING INFORMATION command .............................................................................. 499
6.44 SET PRIORITY command .............................................................................................................. 501
6.45 SET TARGET PORT GROUPS command..................................................................................... 503
6.46 SET TIMESTAMP command .......................................................................................................... 507
6.47 TEST UNIT READY command ....................................................................................................... 508
6.48 WRITE ATTRIBUTE command ...................................................................................................... 510
6.49 WRITE BUFFER command ............................................................................................................ 513
6.49.1 WRITE BUFFER command introduction ..................................................................................... 513
6.49.2 Vendor specific mode (01h)......................................................................................................... 514
6.49.3 Data mode (02h).......................................................................................................................... 514
6.49.4 Download microcode and activate mode (04h) ........................................................................... 515
6.49.5 Download microcode, save, and activate mode (05h)................................................................. 515
6.49.6 Download microcode with offsets and activate mode (06h) ........................................................ 515
6.49.7 Download microcode with offsets, save, and activate mode (07h).............................................. 516
6.49.8 Write data to echo buffer mode (0Ah).......................................................................................... 516
6.49.9 Download microcode with offsets, select activation, save, and defer activate mode (0Dh) ........ 516
6.49.10 Download microcode with offsets, save, and defer activate mode (0Eh) .................................. 517
6.49.11 Activate deferred microcode mode (0Fh) .................................................................................. 518
6.49.12 Download application client error history mode (1Ch) ............................................................... 518

7 Parameters for all device types.................................................................................................................. 522

7.1 Overview........................................................................................................................................... 522
7.2 Diagnostic parameters...................................................................................................................... 522
7.2.1 Summary of diagnostic page codes............................................................................................... 522

Working Draft SCSI Primary Commands - 4 (SPC-4) xv

T10/BSR INCITS 513 Revision 37 17 May 2014

7.2.2 Diagnostic page format for all device types ................................................................................... 522
7.2.3 Protocol Specific diagnostic page.................................................................................................. 524
7.2.4 Supported Diagnostic Pages diagnostic page ............................................................................... 524
7.3 Log parameters................................................................................................................................. 526
7.3.1 Summary of log page codes .......................................................................................................... 526
7.3.2 Log page structure and log parameter structure for all device types............................................. 527
7.3.2.1 Log page structure...................................................................................................................... 527
7.3.2.2 Log parameter structure ............................................................................................................. 529
7.3.2.2.1 Introduction .............................................................................................................................. 529
7.3.2.2.2 Parameter control byte ............................................................................................................ 530
7.3.2.2.2.1 Introduction ........................................................................................................................... 530
7.3.2.2.2.2 Parameter control byte values for bounded data counter parameters.................................. 532
7.3.2.2.2.3 Parameter control byte values for unbounded data counter parameters.............................. 533
7.3.2.2.2.4 Parameter control byte values for ASCII format list log parameters..................................... 534
7.3.2.2.2.5 Parameter control byte values for binary format list log parameters .................................... 535
7.3.3 Resetting and setting log parameters ............................................................................................ 535
7.3.4 Application Client log page ............................................................................................................ 536
7.3.4.1 Overview..................................................................................................................................... 536
7.3.4.2 General Usage Application Client log parameter........................................................................ 537
7.3.5 Buffer Over-Run/Under-Run log page ........................................................................................... 538
7.3.5.1 Overview..................................................................................................................................... 538
7.3.5.2 Buffer Over-run/Under-run log parameter................................................................................... 540
7.3.6 Cache Memory Statistics log page ................................................................................................ 541
7.3.6.1 Overview..................................................................................................................................... 541
7.3.6.2 Read Cache Memory Hits log parameter ................................................................................... 543
7.3.6.3 Reads To Cache Memory log parameter.................................................................................... 544
7.3.6.4 Write Cache Memory Hits log parameter.................................................................................... 545
7.3.6.5 Writes From Cache Memory log parameter................................................................................ 546
7.3.6.6 Time From Last Hard Reset log parameter ................................................................................ 547
7.3.6.7 Time Interval log parameter........................................................................................................ 548
7.3.7 General Statistics and Performance log pages ............................................................................ 549
7.3.7.1 Overview..................................................................................................................................... 549
7.3.7.2 General Access Statistics and Performance log parameter ....................................................... 551
7.3.7.3 Idle Time log parameter.............................................................................................................. 553
7.3.7.4 Force Unit Access Statistics and Performance log parameter ................................................... 554
7.3.8 Group Statistics and Performance (n) log pages........................................................................... 555
7.3.8.1 Overview..................................................................................................................................... 555
7.3.8.2 Group n Statistics and Performance log parameter.................................................................... 559
7.3.8.3 Group n Force Unit Access Statistics and Performance log parameter ..................................... 561
7.3.9 Informational Exceptions log page................................................................................................. 562
7.3.9.1 Overview..................................................................................................................................... 562
7.3.9.2 Informational Exceptions General log parameter ....................................................................... 563
7.3.10 Last n Deferred Errors or Asynchronous Events log page .......................................................... 564
7.3.10.1 Overview................................................................................................................................... 564
7.3.10.2 Deferred Error or Asynchronous Event log parameters............................................................ 566
7.3.11 Last n Error Events log page ....................................................................................................... 566
7.3.11.1 Overview................................................................................................................................... 566
7.3.11.2 Error Event log parameters....................................................................................................... 568
7.3.12 Non-Medium Error log page ........................................................................................................ 568
7.3.12.1 Overview................................................................................................................................... 568
7.3.12.2 Non-Medium Error Count log parameter .................................................................................. 569
7.3.13 Power Condition Transitions log page ......................................................................................... 570
7.3.13.1 Overview................................................................................................................................... 570
7.3.13.2 Accumulated Transitions log parameter ................................................................................... 571

xvi Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.3.14 Protocol Specific Port log page.................................................................................................... 572

7.3.14.1 Overview................................................................................................................................... 572
7.3.14.2 Generic protocol specific port log parameter ............................................................................ 573
7.3.15 Read Error Counters log page..................................................................................................... 574
7.3.15.1 Overview................................................................................................................................... 574
7.3.15.2 Read Error Counter log parameter ........................................................................................... 575
7.3.16 Read Reverse Error Counters log page ...................................................................................... 576
7.3.16.1 Overview................................................................................................................................... 576
7.3.16.2 Read Reverse Error Counter log parameter............................................................................. 577
7.3.17 Self-Test Results log page........................................................................................................... 578
7.3.17.1 Overview................................................................................................................................... 578
7.3.17.2 Self-Test Results log parameters ............................................................................................. 580
7.3.18 Start-Stop Cycle Counter log page .............................................................................................. 582
7.3.18.1 Overview................................................................................................................................... 582
7.3.18.2 Date of Manufacture log parameter .......................................................................................... 583
7.3.18.3 Accounting Date log parameter ................................................................................................ 584
7.3.18.4 Specified Cycle Count Over Device Lifetime log parameter..................................................... 585
7.3.18.5 Accumulated Start-Stop Cycles log parameter......................................................................... 585
7.3.18.6 Specified Load-Unload Count Over Device Lifetime log parameter ......................................... 586
7.3.18.7 Accumulated Load-Unload Cycles log parameter .................................................................... 587
7.3.19 Supported Log Pages log page ................................................................................................... 588
7.3.20 Supported Log Pages and Subpages log page ........................................................................... 589
7.3.21 Supported Subpages log page .................................................................................................... 590
7.3.22 Temperature log page ................................................................................................................. 591
7.3.22.1 Overview................................................................................................................................... 591
7.3.22.2 Temperature log parameter ...................................................................................................... 592
7.3.22.3 Reference Temperature log parameter .................................................................................... 592
7.3.23 Verify Error Counters log page .................................................................................................... 593
7.3.23.1 Overview................................................................................................................................... 593
7.3.23.2 Verify Error Counter log parameter........................................................................................... 595
7.3.24 Write Error Counters log page ..................................................................................................... 595
7.3.24.1 Overview................................................................................................................................... 595
7.3.24.2 Write Error Counter log parameter ........................................................................................... 597
7.4 Medium auxiliary memory attributes ................................................................................................. 598
7.4.1 Attribute format .............................................................................................................................. 598
7.4.2 Attribute identifier values ............................................................................................................... 599
7.4.2.1 Attribute identifier values overview ............................................................................................. 599
7.4.2.2 Device type attributes ................................................................................................................. 599
7.4.2.2.1 REMAINING CAPACITY IN PARTITION and MAXIMUM CAPACITY IN PARTITION ........... 600
7.4.2.2.2 LOAD COUNT ......................................................................................................................... 600
7.4.2.2.3 MAM SPACE REMAINING...................................................................................................... 600
7.4.2.2.4 INITIALIZATION COUNT......................................................................................................... 601
7.4.2.2.5 VOLUME IDENTIFIER............................................................................................................ 601
7.4.2.2.6 DEVICE VENDOR/SERIAL NUMBER AT LAST LOAD, DEVICE VENDOR/SERIAL
NUMBER AT LOAD –1, DEVICE VENDOR/SERIAL NUMBER AT LOAD –2 and DEVICE
VENDOR/SERIAL NUMBER AT LOAD –3 .............................................................................. 601
7.4.2.2.7 TOTAL MEBIBYTES WRITTEN IN MEDIUM LIFE and TOTAL MEBIBYTES READ IN
MEDIUM LIFE .......................................................................................................................... 601
7.4.2.2.8 TOTAL MEBIBYTES WRITTEN IN CURRENT/LAST LOAD and TOTAL MEBIBYTES
READ IN CURRENT/LAST LOAD ........................................................................................... 601
7.4.2.2.9 LOGICAL POSITION OF FIRST ENCRYPTED BLOCK ......................................................... 602
7.4.2.2.10 LOGICAL POSITION OF FIRST UNENCRYPTED BLOCK AFTER THE FIRST
ENCRYPTED BLOCK .............................................................................................................. 602
7.4.2.2.11 MEDIUM USAGE HISTORY.................................................................................................. 603

Working Draft SCSI Primary Commands - 4 (SPC-4) xvii

T10/BSR INCITS 513 Revision 37 17 May 2014

7.4.2.2.12 PARTITION USAGE HISTORY ............................................................................................. 605

7.4.2.3 Medium type attributes ............................................................................................................... 607
7.4.2.3.1 MEDIUM MANUFACTURER ................................................................................................... 608
7.4.2.3.2 MEDIUM SERIAL NUMBER.................................................................................................... 608
7.4.2.3.3 MEDIUM MANUFACTURE DATE ........................................................................................... 608
7.4.2.3.4 MAM CAPACITY ..................................................................................................................... 608
7.4.2.3.5 MEDIUM TYPE and MEDIUM TYPE INFORMATION............................................................. 608
7.4.2.3.6 NUMERIC MEDIUM SERIAL NUMBER .................................................................................. 609
7.4.2.4 Host type attributes..................................................................................................................... 609
7.4.2.4.1 APPLICATION VENDOR......................................................................................................... 610
7.4.2.4.2 APPLICATION NAME.............................................................................................................. 610
7.4.2.4.3 APPLICATION VERSION........................................................................................................ 610
7.4.2.4.4 USER MEDIUM TEXT LABEL................................................................................................. 610
7.4.2.4.5 DATE & TIME LAST WRITTEN............................................................................................... 610
7.4.2.4.6 TEXT LOCALIZATION IDENTIFIER........................................................................................ 611
7.4.2.4.7 BARCODE ............................................................................................................................... 611
7.4.2.4.8 OWNING HOST TEXTUAL NAME .......................................................................................... 611
7.4.2.4.9 MEDIA POOL .......................................................................................................................... 611
7.4.2.4.10 PARTITION USER TEXT LABEL .......................................................................................... 611
7.4.2.4.11 LOAD/UNLOAD AT PARTITION ........................................................................................... 611
7.4.2.4.12 APPLICATION FORMAT VERSION...................................................................................... 612
7.5 Mode parameters.............................................................................................................................. 613
7.5.1 Summary of mode page codes...................................................................................................... 613
7.5.2 Mode page policies........................................................................................................................ 614
7.5.3 Mode parameters overview ........................................................................................................... 614
7.5.4 Mode parameter list format............................................................................................................ 614
7.5.5 Mode parameter header formats ................................................................................................... 615
7.5.6 Mode parameter block descriptor formats ..................................................................................... 616
7.5.6.1 General block descriptor format.................................................................................................. 616
7.5.7 Mode page and subpage formats and page codes ....................................................................... 617
7.5.8 Control mode page ........................................................................................................................ 618
7.5.9 Control Extension mode page ....................................................................................................... 623
7.5.10 Disconnect-Reconnect mode page.............................................................................................. 624
7.5.11 Extended mode page................................................................................................................... 627
7.5.12 Extended Device-Type Specific mode page................................................................................ 628
7.5.13 Power Condition mode page ....................................................................................................... 628
7.5.14 Power Consumption mode page ................................................................................................. 633
7.5.15 Protocol Specific Logical Unit mode page ................................................................................... 634
7.5.16 Protocol Specific Port mode page ............................................................................................... 635
7.6 Protocol specific parameters ............................................................................................................ 637
7.6.1 Protocol specific parameters introduction...................................................................................... 637
7.6.2 Alias entry protocol specific designations ...................................................................................... 637
7.6.2.1 Introduction to alias entry protocol specific designations............................................................ 637
7.6.2.2 Fibre Channel specific alias entry formats.................................................................................. 638
7.6.2.2.1 Summary of Fibre Channel specific alias entry formats .......................................................... 638
7.6.2.2.2 Fibre Channel world wide port name alias entry format .......................................................... 638
7.6.2.2.3 Fibre Channel world wide port name with N_Port checking alias entry format........................ 639
7.6.2.3 RDMA specific alias entry formats.............................................................................................. 640
7.6.2.3.1 Summary of RDMA specific alias entry formats ...................................................................... 640
7.6.2.3.2 RDMA target port identifier alias entry format.......................................................................... 641
7.6.2.3.3 InfiniBand global identifier with target port identifier checking alias entry format .................... 642
7.6.2.4 Internet SCSI specific alias entry formats................................................................................... 643
7.6.2.4.1 Summary of Internet SCSI specific alias entry formats ........................................................... 643
7.6.2.4.2 iSCSI name alias entry format ................................................................................................. 644

xviii Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.6.2.4.3 iSCSI name with binary IPv4 address alias entry format......................................................... 645
7.6.2.4.4 iSCSI name with IPname alias entry format ............................................................................ 647
7.6.2.4.5 iSCSI name with binary IPv6 address alias entry format......................................................... 649
7.6.3 EXTENDED COPY protocol specific CSCD descriptors ............................................................... 651
7.6.3.1 Introduction to EXTENDED COPY protocol specific CSCD descriptors..................................... 651
7.6.3.2 Fibre Channel N_Port_Name CSCD descriptor format .............................................................. 651
7.6.3.3 Fibre Channel N_Port_ID CSCD descriptor format .................................................................... 652
7.6.3.4 Fibre Channel N_Port_ID With N_Port_Name Checking CSCD descriptor format .................... 653
7.6.3.5 SCSI Parallel T_L CSCD descriptor format ............................................................................... 654
7.6.3.6 IEEE 1394 EUI-64 CSCD descriptor format ............................................................................... 655
7.6.3.7 RDMA CSCD descriptor format .................................................................................................. 656
7.6.3.8 iSCSI IPv4 CSCD descriptor format .......................................................................................... 657
7.6.3.9 iSCSI IPv6 CSCD descriptor format .......................................................................................... 658
7.6.3.10 SAS Serial SCSI Protocol CSCD descriptor format.................................................................. 659
7.6.4 TransportID identifiers ................................................................................................................... 659
7.6.4.1 Overview of TransportID identifiers ............................................................................................ 659
7.6.4.2 TransportID for initiator ports using SCSI over Fibre Channel ................................................... 661
7.6.4.3 TransportID for initiator ports using a parallel SCSI bus............................................................. 662
7.6.4.4 TransportID for initiator ports using SCSI over IEEE 1394......................................................... 663
7.6.4.5 TransportID for initiator ports using SCSI over an RDMA interface............................................ 663
7.6.4.6 TransportID for initiator ports using SCSI over iSCSI................................................................. 664
7.6.4.7 TransportID for initiator ports using SCSI over SAS Serial SCSI Protocol ................................. 666
7.6.4.8 TransportID for initiator ports using SCSI over PCI Express ...................................................... 666
7.7 Security protocol parameters............................................................................................................ 667
7.7.1 Security protocol information description....................................................................................... 667
7.7.1.1 Overview..................................................................................................................................... 667
7.7.1.2 CDB description.......................................................................................................................... 667
7.7.1.3 Supported security protocols list description .............................................................................. 668
7.7.1.4 Certificate data description ......................................................................................................... 669
7.7.1.4.1 Certificate overview ................................................................................................................. 669
7.7.1.4.2 Public Key certificate description ............................................................................................. 669
7.7.1.4.3 Attribute certificate description................................................................................................. 669
7.7.1.5 Security compliance information description .............................................................................. 670
7.7.1.5.1 Security compliance information overview............................................................................... 670
7.7.1.5.2 Compliance descriptor overview.............................................................................................. 671
7.7.1.5.3 FIPS 140 compliance descriptor.............................................................................................. 672
7.7.2 SA creation capabilities ................................................................................................................. 673
7.7.2.1 Overview..................................................................................................................................... 673
7.7.2.2 SA creation capabilities CDB description ................................................................................... 673
7.7.2.3 SA creation capabilities parameter data formats ........................................................................ 674
7.7.2.3.1 Supported device server capabilities formats parameter data format ..................................... 674
7.7.2.3.2 IKEv2-SCSI device server capabilities parameter data format................................................ 675
7.7.3 IKEv2-SCSI.................................................................................................................................... 675
7.7.3.1 Overview..................................................................................................................................... 675
7.7.3.2 IKEv2-SCSI SECURITY PROTOCOL IN CDB description......................................................... 676
7.7.3.3 IKEv2-SCSI SECURITY PROTOCOL OUT CDB description..................................................... 677
7.7.3.4 IKEv2-SCSI parameter data format ............................................................................................ 678
7.7.3.5 IKEv2-SCSI payloads ................................................................................................................. 686
7.7.3.5.1 IKEv2-SCSI payload format..................................................................................................... 686
7.7.3.5.2 No Next payload ...................................................................................................................... 687
7.7.3.5.3 Key Exchange payload ............................................................................................................ 687
7.7.3.5.4 Identification – Application Client payload and Identification – Device Server payload........... 688
7.7.3.5.5 Certificate payload ................................................................................................................... 690
7.7.3.5.6 Certificate Request payload..................................................................................................... 691

Working Draft SCSI Primary Commands - 4 (SPC-4) xix

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.3.5.7 Authentication payload ............................................................................................................ 692

7.7.3.5.8 Nonce payload......................................................................................................................... 695
7.7.3.5.9 Notify payload .......................................................................................................................... 696
7.7.3.5.10 Delete payload....................................................................................................................... 697
7.7.3.5.11 Encrypted payload ................................................................................................................. 698
7.7.3.5.11.1 Combined mode encryption................................................................................................ 698
7.7.3.5.11.2 Encrypted payload introduction .......................................................................................... 699
7.7.3.5.11.3 IKEv2-SCSI AAD ................................................................................................................ 701
7.7.3.5.11.4 Processing a received Encrypted payload.......................................................................... 702
7.7.3.5.12 IKEv2-SCSI SA Creation Capabilities payload ...................................................................... 704
7.7.3.5.13 IKEv2-SCSI SA Cryptographic Algorithms payload............................................................... 705
7.7.3.5.14 IKEv2-SCSI SAUT Cryptographic Algorithms payload .......................................................... 707
7.7.3.5.15 IKEv2-SCSI Timeout Values payload .................................................................................... 709
7.7.3.6 IKEv2-SCSI cryptographic algorithm descriptors........................................................................ 710
7.7.3.6.1 Overview.................................................................................................................................. 710
7.7.3.6.2 ENCR IKEv2-SCSI cryptographic algorithm descriptor ........................................................... 711
7.7.3.6.3 PRF IKEv2-SCSI cryptographic algorithm descriptor .............................................................. 713
7.7.3.6.4 INTEG IKEv2-SCSI cryptographic algorithm descriptor .......................................................... 715
7.7.3.6.5 D-H IKEv2-SCSI cryptographic algorithm descriptor ............................................................... 716
7.7.3.6.6 IKEv2-SCSI authentication algorithm IKEv2-SCSI cryptographic algorithm descriptor ........... 718
7.7.3.7 Errors in IKEv2-SCSI security protocol commands .................................................................... 721
7.7.3.8 Errors in IKEv2-SCSI security protocol parameter data ............................................................. 723
7.7.3.8.1 Overview.................................................................................................................................. 723
7.7.3.8.2 Errors with high denial of service attack potential.................................................................... 723
7.7.3.8.3 Errors with low denial of service attack potential ..................................................................... 724
7.7.3.9 Translating IKEv2 errors ............................................................................................................. 724
7.7.4 CbCS security protocol .................................................................................................................. 726
7.7.4.1 Overview..................................................................................................................................... 726
7.7.4.2 CbCS SECURITY PROTOCOL IN CDB description .................................................................. 726
7.7.4.3 CbCS SECURITY PROTOCOL IN parameter data.................................................................... 727
7.7.4.3.1 Supported CbCS SECURITY PROTOCOL IN Pages CbCS page.......................................... 727
7.7.4.3.2 Supported CbCS SECURITY PROTOCOL OUT pages CbCS page ...................................... 727
7.7.4.3.3 Unchangeable CbCS Parameters CbCS page........................................................................ 728
7.7.4.3.4 Security Token CbCS page ..................................................................................................... 731
7.7.4.3.5 Current CbCS Parameters CbCS page ................................................................................... 731
7.7.4.3.6 Set Master Key – Seed Exchange CbCS page ....................................................................... 734
7.7.4.4 CbCS SECURITY PROTOCOL OUT CDB description .............................................................. 736
7.7.4.5 CbCS SECURITY PROTOCOL OUT parameter list .................................................................. 737
7.7.4.5.1 Set Policy Access Tag CbCS page ......................................................................................... 737
7.7.4.5.2 Set Minimum CbCS Method CbCS page................................................................................. 738
7.7.4.5.3 Invalidate Key CbCS page....................................................................................................... 739
7.7.4.5.4 Set Key CbCS page................................................................................................................. 740
7.7.4.5.5 Set Master Key – Seed Exchange CbCS page ....................................................................... 741
7.7.4.5.6 Set Master Key – Change Master Key CbCS page................................................................. 742
7.8 Vital product data parameters........................................................................................................... 744
7.8.1 Vital product data parameters overview and page codes.............................................................. 744
7.8.2 VPD page format for all device types ............................................................................................ 745
7.8.3 ASCII Information VPD page ......................................................................................................... 746
7.8.4 CFA Profile Information VPD page ................................................................................................ 747
7.8.5 Device Constituents VPD page ..................................................................................................... 748
7.8.6 Device Identification VPD page ..................................................................................................... 751
7.8.6.1 Device Identification VPD page overview ................................................................................... 751
7.8.6.2 Device designation descriptor requirements............................................................................... 753
7.8.6.2.1 Designation descriptors for logical units other than well known logical units........................... 753

xx Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.8.6.2.2 Designation descriptors for well known logical units................................................................ 754

7.8.6.2.3 Designation descriptors for SCSI target ports ......................................................................... 754
7.8.6.2.3.1 Relative target port identifiers ............................................................................................... 754
7.8.6.2.3.2 Target port names or identifiers............................................................................................ 754
7.8.6.2.4 Designation descriptors for SCSI target devices ..................................................................... 754
7.8.6.3 Vendor specific designator format .............................................................................................. 755
7.8.6.4 T10 vendor ID based designator format ..................................................................................... 755
7.8.6.5 EUI-64 based designator format................................................................................................. 756
7.8.6.5.1 EUI-64 based designator format overview............................................................................... 756
7.8.6.5.2 EUI-64 designator format......................................................................................................... 756
7.8.6.5.3 EUI-64 based 12-byte designator format................................................................................. 757
7.8.6.5.4 EUI-64 based 16-byte designator format................................................................................. 757
7.8.6.6 NAA designator format ............................................................................................................... 758
7.8.6.6.1 NAA identifier basic format ...................................................................................................... 758
7.8.6.6.2 NAA IEEE Extended designator format ................................................................................... 758
7.8.6.6.3 NAA Locally Assigned designator format ................................................................................ 759
7.8.6.6.4 NAA IEEE Registered designator format................................................................................. 759
7.8.6.6.5 NAA IEEE Registered Extended designator format................................................................. 760
7.8.6.7 Relative target port designator format ........................................................................................ 761
7.8.6.8 Target port group designator format ........................................................................................... 761
7.8.6.9 Logical unit group designator format .......................................................................................... 761
7.8.6.10 MD5 logical unit designator format ........................................................................................... 762
7.8.6.11 SCSI name string designator format......................................................................................... 763
7.8.6.12 Protocol specific port identifier designator format..................................................................... 764
7.8.6.12.1 Protocol specific port identifier designator format overview................................................... 764
7.8.6.12.2 USB target port identifier designator format .......................................................................... 765
7.8.6.12.3 PCI Express routing ID designator format ............................................................................. 765
7.8.7 Extended INQUIRY Data VPD page.............................................................................................. 766
7.8.8 Management Network Addresses VPD page ................................................................................ 770
7.8.9 Mode Page Policy VPD page ........................................................................................................ 772
7.8.10 Power Condition VPD page ......................................................................................................... 774
7.8.11 Power Consumption VPD page ................................................................................................... 776
7.8.12 Protocol Specific Logical Unit Information VPD page.................................................................. 777
7.8.13 Protocol Specific Port Information VPD page .............................................................................. 779
7.8.14 SCSI Ports VPD page.................................................................................................................. 781
7.8.15 Software Interface Identification VPD page ................................................................................. 784
7.8.16 Supported VPD Pages VPD page ............................................................................................... 785
7.8.17 Third-party Copy VPD page......................................................................................................... 786
7.8.17.1 Third-party Copy VPD page overview ...................................................................................... 786
7.8.17.2 Third-party copy descriptor format............................................................................................ 786
7.8.17.3 Third-party copy descriptor type codes..................................................................................... 787
7.8.17.4 Supported Commands third-party copy descriptor ................................................................... 788
7.8.17.4.1 Supported Commands third-party copy descriptor overview ................................................. 788
7.8.17.4.2 Command support descriptor format ..................................................................................... 789
7.8.17.5 Parameter Data third-party copy descriptor.............................................................................. 790
7.8.17.6 Supported Descriptors third-party copy descriptor ................................................................... 791
7.8.17.7 Supported CSCD Descriptor IDs third-party copy descriptor.................................................... 792
7.8.17.8 ROD Token Features third-party copy descriptor ..................................................................... 794
7.8.17.8.1 ROD Token Features third-party copy descriptor overview................................................... 794
7.8.17.8.2 Block ROD device type specific features descriptor .............................................................. 796
7.8.17.8.3 Stream ROD token device type features descriptor .............................................................. 798
7.8.17.8.4 Copy manager ROD token device type features descriptor .................................................. 799
7.8.17.9 Supported ROD Types third-party copy descriptor................................................................... 800
7.8.17.10 General Copy Operations third-party copy descriptor ............................................................ 803

Working Draft SCSI Primary Commands - 4 (SPC-4) xxi

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.17.11 Stream Copy Operations third-party copy descriptor.............................................................. 804

7.8.17.12 Held Data third-party copy descriptor ..................................................................................... 805
7.8.18 Unit Serial Number VPD page ..................................................................................................... 806

8 Well known logical units ............................................................................................................................. 807

8.1 Model for well known logical units .................................................................................................... 807
8.2 REPORT LUNS well known logical unit............................................................................................ 807
8.3 ACCESS CONTROLS well known logical unit ................................................................................. 808
8.3.1 Access controls model................................................................................................................... 808
8.3.1.1 Access controls commands ........................................................................................................ 808
8.3.1.2 Access controls overview ........................................................................................................... 808
8.3.1.3 Access Control List ..................................................................................................................... 809
8.3.1.3.1 ACL overview........................................................................................................................... 809
8.3.1.3.2 Access identifiers..................................................................................................................... 810
8.3.1.3.3 Logical Unit Access Control Descriptor ................................................................................... 811
8.3.1.4 Managing the ACL ...................................................................................................................... 811
8.3.1.4.1 ACL management overview..................................................................................................... 811
8.3.1.4.2 Authorizing ACL management................................................................................................. 811
8.3.1.4.3 Identifying logical units during ACL management.................................................................... 812
8.3.1.4.4 Tracking changes in logical unit identification.......................................................................... 812
8.3.1.5 Enrolling AccessIDs.................................................................................................................... 813
8.3.1.5.1 Enrollment states ..................................................................................................................... 813
8.3.1.5.1.1 Summary of enrollment states .............................................................................................. 813
8.3.1.5.1.2 Not-enrolled state ................................................................................................................. 813
8.3.1.5.1.3 Enrolled state........................................................................................................................ 814
8.3.1.5.1.4 Pending-enrolled state.......................................................................................................... 814
8.3.1.5.2 ACL LUN conflict resolution..................................................................................................... 815
8.3.1.6 Granting and revoking access rights .......................................................................................... 815
8.3.1.6.1 Non-proxy access rights .......................................................................................................... 815
8.3.1.6.2 Proxy access ........................................................................................................................... 816
8.3.1.6.2.1 Proxy tokens ......................................................................................................................... 816
8.3.1.6.2.2 Proxy LUNs........................................................................................................................... 816
8.3.1.7 Verifying access rights................................................................................................................ 817
8.3.1.8 The management identifier key .................................................................................................. 818
8.3.1.8.1 Management identifier key usage............................................................................................ 818
8.3.1.8.2 Overriding the management identifier key ............................................................................... 818
8.3.1.8.2.1 The OVERRIDE MGMT ID KEY service action .................................................................... 818
8.3.1.8.2.2 The override lockout timer .................................................................................................... 819
8.3.1.9 Reporting access control information ......................................................................................... 820
8.3.1.10 Access controls log................................................................................................................... 820
8.3.1.11 Interactions of access controls and other features ................................................................... 821
8.3.1.11.1 Task set management and access controls .......................................................................... 821
8.3.1.11.2 Existing reservations and ACL changes ................................................................................ 821
8.3.1.12 Access controls information persistence and memory usage requirements............................. 822
8.3.1.13 Access identifier formats........................................................................................................... 823
8.3.1.13.1 Access identifier type............................................................................................................. 823
8.3.1.13.2 AccessID access identifiers ................................................................................................... 823
8.3.2 ACCESS CONTROL IN command ................................................................................................ 824
8.3.2.1 ACCESS CONTROL IN introduction .......................................................................................... 824
8.3.2.2 REPORT ACL service action...................................................................................................... 825
8.3.2.2.1 REPORT ACL introduction ...................................................................................................... 825
8.3.2.2.2 REPORT ACL parameter data format ..................................................................................... 826
8.3.2.2.2.1 REPORT ACL parameter data introduction.......................................................................... 826
8.3.2.2.2.2 Granted ACL data page format............................................................................................. 827

xxii Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

8.3.2.2.2.3 Granted All ACL data page format........................................................................................ 828

8.3.2.2.2.4 Proxy Tokens ACL data page format.................................................................................... 830
8.3.2.3 REPORT LU DESCRIPTORS service action ............................................................................. 831
8.3.2.3.1 REPORT LU DESCRIPTORS introduction.............................................................................. 831
8.3.2.3.2 REPORT LU DESCRIPTORS parameter data format............................................................. 833
8.3.2.4 REPORT ACCESS CONTROLS LOG service action ................................................................ 837
8.3.2.4.1 REPORT ACCESS CONTROLS LOG introduction................................................................. 837
8.3.2.4.2 REPORT ACCESS CONTROLS LOG parameter data format................................................ 838
8.3.2.4.2.1 REPORT ACCESS CONTROLS LOG parameter data introduction .................................... 838
8.3.2.4.2.2 Key Overrides access controls log portion page format ....................................................... 839
8.3.2.4.2.3 Invalid Keys access controls log portion page format........................................................... 840
8.3.2.4.2.4 ACL LUN Conflicts access controls log portion page format ................................................ 841
8.3.2.5 REPORT OVERRIDE LOCKOUT TIMER service action ........................................................... 842
8.3.2.6 REQUEST PROXY TOKEN service action ................................................................................ 843
8.3.3 ACCESS CONTROL OUT command ............................................................................................ 845
8.3.3.1 ACCESS CONTROL OUT introduction ...................................................................................... 845
8.3.3.2 MANAGE ACL service action ..................................................................................................... 846
8.3.3.2.1 MANAGE ACL introduction...................................................................................................... 846
8.3.3.2.2 The Grant/Revoke ACE page .................................................................................................. 849
8.3.3.2.3 The Grant All ACE page .......................................................................................................... 852
8.3.3.2.4 The Revoke Proxy Token ACE page....................................................................................... 853
8.3.3.2.5 The Revoke All Proxy Tokens ACE page ................................................................................ 854
8.3.3.3 DISABLE ACCESS CONTROLS service action......................................................................... 854
8.3.3.4 ACCESS ID ENROLL service action .......................................................................................... 855
8.3.3.5 CANCEL ENROLLMENT service action..................................................................................... 856
8.3.3.6 CLEAR ACCESS CONTROLS LOG service action ................................................................... 857
8.3.3.7 MANAGE OVERRIDE LOCKOUT TIMER service action........................................................... 858
8.3.3.8 OVERRIDE MGMT ID KEY service action ................................................................................. 859
8.3.3.9 REVOKE PROXY TOKEN service action................................................................................... 860
8.3.3.10 REVOKE ALL PROXY TOKENS service action ....................................................................... 860
8.3.3.11 ASSIGN PROXY LUN service action ....................................................................................... 861
8.3.3.12 RELEASE PROXY LUN service action .................................................................................... 863
8.4 TARGET LOG PAGES well known logical unit................................................................................. 864
8.5 SECURITY PROTOCOL well known logical unit.............................................................................. 864
8.6 MANAGEMENT PROTOCOL well known logical unit ...................................................................... 864

9 Security manager command set ................................................................................................................ 866

Annex A (Informative) Terminology mapping................................................................................................ 867

Annex B (Informative) REPORT LUNS command examples........................................................................ 868

Annex C (Informative) Replacing RESERVE/RELEASE functionality with PERSISTENT RESERVE

IN/OUT equivalents .................................................................................................................. 872
C.1 Introduction ...................................................................................................................................... 872
C.2 Replacing the reserve/release method with the PERSISTENT RESERVE OUT COMMAND......... 872
C.3 Third party reservations ................................................................................................................... 873

Annex D (Informative) Third-party copy implementation and usage ............................................................. 874

D.1 Embedded and dedicated copy manager implementations ............................................................. 874
D.1.1 Overview ....................................................................................................................................... 874
D.1.2 Embedded copy manager implementations.................................................................................. 874
D.1.3 Dedicated copy manager implementations ................................................................................... 874
D.2 Tracking copy operation progress.................................................................................................... 875

Working Draft SCSI Primary Commands - 4 (SPC-4) xxiii

T10/BSR INCITS 513 Revision 37 17 May 2014

D.2.1 Overview ....................................................................................................................................... 875

D.2.2 Detecting lack of progress in active copy operations .................................................................... 875

Annex E (Informative) Variations between this standard and equivalent security protocols......................... 876
E.1 IKEv2 protocol details and variations for IKEv2-SCSI...................................................................... 876
E.2 ESP protocol details and variations for ESP-SCSI........................................................................... 879

Annex F (Informative) Numeric order codes ................................................................................................. 880

F.1 Numeric order codes introduction..................................................................................................... 880
F.2 Additional sense codes..................................................................................................................... 880
F.3 Operation codes ............................................................................................................................... 900
F.3.1 Operation codes ............................................................................................................................ 900
F.3.2 Additional operation codes for devices with the ENCSERV bit set to one ....................................... 906
F.3.3 MAINTENANCE IN service actions and MAINTENANCE OUT service actions ........................... 907
F.3.4 SERVICE ACTION IN service actions and SERVICE ACTION OUT service actions ................... 908
F.3.5 SERVICE ACTION BIDIRECTIONAL service actions................................................................... 909
F.3.6 Variable length CDB service action codes .................................................................................... 910
F.4 Diagnostic page codes ..................................................................................................................... 911
F.5 Log page codes ................................................................................................................................ 912
F.6 Mode page codes ............................................................................................................................. 915
F.7 VPD page codes............................................................................................................................... 918
F.8 ROD type codes ............................................................................................................................... 920
F.9 Version descriptor values ................................................................................................................. 921
F.10 T10 IEEE binary identifiers ............................................................................................................. 942

Annex G (Informative) T10 vendor identification........................................................................................... 943

Bibliography .................................................................................................................................................. 960

xxiv Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Tables
Page
Table 1 — Numbering conventions examples ................................................................................................ 31
Table 2 — Comparison of decimal prefixes and binary prefixes..................................................................... 32
Table 3 — Class diagram constraints and notes notation............................................................................... 37
Table 4 — Class diagram multiplicity notation ................................................................................................ 37
Table 5 — Class diagram notation for classes................................................................................................ 38
Table 6 — Class diagram notation for associations........................................................................................ 39
Table 7 — Class diagram notation for aggregations....................................................................................... 40
Table 8 — Class diagram notation for generalizations ................................................................................... 41
Table 9 — Class diagram notation for dependencies ..................................................................................... 42
Table 10 — Notation for objects...................................................................................................................... 42
Table 11 — Generic CDB format for 6-byte commands ................................................................................. 45
Table 12 — Typical CDB format for 6-byte commands................................................................................... 45
Table 13 — Generic CDB format for 10-byte commands ............................................................................... 46
Table 14 — Typical CDB format for 10-byte commands................................................................................. 47
Table 15 — Generic CDB format for 12-byte commands ............................................................................... 48
Table 16 — Typical CDB format for 12-byte commands................................................................................. 49
Table 17 — Generic CDB format for MAINTENANCE IN commands............................................................. 50
Table 18 — Generic CDB format for MAINTENANCE OUT commands......................................................... 50
Table 19 — Generic CDB format for SERVICE ACTION IN(12) commands .................................................. 51
Table 20 — Generic CDB format for SERVICE ACTION OUT(12) commands .............................................. 51
Table 21 — Generic CDB format for 16-byte commands ............................................................................... 52
Table 22 — Typical CDB format for 16-byte commands, if eight-byte LBAs not supported ........................... 53
Table 23 — Typical CDB format for 16-byte commands with eight-byte LBAs supported.............................. 54
Table 24 — Generic CDB format for SERVICE ACTION IN(16) commands .................................................. 55
Table 25 — Generic CDB format for SERVICE ACTION OUT(16) commands .............................................. 55
Table 26 — Generic CDB format for SERVICE ACTION BIDIRECTIONAL commands ................................ 56
Table 27 — Generic variable length CDB ....................................................................................................... 57
Table 28 — Typical variable length CDB format for 32-byte commands ........................................................ 58
Table 29 — XCDB format ............................................................................................................................... 59
Table 30 — XCDB descriptor format............................................................................................................... 60
Table 31 — EXTENSION TYPE field.................................................................................................................... 60
Table 32 — OPERATION CODE field................................................................................................................... 61
Table 33 — Code set enumeration ................................................................................................................. 63
Table 34 — Relative port identifier values ...................................................................................................... 64
Table 35 — Sense data response codes ........................................................................................................ 65
Table 36 — Descriptor format sense data ...................................................................................................... 66
Table 37 — Sense data descriptor format ...................................................................................................... 67
Table 38 — DESCRIPTOR TYPE field.................................................................................................................. 68
Table 39 — Information sense data descriptor format .................................................................................... 69
Table 40 — Command-specific information sense data descriptor format ..................................................... 70
Table 41 — Sense key specific sense data descriptor format ........................................................................ 70
Table 42 — Sense key specific information definitions................................................................................... 71
Table 43 — Field pointer sense key specific information................................................................................ 71
Table 44 — Actual retry count sense key specific information........................................................................ 72
Table 45 — Progress indication sense key specific information ..................................................................... 72
Table 46 — Segment pointer sense key specific information ......................................................................... 73
Table 47 — Unit attention condition queue overflow sense key specific information...................................... 73
Table 48 — Field replaceable unit sense data descriptor format.................................................................... 74
Table 49 — Another progress indication sense data descriptor format .......................................................... 74
Table 50 — Forwarded sense data descriptor format..................................................................................... 75
Table 51 — SENSE DATA SOURCE field ............................................................................................................. 76
Table 52 — Vendor specific sense data descriptor format ............................................................................. 76

Working Draft SCSI Primary Commands - 4 (SPC-4) xxv

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 53 — Fixed format sense data .............................................................................................................. 77

Table 54 — Sense key descriptions................................................................................................................ 81
Table 55 — ASC and ASCQ assignments...................................................................................................... 83
Table 56 — Device clock value format.......................................................................................................... 104
Table 57 — Timestamp origin value ............................................................................................................. 104
Table 58 — WRITE BUFFER download microcode modes.......................................................................... 107
Table 59 — WRITE BUFFER download microcode field processing............................................................ 108
Table 60 — MULTI I_T NEXUS MICROCODE DOWNLOAD field ............................................................................. 109
Table 61 — Identifying information types...................................................................................................... 115
Table 62 — Types of MAM attributes............................................................................................................ 116
Table 63 — MAM attribute states.................................................................................................................. 116
Table 64 — Power condition state machine states ....................................................................................... 124
Table 65 — Power condition state machine timers....................................................................................... 124
Table 66 — SPC-4 commands that are allowed in the presence of various reservations ............................ 132
Table 67 — PERSISTENT RESERVE OUT service actions that are allowed in the presence of
various reservations ................................................................................................................. 135
Table 68 — Register behaviors for a REGISTER service action .................................................................. 140
Table 69 — Register behaviors for a REGISTER AND IGNORE EXISTING KEY service action ................ 141
Table 70 — I_T Nexuses being registered.................................................................................................... 142
Table 71 — Register behaviors for a REGISTER AND MOVE service action.............................................. 143
Table 72 — Processing for a released or preempted persistent reservation ................................................ 146
Table 73 — Preempting actions.................................................................................................................... 149
Table 74 — Minimum SA parameters ........................................................................................................... 159
Table 75 — USAGE_TYPE SA parameter ................................................................................................... 161
Table 76 — Security protocols that create SAs ............................................................................................ 162
Table 77 — KDFs summary.......................................................................................................................... 163
Table 78 — HMAC-based KDFs ................................................................................................................... 164
Table 79 — Hash functions used by HMAC based on KDF_ID .................................................................... 165
Table 80 — RFC 3566 parameter translations for the KDF based on AES-XCBC-PRF-128 ....................... 165
Table 81 — IKEv2-SCSI shared key names and SA shared key names...................................................... 177
Table 82 — Shared key size determination .................................................................................................. 178
Table 83 — Device Server Capabilities step parameter data requirements ................................................. 179
Table 84 — IKEv2-SCSI command terminations that do not abandon the CCS .......................................... 191
Table 85 — Security Manager class relationships ........................................................................................ 194
Table 86 — CbCS methods .......................................................................................................................... 201
Table 87 — CbCS communications trust requirement.................................................................................. 203
Table 88 — Summary of CbCS shared keys ................................................................................................ 205
Table 89 — CbCS shared key identifier values ............................................................................................ 205
Table 90 — Associations between commands and permissions .................................................................. 211
Table 91 — Associations between security protocol commands and permissions....................................... 213
Table 92 — Summary of changeable CbCS parameters.............................................................................. 214
Table 93 — CbCS extension descriptor format............................................................................................. 215
Table 94 — ESP-SCSI data format before encryption and after decryption ................................................. 217
Table 95 — ESP-SCSI outbound data descriptors ....................................................................................... 218
Table 96 — ESP-SCSI CDBs or Data-Out Buffer parameter list descriptor without initialization vector....... 219
Table 97 — ESP-SCSI CDBs or Data-Out Buffer full parameter list descriptor............................................ 221
Table 98 — ESP-SCSI Data-Out Buffer parameter list descriptor without length and initialization vector ... 222
Table 99 — ESP-SCSI Data-Out Buffer parameter list descriptor without length......................................... 223
Table 100 — ESP-SCSI Data-In Buffer parameter data descriptors ............................................................ 224
Table 101 — ESP-SCSI Data-In Buffer parameter data descriptor without initialization vector ................... 225
Table 102 — ESP-SCSI Data-In Buffer full parameter data descriptor......................................................... 227
Table 103 — ESP-SCSI Data-In Buffer parameter data descriptor without length and initialization vector.. 228
Table 104 — ESP-SCSI Data-In Buffer parameter data descriptor without length ....................................... 229
Table 105 — Security algorithm codes ......................................................................................................... 230

xxvi Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 106 — Exception commands for background self-tests...................................................................... 234

Table 107 — Self-test mode summary.......................................................................................................... 236
Table 108 — Third-party copy commands .................................................................................................... 248
Table 109 — Mandatory copy manager command support requirements .................................................... 249
Table 110 — Responses to the conditions that result from SCSI events ..................................................... 254
Table 111 — ROD types ............................................................................................................................... 256
Table 112 — ROD token format.................................................................................................................... 260
Table 113 — Generic ROD token format ...................................................................................................... 262
Table 114 — ROD TYPE field in generic ROD ................................................................................................ 263
Table 115 — Generic ROD token errors sorted by reporting importance ..................................................... 266
Table 116 — Copy manager relationships for processing ROD tokens........................................................ 267
Table 117 — Segment descriptor type specific copy manager processing requirements ............................ 271
Table 118 — PAD and CAT bit definitions ....................................................................................................... 273
Table 119 — PAD bit processing if there is no copy source or copy destination ........................................... 274
Table 120 — Commands for all device types ............................................................................................... 280
Table 121 — CHANGE ALIASES command ................................................................................................ 282
Table 122 — CHANGE ALIASES parameter list .......................................................................................... 283
Table 123 — Alias entry format..................................................................................................................... 284
Table 124 — Alias entry PROTOCOL IDENTIFIER field ...................................................................................... 284
Table 125 — Protocol independent alias entry FORMAT CODE field ............................................................... 285
Table 126 — COPY OPERATION ABORT command .................................................................................. 286
Table 127 — EXTENDED COPY(LID4) command ....................................................................................... 287
Table 128 — EXTENDED COPY(LID4) parameter list ................................................................................. 288
Table 129 — PARAMETER LIST FORMAT field ................................................................................................... 289
Table 130 — LIST ID USAGE field for the EXTENDED COPY(LID4) command .............................................. 291
Table 131 — LIST ID USAGE field for the EXTENDED COPY(LID1) command .............................................. 292
Table 132 — EXTENDED COPY descriptor type codes............................................................................... 294
Table 133 — EXTENDED COPY CSCD descriptor type codes ................................................................... 295
Table 134 — CSCD descriptor format .......................................................................................................... 296
Table 135 — LU ID TYPE field ......................................................................................................................... 296
Table 136 — Device type specific parameters in CSCD descriptors ............................................................ 297
Table 137 — CSCD descriptor extension format .......................................................................................... 298
Table 138 — Device type specific CSCD descriptor parameters for block device types .............................. 298
Table 139 — Device type specific CSCD descriptor parameters for sequential-access device types.......... 299
Table 140 — Stream device transfer lengths................................................................................................ 299
Table 141 — Device type specific CSCD descriptor parameters for processor device types....................... 300
Table 142 — Identification Descriptor CSCD descriptor format.................................................................... 301
Table 143 — Alias CSCD descriptor format.................................................................................................. 302
Table 144 — IP Copy Service CSCD descriptor format................................................................................ 303
Table 145 — ROD CSCD descriptor format ................................................................................................. 305
Table 146 — Inputs that affect the processing of the ROD PRODUCER CSCD DESCRIPTOR ID field .................. 307
Table 147 — DEL_TKN bit processing ............................................................................................................ 309
Table 148 — EXTENDED COPY segment descriptor type codes................................................................ 310
Table 149 — Segment descriptor header ..................................................................................................... 312
Table 150 — CSCD descriptor ID values...................................................................................................... 313
Table 151 — Block device to stream device segment descriptor ................................................................. 314
Table 152 — Stream device to block device segment descriptor ................................................................. 315
Table 153 — Block device to block device segment descriptor .................................................................... 317
Table 154 — Stream device to stream device segment descriptor............................................................... 319
Table 155 — Inline data to stream device segment descriptor ..................................................................... 321
Table 156 — Embedded data to stream device segment descriptor ............................................................ 322
Table 157 — Stream device to discard segment descriptor ......................................................................... 324
Table 158 — Verify CSCD segment descriptor............................................................................................. 325
Table 159 — Block device with offset to stream device segment descriptor ................................................ 327

Working Draft SCSI Primary Commands - 4 (SPC-4) xxvii

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 160 — Stream device with offset to block device segment descriptor ................................................ 329
Table 161 — Block device with offset to block device with offset segment descriptor.................................. 331
Table 162 — Write filemarks segment descriptor ......................................................................................... 332
Table 163 — Space segment descriptor....................................................................................................... 333
Table 164 — Locate segment descriptor ...................................................................................................... 334
Table 165 — Tape device image copy segment descriptor .......................................................................... 335
Table 166 — Register persistent reservation key segment descriptor.......................................................... 336
Table 167 — Third party persistent reservations source I_T nexus segment descriptor .............................. 338
Table 168 — Block device image copy segment descriptor ......................................................................... 339
Table 169 — Populate a ROD from one or more block ranges segment descriptor..................................... 341
Table 170 — RANGE DESCRIPTOR TYPE field .................................................................................................. 342
Table 171 — Populate a ROD four gibi-block range descriptor format......................................................... 342
Table 172 — Populate a ROD from one block range segment descriptor .................................................... 343
Table 173 — EXTENDED COPY(LID1) command ....................................................................................... 344
Table 174 — EXTENDED COPY(LID1) parameter list ................................................................................. 345
Table 175 — INQUIRY command................................................................................................................. 347
Table 176 — Standard INQUIRY data format............................................................................................... 348
Table 177 — PERIPHERAL QUALIFIER field....................................................................................................... 350
Table 178 — Peripheral device type ............................................................................................................. 350
Table 179 — VERSION field ............................................................................................................................ 351
Table 180 — RESPONSE DATA FORMAT field ................................................................................................... 352
Table 181 — TPGS field ................................................................................................................................. 352
Table 182 — Version descriptor values ........................................................................................................ 354
Table 183 — SPI-specific standard INQUIRY bits ........................................................................................ 366
Table 184 — Maximum logical device configuration table ............................................................................ 366
Table 185 — CLOCKING field .......................................................................................................................... 367
Table 186 — LOG SELECT command ......................................................................................................... 368
Table 187 — Page control (PC) field ............................................................................................................. 369
Table 188 — PAGE CODE field and SUBPAGE CODE field ................................................................................. 370
Table 189 — PCR bit, SP bit, and PC field meanings when parameter list length is zero ............................... 370
Table 190 — LOG SENSE command ........................................................................................................... 373
Table 191 — MANAGEMENT PROTOCOL IN command ............................................................................ 375
Table 192 — MANAGEMENT PROTOCOL field in MANAGEMENT PROTOCOL IN command .......................... 375
Table 193 — MANAGEMENT PROTOCOL SPECIFIC2 field for MANAGEMENT PROTOCOL IN protocol 00h ..... 376
Table 194 — Supported management protocols MANAGEMENT PROTOCOL IN parameter data ............ 377
Table 195 — MANAGEMENT PROTOCOL OUT command ........................................................................ 378
Table 196 — MANAGEMENT PROTOCOL field in MANAGEMENT PROTOCOL OUT command ...................... 378
Table 197 — MODE SELECT(6) command.................................................................................................. 379
Table 198 — MODE SELECT(10) command................................................................................................ 381
Table 199 — MODE SENSE(6) command ................................................................................................... 382
Table 200 — Page control (PC) field ............................................................................................................. 382
Table 201 — Mode page code usage in MODE SENSE commands for all devices..................................... 383
Table 202 — MODE SENSE(10) command ................................................................................................. 385
Table 203 — PERSISTENT RESERVE IN command .................................................................................. 386
Table 204 — PERSISTENT RESERVE IN service action codes.................................................................. 386
Table 205 — PERSISTENT RESERVE IN parameter data for READ KEYS ............................................... 387
Table 206 — Format of PERSISTENT RESERVE IN parameter data for READ RESERVATION with
no reservation held ................................................................................................................... 388
Table 207 — Format of PERSISTENT RESERVE IN parameter data for READ RESERVATION with
a reservation held ..................................................................................................................... 389
Table 208 — Persistent reservation SCOPE field ........................................................................................... 390
Table 209 — Persistent reservation TYPE field.............................................................................................. 391
Table 210 — PERSISTENT RESERVE IN parameter data for REPORT CAPABILITIES ........................... 392
Table 211 — ALLOW COMMANDS field............................................................................................................. 393

xxviii Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 212 — Persistent Reservation Type Mask format............................................................................... 395

Table 213 — PERSISTENT RESERVE IN parameter data for READ FULL STATUS................................. 396
Table 214 — PERSISTENT RESERVE IN full status descriptor format ....................................................... 397
Table 215 — PERSISTENT RESERVE OUT command .............................................................................. 398
Table 216 — PERSISTENT RESERVE OUT service action codes.............................................................. 400
Table 217 — PERSISTENT RESERVE OUT service actions and valid parameters (part 1 of 2) ................ 401
Table 218 — PERSISTENT RESERVE OUT parameter list ........................................................................ 403
Table 219 — PERSISTENT RESERVE OUT specify initiator ports additional parameter data.................... 405
Table 220 — PERSISTENT RESERVE OUT with REGISTER AND MOVE service action parameter list .. 406
Table 221 — READ ATTRIBUTE command................................................................................................. 408
Table 222 — READ ATTRIBUTE service action codes ................................................................................ 409
Table 223 — Status to be returned if medium auxiliary memory is not accessible....................................... 410
Table 224 — READ ATTRIBUTE with ATTRIBUTE VALUES service action parameter data format .......... 411
Table 225 — READ ATTRIBUTE with ATTRIBUTE LIST service action parameter data format ................. 412
Table 226 — READ ATTRIBUTE with LOGICAL VOLUME LIST service action parameter data format ..... 412
Table 227 — READ ATTRIBUTE with PARTITION LIST service action parameter data format.................. 413
Table 228 — READ ATTRIBUTE with SUPPORTED ATTRIBUTES service action parameter data format 414
Table 229 — READ BUFFER command ...................................................................................................... 415
Table 230 — READ BUFFER MODE field ...................................................................................................... 415
Table 231 — READ BUFFER descriptor ...................................................................................................... 416
Table 232 — OFFSET BOUNDARY field ............................................................................................................ 417
Table 233 — Echo buffer descriptor ............................................................................................................. 418
Table 234 — Error history BUFFER ID field ..................................................................................................... 419
Table 235 — Summary of error history directory device server actions ....................................................... 420
Table 236 — Error history directory .............................................................................................................. 420
Table 237 — EHS_RETRIEVED field................................................................................................................. 421
Table 238 — EHS_SOURCE field..................................................................................................................... 421
Table 239 — Error history directory entry ..................................................................................................... 422
Table 240 — READ MEDIA SERIAL NUMBER command ........................................................................... 423
Table 241 — READ MEDIA SERIAL NUMBER parameter data format ....................................................... 423
Table 242 — RECEIVE COPY DATA(LID4) command ................................................................................ 424
Table 243 — Parameter data for the RECEIVE COPY DATA(LID4) command ........................................... 426
Table 244 — RECEIVE COPY DATA(LID1) command ................................................................................ 427
Table 245 — Parameter data for the RECEIVE COPY DATA(LID1) command ........................................... 428
Table 246 — RECEIVE COPY OPERATING PARAMETERS command..................................................... 429
Table 247 — Parameter data for the RECEIVE COPY OPERATING PARAMETERS command ................ 429
Table 248 — RECEIVE COPY FAILURE DETAILS(LID1) command........................................................... 432
Table 249 — Parameter data for the RECEIVE COPY FAILURE DETAILS(LID1) command...................... 433
Table 250 — RECEIVE COPY STATUS(LID4) command............................................................................ 435
Table 251 — Parameter data for the RECEIVE COPY STATUS(LID4) command....................................... 436
Table 252 — COPY OPERATION STATUS field................................................................................................... 437
Table 253 — EXTENDED COPY COMPLETION STATUS field contents based on COPY OPERATION STATUS field .. 438
Table 254 — COPY STATUS TRANSFER COUNT UNITS field .......................................................................... 438
Table 255 — RECEIVE COPY STATUS(LID1) command............................................................................ 439
Table 256 — Parameter data for the RECEIVE COPY STATUS(LID1) command....................................... 440
Table 257 — COPY COMMAND STATUS field .................................................................................................... 440
Table 258 — RECEIVE CREDENTIAL command ........................................................................................ 441
Table 259 — RECEIVE CREDENTIAL command unencrypted bytes format............................................... 442
Table 260 — CREDENTIAL REQUEST TYPE field ............................................................................................... 442
Table 261 — CbCS logical unit credential request descriptor format ........................................................... 443
Table 262 — CbCS logical unit and volume credential request descriptor format........................................ 443
Table 263 — CbCS credential format ........................................................................................................... 444
Table 264 — Credential format values.......................................................................................................... 445
Table 265 — CbCS capability descriptor format ........................................................................................... 446

Working Draft SCSI Primary Commands - 4 (SPC-4) xxix

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 266 — DESIGNATION TYPE field............................................................................................................. 446

Table 267 — CBCS METHOD field.................................................................................................................... 447
Table 268 — PERMISSIONS BIT MASK field format ........................................................................................... 447
Table 269 — Logical unit designation descriptor format ............................................................................... 449
Table 270 — Volume designation descriptor format ..................................................................................... 449
Table 271 — RECEIVE DIAGNOSTIC RESULTS command ....................................................................... 450
Table 272 — RECEIVE ROD TOKEN INFORMATION command ............................................................... 451
Table 273 — Parameter data for the RECEIVE ROD TOKEN INFORMATION command .......................... 452
Table 274 — ROD token descriptor format................................................................................................... 453
Table 276 — REMOVE I_T NEXUS parameter list format ........................................................................... 454
Table 275 — REMOVE I_T NEXUS command............................................................................................. 454
Table 277 — I_T nexus descriptor ................................................................................................................ 455
Table 278 — REPORT ALIASES command................................................................................................. 456
Table 279 — REPORT ALIASES parameter data ........................................................................................ 457
Table 280 — REPORT ALL ROD TOKENS command................................................................................. 458
Table 281 — Parameter data for the REPORT ALL ROD TOKENS command............................................ 459
Table 282 — REPORT IDENTIFYING INFORMATION command............................................................... 460
Table 283 — IDENTIFYING INFORMATION TYPE field ......................................................................................... 460
Table 284 — Peripheral device identifying information parameter data ....................................................... 461
Table 285 — Identifying information supported parameter data ................................................................... 461
Table 286 — Identifying information descriptor............................................................................................. 462
Table 287 — REPORT LUNS command ...................................................................................................... 463
Table 288 — SELECT REPORT field................................................................................................................. 463
Table 289 — REPORT LUNS parameter data format .................................................................................. 465
Table 290 — REPORT PRIORITY command............................................................................................... 466
Table 291 — PRIORITY REPORTED field .......................................................................................................... 466
Table 292 — REPORT PRIORITY parameter data format ........................................................................... 467
Table 293 — Priority descriptor format ......................................................................................................... 467
Table 294 — REPORT SUPPORTED OPERATION CODES command ..................................................... 468
Table 295 — REPORT SUPPORTED OPERATION CODES REPORTING OPTIONS field............................... 469
Table 296 — All_commands parameter data................................................................................................ 470
Table 297 — Command descriptor format .................................................................................................... 471
Table 298 — One_command parameter data............................................................................................... 472
Table 299 — SUPPORT values ....................................................................................................................... 472
Table 300 — Command timeouts descriptor format ..................................................................................... 474
Table 301 — REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS command .............................. 475
Table 302 — REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS basic parameter data ............ 476
Table 303 — REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS extended parameter data ...... 476
Table 304 — REPORT TARGET PORT GROUPS command...................................................................... 479
Table 305 — PARAMETER DATA FORMAT field ................................................................................................. 479
Table 306 — Length only header parameter data format ............................................................................. 480
Table 307 — Extended header parameter data format................................................................................. 481
Table 308 — Target port group descriptor format......................................................................................... 482
Table 309 — ASYMMETRIC ACCESS STATE field............................................................................................... 482
Table 310 — STATUS CODE field .................................................................................................................... 483
Table 311 — Target port descriptor format ................................................................................................... 484
Table 312 — REPORT TIMESTAMP command........................................................................................... 484
Table 313 — REPORT TIMESTAMP parameter data format ....................................................................... 485
Table 314 — REQUEST SENSE command ................................................................................................. 485
Table 315 — DESC bit.................................................................................................................................... 486
Table 316 — SECURITY PROTOCOL IN command.................................................................................... 488
Table 317 — SECURITY PROTOCOL field in SECURITY PROTOCOL IN command........................................ 489
Table 318 — SECURITY PROTOCOL OUT command................................................................................ 490
Table 319 — SECURITY PROTOCOL field in SECURITY PROTOCOL OUT command.................................... 491

xxx Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 320 — SEND DIAGNOSTIC command .............................................................................................. 492

Table 321 — SELF-TEST CODE field ................................................................................................................ 493
Table 322 — The meanings of the SELF-TEST CODE field, the PF bit, the SELFTEST bit, and the
PARAMETER LIST LENGTH field .................................................................................................... 495
Table 323 — SET IDENTIFYING INFORMATION command....................................................................... 499
Table 324 — IDENTIFYING INFORMATION TYPE field ......................................................................................... 500
Table 325 — SET IDENTIFYING INFORMATION parameter list................................................................. 500
Table 326 — SET PRIORITY command....................................................................................................... 501
Table 327 — I_T_L NEXUS TO SET field .......................................................................................................... 502
Table 328 — SET PRIORITY parameter list format...................................................................................... 503
Table 329 — SET TARGET PORT GROUPS command.............................................................................. 504
Table 330 — SET TARGET PORT GROUPS parameter list format ............................................................ 505
Table 331 — Set target port group descriptor parameter list ........................................................................ 505
Table 332 — ASYMMETRIC ACCESS STATE field............................................................................................... 506
Table 333 — SET TIMESTAMP command................................................................................................... 507
Table 334 — SET TIMESTAMP parameter list format.................................................................................. 508
Table 335 — TEST UNIT READY command................................................................................................ 508
Table 336 — Preferred TEST UNIT READY responses ............................................................................... 509
Table 337 — WRITE ATTRIBUTE command ............................................................................................... 510
Table 338 — WRITE ATTRIBUTE parameter list format .............................................................................. 511
Table 339 — WRITE BUFFER command..................................................................................................... 513
Table 340 — WRITE BUFFER MODE field .................................................................................................... 514
Table 341 — MODE SPECIFIC field .................................................................................................................. 517
Table 342 — Application client error history parameter list format ............................................................... 519
Table 343 — ERROR TYPE field ...................................................................................................................... 520
Table 344 — ERROR LOCATION FORMAT field.................................................................................................. 521
Table 345 — Summary of diagnostic page codes ........................................................................................ 522
Table 346 — Diagnostic page format............................................................................................................ 523
Table 347 — Protocol Specific diagnostic page............................................................................................ 524
Table 348 — Supported Diagnostic Pages diagnostic page......................................................................... 524
Table 349 — Summary of log page codes.................................................................................................... 526
Table 350 — Log page format ...................................................................................................................... 527
Table 351 — LOG SELECT PCR bit, SP bit, and DS bit meanings when parameter list length is not zero .... 528
Table 352 — Log parameter ......................................................................................................................... 529
Table 353 — Threshold met criteria (TMC) field............................................................................................. 531
Table 354 — FORMAT AND LINKING field ......................................................................................................... 531
Table 355 — Parameter control byte values for bounded data counter parameters .................................... 532
Table 356 — Parameter control byte values for unbounded data counter parameters ................................ 533
Table 357 — Parameter control byte values for ASCII format list log parameters........................................ 534
Table 358 — Parameter control byte values for binary format list log parameters ....................................... 535
Table 359 — Keywords for resetting or changing log parameter cumulative values .................................... 536
Table 360 — Application Client log page parameter codes .......................................................................... 536
Table 361 — Application Client log page ...................................................................................................... 537
Table 362 — General Usage Application Client log parameter .................................................................... 537
Table 363 — Buffer Over-Run/Under-Run log page parameter codes ......................................................... 538
Table 364 — Buffer Over-Run/Under-Run log page ..................................................................................... 540
Table 365 — Buffer Over-run/Under-run log parameter ............................................................................... 540
Table 366 — Cache Memory Statistics log page parameter codes .............................................................. 541
Table 367 — Cache Memory Statistics log page commands ....................................................................... 542
Table 368 — Cache Memory Statistics log page .......................................................................................... 542
Table 369 — Read Cache Memory Hits log parameter ................................................................................ 543
Table 370 — Reads To Cache Memory log parameter ................................................................................ 544
Table 371 — Write Cache Memory Hits log parameter ................................................................................ 545
Table 372 — Writes From Cache Memory log parameter ............................................................................ 546

Working Draft SCSI Primary Commands - 4 (SPC-4) xxxi

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 373 — Time From Last Hard Reset log parameter ............................................................................. 547
Table 374 — Time Interval log parameter..................................................................................................... 548
Table 375 — Time interval descriptor ........................................................................................................... 548
Table 376 — General Statistics and Performance log page parameter codes ............................................. 549
Table 377 — Statistics and Performance log pages commands .................................................................. 550
Table 378 — General Statistics and Performance log page ......................................................................... 550
Table 379 — General Access Statistics and Performance log parameter .................................................... 551
Table 380 — Idle Time log parameter........................................................................................................... 553
Table 381 — Force Unit Access Statistics and Performance log parameter ................................................ 554
Table 382 — Group Statistics and Performance log page parameter codes................................................ 555
Table 383 — Group Statistics and Performance (n) log page ...................................................................... 556
Table 384 — Group Statistics and Performance (n) subpage codes............................................................ 557
Table 385 — Group n Statistics and Performance log parameter ................................................................ 559
Table 386 — Group n Force Unit Access Statistics and Performance log parameter .................................. 561
Table 387 — Informational Exceptions log page parameter codes .............................................................. 562
Table 388 — Informational Exceptions log page .......................................................................................... 563
Table 389 — Informational Exceptions General log parameter .................................................................... 563
Table 390 — Last n Deferred Errors or Asynchronous Events log page parameter codes .......................... 564
Table 391 — Last n Deferred Errors or Asynchronous Events log page ...................................................... 565
Table 392 — Deferred Error or Asynchronous Event log parameter ............................................................ 566
Table 393 — Last n Error Events log page parameter codes ....................................................................... 566
Table 394 — Last n Error Events log page ................................................................................................... 567
Table 395 — Error Event log parameter ....................................................................................................... 568
Table 396 — Non-Medium Error log page parameter codes ........................................................................ 568
Table 397 — Non-Medium Error log page .................................................................................................... 569
Table 398 — Non-Medium Error Count log parameter ................................................................................. 569
Table 399 — Power Conditions Transitions log page parameter codes ....................................................... 570
Table 400 — Power Condition Transitions log page..................................................................................... 571
Table 401 — Accumulated Transitions log parameter .................................................................................. 571
Table 402 — Accumulated Transitions parameter codes and saturating counters....................................... 572
Table 403 — Protocol Specific Port log page ............................................................................................... 573
Table 404 — Generic protocol specific port log parameter........................................................................... 573
Table 405 — Read Error Counters log page parameter codes..................................................................... 574
Table 406 — Read Error Counters log page................................................................................................. 575
Table 407 — Read Error Counter log parameter .......................................................................................... 575
Table 408 — Read Reverse Error Counters log page parameter codes ...................................................... 576
Table 409 — Read Reverse Error Counters log page .................................................................................. 577
Table 410 — Read Reverse Error Counter log parameter............................................................................ 577
Table 411 — Self-Test Results log page parameter codes .......................................................................... 578
Table 412 — Self-Test Results log page ...................................................................................................... 578
Table 413 — Unused Self-Test Results log parameter................................................................................. 579
Table 414 — Self-Test Results log parameter .............................................................................................. 580
Table 415 — SELF-TEST RESULTS field ........................................................................................................... 581
Table 416 — Start-Stop Cycle Counter log page parameter codes.............................................................. 582
Table 417 — Start-Stop Cycle Counter log page.......................................................................................... 582
Table 418 — Date of Manufacture log parameter......................................................................................... 583
Table 419 — Accounting Date log parameter ............................................................................................... 584
Table 420 — Specified Cycle Count Over Device Lifetime log parameter.................................................... 585
Table 421 — Accumulated Start-Stop Cycles log parameter........................................................................ 585
Table 422 — Specified Load-Unload Count Over Device Lifetime log parameter ........................................ 586
Table 423 — Accumulated Load-Unload Cycles log parameter ................................................................... 587
Table 424 — Supported Log Pages log page ............................................................................................... 588
Table 425 — Supported page descriptor ...................................................................................................... 588
Table 426 — Supported Log Pages and Subpages log page....................................................................... 589

xxxii Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 427 — Supported page/subpage descriptor ....................................................................................... 589

Table 428 — Supported Subpages log page ................................................................................................ 590
Table 429 — Supported subpage descriptor ................................................................................................ 590
Table 430 — Temperature log page parameter codes ................................................................................. 591
Table 431 — Temperature log page ............................................................................................................. 591
Table 432 — Temperature log parameter..................................................................................................... 592
Table 433 — Reference Temperature log parameter ................................................................................... 592
Table 434 — Verify Error Counters log page parameter codes .................................................................... 594
Table 435 — Verify Error Counters log page ................................................................................................ 594
Table 436 — Verify Error Counter log parameter ......................................................................................... 595
Table 437 — Write Error Counters log page parameter codes..................................................................... 596
Table 438 — Write Error Counters log page................................................................................................. 596
Table 439 — Write Error Counter log parameter .......................................................................................... 597
Table 440 — MAM ATTRIBUTE format ........................................................................................................ 598
Table 441 — MAM attribute FORMAT field ..................................................................................................... 598
Table 442 — MAM attribute identifier range assignments ............................................................................ 599
Table 443 — Device type attributes .............................................................................................................. 599
Table 444 — DEVICE VENDOR/SERIAL NUMBER attribute format ........................................................... 601
Table 445 — MEDIUM USAGE HISTORY attribute format .......................................................................... 603
Table 446 — PARTITION USAGE HISTORY attribute format...................................................................... 605
Table 447 — Medium type attributes ............................................................................................................ 608
Table 448 — MEDIUM TYPE and MEDIUM TYPE INFORMATION attributes............................................. 609
Table 449 — Host type attributes.................................................................................................................. 609
Table 450 — TEXT LOCALIZATION IDENTIFIER attribute values .............................................................. 611
Table 451 — Summary of mode page codes................................................................................................ 613
Table 452 — Mode page policies.................................................................................................................. 614
Table 453 — Mode parameter list................................................................................................................. 614
Table 454 — Mode parameter header(6)...................................................................................................... 615
Table 455 — Mode parameter header(10).................................................................................................... 615
Table 456 — General mode parameter block descriptor .............................................................................. 616
Table 457 — Page_0 mode page format ...................................................................................................... 617
Table 458 — Sub_page mode page format .................................................................................................. 617
Table 459 — Control mode page .................................................................................................................. 618
Table 460 — Task set type (TST) field........................................................................................................... 619
Table 461 — QUEUE ALGORITHM MODIFIER field.............................................................................................. 620
Table 462 — Queue error management (QERR) field ................................................................................... 620
Table 463 — Unit attention interlocks control (UA_INTLCK_CTRL) field........................................................... 621
Table 464 — AUTOLOAD MODE field................................................................................................................ 622
Table 465 — Control Extension mode page ................................................................................................. 623
Table 466 — Disconnect-Reconnect mode page ......................................................................................... 625
Table 467 — Data transfer disconnect control (DTDC) field........................................................................... 627
Table 468 — Extended mode page .............................................................................................................. 627
Table 469 — Extended Device-Type Specific mode page............................................................................ 628
Table 470 — Power Condition mode page ................................................................................................... 629
Table 471 — PM_BG_PRECEDENCE field......................................................................................................... 630
Table 472 — CCF IDLE field............................................................................................................................ 632
Table 473 — CCF STANDBY field .................................................................................................................... 632
Table 474 — CCF STOPPED field .................................................................................................................... 633
Table 475 — Power Consumption mode page ............................................................................................. 633
Table 476 — Protocol Specific Logical Unit mode page ............................................................................... 634
Table 477 — Page_0 mode page format Protocol Specific Port mode page................................................ 635
Table 478 — Sub_page mode page format Protocol Specific Port mode page............................................ 635
Table 479 — PROTOCOL IDENTIFIER field values ............................................................................................ 637
Table 480 — Fibre Channel alias entry format codes................................................................................... 638

Working Draft SCSI Primary Commands - 4 (SPC-4) xxxiii

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 481 — Fibre Channel world wide port name alias entry format .......................................................... 638
Table 482 — Fibre Channel world wide port name with N_Port checking alias entry format ....................... 639
Table 483 — RDMA alias entry format codes............................................................................................... 640
Table 484 — RDMA target port identifier alias entry format ......................................................................... 641
Table 485 — InfiniBand global identifier with target port identifier checking alias entry format .................... 642
Table 486 — iSCSI alias entry format codes ................................................................................................ 643
Table 487 — iSCSI name alias entry format................................................................................................. 644
Table 488 — iSCSI name with binary IPv4 address alias entry format......................................................... 645
Table 489 — iSCSI name with IPname alias entry format ............................................................................ 647
Table 490 — iSCSI name with binary IPv6 address alias entry format......................................................... 649
Table 491 — Fibre Channel N_Port_Name CSCD descriptor format ........................................................... 651
Table 492 — Fibre Channel N_Port_ID CSCD descriptor format ................................................................. 652
Table 493 — Fibre Channel N_Port_ID With N_Port_Name Checking CSCD descriptor format ................. 653
Table 494 — SCSI Parallel T_L CSCD descriptor format............................................................................. 654
Table 495 — IEEE 1394 EUI-64 CSCD descriptor format ............................................................................ 655
Table 496 — RDMA CSCD descriptor format............................................................................................... 656
Table 497 — iSCSI IPv4 CSCD descriptor format ........................................................................................ 657
Table 498 — iSCSI IPv6 CSCD descriptor format ........................................................................................ 658
Table 499 — SAS Serial SCSI Protocol CSCD descriptor format ................................................................ 659
Table 500 — TransportID format .................................................................................................................. 660
Table 501 — TransportID formats for specific SCSI transport protocols ...................................................... 660
Table 502 — Fibre Channel TransportID format........................................................................................... 661
Table 503 — Parallel SCSI bus TransportID format ..................................................................................... 662
Table 504 — IEEE 1394 TransportID format ................................................................................................ 663
Table 505 — RDMA TransportID format....................................................................................................... 663
Table 506 — iSCSI TPID FORMAT field codes ............................................................................................... 664
Table 507 — iSCSI initiator device TransportID format ................................................................................ 664
Table 508 — iSCSI initiator port TransportID format .................................................................................... 665
Table 509 — SAS Serial SCSI Protocol TransportID format ........................................................................ 666
Table 510 — SOP TransportID format.......................................................................................................... 666
Table 511 — SECURITY PROTOCOL SPECIFIC field for SECURITY PROTOCOL IN protocol 00h .................... 667
Table 512 — Supported security protocols SECURITY PROTOCOL IN parameter data............................. 668
Table 513 — Certificate data SECURITY PROTOCOL IN parameter data .................................................. 669
Table 514 — Security compliance information SECURITY PROTOCOL IN parameter data ....................... 670
Table 515 — Compliance descriptor format.................................................................................................. 671
Table 516 — COMPLIANCE DESCRIPTOR TYPE field.......................................................................................... 671
Table 517 — FIPS 140 compliance descriptor.............................................................................................. 672
Table 518 — RELATED STANDARD field ........................................................................................................... 672
Table 519 — SECURITY PROTOCOL SPECIFIC field for the SA creation capabilities ......................................... 674
Table 520 — Supported device server capabilities formats parameter data ................................................ 674
Table 521 — IKEv2-SCSI device server capabilities parameter data........................................................... 675
Table 522 — SECURITY PROTOCOL SPECIFIC field as defined by the IKEv2-SCSI SECURITY PROTOCOL
IN command ............................................................................................................................. 676
Table 523 — SECURITY PROTOCOL SPECIFIC field as defined by the IKEv2-SCSI SECURITY PROTOCOL
OUT command ......................................................................................................................... 677
Table 524 — IKEv2-SCSI SECURITY PROTOCOL OUT command and SECURITY PROTOCOL IN
command parameter data ........................................................................................................ 678
Table 525 — IKEv2-SCSI header checking of SAIs ..................................................................................... 680
Table 526 — NEXT PAYLOAD field................................................................................................................... 681
Table 527 — MESSAGE ID field ....................................................................................................................... 682
Table 528 — Next payload values in SECURITY PROTOCOL OUT/IN parameter data ............................. 683
Table 529 — IKEv2-SCSI payload format..................................................................................................... 686
Table 530 — Key Exchange payload format................................................................................................. 687
Table 531 — Identification payload format.................................................................................................... 688

xxxiv Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 532 — ID TYPE field.............................................................................................................................. 689

Table 533 — Certificate payload format........................................................................................................ 690
Table 534 — CERTIFICATE ENCODING field...................................................................................................... 690
Table 535 — Certificate Request payload format ......................................................................................... 691
Table 536 — Authentication payload format ................................................................................................. 692
Table 537 — Nonce payload format ............................................................................................................. 695
Table 538 — Notify payload format............................................................................................................... 696
Table 539 — Delete payload format ............................................................................................................. 697
Table 540 — Encrypted payload format........................................................................................................ 699
Table 541 — Plaintext format for Encrypted payload CIPHERTEXT field......................................................... 701
Table 542 — IKEv2-SCSI SA Creation Capabilities payload format............................................................. 704
Table 543 — IKEv2-SCSI SA Cryptographic Algorithms payload format ..................................................... 705
Table 544 — IKEv2-SCSI SAUT Cryptographic Algorithms payload format................................................. 707
Table 545 — IKEv2-SCSI Timeout Values payload format........................................................................... 709
Table 546 — IKEv2-SCSI cryptographic algorithm descriptor format ........................................................... 710
Table 547 — ALGORITHM TYPE field ............................................................................................................... 710
Table 548 — ENCR IKEv2-SCSI cryptographic algorithm descriptor format................................................ 711
Table 549 — ENCR ALGORITHM IDENTIFIER field............................................................................................ 712
Table 550 — PRF IKEv2-SCSI cryptographic algorithm descriptor format................................................... 713
Table 551 — PRF ALGORITHM IDENTIFIER field............................................................................................... 714
Table 552 — INTEG IKEv2-SCSI cryptographic algorithm descriptor format ............................................... 715
Table 553 — INTEG ALGORITHM IDENTIFIER field ........................................................................................... 715
Table 554 — D-H IKEv2-SCSI cryptographic algorithm descriptor format.................................................... 716
Table 555 — D-H ALGORITHM IDENTIFIER field ............................................................................................... 717
Table 556 — SA_AUTH_OUT and SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptor format.. 718
Table 557 — SA_AUTH_OUT and SA_AUTH_IN ALGORITHM IDENTIFIER field.............................................. 719
Table 558 — IKEv2-SCSI command ordering processing requirements on a single I_T_L nexus............... 721
Table 559 — IKEv2-SCSI parameter error categories.................................................................................. 723
Table 560 — IKEv2 Notify payload error translations for IKEv2-SCSI.......................................................... 725
Table 561 — SECURITY PROTOCOL SPECIFIC field for the CbCS SECURITY PROTOCOL IN command ....... 726
Table 562 — Supported CbCS SECURITY PROTOCOL IN Pages CbCS page format .............................. 727
Table 563 — Supported CbCS SECURITY PROTOCOL OUT Pages CbCS page format .......................... 728
Table 564 — Unchangeable CbCS Parameters CbCS page format ............................................................ 728
Table 565 — KEYS SUPPORT field .................................................................................................................. 730
Table 566 — MIN CBCS METHOD SUP field ...................................................................................................... 730
Table 567 — Security Token CbCS page format.......................................................................................... 731
Table 568 — Current CbCS Parameters CbCS page format........................................................................ 732
Table 569 — Set Master Key – Seed Exchange CbCS page format............................................................ 734
Table 570 — SECURITY PROTOCOL SPECIFIC field for the CbCS SECURITY PROTOCOL OUT command ... 736
Table 571 — Set Policy Access Tag CbCS page format .............................................................................. 737
Table 572 — Set Minimum CbCS Method CbCS page format ..................................................................... 738
Table 573 — Minimum CbCS Method CbCS Parameter set ........................................................................ 738
Table 574 — Invalidate Key CbCS page format ........................................................................................... 739
Table 575 — Set Key CbCS page format ..................................................................................................... 740
Table 576 — Set Master Key – Seed Exchange CbCS page format............................................................ 741
Table 577 — Set Master Key – Change Master Key CbCS page format ..................................................... 742
Table 578 — Vital product data page codes ................................................................................................. 744
Table 579 — VPD page format ..................................................................................................................... 745
Table 580 — ASCII Information VPD page................................................................................................... 746
Table 581 — CFA Profile Information VPD page.......................................................................................... 747
Table 582 — CFA profile descriptor.............................................................................................................. 747
Table 583 — Device Constituents VPD page ............................................................................................... 748
Table 584 — Constituent descriptor.............................................................................................................. 749
Table 585 — CONSTITUENT TYPE field ............................................................................................................ 749

Working Draft SCSI Primary Commands - 4 (SPC-4) xxxv

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 586 — CONSTITUENT DEVICE TYPE field ................................................................................................ 750

Table 587 — Constituent specific descriptor format ..................................................................................... 750
Table 588 — CONSTITUENT SPECIFIC TYPE field.............................................................................................. 750
Table 589 — Device Identification VPD page ............................................................................................... 751
Table 590 — Designation descriptor............................................................................................................. 752
Table 591 — ASSOCIATION field ..................................................................................................................... 752
Table 592 — DESIGNATOR TYPE field ............................................................................................................. 753
Table 593 — Vendor specific DESIGNATOR field format ................................................................................. 755
Table 594 — T10 vendor ID based DESIGNATOR field format ........................................................................ 755
Table 595 — EUI-64 based designator lengths ............................................................................................ 756
Table 596 — EUI-64 DESIGNATOR field format............................................................................................... 756
Table 597 — EUI-64 based 12-byte DESIGNATOR field format....................................................................... 757
Table 598 — EUI-64 based 16-byte DESIGNATOR field format....................................................................... 757
Table 599 — NAA DESIGNATOR field format .................................................................................................. 758
Table 600 — Network Address Authority (NAA) field ..................................................................................... 758
Table 601 — NAA IEEE Extended DESIGNATOR field format ......................................................................... 758
Table 602 — NAA Locally Assigned DESIGNATOR field format ...................................................................... 759
Table 603 — NAA IEEE Registered DESIGNATOR field format....................................................................... 759
Table 604 — NAA IEEE Registered Extended DESIGNATOR field format....................................................... 760
Table 605 — Relative target port DESIGNATOR field format ........................................................................... 761
Table 606 — Target port group DESIGNATOR field format .............................................................................. 761
Table 607 — Logical unit group DESIGNATOR field format ............................................................................. 762
Table 608 — MD5 logical unit DESIGNATOR field format ................................................................................ 762
Table 609 — MD5 logical unit identifier example available data................................................................... 763
Table 610 — Example MD5 input for computation of a logical unit identifier................................................ 763
Table 611 — SCSI name string DESIGNATOR field format.............................................................................. 763
Table 612 — Protocol specific port designator formats ................................................................................ 764
Table 613 — USB target port identifier DESIGNATOR field format .................................................................. 765
Table 614 — PCI Express routing ID DESIGNATOR field format ..................................................................... 765
Table 615 — Extended INQUIRY Data VPD page ....................................................................................... 766
Table 616 — ACTIVATE MICROCODE field ........................................................................................................ 767
Table 617 — SPT field for peripheral device type 00h ................................................................................... 767
Table 618 — SPT field for peripheral device type 01h ................................................................................... 768
Table 619 — Management Network Addresses VPD page .......................................................................... 770
Table 620 — Network service descriptor format ........................................................................................... 771
Table 621 — SERVICE TYPE field .................................................................................................................... 771
Table 622 — Mode Page Policy VPD page .................................................................................................. 772
Table 623 — Mode page policy descriptor.................................................................................................... 772
Table 624 — MODE PAGE POLICY field............................................................................................................ 773
Table 625 — Power Condition VPD page..................................................................................................... 774
Table 626 — Power Consumption VPD page............................................................................................... 776
Table 627 — Power consumption descriptor format ..................................................................................... 776
Table 628 — POWER CONSUMPTION UNITS field .............................................................................................. 777
Table 629 — Protocol Specific Logical Unit Information VPD page.............................................................. 777
Table 630 — Logical unit information descriptor........................................................................................... 778
Table 631 — Protocol Specific Port Information VPD page.......................................................................... 779
Table 632 — Port information descriptor ...................................................................................................... 780
Table 633 — SCSI Ports VPD page ............................................................................................................. 781
Table 634 — SCSI port designation descriptor............................................................................................. 782
Table 635 — Target port descriptor .............................................................................................................. 783
Table 636 — Software Interface Identification VPD page............................................................................. 784
Table 637 — Software interface identifier format.......................................................................................... 784
Table 638 — Supported VPD Pages VPD page ........................................................................................... 785
Table 639 — Third-party Copy VPD page .................................................................................................... 786

xxxvi Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 640 — Third-party copy descriptor format........................................................................................... 786

Table 641 — Third-party copy descriptor type codes ................................................................................... 787
Table 642 — Supported Commands third-party copy descriptor format....................................................... 788
Table 643 — Command support descriptor format ....................................................................................... 789
Table 644 — Parameter Data third-party copy descriptor format ................................................................. 790
Table 645 — Supported Descriptors third-party copy descriptor format ....................................................... 791
Table 646 — Supported CSCD Descriptor IDs third-party copy descriptor format ....................................... 792
Table 647 — ROD Token Features third-party copy descriptor format......................................................... 794
Table 648 — REMOTE TOKENS field ................................................................................................................ 795
Table 649 — Block ROD device type specific features descriptor format..................................................... 796
Table 650 — Stream ROD device type specific features descriptor format.................................................. 798
Table 651 — Copy manager ROD device type specific features descriptor format...................................... 799
Table 652 — Supported ROD Types third-party copy descriptor format ...................................................... 800
Table 653 — ROD type descriptor format..................................................................................................... 801
Table 654 — General Copy Operations third-party copy descriptor format .................................................. 803
Table 655 — Stream Copy Operations third-party copy descriptor format ................................................... 804
Table 656 — Held Data third-party copy descriptor format........................................................................... 805
Table 657 — Unit Serial Number VPD page................................................................................................. 806
Table 658 — Well known logical unit numbers ............................................................................................. 807
Table 659 — Commands for the REPORT LUNS well known logical unit.................................................... 807
Table 660 — Commands for the ACCESS CONTROLS well known logical unit.......................................... 808
Table 661 — ACCESS CONTROL OUT management identifier key requirements ..................................... 811
Table 662 — ACCESS CONTROL IN management identifier key requirements ......................................... 812
Table 663 — Mandatory access controls resources ..................................................................................... 822
Table 664 — Optional access controls resources......................................................................................... 823
Table 665 — ACCESS IDENTIFIER TYPE field.................................................................................................... 823
Table 666 — AccessID access identifier format ........................................................................................... 823
Table 667 — ACCESS CONTROL IN service actions.................................................................................. 824
Table 668 — ACCESS CONTROL IN command with REPORT ACL service action ................................... 825
Table 669 — ACCESS CONTROL IN with REPORT ACL parameter data format....................................... 826
Table 670 — ACL data page codes .............................................................................................................. 826
Table 671 — Granted ACL data page format ............................................................................................... 827
Table 672 — Granted ACL data page LUACD descriptor format ................................................................. 828
Table 673 — ACCESS MODE field.................................................................................................................... 828
Table 674 — Granted All ACL data page format .......................................................................................... 829
Table 675 — Proxy Tokens ACL data page format ...................................................................................... 830
Table 676 — Proxy token descriptor format.................................................................................................. 831
Table 677 — ACCESS CONTROL IN command with REPORT LU DESCRIPTORS service action ........... 831
Table 678 — ACCESS CONTROL IN with REPORT LU DESCRIPTORS parameter data format .............. 833
Table 679 — SUPPORTED LUN MASK FORMAT field format............................................................................... 834
Table 680 — Logical Unit descriptor format.................................................................................................. 835
Table 681 — ACCESS CONTROL IN command REPORT ACCESS CONTROLS LOG service action ..... 837
Table 682 — CDB LOG PORTION field ............................................................................................................ 838
Table 683 — ACCESS CONTROL IN with REPORT ACCESS CONTROLS LOG parameter data format . 838
Table 684 — Parameter data LOG PORTION field ........................................................................................... 839
Table 685 — Key Overrides access controls log portion page format .......................................................... 839
Table 686 — Invalid Keys access controls log portion page format ............................................................. 840
Table 687 — ACL LUN Conflicts access controls log portion page format................................................... 841
Table 688 — ACCESS CONTROL IN command REPORT OVERRIDE LOCKOUT TIMER service action 842
Table 689 — ACCESS CONTROL IN with REPORT OVERRIDE LOCKOUT TIMER parameter data ....... 843
Table 690 — ACCESS CONTROL IN command with REQUEST PROXY TOKEN service action .............. 844
Table 691 — ACCESS CONTROL IN with REQUEST PROXY TOKEN parameter data ............................ 845
Table 692 — ACCESS CONTROL OUT service actions.............................................................................. 845
Table 693 — ACCESS CONTROL OUT command format........................................................................... 846

Working Draft SCSI Primary Commands - 4 (SPC-4) xxxvii

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 694 — ACCESS CONTROL OUT with MANAGE ACL parameter data format .................................. 847
Table 695 — ACE page codes...................................................................................................................... 848
Table 696 — Grant/Revoke ACE page format.............................................................................................. 849
Table 697 — ACE page LUACD descriptor format ....................................................................................... 850
Table 698 — Access Coordinator Grant/Revoke ACE page actions ............................................................ 851
Table 699 — Grant All ACE page format ...................................................................................................... 852
Table 700 — Revoke Proxy Token ACE page format................................................................................... 853
Table 701 — Revoke All Proxy Tokens ACE page format............................................................................ 854
Table 702 — ACCESS CONTROL OUT with DISABLE ACCESS CONTROLS parameter data format...... 854
Table 703 — ACCESS CONTROL OUT with ACCESS ID ENROLL parameter data format ....................... 855
Table 704 — ACCESS CONTROL OUT with CLEAR ACCESS CONTROLS LOG parameter data format 857
Table 705 — CLEAR ACCESS CONTROLS LOG LOG PORTION field .......................................................... 857
Table 706 — ACCESS CONTROL OUT command MANAGE OVERRIDE LOCKOUT TIMER service
action parameter data format ................................................................................................... 858
Table 707 — ACCESS CONTROL OUT with OVERRIDE MGMT ID KEY parameter data format .............. 859
Table 708 — ACCESS CONTROL OUT with REVOKE PROXY TOKEN parameter data format................ 860
Table 709 — ACCESS CONTROL OUT with REVOKE ALL PROXY TOKENS parameter data format ...... 861
Table 710 — ACCESS CONTROL OUT with ASSIGN PROXY LUN parameter data format ...................... 862
Table 711 — ACCESS CONTROL OUT with RELEASE PROXY LUN parameter data format ................... 863
Table 712 — Commands for the TARGET LOG PAGES well known logical unit......................................... 864
Table 713 — Commands for the SECURITY PROTOCOL well known logical unit ...................................... 864
Table 714 — Commands for the MANAGEMENT PROTOCOL well known logical unit .............................. 865
Table 715 — Commands for a security manager ......................................................................................... 866
Table A.1 — This standard to SPC-2 terminology mapping ......................................................................... 867
Table B.1 — Example logical unit inventory.................................................................................................. 868
Table B.2 — REPORT LUNS command returned LUN list........................................................................... 869
Table C.1 — PERSISTENT RESERVE OUT command features................................................................. 872
Table E.1 — IKE payload names shorthand ................................................................................................. 878
Table F.1 — ASC and ASCQ assignments................................................................................................... 880
Table F.2 — Operation codes ....................................................................................................................... 900
Table F.3 — Additional operation codes for devices with the ENCSERV bit set to one.................................. 906
Table F.4 — MAINTENANCE IN service actions and MAINTENANCE OUT service actions ...................... 907
Table F.5 — SERVICE ACTION IN(12) service actions and SERVICE ACTION OUT(12) service actions . 908
Table F.6 — SERVICE ACTION IN(16) service actions and SERVICE ACTION OUT(16) service actions . 908
Table F.7 — SERVICE ACTION BIDIRECTIONAL service actions.............................................................. 909
Table F.8 — Variable Length CDB Service Action Code Ranges................................................................. 910
Table F.9 — Variable Length CDB Service Action Codes Used by All Device Types .................................. 910
Table F.10 — Diagnostic page codes ........................................................................................................... 911
Table F.11 — Log page codes...................................................................................................................... 912
Table F.12 — Transport protocol specific log page codes............................................................................ 914
Table F.13 — Mode page codes................................................................................................................... 915
Table F.14 — Transport protocol specific mode page codes........................................................................ 917
Table F.15 — VPD page codes .................................................................................................................... 918
Table F.16 — Transport protocol specific VPD page codes ......................................................................... 919
Table F.17 — ROD type codes ..................................................................................................................... 920
Table F.18 — Version descriptor assignments ............................................................................................. 921
Table F.19 — Standard code value guidelines ............................................................................................. 937
Table F.20 — IEEE binary identifiers assigned by T10................................................................................. 942
Table G.1 — T10 vendor identification list .................................................................................................... 943

xxxviii Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Figures
Page
Figure 1 — SCSI document structure ............................................................................................................ xlvi
Figure 2 — Example state diagram................................................................................................................. 35
Figure 3 — Example flowchart ........................................................................................................................ 36
Figure 4 — Example class association relationships ...................................................................................... 39
Figure 5 — Example class aggregation relationships ..................................................................................... 40
Figure 6 — Example class generalization relationships.................................................................................. 41
Figure 7 — Example class dependency relationships .................................................................................... 42
Figure 8 — Power condition state machine .................................................................................................. 125
Figure 9 — Device server interpretation of PREEMPT service action .......................................................... 150
Figure 10 — SA relationships ....................................................................................................................... 158
Figure 11 — IKEv2-SCSI Device Server Capabilities step ........................................................................... 169
Figure 12 — IKEv2-SCSI Key Exchange step .............................................................................................. 170
Figure 13 — IKEv2-SCSI Authentication step............................................................................................... 171
Figure 14 — IKEv2-SCSI Delete operation................................................................................................... 172
Figure 15 — CbCS overview class diagram ................................................................................................. 197
Figure 16 — Primary target port group example........................................................................................... 238
Figure 17 — Examples of copy manager configurations .............................................................................. 247
Figure 18 — EXTENDED COPY parameter list structure diagram............................................................... 269
Figure 19 — ACL Structure........................................................................................................................... 810
Figure B.1 — Example logical unit representation ........................................................................................ 869

Working Draft SCSI Primary Commands - 4 (SPC-4) xxxix

T10/BSR INCITS 513 Revision 37 17 May 2014

Foreword

This foreword is not part of American National Standard INCITS 513-20xx.

The SCSI command set is designed to provide efficient peer-to-peer operation of SCSI devices (e.g., disks,
tapes, media changers) by an operating system. The SCSI command set assumes an underlying
command-response protocol.

The SCSI command set provides multiple operating systems concurrent control over one or more SCSI
devices. However, proper coordination of activities between the multiple operating systems is critical to avoid
data corruption. Commands that assist with coordination between multiple operating systems are described in
this standard. However, details of the coordination are beyond the scope of the SCSI command set.

This standard defines the device model for all SCSI devices. This standard defines the SCSI commands that
are basic to every device model and the SCSI commands that may apply to any device model.

With any technical document there may arise questions of interpretation as new products are implemented.
INCITS has established procedures to issue technical opinions concerning the standards developed by
INCITS. These procedures may result in SCSI Technical Information Bulletins being published by INCITS.

These Bulletins, while reflecting the opinion of the Technical Committee that developed the standard, are
intended solely as supplementary information to other users of the standard. This standard, ANSI INCITS
513-20xx, as approved through the publication and voting procedures of the American National Standards
Institute, is not altered by these bulletins. Any subsequent revision to this standard may or may not reflect the
contents of these Technical Information Bulletins.

Current INCITS practice is to make standards and technical information bulletins available through:

http://www.incits.org/standards-information/purchase-standards

Requests for interpretation, suggestions for improvement and addenda, or defect reports are welcome. They
should be sent to the INCITS Secretariat, National Committee for Information Technology Standards, Infor-
mation Technology Industry Council, 1101 K Street NW, Suite 610, Washington, DC 20005-7031.

xl Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

This standard was processed and approved for submittal to ANSI by the InterNational Committee for Infor-
mation Technology Standards (INCITS). Committee approval of the standard does not necessarily imply that
all committee members voted for approval. At the time it approved this standard, INCITS had the following
members:

Adobe
AIM Global Inc
Apple Inc
EIA
EMC Corporation
Farance Inc
GS1 US
Hewlett-Packard Company
IBM Corporation
IEEE
Intel Corporation
Lexmark International
Microsoft Corporation
NIST
Oracle Corporation
Sony Electronics Inc
U.S. Department of Defense
U.S. Department of Homeland Security

Technical Committee T10 on SCSI Storage Interfaces, which developed and reviewed this standard, had the
following members:

John B. Lohmeyer, Chair

William Martin, Vice-Chair
Ralph O. Weber, Secretary

Organization Represented Name of Representative

Amphenol Corporation ......................................................... Gregory McSorley
David Chan (Alt)
Paul Coddington (Alt)
Zhineng Fan (Alt)
Adrian Green (Alt)
Martin Li (Alt)
Chris Lyon (Alt)
Alex Persaud (Alt)
Chansy Phommachanh (Alt)
Michael Wingard (Alt)
CN Wong (Alt)
Matt Wright (Alt)

Working Draft SCSI Primary Commands - 4 (SPC-4) xli

T10/BSR INCITS 513 Revision 37 17 May 2014

Avago Technologies ............................................................. John Lohmeyer

Patrick Bashford (Alt)
Brad Besmer (Alt)
Srikiran Dravida (Alt)
Bernhard Laschinsky (Alt)
Parag Maharana (Alt)
Harvey Newman (Alt)
George Penokie (Alt)
Sumit Puri (Alt)
Robert Sheffield (Alt)
Ross Stenfort (Alt)
Bill Voorhees (Alt)
Dell, Inc. ............................................................................... Kevin Marks
Mark Bokhan (Alt)
Gary Kotzur (Alt)
Bill Lynn (Alt)
Ash McCarty (Alt)
Daniel Oelke (Alt)
EMC Corporation ................................................................. Gary Robinson
David Black (Alt)
George Ericson (Alt)
Mickey Felton (Alt)
Marlon Ramroopsingh (Alt)
FCI Electronics..................................................................... Donald Harper
Brad Brubaker (Alt)
Paul Rubens (Alt)
Dave Sideck (Alt)
Foxconn Electronics............................................................. Fred Fons
Gary Hsieh (Alt)
Glenn Moore (Alt)
Mike Shu (Alt)
Miller Zhao (Alt)
Fujitsu America Inc............................................................... Kun Katsumata
Jim DeCaires (Alt)
Osamu Kimura (Alt)
Mark Malcolm (Alt)
Gene Owens (Alt)
Sandy Wilson (Alt)
Futurewei Technologies Inc.................................................. Serge Manning
Xiaoyu Ge (Alt)
Xiaoyan He (Alt)
Li Peng (Alt)
Alan Yoder (Alt)
HengLiang Zhang (Alt)
Hewlett-Packard Company .................................................. Curtis Ballard
Wayne Bellamy (Alt)
Chris Cheng (Alt)
Rob Elliott (Alt)
Joe Foster (Alt)
Barry Olawsky (Alt)
Jeff Wolford (Alt)

xlii Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

HGST ................................................................................... Joe Breher

David Brewer (Alt)
Frank Chu (Alt)
Chet Mercado (Alt)
Nadesan Narenthiran (Alt)
IBM Corporation ................................................................... Kevin Butt
Mark Andresen (Alt)
Mike Osborne (Alt)
Ted Vojnovich (Alt)
Intel Corporation................................................................... Pak-Lung Seto
Richard Mellitz (Alt)
KnowledgeTek Inc ................................................................ Dennis Moore
Hugh Curley (Alt)
Marvell Semiconductor Inc................................................... David Geddes
Wei Liu (Alt)
Paul Wassenberg (Alt)
Micron Technology Inc ......................................................... John Geldman
Jerry Barkley (Alt)
Neal Galbo (Alt)
Michael George (Alt)
Alan Haffner (Alt)
Carl Mies (Alt)
Niels Reimers (Alt)
Bob Warren (Alt)
Microsoft Corporation ........................................................... Calvin Chen
Paul Luber (Alt)
Bryan Matthew (Alt)
Steve Olsson (Alt)
Lee Prewitt (Alt)
Molex Inc.............................................................................. Jay Neer
Cong Gao (Alt)
Michael Rost (Alt)
Darian Schulz (Alt)
NetApp Inc ........................................................................... Frederick Knight
Chris Fore (Alt)
Jaimon George (Alt)
Subhash Sankuratripati (Alt)
Ali Yavari (Alt)
Oracle................................................................................... Dennis Appleyard
Jon Allen (Alt)
Seth Goldberg (Alt)
Martin Petersen (Alt)
Wan Shan (Alt)
Phi Tran (Alt)
Lee Wan-Hui (Alt)

Working Draft SCSI Primary Commands - 4 (SPC-4) xliii

T10/BSR INCITS 513 Revision 37 17 May 2014

PMC-Sierra .......................................................................... Tim Symons

David Allen (Alt)
Paul Borsetti (Alt)
Graeme Boyd (Alt)
Steve Gerson (Alt)
Bill Lye (Alt)
Ie-Wei Njoo (Alt)
Keith Shaw (Alt)
Gregory Tabor (Alt)
Neil Wanamaker (Alt)
Rod Zavari (Alt)
Quantum Corporation........................................................... Paul Stone
Paul Suhler (Alt)
Rod Wideman (Alt)
Samsung Semiconductor Inc (SSI) ...................................... William Martin
Judy Brock (Alt)
HeeChang Cho (Alt)
KeunSoo Jo (Alt)
Sreenivas Krishnan (Alt)
Sung Lee (Alt)
Bhavith M.P. (Alt)
Truong Nguyen (Alt)
Santosh Singh (Alt)
SanDisk IL Ltd...................................................................... Avraham Shimor
Dave Landsman (Alt)
Yoni Shternhell (Alt)
Seagate Technology............................................................. Gerald Houlder
Michael K. Connolly (Alt)
Alvin Cox (Alt)
Neil Edmunds (Alt)
John Fleming (Alt)
Jim Hatfield (Alt)
Alan Westbury (Alt)
Judy Westby (Alt)

Synapse Design AutomationMike McKean

xliv Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Introduction

The SCSI Primary Commands - 4 (SPC-4) standard is divided into the following clauses and annexes:

Clause 1 is the scope.

Clause 2 enumerates the normative references that apply to this standard.
Clause 3 describes the definitions, symbols, and abbreviations used in this standard.
Clause 4 describes the conceptual relationship between this document and the SCSI-3 Architecture
Model.
Clause 5 describes the command model for all SCSI devices.
Clause 6 defines the commands that may be implemented by any SCSI device.
Clause 7 defines the parameter data formats that may be implemented by any SCSI device.
Clause 8 defines the well known logical units that may be implemented by any SCSI device.
Clause 9 defines the commands supported by the security manager component of command security.
Annex A identifies differences between the terminology used in this standard and previous versions of
this standard. (informative)
Annex B provides examples of the parameter data returned by the REPORT LUNS command
Annex C describes the PERSISTENT RESERVE OUT command features necessary to replace the
reserve/release management method and provides guidance on how to perform a third party
reservation using persistent reservations. (informative)
Annex D provides information about the third-party copy commands and copy manager. (informative)
Annex E identifies the differences between security protocols defined by other standards (e.g., IKEv2
(see RFC 4306)) and the equivalent protocols defined by this standard (e.g., the IKEv2-SCSI
SA creation protocol). (informative)
Annex F lists code values in numeric order. (informative)
Annex G lists assigned vendor identifiers. (informative)

The annexes provide information to assist with implementation of this standard. The information in the
annexes applies to all command standards.

Working Draft SCSI Primary Commands - 4 (SPC-4) xlv

T10/BSR INCITS 513 Revision 37 17 May 2014

SCSI standards family

Figure 1 shows the relationship of this standard to the other standards and related projects in the SCSI family
of standards as of the publication of this standard.

Primary command set

Device-type specific command sets
(shared for all device types)
(e.g., SBC-3, SSC-4)
SCSI Architecture Model

(this standard)
(SAM-5)

SCSI transport protocols

(e.g., SPL-3, FCP-4)

Interconnects
(e.g., SAS-3, Fibre Channel)

Figure 1 — SCSI document structure

The SCSI document structure in figure 1 is intended to show the general applicability of the documents to one
another. Figure 1 is not intended to imply a relationship such as a hierarchy, protocol stack, or system archi-
tecture.

SCSI Architecture Model: Defines the SCSI systems model, the functional partitioning of the SCSI standard
set and requirements applicable to all SCSI implementations and implementation standards.

Device-Type Specific Command Sets: Implementation standards that define specific device types including
a device model for each device type. These standards specify the required commands and behaviors that are
specific to a given device type and prescribe the requirements to be followed by a SCSI initiator device when
sending commands to a SCSI target device having the specific device type. The commands and behaviors for
a specific device type may include by reference commands and behaviors that are shared by all SCSI
devices.

Shared Command Set: An implementation standard that defines a model for all SCSI device types. This
standard specifies the required commands and behavior that is common to all SCSI devices, regardless of
device type, and prescribes the requirements to be followed by a SCSI initiator device when sending
commands to any SCSI target device.

SCSI Transport Protocols: Implementation standards that define the requirements for exchanging infor-
mation so that different SCSI devices are capable of communicating.

Interconnects: Implementation standards that define the communications mechanism employed by the SCSI
transport protocols. These standards may describe the electrical and signaling requirements essential for
SCSI devices to interoperate over a given interconnect. Interconnect standards may allow the interconnection
of devices other than SCSI devices in ways that are outside the scope of this standard.

The term SCSI is used to refer to the family of standards described in this subclause.

xlvi Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

At the time this standard was generated, examples of the SCSI general structure included:

Interconnects:
Fibre Channel Arbitrated Loop - 2 FC-AL-2 [ISO/IEC 14165-122]
[ANSI INCITS 332-1999]
[ANSI INCITS 332/AM1-2003]
[ANSI INCITS 332/AM2-2006]
Fibre Channel Physical Interfaces FC-PI [ISO/IEC 14165-115]
[ANSI INCITS 352-2002]
Fibre Channel Physical Interfaces - 2 FC-PI-2 [ISO/IEC 14165-142]
[ANSI INCITS 404-2006]
Fibre Channel Physical Interfaces - 3 FC-PI-3 [ISO/IEC 14165-143]
[T11/1625-D]
Fibre Channel Physical Interfaces - 4 FC-PI-4 [ISO/IEC 14165-144]
[ANSI INCITS 450-2009]
Fibre Channel Physical Interfaces - 5 FC-PI-5 [ISO/IEC 14165-145]
[ANSI INCITS 479-2011]
Fibre Channel Physical Interfaces - 6 FC-PI-6 [ISO/IEC 14165-146]
[T11/2221-D]
Fibre Channel - 10 Gigabit 10GFC [ISO/IEC 14165-116]
[ANSI INCITS 364-2003]
[ANSI INCITS 364/AM1-2007]
Fibre Channel Framing and Signaling Interface FC-FS [ISO/IEC 14165-251]
[ANSI INCITS 373-2003]
Fibre Channel Framing and Signaling Interface - 2 FC-FS-2 [ISO/IEC 14165-252]
[ANSI INCITS 424-2007]
[ANSI INCITS 424/AM1-2007]
Fibre Channel Framing and Signaling Interface - 3 FC-FS-3 [ISO/IEC 14165-253]
[T11/1861-D]
Fibre Channel Link Services FC-LS [ANSI INCITS 433-2007]
Fibre Channel Link Services - 2 FC-LS-2 [T11/2103-D]
Fibre Channel Security Protocols FC-SP [ISO/IEC 14165-431]
[ANSI INCITS 426-2007]
Fibre Channel Security Protocols - 2 FC-SP-2 [ISO/IEC 14165-432]
[T11/1835-D]
High Performance Serial Bus [ANSI IEEE 1394-1995]
High Performance Serial Bus [ANSI IEEE 1394a-2000]
(supplement to ANSI/IEEE 1394-1995)
SCSI Parallel Interface - 2 SPI-2 [ISO/IEC 14776-112]
[ANSI INCITS 302-1999]
SCSI Parallel Interface - 3 SPI-3 [ISO/IEC 14776-113]
[ANSI INCITS 336-2000]
SCSI Parallel Interface - 4 SPI-4 [ISO/IEC 14776-114]
[ANSI INCITS 362-2002]
SCSI Parallel Interface - 5 SPI-5 [ISO/IEC 14776-115]
[ANSI INCITS 367-2003]
Serial Storage Architecture Physical Layer 1 SSA-PH [ANSI INCITS 293-1996]
Serial Storage Architecture Physical Layer 2 SSA-PH-2 [ANSI INCITS 307-1998]
Serial Attached SCSI SAS [ISO/IEC 14776-150]
[ANSI INCITS 376-2003]
Serial Attached SCSI - 1.1 SAS-1.1 [ISO/IEC 14776-151]
[ANSI INCITS 417-2006]

Working Draft SCSI Primary Commands - 4 (SPC-4) xlvii

T10/BSR INCITS 513 Revision 37 17 May 2014

Serial Attached SCSI - 2 SAS-2 [ISO/IEC 14776-152]

[ANSI INCITS 457-2010]
Serial Attached SCSI - 2.1 SAS-2.1 [ISO/IEC 14776-153]
[ANSI INCITS 478-2011]
Serial Attached SCSI - 3 SAS-3 [ISO/IEC 14776-154]
[T10/BSR INCITS 519]
Serial Attached SCSI - 4 SAS-4 [ISO/IEC 14776-155]
[T10/BSR INCITS 534]
PCI Express® Queuing Interface PQI [ISO/IEC 14776-171]
[T10/BSR INCITS 490]
PCI Express® Queuing Interface - 2 PQI-2 [ISO/IEC 14776-171]
[T10/BSR INCITS 507]

SCSI Transport Protocols:

Automation/Drive Interface - Transport Protocol ADT [ANSI INCITS 406-2005]
Automation/Drive Interface - Transport Protocol - 2 ADT-2 [ANSI INCITS 472-2011]
Serial Storage Architecture Transport Layer 1 SSA-TL-1 [ANSI INCITS 295-1996]
Serial Storage Architecture Transport Layer 2 SSA-TL-2 [ANSI INCITS 308-1998]
SCSI-3 Fibre Channel Protocol FCP [ISO/IEC 14776-221]
[ANSI INCITS 269-1996]
Fibre Channel Protocol for SCSI - 2 FCP-2 [ISO/IEC 14776-222]
[ANSI INCITS 350-2003]
Fibre Channel Protocol for SCSI - 3 FCP-3 [ISO/IEC 14776-223]
[ANSI INCITS 416-2006]
Fibre Channel Protocol for SCSI - 4 FCP-4 [ISO/IEC 14776-223]
Serial Bus Protocol - 2 SBP-2 [ISO/IEC 14776-232]
[ANSI INCITS 325-1998]
Serial Bus Protocol - 3 SBP-3 [ANSI INCITS 375-2004]
Serial Storage Architecture SCSI-3 Protocol SSA-S3P [ANSI INCITS 309-1998]
SCSI RDMA Protocol SRP [ISO/IEC 14776-241]
[ANSI INCITS 365-2002]
USB Attached SCSI UAS [ISO/IEC 14776-251]
[ANSI INCITS 471-2010]
USB Attached SCSI - 2 UAS-2 [ISO/IEC 14776-252]
[T10/BSR INCITS 520]
SAS Protocol Layer SPL [ISO/IEC 14776-261]
[ANSI INCITS 476-2011]
[ANSI INCITS 476-2011/AM1-2012]
SAS Protocol Layer - 2 SPL-2 [ISO/IEC 14776-262]
[ANSI INCITS 505-2013]
SAS Protocol Layer - 3 SPL-3 [ISO/IEC 14776-263]
[T10/BSR INCITS 492]
SAS Protocol Layer - 4 SPL-4 [ISO/IEC 14776-264]
[T10/BSR INCITS 538]
SCSI over PCI Express® SOP [ISO/IEC 14776-271]
[T10/BSR INCITS 489]
SCSI over PCI Express® - 2 SOP-2 [ISO/IEC 14776-272]
[T10/BSR INCITS 521]

Primary Command Set:

SCSI-3 Primary Commands SPC [ANSI INCITS 301-1997]
SCSI Primary Commands - 2 SPC-2 [ISO/IEC 14776-452]
[ANSI INCITS 351-2001]

xlviii Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

SCSI Primary Commands - 3 SPC-3 [ISO/IEC 14776-453]

[ANSI INCITS 408-2005]
SCSI Primary Commands - 4 SPC-4 [ISO/IEC 14776-454]
[T10/BSR INCITS 513]
SCSI Primary Commands - 5 SPC-5 [ISO/IEC 14776-455]
[T10/BSR INCITS 502]
Security Features for SCSI Commands SFSC [ISO/IEC 14776-481]
[T10/BSR INCITS 501]

Device-Type Specific Command Sets:

SCSI-3 Block Commands SBC [ISO/IEC 14776-321]
[ANSI INCITS 306-1998]
SCSI Block Commands - 2 SBC-2 [ISO/IEC 14776-322]
[ANSI INCITS 405-2005]
SCSI Block Commands - 3 SBC-3 [ISO/IEC 14776-323]
[T10/BSR INCITS 514]
SCSI Block Commands - 4 SBC-4 [ISO/IEC 14776-324]
[T10/BSR INCITS 506]
Zoned-device Block Commands ZBC [ISO/IEC 14776-345]
[T10/BSR INCITS 536]
SCSI-3 Stream Commands SSC [ISO/IEC 14776-331]
[ANSI INCITS 335-2000]
SCSI Stream Commands - 2 SSC-2 [ISO/IEC 14776-332]
[ANSI INCITS 380-2003]
SCSI Stream Commands - 3 SSC-3 [ISO/IEC 14776-333]
[ANSI INCITS 467-2011]
SCSI Stream Commands - 4 SSC-4 [ISO/IEC 14776-334]
[ANSI INCITS 516-2013]
SCSI Stream Commands - 5 SSC-5 [ISO/IEC 14776-335]
[T10/BSR INCITS 503]
SCSI-3 Medium Changer Commands SMC [ANSI INCITS 314-1998]
SCSI Media Changer Commands - 2 SMC-2 [ANSI INCITS 382-2004]
SCSI Media Changer Commands - 3 SMC-3 [ANSI INCITS 484-201x]
SCSI-3 Multimedia Command Set MMC [ANSI INCITS 304-1997]
SCSI Multimedia Command Set - 2 MMC-2 [ISO/IEC 14776-362]
[ANSI INCITS 333-2000]
SCSI Multimedia Command Set - 3 MMC-3 [ANSI INCITS 360-2002]
SCSI Multimedia Command Set - 4 MMC-4 [ANSI INCITS 401-2005]
SCSI Multimedia Command Set - 5 MMC-5 [ANSI INCITS 430-2007]
SCSI Multimedia Command Set - 6 MMC-6 [ANSI INCITS 468-2010]
[ANSI INCITS 468/AM1-201x]
SCSI Controller Commands - 2 SCC-2 [ISO/IEC 14776-342]
[ANSI INCITS 318-1998]
SCSI Reduced Block Commands RBC [ISO/IEC 14776-326]
[ANSI INCITS 330-2000]
[ANSI INCITS 330-2003/AM1]
SCSI-3 Enclosure Services Commands SES [ISO/IEC 14776-371]
[ANSI INCITS 305-1998]
[ANSI INCITS 305-2000/AM1]
SCSI Enclosure Services Commands - 2 SES-2 [ISO/IEC 14776-372]
[ANSI INCITS 448-2008]
SCSI Enclosure Services Commands - 3 SES-3 [ISO/IEC 14776-373]
[T10/BSR INCITS 518]
SCSI Specification for Optical Card Reader/Writer OCRW [ISO/IEC 14776-381]

Working Draft SCSI Primary Commands - 4 (SPC-4) xlix

T10/BSR INCITS 513 Revision 37 17 May 2014

Automation/Drive Interface - Commands ADC [ANSI INCITS 403-2005]

Automation/Drive Interface - Commands - 2 ADC-2 [ANSI INCITS 441-2008]
Automation/Drive Interface - Commands - 3 ADC-3 [ANSI INCITS 497-201x]
Object-based Storage Device Commands OSD [ANSI INCITS 400-2004]
Object-based Storage Device Commands - 2 OSD-2 [ANSI INCITS 458-2011]

Translation Protocols:
SCSI / ATA Translation SAT [ANSI INCITS 431-2007]
SCSI / ATA Translation - 2 SAT-2 [ISO/IEC 14776-922]
[ANSI INCITS 465-2010]
SCSI / ATA Translation - 3 SAT-3 [ISO/IEC 14776-923]
[T10/BSR INCITS 517]
SCSI / ATA Translation - 4 SAT-4 [ISO/IEC 14776-924]
[T10/BSR INCITS 491]

Architecture Model:
SCSI-3 Architecture Model SAM [ISO/IEC 14776-411]
[ANSI INCITS 270-1996]
SCSI Architecture Model - 2 SAM-2 [ISO/IEC 14776-412]
[ANSI INCITS 366-2003]
SCSI Architecture Model - 3 SAM-3 [ISO/IEC 14776-413]
[ANSI INCITS 402-2005]
SCSI Architecture Model - 4 SAM-4 [ISO/IEC 14776-414]
[ANSI INCITS 447-2008]
SCSI Architecture Model - 5 SAM-5 [ISO/IEC 14776-415]
[T10/BSR INCITS 515]

l Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

AMERICAN NATIONAL STANDARD INCITS 513-20xx

American National Standard

for Information Technology -

SCSI Primary Commands - 4 (SPC-4)

1 Scope

The SCSI family of standards provides for many different types of SCSI devices (e.g., disks, tapes, media
changers). This standard defines a device model that is applicable to all SCSI devices. Other command
standards expand on the general SCSI device model in ways appropriate to specific types of SCSI devices.

The set of SCSI standards specifies the interfaces, functions, and operations necessary to ensure
interoperability between conforming SCSI implementations. This standard is a functional description.
Conforming implementations may employ any design technique that does not violate interoperability.

This standard defines the SCSI commands that are mandatory and optional for all SCSI devices. Support for
any feature defined in this standard is optional unless otherwise stated. This standard also defines the SCSI
commands that may apply to any device model.

The following commands, parameter data, and features defined in previous versions of this standard are
made obsolete by this standard:

a) the TARGET RESET supported (TRS) bit and the WAKEUP supported (WAKES) bit in the REPORT
SUPPORTED TASK MANAGEMENT FUNCTIONS parameter data;
b) code value 10b (i.e., Per initiator port) in the MODE PAGE POLICY field in the mode page policy
descriptor in the Mode Page Policy VPD page;
c) the removable medium devices with an attached medium changer model, MCHNGR bit in the standard
INQUIRY data, the MOVE MEDIUM ATTACHED command in disks and tapes, and the READ
ELEMENT STATUS ATTACHED command in disks and tapes;
d) linked commands;
e) the PPC bit in the LOG SENSE command;
f) the NUL bit in EXTENDED COPY command target descriptors (i.e., CSCD descriptors in this
standard);
g) EXTENDED COPY support for the processing of setmarks by sequential-access devices;
h) READ BUFFER commands with the MODE field set to 00h and 1Ah; and
i) WRITE BUFFER commands with the MODE field set to 00h, 1Ah, and 1Bh.

2 Normative references

2.1 General

The following standards contain provisions that, by reference in the text, constitute provisions of this standard.
At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to
agreements based on this standard are encouraged to investigate the possibility of applying the most recent
editions of the standards listed below.

Working Draft SCSI Primary Commands - 4 (SPC-4) 1

T10/BSR INCITS 513 Revision 37 17 May 2014

2.2 Approved references

Copies of the following documents may be obtained from ANSI, an ISO member organization:

a) approved ANSI standards;

b) approved international and regional standards (ISO and IEC); and
c) approved foreign standards (including JIS and DIN).

For further information, contact the ANSI Customer Service Department:

Phone +1 212-642-4980
Fax: +1 212-302-1286
Web: http://www.ansi.org
E-mail: [email protected]

or the InterNational Committee for Information Technology Standards (INCITS):

Phone +1 202-626-5738
Web: http://www.incits.org
E-mail: [email protected]

ISO/IEC 14776-412, SCSI Architecture Model - 2 (SAM-2) [ANSI INCITS 366-2003]

ISO/IEC 14776-414, SCSI Architecture Model - 4 (SAM-4) [ANSI INCITS 447-2008]

ISO/IEC 14776-452, SCSI Primary Commands - 2 (SPC-2) [ANSI INCITS 351-2001]

ISO/IEC 14776-113, SCSI Parallel Interface - 5 (SPI-5) [ANSI INCITS 367-2003]

ANSI INCITS 481-2012, Fibre Channel Protocol for SCSI - 4 (FCP-4)

ISO/IEC 14776-241, SCSI RDMA Protocol (SRP) [ANSI INCITS 365-2002]

ANSI INCITS 457-2010, Serial Attached SCSI - 2 (SAS-2)

NOTE 1 - SAS-2.1 supersedes SAS-2 but does not contain the information that this standard references
normatively in 7.5.13.

ISO/IEC 14776-153, Serial Attached SCSI - 2.1 (SAS-2.1) [ANSI INCITS 478-2011]

ISO/IEC 14776-262, SAS Protocol Layer - 2 (SPL-2) [ANSI INCITS 505-2013]

ISO/IEC 14776-271, SCSI Over PCI Express® (SOP) [ANSI INCITS 489-2014]

ISO/IEC 14776-922, SCSI / ATA Translation - 2 (SAT-2) [ANSI INCITS 465-2010]

ISO/IEC 14776-322, SCSI Block Commands - 2 (SBC-2) [ANSI INCITS 405-2005]

ISO/IEC 14776-323, SCSI Block Commands - 3 (SBC-3) [ANSI INCITS 514-2014]

ISO/IEC 14776-331, SCSI Stream Commands (SSC) [ANSI INCITS 335-2000-R2011]

ISO/IEC 14776-334, SCSI Stream Commands - 4 (SSC-4) [ANSI INCITS 516-2014]

2 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

ANSI INCITS 468-2010, Multi-Media Commands - 6 (MMC-6)

ANSI INCITS 468-2010/AM 1-2012, Multi-Media Commands - 6 (MMC-6) Amendment 1

ANSI INCITS 484-2012, SCSI Media Changer Commands - 3, (SMC-3)

ANSI INCITS 375-2004, Serial Bus Protocol - 3 (SBP-3)

ANSI INCITS 470-2011, Fibre Channel Framing and Signaling Interface-3 (FC-FS-3)

ANSI INCITS 477-2011, Fibre Channel Link Services-2 (FC-LS-2)

ANSI INCITS 496-2012, Fibre Channel Security Protocols-2 (FC-SP-2)

ISO 5807:1995 (R2003), Documentation Symbols and Conventions for Data, Program and System
Flowcharts, Program Network Charts and System Resource Charts

ISO 80000-1:2009, Quantities and units – Part 1: General

IEC 80000-13:2008, Quantities and units – Part 13: Information science and technology

ANSI/IEEE 1394a-2000, High Performance Serial Bus (supplement to ANSI/IEEE 1394-1995)

ANSI/IEEE 1619.1-2007, Standard for Authenticated Encryption with Length Expansion for Storage Devices

ANSI INCITS 4-1986 (R2002), Information Systems - Coded Character Sets - 7-Bit American National
Standard Code for Information Interchange (7-Bit ASCII)

ISO/IEC 13213, Information technology - Microprocessor systems - Control and Status Registers Architecture
for microcomputer buses [ANSI/IEEE 1212, 2001 Edition]

ISO/IEC 646:1991, Information technology - ISO 7-bit coded character set for information interchange (third
edition).

ISO/IEC 8859-1:1998, Information technology - 8-bit single-byte coded graphic character sets - Part 1: Latin
alphabet No. 1

ISO/IEC 8859-2:1999, Information technology - 8-bit single-byte coded graphic character sets - Part 2: Latin
alphabet No. 2

ISO/IEC 8859-3:1999, Information technology - 8-bit single-byte coded graphic character sets - Part 3: Latin
alphabet No. 3

ISO/IEC 8859-4:1998, Information technology - 8-bit single-byte coded graphic character sets - Part 4: Latin
alphabet No. 4

ISO/IEC 8859-5:1999, Information technology - 8-bit single-byte coded graphic character sets - Part 5:
Latin/Cyrillic alphabet

ISO/IEC 8859-6:1999, Information technology - 8-bit single-byte coded graphic character sets - Part 6:
Latin/Arabic alphabet

ISO/IEC 8859-7:1987, Information processing - 8-bit single-byte coded graphic character sets - Part 7:
Latin/Greek alphabet

Working Draft SCSI Primary Commands - 4 (SPC-4) 3

T10/BSR INCITS 513 Revision 37 17 May 2014

ISO/IEC 8859-8:1999, Information technology - 8-bit single-byte coded graphic character sets - Part 8:
Latin/Hebrew alphabet

ISO/IEC 8859-9:1999, Information technology - 8-bit single-byte coded graphic character sets - Part 9: Latin
alphabet No. 5

ISO/IEC 8859-10:1998, Information technology - 8-bit single-byte coded graphic character sets - Part 10:
Latin alphabet No. 6

ISO/IEC 10646:2003, Information technology - Universal Multiple-Octet Coded Character Set (UCS)

ISO/IEC 9594-8:2001, Information technology - Open Systems Interconnection - The Directory: Public-key
and attribute certificate frameworks [ITU-T Recommendation X.509:2000 – http://www.itu.int/ITU-T/]

ISO/IEC 9594-8:2001/Cor 1:2002, Information technology - Open Systems Interconnection - The Directory:
Public-key and attribute certificate frameworks

ISO/IEC 9594-8:2001/Cor 2:2002, Information technology - Open Systems Interconnection - The Directory:
Public-key and attribute certificate frameworks

ISO/IEC 9594-8:2001/Cor 3:2005, Information technology - Open Systems Interconnection - The Directory:
Public-key and attribute certificate frameworks

ANSI/IEEE 1667:2009, Standard Protocol for Authentication in Host Attachments of Transient Storage
Devices

2.3 References under development

At the time of publication, the following referenced standards were still under development. For information on
the current status of the document, or regarding availability, contact the relevant standards body or other
organization as indicated.

ISO/IEC 14776-415, SCSI Architecture Model - 5 (SAM-5) [T10/BSR INCITS 515]

ISO/IEC 14776-324, SCSI Block Commands - 4 (SBC-4) [T10/BSR INCITS 506]

ISO/IEC 14776-335, SCSI Stream Commands - 5 (SSC-5) [T10/BSR INCITS 503]

ISO/IEC 14776-345, Zoned Block Commands (ZBC) [T10/BSR INCITS 536]

ISO/IEC 14776-263, SAS Protocol Layer - 3 (SPL-3) [T10/BSR INCITS 492]

ISO/IEC 14776-252, USB Attached SCSI - 2 (UAS-2) [T10/BSR INCITS 520]

ISO/IEC 14776-923, SCSI / ATA Translation - 3 (SAT-3) [T10/BSR INCITS 517]

T11/2238-D, Fibre Channel Framing and Signaling Interface-4 (FC-FS-4)

T11/2237-D, Fibre Channel Link Services-3 (FC-LS-3)

4 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

2.4 CFA references

Copies of the following standards may be obtained from the CFA at www.compactflash.org.

Video Performance Guarantee Profile 1 Revision 1.0 (VPG1), May 24, 2011

2.5 IETF references

Copies of the following approved IETF standards may be obtained through the Internet Engineering Task
Force (IETF) at www.ietf.org.

RFC 791, Internet Protocol - DARPA Internet Program - Protocol Specification

RFC 1321, The MD5 Message-Digest Algorithm

RFC 2104, HMAC: Keyed-Hashing for Message Authentication

RFC 2279, UTF-8, a transformation format of ISO 10646

RFC 2410, The NULL Encryption Algorithm and Its Use With IPsec

RFC 2437, PKCS #1: RSA Cryptography Specifications Version 2.0

RFC 2616, Hypertext Transfer Protocol - HTTP/1.1

RFC 3281, An Internet Attribute Certificate Profile for Authorization

RFC 3526, More Modular Exponential (MODP) Diffie-Hellman groups for Internet Key Exchange (IKE)

RFC 3566, The AES-XCBC-MAC-96 Algorithm and Its Use With IPsec

RFC 3602, The AES-CBC Cipher Algorithm and Its Use with IPsec

RFC 3766, Determining Strengths For Public Keys Used For Exchanging Symmetric Keys

RFC 4086, Randomness Requirements for Security

RFC 4106, The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload

RFC 4291, IP Version 6 Addressing Architecture

RFC 4303, IP Encapsulating Security Payload (ESP)

RFC 4306, Internet Key Exchange (IKEv2) Protocol

RFC 4309, Using Advanced Encryption Standard (AES) CCM Mode with IPsec Encapsulating Security
Payload

RFC 4434, The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE)

RFC 4595, Use of IKEv2 in the Fibre Channel Security Association Management Protocol

Working Draft SCSI Primary Commands - 4 (SPC-4) 5

T10/BSR INCITS 513 Revision 37 17 May 2014

RFC 4718, IKEv2 Clarifications and Implementation Guidelines

RFC 4753, ECP Groups for IKE and IKEv2

RFC Errata for RFC 4753, http://rfc-editor.org/errata_search.php?rfc=4753

RFC 4754, IKE and IKEv2 Authentication Using the Elliptic Curve Digital Signature Algorithm (ECDSA)

RFC 4868, Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPsec

RFC 5280, Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile

RFC 5282, Using Authenticated Encryption Algorithms with the Encrypted Payload of the Internet Key
Exchange version 2 (IKEv2) Protocol

RFC 7143, iSCSI Protocol (Consolidated)

RFC 7144, Internet Small Computer Systems Interface (iSCSI) SCSI Features Update

2.6 NIST references

Copies of the following approved and draft Federal Information Processing Standards (FIPS) standards may
b e o b t a i n e d t h r o u g h t h e N a t i o n a l I n s t i t u t e o f St a n d a r d s a n d Te c h n o l o g y ( N I S T ) a t
http://csrc.nist.gov/publications/fips/index.html.

NIST SP (Special Publication) 800-38D, R e c o m m e n d a t i o n f o r B l o c k C i p h e r M o d e s o f O p e r a t i o n :

Galois/Counter (GCM) Mode for Confidentiality and Authentication and GMAC

NIST SP 800-90 A, Recommendation for Random Number Generation Using Deterministic Random Bit
Generators

FIPS 140-2, Security Requirements for Cryptographic Modules

FIPS 140-2, Annex C: Approved Random Number Generators

FIPS 140-3, Security Requirements for Cryptographic Modules (in development)

FIPS 180-4, Secure Hash Standard

FIPS 198-1, The Keyed-Hash Message Authentication Code (HMAC)

2.7 USB Implementers Forum references

Copies of the following specifications may be obtained from USB-IF at www.usb.org.

Universal Serial Bus 3.0 Specification Revision 1.0 (USB-3), November 12, 2008

6 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3 Definitions, symbols, abbreviations, and conventions

3.1 Definitions

3.1.1 access control list (ACL)

data used by a SCSI target device to configure access rights for initiator ports according to the access controls
state of the SCSI target device
Note 1 to entry: See 8.3.1.3.

3.1.2 access control list entry (ACE)

one entry in the access control list (see 3.1.1)

3.1.3 access controls

SCSI target device feature that restricts initiator port access to specific logical units
Note 1 to entry: Information is modified about logical units in the parameter data of the INQUIRY command
(see 6.6) and REPORT LUNS command (see 6.33).
Note 2 to entry: See 8.3.1.

3.1.4 access controls coordinator

entity within a SCSI target device that coordinates the management and enforcement of access controls (see
8.3.1) for all logical units within the SCSI target device
Note 1 to entry: The access controls coordinator is always addressable through the ACCESS CONTROLS
well known logical unit (see 8.3) and LUN 0.

3.1.5 active power condition

power condition in which a device server is capable of completing the processing of all its supported
commands
Note 1 to entry: See 5.11.4.

3.1.6 additional authenticated data (AAD)

bytes of data input to a combined mode encryption algorithm (e.g., AES-GCM) as part of integrity checking
computations (e.g., the IKEv2-SCSI Encrypted payload (see 7.7.3.5.11) uses AAD)

3.1.7 additional sense code

combination of the ADDITIONAL SENSE CODE field and the ADDITIONAL SENSE CODE QUALIFIER field in sense data
(see 4.5)

3.1.8 alias list

list of alias values (see 3.1.9) and their associated designations (see 3.1.41) maintained by the device server
and managed by the CHANGE ALIASES command (see 6.2) and REPORT ALIASES command (see 6.30)

3.1.9 alias value

numeric value associated to a designation (see 3.1.41) in the alias list (see 3.1.8)
Note 1 to entry: Used in command or parameter data to reference a SCSI target device or SCSI target port.
Note 2 to entry: See 6.2.2.

3.1.10 application client

object that is the source of SCSI commands
Note 1 to entry: See SAM-5.

Working Draft SCSI Primary Commands - 4 (SPC-4) 7

T10/BSR INCITS 513 Revision 37 17 May 2014

3.1.11 ASCII format list log parameter

log parameter that contains ASCII data in a list log parameter format
Note 1 to entry: See 7.3.2.2.2.4.

3.1.12 attribute
single unit of MAM (see 3.1.87) information

3.1.13 auto contingent allegiance (ACA)

task set condition established following the return of CHECK CONDITION status if the NACA bit is set to one in
the CONTROL byte
Note 1 to entry: See SAM-5.

3.1.14 background function

background scan operation (see SBC-3) or device specific background function (see 5.3)

3.1.15 binary format list log parameter

log parameter that contains binary data in a list log parameter format
Note 1 to entry: See 7.3.2.2.2.5.

3.1.16 blocked command

command that is in the blocked state (see SAM-5)
Note 1 to entry: Commands become blocked if an ACA condition occurs and the blocked state ends when the
ACA condition is cleared.

3.1.17 bounded data counter log parameter

log parameter that contains one saturating counter (see 3.1.133) value for which the establishment of
thresholds is allowed
Note 1 to entry: Effects on other log parameters in the same log page are determined by the format and
linking field in the parameter control byte.
Note 2 to entry: See 7.3.2.2.2.2.

3.1.18 byte (B)

sequence of eight contiguous bits considered as a unit

3.1.19 cache memory

temporary and often volatile data storage area outside the area accessible by application clients
Note 1 to entry: Cache memory may contain a subset of the data stored in the non-volatile data storage area.

3.1.20 CbCS capability

descriptor that specifies access to a logical unit or volume (see SSC-4) for specific commands
Note 1 to entry: A CbCS capability is a component of a CbCS credential (see 3.1.20) and a CbCS extension
descriptor (see 5.13.6.7.16).
Note 2 to entry: See 5.13.6.7.13.

3.1.21 CbCS capability key

shared key (see 3.1.158) that is cryptographically associated with a specific CbCS capability (see 3.1.20)

8 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3.1.22 CbCS credential

combination of a CbCS capability (see 3.1.20) and a CbCS capability key (see 3.1.21)
Note 1 to entry: A CbCS credential is returned by a RECEIVE CREDENTIAL command (see 6.26).
Note 2 to entry: See 5.13.6.7.12.

3.1.23 CbCS Management Application Client class

CbCS (see 5.13.6.7) class whose objects manage, or an object that manages CbCS shared keys (see
5.13.6.7.11)
Note 1 to entry: See 5.13.6.7.4.

3.1.24 CbCS Management Device Server class

CbCS (see 5.13.6.7) class whose objects prepare, or an object that prepares CbCS credentials (see
5.13.6.7.12)
Note 1 to entry: A CbCS credential is prepared in response to a RECEIVE CREDENTIAL command (see
6.26) request from a secure CDB originator (see 5.13.6.7.5).
Note 2 to entry: See 5.13.6.7.3.

3.1.25 CbCS master key

shared key (see 3.1.158) from which CbCS working keys (see 3.1.28) are derived that is composed of an
authentication key component and a generation key component
Note 1 to entry: See 5.13.6.7.11.

3.1.26 CbCS security token

random nonce (see 3.1.118) that is chosen by the enforcement manager (see 5.13.6.7.7) for a given I_T
nexus and returned to a secure CDB originator (see 5.13.6.7.5)
Note 1 to entry: See 5.13.6.7.10.

3.1.27 CbCS working keys

shared keys (see 3.1.158) that are used to cryptographically associate a CbCS capability (see 3.1.20) with a
CbCS capability key (see 3.1.21)
Note 1 to entry: See 5.13.6.7.11.

3.1.28 code set enumeration

coded value used in one field to indicate the format of data in other fields or descriptors
Note 1 to entry: See 4.3.3.

3.1.29 command
request describing a unit of work to be performed by a device server
Note 1 to entry: See SAM-5.

3.1.30 command descriptor block (CDB)

structure used to communicate commands from an application client to a device server (see 4.2)
Note 1 to entry: A CDB may have a fixed length of up to 16 bytes or a variable length of between 12 and 260
bytes.

3.1.31 command standard

SCSI standard that defines the model, commands, and parameter data for a device type (e.g., SBC-3, SSC-4,
SMC-3, MMC-6, or SES-2)

Working Draft SCSI Primary Commands - 4 (SPC-4) 9

T10/BSR INCITS 513 Revision 37 17 May 2014

3.1.32 company_id
synonym for OUI (see 3.1.98)

3.1.33 copy manager

object (see SAM-5) that processes third-party copy commands (see 5.16.3) and manages copy operations
(see 5.16.4.3)

3.1.34 copy operation

foreground or background operation that results from the processing of a third-party copy command
Note 1 to entry: See 5.16.4.3.

3.1.35 copy source or copy destination (CSCD)

source or destination of a copy operation (see 6.4.6) performed by an EXTENDED COPY(LID4) command
(see 6.4) or an EXTENDED COPY(LID1) command (see 6.5)

3.1.36 cryptographic command sequence (CCS)

defined sequence of SECURITY PROTOCOL IN commands (see 6.40) and SECURITY PROTOCOL OUT
commands (see 6.41) that realize the cryptographic protocol of a specified security operation (e.g., the
SECURITY PROTOCOL IN commands and SECURITY PROTOCOL OUT commands in the Key Exchange
step and Authentication step, if any, of an IKEv2-SCSI (see 3.1.66) SA creation transaction (see 3.1.127))

3.1.37 data counter log parameter

bounded data counter log parameter (see 7.3.2.2.2.2) or unbounded data counter log parameter (see
7.3.2.2.2.3)

3.1.38 Data-In Buffer

buffer specified by the application client to receive data from the device server during the processing of a
command
Note 1 to entry: See SAM-5.

3.1.39 Data-Out Buffer

buffer specified by the application client to supply data that is sent from the application client to the device
server during the processing of a command
Note 1 to entry: See SAM-5.

3.1.40 deferred error

CHECK CONDITION status and sense data that is returned as the result of an error or exception condition
that occurred during processing of a previous command for which GOOD status or CONDITION MET status
has already been returned
Note 1 to entry: See 4.5.7.

3.1.41 designation
when used in reference to access controls, name and optional identifier information that specifies a SCSI
target device or SCSI target port for association with an alias value (see 3.1.9) in the alias list (see 3.1.8) as
described in 6.2.2; otherwise, distinguishing name, identifier, or title

3.1.42 device server

object within a logical unit that processes SCSI commands according to the rules of command management
Note 1 to entry: See SAM-5.

10 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3.1.43 device service request

request, submitted by an application client, conveying a SCSI command to a device server
Note 1 to entry: See SAM-5.

3.1.44 device service response

response returned to an application client by a device server on completion of a SCSI command
Note 1 to entry: See SAM-5.

3.1.45 device type

type of peripheral device (i.e., device model) implemented by the device server and indicated to the appli-
cation client by the contents of the PERIPHERAL DEVICE TYPE field in the standard INQUIRY data (see 6.6.2)

3.1.46 element
addressable physical component of a medium changer SCSI device that may serve as the location of a
removable unit of data storage medium
Note 1 to entry: See SMC-3.

3.1.47 enabled command state

command state in which a command may make progress towards completion
Note 1 to entry: No other command state allows a command to make progress towards completion.
Note 2 to entry: See SAM-5.

3.1.48 Encapsulating Security Payload for SCSI (ESP-SCSI)

method for transferring encrypted and/or integrity checked parameter data in Data-In Buffers and/or Data-Out
Buffers based on Encapsulating Security Payload (see RFC 4303)
Note 1 to entry: See 5.13.7.

3.1.49 Enforcement Manager class

command security (see 5.13.6) class whose objects are, or an object that is consulted by the Secure CDB
Processor class (see 3.1.146) or Secure CDB Processor class objects to determine if the processing of a
command is permitted or prohibited
Note 1 to entry: The Enforcement Manager class is equivalent to the Policy Enforcement Point in the policy
model defined by RFC 2753 and similar policy-based authorization standards.
Note 2 to entry: See 5.13.6.4.

3.1.50 Error history I_T nexus

I_T nexus for which the device server has reserved access to the error history snapshot (see 3.1.51)

3.1.51 Error history snapshot

contents of the error history at a specific point in time
Note 1 to entry: See 5.5.2.

3.1.52 Extended CDB (XCDB)

CDB that contains another CDB and additional information to support extra processing (e.g., security
features)
Note 1 to entry: See 4.2.4.

Working Draft SCSI Primary Commands - 4 (SPC-4) 11

T10/BSR INCITS 513 Revision 37 17 May 2014

3.1.53 Extended Unique Identifier, a 48-bit globally unique identifier (EUI-48)

48-bit identifier that is globally unique
Note 1 to entry: The IEEE maintains a tutorial describing EUI-48 at
http://standards.ieee.org/regauth/oui/tutorials/EUI48.html.

3.1.54 Extended Unique Identifier, a 64-bit globally unique identifier (EUI-64)

64-bit identifier that is globally unique
Note 1 to entry: The IEEE maintains a tutorial describing EUI-64 at
http://standards.ieee.org/regauth/oui/tutorials/EUI64.html.

3.1.55 faulted I_T nexus

I_T nexus on which a CHECK CONDITION status was returned that resulted in the establishment of an ACA;
the faulted I_T nexus condition is cleared when the ACA condition is cleared
Note 1 to entry: See SAM-5.

3.1.56 field
group of one or more contiguous bits, a part of a larger structure such as a CDB (see 3.1.30) or sense data
(see 3.1.154)

3.1.57 hard reset

condition resulting from the events defined by SAM-5 in which the SCSI device performs the hard reset opera-
tions described in SAM-5, this standard, and the applicable command standards

3.1.58 hashed message authentication code (HMAC)

type of message authentication code that is calculated using the cryptographic hash function as defined in
FIPS 198-1 (see 2.6) in combination with a secret key

3.1.59 host
SCSI device with the characteristics of a primary computing device
Note 1 to entry: A host is typically a personal computer, workstation, server, minicomputer, mainframe
computer, or auxiliary computing device.
Note 2 to entry: A host includes one or more SCSI initiator devices.

3.1.60 IEEE company_id

synonym for OUI (see 3.1.98)

3.1.61 I_T nexus

nexus between a SCSI initiator port and a SCSI target port
Note 1 to entry: See SAM-5.

3.1.62 I_T nexus loss

condition resulting from the events defined by SAM-5
Note 1 to entry: In response to this condition, the SCSI device performs the I_T nexus loss operations
described in SAM-5, this standard, and other applicable standards.

3.1.63 I_T_L nexus

nexus between a SCSI initiator port, a SCSI target port, and a logical unit
Note 1 to entry: See SAM-5.

12 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3.1.64 I_T_L_Q nexus transaction

information transferred between SCSI ports in a single data structure with defined boundaries (e.g., an infor-
mation unit)

3.1.65 idle power condition

power condition in which a device server is capable of completing the processing of all its supported
commands, except those that require the logical unit be in the active power condition (see 3.1.5) to be capable
of completing the command with GOOD status
Note 1 to entry: See 5.11.5.

3.1.66 IKEv2-SCSI
Internet Key Exchange protocol version 2 for SCSI
Note 1 to entry: See 5.13.4.

3.1.67 IKEv2-SCSI keys

shared keys (see 3.1.158) used to provide security for IKEv2-SCSI operations (e.g., creation and deletion of
the SA)
Note 1 to entry: IKEv2-SCSI keys used after SA creation is complete are maintained in the MGMT_DATA SA
parameter (see 3.1.130).
Note 2 to entry: The shared key names used by IKEv2-SCSI are listed in 5.13.4.4.

3.1.68 IKEv2-SCSI CCS

CCS (see 3.1.36) that is the Key Exchange step and Authentication step, if any, of an IKEv2-SCSI (see
3.1.66) SA creation transaction (see 3.1.127)

3.1.69 information unit (IU)

delimited and sequenced set of information in a format appropriate for transport by the service delivery
subsystem (e.g., a CDB for a specific SCSI command)

3.1.70 initiator port

synonymous with SCSI initiator port (see 3.1.138)

3.1.71 initiator port identifier

value by which a SCSI initiator port (see 3.1.138) is referenced within a SCSI domain (see SAM-5)

3.1.72 initiator port name

name (see 3.1.90) of a SCSI initiator port

3.1.73 integrity check value

value used to cryptographically validate the integrity of a specified set of bytes that contain specified data
based on a shared key (see 3.1.158)

3.1.74 internet assigned numbers authority (IANA)

service that assigns and manages registries of code values (i.e., code points) for the IETF (see
http://www.ietf.org) and other users of the public internet (see http://www.iana.org); IANA maintains code
values used by Internet Key Exchange version 2 (IKEv2) at http://www.iana.org/assignments/ikev2-param-
eters

Working Draft SCSI Primary Commands - 4 (SPC-4) 13

T10/BSR INCITS 513 Revision 37 17 May 2014

3.1.75 Internet protocol domain name

name of a computer or hierarchy of computers within the domain name system defined by the IETF (see RFC
1035 and RFC 1591)
Note 1 to entry: IANA maintains a list of domain name assignments at:
http://www.iana.org/assignments/domain-names.

3.1.76 Internet protocol number

coded value assigned to identify protocols that layer on the Internet protocol (see RFC 791)
Note 1 to entry: The Internet protocol number assigned to the transmission control protocol (TCP, see RFC
793) is six.
Note 2 to entry: IANA maintains a list of Internet protocol number assignments at:
http://www.iana.org/assignments/protocol-numbers.

3.1.77 key derivation function (KDF)

algorithm that is used to derive cryptographic keying material from a shared secret and other information

3.1.78 least significant bit (LSB)

in a binary code, the bit or bit position with the smallest numerical weighting in a group of bits that, when taken
as a whole, represent a numerical value
EXAMPLE – In the number 0001b, the bit that is set to one.

3.1.79 left-aligned
type of field containing ASCII data in which unused bytes are placed at the end of the field (i.e., highest offset)
and are filled with ASCII space (20h) characters
Note 1 to entry: See 4.3.1.

3.1.80 logical unit

externally addressable entity within a SCSI target device that implements a SCSI device model and contains a
device server
Note 1 to entry: See SAM-5.

3.1.81 logical unit access control descriptor (LUACD)

structure within an ACE (see 3.1.2) that identifies a logical unit to which access is allowed and specifies the
LUN by which the logical unit is to be accessed (see 8.3.1.3.3)

3.1.82 logical unit inventory

list of the logical unit numbers reported by a REPORT LUNS command (see 6.33)

3.1.83 logical unit number (LUN)

encoded 64-bit identifier for a logical unit
Note 1 to entry: See SAM-5.

3.1.84 logical unit reset

condition resulting from the events defined by SAM-5
Note 1 to entry: In response to this condition, the logical unit performs the logical unit reset operations
described in SAM-5, this standard, and other applicable standards.

3.1.85 low power condition

any power condition other than the active power condition (see 5.11.4)

14 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3.1.86 medium
physical entity that stores data in a nonvolatile manner (i.e., retained through a power cycle) in accordance
with commands processed by the device server

3.1.87 medium auxiliary memory (MAM)

auxiliary memory residing in a volume (e.g., a tape cartridge) that is accessible to the device server
Note 1 to entry: See 7.4.

3.1.88 media changer

device that mechanizes the movement of volumes to and from the SCSI device that records on or reads from
the media
Note 1 to entry: See SMC-3.

3.1.89 most significant bit (MSB)

in a binary code, the bit or bit position with the largest numerical weighting in a group of bits that, when taken
as a whole, represent a numerical value (e.g., in the number 1000b, the bit that is set to one)

3.1.90 name
label of an object that is unique within a specified context and should never change (e.g., the term name and
world wide identifier (WWID) may be interchangeable)

3.1.91 network address authority (NAA)

field within a name (see 3.1.90) that specifies the format and length of that name
Note 1 to entry: See 7.8.6.6 and FC-FS-3.

3.1.92 nexus
relationship between two SCSI devices, and the SCSI initiator port and SCSI target port objects within those
SCSI devices
Note 1 to entry: See SAM-5.

3.1.93 non-volatile cache memory

cache memory (see 3.1.19) that retains data through any power cycle

3.1.94 nonce
value that is used one and only one time to provide uniqueness to a value (e.g., a secure cryptographic key) in
whose derivation it participates or to uniquely identify a single instance of something (e.g., a timestamp)
exchanged between an application client and a device server

3.1.95 null-padded
type of field in which unused bytes are placed at the end of the field (i.e., highest offset) and are filled with
ASCII null (00h) characters
Note 1 to entry: See 4.3.2.

3.1.96 null-terminated
type of field in which the last used byte (i.e., highest offset) is required to contain an ASCII null (00h) character
Note 1 to entry: See 4.3.2.

3.1.97 one
logical true condition of a variable

Working Draft SCSI Primary Commands - 4 (SPC-4) 15

T10/BSR INCITS 513 Revision 37 17 May 2014

3.1.98 organizationally unique identifier (OUI)

numeric identifier that is assigned by the IEEE such that no assigned identifiers are identical
Note 1 to entry: OUI is equivalent to company_id or IEEE company_id.
Note 2 to entry: The IEEE prefers OUI for EUI-48 identifiers (see 3.1.53) and company_id for EUI-64
identifiers (see 3.1.54). However, the numeric identifier is called an OUI when that identifier is assigned by the
IEEE.
Note 3 to entry: The IEEE maintains a tutorial describing the OUI at http://standards.ieee.org/regauth/oui/.

3.1.99 page
regular parameter structure or format used by several commands and identified with a value known as a page
code

3.1.100 peripheral device

object that connects to a logical unit

3.1.101 peripheral device identifying information

value associated with a peripheral device accessed via the REPORT IDENTIFYING INFORMATION
command (see 6.32) and SET IDENTIFYING INFORMATION command (see 6.43)
Note 1 to entry: See 5.6.

3.1.102 peripheral device text identifying information

UTF-8 (see 3.1.186) format string associated with a peripheral device accessed via the REPORT IDENTI-
FYING INFORMATION command (see 6.32) and SET IDENTIFYING INFORMATION command (see 6.43)
Note 1 to entry: See 5.6.

3.1.103 peripheral device type

synonym for device type (see 3.1.45)

3.1.104 persist through power loss

capability associated with some features that allows an application client to request that a device server
maintain information regarding that feature across power failures

3.1.105 persistent reservation holder

I_T nexus(es) that are allowed to release or change a persistent reservation without preempting it
Note 1 to entry: See 5.12.10.

3.1.106 plaintext
unencrypted bytes

3.1.107 power cycle

power being removed from and later applied to a SCSI device

3.1.108 power on
condition resulting from the events defined by SAM-5 in which the SCSI device performs the power on opera-
tions described in SAM-5, this standard, and the applicable command standards

16 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3.1.109 pre-shared key

shared key (see 3.1.158) that is established by a method outside the scope of this standard prior to the initi-
ation of the function that requires its use
Note 1 to entry: The requirements on pre-shared keys that are particular to this standard are described in
5.13.4.3.2.
Note 2 to entry: Some of the RFCs referenced by this standard use the name pre-shared secret for the same
information that this standard calls a pre-shared key.

3.1.110 primary target port asymmetric access state

characteristic that defines the behavior of a target port and the allowable command set for a logical unit when
commands and task management functions are routed through the target port maintaining that state
Note 1 to entry: See 5.15.2.1.

3.1.111 primary target port group

set of target ports that are in the same primary target port asymmetric access state (see 3.1.110) at all times
Note 1 to entry: See 5.15.2.1.

3.1.112 primary target port group asymmetric access state

primary target port asymmetric access state (see 3.1.110) common to the set of target ports in a primary target
port group (see 3.1.111)
Note 1 to entry: See 5.15.2.1.

3.1.113 protection information

one or more fields appended to each logical block that contain a CRC and device type specific information
Note 1 to entry: See SBC-3 and SSC-4.

3.1.114 protocol identifier

coded value used in various fields to identify the SCSI transport protocol to which other fields apply
Note 1 to entry: See 7.6.1.

3.1.115 protocol specific

requirement that is defined by a SCSI transport protocol standard (see 3.1.142)
Note 1 to entry: See SAM-5.

3.1.116 protocol standard

synonymous with SCSI transport protocol standard (see 3.1.142)

3.1.117 proxy token

identifier for a logical unit that may be generated to share access to that logical unit in the presence of access
controls
Note 1 to entry: See 8.3.1.6.2.

3.1.118 random nonce

secure random number (see 4.4) that has a negligible chance of repeating and whose uses include providing
significant uniqueness and randomness in cryptographic calculations

3.1.119 request for comment (RFC)

name given to standards developed by the Internet Engineering Task Force (see 2.5)

Working Draft SCSI Primary Commands - 4 (SPC-4) 17

T10/BSR INCITS 513 Revision 37 17 May 2014

3.1.120 registered
condition that exists for an I_T nexus following the successful completion of a PERSISTENT RESERVE OUT
command with a REGISTER service action, REGISTER AND IGNORE EXISTING KEY service action (see
5.12.7), or REGISTER AND MOVE service action (see 5.12.8) and lasting until the registration is removed
(see 5.12.11)

3.1.121 registrant
I_T nexus that is registered (see 3.1.120)

3.1.122 right-aligned
type of field containing ASCII data in which unused bytes are placed at the start of the field (i.e., lowest offset)
and are filled with ASCII space (20h) characters
Note 1 to entry: See 4.3.1.

3.1.123 relative port identifier

identifier for a SCSI port (see 3.1.139) that is unique within a SCSI device (see 3.1.134)
Note 1 to entry: Application clients may use the SCSI Ports VPD page (see 7.8.14) to determine relative port
identifier values.
Note 2 to entry: See SAM-5.

3.1.124 relative initiator port identifier

relative port identifier (see 3.1.123) for a SCSI initiator port (see 3.1.138)

3.1.125 relative target port identifier

relative port identifier (see 3.1.123) for a SCSI target port (see 3.1.141)

3.1.126 ROD token

kind of token (see 3.1.178) that is a representation of data
Note 1 to entry: See 5.16.6.

3.1.127 SA creation transaction

any sequence of SECURITY PROTOCOL IN commands (see 6.40) and SECURITY PROTOCOL OUT
commands (see 6.41) that is used to create an SA between an application client and device server
Note 1 to entry: A CCS (see 3.1.36) is a kind of SA creation transaction.

3.1.128 SA generation
computation and initialization of the SA parameter values (see 3.1.130) required to create an SA (see 3.1.151)
Note 1 to entry: SA generation is performed separately by the application client and device server after all
SCSI commands required to create an SA have been performed without error
Note 2 to entry: See 5.13.4.9.

3.1.129 SA keys
shared keys (see 3.1.158) that are maintained in the USAGE_DATA SA parameter (see 3.1.130)
Note 1 to entry: SA keys are used to provide security for the operations that use the SA (e.g., encryption of
command parameter data).
Note 2 to entry: The shared key names used by IKEv2-SCSI are listed in 5.13.4.4

18 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3.1.130 SA parameters (see 5.13.2.2)

parameters stored by both an application client and a device server
Note 1 to entry: SA parameters are associated with one SA (see 3.1.151) and identified by a pair of SAIs (see
3.1.152).

3.1.131 SA participant
application client or device server that participates in the creation or use of an SA (see 3.1.151)

3.1.132 salt bytes

sequence of bytes whose contents are unpredictable in advance of their use
Note 1 to entry: Salt bytes kept secret prior to their use, and disclosed during their use (e.g., bytes added to a
cryptographic operation to increase the entropy in the result (see RFC 4106)).

3.1.133 saturating counter

counter that remains at its maximum value after reaching its maximum value

3.1.134 SCSI device

device that contains one or more SCSI ports that are each connected to a service delivery subsystem and
supports a SCSI application protocol
Note 1 to entry: See SAM-5.

3.1.135 SCSI device name

name (see 3.1.90) of a SCSI device that is world wide unique within the protocol of a SCSI domain (see
3.1.136) in which the SCSI device has SCSI ports (see 3.1.139)
Note 1 to entry: The SCSI device name may be made available to other SCSI devices or SCSI ports in
protocol specific ways.
Note 2 to entry: See SAM-5.

3.1.136 SCSI domain

interconnection of two or more SCSI devices and a service delivery subsystem

3.1.137 SCSI initiator device

SCSI device (see 3.1.134) containing application clients (see 3.1.10) and SCSI initiator ports (see 3.1.138)
Note 1 to entry: SCSI initiator devices originate device service and task management requests (see SAM-5)
to be processed by a SCSI target device (see 3.1.140) and receive device service and task management
responses from SCSI target devices.
Note 2 to entry: See SAM-5.

3.1.138 SCSI initiator port

SCSI initiator device (see SAM-5) object that acts as the connection between application clients and a service
delivery subsystem through which requests and responses are routed
Note 1 to entry: See SAM-5.

3.1.139 SCSI port

SCSI initiator port (see 3.1.138) or SCSI target port (see 3.1.141)

Working Draft SCSI Primary Commands - 4 (SPC-4) 19

T10/BSR INCITS 513 Revision 37 17 May 2014

3.1.140 SCSI target device

SCSI device (see 3.1.134) containing logical units (see 3.1.80) and SCSI target ports (see 3.1.141)
Note 1 to entry: SCSI target devices receive device service and task management requests (see SAM-5) for
processing and send device service and task management responses to SCSI initiator devices.
Note 2 to entry: See SAM-5.

3.1.141 SCSI target port

SCSI target device (see SAM-5) object that acts as the connection between device servers and task
managers and a service delivery subsystem through which requests and responses are routed
Note 1 to entry: See SAM-5.

3.1.142 SCSI transport protocol standard

SCSI standard that defines a SCSI transport protocol (e.g., FCP-4, SPL-3, SRP, or SBP-3)

3.1.143 secondary target port asymmetric access state

characteristic indicating a condition that affects the way in which an individual target port participates in its
assigned primary target port group (see 3.1.111)
Note 1 to entry: See 5.15.2.1.

3.1.144 secondary target port group

one or more target ports that are in the same secondary target port asymmetric access state (see 3.1.143)
Note 1 to entry: See 5.15.2.1.

3.1.145 Secure CDB Originator class

command security (see 5.13.6) class whose objects are, or an object that is an application client that origi-
nates secure CDBs
Note 1 to entry: See 5.13.6.2.

3.1.146 Secure CDB Processor class

command security (see 5.13.6) class whose objects are, or an object that is a device server that processes
secure CDBs
Note 1 to entry: See 5.13.6.3.

3.1.147 Secure Content Storage Association (SCSA)

organization that develops specifications for protecting digital media content
Note 1 to entry: See http://www.scsallc.com.

3.1.148 Secure Digital Card Association (SD Card)

organization that establishes and maintains standards for secure digital memory card applications
Note 1 to entry: See http://www.sdcard.org/.

3.1.149 secure hash algorithm (SHA)

secure hash algorithm (e.g., SHA-1) defined in FIPS 180-4, Secure Hash Standard (SHS) (see 2.6)

3.1.150 secure random number

random number that is generated in ways that protect it from security attacks
Note 1 to entry: See 4.4.

20 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3.1.151 security association (SA)

relationship and associated security processing between an application client and a device server that is used
to apply security functions (e.g., integrity checking, encryption) to data that is transferred in either direction
Note 1 to entry: See 5.13.2.

3.1.152 security association index (SAI)

number representing the parameters for an SA as stored internally by the application client or device server
Note 1 to entry: In other security models, this value is called the security parameters index (SPI).
Note 2 to entry: See 5.13.2.

3.1.153 Security Manager class

command security (see 5.13.6) class whose objects maintain, or an object that maintains information about
which secure CDBs may be originated by which secure CDB originator (see 3.1.145) application clients to
which secure CDB processor (see 3.1.146) device servers
Note 1 to entry: The Security Manager responds to requests to allow the origination of secure CDBs from
secure CDB originator application clients, and updates secure CDB permissions and prohibitions in
appropriate enforcement manager (see 3.1.49) members.
Note 2 to entry: The Security Manager is equivalent to the Policy Decision Point in the policy model defined
by RFC 2753 and similar policy-based authorization standards.
Note 3 to entry: See 5.13.6.5.

3.1.154 sense data

data describing an error, exceptional condition, or completion information
Note 1 to entry: A device server delivers sense data to an application client in the same I_T_L_Q nexus
transaction (see 3.1.64) as the status or as parameter data in response to a REQUEST SENSE command
(see 6.39).
Note 2 to entry: See 4.5.

3.1.155 sense key

contents of the SENSE KEY field in sense data (see 4.5)

3.1.156 service action

extension of the operation code (see 4.2.5.1) used to define a command
Note 1 to entry: See 4.2.5.2.

3.1.157 service delivery subsystem

that part of a SCSI domain that transmits service requests to a logical unit or SCSI target device and returns
logical unit or SCSI target device responses to a SCSI initiator device
Note 1 to entry: See SAM-5.

3.1.158 shared key (SK)

cryptographically protected secret (e.g., with more randomness (see RFC 4089) than a password) that is
known only to a defined and limited set of entities (e.g., one application client and one device server)
Note 1 to entry: The shared key names used by IKEv2-SCSI are listed in 5.13.4.4.

3.1.159 SK_ai
shared key (see 3.1.158) used for integrity checking data in a Data-Out Buffer (e.g., integrity checking the
Encrypted payload in an IKEv2-SCSI Authentication step SECURITY PROTOCOL OUT command (see
5.13.4.7.2))

Working Draft SCSI Primary Commands - 4 (SPC-4) 21

T10/BSR INCITS 513 Revision 37 17 May 2014

3.1.160 SK_ar
shared key (see 3.1.158) used for integrity checking data in a Data-In Buffer (e.g., integrity checking the
Encrypted payload in an IKEv2-SCSI Authentication step SECURITY PROTOCOL IN command (see
5.13.4.7.3))

3.1.161 SK_d
shared key (see 3.1.158) KDF input material use to generate the shared keys stored in the KEYMAT SA
Parameter (see 3.1.130)

3.1.162 SK_ei
shared key (see 3.1.158) used for encrypting data in a Data-Out Buffer (e.g., encrypting the Encrypted
payload in an IKEv2-SCSI Authentication step SECURITY PROTOCOL OUT command (see 5.13.4.7.2))

3.1.163 SK_er
shared key (see 3.1.158) used for encrypting data in a Data-In Buffer (e.g., encrypting the Encrypted payload
in an IKEv2-SCSI Authentication step SECURITY PROTOCOL IN command (see 5.13.4.7.3))

3.1.164 SK_pi
shared key (see 3.1.158) used to construct the IKEv2-SCSI Data-Out Buffer Authentication payload (see
5.13.4.7.2)

3.1.165 SK_pr
shared key (see 3.1.158) used to construct the IKEv2-SCSI Data-In Buffer Authentication payload (see
5.13.4.7.3)

3.1.166 standby power condition

power condition in which a device server is capable of completing the processing of all its supported
commands, except those that require the logical unit be in the idle power condition (see 3.1.65) or active
power condition (see 3.1.5) to be capable of completing the command with GOOD status
Note 1 to entry: See 5.11.6.

3.1.167 status
one byte of response information that contains a coded value defined in SAM-5, transferred from a device
server to an application client upon completion of each command
Note 1 to entry: See SAM-5.

3.1.168 storage networking industry association (SNIA)

organization that develops and promotes standards for storage management and other storage-related
functions
Note 1 to entry: See http://www.snia.org/.

3.1.169 system
one or more SCSI domains operating as a single configuration

3.1.170 target port

synonymous with SCSI target port (see 3.1.141)

3.1.171 target port asymmetric access state

primary target port asymmetric access state (see 3.1.110) or secondary target port asymmetric access state
(see 3.1.143)

3.1.172 target port group

primary target port group (see 3.1.111) or secondary target port group (see 3.1.144)

22 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3.1.173 target port identifier

value by which a SCSI target port (see 3.1.141) is referenced within a SCSI domain (see SAM-5)

3.1.174 target port name

name (see 3.1.90) of a SCSI target port

3.1.175 task set

group of commands within a logical unit, whose interaction is dependent on the task management (i.e.,
queuing) and ACA rules
Note 1 to entry: The Control mode page (see 7.5.8) defines management capabilities for task sets.
Note 2 to entry: See SAM-5.

3.1.176 TCP port numbers

one of the data necessary to establish a TCP connection
Note 1 to entry: TCP port numbers may be assigned to protocols that layer on TCP by IANA. IANA maintains
a list of TCP port number assignments at http://www.iana.org/assignments/port-numbers.

3.1.177 third-party command

command sent to one SCSI device requesting that an operation be performed involving two other SCSI
devices (e.g., the EXTENDED COPY command may perform copy operations between two or more SCSI
devices none of which are the SCSI device to which the EXTENDED COPY command was sent)

3.1.178 token
a representation of a collection of data (e.g., management data, security data)

3.1.179 Trusted Computing Group (TCG)

organization that develops and promotes open standards for hardware-enabled trusted computing and
security technologies
Note 1 to entry: See https://www.trustedcomputinggroup.org.

3.1.180 unbounded data counter log parameter

log parameter that contains one or more saturating counter values (see 3.1.133) or wrapping counter values
(see 3.1.190) that do not affect other log parameters in the same log page and for which the establishment of
thresholds is not allowed
Note 1 to entry: See 7.3.2.2.2.3.

3.1.181 unit attention condition

asynchronous status information that a logical unit establishes to report to the initiator ports associated with
one or more I_T nexuses
Note 1 to entry: See SAM-5.

3.1.182 universal time (UT)

time at longitude zero, colloquially known as Greenwich Mean Time
Note 1 to entry: See http://www.usno.navy.mil/USNO/astronomical-applications/astronomical-information-cent
er/universal-time.

3.1.183 URI Schemes

syntax specifications for UTF-8 (see 3.1.186) format strings that identify resources (see RFC 3986)
Note 1 to entry: IANA maintains a list of schemes for URI and URL names at:
http://www.iana.org/assignments/uri-schemes.

Working Draft SCSI Primary Commands - 4 (SPC-4) 23

T10/BSR INCITS 513 Revision 37 17 May 2014

3.1.184 user data

data contained in logical blocks (e.g., see SBC-3) that is not protection information (see 3.1.113)
Note 1 to entry: Each command standard (see 3.1.31) may provide its own definition of user data.

3.1.185 user data segment

contiguous sequence of logical blocks
Note 1 to entry: See SBC-3.

3.1.186 UTF-8
character set that is a transformation format of the character set defined by ISO 10646
Note 1 to entry: See RFC 2279.

3.1.187 volatile cache memory

cache memory (see 3.1.19) that does not retain data through power cycles

3.1.188 well known logical unit

logical unit that only does specific functions in a SCSI target device
Note 1 to entry: Well known logical units allow an application client to issue requests to receive and manage
specific information usually relating to a SCSI target device.
Note 2 to entry: See clause 8 and SAM-5.

3.1.189 word
sequence of 16 contiguous bits considered as a unit

3.1.190 wrapping counter

counter that wraps back to zero after reaching its maximum value

3.1.191 zero
logical false condition of a variable

3.1.192 zero-padded
type of field in which unused bytes are placed at the end of the field (i.e., highest offset) and are filled with
zeros
Note 1 to entry: See 4.3.2.

24 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3.2 Abbreviations and symbols

3.2.1 Abbreviations

See Clause 2 for abbreviations of standards bodies (e.g., ISO). Abbreviations used in this standard:

Abbreviation Meaning
AAD Additional Authenticated Data (see 3.1.6)
ACE Access Control list Entry (see 3.1.2)
ACL Access Control List (see 3.1.1)
ACA Auto Contingent Allegiance (see 3.1.13)
ADC-3 Automation/Drive Interface - Commands -3
ADT-2 Automation/Drive Interface - Transport Protocol -2
AES Advanced Encryption Standards
AES-GCM Advanced Encryption Standard - Galois Counter Mode (see RFC 4106)
ASC Additional Sense Code (see 4.5)
ASCII American Standard Code for Information Interchange (see 2.2)
ASCQ Additional Sense Code Qualifier (see 4.5)
ASN.1 Abstract Syntax Notation One (see 2.2)
ATA AT Attachment (see www.t13.org)
ATAPI AT Attachment with Packet Interface (see www.t13.org)
CbCS Capability-based Command Security (see 5.13.6.7)
CCS Cryptographic Command Sequence (see 3.1.36)
CDB Command Descriptor Block (see 3.1.30)
CFA CompactFlash Association (see 2.4)
CRC Cyclic Redundancy Check
CSCD Copy Source or Copy Destination (see 3.1.35)
CSEC Communications Security Establishment Canada
D_ID Destination Identifier (defined in FC-FS-3)
ECP Elliptic Curve group modulo Prime (see RFC 4753)
ECDSA Elliptic Curve Digital Signature Algorithm (see RFC 4754)
ESP-SCSI Encapsulating Security Payload for SCSI (see 3.1.48)
EUI-48 Extended Unique Identifier, a 48-bit globally unique identifier (see 3.1.53)
EUI-64 Extended Unique Identifier, a 64-bit globally unique identifier (see 3.1.54)
FC-FS-3 Fibre Channel Framing and Signaling Interface-3
FC-LS-2 Fibre Channel Link Services-2
FC-SP-2 Fibre Channel Security Protocols-2
FCP-4 Fibre Channel Protocol for SCSI -4
FIPS Federal Information Processing Standard
HMAC Hashed Message Authentication Code (see 3.1.58)
HTTP Hypertext Transfer Protocol (see RFC 2616)
IANA Internet Assigned Numbers Authority (see 3.1.74)
ID Identifier or Identification
IEEE Institute of Electrical and Electronics Engineers
IKEv2 Internet Key Exchange version 2 (see 2.5)
IP Internet Protocol (see 2.5)
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
iSCSI Internet SCSI (see 2.5)
IU Information Unit

Working Draft SCSI Primary Commands - 4 (SPC-4) 25

T10/BSR INCITS 513 Revision 37 17 May 2014

Abbreviation Meaning
KDF Key Derivation Function (see 3.1.77)
LBA Logical Block Address
LID1 List Identifier is 1 byte (i.e., a third-party copy command with a one-byte LIST IDENTI-
FIER field)
LID4 List Identifier is 4 bytes (i.e., a third-party copy command with a four-byte LIST IDEN-
TIFIER field)
LSB Least Significant Bit (see 3.1.78)
LUACD Logical Unit Access Control Descriptor (see 3.1.81)
LUN Logical Unit Number (see 3.1.83)
MAC Message Authentication Code
MAM Medium Auxiliary Memory (see 3.1.87)
MMC-6 SCSI Multi-Media Commands - 6 and MMC-6 Amendment 1
MODP Modular exponential (see RFC 3526)
MSB Most Significant Bit (see 3.1.89)
NAA Network Address Authority (see 3.1.91)
OCRW SCSI Specification for Optical Card Reader/Writer
OSD Object-based Storage Devices Commands
OUI Organizationally Unique Identifier (see 3.1.98)
PKI Public Key Infrastructure (see RFC 5280)
PRF Pseudo-Random Function (see RFC 4306)
RAID Redundant Array of Independent Disks
RBC SCSI Reduced Block Commands
RDMA Remote Direct Memory Access (see SRP)
RFC Request For Comments (see 3.1.119)
ROD Representation Of Data (see 5.16.6)
SA Security Association (see 3.1.151)
SAI Security Association Index (see 3.1.152)
SAM-2 SCSI Architecture Model -2
SAM-4 SCSI Architecture Model -4
SAM-5 SCSI Architecture Model -5
SAS-2 Serial Attached SCSI - 2
SAT-3 SCSI / ATA Translation -3
SAUT SA Usage Type (see 7.7.3.5.14)
SBC-2 SCSI Block Commands -2
SBC-3 SCSI Block Commands -3
SBC-4 SCSI Block Commands -4
SBP-3 Serial Bus Protocol -3
SCC-2 SCSI Controller Commands -2
SCSA Secure Content Storage Association
SCSI Small Computer System Interface
SES-2 SCSI Enclosure Services -2
SES-3 SCSI Enclosure Services -3
SHA-1 Secure Hash Algorithm, 160 bits (see 3.1.149)
SHA-256 Secure Hash Algorithm, 256 bits (see 3.1.149)
SHA-384 Secure Hash Algorithm, 384 bits (see 3.1.149)
SHA-512 Secure Hash Algorithm, 512 bits (see 3.1.149)
SK Shared Key (see 3.1.158)
SMC-3 SCSI Media Changer Commands -3
SNIA Storage Networking Industry Association (see 3.1.168)

26 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Abbreviation Meaning
SPC-2 SCSI Primary Commands -2
SPC-3 SCSI Primary Commands -3
SPC-4 SCSI Primary Commands -4 (this standard)
SPI-5 SCSI Parallel Interface -5
SPL-2 SAS Protocol Layer -2
SPL-3 SAS Protocol Layer -3
SRP SCSI RDMA Protocol
SSC-4 SCSI Stream Commands -4
SSC-5 SCSI Stream Commands -5
TCG Trusted Computing Group (see 3.1.179)
TCP Transmission Control Protocol (see RFC 793)
UFS Universal Flash Storage (developed by JEDEC)
UML Unified Modeling Language (developed by OMG)
URI Uniform Resource Identifier (see RFC 3986 and 3.1.183)
URL Uniform Resource Locator (see RFC 3986 and 3.1.183)
UT Universal time (see 3.1.182)
USB Universal Serial Bus
USB-3 Universal Serial Bus -3 (see 2.7)
VPD Vital Product Data (see 7.8)
VPG1 Video Performance Guarantee Profile 1 (see 2.4)
VS Vendor Specific (see 3.3.12)
XCDB Extended CDB (see 3.1.52)
ZBC Zoned Block Commands

3.2.2 Symbols

Symbols used in this standard:

Symbol Meaning
|| concatenation
n/a not applicable
x, xx any valid value for a bit or field
& grammatical and
 segment descriptor transfer data (see 3.7.5)

Working Draft SCSI Primary Commands - 4 (SPC-4) 27

T10/BSR INCITS 513 Revision 37 17 May 2014

3.2.3 Mathematical operators

Mathematical operators used in this standard:

Mathematical
operator Meaning
+ plus
– minus
 divided by
 multiplied by
 less than
 less than or equal to
 greater than
greater than or equal to
 not equal to
|| concatenation

3.3 Keywords

3.3.1 invalid
keyword used to describe an illegal or unsupported bit, byte, word, field or code value
Note 1 to entry: Receipt by the device server of an invalid bit, byte, word, field or code value shall be reported
as an error.

3.3.2 mandatory
keyword indicating an item that is required to be implemented as defined in this standard

3.3.3 may
keyword indicating flexibility of choice with no implied preference

3.3.4 may not

keyword indicating flexibility of choice with no implied preference

3.3.5 obsolete
keyword indicating that an item was defined in prior SCSI standards but has been removed from this standard

3.3.6 option, optional

keywords that describe features that are not required to be implemented by this standard
Note 1 to entry: If any optional feature defined by this standard is implemented, then it shall be implemented
as defined in this standard.

3.3.7 prohibited
keyword used to describe a feature, function, or coded value that is defined in a non-SCSI standard (i.e., a
standard that is not a member of the SCSI family of standards) to which this standard makes a normative
reference where the use of said feature, function, or coded value is not allowed for implementations of this
standard

28 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3.3.8 reserved
keyword referring to bits, bytes, words, fields and code values that are set aside for future standardization
Note 1 to entry: A reserved bit, byte, word or field shall be set to zero, or in accordance with a future extension
to this standard.
Note 2 to entry: Recipients are not required to check reserved bits, bytes, words or fields for zero values.
Note 3 to entry: Receipt of reserved code values in defined fields shall be reported as an error.

3.3.9 restricted
keyword referring to bits, bytes, words, and fields that are set aside for other identified standardization
purposes
Note 1 to entry: A restricted bit, byte, word, or field shall be treated as a reserved bit, byte, word or field in the
context where the restricted designation appears.

3.3.10 shall
keyword indicating a mandatory requirement
Note 1 to entry: Designers are required to implement all such mandatory requirements to ensure
interoperability with other products that conform to this standard.

3.3.11 should
keyword indicating flexibility of choice with a strongly preferred alternative

3.3.12 vendor specific (VS)

something (e.g., a bit, field, code value) that is not defined by this standard
Note 1 to entry: Specification of the referenced item is determined by the SCSI device vendor and may be
used differently in various implementations.

3.4 Conventions

Certain words and terms used in this standard have a specific meaning beyond the normal English meaning.
These words and terms are defined either in 3.1 or in the text where they first appear. Names of commands,
statuses, sense keys, and additional sense codes are in all uppercase (e.g., REQUEST SENSE). Lowercase
is used for words having the normal English meaning.

If there is more than one CDB length for a particular command (e.g., MODE SENSE(6) and MODE
SENSE(10)) and the name of the command is used in a sentence without any CDB length descriptor (e.g.,
MODE SENSE), then the condition described in the sentence applies to all CDB lengths for that command.

The names of fields are in small uppercase (e.g., ALLOCATION LENGTH). When a field name is a concatenation
of acronyms, uppercase letters may be used for readability (e.g., NORMACA). Normal case is used when the
contents of a field are being discussed. Fields containing only one bit are usually referred to as the name bit
instead of the name field.

When the value of the bit or field is not relevant, x or xx appears in place of a specific value.

Lists sequenced by lowercase or uppercase letters show no ordering relationship between the listed items.

EXAMPLE 1 – The following list shows no relationship between the colors named:

a) red, specificity one of the following colors:

A) crimson; or

Working Draft SCSI Primary Commands - 4 (SPC-4) 29

T10/BSR INCITS 513 Revision 37 17 May 2014

B) amber;
b) blue; or
c) green.

Lists sequenced by numbers show an ordering relationship between the listed items.

EXAMPLE 2 – The following list shows the order in which a page is meant to be read:

1) top;
2) middle; and
3) bottom.

Lists are associated with an introductory paragraph or phrase, and are numbered relative to that paragraph or
phrase (i.e., all lists begin with an a) or 1) entry).

If a conflict arises between text, tables, or figures, the order of precedence to resolve the conflicts is text; then
tables; and finally figures. Not all tables or figures are fully described in the text. Tables show data format and
values. Notes do not constitute any requirements for implementors.

3.5 Numeric and character conventions

3.5.1 Numeric conventions

A binary number is represented in this standard by any sequence of digits comprised of only the Arabic
numerals 0 and 1 immediately followed by a lower-case b (e.g., 0101b). Underscores or spaces may be
included in binary number representations to increase readability or delineate field boundaries (e.g.,
0 0101 1010b or 0_0101_1010b).

A hexadecimal number is represented in this standard by any sequence of digits comprised of only the Arabic
numerals 0 through 9 and/or the upper-case English letters A through F immediately followed by a lower-case
h (e.g., FA23h). Underscores or spaces may be included in hexadecimal number representations to increase
readability or delineate field boundaries (e.g., B FD8C FA23h or B_FD8C_FA23h).

A decimal number is represented in this standard by any sequence of digits comprised of only the Arabic
numerals 0 through 9 not immediately followed by a lower-case b or lower-case h (e.g., 25).

A range of numeric values is represented in this standard in the form “a to z”, where a is the first value
included in the range, all values between a and z are included in the range, and z is the last value included in
the range (e.g., the representation “0h to 3h” includes the values 0h, 1h, 2h, and 3h).

This standard uses the following conventions for representing decimal numbers:

a) the decimal separator (i.e., separating the integer and fractional portions of the number) is a period;
b) the thousands separator (i.e., separating groups of three digits in a portion of the number) is a space;
c) the thousands separator is used in both the integer portion and the fraction portion of a number; and
d) the decimal representation for a year is 1999 not 1 999.

30 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 1 shows some examples of decimal numbers represented using various conventions.

Table 1 — Numbering conventions examples

French English This standard

0,6 0.6 0.6
3,141 592 65 3.14159265 3.141 592 65
1 000 1,000 1 000
1 323 462,95 1,323,462.95 1 323 462.95

A decimal number represented in this standard with an overline over one or more digits following the decimal
point is a number where the overlined digits are infinitely repeating (e.g., 666.6 means 666.666 666… or 666
2/3 and 12.142 857 means 12.142 857 142 857… or 12 1/7).

3.5.2 Units of measure

This standard represents values using both decimal units of measure and binary units of measure. Values are
represented by the following formats:

a) for values based on decimal units of measure:

1) numerical value (e.g., 100);
2) space;
3) prefix symbol and unit:
1) decimal prefix symbol (e.g., M) (see table 2); and
2) unit abbreviation (e.g., B);
and
b) for values based on binary units of measure:
1) numerical value (e.g., 1 024);
2) space;
3) prefix symbol and unit:
1) binary prefix symbol (e.g., Gi) (see table 2); and
2) unit abbreviation (e.g., b).

Working Draft SCSI Primary Commands - 4 (SPC-4) 31

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 2 compares the prefix, symbols, and power of the binary and decimal units.

Table 2 — Comparison of decimal prefixes and binary prefixes

Decimal Binary

Prefix Prefix Power Prefix Prefix Power

name symbol (base-10) name symbol (base-2)

kilo k 103 kibi Ki 210

mega M 106 mebi Mi 220
giga G 109 gibi Gi 230
tera T 1012 tebi Ti 240
peta P 1015 pebi Pi 250
exa E 1018 exbi Ei 260
zetta Z 1021 zebi Zi 270
yotta Y 1024 yobi Yi 280

3.5.3 Byte encoded character strings conventions

When this standard requires one or more bytes to contain specific encoded characters, the specific characters
are enclosed in single quotation marks. The single quotation marks identify the start and end of the characters
that are required to be encoded but are not themselves to be encoded. The characters that are to be encoded
are shown in the case that is to be encoded.

An ASCII space character (i.e., 20h) may be represented in a string by the character ‘¬’ (e.g., ‘SCSI¬device’).

The encoded characters and the single quotation marks that enclose them are preceded by text that specifies
the character encoding methodology and the number of characters required to be encoded.

EXAMPLE - Using the notation described in this subclause, stating that the eleven ASCII characters ‘SCSI device’
represent encoded characters is the same as writing out the following sequence of byte values: 53h 43h 53h 49h 20h 64h
65h 76h 69h 63h 65h.

3.6 Bit and byte ordering

This subclause describes the representation of fields in a table that defines the format of a SCSI structure
(e.g., the format of a CDB).

If a field consists of more than one bit and contains a single value (e.g., a number), the least significant bit
(LSB) is shown on the right and the most significant bit (MSB) is shown on the left (e.g., in a byte, bit 7 is the
MSB and is shown on the left, and bit 0 is the LSB and is shown on the right). The MSB and LSB are not
labeled if the field consists of 8 or fewer bits.

If a field consists of more than one byte and contains a single value, the byte containing the MSB is stored at
the lowest address and the byte containing the LSB is stored at the highest address (i.e., big-endian byte
ordering). The MSB and LSB are labeled.

32 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If a field consists of more than one byte and always contains multiple fields each with their own values (e.g., a
descriptor), then there is no MSB and LSB of the field itself and thus there are no MSB and LSB labels. Each
individual field has an MSB and LSB that are labeled as appropriate in the table, if any, that describes the
format of the sub-structure having multiple fields.

If a field that consists of more than one byte contains either multiple fields each with their own values or a
single value, then:

a) the MSB and LSB are labeled and they apply as described in this subclause whenever the field
contains a single value; and
b) the labels on constituent fields supersede the single value labels whenever the field contains multiple
fields.

If a field contains a text string (e.g., ASCII or UTF-8), the MSB label is the MSB of the first character and the
LSB label is the LSB of the last character.

When required for clarity, multiple byte fields may be represented with only two rows in a table. This condition
is represented by values in the byte number column not increasing by one in each subsequent table row, thus
indicating the presence of additional bytes.

Working Draft SCSI Primary Commands - 4 (SPC-4) 33

T10/BSR INCITS 513 Revision 37 17 May 2014

3.7 Notation conventions

3.7.1 Notation for procedure calls

In this standard, the model for functional interfaces between objects is a procedure call. Such interfaces are
specified using the following notation:

[Result =] Procedure Name (IN ([input-1] [,input-2] …]), OUT ([output-1] [,output-2] …))

Where:

Result: A single value representing the outcome of the procedure call.

Procedure Name: A descriptive name for the function modeled by the procedure call. When the
procedure call model is used to describe a SCSI transport protocol service, the
procedure name is the same as the service name.

Input-1, Input-2, …: A comma-separated list of names identifying caller-supplied input arguments.

Output-1, Output-2, …: A comma-separated list of names identifying output arguments to be returned by

the procedure call.

"[ …]": Brackets enclosing optional or conditional arguments.

This notation allows arguments to be specified as inputs and outputs. An interface between entities may
require only inputs. If a procedure call has no output arguments, the word OUT, preceding comma, and
associated pair of balanced parentheses are omitted.

The following is an example of a procedure call specification:

Found = Search (IN (Pattern, Item List), OUT ([Item Found]))

Where:

Found = Flag
Flag: if set to one, indicates that a matching item was located.

Input Arguments:

Pattern = … /* Definition of Pattern argument */

Argument containing the search pattern.

Item List = Item<NN> /* Definition of Item List as an array of NN Item arguments*/

Contains the items to be searched for a match.

Output Arguments:

Item Found = Item … /* Item located by the search procedure call */

This argument is only returned if the search succeeds.

34 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3.7.2 Notation for state diagrams

All state diagrams use the notation shown in figure 2.

S0: State 0 S1: State 1

State1

State 0
State 0

Transition destination labels

Figure 2 — Example state diagram

The state diagram is followed by subclauses describing the states and state transitions.

Each state and state transition is described in the list with particular attention to the conditions that cause the
transition to occur and special conditions related to the transition.

A system described in this manner has the following properties:

a) time elapses only within discrete states; and

b) state transitions are logically instantaneous.

Working Draft SCSI Primary Commands - 4 (SPC-4) 35

T10/BSR INCITS 513 Revision 37 17 May 2014

3.7.3 Notation for flowcharts

This standard uses flowcharts that ISO 5807:1995 (R2003) defines as program flowcharts. Figure 3 shows an
example flowchart.

Start

Process

Decision Yes 1

No 2

Process End

Figure 3 — Example flowchart

The following types of symbols are shown in figure 3:

a) a termination (e.g., start and end) symbol;

b) a process symbol;
c) a decision symbol; and
d) a reference (e.g., 1 and 2) symbol.

A termination symbol shows the starting point for the flowchart or the ending point for the flowchart.

A process symbol shows any kind of processing function that occurs as a result of entering this condition from
a previous symbol.

A decision symbol shows a point in the progression of the flowchart from which there is more than one exit
possibility of which only one is satisfied by the condition described within the decision symbol.

A reference symbol shows a connection to or from another flowchart and has the same number in both the
source flowchart and destination flowchart.

36 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3.7.4 Notation for UML figures

3.7.4.1 Introduction

This standard contains class diagram figures that use notation that is based on UML.

Some class diagrams contain constraints or notes that use the notion shown in table 3.

Table 3 — Class diagram constraints and notes notation

Notation Description

The presence of the curly brackets defines constraint that

{constraint text} is a normative requirement. An example of a constraint is
shown in figure 4.

The absence of curly brackets defines a note that is infor-

note text mative. An example of a note is shown in figure 6.

The notation used to denote multiplicity of instances of classes and attributes in class diagrams is shown in
table 4.

Table 4 — Class diagram multiplicity notation

Notation Description
not specified The number of instances of a class or an attribute is not specified.
1 One instance of the class or attribute exists.
0..* Zero or more instances of the class or attribute exist.
1..* One or more instances of the class or attribute exist.
0..1 Zero or one instance of the class or attribute exists.
n..m n to m instances of the class or attribute exist (e.g., 2..8).
x,n..m Multiple disjoint instances of the class or attribute exist (e.g., 2, 8..15).

Class diagrams show:

a) two or more classes (see 3.7.4.2); and

b) one or more of the following relationships between them:
A) association (see 3.7.4.3);
B) aggregation (see 3.7.4.4);
C) generalization (see 3.7.4.5); and
D) dependency (see 3.7.4.6).

Working Draft SCSI Primary Commands - 4 (SPC-4) 37

T10/BSR INCITS 513 Revision 37 17 May 2014

3.7.4.2 Class notation

The notation used for classes is shown in table 5.

Table 5 — Class diagram notation for classes

Notation Description

Class Name Class Name Class Name

A class with no attributes or operations

Class Name Class Name

Attribute01[1] Attribute01[1]
A class with attributes and no operations
Attribute02[1] Attribute02[1]

Class Name

A class with operations and no attributes

Operation01()
Operation02()

Class Name
Attribute01[1]
Attribute02[1] A class with attributes and operations
Operation01()
Operation02()

Class Name
Attribute01[1..*] A class with attributes that have a
Attribute02[1] specified multiplicity (see table 4 in
Operation01() 3.7.4.1) and operations
Operation02()

3.7.4.3 Class association relationships notation

The notation used to denote association (i.e., "knows about") relationships between classes is shown in table
6. Unless the two classes in an association relationship also have an aggregation relationship (see 3.7.4.4),

38 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

association relationships have multiplicity notation (see table 4 in 3.7.4.1) at each end of the relationship line.

Table 6 — Class diagram notation for associations

Notation Description

association name Class A knows about Class B (i.e., read as "Class

Class A Class B A association name Class B") and Class B knows
1..* 0..1 about Class A (i.e., read as "Class B association
multiplicity notation (see table 4) name Class A")

Class B knows about Class A (i.e., read as "Class

Class A Class B B knows about Class A") but Class A does not
1 0..1 know about Class B

role name Class A knows about Class B (i.e., read as "Class

Class A Class B A uses the role name attribute of Class B") but
0..* 0..1 Class B does not know about Class A
Note: The use of role names and association names are optional.

Several example association relationships between classes are shown in figure 4.

Class A Class D 1 0..1 Class C

Attribute 01[1] Attribute aa[1] Attribute 01[1]
Attribute 02[1] Attribute 02[1]
Operation 1()

1 0..*
1..* association name {Constraint between
associations} 0..1 Attribute cc
0..1 0..1
Class E Class F
Class B
Attribute cc[1]
Attribute 03[1]

Figure 4 — Example class association relationships

3.7.4.4 Class aggregation relationships notation

The aggregation relationship is a specific type of association (see table 6). The notation used to denote
aggregation (i.e., "is a part of" or "contains") relationships between classes is shown in table 7. Aggregation

Working Draft SCSI Primary Commands - 4 (SPC-4) 39

T10/BSR INCITS 513 Revision 37 17 May 2014

relationships always include multiplicity notation (see table 4 in 3.7.4.1) at each end of the relationship line.

Table 7 — Class diagram notation for aggregations

Notation Description

The Part class is part of the Whole class and may

Whole Part continue to exist even if the Whole class is
0..* 0..* removed (i.e., read as "the Whole contains the
multiplicity notation (see table 4) Part.")
The Part class is part of the Whole class, shall
Whole Part only belong to one Whole class, and shall not con-
1 0..* tinue to exist if the Whole class is removed (i.e.,
read as "the Whole contains the Part.")

Several example aggregation relationships between classes are shown in figure 5.

Whole Part A 0..* 1 Whole

Attribute 01[1] Attribute A[1] Attribute 01[1]
Attribute 02[1] Attribute 02[1]
Operation 1()

1..* 1 1
{Constraint between
0..1 associations} 1..* 1..*
Part Part B Part C
Attribute 03[1] Attribute B[1] Attribute C[1]

Figure 5 — Example class aggregation relationships

40 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3.7.4.5 Class generalization relationships notation

The notation used to denote generalization (i.e., "is a kind of") relationships between classes is shown in table
8.

Table 8 — Class diagram notation for generalizations

Notation Description
Subclass is a kind of superclass. A subclass
Superclass Subclass shares all the attributes and operations of the
superclass (i.e., the subclass inherits from the
superclass).

Several example generalization relationships between classes are shown in figure 6.

Single superclass — single subclass Multiple superclasses — single subclass

(i.e., multiple inheritance)
Superclass
Attribute 01[1] Superclass A Superclass B
Attribute 02[1] Attribute 1A[1] Attribute 1B[1]
Attribute 2A[1] Attribute 2B[1]

Subclass A
Subclass B
Attribute 03[1]
Attribute 04[1]
Single superclass — multiple subclasses
Superclass
Attribute 01[1]
Attribute 02[1]
There is no significance
to generalizations that are
combined or not combined.
Subclass A Subclass B Subclass C
Attribute A[1] Attribute B[1] Attribute C[1]

Figure 6 — Example class generalization relationships

Working Draft SCSI Primary Commands - 4 (SPC-4) 41

T10/BSR INCITS 513 Revision 37 17 May 2014

3.7.4.6 Class dependency relationships notation

The notation used to denote dependency (i.e., "depends on") relationships between classes is shown in table
9.

Table 9 — Class diagram notation for dependencies

Notation Description

Class A depends on class B. A change in class B

Class A Class B may cause a change in class A.

An example dependency relationship between classes is shown in figure 7.

Dependent Independent

Figure 7 — Example class dependency relationships

3.7.4.7 Object notation

The notation used for objects is shown in table 10.

Table 10 — Notation for objects

Notation Description

label : Class Name Notation for a named object with no attributes

label : Class Name

Attribute01 = x Notation for a named object with attributes
Attribute02 = y

: Class Name Notation for an anonymous object with no attributes

: Class Name
Attribute01 = x Notation for an anonymous object with attributes
Attribute02 = y

42 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

3.7.5 Notation for EXTENDED COPY command segment descriptors

The segment descriptors (see 6.4.6) contained in the parameter list for an EXTENDED COPY command (see
6.4) request the copy manager to perform operations on copy sources and copy destinations. The names of
segment descriptors indicate this by inserting a right pointing arrow (i.e., ) between a brief description of the
copy source and a brief description of the copy destination (e.g., blockstream).

If the segment descriptor requests the transfer of data to the copy destination and another location, an
ampersand (i.e., &) is appended to the copy destination with a description of the additional location following
the ampersand (e.g., blockstream&application client\).

Working Draft SCSI Primary Commands - 4 (SPC-4) 43

T10/BSR INCITS 513 Revision 37 17 May 2014

4 General concepts

4.1 Introduction

This standard defines behaviors that are common to all SCSI device models (see clause 5). This standard
defines the SCSI commands that are basic to more than one device model and the SCSI commands that may
apply to any device model (see clause 6). This standard defines the parameters that are basic to more than
one device model (see clause 7).

4.2 Command Descriptor Block

4.2.1 CDB usage and structure

A command is communicated by sending a CDB to the device server. For some commands, the CDB is
accompanied by a list of parameters in the Data-Out Buffer. See the specific commands for detailed
information.

If an object in a logical unit (e.g., a device server) validates reserved CDB fields and receives a reserved field
within the CDB that is not zero, then the logical unit shall terminate the command with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN
CDB.

If a logical unit receives a reserved CDB code value in a field other than the OPERATION CODE field, then the
logical unit shall terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

The fixed length CDB formats are described in 4.2.2. The variable length CDB formats are described in 4.2.3.
The XCDB format is described in 4.2.4. The CDB fields that are common to most commands are described in
4.2.5. The fields shown in 4.2.2 and 4.2.3 and described in 4.2.5 are used consistently by most commands.
Except for the OPERATION CODE field, the SERVICE ACTION field, if any, and the CONTROL byte, the actual usage
of any field is described in the standard defining that command. If a device server receives a CDB containing
an operation code that is invalid or not supported, the device server shall terminate the command with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set
to INVALID COMMAND OPERATION CODE.

For all commands, if there is an invalid parameter in the CDB, the device server shall terminate the command
without altering the medium.

The XCDB format (see 4.2.4) is a CDB in which additional information is appended to another CDB. The
requirements in this subclause apply to the XCDB and the CDB contained in the XCDB.

44 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

4.2.2 Fixed length CDB formats

4.2.2.1 Formats for 6-byte CDBs

4.2.2.1.1 Generic 6-byte CDB format

Table 11 shows the generic format of a 6-byte CDB.

Table 11 — Generic CDB format for 6-byte commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE

1
•• • miscellaneous CDB information
4
5 CONTROL

The OPERATION CODE field is defined in 4.2.5.1.

Miscellaneous CDB information is defined by the standard that defines the command.

The CONTROL byte is defined in SAM-5.

4.2.2.1.2 Typical 6-byte CDB format

Table 12 shows the typical format of a 6-byte CDB, including the location of:

a) the TRANSFER LENGTH field, if any;

b) the PARAMETER LIST LENGTH field, if any; and
c) the ALLOCATION LENGTH field, if any.

Table 12 — Typical CDB format for 6-byte commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE

1
•• • miscellaneous CDB information
3
TRANSFER LENGTH (if any)
4 PARAMETER LIST LENGTH (if any)
ALLOCATION LENGTH (if any)

5 CONTROL

The OPERATION CODE field is defined in 4.2.5.1.

Miscellaneous CDB information is defined by the standard that defines the command.

The TRANSFER LENGTH field, if any, is defined in 4.2.5.4.

Working Draft SCSI Primary Commands - 4 (SPC-4) 45

T10/BSR INCITS 513 Revision 37 17 May 2014

The PARAMETER LIST LENGTH field, if any, is defined in 4.2.5.5.

The ALLOCATION LENGTH field, if any, is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

4.2.2.2 Formats for 10-byte CDBs

4.2.2.2.1 Generic 10-byte CDB format

Table 13 shows the generic format of a 10-byte CDB, including the location of the SERVICE ACTION field, if any.

Table 13 — Generic CDB format for 10-byte commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE

SERVICE ACTION (if any)

1 miscellaneous CDB information
miscellaneous CDB information (if any)
2
•• • miscellaneous CDB information
8
9 CONTROL

The OPERATION CODE field is defined in 4.2.5.1.

Miscellaneous CDB information is defined by the standard that defines the command.

The SERVICE ACTION field, if any, is defined in 4.2.5.2.

The CONTROL byte is defined in SAM-5.

46 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

4.2.2.2.2 Typical 10-byte CDB format

Table 14 shows the typical format of a 10-byte CDB, including the location of:

a) the SERVICE ACTION field, if any;

b) the LOGICAL BLOCK ADDRESS field, if any;
c) the TRANSFER LENGTH field, if any;
d) the PARAMETER LIST LENGTH field, if any; and
e) the ALLOCATION LENGTH field, if any.

Table 14 — Typical CDB format for 10-byte commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE

1 miscellaneous CDB information SERVICE ACTION (if any)

2 (MSB)
•• • LOGICAL BLOCK ADDRESS (if any)
5 (LSB)
6 miscellaneous CDB information
7 (MSB) TRANSFER LENGTH (if any)
PARAMETER LIST LENGTH (if any)
8 ALLOCATION LENGTH (if any) (LSB)
9 CONTROL

The OPERATION CODE field is defined in 4.2.5.1.

Miscellaneous CDB information is defined by the standard that defines the command.

The SERVICE ACTION field, if any, is defined in 4.2.5.2.

The LOGICAL BLOCK ADDRESS field, if any, is defined in 4.2.5.3.

The TRANSFER LENGTH field, if any, is defined in 4.2.5.4.

The PARAMETER LIST LENGTH field, if any, is defined in 4.2.5.5.

The ALLOCATION LENGTH field, if any, is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

Working Draft SCSI Primary Commands - 4 (SPC-4) 47

T10/BSR INCITS 513 Revision 37 17 May 2014

4.2.2.3 Formats for 12-byte CDBs

4.2.2.3.1 Generic 12-byte CDB format

Table 15 shows the generic format of a 12-byte CDB, including the location of the SERVICE ACTION field, if any.

Table 15 — Generic CDB format for 12-byte commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE

SERVICE ACTION (if any)

1 miscellaneous CDB information
miscellaneous CDB information (if any)
2
•• • miscellaneous CDB information
10
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1.

Miscellaneous CDB information is defined by the standard that defines the command.

The SERVICE ACTION field, if any, is defined in 4.2.5.2.

The CONTROL byte is defined in SAM-5.

48 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

4.2.2.3.2 Typical 12-byte CDB format

Table 16 shows the typical format of a 12-byte CDB, including the location of:

a) the SERVICE ACTION field, if any;

b) the LOGICAL BLOCK ADDRESS field, if any;
c) the TRANSFER LENGTH field, if any;
d) the PARAMETER LIST LENGTH field, if any; and
e) the ALLOCATION LENGTH field, if any.

Table 16 — Typical CDB format for 12-byte commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE

1 miscellaneous CDB information SERVICE ACTION (if any)

2 (MSB)
•• • LOGICAL BLOCK ADDRESS (if any)
5 (LSB)
6 (MSB) TRANSFER LENGTH (if any)
•• • PARAMETER LIST LENGTH (if any)
9 ALLOCATION LENGTH (if any) (LSB)
10 miscellaneous CDB information
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1.

Miscellaneous CDB information is defined by the standard that defines the command.

The SERVICE ACTION field, if any, is defined in 4.2.5.2.

The LOGICAL BLOCK ADDRESS field, if any, is defined in 4.2.5.3.

The TRANSFER LENGTH field, if any, is defined in 4.2.5.4.

The PARAMETER LIST LENGTH field, if any, is defined in 4.2.5.5.

The ALLOCATION LENGTH field, if any, is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

Working Draft SCSI Primary Commands - 4 (SPC-4) 49

T10/BSR INCITS 513 Revision 37 17 May 2014

4.2.2.3.3 MAINTENANCE IN CDB format

Table 17 shows the generic format of a CDB that uses the MAINTENANCE IN operation code. If the
PERIPHERAL DEVICE TYPE field is set to 0Ch (i.e., storage array controller device) or the SCCS bit is set to one in
the standard INQUIRY data (see 6.6.2), then the MAINTENANCE IN service action definition in SCC-2 for the
specified service action, if any, applies.

Table 17 — Generic CDB format for MAINTENANCE IN commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A3h)
1 miscellaneous CDB information SERVICE ACTION

2
•• • miscellaneous CDB information
10
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 17 for any command that
uses the MAINTENANCE IN CDB format.

Miscellaneous CDB information is defined by the standard that defines the command that uses the
MAINTENANCE IN CDB format.

The SERVICE ACTION field is defined in 4.2.5.2, and in the standard that defines the command that uses the
MAINTENANCE IN CDB format. A numeric ordered listing of service actions associated with the
MAINTENANCE IN CDB format is provided in F.3.3.

The CONTROL byte is defined in SAM-5.

4.2.2.3.4 MAINTENANCE OUT CDB format

Table 18 shows the generic format of a CDB that uses the MAINTENANCE OUT operation code. If the
PERIPHERAL DEVICE TYPE field is set to 0Ch (i.e., storage array controller device) or the SCCS bit is set to one in
the standard INQUIRY data (see 6.6.2), then the MAINTENANCE OUT service action definition in SCC-2 for
the specified service action, if any, applies.

Table 18 — Generic CDB format for MAINTENANCE OUT commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A4h)
1 miscellaneous CDB information SERVICE ACTION

2
•• • miscellaneous CDB information
10
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 18 for any command that
uses the MAINTENANCE OUT CDB format.

50 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Miscellaneous CDB information is defined by the standard that defines the command that uses the
MAINTENANCE OUT CDB format.

The SERVICE ACTION field is defined in 4.2.5.2, and in the standard that defines the command that uses the
MAINTENANCE OUT CDB format. A numeric ordered listing of service actions associated with the
MAINTENANCE OUT CDB format is provided in F.3.3.

The CONTROL byte is defined in SAM-5.

4.2.2.3.5 SERVICE ACTION IN(12) CDB format

Table 19 shows the generic format of a CDB that uses the SERVICE ACTION IN(12) operation code.

Table 19 — Generic CDB format for SERVICE ACTION IN(12) commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (ABh)
1 miscellaneous CDB information SERVICE ACTION

2
•• • miscellaneous CDB information
10
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 19 for any command that
uses the SERVICE ACTION IN(12) CDB format.

Miscellaneous CDB information is defined by the standard that defines the command that uses the SERVICE
ACTION IN(12) CDB format.

The SERVICE ACTION field is defined in 4.2.5.2, and in the standard that defines the command that uses the
SERVICE ACTION IN(12) CDB format. A numeric ordered listing of service actions associated with the
SERVICE ACTION IN(12) CDB format is provided in table F.5 (see F.3.4).

The CONTROL byte is defined in SAM-5.

4.2.2.3.6 SERVICE ACTION OUT(12) CDB format

Table 20 shows the generic format of a CDB that uses the SERVICE ACTION OUT(12) operation code.

Table 20 — Generic CDB format for SERVICE ACTION OUT(12) commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A9h)
1 miscellaneous CDB information SERVICE ACTION

2
•• • miscellaneous CDB information
10
11 CONTROL

Working Draft SCSI Primary Commands - 4 (SPC-4) 51

T10/BSR INCITS 513 Revision 37 17 May 2014

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 20 for any command that
uses the SERVICE ACTION OUT(12) CDB format.

Miscellaneous CDB information is defined by the standard that defines the command that uses the SERVICE
ACTION OUT(12) CDB format.

The SERVICE ACTION field is defined in 4.2.5.2, and in the standard that defines the command that uses the
SERVICE ACTION OUT(12) CDB format. A numeric ordered listing of service actions associated with the
SERVICE ACTION OUT(12) CDB format is provided in table F.5 (see F.3.4).

The CONTROL byte is defined in SAM-5.

4.2.2.4 Formats for 16-byte CDBs

4.2.2.4.1 Generic 16-byte CDB format

Table 21 shows the generic format of a 16-byte CDB, including the location of the SERVICE ACTION field, if any.

Table 21 — Generic CDB format for 16-byte commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE

SERVICE ACTION (if any)

1 miscellaneous CDB information
miscellaneous CDB information (if any)
2
•• • miscellaneous CDB information
14
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1.

Miscellaneous CDB information is defined by the standard that defines the command.

The SERVICE ACTION field, if any, is defined in 4.2.5.2.

The CONTROL byte is defined in SAM-5.

52 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

4.2.2.4.2 Typical 16-byte CDB format, if eight-byte LBAs not supported

Table 22 shows the typical format of a 16-byte CDB for commands that do not support eight-byte LBA values,
including the location of:

a) the SERVICE ACTION field, if any;

b) the LOGICAL BLOCK ADDRESS field, if any;
c) the TRANSFER LENGTH field, if any;
d) the PARAMETER LIST LENGTH field, if any; and
e) the ALLOCATION LENGTH field, if any.

Table 22 — Typical CDB format for 16-byte commands, if eight-byte LBAs not supported

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE

1 miscellaneous CDB information SERVICE ACTION (if any)

2 (MSB)
•• • LOGICAL BLOCK ADDRESS (if any)
5 (LSB)
6
•• • miscellaneous CDB information
9
10 (MSB) TRANSFER LENGTH (if any)
•• • PARAMETER LIST LENGTH (if any)
13 ALLOCATION LENGTH (if any) (LSB)
14 miscellaneous CDB information
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1.

Miscellaneous CDB information is defined by the standard that defines the command.

The SERVICE ACTION field, if any, is defined in 4.2.5.2.

The LOGICAL BLOCK ADDRESS field, if any, is defined in 4.2.5.3.

The TRANSFER LENGTH field, if any, is defined in 4.2.5.4.

The PARAMETER LIST LENGTH field, if any, is defined in 4.2.5.5.

The ALLOCATION LENGTH field, if any, is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

Working Draft SCSI Primary Commands - 4 (SPC-4) 53

T10/BSR INCITS 513 Revision 37 17 May 2014

4.2.2.4.3 Typical 16-byte CDB format with eight-byte LBAs supported

Table 23 shows the typical format of a 16-byte CDB for commands that support eight-byte LBA values,
including the location of:

a) the SERVICE ACTION field, if any;

b) the LOGICAL BLOCK ADDRESS field;
c) the TRANSFER LENGTH field, if any;
d) the PARAMETER LIST LENGTH field, if any; and
e) the ALLOCATION LENGTH field, if any.

Table 23 — Typical CDB format for 16-byte commands with eight-byte LBAs supported

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE

1 miscellaneous CDB information SERVICE ACTION (if any)

2 (MSB)
•• • LOGICAL BLOCK ADDRESS
9 (LSB)
10 (MSB) TRANSFER LENGTH (if any)
•• • PARAMETER LIST LENGTH (if any)
13 ALLOCATION LENGTH (if any) (LSB)
14 miscellaneous CDB information
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1.

Miscellaneous CDB information is defined by the standard that defines the command.

The SERVICE ACTION field, if any, is defined in 4.2.5.2.

The LOGICAL BLOCK ADDRESS field is defined in 4.2.5.3.

The TRANSFER LENGTH field, if any, is defined in 4.2.5.4.

The PARAMETER LIST LENGTH field, if any, is defined in 4.2.5.5.

The ALLOCATION LENGTH field, if any, is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

54 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

4.2.2.4.4 SERVICE ACTION IN(16) CDB format

Table 24 shows the generic format of a CDB that uses the SERVICE ACTION IN(16) operation code.

Table 24 — Generic CDB format for SERVICE ACTION IN(16) commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (9Eh)
1 miscellaneous CDB information SERVICE ACTION

2
•• • miscellaneous CDB information
14
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 24 for any command that
uses the SERVICE ACTION IN(16) CDB format.

Miscellaneous CDB information is defined by the standard that defines the command that uses the SERVICE
ACTION IN(16) CDB format.

The SERVICE ACTION field is defined in 4.2.5.2, and in the standard that defines the command that uses the
SERVICE ACTION IN(16) CDB format. A numeric ordered listing of service actions associated with the
SERVICE ACTION IN(16) CDB format is provided in table F.6 (see F.3.4).

The CONTROL byte is defined in SAM-5.

4.2.2.4.5 SERVICE ACTION OUT(16) CDB format

Table 25 shows the generic format of a CDB that uses the SERVICE ACTION OUT(16) operation code.

Table 25 — Generic CDB format for SERVICE ACTION OUT(16) commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (9Fh)
1 miscellaneous CDB information SERVICE ACTION

2
•• • miscellaneous CDB information
14
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 25 for any command that
uses the SERVICE ACTION OUT(16) CDB format.

Miscellaneous CDB information is defined by the standard that defines the command that uses the SERVICE
ACTION OUT(16) CDB format.

The SERVICE ACTION field is defined in 4.2.5.2, and in the standard that defines the command that uses the
SERVICE ACTION OUT(16) CDB format. A numeric ordered listing of service actions associated with the

Working Draft SCSI Primary Commands - 4 (SPC-4) 55

T10/BSR INCITS 513 Revision 37 17 May 2014

SERVICE ACTION OUT(16) CDB format is provided in table F.6 (see F.3.4).

The CONTROL byte is defined in SAM-5.

4.2.2.4.6 SERVICE ACTION BIDIRECTIONAL CDB format

Table 26 shows the generic format of a CDB that uses the SERVICE ACTION BIDIRECTIONAL operation
code.

Table 26 — Generic CDB format for SERVICE ACTION BIDIRECTIONAL commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (9Dh)
1 miscellaneous CDB information SERVICE ACTION

2
•• • miscellaneous CDB information
14
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 26 for any command that
uses the SERVICE ACTION BIDIRECTIONAL CDB format.

Miscellaneous CDB information is defined by the standard that defines the command that uses the SERVICE
ACTION BIDIRECTIONAL CDB format.

The SERVICE ACTION field is defined in 4.2.5.2, and in the standard that defines the command that uses the
SERVICE ACTION BIDIRECTIONAL CDB format. A numeric ordered listing of service actions associated with
the SERVICE ACTION BIDIRECTIONAL CDB format is provided in table F.7 (see F.3.5).

The CONTROL byte is defined in SAM-5.

56 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

4.2.3 Variable length CDB formats

4.2.3.1 Generic variable length CDB format

Table 27 shows the generic format of a variable length CDB.

Table 27 — Generic variable length CDB

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (7Fh)
1 CONTROL

2
•• • miscellaneous CDB information
6
7 ADDITIONAL CDB LENGTH (n-7)
8 (MSB)
SERVICE ACTION
9 (LSB)
10
•• • miscellaneous CDB information
n

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 27 for any command that
uses the variable length CDB format.

The ADDITIONAL CDB LENGTH field specifies the number of additional CDB bytes that follow. The value in the
ADDITIONAL CDB LENGTH field shall be a multiple of four. If the number of CDB bytes delivered by the service
delivery subsystem is not sufficient to contain the number of bytes specified by the ADDITIONAL CDB LENGTH
field, then the command shall be terminated with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

The CONTROL byte is defined in SAM-5.

Miscellaneous CDB information is defined by the standard that defines the command that uses the variable
length CDB format.

The SERVICE ACTION field is defined in 4.2.5.2, and in the standard that defines the command that uses the
variable length CDB format. The SERVICE ACTION field is required in the variable length CDB format. Lists of
service action values ranges associated with the variable length CDB format are provided in F.3.6.

Working Draft SCSI Primary Commands - 4 (SPC-4) 57

T10/BSR INCITS 513 Revision 37 17 May 2014

4.2.3.2 Typical 32-byte variable length CDB format

Table 28 shows the typical format of a 32-byte CDB for commands that support eight-byte LBA values,
including the location of:

a) the SERVICE ACTION field;

b) the LOGICAL BLOCK ADDRESS field, if any;
c) the TRANSFER LENGTH field, if any;
d) the PARAMETER LIST LENGTH field, if any; and
e) the ALLOCATION LENGTH field, if any.

Table 28 — Typical variable length CDB format for 32-byte commands

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (7Fh)
1 CONTROL

2
•• • miscellaneous CDB information
6
7 ADDITIONAL CDB LENGTH (18h)
8 (MSB)
SERVICE ACTION
9 (LSB)
10
miscellaneous CDB information
11
12 (MSB)
•• • LOGICAL BLOCK ADDRESS (if any)
19 (LSB)
20
•• • miscellaneous CDB information
27
28 (MSB) TRANSFER LENGTH (if any)
•• • PARAMETER LIST LENGTH (if any)
ALLOCATION LENGTH (if any) (LSB)
31

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 28 for any command that
uses the typical variable length CDB format for 32-byte commands.

The CONTROL byte is defined in SAM-5.

Miscellaneous CDB information is defined by the standard that defines the command.

The ADDITIONAL CDB LENGTH field is defined in 4.2.3.1 and shall be set as shown in table 28 for any command
that uses the typical variable length CDB format for 32-byte commands.

The SERVICE ACTION field is defined in 4.2.5.2.

The LOGICAL BLOCK ADDRESS field, if any, is defined in 4.2.5.3.

58 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The TRANSFER LENGTH field, if any, is defined in 4.2.5.4.

The PARAMETER LIST LENGTH field, if any, is defined in 4.2.5.5.

The ALLOCATION LENGTH field, if any, is defined in 4.2.5.6.

4.2.4 Extended CDBs

4.2.4.1 XCDB model

Any SCSI CDB except an XCDB may be extended in an XCDB. An XCDB shall be extended by adding
additional XCDB descriptors to the existing XCDB.

XCDB descriptors may be:

a) added by application clients and removed by device servers; or

b) added and removed by entities outside the scope of this standard that transport or process CDBs and
XCDBs during their transfer from an application client to a device server.

4.2.4.2 The XCDB format

Table 29 shows the format of an XCDB. In an XCDB, the CONTROL byte (see SAM-5) is the CONTROL byte in
the CDB field.

Table 29 — XCDB format

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (7Eh)
1 Reserved
2 (MSB)
LENGTH (n-3)
3 (LSB)
4
•• • CDB
i
XCDB descriptors
k
•• • XCDB descriptor [first]

••
•

•• • XCDB descriptor [last]

n

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 29 for an XCDB.

The LENGTH field specifies the number of bytes that follow in the XCDB.

Working Draft SCSI Primary Commands - 4 (SPC-4) 59

T10/BSR INCITS 513 Revision 37 17 May 2014

The CDB field contains the CDB to which XCDB descriptors are being appended.

Each XCDB descriptor (see table 30) contains fields associated with a specified extension type (see table 31). The
command shall be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and
the additional sense code set to INVALID XCDB, if:

a) an XCDB does not contain at least one XCDB descriptor;

b) more than one XCDB descriptor contains the same extension type; or
c) the order of extension types in the XCDB descriptors differs from that shown in table 31.

Table 30 — XCDB descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 EXTENSION TYPE

1
•• • Extension parameters
n

The EXTENSION TYPE field (see table 31) specifies the size and format of the extension parameters that follow in the
XCDB descriptor.

Table 31 — EXTENSION TYPE field

Extension
Descriptor size
Code Order a Description (bytes) Reference
40h first CbCS extension descriptor 140 5.13.6.7.16
all others Reserved
a
The order in which XCDB descriptors appear in an XCDB is arranged so that all the XCDB descriptors
that follow an XCDB descriptor defined in a future version of this standard are also XCDB descriptors
defined in a future version of this standard (i.e., after encountering one unrecognized XCDB
descriptor, all subsequent XCDB descriptors are also going to be unrecognized).

The extension parameters contain additional information whose processing is associated with the CDB in the CDB
field. The number, content, and size of the extension parameters depends on the contents of the EXTENSION TYPE
field.

60 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

4.2.5 Common CDB fields

4.2.5.1 Operation code

The first byte of a SCSI CDB shall contain the OPERATION CODE field (see table 32) specifying the command
being requested by the CDB.

Some operation codes are further qualified by a service action code (see 4.2.5.2). In such cases, the
operation code and service action code combine to specify the command being requested. The location of the
SERVICE ACTION field in the CDB varies depending on the operation code value. Operation codes and service
action codes are defined in this standard and command standards.

Table 32 — OPERATION CODE field

Code Length of CDB Generic CDB format Reference

00h to 1Fh 6 byte command see table 11 4.2.2.1
20h to 5Fh 10 byte command see table 13 4.2.2.2
60h to 7Dh Reserved
7Eh variable (i.e., extended) see table 29 4.2.4.2
7Fh variable see table 27 4.2.3.1
80h to 9Fh 16 byte command see table 21 4.2.2.4
A0h to BFh 12 byte command see table 15 4.2.2.3
C0h to FFh vendor specific

4.2.5.2 Service action

The SERVICE ACTION field provides further qualification for the OPERATION CODE field for some commands,
allowing for:

a) unrelated commands that share the same operation code (e.g., the REPORT SUPPORTED
OPERATION CODES command and the REPORT TARGET PORT GROUPS command); and
b) a set of related functions that share the same operation code (e.g., the PERSISTENT RESERVE IN
command).

4.2.5.3 Logical block address

The logical block addresses on a logical unit or within a volume or partition shall begin with block zero and be
contiguous up to the last logical block of that logical unit or within that volume or partition.

The typical 10-byte CDB format and typical 12-byte CDB format allow 32-bit LOGICAL BLOCK ADDRESS fields.
The 16-byte CDB has two typical formats:

a) one allows a 32-bit LOGICAL BLOCK ADDRESS field (see table 22); and
b) the other allows a 64-bit LOGICAL BLOCK ADDRESS field (see table 23).

The typical 32-byte variable length CDB format (see table 28) allows a 64-bit LOGICAL BLOCK ADDRESS field.

LOGICAL BLOCK ADDRESS fields in additional parameter data have their length specified for each occurrence.
See the specific command descriptions.

Working Draft SCSI Primary Commands - 4 (SPC-4) 61

T10/BSR INCITS 513 Revision 37 17 May 2014

4.2.5.4 Transfer length

The TRANSFER LENGTH field specifies the amount of data to be transferred, usually the number of blocks. Some
commands use transfer length to specify the requested number of bytes to be sent as defined in the command
description.

In commands that use multiple bytes for the TRANSFER LENGTH field, a transfer length of zero specifies that no
data transfer shall take place. This condition shall not be considered an error. A value of one or greater
specifies the number of blocks or bytes that shall be transferred.

Refer to the specific command description for further information.

4.2.5.5 Parameter list length

The PARAMETER LIST LENGTH field is used to specify the number of bytes available for transfer in the Data-Out
Buffer. This field is typically used in CDBs for parameters that are sent to a device server (e.g., mode
parameters, diagnostic parameters, log parameters). A parameter length of zero specifies that no data shall
be transferred. This condition shall not be considered an error, unless otherwise specified.

4.2.5.6 Allocation length

The ALLOCATION LENGTH field specifies the maximum number of bytes or blocks that an application client has
allocated in the Data-In Buffer. The ALLOCATION LENGTH field specifies bytes unless a different requirement is
stated in the command definition.

An allocation length of zero specifies that no data shall be transferred. This condition shall not be considered
an error.

The device server shall terminate transfers to the Data-In Buffer when the number of bytes or blocks specified
by the ALLOCATION LENGTH field have been transferred or when all available data have been transferred,
whichever is less. The allocation length is used to limit the maximum amount of variable length data (e.g.,
mode data, log data, diagnostic data) returned to an application client. If the information being transferred to
the Data-In Buffer includes fields containing counts of the number of bytes in some or all of the data (e.g., a
PARAMETER DATA LENGTH field, a PAGE LENGTH field, a DESCRIPTOR LENGTH field, an AVAILABLE DATA field), then
the contents of these fields shall not be altered to reflect the truncation, if any, that results from an insufficient
ALLOCATION LENGTH value, unless the standard that describes the Data-In Buffer format states otherwise.

If the amount of information that is available to be transferred exceeds the maximum value that the
ALLOCATION LENGTH field in combination with other fields in the CDB is capable of specifying, then no data
shall be transferred and the command shall be terminated with CHECK CONDITION status, with the sense
key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

4.3 Data field requirements

4.3.1 ASCII data field requirements

ASCII data fields shall contain only ASCII printable characters (i.e., code values 20h to 7Eh) and may be
terminated with one or more ASCII null (00h) characters.

ASCII data fields described as being left-aligned shall have any unused bytes at the end of the field (i.e.,
highest offset) and the unused bytes shall be filled with ASCII space characters (20h).

62 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

ASCII data fields described as being right-aligned shall have any unused bytes at the start of the field (i.e.,
lowest offset) and the unused bytes shall be filled with ASCII space characters (20h).

4.3.2 Null data field termination and zero padding requirements

A data field that is described as being null-terminated shall have:

1) zero or more bytes that contain ASCII or UTF-8 characters that are not the null (i.e., 00h) character;
2) followed by one byte that contains the ASCII/UTF-8 null character; and
3) followed by zero or more bytes whose contents are ignored.

A data field may be specified to be a fixed length. The length specified for a data field may be greater than the
length required to contain the contents of the field. A data field may be specified to have a length that is a
multiple of a given value (e.g., a multiple of four bytes). When such fields are described as being null-padded,
the bytes, if any, between the end of the data and the end of the field data shall contain ASCII or UTF-8 null
(00h) characters. When such fields are described as being zero-padded, the bytes, if any, between the end of
the data and the end of the field data shall contain zeros.

NOTE 2 - There is no difference between the pad byte contents in null-padded and zero-padded fields. The
difference is in the format of the other bytes in the field.

A data field that is described as being both null-terminated and null-padded shall have at least one byte
containing an ASCII or UTF-8 null (00h) character in the end of the field (i.e., highest offset) and may have
more than one byte containing ASCII or UTF-8 null characters to meet the specified field length requirements.
If more than one byte in a null-terminated, null-padded field contains the ASCII or UTF-8 null character, then
all the bytes containing the ASCII or UTF-8 null character shall be at the end of the field (i.e., only the highest
offsets).

4.3.3 Variable type data field requirements

Parameter lists may contain fields or descriptors in which data may be represented in different formats. To
indicate which format is being used a field may be defined that contains a code set enumeration (see table
33).

Table 33 — Code set enumeration

Code Description
0h Reserved
1h The associated fields or descriptors contain binary values
2h The associated fields or descriptors contain ASCII printable characters
(i.e., code values 20h to 7Eh)
3h The associated fields or descriptors contain UTF-8 codes
4h to Fh Reserved

Working Draft SCSI Primary Commands - 4 (SPC-4) 63

T10/BSR INCITS 513 Revision 37 17 May 2014

4.3.4 Port identifier field requirements

The contents of RELATIVE PORT IDENTIFIER fields, RELATIVE INITIATOR PORT IDENTIFIER fields, and RELATIVE
TARGET PORT IDENTIFIER fields are defined in table 34.

Table 34 — Relative port identifier values

Value Description
0h Reserved
1h Relative port 1, historically known as port A
2h Relative port 2, historically known as port B
3h to FFFFh Relative port 3 through 65 535

4.4 Secure random numbers

Secure random numbers should be generated as specified by RFC 4086 (e.g., see NIST SP 800-90 A).

If the same random number source is used to generate random numbers for multiple purposes (e.g., nonces
and secret keys), then interactions between the two shall not be allowed to compromise secrecy. If the value
sequence generated by the common random number source is predictable to any degree, then the random
number values that are transmitted outside the SCSI device may provide information about the random
number values that the SCSI device maintains internally, based on the reasonable assumption that an
adversary knows the order in which the random numbers are obtained from the common random number
source. SCSI devices shall eliminate sources of such predictability.

Compliance with RFC 4086 is one method for achieving the required independence between random number
values.

4.5 Sense data

4.5.1 Sense data introduction

Sense data shall be returned in the same I_T_L_Q nexus transaction as the status and as parameter data in
response to the REQUEST SENSE command (see 6.39). Sense data returned in the same I_T_L_Q nexus
transaction as the status shall be either fixed format or descriptor format sense data format based on the
value of the D_SENSE bit in the Control mode page (see 7.5.8). The REQUEST SENSE command may be
used to request either fixed format sense data or descriptor format sense data.

64 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The first byte of all sense data contains the RESPONSE CODE field (see table 35) that indicates the report type
and format of the sense data.

Table 35 — Sense data response codes

Report type Sense data format

Response
Code Description Reference Description Reference
00h to 6Fh Reserved
70h Current information 4.5.6 Fixed 4.5.3
71h Deferred error 4.5.7 Fixed 4.5.3
72h Current information 4.5.6 Descriptor 4.5.2
73h Deferred error 4.5.7 Descriptor 4.5.2
74h to 7Eh Reserved
7Fh Vendor specific

If sense data is returned in the same I_T_L_Q nexus transaction as the status, the RESPONSE CODE field shall
be set to 70h in all unit attention condition sense data in which:

a) the ADDITIONAL SENSE CODE field is set to 29h; or

b) the additional sense code is set to MODE PARAMETERS CHANGED.

Working Draft SCSI Primary Commands - 4 (SPC-4) 65

T10/BSR INCITS 513 Revision 37 17 May 2014

4.5.2 Descriptor format sense data

4.5.2.1 Descriptor format sense data overview

The descriptor format sense data for response codes 72h (i.e., current information) and 73h (i.e., deferred
errors) is defined in table 36.

Table 36 — Descriptor format sense data

Bit
7 6 5 4 3 2 1 0
Byte
0 Reserved RESPONSE CODE (72h or 73h)
1 Reserved SENSE KEY

2 ADDITIONAL SENSE CODE

3 ADDITIONAL SENSE CODE QUALIFIER

4 SDAT_OVFL Reserved
5
Reserved
6
7 ADDITIONAL SENSE LENGTH (n-7)
Sense data descriptor list
8
•• • Sense data descriptor (see table 37) [first]

••
•

•• • Sense data descriptor (see table 37) [last]

n

The contents of the RESPONSE CODE field indicate the report type and format of the sense data (see 4.5.1). For
descriptor format sense data, the RESPONSE CODE field shall be set to 72h or 73h.

The SENSE KEY field, ADDITIONAL SENSE CODE field, and ADDITIONAL SENSE CODE QUALIFIER field provide a
hierarchy of information. The hierarchy provides a top-down approach for an application client to determine
information relating to the reported condition.

The SENSE KEY field indicates generic information describing a reported condition. The sense keys are defined
in 4.5.8.

The ADDITIONAL SENSE CODE field indicates further information related to the condition reported in the SENSE
KEY field. Support of the additional sense codes not required by this standard is optional. For a list of additional
sense codes see 4.5.8. If the device server does not have further information related to the reported condition,
the ADDITIONAL SENSE CODE field shall be set to zero.

The ADDITIONAL SENSE CODE QUALIFIER field indicates detailed information related to the condition reported in
the ADDITIONAL SENSE CODE field. If the condition is reported by the device server, the value returned shall be
as defined in 4.5.8. If the device server does not have detailed information related to the reported condition,
the ADDITIONAL SENSE CODE QUALIFIER field shall be set to zero.

66 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

A sense data overflow (SDAT_OVFL) bit set to one indicates that the device server truncated the sense data to
ensure that the sense data length is less than or equal to the length specified in the MAXIMUM SENSE DATA
LENGTH field in the Control Extension mode page (see 7.5.9). A SDAT_OVFL bit set to zero indicates that the
device server did not truncate the sense data to ensure that the sense data length is less than or equal to the
length specified in the MAXIMUM SENSE DATA LENGTH field in the Control Extension mode page.

The ADDITIONAL SENSE LENGTH field indicates the number of additional sense bytes that follow. The additional
sense length shall be less than or equal to 244 (i.e., limiting the total length of the sense data to 252 bytes). If
the sense data is being transferred as parameter data by a REQUEST SENSE command, then the contents of
the ADDITIONAL SENSE LENGTH field are not altered based on the allocation length (see 4.2.5.6). If the sense
data is being transferred in the same I_T_L_Q nexus transaction as the status and the sense data is longer
than the length specified in the MAXIMUM SENSE DATA LENGTH field in the Control Extension mode page (see
7.5.9), then the device server shall ensure the number of sense data bytes is less than or equal to the length
specified in the MAXIMUM SENSE DATA LENGTH field in the Control Extension mode page by discarding entire
descriptors (i.e., not including a partial descriptor). The maximum total length of the sense data transferred by
the device server is indicated in the MAXIMUM SUPPORTED SENSE DATA LENGTH field in the Extended INQUIRY
VPD page (see 7.8.7).

Sense data descriptors (see table 37) provide specific sense information. A given type of sense data
descriptor shall be included in the sense data only if that descriptor contains valid information.

Table 37 — Sense data descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE

1 ADDITIONAL LENGTH (n-1)

2
•• • Sense data descriptor specific
n

Working Draft SCSI Primary Commands - 4 (SPC-4) 67

T10/BSR INCITS 513 Revision 37 17 May 2014

The DESCRIPTOR TYPE field (see table 38) identifies the type of sense data descriptor.

Table 38 — DESCRIPTOR TYPE field

Number of
descriptors
allowed
Code Description (maximum) Reference
00h Information 1 a 4.5.2.2
01h Command specific information 1a 4.5.2.3
a
02h Sense key specific 1 4.5.2.4
03h Field replaceable unit 1 a 4.5.2.5
04h Stream commands 1 SSC-4
05h Block commands 1a SBC-3
06h OSD object identification 1 OSD
07h OSD response integrity check value 1 OSD
08h OSD attribute identification 1 OSD
09h ATA Status Return 1 SAT-3
0Ah Another progress indication 32 4.5.2.6
0Bh User data segment referral 1 SBC-3
0Ch Forwarded sense data 2 4.5.2.7
0Dh Direct-access block device 1a SBC-3
0Eh to 7Fh Reserved
80h to FFh Vendor specific 4.5.2.8
a The direct-access block device sense data descriptor, if used, is used by a direct-access
block device instead of the information, command specific information, sense key
specific, field replaceable unit, and block commands sense data descriptors. See SBC-3.

The ADDITIONAL LENGTH field indicates the number of sense data descriptor specific bytes that follow in the
sense data descriptor.

68 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

4.5.2.2 Information sense data descriptor

The information sense data descriptor (see table 39) is included in the descriptor format sense data if
device-type information or command specific information is available as defined in this standard or a
command standard. See 4.5.4 for device server requirements regarding how values are returned in the
INFORMATION field.

Table 39 — Information sense data descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE (00h)
1 ADDITIONAL LENGTH (0Ah)
2 VALID (1b) Reserved
3 Reserved
4 (MSB)
•• • INFORMATION
11 (LSB)

The DESCRIPTOR TYPE and ADDITIONAL LENGTH fields are described in 4.5.2.1 and shall be set as shown in
table 39 for the information sense data descriptor.

The VALID bit shall be set to one.

NOTE 3 - In SPC-2, in the fixed format sense data (see 4.5.3), and in sense data descriptors other than the
information sense data descriptor that contain a VALID bit and an INFORMATION field (e.g., the direct-access
block device sense data descriptor (see SBC-3)), the VALID bit indicates whether the contents of the
INFORMATION field are valid as defined by a command standard. Since the contents of the INFORMATION field
are valid whenever the information sense data descriptor is included in the sense data, the only legal value for
the VALID bit in the information sense data descriptor is one.

The contents of the INFORMATION field are device-type or command specific and are defined in a command
standard.

Working Draft SCSI Primary Commands - 4 (SPC-4) 69

T10/BSR INCITS 513 Revision 37 17 May 2014

4.5.2.3 Command-specific information sense data descriptor

The command-specific information sense data descriptor (see table 40) is included in the descriptor format
sense data if sense data information is available that depends on the command for which the reported
condition occurred. See 4.5.5 for device server requirements regarding how values are returned in the
COMMAND-SPECIFIC INFORMATION field.

Table 40 — Command-specific information sense data descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE (01h)
1 ADDITIONAL LENGTH (0Ah)
2 Reserved
3 Reserved
4 (MSB)
•• • COMMAND-SPECIFIC INFORMATION
11 (LSB)

The DESCRIPTOR TYPE and ADDITIONAL LENGTH fields are described in 4.5.2.1 and shall be set as shown in
table 40 for the command-specific information sense data descriptor.

The contents of the COMMAND -SPECIFIC INFORMATION field are command specific, and are defined in this
standard or a command standard.

4.5.2.4 Sense key specific sense data descriptor

4.5.2.4.1 Sense key specific sense data descriptor overview

The sense key specific sense data descriptor (see table 41) is included in the descriptor format sense data if
additional information is available about the reported condition described in 4.5.2.1. The format and content of
the sense key specific information depends on the value in the SENSE KEY field (see 4.5.2.1).

Table 41 — Sense key specific sense data descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE (02h)
1 ADDITIONAL LENGTH (06h)
2 Reserved
3 Reserved
4 SKSV (1b)
5 sense key specific information (see table 42)
6
7 Reserved

The DESCRIPTOR TYPE and ADDITIONAL LENGTH fields are described in 4.5.2.1 and shall be set as shown in
table 41 for the sense-key specific sense data descriptor.

70 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The sense-key specific valid (SKSV) bit shall be set to one.

NOTE 4 - In SPC-2, in the fixed format sense data (see 4.5.3), and in sense data descriptors other than the
sense key specific sense data descriptor that contain a VALID bit and an INFORMATION field (e.g., the
direct-access block device sense data descriptor (see SBC-3)), the SKSV bit indicates whether the sense key
specific information is valid as defined by a command standard. Since the sense key specific information is
valid whenever a sense key specific sense data descriptor is included in the sense data, the only legal value
for the SKSV bit in the sense key specific sense data descriptor is one.

The content and format of the sense key specific information (see table 42) is determined by the value of the
SENSE KEY field (see 4.5.2.1).

Table 42 — Sense key specific information definitions

Sense key Sense key specific information Reference

ILLEGAL REQUEST Field pointer 4.5.2.4.2
HARDWARE ERROR, Actual retry count 4.5.2.4.3
MEDIUM ERROR, or
RECOVERED ERROR
NO SENSE or NOT READY Progress indication 4.5.2.4.4
COPY ABORTED Segment pointer 4.5.2.4.5
UNIT ATTENTION Unit attention condition queue overflow 4.5.2.4.6
All other sense keys In descriptor format sense data:
a) the sense key specific sense data descriptor shall
not appear in the sense data descriptor list; and
b) in other sense data descriptors that contain an SKSV
bit and sense key specific information (e.g., the
direct-access block device sense data descriptor
(see SBC-3)), the SKSV bit shall be set to zero.
In fixed format sense data (see 4.5.3), the SKSV bit shall be
set to zero.

4.5.2.4.2 Field pointer sense key specific information

If the sense key is ILLEGAL REQUEST, the sense key specific information (see table 41) shall have the
content and format shown in table 43.

Table 43 — Field pointer sense key specific information

Bit
7 6 5 4 3 2 1 0
Byte
0 SKSV C/D Reserved BPV BIT POINTER

1 (MSB)
FIELD POINTER
2 (LSB)

The SKSV bit is described in 4.5.2.4.1 for descriptor format sense data and in 4.5.3 for fixed format sense data.

A command data (C/D) bit set to one indicates that the illegal parameter is in the CDB. A C/D bit set to zero
indicates that the illegal parameter is in the data parameters transferred by the application client in the
Data-Out Buffer.

Working Draft SCSI Primary Commands - 4 (SPC-4) 71

T10/BSR INCITS 513 Revision 37 17 May 2014

A bit pointer valid (BPV) bit set to zero indicates that the value in the BIT POINTER field is not valid. A BPV bit set
to one indicates that the BIT POINTER field specifies which bit of the byte designated by the FIELD POINTER field
is in error. If a multiple-bit field is in error, the BIT POINTER field shall point to the first bit (i.e., the left-most bit) of
the field. If several consecutive bits are reserved, each bit should be treated as a single-bit field.

The FIELD POINTER field indicates which byte of the CDB or of the parameter data was in error. Bytes are
numbered starting from zero, as shown in the tables describing the commands and parameters. If a
multiple-byte field is in error, the field pointer shall point to the first byte (i.e., the left-most byte) of the field. If
several consecutive bytes are reserved, each shall be treated as a single-byte field.

NOTE 5 - The byte or bytes identified as being in error may not be the bytes that need to be changed to
correct the problem.

4.5.2.4.3 Actual retry count sense key specific information

If the sense key is HARDWARE ERROR, MEDIUM ERROR, or RECOVERED ERROR, then the sense key
specific information (see table 41) shall have the content and format shown in table 44.

Table 44 — Actual retry count sense key specific information

Bit
7 6 5 4 3 2 1 0
Byte
0 SKSV Reserved
1 (MSB)
ACTUAL RETRY COUNT
2 (LSB)

The SKSV bit is described in 4.5.2.4.1 for descriptor format sense data and in 4.5.3 for fixed format sense data.

The ACTUAL RETRY COUNT field contains vendor specific information on the number of retries of the recovery
algorithm used in attempting to recover an error or exception condition. This field should be computed in the
same way as the retry count fields within the Read-Write Error Recovery mode page (see SBC-3, SSC-4, and
MMC-6).

4.5.2.4.4 Progress indication sense key specific information

If the sense key is NO SENSE or NOT READY, the sense key specific information (see table 41) shall have
the content and format shown in table 45.

Table 45 — Progress indication sense key specific information

Bit
7 6 5 4 3 2 1 0
Byte
0 SKSV Reserved
1 (MSB)
PROGRESS INDICATION
2 (LSB)

The SKSV bit is described in 4.5.2.4.1 for descriptor format sense data and in 4.5.3 for fixed format sense data.

The PROGRESS INDICATION field is a percent complete indication in which the value is a numerator that has
65 536 (10000h) as its denominator. The progress indication shall be based upon the total operation. The
progress indication numerator should be time related; however, this is not an absolute requirement.

72 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

EXAMPLE - Since format time varies with the number of defects encountered, etc., the device server may assign values
to various steps within the process, and use these values as the progress indication numerator. The granularity of these
steps should be small enough to provide reasonable assurances to the application client that progress is being made.

4.5.2.4.5 Segment pointer sense key specific information

If the sense key is COPY ABORTED, the sense key specific information (see table 41) shall have the content
and format shown in table 46.

Table 46 — Segment pointer sense key specific information

Bit
7 6 5 4 3 2 1 0
Byte
0 SKSV Reserved SD Reserved BPV BIT POINTER

1 (MSB)
FIELD POINTER
2 (LSB)

The SKSV bit is described in 4.5.2.4.1 for descriptor format sense data and in 4.5.3 for fixed format sense data.

The segment descriptor (SD) bit indicates whether the field pointer is relative to the start of the parameter list
or to the start of a segment descriptor. An SD bit set to zero indicates that the field pointer is relative to the start
of the parameter list. An SD bit set to one indicates that the field pointer is relative to the start of the segment
descriptor indicated by the third and fourth bytes of the COMMAND-SPECIFIC INFORMATION field (see 5.16.7.4).

A bit pointer valid (BPV) bit set to zero indicates that the value in the BIT POINTER field is not valid. A BPV bit set
to one indicates that the BIT POINTER field specifies which bit of the byte designated by the FIELD POINTER field
is in error. If a multiple-bit field is in error, the BIT POINTER field shall point to the most-significant (i.e., left-most)
bit of the field.

The FIELD POINTER field indicates which byte of the parameter list or segment descriptor was being processed
when the error or exception condition was detected.

If the SD bit is set to zero and the byte in error has an offset greater than FFFFh, the FIELD POINTER field shall
be set to FFFFh and the BPV bit shall be set to zero.

4.5.2.4.6 Unit attention condition queue overflow sense key specific information

If the sense key is UNIT ATTENTION, the sense key specific information (see table 41) shall have the content
and format shown in table 47.

Table 47 — Unit attention condition queue overflow sense key specific information

Bit
7 6 5 4 3 2 1 0
Byte
0 SKSV Reserved OVERFLOW

1
Reserved
2

The SKSV bit is described in 4.5.2.4.1 for descriptor format sense data and in 4.5.3 for fixed format sense data.

Working Draft SCSI Primary Commands - 4 (SPC-4) 73

T10/BSR INCITS 513 Revision 37 17 May 2014

An OVERFLOW bit set to one indicates that the unit attention condition queue has overflowed. An OVERFLOW bit
set to zero indicates that the unit attention condition queue has not overflowed.

4.5.2.5 Field replaceable unit sense data descriptor

The field replaceable unit sense data descriptor (see table 48) is included in the descriptor format sense data
if information is available about a component associated with the sense data.

Table 48 — Field replaceable unit sense data descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE (03h)
1 ADDITIONAL LENGTH (02h)
2 Reserved
3 FIELD REPLACEABLE UNIT CODE

The DESCRIPTOR TYPE and ADDITIONAL LENGTH fields are described in 4.5.2.1 and shall be set as shown in
table 48 for the field replaceable unit sense data descriptor.

Non-zero values in the FIELD REPLACEABLE UNIT CODE field are used to identify a component associated with
the sense data. A value of zero in this field indicates that no specific component has been associated with the
sense data or that the data is not available. The format of this information is not specified by this standard.
Additional information about the field replaceable unit may be available in the ASCII Information VPD page
(see 7.8.3), if supported by the device server.

4.5.2.6 Another progress indication sense data descriptor

If the sense key is set to NO SENSE or NOT READY, the another progress indication sense data descriptor
(see table 49) may be included in the descriptor format sense data to provide a progress indication for one
operation other than the one described by the non-descriptor fields in 4.5.2.1. The sense data should include
one another progress indication sense data descriptor for each operation for which the device server is able to
report progress other than the operation described by the non-descriptor fields in 4.5.2.1.

Table 49 — Another progress indication sense data descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE (0Ah)
1 ADDITIONAL LENGTH (06h)
2 ANOTHER SENSE KEY

3 ANOTHER ADDITIONAL SENSE CODE

4 ANOTHER ADDITIONAL SENSE CODE QUALIFIER

5 Reserved
6 (MSB)
ANOTHER PROGRESS INDICATION
7 (LSB)

The DESCRIPTOR TYPE field and ADDITIONAL LENGTH field are described in 4.5.2.1 and shall be set as shown in
table 49 for the progress indications sense data descriptor.

74 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The ANOTHER SENSE KEY field indicates generic information about the operation for which this another
progress indication sense data descriptor provides a progress indication. A list of sense key values is in 4.5.8.

The ANOTHER ADDITIONAL SENSE CODE field indicates further information about the operation for which this
another progress indication sense data descriptor provides a progress indication. A list of additional sense
codes is in 4.5.8.

The ANOTHER ADDITIONAL SENSE CODE QUALIFIER field indicates detailed information related to the additional
sense code for the operation for which this another progress indication sense data descriptor provides a
progress indication. The value returned in the ADDITIONAL SENSE CODE QUALIFIER field shall be as defined in
4.5.8.

The ANOTHER PROGRESS INDICATION field indicates a percent complete for the operation indicated by the
ANOTHER SENSE KEY field, the ANOTHER ADDITIONAL SENSE CODE field, and the ANOTHER ADDITIONAL SENSE CODE
QUALIFIER field. The value in the ANOTHER PROGRESS INDICATION field shall be as defined in 4.5.2.4.4.

4.5.2.7 Forwarded sense data

Forwarded sense data descriptors (see table 50) are included in the descriptor format sense data if status and
sense data is available from another device server as part of command completion (e.g., an exception
condition returned by a copy target device in an EXTENDED COPY(LID4) command (see 6.4) or EXTENDED
COPY(LID1) command (see 6.5) during segment descriptor processing).

Table 50 — Forwarded sense data descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE (0Ch)
1 ADDITIONAL LENGTH (n-1)
2 FSDT Reserved SENSE DATA SOURCE

3 FORWARDED STATUS

4
•• • FORWARDED SENSE DATA
n

The DESCRIPTOR TYPE field is described in 4.5.2.1, and shall be set as shown in table 50 for the forwarded
sense data descriptor.

The ADDITIONAL LENGTH field shall be set to:

a) a minimum of 22, if the FORWARDED SENSE DATA field contains fixed format sense data (i.e., the
RESPONSE CODE field (see 4.5.1) in the forwarded sense data is 70h or 71h);
b) a minimum of 10, if the FORWARDED SENSE DATA field contains descriptor format sense data (i.e., the
RESPONSE CODE field in the forwarded sense data is 72h or 73h); and
c) two less than a multiple of four (i.e., the FORWARDED SENSE DATA field is a multiple of four bytes in
length).

A forwarded sense data truncated (FSDT) bit set to one indicates that the contents of the FORWARDED SENSE
DATA field have been truncated (i.e., the FORWARDED SENSE DATA field does not contain all of the sense data
that was supplied). An FSDT bit set to zero indicates that the contents of the FORWARDED SENSE DATA field have
not been truncated.

Working Draft SCSI Primary Commands - 4 (SPC-4) 75

T10/BSR INCITS 513 Revision 37 17 May 2014

The SENSE DATA SOURCE field (see table 51) indicates the supplier of the forwarded sense data.

Table 51 — SENSE DATA SOURCE field

Code Description
0h Unknown
1h EXTENDED COPY command copy source (see 5.16.7.2)
2h EXTENDED COPY command copy destination (see 5.16.7.2)
all others Reserved

The FORWARDED STATUS field contains the status code (see SAM-5) returned by the supplier of the forwarded
sense data at the same time that the forwarded sense data was returned.

The FORWARDED SENSE DATA field contains the forwarded sense data. The FORWARDED SENSE DATA field is a
zero-padded (see 4.3.2) field whose length is a multiple of four bytes.

4.5.2.8 Vendor specific sense data descriptors

Vendor specific sense data descriptors (see table 52) may be included in the descriptor format sense data if
vendor specific data is available that further defines the nature of the reported condition.

Table 52 — Vendor specific sense data descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE (80h to FFh)
1 ADDITIONAL LENGTH (n-1)
2
•• • Vendor specific
n

The DESCRIPTOR TYPE field and ADDITIONAL LENGTH field are described in 4.5.2.1. The DESCRIPTOR TYPE field
shall be set as shown in table 52 for the vendor specific sense data descriptor.

76 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

4.5.3 Fixed format sense data

The fixed format sense data for response codes 70h (current information) and 71h (deferred errors) is defined
in table 53.

Table 53 — Fixed format sense data

Bit
7 6 5 4 3 2 1 0
Byte
0 VALID RESPONSE CODE (70h or 71h)
1 Obsolete
2 FILEMARK EOM ILI SDAT_OVFL SENSE KEY

3 (MSB)
•• • INFORMATION
6 (LSB)
7 ADDITIONAL SENSE LENGTH (n-7)
8 (MSB)
•• • COMMAND-SPECIFIC INFORMATION
11 (LSB)
12 ADDITIONAL SENSE CODE

13 ADDITIONAL SENSE CODE QUALIFIER

14 FIELD REPLACEABLE UNIT CODE

15 SKSV

16 sense key specific information (see 4.5.2.4)

17
18
•• • Additional sense bytes
n

A VALID bit set to zero indicates that the INFORMATION field is not defined in this standard or any other
command standard. A VALID bit set to one indicates the INFORMATION field contains valid information as defined
in this standard or a command standard. See 4.5.4 for device server requirements regarding the VALID bit.

The contents of the RESPONSE CODE field indicate the report type and format of the sense data (see 4.5.1). For
fixed format sense data, the RESPONSE CODE field shall be set to 70h or 71h.

The meaning of the FILEMARK bit is device-type or command specific (e.g., see the SSC-4 READ command
and SPACE command for examples of FILEMARK bit usage) and the bit is defined in a command standard.

The meaning of the end-of-medium (EOM) bit is device-type or command specific (e.g., see the SSC-4 READ
command, SPACE command, and WRITE command for examples of EOM bit usage) and the bit is defined in a
command standard.

The meaning of the incorrect length indicator (ILI) bit is device-type or command specific (e.g., see the SSC-4
READ command an example of ILI bit usage) and the bit is defined in a command standard.

The SDAT_OVFL bit, SENSE KEY field, ADDITIONAL SENSE CODE field, and ADDITIONAL SENSE CODE QUALIFIER field
are described in 4.5.2.1.

Working Draft SCSI Primary Commands - 4 (SPC-4) 77

T10/BSR INCITS 513 Revision 37 17 May 2014

The contents of the INFORMATION field are device-type or command specific and are defined in a command
standard. See 4.5.4 for device server requirements regarding how values are returned in the INFORMATION
field.

The ADDITIONAL SENSE LENGTH field indicates the number of additional sense bytes that follow. The additional
sense length shall be less than or equal to 244 (i.e., limiting the total length of the sense data to 252 bytes). If
the sense data is being returned as parameter data by a REQUEST SENSE command, then the contents of
the ADDITIONAL SENSE LENGTH field are not altered based on the allocation length (see 4.2.5.6). If the sense
data is being returned in the same I_T_L_Q nexus transaction as the status and the sense data is longer than
the length specified in the MAXIMUM SENSE DATA LENGTH field in the Control Extension mode page (see 7.5.9),
then the device server shall ensure the number of sense data bytes is less than or equal to the length
specified in the MAXIMUM SENSE DATA LENGTH field in the Control Extension mode page. The maximum total
length of the sense data returned by the device server is indicated in the MAXIMUM SUPPORTED SENSE DATA
LENGTH field in the Extended INQUIRY VPD page (see 7.8.7).

The contents of the COMMAND -SPECIFIC INFORMATION field are command specific, and are defined in this
standard or a command standard. The COMMAND-SPECIFIC INFORMATION field should be ignored in sense data:

a) for a command or operation for which the COMMAND-SPECIFIC INFORMATION field is not defined; or
b) that is not related to a command or operation (e.g., pollable sense data (see 5.10)).

See 4.5.5 for device server requirements regarding how values are returned in the COMMAND - SPECIFIC
INFORMATION field.

The FIELD REPLACEABLE UNIT CODE field is described in 4.5.2.5.

A sense-key specific valid (SKSV) bit set to one indicates the sense key specific information is valid as defined
in this standard. An SKSV bit set to zero indicates that the content and format of the sense key specific
information is not as defined by this standard.

The sense key specific information is described in 4.5.2.4.

The additional sense bytes may contain:

a) information related to conditions detected during the processing of an EXTENDED COPY command
(see 5.16.7.4); and/or
b) vendor specific data that further defines the nature of the reported condition.

4.5.4 Returning a value in the INFORMATION field in the sense data

To return a value less than or equal to FFFF_FFFFh in the INFORMATION field:

a) if fixed format sense data (see 4.5.3) is being returned, the device server shall set the VALID bit to one
and shall set the INFORMATION field to the value; and
b) if descriptor format sense data (see 4.5.2) is being returned and a sense data descriptor that contains
a VALID bit and an INFORMATION field is being returned (e.g., the information descriptor (see 4.5.2.2) or
the direct-access block device sense data descriptor (see SBC-3)), then the device server shall set
the VALID bit to one, the first four bytes of the INFORMATION field to zero, and the next four bytes of the
INFORMATION field to the value.

78 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

To return a value greater than FFFF_FFFFh in the INFORMATION field:

a) if fixed format sense data (see 4.5.3) is being returned, the device server shall set the VALID bit to zero
and shall set the INFORMATION field to a vendor specific value. The value is not able to be reported;
and
b) if descriptor format sense data (see 4.5.2) is being returned and a sense data descriptor that contains
a VALID bit and an INFORMATION field is being returned (e.g., the information descriptor (see 4.5.2.2) or
the direct-access block device sense data descriptor (see SBC-3)), then the device server shall set
the VALID bit to one and shall set the INFORMATION field to the value.

To return sense data and not return a value in the INFORMATION field:

a) if fixed format sense data (see 4.5.3) is being returned, the device server shall set the VALID bit to zero
and shall set the INFORMATION field to a vendor specific value; and
b) if descriptor format sense data (see 4.5.2) is being returned, then:
A) the device server shall not return an information descriptor (see 4.5.2.2); and
B) if a sense data descriptor other than an information descriptor that contains a VALID bit and an
INFORMATION field is being returned (e.g., the direct-access block device sense data descriptor
(see SBC-3)), then the device server shall set the VALID bit to zero and shall set the INFORMATION
field to a vendor specific value.

4.5.5 Returning a value in the COMMAND-SPECIFIC INFORMATION field in the sense data

To return a value less than or equal to FFFF_FFFFh in the COMMAND-SPECIFIC INFORMATION field:

a) if fixed format sense data (see 4.5.3) is being returned, the device server shall set the
COMMAND-SPECIFIC INFORMATION field to the value; and
b) if descriptor format sense data (see 4.5.2) is being returned and a sense data descriptor that contains
a COMMAND-SPECIFIC INFORMATION field is being returned (e.g., the command-specific information
descriptor (see 4.5.2.3) or the direct-access block device sense data descriptor (see SBC-3)), then
the device server shall set the first four bytes of the COMMAND-SPECIFIC INFORMATION field to zero, and
the next four bytes of the COMMAND-SPECIFIC INFORMATION field to the value.

To return a value greater than FFFF_FFFFh in the COMMAND-SPECIFIC INFORMATION field:

a) if fixed format sense data (see 4.5.3) is being returned, the device server shall set the
COMMAND-SPECIFIC INFORMATION field to a vendor specific value. The value is not able to be reported;
and
b) if descriptor format sense data (see 4.5.2) is being returned and a sense data descriptor that contains
a COMMAND-SPECIFIC INFORMATION field is being returned (e.g., the command-specific information
descriptor (see 4.5.2.3) or the direct-access block device sense data descriptor (see SBC-3)), then
the device server shall set the COMMAND-SPECIFIC INFORMATION field to the value.

To return sense data and not return a value in the COMMAND-SPECIFIC INFORMATION field:

a) if fixed format sense data (see 4.5.3) is being returned, the device server shall set the
COMMAND-SPECIFIC INFORMATION field to a vendor specific value; and
b) if descriptor format sense data (see 4.5.2) is being returned, then:
A) the device server shall not return a command-specific information descriptor (see 4.5.2.3); and
B) if a sense data descriptor that contains a COMMAND-SPECIFIC INFORMATION field is being returned
(e.g., the direct-access block device sense data descriptor (see SBC-3)), then the device server
shall set the COMMAND-SPECIFIC INFORMATION field to a vendor specific value.

Working Draft SCSI Primary Commands - 4 (SPC-4) 79

T10/BSR INCITS 513 Revision 37 17 May 2014

4.5.6 Current information

Response codes 70h and 72h (i.e., current information) indicate that the sense data is:

a) the result of an error, exception condition, or protocol specific failure that is associated with CHECK
CONDITION status; or
b) additional information that is associated with a status other than CHECK CONDITION.

Current information includes:

a) errors generated during processing of a command terminated with CHECK CONDITION status;
b) errors not related to any command that are detected during processing of a command (e.g., disk
servomechanism failures, off-track errors, or power-up test errors); and
c) referral information (see SBC-3) associated with GOOD status.

4.5.7 Deferred errors

Response codes 71h and 73h (deferred error) indicate that the sense data is the result of an error or
exception condition that occurred during processing of a previous command for which GOOD status or
CONDITION MET status has already been returned. Such commands are associated with the use of the
immediate bit and with some forms of caching. Device servers that implement these features shall implement
deferred error reporting.

The deferred error may be indicated by returning CHECK CONDITION status to an application client
accessed through a defined I_T nexus as described in this subclause.

If a command terminates with CHECK CONDITION status and the sense data describes a deferred error, the
terminated command shall not have been processed. After the device server detects a deferred error
condition, the device server shall return a deferred error according to the following rules:

a) if no external intervention is necessary to recover a deferred error, a deferred error indication shall not
be returned unless required by the error handling parameters of a mode page (e.g., the Informational
Exceptions mode page defined by SBC-3 and SSC-4). The occurrence of the error may be logged;
b) if it is possible to associate a deferred error with an I_T nexus and with a particular function or a
particular subset of data, and the error is either unrecovered or required to be reported by the mode
parameters, then a deferred error indication shall be returned for a command received on the I_T
nexus associated with the deferred error. If a command received on an I_T nexus other than the I_T
nexus associated with the deferred error attempts to access the particular function or subset of data
associated with the deferred error and the TST field equals 000b (see 7.5.8), then the device server
shall complete the command with BUSY status or ACA ACTIVE status according to the requirements
in SAM-5. If a command received on an I_T nexus other than the I_T nexus associated with the
deferred error attempts to access the particular function or subset of data associated with the deferred
error and the TST field equals 001b, then the command attempting the access shall not be blocked by
the deferred error and the cause of the deferred error may result in an error being reported for the
command attempting the access;
c) if the device server is unable to associate a deferred error with an I_T nexus or with a particular
subset of data, then the device server shall return a deferred error for one command received on each
I_T nexus. If multiple deferred errors have accumulated for an I_T nexus, then:
A) one error shall be returned; and
B) only the last error should be returned;
d) if the SCSI target device is unable to associate a deferred error with a particular logical unit, the SCSI
target device shall establish a deferred error for every logical unit and shall return the deferred error
for one command received on each appropriate I_T nexus associated with each logical unit; or

80 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

e) if a command has never entered the enabled command state, and a deferred error occurs, the device
server shall terminate the command with CHECK CONDITION status and deferred error information
returned in the sense data. If a deferred error occurs after a command has entered the enabled
command state and the command is affected by the error, then the device server shall terminate the
command with CHECK CONDITION status and the current error information shall be returned in the
sense data. In this case, if the current error information does not adequately define the deferred error
condition, a deferred error may still exist after the current error information has been returned. If a
deferred error occurs after a command has entered the enabled command state and the command
completes successfully, then the device server may choose to return the deferred error information
after the completion of the current command in conjunction with a subsequent command that has not
begun processing.

NOTE 6 - A deferred error may indicate that an operation was unsuccessful long after GOOD status was
returned. If the application client is unable to replicate or recover from other sources the data that is being
written using cached or buffered write operations, then synchronization commands should be performed
before the critical data is destroyed. This is necessary for actions taken when deferred errors occur in the
storing of the data. The synchronizing process should provide the necessary commands to allow returning
CHECK CONDITION status and subsequent returning of deferred error sense information after all cached or
buffered operations are completed.

4.5.8 Sense key and additional sense code definitions

The sense keys are defined in table 54.

Table 54 — Sense key descriptions (part 1 of 2)

Sense
Key Description
0h NO SENSE: Indicates that there is no specific sense key information to be reported. This
may occur for a successful command or for a command that is terminated with CHECK
CONDITION status (e.g., as a result of the FILEMARK bit, EOM bit, or ILI bit being set to one).
1h RECOVERED ERROR: Indicates that the command completed successfully, with some recov-
ery action performed by the device server. Details may be determined by examining the sense
data (e.g., the INFORMATION field). If multiple recovered errors occur during one command, the
choice of which error to report (e.g., first, last, most severe) is vendor specific.
2h NOT READY: Indicates that the logical unit is not accessible. Operator intervention may be
required to correct this condition.
3h MEDIUM ERROR: Indicates that the command terminated with a non-recovered error condi-
tion that may have been caused by a flaw in the medium or an error in the recorded data. This
sense key may also be returned if the device server is unable to distinguish between a flaw in
the medium and a specific hardware failure (i.e., sense key 4h).
4h HARDWARE ERROR: Indicates that the device server detected a non-recoverable hardware
failure (e.g., controller failure, device failure, or parity error) while performing the command or
during a self test.

Working Draft SCSI Primary Commands - 4 (SPC-4) 81

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 54 — Sense key descriptions (part 2 of 2)

Sense
Key Description
5h ILLEGAL REQUEST: Indicates that:
a) the command was addressed to an incorrect logical unit number (see SAM-5);
b) the command had an invalid task attribute (see SAM-5);
c) the command was addressed to a logical unit whose current configuration prohibits
processing the command;
d) there was an illegal parameter in the CDB; or
e) there was an illegal parameter in the additional parameters supplied as data for some
commands (e.g., PERSISTENT RESERVE OUT).
If the device server detects an invalid parameter in the CDB, the device server shall terminate
the command without altering the medium. If the device server detects an invalid parameter in
the additional parameters supplied as data, then the device server may have already altered
the medium.
6h UNIT ATTENTION: Indicates that a unit attention condition has been established (e.g., the
removable medium may have been changed, a logical unit reset occurred). See SAM-5.
7h DATA PROTECT: Indicates that a command that reads or writes the medium was attempted
on a block that is protected. The read or write operation was not performed.
8h BLANK CHECK: Indicates that blank or non-blank medium was encountered when not
expected.
9h VENDOR SPECIFIC: This sense key is available for reporting vendor specific conditions.
Ah COPY ABORTED: Indicates a third-party copy command (see 5.16.3) was aborted after some
data was transferred but before all data was transferred.
Bh ABORTED COMMAND: Indicates that the device server aborted the command. The appli-
cation client may be able to recover by trying the command again.
Ch Reserved
Dh VOLUME OVERFLOW: Indicates that a buffered SCSI device has reached the end-of-partition
and data may remain in the buffer that has not been written to the medium. One or more
RECOVER BUFFERED DATA command(s) may be issued to read the unwritten data from the
buffer. (See SSC-4.)
Eh MISCOMPARE: Indicates that the source data did not match the data read from the medium.
Fh COMPLETED: Indicates there is command completed sense data (see SAM-5) to be reported.
This may occur for a successful command.

82 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The additional sense codes (i.e., the ADDITIONAL SENSE CODE field and ADDITIONAL SENSE CODE QUALIFIER field
values in sense data) are defined in table 55.

Table 55 — ASC and ASCQ assignments (part 1 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
20h 0Bh DT P WROM AE B K ACCESS DENIED - ACL LUN CONFLICT
20h 08h DT P WROM AE B K ACCESS DENIED - ENROLLMENT CONFLICT
20h 01h DT P WROM AE B K ACCESS DENIED - INITIATOR PENDING-ENROLLED
20h 09h DT P WROM AE B K ACCESS DENIED - INVALID LU IDENTIFIER
20h 03h DT P WROM AE B K ACCESS DENIED - INVALID MGMT ID KEY
20h 0Ah DT P WROM AE B K ACCESS DENIED - INVALID PROXY TOKEN
20h 02h DT P WROM AE B K ACCESS DENIED - NO ACCESS RIGHTS
4Bh 03h DT P WROM AE B K ACK/NAK TIMEOUT
67h 02h A ADD LOGICAL UNIT FAILED
13h 00h D W O BK ADDRESS MARK NOT FOUND FOR DATA FIELD
12h 00h D W O BK ADDRESS MARK NOT FOUND FOR ID FIELD
67h 08h A ASSIGN FAILURE OCCURRED
27h 03h T R ASSOCIATED WRITE PROTECT
2Ah 06h DT L P WROM AE B KV F ASYMMETRIC ACCESS STATE CHANGED
47h 04h DT L P WROM AE B KV F ASYNCHRONOUS INFORMATION PROTECTION ERROR DETECTED
44h 71h DT B ATA DEVICE FAILED SET FEATURES
67h 0Bh DT B ATA DEVICE FEATURE NOT ENABLED
00h 1Dh DT B ATA PASS THROUGH INFORMATION AVAILABLE
00h 21h D ATOMIC COMMAND ABORTED DUE TO ACA
67h 06h A ATTACHMENT OF LOGICAL UNIT FAILED
21h 06h D ATTEMPT TO READ INVALID DATA
00h 11h R AUDIO PLAY OPERATION IN PROGRESS
00h 12h R AUDIO PLAY OPERATION PAUSED
00h 14h R AUDIO PLAY OPERATION STOPPED DUE TO ERROR
00h 13h R AUDIO PLAY OPERATION SUCCESSFULLY COMPLETED
74h 40h DT R M AE B KV AUTHENTICATION FAILED
66h 00h AUTOMATIC DOCUMENT FEEDER COVER UP
66h 01h AUTOMATIC DOCUMENT FEEDER LIFT UP
55h 06h DT WROM B AUXILIARY MEMORY OUT OF SPACE
11h 12h DT WROM B AUXILIARY MEMORY READ ERROR
0Ch 0Bh DT WROM B AUXILIARY MEMORY WRITE ERROR
00h 04h T BEGINNING-OF-PARTITION/MEDIUM DETECTED
0Ch 06h DT W O B BLOCK NOT COMPRESSIBLE
14h 04h T BLOCK SEQUENCE ERROR
29h 03h DT L P WROM AE B KV F BUS DEVICE RESET FUNCTION OCCURRED
11h 0Eh DT WRO B CANNOT DECOMPRESS USING DECLARED ALGORITHM
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 83

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 55 — ASC and ASCQ assignments (part 2 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
30h 06h DT WRO B CANNOT FORMAT MEDIUM - INCOMPATIBLE MEDIUM
30h 02h DT WRO BK CANNOT READ MEDIUM - INCOMPATIBLE FORMAT
30h 01h DT WRO BK CANNOT READ MEDIUM - UNKNOWN FORMAT
30h 08h R CANNOT WRITE - APPLICATION CODE MISMATCH
30h 05h DT WRO BK CANNOT WRITE MEDIUM - INCOMPATIBLE FORMAT
30h 04h DT WRO BK CANNOT WRITE MEDIUM - UNKNOWN FORMAT
2Ah 09h D CAPACITY DATA HAS CHANGED
52h 00h T CARTRIDGE FAULT
73h 00h R CD CONTROL ERROR
24h 01h DT L P WRO AE B KV F CDB DECRYPTION ERROR
3Fh 02h DT L P WROM BK CHANGED OPERATING DEFINITION
11h 06h WRO B CIRC UNRECOVERED ERROR
30h 03h DT R M K CLEANING CARTRIDGE INSTALLED
30h 07h DT L WROM AE B KV F CLEANING FAILURE
30h 0Ah DT WRO AE B K CLEANING REQUEST REJECTED
00h 17h DT L WROM AE B KV F CLEANING REQUESTED
30h 13h M CLEANING VOLUME EXPIRED
4Ah 00h DT L P WROM AE B KV F COMMAND PHASE ERROR
2Ch 00h DT L P WROM AE B KV F COMMAND SEQUENCE ERROR
2Eh 01h D W OM B COMMAND TIMEOUT BEFORE PROCESSING
2Eh 02h D W OM B COMMAND TIMEOUT DURING PROCESSING
COMMAND TIMEOUT DURING PROCESSING DUE TO ERROR
2Eh 03h D W OM B
RECOVERY
6Eh 00h A COMMAND TO LOGICAL UNIT FAILED
2Fh 00h DT L P WROM AE B KV F COMMANDS CLEARED BY ANOTHER INITIATOR
2Fh 02h DT L P WROM AE B KV F COMMANDS CLEARED BY DEVICE SERVER
2Fh 01h D COMMANDS CLEARED BY POWER LOSS NOTIFICATION
3Fh 04h DT WROM AE B K COMPONENT DEVICE ATTACHED
0Ch 04h DT W O B COMPRESSION CHECK MISCOMPARE ERROR
27h 06h R F CONDITIONAL WRITE PROTECT
67h 00h A CONFIGURATION FAILURE
67h 01h A CONFIGURATION OF INCAPABLE LOGICAL UNITS FAILED
6Fh 07h R CONFLICT IN BINDING NONCE RECORDING
00h 1Eh DT R M AE B KV CONFLICTING SA CREATION REQUEST
4Bh 07h DT P WROM AE B K F CONNECTION LOST
5Dh 25h D B CONTROLLER IMPENDING FAILURE ACCESS TIMES TOO HIGH
5Dh 27h D B CONTROLLER IMPENDING FAILURE CHANNEL PARAMETRICS
5Dh 28h D B CONTROLLER IMPENDING FAILURE CONTROLLER DETECTED
5Dh 22h D B CONTROLLER IMPENDING FAILURE DATA ERROR RATE TOO HIGH
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

84 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 55 — ASC and ASCQ assignments (part 3 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
CONTROLLER IMPENDING FAILURE DRIVE CALIBRATION RETRY
5Dh 2Ch D B
COUNT
5Dh 21h D B CONTROLLER IMPENDING FAILURE DRIVE ERROR RATE TOO HIGH
5Dh 20h D B CONTROLLER IMPENDING FAILURE GENERAL HARD DRIVE FAILURE
5Dh 23h D B CONTROLLER IMPENDING FAILURE SEEK ERROR RATE TOO HIGH
5Dh 2Ah D B CONTROLLER IMPENDING FAILURE SEEK TIME PERFORMANCE
5Dh 2Bh D B CONTROLLER IMPENDING FAILURE SPIN-UP RETRY COUNT
5Dh 26h D B CONTROLLER IMPENDING FAILURE START UNIT TIMES TOO HIGH
5Dh 29h D B CONTROLLER IMPENDING FAILURE THROUGHPUT PERFORMANCE
5Dh 24h D B CONTROLLER IMPENDING FAILURE TOO MANY BLOCK REASSIGNS
2Bh 00h DT L P WRO K COPY CANNOT EXECUTE SINCE HOST CANNOT DISCONNECT
COPY PROTECTION KEY EXCHANGE FAILURE - AUTHENTICATION
6Fh 00h R
FAILURE
COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT
6Fh 02h R
ESTABLISHED
6Fh 01h R COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT PRESENT
26h 0Dh DT L P WRO K COPY SEGMENT GRANULARITY VIOLATION
0Dh 05h DT L P WRO A K COPY TARGET DEVICE DATA OVERRUN
0Dh 04h DT L P WRO A K COPY TARGET DEVICE DATA UNDERRUN
0Dh 02h DT L P WRO A K COPY TARGET DEVICE NOT REACHABLE
67h 07h A CREATION OF LOGICAL UNIT FAILED
74h 04h T CRYPTOGRAPHIC INTEGRITY VALIDATION FAILED
73h 10h R CURRENT POWER CALIBRATION AREA ALMOST FULL
73h 11h R CURRENT POWER CALIBRATION AREA IS FULL
2Ch 04h R CURRENT PROGRAM AREA IS EMPTY
2Ch 03h R CURRENT PROGRAM AREA IS NOT EMPTY
30h 09h R CURRENT SESSION NOT FIXATED FOR APPEND
5Dh 35h D B DATA CHANNEL IMPENDING FAILURE ACCESS TIMES TOO HIGH
5Dh 37h D B DATA CHANNEL IMPENDING FAILURE CHANNEL PARAMETRICS
5Dh 38h D B DATA CHANNEL IMPENDING FAILURE CONTROLLER DETECTED
5Dh 32h D B DATA CHANNEL IMPENDING FAILURE DATA ERROR RATE TOO HIGH
DATA CHANNEL IMPENDING FAILURE DRIVE CALIBRATION RETRY
5Dh 3Ch D B
COUNT
5Dh 31h D B DATA CHANNEL IMPENDING FAILURE DRIVE ERROR RATE TOO HIGH
5Dh 30h D B DATA CHANNEL IMPENDING FAILURE GENERAL HARD DRIVE FAILURE
5Dh 33h D B DATA CHANNEL IMPENDING FAILURE SEEK ERROR RATE TOO HIGH
5Dh 3Ah D B DATA CHANNEL IMPENDING FAILURE SEEK TIME PERFORMANCE
5Dh 3Bh D B DATA CHANNEL IMPENDING FAILURE SPIN-UP RETRY COUNT
5Dh 36h D B DATA CHANNEL IMPENDING FAILURE START UNIT TIMES TOO HIGH
5Dh 39h D B DATA CHANNEL IMPENDING FAILURE THROUGHPUT PERFORMANCE
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 85

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 55 — ASC and ASCQ assignments (part 4 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
5Dh 34h D B DATA CHANNEL IMPENDING FAILURE TOO MANY BLOCK REASSIGNS
55h 0Ah M DATA CURRENTLY UNAVAILABLE
26h 05h DT L P WRO A B K DATA DECRYPTION ERROR
26h 10h T DATA DECRYPTION KEY FAIL LIMIT REACHED
2Ah 0Dh T DATA ENCRYPTION CAPABILITIES CHANGED
74h 21h T DATA ENCRYPTION CONFIGURATION PREVENTED
2Ah 13h T DATA ENCRYPTION KEY INSTANCE COUNTER HAS CHANGED
2Ah 11h T DATA ENCRYPTION PARAMETERS CHANGED BY ANOTHER I_T NEXUS
DATA ENCRYPTION PARAMETERS CHANGED BY VENDOR SPECIFIC
2Ah 12h T
EVENT
0Ch 05h DT W O B DATA EXPANSION OCCURRED DURING COMPRESSION
69h 00h A DATA LOSS ON LOGICAL UNIT
4Bh 05h DT P WROM AE B K DATA OFFSET ERROR
41h 00h D DATA PATH FAILURE (SHOULD USE 40 NN)
47h 01h DT L P WROM AE B KV F DATA PHASE CRC ERROR DETECTED
4Bh 00h DT L P WROM AE B KV F DATA PHASE ERROR
11h 07h W O B DATA RE-SYNCHRONIZATION ERROR
16h 03h D W O BK DATA SYNC ERROR - DATA AUTO-REALLOCATED
16h 01h D W O BK DATA SYNC ERROR - DATA REWRITTEN
16h 04h D W O BK DATA SYNC ERROR - RECOMMEND REASSIGNMENT
16h 02h D W O BK DATA SYNC ERROR - RECOMMEND REWRITE
16h 00h D W O BK DATA SYNCHRONIZATION MARK ERROR
53h 0Ch M DATA TRANSFER DEVICE ERROR - EJECT FAILED
53h 0Dh M DATA TRANSFER DEVICE ERROR - LIBRARY COMMUNICATION FAILED
53h 09h M DATA TRANSFER DEVICE ERROR - LOAD FAILED
53h 0Ah M DATA TRANSFER DEVICE ERROR - UNLOAD FAILED
53h 0Bh M DATA TRANSFER DEVICE ERROR - UNLOAD MISSING
3Bh 1Bh M DATA TRANSFER DEVICE INSERTED
3Bh 1Ah M DATA TRANSFER DEVICE REMOVED
4Bh 0Ah DT P WROM AE B K F DATA-IN BUFFER ERROR
4Bh 09h DT P WROM AE B K F DATA-IN BUFFER OVERFLOW - DATA BUFFER DESCRIPTOR AREA
4Bh 08h DT P WROM AE B K F DATA-IN BUFFER OVERFLOW - DATA BUFFER SIZE
4Bh 0Dh DT P WROM AE B K F DATA-OUT BUFFER ERROR
4Bh 0Ch DT P WROM AE B K F DATA-OUT BUFFER OVERFLOW - DATA BUFFER DESCRIPTOR AREA
4Bh 0Bh DT P WROM AE B K F DATA-OUT BUFFER OVERFLOW - DATA BUFFER SIZE
11h 0Dh DT WRO B DE-COMPRESSION CRC ERROR
71h 00h T DECOMPRESSION EXCEPTION LONG ALGORITHM ID
70h NNh T DECOMPRESSION EXCEPTION SHORT ALGORITHM ID OF NN
19h 00h D O K DEFECT LIST ERROR
19h 03h D O K DEFECT LIST ERROR IN GROWN LIST
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

86 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 55 — ASC and ASCQ assignments (part 5 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
19h 02h D O K DEFECT LIST ERROR IN PRIMARY LIST
19h 01h D O K DEFECT LIST NOT AVAILABLE
1Ch 00h D O BK DEFECT LIST NOT FOUND
32h 01h D W O BK DEFECT LIST UPDATE FAILURE
0Ch 0Fh R DEFECTS IN ERROR WINDOW
3Fh 05h DT WROM AE B K DEVICE IDENTIFIER CHANGED
29h 04h DT L P WROM AE B KV F DEVICE INTERNAL RESET
40h NNh DT L P WROM AE B KV F DIAGNOSTIC FAILURE ON COMPONENT NN (80h-FFh)
74h 08h DT R M E V F DIGITAL SIGNATURE VALIDATION FAILURE
66h 02h DOCUMENT JAM IN AUTOMATIC DOCUMENT FEEDER
66h 03h DOCUMENT MISS FEED AUTOMATIC IN DOCUMENT FEEDER
6Fh 05h R DRIVE REGION MUST BE PERMANENT/REGION RESET COUNT ERROR
53h 07h M DUPLICATE VOLUME IDENTIFIER
3Fh 0Fh DT L P WROM AE B KV F ECHO BUFFER OVERWRITTEN
3Bh 18h M ELEMENT DISABLED
3Bh 19h M ELEMENT ENABLED
53h 08h M ELEMENT STATUS UNKNOWN
72h 04h R EMPTY OR PARTIALLY WRITTEN RESERVED TRACK
34h 00h DT L P WROM AE B KV F ENCLOSURE FAILURE
35h 05h DT L WROM AE B KV F ENCLOSURE SERVICES CHECKSUM ERROR
35h 00h DT L P WROM AE B KV F ENCLOSURE SERVICES FAILURE
35h 03h DT L P WROM AE B KV F ENCLOSURE SERVICES TRANSFER FAILURE
35h 04h DT L P WROM AE B KV F ENCLOSURE SERVICES TRANSFER REFUSED
35h 02h DT L P WROM AE B KV F ENCLOSURE SERVICES UNAVAILABLE
74h 0Ah T ENCRYPTED BLOCK NOT RAW READ ENABLED
74h 0Dh T ENCRYPTION ALGORITHM DISABLED
74h 09h T ENCRYPTION MODE MISMATCH ON READ
74h 07h T ENCRYPTION PARAMETERS NOT USEABLE
3Bh 0Fh R END OF MEDIUM REACHED
63h 00h R END OF USER AREA ENCOUNTERED ON THIS TRACK
00h 05h TL END-OF-DATA DETECTED
14h 03h T END-OF-DATA NOT FOUND
00h 02h T END-OF-PARTITION/MEDIUM DETECTED
51h 00h DT RO ERASE FAILURE
51h 01h D R ERASE FAILURE - INCOMPLETE ERASE OPERATION DETECTED
00h 18h T ERASE OPERATION IN PROGRESS
74h 05h T ERROR DECRYPTING DATA
0Dh 00h DT L P WRO A K ERROR DETECTED BY THIRD PARTY TEMPORARY INITIATOR
2Ah 0Ah DT ERROR HISTORY I_T NEXUS CLEARED
2Ah 0Bh DT ERROR HISTORY SNAPSHOT RELEASED
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 87

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 55 — ASC and ASCQ assignments (part 6 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
0Ah 00h DT L P WROM AE B KV F ERROR LOG OVERFLOW
11h 10h R ERROR READING ISRC NUMBER
11h 0Fh R ERROR READING UPC/EAN NUMBER
2Ah 0Ch F ERROR RECOVERY ATTRIBUTES HAVE CHANGED
11h 02h DT WRO BK ERROR TOO LONG TO CORRECT
38h 06h B ESN - DEVICE BUSY CLASS EVENT
38h 04h B ESN - MEDIA CLASS EVENT
38h 02h B ESN - POWER MANAGEMENT CLASS EVENT
38h 00h B EVENT STATUS NOTIFICATION
03h 02h T EXCESSIVE WRITE ERRORS
67h 04h A EXCHANGE OF LOGICAL UNIT FAILED
00h 20h DT P B EXTENDED COPY INFORMATION AVAILABLE
74h 6Fh T EXTERNAL DATA ENCRYPTION CONTROL ERROR
74h 6Eh T EXTERNAL DATA ENCRYPTION CONTROL TIMEOUT
74h 61h V EXTERNAL DATA ENCRYPTION KEY MANAGER ACCESS ERROR
74h 62h V EXTERNAL DATA ENCRYPTION KEY MANAGER ERROR
74h 63h V EXTERNAL DATA ENCRYPTION KEY NOT FOUND
74h 64h V EXTERNAL DATA ENCRYPTION REQUEST NOT AUTHORIZED
3Bh 07h L FAILED TO SENSE BOTTOM-OF-FORM
3Bh 06h L FAILED TO SENSE TOP-OF-FORM
5Dh 00h DT L P WROM AE B KV F FAILURE PREDICTION THRESHOLD EXCEEDED
5Dh FFh DT L P WROM AE B KV F FAILURE PREDICTION THRESHOLD EXCEEDED (FALSE)
00h 01h T FILEMARK DETECTED
14h 02h T FILEMARK OR SETMARK NOT FOUND
5Dh 65h D B FIRMWARE IMPENDING FAILURE ACCESS TIMES TOO HIGH
5Dh 67h D B FIRMWARE IMPENDING FAILURE CHANNEL PARAMETRICS
5Dh 68h D B FIRMWARE IMPENDING FAILURE CONTROLLER DETECTED
5Dh 62h D B FIRMWARE IMPENDING FAILURE DATA ERROR RATE TOO HIGH
5Dh 6Ch D B FIRMWARE IMPENDING FAILURE DRIVE CALIBRATION RETRY COUNT
5Dh 61h D B FIRMWARE IMPENDING FAILURE DRIVE ERROR RATE TOO HIGH
5Dh 60h D B FIRMWARE IMPENDING FAILURE GENERAL HARD DRIVE FAILURE
5Dh 63h D B FIRMWARE IMPENDING FAILURE SEEK ERROR RATE TOO HIGH
5Dh 6Ah D B FIRMWARE IMPENDING FAILURE SEEK TIME PERFORMANCE
5Dh 6Bh D B FIRMWARE IMPENDING FAILURE SPIN-UP RETRY COUNT
5Dh 66h D B FIRMWARE IMPENDING FAILURE START UNIT TIMES TOO HIGH
5Dh 69h D B FIRMWARE IMPENDING FAILURE THROUGHPUT PERFORMANCE
5Dh 64h D B FIRMWARE IMPENDING FAILURE TOO MANY BLOCK REASSIGNS
09h 02h WRO K FOCUS SERVO FAILURE
31h 01h D L RO B FORMAT COMMAND FAILED
28h 02h R FORMAT-LAYER MAY HAVE CHANGED
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

88 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 55 — ASC and ASCQ assignments (part 7 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
58h 00h O GENERATION DOES NOT EXIST
1Ch 02h D O BK GROWN DEFECT LIST NOT FOUND
5Dh 15h D B HARDWARE IMPENDING FAILURE ACCESS TIMES TOO HIGH
5Dh 17h D B HARDWARE IMPENDING FAILURE CHANNEL PARAMETRICS
5Dh 18h D B HARDWARE IMPENDING FAILURE CONTROLLER DETECTED
5Dh 12h D B HARDWARE IMPENDING FAILURE DATA ERROR RATE TOO HIGH
5Dh 1Ch D B HARDWARE IMPENDING FAILURE DRIVE CALIBRATION RETRY COUNT
5Dh 11h D B HARDWARE IMPENDING FAILURE DRIVE ERROR RATE TOO HIGH
5Dh 10h D B HARDWARE IMPENDING FAILURE GENERAL HARD DRIVE FAILURE
5Dh 13h D B HARDWARE IMPENDING FAILURE SEEK ERROR RATE TOO HIGH
5Dh 1Ah D B HARDWARE IMPENDING FAILURE SEEK TIME PERFORMANCE
5Dh 1Bh D B HARDWARE IMPENDING FAILURE SPIN-UP RETRY COUNT
5Dh 16h D B HARDWARE IMPENDING FAILURE START UNIT TIMES TOO HIGH
5Dh 19h D B HARDWARE IMPENDING FAILURE THROUGHPUT PERFORMANCE
5Dh 14h D B HARDWARE IMPENDING FAILURE TOO MANY BLOCK REASSIGNS
27h 01h DT WRO BK HARDWARE WRITE PROTECTED
09h 04h DT WRO B HEAD SELECT FAULT
00h 06h DT L P WROM AE B KV F I/O PROCESS TERMINATED
10h 00h D W O BK ID CRC OR ECC ERROR
5Eh 03h DT L P WRO A K IDLE CONDITION ACTIVATED BY COMMAND
5Eh 01h DT L P WRO A K IDLE CONDITION ACTIVATED BY TIMER
5Eh 06h DT L P WRO A K IDLE_B CONDITION ACTIVATED BY COMMAND
5Eh 05h DT L P WRO A K IDLE_B CONDITION ACTIVATED BY TIMER
5Eh 08h DT L P WRO A K IDLE_C CONDITION ACTIVATED BY COMMAND
5Eh 07h DT L P WRO A K IDLE_C CONDITION ACTIVATED BY TIMER
20h 0Ch T ILLEGAL COMMAND WHEN NOT IN APPEND-ONLY MODE
20h 06h T ILLEGAL COMMAND WHILE IN EXPLICIT ADDRESS MODE
20h 07h T ILLEGAL COMMAND WHILE IN IMPLICIT ADDRESS MODE
20h 04h T ILLEGAL COMMAND WHILE IN WRITE CAPABLE STATE
22h 00h D ILLEGAL FUNCTION (USE 20 00, 24 00, OR 26 00)
64h 00h R ILLEGAL MODE FOR THIS TRACK
2Ch 05h B ILLEGAL POWER CONDITION REQUEST
2Ah 07h DT L P WROM AE B KV F IMPLICIT ASYMMETRIC ACCESS STATE TRANSITION FAILED
28h 01h DT WROM B IMPORT OR EXPORT ELEMENT ACCESSED
28h 03h M IMPORT/EXPORT ELEMENT ACCESSED, MEDIUM CHANGED
30h 00h DT WROM BK INCOMPATIBLE MEDIUM INSTALLED
30h 12h M INCOMPATIBLE VOLUME QUALIFIER
30h 11h M INCOMPATIBLE VOLUME TYPE
11h 08h T INCOMPLETE BLOCK READ
26h 11h T INCOMPLETE KEY-ASSOCIATED DATA SET
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 89

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 55 — ASC and ASCQ assignments (part 8 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
0Dh 03h DT L P WRO A K INCORRECT COPY TARGET DEVICE TYPE
74h 03h T INCORRECT DATA ENCRYPTION KEY
74h 0Bh T INCORRECT ENCRYPTION PARAMETERS
0Eh 02h DT P WROM AE B K F INFORMATION UNIT TOO LONG
0Eh 01h DT P WROM AE B K F INFORMATION UNIT TOO SHORT
47h 03h DT L P WROM AE B KV F INFORMATION UNIT iuCRC ERROR DETECTED
6Ah 00h A INFORMATIONAL, REFER TO LOG
48h 00h DT L P WROM AE B KV F INITIATOR DETECTED ERROR MESSAGE RECEIVED
4Bh 06h DT P WROM AE B K INITIATOR RESPONSE TIMEOUT
26h 0Bh DT L P WRO K INLINE DATA LENGTH EXCEEDED
3Fh 03h DT L P WROM AE B KV F INQUIRY DATA HAS CHANGED
3Fh 15h DT L P WR M AE B K INSPECT REFERRALS SENSE DESCRIPTORS
55h 05h DT P WROM AE B K INSUFFICIENT ACCESS CONTROL RESOURCES
6Fh 06h R INSUFFICIENT BLOCK COUNT FOR BINDING NONCE RECORDING
55h 0Bh DT L P WROM AE B KV F INSUFFICIENT POWER FOR OPERATION
55h 04h DT L P WROM AE K INSUFFICIENT REGISTRATION RESOURCES
55h 02h DT L P WROM AE K INSUFFICIENT RESERVATION RESOURCES
55h 03h DT L P WROM AE K INSUFFICIENT RESOURCES
55h 0Ch DT P B INSUFFICIENT RESOURCES TO CREATE ROD
55h 0Dh DT P B INSUFFICIENT RESOURCES TO CREATE ROD TOKEN
2Eh 00h D WROM B INSUFFICIENT TIME FOR OPERATION
44h 00h DT L P WROM AE B KV F INTERNAL TARGET FAILURE
21h 02h R INVALID ADDRESS FOR WRITE
3Dh 00h DT L P WROM AE K INVALID BITS IN IDENTIFY MESSAGE
2Ch 02h INVALID COMBINATION OF WINDOWS SPECIFIED
20h 00h DT L P WROM AE B KV F INVALID COMMAND OPERATION CODE
26h 0Fh F INVALID DATA-OUT BUFFER INTEGRITY CHECK VALUE
21h 01h DT WROM BK INVALID ELEMENT ADDRESS
24h 00h DT L P WROM AE B KV F INVALID FIELD IN CDB
0Eh 03h DT P R M AE B K F INVALID FIELD IN COMMAND INFORMATION UNIT
26h 00h DT L P WROM AE B KV F INVALID FIELD IN PARAMETER LIST
0Eh 00h DT P WROM AE B K F INVALID INFORMATION UNIT
49h 00h DT L P WROM AE B KV F INVALID MESSAGE ERROR
26h 0Ch DT L P WRO K INVALID OPERATION FOR COPY SOURCE OR DESTINATION
64h 01h R INVALID PACKET SIZE
26h 0Eh DT P WROM AE B K INVALID PARAMETER WHILE PORT IS ENABLED
26h 04h DT L P WROM AE B KV F INVALID RELEASE OF PERSISTENT RESERVATION
74h 12h DT R M AE B KV INVALID SA USAGE
4Bh 01h DT P WROM AE B K INVALID TARGET PORT TRANSFER TAG RECEIVED
23h 00h DT P B INVALID TOKEN OPERATION, CAUSE NOT REPORTABLE
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

90 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 55 — ASC and ASCQ assignments (part 9 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
23h 0Ah DT P B INVALID TOKEN OPERATION, INVALID TOKEN LENGTH
INVALID TOKEN OPERATION, REMOTE ROD TOKEN CREATION NOT
23h 03h DT P B
SUPPORTED
INVALID TOKEN OPERATION, REMOTE TOKEN USAGE NOT
23h 02h DT P B
SUPPORTED
23h 08h DT P B INVALID TOKEN OPERATION, TOKEN CANCELLED
23h 05h DT P B INVALID TOKEN OPERATION, TOKEN CORRUPT
23h 09h DT P B INVALID TOKEN OPERATION, TOKEN DELETED
23h 07h DT P B INVALID TOKEN OPERATION, TOKEN EXPIRED
23h 06h DT P B INVALID TOKEN OPERATION, TOKEN REVOKED
23h 04h DT P B INVALID TOKEN OPERATION, TOKEN UNKNOWN
23h 01h DT P B INVALID TOKEN OPERATION, UNSUPPORTED TOKEN TYPE
21h 03h R INVALID WRITE CROSSING LAYER JUMP
24h 08h DT R M AE B KV INVALID XCDB
29h 07h DT L P WROM AE B KV F I_T NEXUS LOSS OCCURRED
11h 05h WRO B L-EC UNCORRECTABLE ERROR
60h 00h LAMP FAILURE
14h 07h T LOCATE OPERATION FAILURE
00h 19h T LOCATE OPERATION IN PROGRESS
5Bh 02h DT L P WROM K LOG COUNTER AT MAXIMUM
5Bh 00h DT L P WROM K LOG EXCEPTION
5Bh 03h DT L P WROM K LOG LIST CODES EXHAUSTED
2Ah 02h DT L WROM AE K LOG PARAMETERS CHANGED
21h 00h DT WRO BK LOGICAL BLOCK ADDRESS OUT OF RANGE
10h 02h DT W O LOGICAL BLOCK APPLICATION TAG CHECK FAILED
10h 01h DT W O LOGICAL BLOCK GUARD CHECK FAILED
10h 04h T LOGICAL BLOCK PROTECTION ERROR ON RECOVER BUFFERED DATA
10h 05h T LOGICAL BLOCK PROTECTION METHOD ERROR
10h 03h DT W O LOGICAL BLOCK REFERENCE TAG CHECK FAILED
74h 71h DT R M E V LOGICAL UNIT ACCESS NOT AUTHORIZED
08h 03h DT ROM BK LOGICAL UNIT COMMUNICATION CRC ERROR (ULTRA-DMA/32)
08h 00h DT L WROM AE B KV F LOGICAL UNIT COMMUNICATION FAILURE
08h 02h DT L WROM AE B KV F LOGICAL UNIT COMMUNICATION PARITY ERROR
08h 01h DT L WROM AE B KV F LOGICAL UNIT COMMUNICATION TIME-OUT
05h 00h DT L WROM AE B KV F LOGICAL UNIT DOES NOT RESPOND TO SELECTION
4Ch 00h DT L P WROM AE B KV F LOGICAL UNIT FAILED SELF-CONFIGURATION
3Eh 03h DT L P WROM AE B KV F LOGICAL UNIT FAILED SELF-TEST
3Eh 01h DT L P WROM AE B KV F LOGICAL UNIT FAILURE
5Dh 02h R LOGICAL UNIT FAILURE PREDICTION THRESHOLD EXCEEDED
3Eh 00h DT L P WROM AE B KV F LOGICAL UNIT HAS NOT SELF-CONFIGURED YET
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 91

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 55 — ASC and ASCQ assignments (part 10 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
04h 01h DT L P WROM AE B KV F LOGICAL UNIT IS IN PROCESS OF BECOMING READY
LOGICAL UNIT NOT ACCESSIBLE, ASYMMETRIC ACCESS STATE
04h 0Ah DT L P WROM AE B KV F
TRANSITION
04h 0Bh DT L P WROM AE B KV F LOGICAL UNIT NOT ACCESSIBLE, TARGET PORT IN STANDBY STATE
LOGICAL UNIT NOT ACCESSIBLE, TARGET PORT IN UNAVAILABLE
04h 0Ch DT L P WROM AE B KV F
STATE
68h 00h A LOGICAL UNIT NOT CONFIGURED
04h 18h M LOGICAL UNIT NOT READY, A DOOR IS OPEN
LOGICAL UNIT NOT READY, ADDITIONAL POWER USE NOT YET
04h 1Ch DT M AE B
GRANTED
04h 10h DT WROM B LOGICAL UNIT NOT READY, AUXILIARY MEMORY NOT ACCESSIBLE
04h 17h M LOGICAL UNIT NOT READY, CALIBRATION REQUIRED
04h 00h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE
04h 1Dh D LOGICAL UNIT NOT READY, CONFIGURATION IN PROGRESS
04h 16h M LOGICAL UNIT NOT READY, CONFIGURATION REQUIRED
04h 04h DT L RO B LOGICAL UNIT NOT READY, FORMAT IN PROGRESS
04h 21h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, HARD RESET REQUIRED
04h 02h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, INITIALIZING COMMAND REQUIRED
04h 20h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, LOGICAL UNIT RESET REQUIRED
04h 08h R LOGICAL UNIT NOT READY, LONG WRITE IN PROGRESS
04h 03h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED
04h 1Eh D LOGICAL UNIT NOT READY, MICROCODE ACTIVATION REQUIRED
04h 1Fh DT L P WROM AE B KV F LOGICAL UNIT NOT READY, MICROCODE DOWNLOAD REQUIRED
04h 11h DT WRO AE B V F LOGICAL UNIT NOT READY, NOTIFY (ENABLE SPINUP) REQUIRED
04h 12h M V LOGICAL UNIT NOT READY, OFFLINE
04h 19h M LOGICAL UNIT NOT READY, OPERATING IN SEQUENTIAL MODE
04h 07h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, OPERATION IN PROGRESS
04h 22h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, POWER CYCLE REQUIRED
04h 05h DT W O A B K F LOGICAL UNIT NOT READY, REBUILD IN PROGRESS
04h 06h DT W O A BK LOGICAL UNIT NOT READY, RECALCULATION IN PROGRESS
04h 15h M LOGICAL UNIT NOT READY, ROBOTICS DISABLED
04h 13h DT R M AE B KV LOGICAL UNIT NOT READY, SA CREATION IN PROGRESS
04h 1Bh D B LOGICAL UNIT NOT READY, SANITIZE IN PROGRESS
04h 0Eh DT R M AE B KV F LOGICAL UNIT NOT READY, SECURITY SESSION IN PROGRESS
04h 09h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, SELF-TEST IN PROGRESS
04h 14h D B LOGICAL UNIT NOT READY, SPACE ALLOCATION IN PROGRESS
LOGICAL UNIT NOT READY, START STOP UNIT COMMAND IN
04h 1Ah D B
PROGRESS
04h 0Dh F LOGICAL UNIT NOT READY, STRUCTURE CHECK REQUIRED
25h 00h DT L P WROM AE B KV F LOGICAL UNIT NOT SUPPORTED
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

92 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 55 — ASC and ASCQ assignments (part 11 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
27h 02h DT WRO BK LOGICAL UNIT SOFTWARE WRITE PROTECTED
00h 1Fh DT B LOGICAL UNIT TRANSITIONING TO ANOTHER POWER CONDITION
3Eh 04h DT L P WROM AE B KV F LOGICAL UNIT UNABLE TO UPDATE SELF-TEST LOG
5Eh 00h DT L P WRO A K LOW POWER CONDITION ON
MAXIMUM NUMBER OF SUPPLEMENTAL DECRYPTION KEYS
55h 08h T
EXCEEDED
15h 01h DT L WROM BK MECHANICAL POSITIONING ERROR
3Bh 16h R MECHANICAL POSITIONING OR CHANGER ERROR
5Dh 01h R B MEDIA FAILURE PREDICTION THRESHOLD EXCEEDED
53h 00h DT L WROM BK MEDIA LOAD OR EJECT FAILED
6Fh 04h R MEDIA REGION CODE IS MISMATCHED TO LOGICAL UNIT REGION
3Fh 11h DT WROM B MEDIUM AUXILIARY MEMORY ACCESSIBLE
55h 09h M MEDIUM AUXILIARY MEMORY NOT ACCESSIBLE
3Bh 0Dh DT WROM BK MEDIUM DESTINATION ELEMENT FULL
31h 00h DT WRO BK MEDIUM FORMAT CORRUPTED
3Fh 10h DT WROM B MEDIUM LOADABLE
3Bh 13h DT WROM BK MEDIUM MAGAZINE INSERTED
3Bh 14h DT WROM BK MEDIUM MAGAZINE LOCKED
3Bh 11h DT WROM BK MEDIUM MAGAZINE NOT ACCESSIBLE
3Bh 12h DT WROM BK MEDIUM MAGAZINE REMOVED
3Bh 15h DT WROM BK MEDIUM MAGAZINE UNLOCKED
30h 10h R MEDIUM NOT FORMATTED
3Ah 00h DT L WROM BK MEDIUM NOT PRESENT
3Ah 03h DT WROM B MEDIUM NOT PRESENT - LOADABLE
3Ah 04h DT WRO B MEDIUM NOT PRESENT - MEDIUM AUXILIARY MEMORY ACCESSIBLE
3Ah 01h DT WROM BK MEDIUM NOT PRESENT - TRAY CLOSED
3Ah 02h DT WROM BK MEDIUM NOT PRESENT - TRAY OPEN
53h 02h DT WROM BK MEDIUM REMOVAL PREVENTED
53h 03h M MEDIUM REMOVAL PREVENTED BY DATA TRANSFER ELEMENT
2Ah 15h T M V MEDIUM REMOVAL PREVENTION PREEMPTED
3Bh 0Eh DT WROM BK MEDIUM SOURCE ELEMENT EMPTY
53h 04h T MEDIUM THREAD OR UNTHREAD FAILURE
43h 00h DT L P WROM AE B KV F MESSAGE ERROR
3Fh 01h DT L P WROM AE B KV F MICROCODE HAS BEEN CHANGED
3Fh 16h DT P WROM AE B KV F MICROCODE HAS BEEN CHANGED WITHOUT RESET
1Dh 00h DT WRO BK MISCOMPARE DURING VERIFY OPERATION
1Dh 01h D B MISCOMPARE VERIFY OF UNMAPPED LBA
11h 0Ah DT O BK MISCORRECTED ERROR
2Ah 01h DT L WROM AE B KV F MODE PARAMETERS CHANGED
67h 03h A MODIFICATION OF LOGICAL UNIT FAILED
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 93

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 55 — ASC and ASCQ assignments (part 12 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
69h 01h A MULTIPLE LOGICAL UNIT FAILURES
07h 00h DT L WROM BK MULTIPLE PERIPHERAL DEVICES SELECTED
11h 03h DT W O BK MULTIPLE READ ERRORS
0Ch 0Eh DT W O BK MULTIPLE WRITE ERRORS
67h 09h A MULTIPLY ASSIGNED LOGICAL UNIT
4Bh 04h DT P WROM AE B K NAK RECEIVED
00h 00h DT L P WROM AE B KV F NO ADDITIONAL SENSE INFORMATION
00h 15h R NO CURRENT AUDIO STATUS TO RETURN
32h 00h D W O BK NO DEFECT SPARE LOCATION AVAILABLE
11h 09h T NO GAP FOUND
01h 00h D W O BK NO INDEX/SECTOR SIGNAL
72h 07h R NO MORE TEST ZONE EXTENSIONS ARE ALLOWED
72h 05h R NO MORE TRACK RESERVATIONS ALLOWED
06h 00h D WROM BK NO REFERENCE POSITION FOUND
02h 00h D WRO BK NO SEEK COMPLETE
03h 01h T NO WRITE CURRENT
24h 06h F NONCE NOT UNIQUE
24h 07h F NONCE TIMESTAMP OUT OF RANGE
28h 00h DT L P WROM AE B KV F NOT READY TO READY CHANGE, MEDIUM MAY HAVE CHANGED
2Ch 0Bh T NOT RESERVED
00h 16h DT L P WROM AE B KV F OPERATION IN PROGRESS
5Ah 01h DT WROM BK OPERATOR MEDIUM REMOVAL REQUEST
5Ah 00h DT L P WRO BK OPERATOR REQUEST OR STATE CHANGE INPUT
5Ah 03h DT WRO A B K OPERATOR SELECTED WRITE PERMIT
5Ah 02h DT WRO A B K OPERATOR SELECTED WRITE PROTECT
2Ch 0Ch D ORWRITE GENERATION DOES NOT MATCH
61h 02h OUT OF FOCUS
4Eh 00h DT L P WROM AE B KV F OVERLAPPED COMMANDS ATTEMPTED
2Dh 00h T OVERWRITE ERROR ON UPDATE IN PLACE
20h 05h T Obsolete
24h 02h T Obsolete
24h 03h T Obsolete
63h 01h R PACKET DOES NOT FIT IN AVAILABLE SPACE
3Bh 05h L PAPER JAM
1Ah 00h DT L P WROM AE B KV F PARAMETER LIST LENGTH ERROR
26h 01h DT L P WROM AE B KV F PARAMETER NOT SUPPORTED
26h 02h DT L P WROM AE B KV F PARAMETER VALUE INVALID
2Ah 00h DT L WROM AE B KV F PARAMETERS CHANGED
69h 02h A PARITY/DATA MISMATCH
1Fh 00h D O K PARTIAL DEFECT LIST TRANSFER
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

94 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 55 — ASC and ASCQ assignments (part 13 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
2Ch 0Ah F PARTITION OR COLLECTION CONTAINS USER OBJECTS
4Bh 14h DT P WROM AE B K F PCIE ACS VIOLATION
4Bh 10h DT P WROM AE B K F PCIE COMPLETER ABORT
4Bh 0Fh DT P WROM AE B K F PCIE COMPLETION TIMEOUT
4Bh 12h DT P WROM AE B K F PCIE ECRC CHECK FAILED
4Bh 0Eh DT P WROM AE B K F PCIE FABRIC ERROR
4Bh 11h DT P WROM AE B K F PCIE POISONED TLP RECEIVED
4Bh 15h DT P WROM AE B K F PCIE TLP PREFIX BLOCKED
4Bh 13h DT P WROM AE B K F PCIE UNSUPPORTED REQUEST
03h 00h DT L W O BK PERIPHERAL DEVICE WRITE FAULT
27h 05h T R PERMANENT WRITE PROTECT
2Ch 06h R PERSISTENT PREVENT CONFLICT
44h 01h DT P M AE B KV F PERSISTENT RESERVATION INFORMATION LOST
27h 04h T R PERSISTENT WRITE PROTECT
47h 06h DT M AE B KV F PHY TEST FUNCTION IN PROGRESS
50h 02h T POSITION ERROR RELATED TO TIMING
3Bh 0Ch T POSITION PAST BEGINNING OF MEDIUM
3Bh 0Bh POSITION PAST END OF MEDIUM
15h 02h DT WRO BK POSITIONING ERROR DETECTED BY READ OF MEDIUM
73h 01h R POWER CALIBRATION AREA ALMOST FULL
73h 03h R POWER CALIBRATION AREA ERROR
73h 02h R POWER CALIBRATION AREA IS FULL
29h 01h DT L P WROM AE B KV F POWER ON OCCURRED
29h 00h DT L P WROM AE B KV F POWER ON, RESET, OR BUS DEVICE RESET OCCURRED
5Eh 41h B POWER STATE CHANGE TO ACTIVE
5Eh 47h BK POWER STATE CHANGE TO DEVICE CONTROL
5Eh 42h B POWER STATE CHANGE TO IDLE
5Eh 45h B POWER STATE CHANGE TO SLEEP
5Eh 43h B POWER STATE CHANGE TO STANDBY
42h 00h D POWER-ON OR SELF-TEST FAILURE (SHOULD USE 40 NN)
2Ch 07h DT L P WROM AE B KV F PREVIOUS BUSY STATUS
2Ch 09h DT L P WROM E B KV F PREVIOUS RESERVATION CONFLICT STATUS
2Ch 08h DT L P WROM AE B KV F PREVIOUS TASK SET FULL STATUS
1Ch 01h D O BK PRIMARY DEFECT LIST NOT FOUND
2Ah 08h DT WROM AE B KV F PRIORITY CHANGED
73h 05h R PROGRAM MEMORY AREA IS FULL
73h 04h R PROGRAM MEMORY AREA UPDATE FAILURE
00h 07h T PROGRAMMABLE EARLY WARNING DETECTED
47h 05h DT L P WROM AE B KV F PROTOCOL SERVICE CRC ERROR
55h 07h F QUOTA ERROR
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 95

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 55 — ASC and ASCQ assignments (part 14 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
40h 00h D RAM FAILURE (SHOULD USE 40 NN)
15h 00h DT L WROM BK RANDOM POSITIONING ERROR
73h 17h R RDZ IS FULL
21h 07h D READ BOUNDARY VIOLATION
11h 13h DT L P WRO AE B KV F READ ERROR - FAILED RETRANSMISSION REQUEST
11h 14h D READ ERROR - LBA MARKED BAD BY APPLICATION CLIENT
11h 11h R READ ERROR - LOSS OF STREAMING
6Fh 03h R READ OF SCRAMBLED SECTOR WITHOUT AUTHENTICATION
3Bh 0Ah READ PAST BEGINNING OF MEDIUM
3Bh 09h READ PAST END OF MEDIUM
3Bh 17h F READ PAST END OF USER OBJECT
11h 01h DT WRO BK READ RETRIES EXHAUSTED
6Ch 00h A REBUILD FAILURE OCCURRED
6Dh 00h A RECALCULATE FAILURE OCCURRED
14h 01h DT WRO BK RECORD NOT FOUND
14h 06h DT W O BK RECORD NOT FOUND - DATA AUTO-REALLOCATED
14h 05h DT W O BK RECORD NOT FOUND - RECOMMEND REASSIGNMENT
14h 00h DT L WRO BK RECORDED ENTITY NOT FOUND
18h 02h D WRO BK RECOVERED DATA - DATA AUTO-REALLOCATED
18h 05h D WRO BK RECOVERED DATA - RECOMMEND REASSIGNMENT
18h 06h D WRO BK RECOVERED DATA - RECOMMEND REWRITE
17h 05h D WRO BK RECOVERED DATA USING PREVIOUS SECTOR ID
18h 03h R RECOVERED DATA WITH CIRC
18h 07h D W O BK RECOVERED DATA WITH ECC - DATA REWRITTEN
18h 01h D WRO BK RECOVERED DATA WITH ERROR CORR. & RETRIES APPLIED
18h 00h DT WRO BK RECOVERED DATA WITH ERROR CORRECTION APPLIED
18h 04h R RECOVERED DATA WITH L-EC
18h 08h R RECOVERED DATA WITH LINKING
17h 03h DT WRO BK RECOVERED DATA WITH NEGATIVE HEAD OFFSET
17h 00h DT WRO BK RECOVERED DATA WITH NO ERROR CORRECTION APPLIED
17h 02h DT WRO BK RECOVERED DATA WITH POSITIVE HEAD OFFSET
17h 01h DT WRO BK RECOVERED DATA WITH RETRIES
17h 04h WRO B RECOVERED DATA WITH RETRIES AND/OR CIRC APPLIED
17h 06h D W O BK RECOVERED DATA WITHOUT ECC - DATA AUTO-REALLOCATED
17h 09h D WRO BK RECOVERED DATA WITHOUT ECC - DATA REWRITTEN
17h 07h D WRO BK RECOVERED DATA WITHOUT ECC - RECOMMEND REASSIGNMENT
17h 08h D WRO BK RECOVERED DATA WITHOUT ECC - RECOMMEND REWRITE
1Eh 00h D W O BK RECOVERED ID WITH ECC CORRECTION
3Fh 06h DT WROM AE B REDUNDANCY GROUP CREATED OR MODIFIED
3Fh 07h DT WROM AE B REDUNDANCY GROUP DELETED
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

96 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 55 — ASC and ASCQ assignments (part 15 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
6Bh 01h A REDUNDANCY LEVEL GOT BETTER
6Bh 02h A REDUNDANCY LEVEL GOT WORSE
2Ah 05h DT L P WROM AE REGISTRATIONS PREEMPTED
67h 05h A REMOVE OF LOGICAL UNIT FAILED
3Fh 0Eh DT L P WROM AE REPORTED LUNS DATA HAS CHANGED
3Bh 08h T REPOSITION ERROR
2Ah 03h DT L P WROM AE K RESERVATIONS PREEMPTED
2Ah 04h DT L P WROM AE RESERVATIONS RELEASED
00h 1Ah T REWIND OPERATION IN PROGRESS
36h 00h L RIBBON, INK, OR TONER FAILURE
73h 06h R RMA/PMA IS ALMOST FULL
72h 06h R RMZ EXTENSION IS NOT ALLOWED
37h 00h DT L WROM AE B KV F ROUNDED PARAMETER
5Ch 00h D O RPL STATUS CHANGE
2Ah 14h DT R M AE B KV SA CREATION CAPABILITIES DATA HAS CHANGED
74h 30h DT R M AE B KV SA CREATION PARAMETER NOT SUPPORTED
74h 10h DT R M AE B KV SA CREATION PARAMETER VALUE INVALID
74h 11h DT R M AE B KV SA CREATION PARAMETER VALUE REJECTED
31h 03h D B SANITIZE COMMAND FAILED
39h 00h DT L WROM AE K SAVING PARAMETERS NOT SUPPORTED
62h 00h SCAN HEAD POSITIONING ERROR
29h 02h DT L P WROM AE B KV F SCSI BUS RESET OCCURRED
47h 00h DT L P WROM AE B KV F SCSI PARITY ERROR
47h 02h DT L P WROM AE B KV F SCSI PARITY ERROR DETECTED DURING ST DATA PHASE
54h 00h P SCSI TO HOST SYSTEM INTERFACE FAILURE
24h 04h F SECURITY AUDIT VALUE FROZEN
74h 79h D SECURITY CONFLICT IN TRANSLATED DEVICE
74h 00h T SECURITY ERROR
24h 05h F SECURITY WORKING KEY FROZEN
45h 00h DT L P WROM AE B KV F SELECT OR RESELECT FAILURE
3Bh 00h TL SEQUENTIAL POSITIONING ERROR
5Dh 45h D B SERVO IMPENDING FAILURE ACCESS TIMES TOO HIGH
5Dh 47h D B SERVO IMPENDING FAILURE CHANNEL PARAMETRICS
5Dh 48h D B SERVO IMPENDING FAILURE CONTROLLER DETECTED
5Dh 42h D B SERVO IMPENDING FAILURE DATA ERROR RATE TOO HIGH
5Dh 4Ch D B SERVO IMPENDING FAILURE DRIVE CALIBRATION RETRY COUNT
5Dh 41h D B SERVO IMPENDING FAILURE DRIVE ERROR RATE TOO HIGH
5Dh 40h D B SERVO IMPENDING FAILURE GENERAL HARD DRIVE FAILURE
5Dh 43h D B SERVO IMPENDING FAILURE SEEK ERROR RATE TOO HIGH
5Dh 4Ah D B SERVO IMPENDING FAILURE SEEK TIME PERFORMANCE
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 97

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 55 — ASC and ASCQ assignments (part 16 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
5Dh 4Bh D B SERVO IMPENDING FAILURE SPIN-UP RETRY COUNT
5Dh 46h D B SERVO IMPENDING FAILURE START UNIT TIMES TOO HIGH
5Dh 49h D B SERVO IMPENDING FAILURE THROUGHPUT PERFORMANCE
5Dh 44h D B SERVO IMPENDING FAILURE TOO MANY BLOCK REASSIGNS
72h 00h R SESSION FIXATION ERROR
72h 03h R SESSION FIXATION ERROR - INCOMPLETE TRACK IN SESSION
72h 01h R SESSION FIXATION ERROR WRITING LEAD-IN
72h 02h R SESSION FIXATION ERROR WRITING LEAD-OUT
00h 1Bh T SET CAPACITY OPERATION IN PROGRESS
67h 0Ah DT L P WROM AE B KV F SET TARGET PORT GROUPS COMMAND FAILED
00h 03h T SETMARK DETECTED
3Bh 04h L SLEW FAILURE
47h 7Fh DT P WROM AE B K SOME COMMANDS CLEARED BY ISCSI PROTOCOL EVENT
2Fh 03h DT L P WROM AE B KV F SOME COMMANDS CLEARED BY QUEUING LAYER EVENT
27h 07h D B SPACE ALLOCATION FAILED WRITE PROTECT
5Dh 03h R SPARE AREA EXHAUSTION PREDICTION THRESHOLD EXCEEDED
3Fh 08h DT WROM AE B SPARE CREATED OR MODIFIED
3Fh 09h DT WROM AE B SPARE DELETED
5Dh 55h D B SPINDLE IMPENDING FAILURE ACCESS TIMES TOO HIGH
5Dh 57h D B SPINDLE IMPENDING FAILURE CHANNEL PARAMETRICS
5Dh 58h D B SPINDLE IMPENDING FAILURE CONTROLLER DETECTED
5Dh 52h D B SPINDLE IMPENDING FAILURE DATA ERROR RATE TOO HIGH
5Dh 5Ch D B SPINDLE IMPENDING FAILURE DRIVE CALIBRATION RETRY COUNT
5Dh 51h D B SPINDLE IMPENDING FAILURE DRIVE ERROR RATE TOO HIGH
5Dh 50h D B SPINDLE IMPENDING FAILURE GENERAL HARD DRIVE FAILURE
5Dh 53h D B SPINDLE IMPENDING FAILURE SEEK ERROR RATE TOO HIGH
5Dh 5Ah D B SPINDLE IMPENDING FAILURE SEEK TIME PERFORMANCE
5Dh 5Bh D B SPINDLE IMPENDING FAILURE SPIN-UP RETRY COUNT
5Dh 56h D B SPINDLE IMPENDING FAILURE START UNIT TIMES TOO HIGH
5Dh 59h D B SPINDLE IMPENDING FAILURE THROUGHPUT PERFORMANCE
5Dh 54h D B SPINDLE IMPENDING FAILURE TOO MANY BLOCK REASSIGNS
09h 03h WRO SPINDLE SERVO FAILURE
5Ch 02h D O SPINDLES NOT SYNCHRONIZED
5Ch 01h D O SPINDLES SYNCHRONIZED
5Eh 04h DT L P WRO A K STANDBY CONDITION ACTIVATED BY COMMAND
5Eh 02h DT L P WRO A K STANDBY CONDITION ACTIVATED BY TIMER
5Eh 0Ah DT L P WRO A K STANDBY_Y CONDITION ACTIVATED BY COMMAND
5Eh 09h DT L P WRO A K STANDBY_Y CONDITION ACTIVATED BY TIMER
6Bh 00h A STATE CHANGE HAS OCCURRED
68h 01h D SUBSIDIARY LOGICAL UNIT NOT CONFIGURED
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

98 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 55 — ASC and ASCQ assignments (part 17 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
1Bh 00h DT L P WROM AE B KV F SYNCHRONOUS DATA TRANSFER ERROR
55h 01h D O BK SYSTEM BUFFER FULL
55h 00h P SYSTEM RESOURCE FAILURE
4Dh NNh DT L P WROM AE B KV F TAGGED OVERLAPPED COMMANDS (NN = TASK TAG)
33h 00h T TAPE LENGTH ERROR
3Bh 03h L TAPE OR ELECTRONIC VERTICAL FORMS UNIT NOT READY
3Bh 01h T TAPE POSITION ERROR AT BEGINNING-OF-MEDIUM
3Bh 02h T TAPE POSITION ERROR AT END-OF-MEDIUM
3Fh 00h DT L P WROM AE B KV F TARGET OPERATING CONDITIONS HAVE CHANGED
38h 07h D THIN PROVISIONING SOFT THRESHOLD REACHED
0Dh 01h DT L P WRO A K THIRD PARTY DEVICE FAILURE
5Bh 01h DT L P WROM K THRESHOLD CONDITION MET
26h 03h DT L P WROM AE K THRESHOLD PARAMETERS NOT SUPPORTED
3Eh 02h DT L P WROM AE B KV F TIMEOUT ON LOGICAL UNIT
2Ah 10h DT M E V TIMESTAMP CHANGED
TOO MANY LOGICAL OBJECTS ON PARTITION TO SUPPORT
3Bh 1Ch T
OPERATION
26h 08h DT L P WRO K TOO MANY SEGMENT DESCRIPTORS
26h 06h DT L P WRO K TOO MANY TARGET DESCRIPTORS
2Ch 01h TOO MANY WINDOWS SPECIFIED
4Bh 02h DT P WROM AE B K TOO MUCH WRITE DATA
09h 00h DT WRO B TRACK FOLLOWING ERROR
09h 01h WRO K TRACKING SERVO FAILURE
29h 06h DT L P WROM AE B KV F TRANSCEIVER MODE CHANGED TO LVD
29h 05h DT L P WROM AE B KV F TRANSCEIVER MODE CHANGED TO SINGLE-ENDED
61h 01h UNABLE TO ACQUIRE VIDEO
74h 01h T UNABLE TO DECRYPT DATA
74h 0Ch DT R M AE B KV UNABLE TO DECRYPT PARAMETER LIST
57h 00h R UNABLE TO RECOVER TABLE-OF-CONTENTS
21h 04h D UNALIGNED WRITE COMMAND
74h 02h T UNENCRYPTED DATA ENCOUNTERED WHILE DECRYPTING
26h 0Ah DT L P WRO K UNEXPECTED INEXACT SEGMENT
74h 06h T UNKNOWN SIGNATURE VERIFICATION KEY
53h 01h T UNLOAD TAPE FAILURE
08h 04h DT L P WRO K UNREACHABLE COPY TARGET
11h 00h DT WRO BK UNRECOVERED READ ERROR
11h 04h D W O BK UNRECOVERED READ ERROR - AUTO REALLOCATE FAILED
11h 0Bh D W O BK UNRECOVERED READ ERROR - RECOMMEND REASSIGNMENT
11h 0Ch D W O BK UNRECOVERED READ ERROR - RECOMMEND REWRITE THE DATA
46h 00h DT L P WROM BK UNSUCCESSFUL SOFT RESET
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 99

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 55 — ASC and ASCQ assignments (part 18 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
35h 01h DT L P WROM AE B KV F UNSUPPORTED ENCLOSURE FUNCTION
26h 09h DT L P WRO K UNSUPPORTED SEGMENT DESCRIPTOR TYPE CODE
26h 07h DT L P WRO K UNSUPPORTED TARGET DESCRIPTOR TYPE CODE
59h 00h O UPDATED BLOCK READ
26h 12h T VENDOR SPECIFIC KEY REFERENCE NOT FOUND
00h 1Ch T VERIFY OPERATION IN PROGRESS
61h 00h VIDEO ACQUISITION ERROR
65h 00h DT L P WROM AE B KV F VOLTAGE FAULT
53h 05h M VOLUME IDENTIFIER INVALID
53h 06h M VOLUME IDENTIFIER MISSING
3Fh 0Ah DT WROM AE B K VOLUME SET CREATED OR MODIFIED
3Fh 0Ch DT WROM AE B K VOLUME SET DEASSIGNED
3Fh 0Bh DT WROM AE B K VOLUME SET DELETED
3Fh 0Dh DT WROM AE B K VOLUME SET REASSIGNED
0Bh 00h DT L P WROM AE B KV F WARNING
0Bh 05h DT L P WRO AE B KV F WARNING - BACKGROUND MEDIUM SCAN DETECTED MEDIUM ERROR
0Bh 04h DT L P WRO AE B KV F WARNING - BACKGROUND PRE-SCAN DETECTED MEDIUM ERROR
0Bh 03h DT L P WROM AE B KV F WARNING - BACKGROUND SELF-TEST FAILED
0Bh 07h DT L P WROM AE B KV F WARNING - DEGRADED POWER TO NON-VOLATILE CACHE
0Bh 09h D WARNING - DEVICE STATISTICS NOTIFICATION ACTIVE
0Bh 02h DT L P WROM AE B KV F WARNING - ENCLOSURE DEGRADED
0Bh 06h DT L P WROM AE B KV F WARNING - NON-VOLATILE CACHE NOW VOLATILE
0Bh 08h DT L P WROM AE B KV F WARNING - POWER LOSS EXPECTED
0Bh 01h DT L P WROM AE B KV F WARNING - SPECIFIED TEMPERATURE EXCEEDED
30h 0Dh T WORM MEDIUM - INTEGRITY CHECK
30h 0Ch T WORM MEDIUM - OVERWRITE ATTEMPTED
11h 15h D WRITE AFTER SANITIZE REQUIRED
50h 00h T WRITE APPEND ERROR
50h 01h T WRITE APPEND POSITION ERROR
21h 05h D WRITE BOUNDARY VIOLATION
0Ch 00h T R WRITE ERROR
0Ch 02h D W O BK WRITE ERROR - AUTO REALLOCATION FAILED
0Ch 09h R WRITE ERROR - LOSS OF STREAMING
0Ch 0Dh DT L P WRO AE B KV F WRITE ERROR - NOT ENOUGH UNSOLICITED DATA
0Ch 0Ah R WRITE ERROR - PADDING BLOCKS ADDED
0Ch 03h D W O BK WRITE ERROR - RECOMMEND REASSIGNMENT
0Ch 01h K WRITE ERROR - RECOVERED WITH AUTO REALLOCATION
0Ch 08h R WRITE ERROR - RECOVERY FAILED
0Ch 07h R WRITE ERROR - RECOVERY NEEDED
0Ch 0Ch DT L P WRO AE B KV F WRITE ERROR - UNEXPECTED UNSOLICITED DATA
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

100 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 55 — ASC and ASCQ assignments (part 19 of 19)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
27h 00h DT WRO BK WRITE PROTECTED
27h 08h D ZONE IS READ ONLY
31h 02h R ZONED FORMATTING FAILED DUE TO SPARE LINKING
3Fh 12h DT L P WR M AE B K F iSCSI IP ADDRESS ADDED
3Fh 14h DT L P WR M AE B K F iSCSI IP ADDRESS CHANGED
3Fh 13h DT L P WR M AE B K F iSCSI IP ADDRESS REMOVED

80h xxh \
Through > Vendor specific
FFh xxh /

xxh 80h \
Through > Vendor specific qualification of standard ASC
xxh FFh /
All codes not shown are reserved.
A numeric ordered listing of the ASC and ASCQ assignments is provided in F.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 101

T10/BSR INCITS 513 Revision 37 17 May 2014

5 Model common to all device types

5.1 Introduction to the model common to all device types

5.1.1 Overview

This model describes some of the general characteristics expected of most SCSI devices. This model is not
intended to alter any requirements defined elsewhere in SCSI. Devices conforming to this standard shall
conform to SAM-5.

5.1.2 Important commands for all SCSI device servers

5.1.2.1 Commands implemented by all SCSI device servers

This standard defines the following mandatory commands (see 6.1):

a) the INQUIRY command (see 5.1.2.3);

b) the REPORT LUNS command (see 5.1.2.4); and
c) the TEST UNIT READY command (see 5.1.2.5).

These commands are used to discover a logical unit’s capabilities, to discover the system configuration, and
to determine whether a logical unit is ready.

If the device server is able to process commands after an error occurs that prohibits normal command
completion, then the device server may include a field replaceable unit code in the sense data when returning
CHECK CONDITION status for commands other than the INQUIRY command (see 6.6), the REPORT LUNS
command (see 6.33), and the REQUEST SENSE command (see 6.39). If the sense data includes a field
replaceable unit code, then an application client may use the INQUIRY command to request the
corresponding ASCII Information VPD page (see 7.8.3), if any, which contains ASCII information about the
field replaceable unit causing the error.

5.1.2.2 Commands recommended for all SCSI device servers

Support for the REQUEST SENSE command is recommended to provide compatibility with application clients
designed to use previous versions of this standard or status polling features defined by command standards.

5.1.2.3 Using the INQUIRY command

The INQUIRY command (see 6.6) may be used by an application client to determine the configuration of a
logical unit. Device servers respond with information that includes their device type and standard version and
may include the manufacturer's identification, model number and other information.

The Device Identification VPD page (see 7.8.6) returned in response to an INQUIRY command with the EVPD
bit set to one and the PAGE CODE field set to 83h contains identifying information for the logical unit, the target
port, and the SCSI target device.

The INQUIRY command may return incomplete information until the device serve completes the power on
process (see 6.6.1).

102 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.1.2.4 Using the REPORT LUNS command

The REPORT LUNS command (see 6.33) may be used by an application client to request a logical unit
inventory report of the logical units that are accessible to the I_T nexus on which the command is sent.

The application client may select different types of logical unit inventories to be reported. Examples of using
different logical unit inventory report types are shown in Annex B.

5.1.2.5 Using the TEST UNIT READY command

The TEST UNIT READY command (see 6.47) allows an application client to poll a logical unit until it is ready
without allocating space for returned data. The TEST UNIT READY command may be used to check the
media status of logical units with removable media. Device servers should respond promptly to indicate the
current status of the SCSI device.

5.1.2.6 Using the REQUEST SENSE command

The REQUEST SENSE command (see 6.39) may be used by an application client to poll the status of some
background operations and to clear interlocked unit attention conditions (see 7.5.8).

5.1.3 Implicit head of queue

Each of the following commands may be processed by the task manager as if the command has a task
attribute of HEAD OF QUEUE (see SAM-5) if the command is received with a SIMPLE task attribute or an ORDERED
task attribute:

a) INQUIRY; and
b) REPORT LUNS.

See SAM-5 for additional rules on implicit head of queue processing.

5.2 Device clocks and timestamps

A timestamp may be included in data logged or recorded by a device server based on a the contents of a
device clock saturating counter described in this subclause.

Device clocks may be managed with:

a) the REPORT TIMESTAMP command (see 6.38);

b) the SET TIMESTAMP command (see 6.46);
c) the Control Extension mode page (see 7.5.9); and
d) methods outside the scope of this standard.

A device clock is initialized by a:

a) power on reset or hard reset that sets a device clock to zero;

b) SET TIMESTAMP command that sets a device clock to a specified value; or
c) method outside the scope of this standard.

The TCMOS bit in the Control Extension mode page (see 7.5.9) specifies whether the device server allows a
device clock to be initialized by methods outside the scope of this standard. The SCSIP bit in the Control

Working Draft SCSI Primary Commands - 4 (SPC-4) 103

T10/BSR INCITS 513 Revision 37 17 May 2014

Extension mode page (see 7.5.9) specifies whether methods outside the scope of this standard take
precedence over the SET TIMESTAMP command for initializing a device clock.

After a device clock is initialized, the device server shall increment it by one every millisecond, plus or minus a
vendor specific tolerance.

A device clock shall not be affected by an I_T nexus loss or a logical unit reset.

If a device clock is initialized by means other than the SET TIMESTAMP command (see 6.46), the device
server shall establish a unit attention condition for the initiator port associated with every I_T nexus (see
SAM-5), with the additional sense code set to TIMESTAMP CHANGED.

The format of a device clock value is shown in table 56.

Table 56 — Device clock value format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • TIMESTAMP
5 (LSB)

The TIMESTAMP field contains the value of a device clock.

A data structure that contains a device clock value may indicate the most recent event that initialized that
device clock by associating a timestamp origin value (see table 57) with that device clock value.

Table 57 — Timestamp origin value

Code Description
000b Device clock initialized to zero at power on or as the result of a hard reset
001b Reserved
010b Device clock initialized by the SET TIMESTAMP command (see 6.46)
011b Device clock initialized by methods outside the scope of this standard
100b to 111b Reserved

5.3 Device specific background functions

5.3.1 Introduction

Device specific background functions are SCSI target device specific functions that a SCSI target device may
perform that have no specific association with application client initiated operations. A device specific
background function is initiated if:

a) a device specific event associated with the function occurs (e.g., a timer expires or a counter reaches
its limit); and
b) the function is enabled.

104 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If conditions are met to initiate more than one device specific background function (e.g., more than one device
specific event occurs), then the order of performing the functions is device specific. Other device server
processes (e.g., processing a command) may or may not have any impact on events associated with device
specific background functions.

Device specific background functions do not include self-test operations (see 5.14) or background scan
operations (see SBC-3).

Device specific background functions:

a) may include background functions for the informational exceptions that are managed using the
Informational Exceptions Control mode page (see applicable command standard);
b) may include regular, device specific self testing or saving of device specific data;
c) may require the logical unit to be in a different power condition to be performed (e.g., a logical unit
may require being in the active power condition to access the medium for some functions);
d) may be enabled or disabled via the EBF bit in the Informational Exceptions Control mode page;
e) shall be affected by the PERF bit and the LOGERR bit in the Informational Exceptions Control mode
page, if the background function is associated with informational exceptions;
f) should be processed relative to power conditions based on the setting in the PM_BG_PRECEDENCE field
in the Power Condition mode page (see 7.5.13);
g) may have impact on the SCSI target device’s performance (e.g., if a logical unit is performing a
background function, and the device server receives a command from an application client that
requires access to the logical unit, then the logical unit may take a short period of time (e.g., two
seconds) to suspend the background function before the logical unit is able to process the command);
h) shall not affect power condition timers as defined in the Power Condition mode page;
i) shall not affect timers defined in the Background Control mode page (see SBC-3); and
j) shall have no negative impact on the reliability of the logical unit.

5.3.2 Suspending and resuming device specific background functions

The SCSI target device shall suspend a device specific background function in progress if:

a) any of the following are true:

A) a command or task management function is processed that requires the device specific
background function to be suspended; or
B) a SCSI event (e.g., a reset event) (see SAM-5) occurs that requires the device specific
background function to be suspended;
or
b) all of the following are true:
A) a power condition timer defined in the Power Condition mode page (see 7.5.13) expires;
B) the PM_BG_PRECEDENCE field in the Power Condition mode page is set to 10b; and
C) the SCSI target device is unable to continue performing the device specific background function
in the power condition associated with the timer that expired.

The SCSI target device may suspend a device specific background function in progress if:

a) a power condition timer defined in the Power Condition mode page (see 7.5.13) expires;
b) the PM_BG_PRECEDENCE field in the Power Condition mode page is set to 00b; and
c) the SCSI target device is unable to continue performing the device-specific background function in the
power condition associated with the timer that expired.

Working Draft SCSI Primary Commands - 4 (SPC-4) 105

T10/BSR INCITS 513 Revision 37 17 May 2014

If a device specific background function is suspended, the device server shall not stop any process that
causes a device specific background function to be initiated (e.g., not stop any timers or counters associated
with device specific background functions).

A suspended device specific background function may be resumed if:

a) there are no commands in the task set to be processed;

b) there are no task management functions to be processed;
c) there are no SCSI events to be processed;
d) no ACA condition (see SAM-5) exists;
e) the PM_BG_PRECEDENCE field in the Power Condition mode page (see 7.5.13) is set to 00b; or
f) the PM_BG_PRECEDENCE field in the Power Condition mode page is set to 10b, and no power condition
timer defined in the Power Condition mode page has expired.

5.4 Downloading and activating microcode

5.4.1 Downloading microcode

SCSI target device implementations may use microcode (e.g., firmware) that is stored in nonvolatile storage.
Microcode may be changeable by an application client using the WRITE BUFFER command (see 6.49). The
WRITE BUFFER command provides multiple methods for downloading microcode to the SCSI target device
and activating the microcode.

Downloading microcode involves the following steps:

1) Download: the application client transfers complete microcode from the Data-Out buffer to the device
server in one or more WRITE BUFFER commands; and
2) Save: if defined by the download microcode mode, the device server saves the microcode to
nonvolatile storage.

The SCSI target device begins using the new microcode for the first time after it is activated (see 5.4.2) as part
of the response to an event defined by the download microcode mode.

After power on or hard reset, the logical unit shall use the last microcode for that logical unit that was saved to
nonvolatile storage.

106 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 58 defines the WRITE BUFFER download microcode modes with respect to the steps described in this
subclause.

Table 58 — WRITE BUFFER download microcode modes

Down-
Mode load a Save b Activate c
Download microcode and activate (i.e., 04h) yes d no yes
d
Download microcode, save, and activate (i.e., 05h) yes yes optional
e
Download microcode with offsets and activate (i.e., 06h) yes no yes
e
Download microcode with offsets, save, and activate (i.e., 07h) yes yes optional
Download microcode with offsets, save, and defer activate (i.e., 0Eh) f yes e yes no
e
Download microcode with offsets, select activation events, save, and yes yes no
defer activate (i.e., 0Dh) f
Activate deferred microcode (i.e., 0Fh) g no no yes
a
Entries in the Download column are as follows. For modes labeled yes, the application client delivers
microcode in the WRITE BUFFER command(s). For modes labeled no, the application client does not
deliver microcode with the WRITE BUFFER command.
b
Entries in the Save column are as follows. For modes labeled yes, the device server shall save the
microcode to nonvolatile storage for use after each subsequent power on or hard reset, and shall not
return GOOD status for the final command in the WRITE BUFFER sequence (i.e., the series of WRITE
BUFFER commands that downloads the microcode) until the microcode has been saved. For modes
labeled no, the device server shall discard the microcode on the next power on or hard reset.
c
Entries in the Activate column are as follows. For modes labeled yes, the device server shall activate
the microcode (see 5.4.2) after completion of the final command in the WRITE BUFFER sequence (i.e.,
the series of WRITE BUFFER commands that downloads the microcode and activates it). For modes
labeled optional, the device server may or may not activate the microcode image upon completion of
the final command in the WRITE BUFFER sequence. For modes labeled no, the device server shall not
activate the microcode upon completion of the final command in the WRITE BUFFER sequence.
d
The application client delivers microcode in a vendor specific number of WRITE BUFFER commands
(i.e., a WRITE BUFFER sequence). The device server should require that the microcode be delivered in
a single command. The device server shall perform any required verification of the microcode prior to
returning GOOD status for the final WRITE BUFFER command in a sequence (i.e., the WRITE
BUFFER command delivering the last part of the microcode).
e The application client delivers microcode in one or more WRITE BUFFER commands, specifying a
buffer ID and buffer offset in each command. If the device server does not receive the necessary
WRITE BUFFER commands required to deliver the complete microcode before a logical unit reset
occurs, an I_T nexus loss occurs, or a WRITE BUFFER command specifying a different download
microcode mode is processed, then the device server shall discard the new microcode. If the device
server determines that it is processing the final WRITE BUFFER command (i.e., the WRITE BUFFER
command delivering the last part of the microcode), then the device server shall perform any required
verification of the microcode prior to returning GOOD status for the command.
f Microcode downloaded with this mode is defined as deferred microcode.
g
Support for mode 0Fh is mandatory if either mode 0Dh or mode 0Eh is supported.

Working Draft SCSI Primary Commands - 4 (SPC-4) 107

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 59 summarizes how the WRITE BUFFER download microcode modes process the BUFFER ID field, the
BUFFER OFFSETfield, and the PARAMETER LIST LENGTH field in the WRITE BUFFER CDB.

Table 59 — WRITE BUFFER download microcode field processing

BUFFER ID field, BUFFER OFFSET

field, and PARAMETER LIST
Mode LENGTH field processing

Download microcode and activate (i.e., 04h) vendor specific

Download microcode, save, and activate (i.e., 05h) vendor specific
Download microcode with offsets and activate (i.e., 06h) 6.49.6
Download microcode with offsets, save, and activate (i.e., 07h) 6.49.6
Download microcode with offsets, select activation events, save, and 6.49.6 and 6.49.9
defer activate (i.e., 0Dh)
Download microcode with offsets, save, and defer activate (i.e., 0Eh) 6.49.6
Activate deferred microcode (i.e., 0Fh) ignored

If the device server is unable to process a WRITE BUFFER command with a download microcode mode
because of a vendor specific condition (e.g., the device server requires the microcode be delivered in order,
and the BUFFER OFFSET field is not equal to the contents of the previous WRITE BUFFER command’s BUFFER
OFFSET field plus the contents of the previous WRITE BUFFER command’s PARAMETER LIST LENGTH field),
then the device server shall terminate the command with CHECK CONDITION status, with the sense key set
to ILLEGAL REQUEST, and the additional sense code set to COMMAND SEQUENCE ERROR.

If the device server detects a digital signature validation failure while processing a WRITE BUFFER command
that downloads microcode, it shall terminate the command with CHECK CONDITION status, with the sense
key set to ABORTED COMMAND, and the additional sense code set to DIGITAL SIGNATURE VALIDATION
FAILURE.

108 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The MULTI I_T NEXUS MICROCODE DOWNLOAD field (see table 58) in the Extended INQUIRY Data VPD page
(see 7.8.7) indicates how the device server handles concurrent attempts to download microcode using the
WRITE BUFFER command download microcode modes from multiple I_T nexuses.

Table 60 — MULTI I_T NEXUS MICROCODE DOWNLOAD field (part 1 of 2)

Code Description
0h The handling of concurrent WRITE BUFFER download microcode operations from
multiple I_T nexus is vendor specific.
1h For modes that download microcode (see table 58), the device server shall:
a) if a WRITE BUFFER command with the BUFFER OFFSET field set to zero is
received on any I_T nexus, then the command shall be processed as described
elsewhere in this subclause. This shall establish the I_T nexus for the WRITE
BUFFER sequence, and cause any microcode downloaded on another I_T nexus
to be discarded;
b) if a WRITE BUFFER command with the BUFFER OFFSET field set to a non-zero
value is received on the established I_T nexus for the WRITE BUFFER
sequence, then the command shall be processed as described elsewhere in this
subclause; and
c) if a WRITE BUFFER command with the BUFFER OFFSET field set to a non-zero
value is received on an I_T nexus that is different from the established I_T nexus
for the WRITE BUFFER sequence, then the device server shall terminate the
command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to COMMAND SEQUENCE
ERROR. The WRITE BUFFER sequence for the established I_T nexus should
not be affected.
If a WRITE BUFFER command with mode 0Fh (i.e., activate deferred microcode) is
received on an I_T nexus that is different from the established I_T nexus for the WRITE
BUFFER sequence, then the device server shall terminate the WRITE BUFFER
command with mode 0Fh with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to COMMAND SEQUENCE
ERROR. Any deferred microcode shall not be invalidated.
2h For modes that download microcode (see table 58), the device server shall allow con-
current sequences of WRITE BUFFER commands to be processed as described else-
where in this subclause on more than one I_T nexus.
If a WRITE BUFFER command with mode 0Fh (i.e., activate deferred microcode) is
received on an I_T nexus that is different from the established I_T nexus for the WRITE
BUFFER sequence, then the device server shall process the command as described
elsewhere in this subclause.

Working Draft SCSI Primary Commands - 4 (SPC-4) 109

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 60 — MULTI I_T NEXUS MICROCODE DOWNLOAD field (part 2 of 2)

Code Description
3h For modes that download microcode (see table 58), the device server shall:
a) if a WRITE BUFFER command with the BUFFER OFFSET field set to zero is
received on any I_T nexus, then the command shall be processed as described
elsewhere in this subclause. This shall establish the I_T nexus for the WRITE
BUFFER sequence, and cause any microcode downloaded on another I_T nexus
to be discarded;
b) if a WRITE BUFFER command with the BUFFER OFFSET field set to a non-zero
value is received on the established I_T nexus for the WRITE BUFFER
sequence, then the command shall be processed as described elsewhere in this
subclause; and
c) if a WRITE BUFFER command with the BUFFER OFFSET field set to a non-zero
value is received on an I_T nexus that is different from the established I_T nexus
for the WRITE BUFFER sequence, then the device server shall terminate the
command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to COMMAND SEQUENCE
ERROR. The WRITE BUFFER sequence for the established I_T nexus should
not be affected.
If a WRITE BUFFER command with mode 0Fh (i.e., activate deferred microcode) is
received on an I_T nexus that is different from the established I_T nexus for the WRITE
BUFFER sequence, then the device server shall process the command as described
elsewhere in this subclause.
4h to Fh Reserved

For all WRITE BUFFER command modes that download microcode (see table 58), the COMMAND SPECIFIC
field (see 6.35.4.2) located in the command timeouts descriptor of the parameter data returned by the
REPORT SUPPORTED OPERATION CODES command (see 6.35) indicates the maximum time that access
to the SCSI device is limited or not possible through any SCSI ports associated with a logical unit that
processes a WRITE BUFFER command that activates microcode.

5.4.2 Activating microcode

If the SCSI target device contains multiple logical units, the activation of microcode by one logical unit may
change the microcode for other logical units in that SCSI target device.

Activating microcode for a logical unit may result in:

a) a hard reset; or
b) a logical unit reset for each logical unit affected by the microcode download (i.e., logical units that
activated microcode or logical units that processed a logical unit reset due to another logical unit
activated microcode).

If microcode is activated due to processing a WRITE BUFFER command with a mode that requires activation
after processing (i.e., modes 04h (see 6.49.4), 06h (see 6.49.6), and 0Fh (see 6.49.11)), then:

a) if the microcode activation resulted in a hard reset or resulted in a logical unit reset, the device server
shall establish a unit attention condition (see SAM-5) for the initiator port associated with every I_T
nexus affected by the microcode activation except the I_T nexus on which the WRITE BUFFER

110 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

command was received with the additional sense code set to MICROCODE HAS BEEN CHANGED;
or
b) if the microcode activation did not result in a hard reset and did not result in a logical unit reset, the
device server shall establish a unit attention condition for the initiator port associated with every I_T
nexus affected by the microcode activation with the additional sense code set to MICROCODE HAS
BEEN CHANGED WITHOUT RESET.

If microcode is activated due to processing a WRITE BUFFER command with a mode that may cause
activation after processing (i.e., for modes 05h (see 6.49.5) and 07h (see 6.49.7)), then the device server shall
establish a unit attention condition (see SAM-5) based on the setting of the ACTIVATE MICROCODE field in the
Extended INQUIRY VPD page (see 7.8.7).

If microcode is activated as a result of a power on or as a result of a hard reset, the device server may
establish a unit attention condition (see SAM-5) for the initiator port associated with every I_T nexus with the
additional sense code set to MICROCODE HAS BEEN CHANGED in addition to the unit attention condition
for the power on or hard reset.

If deferred microcode (see table 58) is activated due to a command defined by its command standard as
causing deferred microcode to be activated (e.g., the FORMAT UNIT command and the START STOP UNIT
command (see SBC-3)), then the device server:

a) shall establish a unit attention condition (see SAM-5) for the initiator port associated with every I_T
nexus affected by the microcode activation:
A) if the microcode activation resulted in a hard reset or resulted in a logical unit reset, the additional
sense code for the established unit attention shall be set to MICROCODE HAS BEEN
CHANGED; or
B) if the microcode activation did not result in a hard reset and did not result in a logical unit reset,
the additional sense code for the established unit attention shall be set to MICROCODE HAS
BEEN CHANGED WITHOUT RESET;
and
b) may establish other unit attention condition(s) as defined for the command (e.g., CAPACITY DATA
HAS CHANGED for the FORMAT UNIT command).

If new microcode is saved before deferred microcode is activated, then that deferred microcode is not
activated.

5.5 Error history

5.5.1 Error history overview

Error history is data collected by a logical unit to aid in troubleshooting errors.

The READ BUFFER command (see 6.18.7) provides a method for retrieving error history from the logical unit
(see 5.5.2).

The WRITE BUFFER command (see 6.49.12) provides a method for inserting application client error history
into the error history (see 5.5.3) and for clearing the error history (see 5.5.4).

The format of the application client error history is defined by the manufacturer of the application client. The
format of the error history, including how the application client error history, if any, is incorporated into the error
history, is defined by the manufacturer of the logical unit.

Working Draft SCSI Primary Commands - 4 (SPC-4) 111

T10/BSR INCITS 513 Revision 37 17 May 2014

5.5.2 Retrieving error history with the READ BUFFER command

Device servers may allow the error history to be retrieved using a sequence of READ BUFFER commands on
one I_T nexus.

Error history is returned using error history snapshots. An error history snapshot is the contents of the error
history at a specific point in time, created by the device server at vendor specific times or requested by the
application client using the READ BUFFER command with certain buffer IDs.

The I_T nexus being used to retrieve an error history snapshot is called the error history I_T nexus. Only one
I_T nexus at a time is allowed to be the error history I_T nexus, and only the error history I_T nexus is allowed
to retrieve an error history snapshot.

To retrieve the complete error history, an application client uses one I_T nexus to:

1) create an error history snapshot if one does not already exist, establish the I_T nexus as the error
history I_T nexus, and retrieve the error history directory by sending a READ BUFFER command (see
6.18.7.2) with:
A) the MODE field set to 1Ch (i.e., error history);
B) the BUFFER ID field set to one of the following:
a) If the error history I_T nexus is expected to be valid:
A) 00h (i.e., return error history directory); or
B) 01h (i.e., return error history directory and create new snapshot);
b) if the application client has knowledge obtained by means outside the scope of this standard
that the error history I_T nexus is no longer valid:
A) 02h (i.e., return error history directory and establish new error history I_T nexus); or
B) 03h (i.e., return error history directory, establish new error history I_T nexus, and create
new snapshot);
C) the BUFFER OFFSET field set to 000000h; and
D) the ALLOCATION LENGTH field set to at least 2 088 (i.e., large enough to transfer the complete error
history directory);
2) retrieve the error history. The application client uses a Data-In Buffer size that is a multiple of the
offset boundary indicated in the READ BUFFER descriptor (see 6.18.4). For each buffer ID indicated
in the error history directory in the range of 10h to EFh, the application client sends one or more
READ BUFFER commands (see 6.18.7.3) as follows:
1) send the first READ BUFFER command with:
a) the MODE field set to 1Ch (i.e., error history);
b) the BUFFER ID field set to the buffer ID (i.e., an error history data buffer);
c) the BUFFER OFFSET field set to 000000h; and
d) the ALLOCATION LENGTH field set to the size of the Data-In Buffer;
and
2) until the number of bytes returned by the previous READ BUFFER command does not equal the
specified allocation length and/or the total number of bytes returned from the buffer ID equals the
maximum available length indicated in the error history directory, send zero or more additional
READ BUFFER commands with:
a) the MODE field set to 1Ch (i.e., error history);
b) the BUFFER ID field set to the buffer ID (i.e., an error history data buffer);
c) the BUFFER OFFSET field set to the previous buffer offset plus the previous allocation length;
and
d) the ALLOCATION LENGTH field set to the size of the Data-In Buffer;
and
3) clear the error history I_T nexus and, depending on the buffer ID, release the error history snapshot
by sending a READ BUFFER command with:
A) the MODE field set to 1Ch (i.e., error history);

112 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

B) the BUFFER ID field set to:

a) FEh (i.e., clear error history I_T nexus) (see 6.18.7.4); or
b) FFh (i.e., clear error history I_T nexus and release snapshot) (see 6.18.7.5);
C) the BUFFER OFFSET field set to any value allowed by table 234 (see 6.18.7.1) (e.g., 000000h); and
D) the ALLOCATION LENGTH field set to any value allowed for the chosen BUFFER ID field value (see
6.18.7.4 or 6.18.7.5) (e.g., 000000h).

While an error history snapshot exists, the device server:

a) shall not modify the error history snapshot to reflect any changes to the error history;
b) may or may not record events that are detected into the error history; and
c) if the device server supports the WRITE BUFFER command download application client error history
mode (see 6.49.12), shall record the specified application client error history into the error history.

The device server shall clear the established error history I_T nexus and not release the error history
snapshot:

a) upon processing of a READ BUFFER command on the error history I_T nexus with:
A) the MODE field set to 1Ch (i.e., error history); and
B) the BUFFER ID field set to FEh (i.e., clear error history I_T nexus) (see 6.18.7.4);
or
b) if an I_T nexus loss occurs on the error history I_T nexus.

The device server shall clear the established error history I_T nexus and release the error history snapshot:

a) upon processing of a READ BUFFER command using the same I_T nexus that was used to establish
the snapshot with:
A) the MODE field set to 1Ch (i.e., error history); and
B) the BUFFER ID field set to FFh (i.e., clear error history I_T nexus and release snapshot) (see
6.18.7.5);
b) if a power on occurs;
c) if a hard reset occurs; or
d) if a logical unit reset occurs.

The device server shall not replace or release the error history snapshot while the error history I_T nexus is
established.

The device server shall implement a vendor specific timer for error history snapshot retrieval. If the vendor
specific timer expires, then:

a) the device server shall:

A) clear the error history I_T nexus; and
B) establish a unit attention condition for the error history I_T nexus with the additional sense code
set to ERROR HISTORY I_T NEXUS CLEARED;
or
b) the device server shall:
A) clear the error history I_T nexus;
B) release the error history snapshot; and
C) establish a unit attention condition for the error history I_T nexus with the additional sense code
set to ERROR HISTORY SNAPSHOT RELEASED.

After an error history snapshot is released, the device server shall resume recording error history for events
that are detected.

Working Draft SCSI Primary Commands - 4 (SPC-4) 113

T10/BSR INCITS 513 Revision 37 17 May 2014

Error history may also be retrieved by vendor specific methods or other READ BUFFER command sequences
that are outside the scope of this standard.

5.5.3 Adding application client error history with the WRITE BUFFER command

An application client adds application client detected error history to the error history collected by a logical unit
using a WRITE BUFFER command with the MODE field set to 1Ch (see 6.49.12). The application client error
history:

a) may be recovered:
A) as part of the error history (see 5.5.2); or
B) by means outside the scope of this standard;
and
b) is not used for any logical unit related error recovery.

Error history that contains a mix of application client error history and logical unit error history may be used to
correlate an application client-detected error with errors detected internally by the logical unit.

Application clients should minimize the amount of error history they store to prevent error history overflows
(see 6.49.12).

5.5.4 Clearing error history with the WRITE BUFFER command

An application client clears the portions of the error history that the device server allows to be cleared by
sending a WRITE BUFFER command (see 6.49.12) with:

a) the MODE field set to 1Ch (i.e., download error history);

b) the PARAMETER LIST LENGTH field set to 00001Ah;
c) in the parameter list, the CLR bit set to one; and
d) all other fields in the parameter list set as 6.49.12 describes.

Clearing error history shall not:

a) clear the error history I_T nexus, if any; or

b) release the error history snapshot, if any, if it was created with the READ BUFFER command (see
5.5.2).

114 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.6 Identifying information

The REPORT IDENTIFYING INFORMATION command (see 6.32) and SET IDENTIFYING INFORMATION
command (see 6.43) allow an application client to maintain one or more sets of identifying information
associated with the peripheral device.

Identifying information shall persist through power cycles (i.e., be stored in non-volatile storage), hard resets,
logical unit resets, I_T nexus losses, media format operations, and media replacement.

Table 61 defines the identifying information types.

Table 61 — Identifying information types

Identifying information type Length Support a

Peripheral device identifying information: a value describing 0 to 64 bytes Mandatory
the peripheral device (e.g., an operating system volume label)
65 to 512 bytes Optional

Peripheral device text identifying information: a null-termi- 0 to 256 bytes Optional

nated (see 4.3.2) UTF-8 format string providing an informational
description of the peripheral device (e.g., a descriptive string
entered by a system administrator)
a
These support requirements shall apply only if the REPORT IDENTIFYING INFORMATION
command and/or SET IDENTIFYING INFORMATION command are implemented.

Identifying information is changed by:

a) the SET IDENTIFYING INFORMATION command; or

b) a mechanism outside the scope of this standard (e.g., a system administrator may be able to change
identifying information through a management interface).

If a mechanism outside the scope of this standard changes the identifying information, then the device server
shall establish a unit attention condition for the initiator port associated with every I_T nexus with the
additional sense code set to DEVICE IDENTIFIER CHANGED.

5.7 Medium auxiliary memory

Some types of media, especially removable media, include a non-volatile memory referred to as MAM.
Medium auxiliary memory is used to store data describing the media and its contents. This standard supports
medium auxiliary memory with the READ ATTRIBUTE command (see 6.17) and the WRITE ATTRIBUTE
command (see 6.48). These commands are used to retrieve and store information in the medium auxiliary
memory in the form of MAM attributes.

A MAM attribute is represented in a format described in 7.4.

Working Draft SCSI Primary Commands - 4 (SPC-4) 115

T10/BSR INCITS 513 Revision 37 17 May 2014

There are three types of MAM attributes (see table 62).

Table 62 — Types of MAM attributes

Readable Writable
Attribute with READ with WRITE
Type Attribute Source Example ATTRIBUTE ATTRIBUTE
Medium Permanently stored in the medium Media Serial Yes No
auxiliary memory during manufacture. Number
Device Maintained by the device server. Load Count Yes No
Host Maintained by the application client. Backup Date Yes Yes

Depending on the attribute type, MAM attributes have the states shown in table 63.

Table 63 — MAM attribute states

Attribute
Type Attribute State Description
Medium Read Only An application client may read the contents of the MAM attribute with the
or READ ATTRIBUTE command, but an attempt to clear or change the MAM
Device attribute using the WRITE ATTRIBUTE command shall result in the device
server terminating the command with CHECK CONDITION status. If the
READ ONLY bit (see 7.4.1) is set to one, the attribute is in the read only state.

Unsupported The device server does not support the MAM attribute and shall not return
this attribute in response to a READ ATTRIBUTE command.
Unavailable The MAM attribute exists but is not available at this time. The device server
shall not return this attribute in response to a READ ATTRIBUTE command.
Host Nonexistent A host attribute does not exist in the medium auxiliary memory until a
WRITE ATTRIBUTE command creates it.
Read/Write The MAM attribute has been created using the WRITE ATTRIBUTE
command. After the MAM attribute has been created, the contents may be
altered using subsequent WRITE ATTRIBUTE commands. A read/write
MAM attribute may be placed in the nonexistent state using a WRITE
ATTRIBUTE command with the attribute length set to zero. If the READ ONLY
bit (see 7.4.1) is set to zero, the MAM attribute is in the read/write state.
Unsupported The device server does not support the MAM attribute and shall not return
this attribute in response to a READ ATTRIBUTE command.

5.8 Parameter rounding

For certain commands, one or more specified parameters may be constrained to a range of values. Device
servers may choose to implement only selected values from this range. If the device server receives a value
that it does not support, the device server shall:

a) terminate the command (e.g., by returning CHECK CONDITION status with ILLEGAL REQUEST
sense key); or
b) round the value received to a supported value.

116 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If parameter rounding is implemented, a device server that receives a parameter value that is not an exact
supported value shall adjust the value to one that it supports and shall return CHECK CONDITION status, with
the sense key set to RECOVERED ERROR, and the additional sense code set to ROUNDED PARAMETER.
The application client should send an appropriate command to learn what value the device server has
selected.

The device server shall reject unsupported values unless rounding is permitted in the description of the
parameter. When the description of a parameter states that rounding is permitted, the device server should
adjust maximum value fields down to the next lower supported value than the one specified by the application
client. Minimum value fields should be rounded up to the next higher supported value than the one specified
by the application client. In some cases, the type of rounding (i.e., up or down) is described in the definition of
the parameter.

5.9 Parsing variable length parameter lists and parameter data

Parameter lists and parameter data (e.g., diagnostic pages, mode pages, log pages, and VPD pages) often
include length fields indicating the size of the parameter list or parameter data (e.g., the MODE DATA LENGTH
field in the mode parameter header (see 7.5.5)). Parameter lists and parameter data often include descriptor
lists and descriptor length fields containing the length of the descriptors in the descriptor lists (e.g., the
DESIGNATOR LENGTH field in the designation descriptor used in the Device Identification VPD page (see
7.8.6.1)).

An application client or device server shall not assume that any length field contains the value defined in a
SCSI standard.

If a device server receives a parameter list containing a length field (e.g., a PAGE LENGTH field) and containing
more bytes than are defined in the standard to which it was designed (e.g., the device server complies with a
version of a SCSI standard defining that a parameter list has 24 bytes, but receives a parameter list containing
36 bytes), then the device server shall terminate the command with CHECK CONDITION status, with the
sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER
LIST.

For parameter lists containing a descriptor length field and a descriptor list, if a device server receives more
bytes in a descriptor than are defined in the standard to which the device server was designed (e.g., the
device server complies with a version of a SCSI standard defining that a descriptor is 12 bytes, but receives a
parameter list containing a 16 byte form of that descriptor), then the device server shall terminate the
command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID FIELD IN PARAMETER LIST.

An application client should ignore any bytes of parameter data beyond those defined in the standard to which
the application client was designed (e.g., if the application client complies with a version of a SCSI standard
defining 24 bytes of parameter data, but receives 36 bytes of parameter data, then the application client
should ignore the last 12 bytes or the parameter data).

For additional response bytes containing a descriptor length field and a descriptor list, an application client
should ignore any bytes in each descriptor beyond those defined in the standard to which the application client
was designed (e.g., if the application client complies with a version of a SCSI standard defining that a
descriptor has 24 bytes, but receives parameter data containing a descriptor list with a 36 byte form of that
descriptor, then the application client should ignore the last 12 bytes of the descriptor).

Working Draft SCSI Primary Commands - 4 (SPC-4) 117

T10/BSR INCITS 513 Revision 37 17 May 2014

5.10 Pollable condition information

5.10.1 Information that does not represent an exception condition

A device server may have information about a condition that does not represent an exception condition. This
information is not reported with a CHECK CONDITION status. Instead, this information is reported:

a) as sense data format parameter data in response to a REQUEST SENSE command as described in
5.10.2; or
b) as log parameter data as described in 5.10.3.

5.10.2 REQUEST SENSE pollable sense data

5.10.2.1 Making information available for the REQUESE SENSE command

SCSI target devices are required to make specified information used in the parameter data returned by the
REQUEST SENSE command (see 6.39) available whenever that information is applicable. Which sense data
is returned in the REQUEST SENSE parameter data is determined at the time the REQUEST SENSE
command is processed.

Application clients have no way to control which pollable sense data is returned by a REQUEST SENSE
command. Mechanisms that are specialized to a particular function (e.g., log pages, mode pages) should be
used to obtain information about that function.

5.10.2.2 Selecting pollable sense data to return

Conditions that are not related to the availability of pollable sense data (e.g., a pending unit attention
condition) may cause the device server to ignore all available pollable sense data.

If pollable sense data is available to be returned by a REQUEST SENSE command (see 6.39), the choice of
which sense key and additional sense code to return shall be made as follows:

1) sense data with the sense key set to NOT READY and the additional sense code set to:
1) LOGICAL UNIT NOT READY, INITIALIZING COMMAND REQUIRED (see 5.11.7); and
2) any other additional sense code that is associated with pollable sense data when combined with a
sense key set to NOT READY;
and
2) sense data with the sense key set to NO SENSE and the additional sense code set:
1) as defined for the informational exceptions sense data described in the Informational Exceptions
Control mode page (see applicable command standard);
2) to LOGICAL UNIT TRANSITIONING TO ANOTHER POWER CONDITION (see 5.11.8 and
SBC-3);
3) as defined for any power condition related sense data described in 5.11.7; and
4) any other additional sense code that is associated with pollable sense data when combined with a
sense key set to NO SENSE.

5.10.2.3 Returning one or more progress indications

If the sense key is set to NOT READY or NO SENSE in the header of the sense data being returned by a
REQUEST SENSE command (see 6.39) and progress indication information is associated with the pollable

118 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

sense data, if any, in the sense data (see 5.10.2.1), then:

a) if the DESC bit is set to zero in the REQUEST SENSE command, the device server shall set the SKSV
bit in the fixed-format sense data to one only if progress indication information is available for the
additional sense code associated with the ADDITIONAL SENSE CODE field and ADDITIONAL SENSE CODE
QUALIFIER field; or
b) if the DESC bit is set to one in the REQUEST SENSE command, the device server places progress
indications in the sense data as follows:
A) if progress indication information is available for the additional sense code associated with the
ADDITIONAL SENSE CODE field and ADDITIONAL SENSE CODE QUALIFIER field in the sense data header,
then the device server shall include one sense key specific sense data descriptor (see 4.5.2.4)
that contains the available progress indication information; and
B) if progress indication information is available for one or more additional sense codes that are not
associated with the ADDITIONAL SENSE CODE field and ADDITIONAL SENSE CODE QUALIFIER field in the
sense data header, then for each instance of available progress indication information, the device
server should include one another progress indication sense data descriptor (see 4.5.2.6) that
contains the available progress indication information.

5.10.3 Log parameter pollable device condition information

The following background testing functions report their condition information using log page parameters:

a) self-test operations report whether a test is in progress, but not how far it has progressed using the
Self-Test Results log page (see 7.3.17); and
b) direct-access block devices report progress for background pre-scan operations and background
medium scan operations using the Background Scan Results log page (see SBC-3).

5.11 Power management

5.11.1 Power management overview

The Power Condition mode page (see 7.5.13) and Power Consumption mode page (see 7.5.14) allow an
application client to manage the power utilization of a logical unit in a manner that may reduce power
consumption of the SCSI target device.

Power consumption management is described in 5.11.2, including its interactions with power condition
management. Power condition management is described in 5.11.3.

A change in the power consumption setting or power condition of any logical unit in a SCSI target device may
result in a change in the SCSI target device's power utilization. If a SCSI target device contains multiple logical
units, then the SCSI target device’s power utilization may not change until a group of the logical units have
changed their power consumption in the active power condition (see 5.11.2) or changed to a lower power
condition (see 5.11.3). Any grouping or groupings of logical units for power management is outside the scope
of this standard.

5.11.2 Power consumption management

Power consumption management allows control of the maximum power consumption (e.g., see USB-3) of a
logical unit that is in the active power condition (see 5.11.4).

Working Draft SCSI Primary Commands - 4 (SPC-4) 119

T10/BSR INCITS 513 Revision 37 17 May 2014

If power consumption management is supported, the device server shall support:

a) the Power Consumption mode page (see 7.5.14); and

b) the Power Consumption VPD page (see 7.8.11).

The Power Consumption VPD page contains one or more power consumption descriptors that indicate the
maximum power consumption levels supported by the device server using:

a) a power consumption identifier; and

b) information about the maximum power consumption associated with that power consumption
identifier.

An application client may specify use of one of the maximum power consumption levels indicated by the
Power Consumption VPD page by setting the POWER CONSUMPTION IDENTIFIER field in the Power Consumption
mode page to the contents of that POWER CONSUMPTION IDENTIFIER field in the Power Consumption VPD page.
The SCSI target device shall limit the maximum power consumption while the logical unit is in the active
power condition to the value indicated in the power consumption descriptor in the Power Consumption VPD
page that is associated with the POWER CONSUMPTION IDENTIFIER field in the Power Consumption mode page.

Power consumption management shall:

a) be used to limit the maximum power consumption while in the active power condition;
b) not affect the power consumed during a change between power conditions; and
c) not affect the power consumed while in a power condition other than active.

5.11.3 Power conditions management

Fields in the Power Condition mode page (see 7.5.13) by enabling and initializing one or more idle condition
timers and/or standby condition timers.

Command standards may define the following additional power management features:

a) power conditions (e.g., the stopped power condition in SBC-3);

b) changes to the power condition state machine (e.g., the SSU_PC8:Stopped state in SBC-3);
c) commands that manage power conditions (e.g., a START STOP UNIT command in SBC-3 or
MMC-6);
d) changes to commands defined in this standard; or
e) mode pages, log pages, or VPD pages that are associated with managing power conditions.

Transport protocol standards (e.g., SPL-3) may define additional requirements on the states in the power
condition state machine defined in this standard or a command standard.

There shall be no notification to the application client that a logical unit has changed from one power condition
to another. The response to a REQUEST SENSE command (see 6.39) may indicate whether a logical unit is
in a low power condition and which low power condition.

The current power condition of a logical unit may be decreased by:

a) the expiration of a power condition timer;

b) the completion of background functions; or
c) power condition activities described in a command standard.

120 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The current power condition of a logical unit is increased by:

a) the processing of a command that the device server is unable to continue processing while in the
current power condition;
b) the processing of a background function that the device server is unable to process while in the
current power condition; or
c) power condition activities described in a command standard.

If a device server processes a command that the device server is capable of completing while the logical unit
is in a low power condition, then the device server shall not stop any enabled power condition timers,
regardless of which power condition the logical unit was in when the device server began processing the
command.

If a device server processes a command that the device server is not capable of completing while the logical
unit is in a low power condition, then the device server shall stop any running power condition timers. On
completion of the command, the device server shall reinitialize all enabled power condition timers based on
their values in the Power Condition mode page (see 7.5.13) and start the timers, regardless of which power
condition the logical unit was in when the device server began processing the command.

The device server shall process any task management function (see SAM-5), except LOGICAL UNIT RESET,
regardless of current power condition, without changing to a different power condition. The power condition
timers shall not be affected by task management functions, except LOGICAL UNIT RESET.

The device server may change power conditions or power condition timers while processing a LOGICAL UNIT
RESET.

No power condition defined in this standard shall affect the supply of any power required for proper operation
of a service delivery subsystem.

Logical units that contain cache memory shall write all cached data to the medium for the logical unit (e.g., as
a logical unit would do in response to a SYNCHRONIZE CACHE command as described in SBC-3) prior to
entering into any power condition that prevents accessing the media (e.g., before a SCSI target device stops
its spindle motor during a change to the standby power condition).

5.11.4 Active power condition

While in the active power condition:

a) the device server is capable of completing the processing of its supported commands, including those
that require media access, without the logical unit changing power condition;
b) the device server completes processing of a command in the shortest time when compared to the
time required for completion of that command if command processing began while the logical unit was
in any of the idle power conditions or standby power conditions; and
c) the SCSI target device may consume more power than while the logical unit is in any of the idle power
conditions or standby power conditions (e.g., a disk drive's spindle motor may be active).

A logical unit that is in the active power condition may be affected by power consumption management (see
5.11.2).

Working Draft SCSI Primary Commands - 4 (SPC-4) 121

T10/BSR INCITS 513 Revision 37 17 May 2014

5.11.5 Idle power conditions

A device server may support more than one idle power condition (i.e., idle_a, idle_b, and idle_c) to provide
progressively lower power consumption (i.e., the following power consumption relationship: idle_a idle_b
idle_c).

NOTE 7 - The idle_a power condition was referenced as the idle power condition in SPC-3.

While in one of the idle power conditions:

a) the device server is capable of completing the processing of its supported commands, except those
that require the logical unit to be in the active power condition to be capable of completing the
command with GOOD status (e.g., commands that require media access to complete processing);
b) the device server may take longer to complete processing a command than while the logical unit is in
the active power condition (e.g., the device may have to activate some circuitry before completing
processing of a command);
c) the power consumed by the SCSI target device while in an idle power condition should be less than
the power consumed while the logical unit is in the active power condition and may be greater than
the power consumed while the logical unit is in a standby power condition; and
d) the peak power consumption during a change from an idle power condition to the active power
condition shall be no more than the typical peak power consumption in the active power condition.

5.11.6 Standby power conditions

A device server may support more than one standby power condition (i.e., standby_y and standby_z) to
provide progressively lower power consumption (i.e., the following power consumption relationship: standby_y
standby_z).

NOTE 8 - The standby_z power condition was referenced as the standby power condition in SPC-3.

While in one of the standby power conditions:

a) the device server is not capable of completing the processing of commands that require media access
without the logical unit changing to the active power condition. SCSI transport protocol standards may
impose additional requirements on command processing while changing to a higher power condition
(e.g., the response may be CHECK CONDITION status with sense key set to NOT READY and
additional sense bytes set to LOGICAL UNIT NOT READY, NOTIFY (ENABLE SPINUP) REQUIRED
instead of GOOD status (see SPL-3));
b) the device server may take longer to complete processing a command than while the logical unit is in
the active power condition or one of the idle power conditions (e.g., a disk drive's spindle motor may
need to be started);
c) the power consumed by the SCSI target device while in one of the standby power conditions should
be less than the power consumed while the logical unit is in the active power condition or any of the
idle power conditions; and
d) the peak power consumption during a change from a standby power condition to the active power
condition or an idle power condition is not limited by this standard.

122 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.11.7 Power condition pollable sense data

If the logical unit is in any power condition other than active, the following data shall be available for use by the
REQUEST SENSE command while returning pollable sense data (see 5.10.2) and:

a) if the logical unit is in an idle power condition (see 5.11.5), then the sense key shall be set to NO
SENSE and the additional sense code set to one of the following:
A) LOW POWER CONDITION ON if the reason for entry into the idle power condition is unknown;
B) IDLE CONDITION ACTIVATED BY TIMER if the logical unit entered the idle_a power condition
due to the idle_a condition timer (see 5.11.8.4);
C) IDLE CONDITION ACTIVATED BY COMMAND if the logical unit entered the idle_a power
condition due to processing of a command;
D) IDLE_B CONDITION ACTIVATED BY TIMER if the logical unit entered the idle_b power condition
due to the idle_b condition timer (see 5.11.8.4);
E) IDLE_B CONDITION ACTIVATED BY COMMAND if the logical unit entered the idle_b power
condition due to processing of a command;
F) IDLE_C CONDITION ACTIVATED BY TIMER if the logical unit entered the idle_c power condition
due to the idle_c condition timer (see 5.11.8.4); or
G) IDLE_C CONDITION ACTIVATED BY COMMAND if the logical unit entered the idle_c power
condition due to processing of a command;
b) if the logical unit is in a standby power condition (see 5.11.6), then the sense key shall be set to NO
SENSE and the additional sense code set to one of the following:
A) LOW POWER CONDITION ON if the reason for entry into the standby power condition is
unknown;
B) STANDBY_Y CONDITION ACTIVATED BY TIMER if the logical unit entered the standby_y power
condition due to the standby_y condition timer (see 5.11.8.5);
C) STANDBY_Y CONDITION ACTIVATED BY COMMAND if the logical unit entered the standby_y
power condition due to processing of a command;
D) STANDBY CONDITION ACTIVATED BY TIMER if the logical unit entered the standby_z power
condition due to the standby_z condition timer (see 5.11.8.5); or
E) STANDBY CONDITION ACTIVATED BY COMMAND if the logical unit entered the standby_z
power condition due to processing of a command;
or
c) if the logical unit is in the stopped power condition (see SBC-3), then the sense key shall be set to
NOT READY and the additional sense code shall be set to LOGICAL UNIT NOT READY,
INITIALIZING COMMAND REQUIRED.

NOTE 9 - Device servers that conform to SBC-2 may not provide the pollable sense data described in c).

5.11.8 Power condition state machine

5.11.8.1 Power condition state machine overview

The power condition state machine describes the logical unit power states and transitions resulting from
command processing and Power Condition mode page values (see 7.5.13).

Working Draft SCSI Primary Commands - 4 (SPC-4) 123

T10/BSR INCITS 513 Revision 37 17 May 2014

The power condition state machine states are shown in table 64.

Table 64 — Power condition state machine states

State Reference
a
PC0:Powered_On 5.11.8.2
PC1:Active 5.11.8.3
PC2:Idle 5.11.8.4
PC3:Standby 5.11.8.5
PC4:Active_Wait 5.11.8.6
PC5:Wait_Idle 5.11.8.7
PC6:Wait_Standby 5.11.8.8
a
PC0:Powered_On is the initial state.

While in the following power condition state machine states the logical unit may be increasing power usage to
enter a higher power condition:

a) PC4:Active_Wait.

While in the following power condition state machine states the logical unit may be decreasing power usage to
enter a lower power condition:

a) PC5:Wait_Idle; and
b) PC6:Wait_Standby.

The power condition state machine maintains the timers listed in table 65.

Table 65 — Power condition state machine timers

Timer Initial value a Enable bit a, b

idle_a condition IDLE_A CONDITION TIMER field IDLE_A bit
idle_b condition IDLE_B CONDITION TIMER field IDLE_B bit
idle_c condition IDLE_C CONDITION TIMER field IDLE_C bit
standby_y condition STANDBY_Y CONDITION TIMER field STANDBY_Y bit
standby_z condition STANDBY_Z CONDITION TIMER field STANDBY_Z bit
a
These fields and bits are in the Power Condition mode page (see 7.5.13).
b
In a direct-access block device, the enabled state of these bits may be
overridden by a START STOP UNIT command (see SBC-3).

If more than one of the timers listed in table 65 expire at the same time, then only one timer is processed. The
processing priority order shall be as follows:

1) standby_z condition timer;

2) standby_y condition timer;
3) idle_c condition timer;
4) idle_b condition timer; and
5) idle_a condition timer.

124 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The power condition state machine shall start in the PC0:Powered_On state after power on.

Figure 8 describes the power condition state machine.

PC4: PC1:
Active_Wait Active

PC5: PC2:
PC0: Wait_Idle Idle
Powered_On

PC6: PC3:
Wait_Standby Standby

Figure 8 — Power condition state machine

5.11.8.2 PC0:Powered_On state

5.11.8.2.1 PC0:Powered_On state description

The logical unit shall enter this state upon power on.

5.11.8.2.2 Transition PC0:Powered_On to PC4:Active_Wait

This transition shall occur after:

a) the logical unit is ready to begin power on initialization.

The transition shall include a Transitioning From Powered On argument.

5.11.8.3 PC1:Active state

5.11.8.3.1 PC1:Active state description

While in this state, if power on initialization is not complete, then the logical unit shall complete its power on
initialization.

While in this state, if power on initialization is complete, then:

a) the logical unit is in the active power condition (see 5.11.4);

b) each enabled idle condition timer is running; and
c) each enabled standby condition timer is running.

Working Draft SCSI Primary Commands - 4 (SPC-4) 125

T10/BSR INCITS 513 Revision 37 17 May 2014

5.11.8.3.2 Transition PC1:Active to PC5:Wait_Idle

This transition shall occur if:

a) an idle condition timer is enabled; and

b) that idle condition timer has expired.

The transition shall include a:

a) Transitioning To Idle_a argument, if the highest priority timer (see 5.11.8.1) that expired is the idle_a
condition timer;
b) Transitioning To Idle_b argument, if the highest priority timer that expired is the idle_b condition timer;
or
c) Transitioning To Idle_c argument, if the highest priority timer that expired is the idle_c condition timer.

5.11.8.3.3 Transition PC1:Active to PC6:Wait_Standby

This transition shall occur if:

a) a standby condition timer is enabled; and

b) that standby condition timer has expired.

The transition shall include a:

a) Transitioning To Standby_z argument, if the highest priority timer (see 5.11.8.1) that expired is the
standby_z condition timer; or
b) Transitioning To Standby_y argument, if the highest priority timer that expired is the standby_y
condition timer.

5.11.8.4 PC2:Idle state

5.11.8.4.1 PC2:Idle state description

While in this state:

a) the logical unit is in an idle power condition (see 5.11.5);

b) the device server shall provide power condition pollable sense data (see 5.11.7);
c) each enabled idle condition timer that has not expired is running; and
d) each enabled standby condition timer that has not expired is running.

If a lower priority (see 5.11.8.1) idle condition timer is enabled and expires, then that timer is ignored.

5.11.8.4.2 Transition PC2:Idle to PC4:Active_Wait

This transition shall occur if:

a) the device server processes a command that requires the logical unit to be in the PC1:Active state to
continue processing that command.

The transition shall include a:

a) Transitioning From Idle argument; and

b) Transitioning From Idle_c argument, if the current power condition is the idle_c power condition.

126 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.11.8.4.3 Transition PC2:Idle to PC5:Wait_Idle

This transition shall occur if:

a) an idle condition timer is enabled;

b) that idle condition timer has expired; and
c) the priority (see 5.11.8.1) of that idle condition timer is greater than the priority of the idle condition
timer associated with the current idle power condition.

The transition shall include a:

a) Transitioning To Idle_b argument, if the highest priority timer that expired is the idle_b condition timer;
or
b) Transitioning To Idle_c argument, if the highest priority timer that expired is the idle_c condition timer.

5.11.8.4.4 Transition PC2:Idle to PC6:Wait_Standby

This transition shall occur if:

a) a standby condition timer is enabled; and

b) that standby condition timer has expired.

The transition shall include a:

a) Transitioning To Standby_z argument, if the highest priority timer (see 5.11.8.1) that expired is the
standby_z condition timer; or
b) Transitioning To Standby_y argument, if the highest priority timer that expired is the standby_y
condition timer.

5.11.8.5 PC3:Standby state

5.11.8.5.1 PC3:Standby state description

While in this state:

a) the logical unit is in a standby power condition (see 5.11.6);

b) the device server shall provide power condition pollable sense data (see 5.11.7);
c) each enabled idle condition timer that has not expired is running; and
d) each enabled standby condition timer that has not expired is running.

If an idle condition timer or a lower priority (see 5.11.8.1) standby condition timer is enabled and expires, then
that timer is ignored.

5.11.8.5.2 Transition PC3:Standby to PC4:Active_Wait

This transition shall occur if:

a) the device server processes a command that requires the logical unit to be in the PC1:Active state to
continue processing that command.

The transition shall include a Transitioning From Standby argument.

Working Draft SCSI Primary Commands - 4 (SPC-4) 127

T10/BSR INCITS 513 Revision 37 17 May 2014

5.11.8.5.3 Transition PC3:Standby to PC6:Wait_Standby

This transition shall occur if:

a) the standby_z condition timer is enabled;

b) the standby_z condition timer expired; and
c) the current power condition is the standby_y power condition.

The transition shall include a Transitioning To Standby_z argument.

5.11.8.6 PC4:Active_Wait state

5.11.8.6.1 PC4:Active_Wait state description

While in this state:

a) each idle condition timer that is enabled and not expired is running;
b) each standby condition timer that is enabled and not expired is running;
c) the device server shall provide power condition pollable sense data (see 5.11.7) with the sense key
set to NO SENSE and the additional sense code set to LOGICAL UNIT TRANSITIONING TO
ANOTHER POWER CONDITION; and
d) the logical unit is performing the operations required for it to be in the PC1:Active state (e.g., a disk
drive spins up its media).

If this state was entered with a Transitioning From Idle argument, then:

a) the device server is capable of processing and completing the same commands that the device server
is able to process and complete while in the PC2:Idle state;
b) the peak power consumed in this state shall be no more than the typical peak power consumed in the
PC1: Active state; and
c) the device server shall terminate any command that requires the logical unit be in the PC1:Active
state to continue processing, with CHECK CONDITION status, with the sense key set to NOT READY
and the additional sense code set to LOGICAL UNIT IS IN PROCESS OF BECOMING READY if all
of the following are true:
A) this state was entered with a Transitioning From Idle_c argument; and
B) the CCF IDLE field in the Power Condition mode page (see 7.5.13) is set to 10b (i.e., enabled).

If this state was entered with a Transitioning From Standby argument, then:

a) the device server is capable of processing and completing the same commands that the device server
is able to process and complete while in the PC3:Standby state;
b) the peak power consumption in this state is not limited by this standard; and
c) if the CCF STANDBY field in the Power Condition mode page (see 7.5.13) is set to 10b (i.e., enabled),
then the device server shall terminate any command that requires the logical unit be in the PC1:Active
state or PC2:Idle state to continue processing, with CHECK CONDITION status, with the sense key
set to NOT READY and the additional sense code set to LOGICAL UNIT IS IN PROCESS OF
BECOMING READY.

If this state was entered with a Transitioning From Powered On argument, then:

a) the device server is capable of processing and completing the same commands (except a TEST UNIT
READY command) that the device server is able to process and complete while in the PC3:Standby
state; and

128 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

b) the device server shall terminate with CHECK CONDITION status, with the sense key set to NOT
READY and the additional sense code set to LOGICAL UNIT IS IN PROCESS OF BECOMING
READY any of the following commands:
A) any command that requires the logical unit be in the PC1:Active state or PC2:Idle state to
continue processing; and
B) all TEST UNIT READY commands (see 6.47).

If an idle condition timer or a standby condition timer is enabled and expires, then that timer is ignored in this
state.

5.11.8.6.2 Transition PC4:Active_Wait to PC1:Active

This transition shall occur if:

a) the logical unit meets the requirements for being in the PC1:Active state.

5.11.8.7 PC5:Wait_Idle state

5.11.8.7.1 PC5:Wait_Idle state description

While in this state:

a) each idle condition timer that is enabled and not expired is running;
b) each standby condition timer that is enabled and not expired is running;
c) the device server shall provide power condition pollable sense data (see 5.11.7) with the sense key
set to NO SENSE and the additional sense code set to LOGICAL UNIT TRANSITIONING TO
ANOTHER POWER CONDITION;
d) the logical unit is performing the operations required for it to be in the PC2:Idle state (e.g., reducing
power usage); and
e) the device server is capable of processing and completing the same commands, except a START
STOP UNIT command with the IMMED bit set to zero (see SBC-3), that the device server is able to
process and complete in the PC2:Idle state.

If an idle condition timer or a standby condition timer is enabled and expires, then that timer is ignored in this
state.

5.11.8.7.2 Transition PC5:Wait_Idle to PC2:Idle

This transition shall occur if:

a) the logical unit meets the requirements for being in:

A) the idle_a power condition, if this state was entered with a Transitioning To Idle_a argument;
B) the idle_b power condition, if this state was entered with a Transitioning To Idle_b argument; or
C) the idle_c power condition, if this state was entered with a Transitioning To Idle_c argument.

5.11.8.8 PC6:Wait_Standby state

5.11.8.8.1 PC6:Wait_Standby state description

While in this state:

a) each idle condition timer that is enabled and not expired is running;
b) each standby condition timer that is enabled and not expired is running;

Working Draft SCSI Primary Commands - 4 (SPC-4) 129

T10/BSR INCITS 513 Revision 37 17 May 2014

c) the device server shall provide power condition pollable sense data (see 5.11.7) with the sense key
set to NO SENSE and the additional sense code set to LOGICAL UNIT TRANSITIONING TO
ANOTHER POWER CONDITION;
d) the logical unit is performing the operations required for it to be in the PC3:Standby state (e.g.,
reducing power usage); and
e) the device server is capable of processing and completing the same commands, except a START
STOP UNIT command with the IMMED bit set to zero (see SBC-3), that the device server is able to
process and complete in the PC3:Standby state.

If an idle condition timer or a standby condition timer is enabled and expires, then that timer is ignored in the
state.

5.11.8.8.2 Transition PC6:Wait_Standby to PC3:Standby

This transition shall occur if:

a) the logical unit meets the requirements for being in:

A) the standby_y power condition, if this state was entered with a Transitioning To Standby_y
argument; or
B) the standby_z power condition, if this state was entered with a Transitioning To Standby_z
argument.

5.12 Reservations

5.12.1 Persistent Reservations overview

Reservations may be used to allow a device server to process commands from a selected set of I_T nexuses
(i.e., combinations of initiator ports accessing target ports) and reject commands from I_T nexuses outside the
selected set. The device server uniquely identifies I_T nexuses using protocol specific mechanisms.

Application clients may add or remove I_T nexuses from the selected set using reservation commands. If the
application clients do not cooperate in the reservation protocol, data may be unexpectedly modified and
deadlock conditions may occur.

The persistent reservations mechanism allows multiple application clients communicating through multiple I_T
nexuses to preserve reservation operations across SCSI initiator device failures, which usually involve logical
unit resets and involve I_T nexus losses. Persistent reservations persist across recovery actions. Persistent
reservations are not reset by hard reset, logical unit reset, or I_T nexus loss.

The persistent reservation held by a failing I_T nexus may be preempted by another I_T nexus as part of its
recovery process. Persistent reservations shall be retained by the device server until released, preempted, or
cleared by mechanisms defined in this standard. Persistent reservations may be retained if power to the SCSI
target device is removed.

The PERSISTENT RESERVE OUT command and PERSISTENT RESERVE IN command provide the basic
mechanism for dynamic contention resolution in systems with multiple initiator ports accessing a logical unit.

Before a persistent reservation may be established, the application client shall register a reservation key for
each I_T nexus with the device server. Reservation keys allow:

a) authentication of subsequent PERSISTENT RESERVE OUT commands;

130 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

b) identification of other I_T nexuses that are registered;

c) identification of the reservation key(s) that have an associated persistent reservation;
d) preemption of a persistent reservation from a failing or uncooperative I_T nexus; and
e) multiple I_T nexuses to participate in a persistent reservation.

The reservation key provides a method for the application client to associate a protocol-independent identifier
with a registered I_T nexus. The reservation key is used in the PERSISTENT RESERVE IN command to
identify which I_T nexuses are registered and which I_T nexus, if any, holds the persistent reservation. The
reservation key is used in the PERSISTENT RESERVE OUT command to register an I_T nexus, to verify the
I_T nexus being used for the PERSISTENT RESERVE OUT command is registered, and to specify which
registrations or persistent reservation to preempt.

Reservation key values may be used by application clients to identify registered I_T nexuses, using
application specific methods that are outside the scope of this standard. This standard provides the ability to
register no more than one reservation key per I_T nexus. Multiple initiator ports may use the same reservation
key value for a logical unit accessed through the same target ports. An initiator port may use the same
reservation key value for a logical unit accessed through different target ports. The logical unit shall maintain a
separate reservation key for each I_T nexus, regardless of the reservation key’s value.

An application client may register an I_T nexus with multiple logical units in a SCSI target device using any
combination of unique or duplicate reservation keys. These rules provide the ability for an application client to
preempt multiple I_T nexuses with a single PERSISTENT RESERVE OUT command, but they do not provide
the ability for the application client to uniquely identify the I_T nexuses using the PERSISTENT RESERVE
commands.

See table 216 in 6.16.2 for a list of PERSISTENT RESERVE OUT service actions. See table 204 in 6.15.1 for
a list of PERSISTENT RESERVE IN service actions.

The scope (see 6.15.3.2) of a persistent reservation shall be the entire logical unit.

The type (see 6.15.3.3) of a persistent reservation defines the selected set of I_T nexuses for which the
persistent reservation places restrictions on commands.

The details of which commands are allowed under what types of reservations are described in table 66.

In table 66 and table 67 the following keywords are used:

a) allowed: Commands received from I_T nexuses not holding the reservation or from I_T nexuses not
registered if a registrants only or all registrants type persistent reservation is present should complete
normally.
b) conflict: Commands received from I_T nexuses not holding the reservation or from I_T nexuses not
registered if a registrants only or all registrants type persistent reservation is present shall not be
performed and the device server shall complete the command with RESERVATION CONFLICT
status.

Commands from I_T nexuses holding a reservation should complete normally. The behavior of commands
from registered I_T nexuses if a registrants only or all registrants type persistent reservation is present is
defined in table 66 and table 67.

A command shall be checked for reservation conflicts when the device server begins processing of the
command. After that check succeeds, the device server shall not complete the command with RESERVATION
CONFLICT status due to a subsequent reservation.

Working Draft SCSI Primary Commands - 4 (SPC-4) 131

T10/BSR INCITS 513 Revision 37 17 May 2014

The time at which a reservation is established with respect to other commands being managed by the device
server is vendor specific. Successful completion of a reservation command indicates that the new reservation
is established. A reservation may apply to some or all of the commands in the task set before the completion
of the reservation command. The reservation shall apply to all commands received by the device server after
successful completion of the reservation command. Any persistent reserve service action shall be performed
as a single indivisible event.

Multiple persistent reserve service actions may be present in the task set at the same time. The order of
processing of such service actions is defined by the task set management requirements defined in SAM-5, but
each is processed as a single indivisible command without any interleaving of actions that may be required by
other reservation commands.

For each command, this standard or a command standard defines the conditions that result in the command
being completed with RESERVATION CONFLICT. Command standards define the conditions either in the
device model or in the descriptions of each specific command.

Table 66 — SPC-4 commands that are allowed in the presence of various reservations (part 1 of 3)

Addressed logical unit has this type of persistent

reservation held by another I_T nexus

From any I_T From From not registered

nexus registered I_T nexus
I_T nexus
Write Excl (RR all Write Excl Excl Acc-
Command Excl Access types) RR ess – RR

ACCESS CONTROL IN Allowed Allowed Allowed Allowed Allowed

ACCESS CONTROL OUT Allowed Allowed Allowed Allowed Allowed
CHANGE ALIASES Conflict Conflict Allowed Conflict Conflict
COPY OPERATION ABORT Conflict Conflict Allowed Conflict Conflict
EXTENDED COPY(LID4) Conflict Conflict Allowed Conflict Conflict
EXTENDED COPY(LID1) Conflict Conflict Allowed Conflict Conflict
INQUIRY Allowed Allowed Allowed Allowed Allowed
LOG SELECT Conflict Conflict Allowed Conflict Conflict
LOG SENSE Allowed Allowed Allowed Allowed Allowed
MANAGEMENT PROTOCOL IN Allowed Conflict Allowed Allowed Conflict
MANAGEMENT PROTOCOL OUT Conflict Conflict Allowed Conflict Conflict
MODE SELECT(6) / MODE SELECT(10) Conflict Conflict Allowed Conflict Conflict
MODE SENSE(6) / MODE SENSE(10) Allowed b Conflict Allowed Allowed b Conflict
PERSISTENT RESERVE IN Allowed Allowed Allowed Allowed Allowed
Key: Excl=Exclusive, RR=Registrants Only or All Registrants
a
Exceptions to the behavior of the RESERVE and RELEASE commands described in SPC-2 are
defined in 5.12.3.
b
Logical units claiming compliance with SPC-2 or SPC-3 may return RESERVATION CONFLICT status
in this case. Logical units may report whether certain commands are allowed in the ALLOW COMMANDS
field of the parameter data returned by the PERSISTENT RESERVE IN command with REPORT
CAPABILITIES service action (see 6.15.4).

132 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 66 — SPC-4 commands that are allowed in the presence of various reservations (part 2 of 3)

Addressed logical unit has this type of persistent

reservation held by another I_T nexus

From any I_T From From not registered

nexus registered I_T nexus
I_T nexus
Write Excl (RR all Write Excl Excl Acc-
Command Excl Access types) RR ess – RR

PERSISTENT RESERVE OUT see table 67

b
READ ATTRIBUTE Allowed Conflict Allowed Allowed b Conflict
READ BUFFER Allowed b Conflict Allowed Allowed b Conflict
READ MEDIA SERIAL NUMBER Allowed Allowed Allowed Allowed Allowed
RECEIVE CREDENTIAL Conflict Conflict Allowed Conflict Conflict
RECEIVE COPY DATA(LID4) Allowed Allowed Allowed Allowed Allowed
RECEIVE COPY DATA(LID1) Allowed b Allowed b Allowed Allowed b Allowed b
RECEIVE COPY OPERATING Allowed b Allowed b Allowed b Allowed b
Allowed
PARAMETERS
RECEIVE COPY FAILURE Allowed b Allowed b Allowed b Allowed b
Allowed
DETAILS(LID1)
RECEIVE COPY STATUS(LID4) Allowed Allowed Allowed Allowed Allowed
RECEIVE COPY STATUS(LID1) Allowed b Allowed b Allowed Allowed b Allowed b
RECEIVE ROD TOKEN INFORMATION Allowed Allowed Allowed Allowed Allowed
b b
RECEIVE DIAGNOSTIC RESULTS Allowed Conflict Allowed Allowed Conflict
a
RELEASE(6) / RELEASE(10) As defined in SPC-2
REMOVE I_T NEXUS Conflict Conflict Allowed Conflict Conflict
REPORT ALIASES Allowed Allowed Allowed Allowed Allowed
REPORT ALL ROD TOKENS Allowed Allowed Allowed Allowed Allowed
REPORT IDENTIFYING INFORMATION Allowed Allowed Allowed Allowed Allowed
REPORT LUNS Allowed Allowed Allowed Allowed Allowed
REPORT PRIORITY Allowed Allowed Allowed Allowed Allowed
REPORT SUPPORTED OPERATION
Allowed b Allowed b Allowed Allowed b Allowed b
CODES
REPORT SUPPORTED TASK
Allowed b Allowed b Allowed Allowed b Allowed b
MANAGEMENT FUNCTIONS
Key: Excl=Exclusive, RR=Registrants Only or All Registrants
a
Exceptions to the behavior of the RESERVE and RELEASE commands described in SPC-2 are
defined in 5.12.3.
b
Logical units claiming compliance with SPC-2 or SPC-3 may return RESERVATION CONFLICT status
in this case. Logical units may report whether certain commands are allowed in the ALLOW COMMANDS
field of the parameter data returned by the PERSISTENT RESERVE IN command with REPORT
CAPABILITIES service action (see 6.15.4).

Working Draft SCSI Primary Commands - 4 (SPC-4) 133

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 66 — SPC-4 commands that are allowed in the presence of various reservations (part 3 of 3)

Addressed logical unit has this type of persistent

reservation held by another I_T nexus

From any I_T From From not registered

nexus registered I_T nexus
I_T nexus
Write Excl (RR all Write Excl Excl Acc-
Command Excl Access types) RR ess – RR

REPORT TARGET PORT GROUPS Allowed Allowed Allowed Allowed Allowed

REPORT TIMESTAMP Allowed Allowed Allowed Allowed Allowed
REQUEST SENSE Allowed Allowed Allowed Allowed Allowed
a
RESERVE(6) / RESERVE(10) As defined in SPC-2
SECURITY PROTOCOL IN Allowed Conflict Allowed Allowed Conflict
SECURITY PROTOCOL OUT Conflict Conflict Allowed Conflict Conflict
SEND DIAGNOSTIC Conflict Conflict Allowed Conflict Conflict
SET IDENTIFYING INFORMATION Conflict Conflict Allowed Conflict Conflict
SET PRIORITY Conflict Conflict Allowed Conflict Conflict
SET TARGET PORT GROUPS Conflict Conflict Allowed Conflict Conflict
SET TIMESTAMP Conflict Conflict Allowed Conflict Conflict
TEST UNIT READY Allowed b Allowed b Allowed Allowed b Allowed b
WRITE ATTRIBUTE Conflict Conflict Allowed Conflict Conflict
WRITE BUFFER Conflict Conflict Allowed Conflict Conflict
Key: Excl=Exclusive, RR=Registrants Only or All Registrants
a Exceptions to the behavior of the RESERVE and RELEASE commands described in SPC-2 are
defined in 5.12.3.
b
Logical units claiming compliance with SPC-2 or SPC-3 may return RESERVATION CONFLICT status
in this case. Logical units may report whether certain commands are allowed in the ALLOW COMMANDS
field of the parameter data returned by the PERSISTENT RESERVE IN command with REPORT
CAPABILITIES service action (see 6.15.4).

134 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 67 — PERSISTENT RESERVE OUT service actions that are allowed in the presence of
various reservations

Addressed logical unit has a persistent

reservation held by another I_T nexus

Command is from Command is from

a registered a not registered
Service action I_T nexus I_T nexus
CLEAR Allowed Conflict
PREEMPT Allowed Conflict
PREEMPT AND ABORT Allowed Conflict
REGISTER Allowed Allowed
REGISTER AND IGNORE EXISTING KEY Allowed Allowed
REGISTER AND MOVE Conflict Conflict
RELEASE Allowed a Conflict
b
REPLACE LOST RESERVATION Allowed Conflict
RESERVE Conflict Conflict
a The reservation is not released (see 5.12.11.2.2).
b
If the device server has not detected that persistent reservation information has
been lost, then the command shall be processed as shown in this table. If the device
server has detected that persistent reservation information has been lost, then the
command shall be processed as described in 5.12.5.4.

5.12.2 Third party persistent reservations

Except for all registrants type reservations, a reservation holder (see 5.12.10) may move the persistent
reservation to a third party (e.g., a copy manager supporting the EXTENDED COPY command) using the
REGISTER AND MOVE service action (see 5.12.8). A copy manager supporting the EXTENDED COPY
command may be instructed to move the persistent reservation to a specified I_T nexus using the third party
persistent reservations source I_T nexus segment descriptor (see 6.4.6.18).

5.12.3 Exceptions to SPC-2 RESERVE and RELEASE behavior

This subclause defines exceptions to the behavior of the RESERVE command and RELEASE command
defined in SPC-2. The RESERVE command and RELEASE command are obsolete in this standard, except
for the behavior defined in this subclause. Device servers that operate using the exceptions described in this
subclause shall set the CRH bit to one in the parameter data returned by the REPORT CAPABILITIES service
action of the PERSISTENT RESERVE IN command (see 6.15.4).

A RELEASE(6) command or RELEASE(10) command shall complete with GOOD status, but the persistent
reservation shall not be released, if the command is received from:

a) an I_T nexus that is a persistent reservation holder (see 5.12.10); or

b) an I_T nexus that is registered if a registrants only or all registrants type persistent reservation is
present.

Working Draft SCSI Primary Commands - 4 (SPC-4) 135

T10/BSR INCITS 513 Revision 37 17 May 2014

A RESERVE(6) command or RESERVE(10) command shall complete with GOOD status, but no reservation
shall be established and the persistent reservation shall not be changed, if the command is received from:

a) an I_T nexus that is a persistent reservation holder; or

b) an I_T nexus that is registered if a registrants only or all registrants type persistent reservation is
present.

In all other cases, the device server shall process a RESERVE(6) command, RESERVE(10) command,
RELEASE(6) command, or RELEASE(10) command as defined in SPC-2.

5.12.4 Persistent reservations interactions with IKEv2-SCSI SA creation

If a PERSISTENT RESERVE OUT command is received while an IKEv2-SCSI CCS is in progress (see
5.13.4), the device server shall terminate the command with CHECK CONDITION status, with the sense key
NOT READY, and the additional sense code set to LOGICAL UNIT NOT READY, SA CREATION IN
PROGRESS. The sense key specific additional sense data may be set as described in 5.13.5.

5.12.5 Preserving persistent reservations and registrations

5.12.5.1 Requirements for preserving persistent reservations and registrations

The device server shall preserve the following information for each existing registration across any hard reset,
logical unit reset, or I_T nexus loss, and if the persist through power loss capability is enabled (see 5.12.5.2),
across any power cycle:

a) for SCSI transport protocols where initiator port names are required, the initiator port name;
otherwise, the initiator port identifier;
b) reservation key; and
c) indication of the target port to which the registration was applied.

The device server shall preserve the following information about the existing persistent reservation across any
hard reset, logical unit reset, or I_T nexus loss, and if the persist through power loss capability is enabled (see
5.12.5.2), across any power cycle:

a) for SCSI transport protocols where initiator port names are required, the initiator port name;
otherwise, the initiator port identifier;
b) reservation key;
c) scope;
d) type; and
e) indication of the target port through which the reservation was established.

NOTE 10 - The scope of a persistent reservation is always LU_SCOPE (see 6.15.3.2). For an all registrants
type persistent reservation, preserving the scope and type is sufficient.

5.12.5.2 Preserving persistent reservations and registrations through power loss

The application client may request activation of the persist through power loss device server capability to
preserve the persistent reservation and registrations across power cycles by setting the APTPL bit to one in the
PERSISTENT RESERVE OUT parameter data associated with a REGISTER service action, REGISTER AND
IGNORE EXISTING KEY service action, or REGISTER AND MOVE service action.

136 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

After the application client enables the persist through power loss capability the device server shall preserve
the persistent reservation, if any, and all current and future registrations associated with the logical unit to
which the REGISTER service action, the REGISTER AND IGNORE EXISTING KEY service action, or the
REGISTER AND MOVE service action was addressed until an application client disables the persist through
power loss capability. The APTPL value from the most recent successfully completed REGISTER service
action, REGISTER AND IGNORE EXISTING KEY service action, or REGISTER AND MOVE service action
from any application client shall determine the logical unit’s behavior in the event of a power loss.

5.12.5.3 Nonvolatile memory considerations for preserving persistent reservations and registrations

The capability of preserving persistent reservations and registrations across power cycles requires logical
units to use nonvolatile memory within the SCSI device. Any logical unit that supports the persist through
power loss capability of persistent reservation and has nonvolatile memory that is not ready shall allow the
following commands into the task set:

a) INQUIRY;
b) LOG SENSE;
c) READ BUFFER;
d) REPORT LUNS;
e) REPORT TARGET PORT GROUPS;
f) REQUEST SENSE;
g) START STOP UNIT with the START bit set to one and the POWER CONDITION field set to 0h (see
SBC-3); and
h) WRITE BUFFER.

Until nonvolatile memory has become ready after a power cycle, commands other than those listed in this
subclause shall be terminated with CHECK CONDITION status, with the sense key set to NOT READY, and
the additional sense code set as described in table 336 (see 6.47).

5.12.5.4 Loss of persistent reservation information

5.12.5.4.1 Loss of persistent reservation information overview

While the persist through power loss capability is enabled (see 5.12.5.2), the device server may detect a
failure (e.g., a hardware failure in nonvolatile memory) that causes the loss of the preserved persistent
reservation information.

The failure detected by the device server may be:

a) recoverable through the combined actions of the device server and application client (e.g., sufficient
nonvolatile memory is available to recreate the lost persistent reservation and registrations
information) using the processes described in 5.12.5.4.2 (i.e., a recoverable lost persistent
reservation); or
b) unrecoverable, except by operator intervention (i.e., an unrecoverable lost persistent reservation).

5.12.5.4.2 Recoverable loss of persistent reservation information

If the device server detects a recoverable lost persistent reservation, the device server shall establish a
recoverable lost persistent reservation condition. A recoverable lost persistent reservation condition is a
condition in which the device server shall:

a) not terminate a PERSISTENT RESERVE OUT command with the REPLACE LOST RESERVATION
service action with RESERVATION CONFLICT status; and

Working Draft SCSI Primary Commands - 4 (SPC-4) 137

T10/BSR INCITS 513 Revision 37 17 May 2014

b) terminate with CHECK CONDITION status with the sense key set to DATA PROTECT and the
additional sense code set to PERSISTENT RESERVATION INFORMATION LOST all commands
other than:
A) a PERSISTENT RESERVE OUT command with a REPLACE LOST RESERVATION service
action; and
B) those commands listed in 5.12.5.3.

The device server shall clear a recoverable lost persistent reservation condition in response to:

a) the successful processing of a PERSISTENT RESERVE OUT command with the REPLACE LOST
RESERVATION service action (see 5.12.11.3); or
b) the recoverable lost persistent reservation becoming an unrecoverable lost persistent reservation.

The device server shall not clear a recoverable lost persistent reservation condition for any reason other than
the reasons described in this subclause.

5.12.5.4.3 Unrecoverable loss of persistent reservation information overview

If the device server detects an unrecoverable lost persistent reservation, then the device server:

a) should operate as if it has non volatile memory that is not ready (see 5.12.5.3); or
b) may terminate commands other than those commands listed in 5.12.5.3 with CHECK CONDITION
status with the sense key set to HARDWARE ERROR with the additional sense code set to an
appropriate value.

5.12.6 Finding persistent reservations and reservation keys

5.12.6.1 Summary of commands for finding persistent reservations and reservation keys

The application client may obtain information about the persistent reservation and the reservation keys (i.e.,
registrations) that are present within a device server by issuing a PERSISTENT RESERVE IN command with
a READ RESERVATION service action, a READ KEYS service action, or a READ FULL STATUS service
action.

5.12.6.2 Reporting reservation keys

An application client may send a PERSISTENT RESERVE IN command with READ KEYS service action to
determine if any I_T nexuses have been registered with a logical unit through any target port.

In response to a PERSISTENT RESERVE IN with READ KEYS service action the device server shall report
the following:

a) the current PRgeneration value (see 6.15.2); and

b) the reservation key for every I_T nexus that is currently registered regardless of the target port
through which the registration occurred.

The PRgeneration value allows the application client to verify that the configuration of the I_T nexuses
registered with a logical unit has not been modified (i.e., if the PRgeneration value is not changed, the
configuration of the I_T nexus registered with a logical unit has not been modified).

Duplicate reservation keys shall be reported if multiple I_T nexuses are registered using the same reservation
key.

138 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If an application client uses a different reservation key for each I_T nexus, the application client may use the
reservation key to uniquely identify an I_T nexus.

5.12.6.3 Reporting the persistent reservation

An application client may send a PERSISTENT RESERVE IN command with READ RESERVATION service
action to receive the persistent reservation information.

In response to a PERSISTENT RESERVE IN command with READ RESERVATION service action the device
server shall report the following information for the persistent reservation, if any:

a) the current PRgeneration value (see 6.15.2);

b) the registered reservation key, if any, associated with the I_T nexus that holds the persistent
reservation (see 5.12.10). If the persistent reservation is an all registrants type, the registered
reservation key reported shall be zero; and
c) the scope and type of the persistent reservation, if any.

If an application client uses a different reservation key for each I_T nexus, the application client may use the
reservation key to associate the persistent reservation with the I_T nexus that holds the persistent
reservation. This association is done using techniques that are outside the scope of this standard.

5.12.6.4 Reporting full status

An application client may send a PERSISTENT RESERVE IN command with READ FULL STATUS service
action to receive all information about registrations and the persistent reservation, if any.

In response to a PERSISTENT RESERVE IN command with READ FULL STATUS service action the device
server shall report the current PRgeneration value (see 6.15.2) and, for every I_T nexus that is currently
registered, the following information:

a) the registered reservation key;

b) whether the I_T nexus is a persistent reservation holder;
c) if the I_T nexus is a persistent reservation holder, the scope and type of the persistent reservation;
d) the relative target port identifier identifying the target port of the I_T nexus; and
e) a TransportID identifying the initiator port of the I_T nexus.

5.12.7 Registering

To establish a persistent reservation the application client shall first register an I_T nexus with the device
server. An application client registers with a logical unit by issuing a PERSISTENT RESERVE OUT command
with REGISTER service action or REGISTER AND IGNORE EXISTING KEY service action.

If the I_T nexus has an established registration, an application client may remove the reservation key (see
5.12.11.2.3). This is accomplished by issuing a PERSISTENT RESERVE OUT command with a REGISTER
service action or a REGISTER AND IGNORE EXISTING KEY service action as shown in table 68 and table
69, respectively.

If an I_T nexus has not yet established a reservation key or the reservation key and registration have been
removed, then an application client may register that I_T nexus and zero or more specified unregistered I_T
nexuses by issuing a PERSISTENT RESERVE OUT command with REGISTER service action as defined in
table 68.

Working Draft SCSI Primary Commands - 4 (SPC-4) 139

T10/BSR INCITS 513 Revision 37 17 May 2014

If the I_T nexus has an established registration, the application client may change the reservation key by
issuing a PERSISTENT RESERVE OUT command with REGISTER service action as defined in table 68.

Table 68 — Register behaviors for a REGISTER service action

Parameter list fields a

Command SERVICE ACTION

I_T nexus RESERVATION RESERVATION
status KEY KEY SPEC_I_PT Device server action
zero ignore Do nothing except return GOOD status.
Register the I_T nexus on which the com-
zero mand was received with the value specified
received in the SERVICE ACTION RESERVATION KEY field.
on an zero Register the I_T nexus on which the com-
non-zero
unregistered mand was received and each unregistered
I_T nexus one I_T nexus specified in the parameter list with
the value specified in the SERVICE ACTION
RESERVATION KEY field. b

non-zero ignore ignore Return RESERVATION CONFLICT status.

Not equal to
I_T nexus
ignore ignore Return RESERVATION CONFLICT status.
reservation
key
Unregister the I_T nexus on which the
received on zero
zero command was received (see 5.12.11.2.3).
a registered
Equal to one Return CHECK CONDITION status. c
I_T nexus
I_T nexus Change the reservation key of the I_T nexus
reservation on which the command was received to the
key zero
non-zero value specified in the SERVICE ACTION RESER-
VATION KEY field.

one Return CHECK CONDITION status. c

a For requirements regarding the parameter list fields not shown in this table see 6.16.3.
b If any I_T nexus specified in the parameter list is registered, the device server shall terminate the
command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the
additional sense code set to INVALID FIELD IN PARAMETER LIST. Devices compliant with SPC-3
may return an additional sense code set to INVALID FIELD IN CDB.
c
The sense key shall be set to ILLEGAL REQUEST, and the additional sense code shall be set to
INVALID FIELD IN PARAMETER LIST. Devices compliant with SPC-3 may return an additional sense
code set to INVALID FIELD IN CDB.

Alternatively, an application client may establish a reservation key for an I_T nexus without regard for whether
one has previously been established by issuing a PERSISTENT RESERVE OUT command with REGISTER

140 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

AND IGNORE EXISTING KEY service action as defined in table 69.

Table 69 — Register behaviors for a REGISTER AND IGNORE EXISTING KEY service action

Parameter list
fields a
Command
I_T nexus SERVICE ACTION
status RESERVATION KEY Results
zero Do nothing except return GOOD status.
received on an
unregistered Register the I_T nexus on which the command was received
I_T nexus non-zero with the value specified in the SERVICE ACTION RESERVATION
KEY field.

Unregister the I_T nexus on which the command was received

zero
received on a (see 5.12.11.2.3).
registered Change the reservation key of the I_T nexus on which the
I_T nexus non-zero command was received to the value specified in the SERVICE
ACTION RESERVATION KEY field.
a
The RESERVATION KEY field is ignored when processing a REGISTER AND IGNORE EXISTING KEY
service action. For requirements regarding other parameter list fields not shown in this table see
6.16.3.

If a PERSISTENT RESERVE OUT command with a REGISTER service action or a REGISTER AND
IGNORE EXISTING KEY service action is attempted, but there are insufficient device server resources to
complete the operation, then the device server shall terminate the command with CHECK CONDITION status,
with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INSUFFICIENT
REGISTRATION RESOURCES.

In response to a PERSISTENT RESERVE OUT command with a REGISTER service action or a REGISTER
AND IGNORE EXISTING KEY service action the device server shall perform a registration for each specified
I_T nexus by doing the following as an uninterrupted series of actions:

a) process the registration request regardless of any persistent reservations;

b) process the APTPL bit;
c) ignore the contents of the SCOPE and TYPE fields;
d) associate the reservation key specified in the SERVICE ACTION RESERVATION KEY field with the I_T
nexus being registered, where:
A) the I_T nexus(es) being registered are shown in table 70; and
B) regardless of how the I_T nexus initiator port is specified, the association for the initiator port is
based on either the initiator port name on SCSI transport protocols where initiator port names are
required or the initiator port identifier on SCSI transport protocols where initiator port names are
not required;
e) register the reservation key specified in the SERVICE ACTION RESERVATION KEY field without changing
any persistent reservation that may exist; and
f) retain the reservation key specified in the SERVICE ACTION RESERVATION KEY field and associated
information.

Working Draft SCSI Primary Commands - 4 (SPC-4) 141

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 70 — I_T Nexuses being registered

I_T nexus(es) being registered

a
SPEC_I_PT ALL_TG_PT Initiator port Target port
0 0 The port’s names or identifiers to be registered are determined from the I_T
nexus on which the PERSISTENT RESERVE OUT command was received
0 1 The port’s name or identifier to be Register all of the target ports in the
registered is determined from the I_T SCSI target device
nexus on which the PERSISTENT
RESERVE OUT command was
received
1 0 a) The port’s name or identifier to be The port’s name or identifier to be
registered is determined from the registered is determined from the I_T
I_T nexus on which the PERSIS- nexus on which the PERSISTENT
TENT RESERVE OUT command RESERVE OUT command was
was received; and received
b) Specified by each TransportID in
the additional parameter data (see
6.16.3)
1 1 a) The port’s name or identifier to be Register all of the target ports in the
registered is determined from the SCSI target device
I_T nexus on which the PERSIS-
TENT RESERVE OUT command
was received; and
b) Specified by each TransportID in
the additional parameter data
a If the SPEC_I_PT bit is set to one and the service action is REGISTER AND IGNORE EXISTING KEY,
then the device server shall terminate the command with CHECK CONDITION status, with the sense
key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER
LIST.

After the registration request has been processed, the device server shall then allow other PERSISTENT
RESERVE OUT commands from the registered I_T nexus to be processed. The device server shall retain the
reservation key until the key is changed as described in this subclause or removed as described in 5.12.11.

Any PERSISTENT RESERVE OUT command service action received from an unregistered I_T nexus, other
than the REGISTER or the REGISTER AND IGNORE EXISTING KEY service action, shall be completed with
RESERVATION CONFLICT status.

It is not an error for an I_T nexus that is registered to be registered again with the same reservation key or a
new reservation key. A registration shall have no effect on any other registrations (e.g., if more than one I_T
nexus is registered with the same reservation key and one of those I_T nexuses registers again it has no
effect on the other I_T nexus’ registrations). A registration that contains a non-zero value in the SERVICE
ACTION RESERVATION KEY field shall have no effect on any persistent reservations (i.e., the reservation key for
an I_T nexus may be changed without affecting any previously created persistent reservation).

Multiple I_T nexuses may be registered with the same reservation key. An application client may use the
same reservation key for other I_T nexuses and logical units.

142 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.12.8 Registering and moving the reservation

The PERSISTENT RESERVE OUT command REGISTER AND MOVE service action is used to register a
specified I_T nexus (see table 71) and move the reservation to establish that I_T nexus as the reservation
holder.

Table 71 — Register behaviors for a REGISTER AND MOVE service action

Parameter list fields a

Command SERVICE ACTION

I_T nexus RESERVATION RESERVATION
status KEY KEY UNREG Device server action
received on
an unregis-
ignore ignore ignore Return RESERVATION CONFLICT status. d
tered
I_T nexus
Not equal to
I_T nexus
ignore ignore Return RESERVATION CONFLICT status.
reservation
key
zero ignore Return CHECK CONDITION status. b
received on The I_T nexus on which PERSISTENT
the registered RESERVE OUT command was received shall
I_T nexus of zero
remain registered. See this subclause for the
reservation Equal to
registration and the move specifications.
holder I_T nexus
reservation non-zero c The I_T nexus on which PERSISTENT
key RESERVE OUT command was received shall
be unregistered (see 5.12.11.2.3) upon com-
one
pletion of command processing. See this sub-
clause for the registration and the move
specifications.
received on a
registered I_T
nexus that is ignore ignore ignore Return RESERVATION CONFLICT status.
not the reser-
vation holder
a
For requirements regarding other parameter list fields not shown in this table see 6.16.4.
b
The sense key shall be set to ILLEGAL REQUEST, and the additional sense code shall be set to
INVALID FIELD IN PARAMETER LIST. Devices compliant with SPC-3 may return an additional sense
code set to INVALID FIELD IN CDB.
c
The application client and backup application should use the same reservation key.
d Devices compliant with SPC-3 may return CHECK CONDITION status with the sense key set to

ILLEGAL REQUEST and the additional sense code set to INVALID FIELD IN CDB.

If a PERSISTENT RESERVE OUT command with a REGISTER AND MOVE service action is attempted, but
there are insufficient device server resources to complete the operation, then the device server shall terminate
the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the
additional sense code set to INSUFFICIENT REGISTRATION RESOURCES.

Working Draft SCSI Primary Commands - 4 (SPC-4) 143

T10/BSR INCITS 513 Revision 37 17 May 2014

If a PERSISTENT RESERVE OUT command with a REGISTER AND MOVE service action is received and
the established persistent reservation is a Write Exclusive - All Registrants type reservation or Exclusive
Access - All Registrants type reservation, then the device server shall complete the command with
RESERVATION CONFLICT status.

If a PERSISTENT RESERVE OUT command with a REGISTER AND MOVE service action is received and
there is no persistent reservation established, then the device server shall terminate the command with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set
to INVALID FIELD IN CDB.

If a PERSISTENT RESERVE OUT command with a REGISTER AND MOVE service action specifies a
TransportID that is the same as the initiator port of the I_T nexus on which the command received, then the
device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

In response to a PERSISTENT RESERVE OUT command with a REGISTER AND MOVE service action the
device server shall perform a register and move by doing the following as an uninterrupted series of actions:

a) process the APTPL bit;

b) ignore the contents of the SCOPE and TYPE fields;
c) associate the reservation key specified in the SERVICE ACTION RESERVATION KEY field with the I_T
nexus specified as the destination of the register and move, where:
A) the I_T nexus is specified by the TransportID and the RELATIVE TARGET PORT IDENTIFIER field (see
6.16.4); and
B) regardless of the TransportID format used, the association for the initiator port is based on either
the initiator port name on SCSI transport protocols where initiator port names are required or the
initiator port identifier on SCSI transport protocols where initiator port names are not required;
d) register the reservation key specified in the SERVICE ACTION RESERVATION KEY field;
e) retain the reservation key specified in the SERVICE ACTION RESERVATION KEY field and associated
information;
f) release the persistent reservation for the persistent reservation holder (i.e., the I_T nexus on which
the command was received);
g) move the persistent reservation to the specified I_T nexus using the same scope and type as the
persistent reservation released in item f); and
h) if the UNREG bit is set to one, unregister (see 5.12.11.2.3) the I_T nexus on which PERSISTENT
RESERVE OUT command was received.

It is not an error for a REGISTER AND MOVE service action to register an I_T nexus that is already registered
with the same reservation key or a different reservation key.

5.12.9 Reserving

An application client creates a persistent reservation by issuing a PERSISTENT RESERVE OUT command
with RESERVE service action through a registered I_T nexus with the following parameters:

a) RESERVATION KEY set to the value of the reservation key that is registered with the logical unit for the
I_T nexus; and
b) TYPE field and SCOPE field set to the persistent reservation being created.

Only one persistent reservation is allowed at a time per logical unit and that persistent reservation has a scope
of LU_SCOPE.

144 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If the device server receives a PERSISTENT RESERVE OUT command from an I_T nexus other than a
persistent reservation holder (see 5.12.10) that attempts to create a persistent reservation when a persistent
reservation already exists for the logical unit, then the device server shall complete the command with
RESERVATION CONFLICT status.

If a persistent reservation holder attempts to modify the type or scope of an existing persistent reservation, the
device server shall complete the command with RESERVATION CONFLICT status.

If the device server receives a PERSISTENT RESERVE OUT command with RESERVE service action where
the TYPE field and the SCOPE field contain the same values as the existing type and scope from a persistent
reservation holder, then the device server shall not make any change to the existing persistent reservation
and shall complete the command with GOOD status.

See 5.12.1 for information on when a persistent reservation takes effect.

5.12.10 Persistent reservation holder

The persistent reservation holder is determined by the type of the persistent reservation as follows:

a) for a persistent reservation of the type Write Exclusive – All Registrants or Exclusive Access – All
Registrants, the persistent reservation holder is any registered I_T nexus; or
b) for all other persistent reservation types, the persistent reservation holder is the I_T nexus:
A) for which the reservation was established with a PERSISTENT RESERVE OUT command with
the RESERVE service action, the PREEMPT service action, the PREEMPT AND ABORT service
action, or the REPLACE LOST RESERVATION service action; or
B) to which the reservation was moved by a PERSISTENT RESERVE OUT command with
REGISTER AND MOVE service action.

A persistent reservation holder has its reservation key returned in the parameter data from a PERSISTENT
RESERVE IN command with READ RESERVATION service action as follows:

a) for a persistent reservation of the type Write Exclusive – All Registrants or Exclusive Access – All
Registrants, the reservation key shall be set to zero; or
b) for all other persistent reservation types, the reservation key shall be set to the registered reservation
key for the I_T nexus that holds the persistent reservation.

It is not an error for a persistent reservation holder to send a PERSISTENT RESERVE OUT command with
RESERVE service action to the reserved logical unit with TYPE and SCOPE fields that match those of the
persistent reservation (see 5.12.9).

A persistent reservation holder is allowed to release the persistent reservation using the PERSISTENT
RESERVE OUT command with RELEASE service action (see 5.12.11.2.2).

If the registration of the persistent reservation holder is removed (see 5.12.11.2), the reservation shall be
released. If the persistent reservation holder is more than one I_T nexus, the reservation shall not be released
until the registrations for all persistent reservation holder I_T nexuses are removed.

Working Draft SCSI Primary Commands - 4 (SPC-4) 145

T10/BSR INCITS 513 Revision 37 17 May 2014

5.12.11 Releasing persistent reservations and removing registrations

5.12.11.1 Releasing persistent reservations, removing registrations, and lost reservation information

The application client may use PERSISTENT RESERVE OUT command service actions to:

a) release persistent reservations and remove registrations (see 5.12.11.2); and

b) begin the process of recovering from lost reservation information, if any (see 5.12.5.4 and 5.12.11.3).

5.12.11.2 Service actions that release persistent reservations and remove registrations

5.12.11.2.1 Service actions that release persistent reservations and remove registrations overview

An application client may release or preempt the persistent reservation by issuing one of the following
commands through a registered I_T nexus with the RESERVATION KEY field set to the reservation key value that
is registered with the logical unit for that I_T nexus:

a) a PERSISTENT RESERVE OUT command with RELEASE service action from a persistent
reservation holder (see 5.12.11.2.2);
b) a PERSISTENT RESERVE OUT command with PREEMPT service action specifying the reservation
key of the persistent reservation holder or holders (see 5.12.11.2.4);
c) a PERSISTENT RESERVE OUT command with PREEMPT AND ABORT service action specifying
the reservation key of the persistent reservation holder or holders (see 5.12.11.2.6);
d) a PERSISTENT RESERVE OUT command with CLEAR service action (see 5.12.11.2.7); or
e) if the I_T nexus is the persistent reservation holder and the persistent reservation is not an all
registrants type, then a PERSISTENT RESERVE OUT command with REGISTER service action or
REGISTER AND IGNORE EXISTING KEY service action with the SERVICE ACTION RESERVATION KEY
field set to zero (see 5.12.11.2.3).

Table 72 defines processing for a persistent reservation released or preempted by an application client based
on the reservation type.

Table 72 — Processing for a released or preempted persistent reservation

Reservation Type Processing

Write Exclusive – Registrants Only or This persistent reservation shall be released if the persis-
Exclusive Access – Registrants Only tent reservation holder (see 5.12.10) of this reservation
type becomes unregistered.
Write Exclusive – All Registrants or This persistent reservation shall be released if:
Exclusive Access – All Registrants a) the registration for the last registered I_T nexus
is removed; or
b) the type or scope is changed.
Write Exclusive or Exclusive Access This persistent reservation shall be released if the persis-
tent reservation holder (see 5.12.10) of this reservation
type becomes unregistered.

An application client may remove registrations by issuing one of the following commands through a registered
I_T nexus with the RESERVATION KEY field set to the reservation key value that is registered with the logical unit
for that I_T nexus:

a) a PERSISTENT RESERVE OUT command with PREEMPT service action with the SERVICE ACTION
RESERVATION KEY field set to the reservation key (see 5.12.11.2.4) to be removed;

146 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

b) a PERSISTENT RESERVE OUT command with PREEMPT AND ABORT service action with the
SERVICE ACTION RESERVATION KEY field set to the reservation key (see 5.12.11.2.6) to be removed;
c) a PERSISTENT RESERVE OUT command with CLEAR service action (see 5.12.11.2.7); or
d) a PERSISTENT RESERVE OUT command with REGISTER service action or REGISTER AND
IGNORE EXISTING KEY service action with the SERVICE ACTION RESERVATION KEY field set to zero
(see 5.12.11.2.3).

After a reservation key (i.e., registration) has been removed, no information shall be reported for that
unregistered I_T nexus in subsequent READ KEYS service actions until the I_T nexus is registered again
(see 5.12.7).

If the persist through power loss capability is not enabled, loss of power also causes persistent reservations to
be released and registrations to be removed. If the most recent APTPL value received by the device server is
zero (see 6.16.3), the processing of a power on condition:

a) releases all persistent reservations; and

b) removes all registered reservation keys (see 5.12.7).

5.12.11.2.2 Releasing

Only the persistent reservation holder (see 5.12.10) is allowed to release a persistent reservation.

An application client releases the persistent reservation by issuing a PERSISTENT RESERVE OUT
command with RELEASE service action through an I_T nexus that is a persistent reservation holder with the
following parameters:

a) RESERVATION KEY field set to the value of the reservation key that is registered with the logical unit for
the I_T nexus; and
b) TYPE field and SCOPE field set to match the persistent reservation being released.

In response to a persistent reservation release request from the persistent reservation holder the device
server shall perform a release by doing the following as an uninterrupted series of actions:

a) release the persistent reservation;

b) not remove any registration(s);
c) if the NUAR bit (see 7.5.8) is set to zero and the released persistent reservation is either a registrants
only type or an all registrants type persistent reservation, then the device server shall establish a unit
attention condition for the initiator port associated with every registered I_T nexus other than I_T
nexus on which the PERSISTENT RESERVE OUT command with RELEASE service action was
received, with the additional sense code set to RESERVATIONS RELEASED;
d) if the NUAR bit is set to one and the released persistent reservation is either a registrants only type or
an all registrants type persistent reservation, then the device server shall not establish a unit attention
condition; and
e) if the persistent reservation is of any other type, the device server shall not establish a unit attention
condition.

The device server shall not alter the established persistent reservation and shall terminate the command with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set
to INVALID RELEASE OF PERSISTENT RESERVATION, for a PERSISTENT RESERVE OUT command that
specifies the release of a persistent reservation if:

a) the requesting I_T nexus is a persistent reservation holder (see 5.12.10); and
b) the SCOPE and TYPE fields do not match the scope and type of the established persistent reservation.

Working Draft SCSI Primary Commands - 4 (SPC-4) 147

T10/BSR INCITS 513 Revision 37 17 May 2014

If there is no persistent reservation or in response to a persistent reservation release request from a

registered I_T nexus that is not a persistent reservation holder (see 5.12.10), then the device server shall do
the following:

a) not release the persistent reservation, if any;

b) not remove any registrations; and
c) complete the command with GOOD status.

5.12.11.2.3 Unregistering

An application client may remove a registration for an I_T nexus by issuing a PERSISTENT RESERVE OUT
command with REGISTER service action or a REGISTER AND IGNORE EXISTING KEY service action with
the SERVICE ACTION RESERVATION KEY field set to zero through that I_T nexus.

If the I_T nexus is a reservation holder, the persistent reservation is of an all registrants type, and the I_T
nexus is the last remaining registered I_T nexus, then the device server shall also release the persistent
reservation.

If the I_T nexus is the reservation holder and the persistent reservation is of a type other than all registrants,
then the device server shall also release the persistent reservation. If the persistent reservation is a
registrants only type, then the device server shall establish a unit attention condition for the initiator port
associated with every registered I_T nexus except for the I_T nexus on which the PERSISTENT RESERVE
OUT command was received, with the additional sense code set to RESERVATIONS RELEASED.

148 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.12.11.2.4 Preempting

5.12.11.2.4.1 Commands that preempt reservations

A PERSISTENT RESERVE OUT command with PREEMPT service action or PREEMPT AND ABORT
service action is used to:

a) preempt (i.e., replace) the persistent reservation and remove registrations (see 5.12.11.2.4.3); or
b) remove registrations (see 5.12.11.2.5).

Table 73 lists the actions taken by the device server based on the current persistent reservation type and the
SERVICE ACTION RESERVATION KEY field in the PERSISTENT RESERVE OUT command.

Table 73 — Preempting actions

Reservation Service Action

Type Reservation Key Device server action Reference
All Registrants Zero Preempt the persistent reservation and 5.12.11.2.4.3
remove registrations.
Not Zero Remove registrations. 5.12.11.2.5
All other types Zero Terminate the command with CHECK CONDI-
TION status, with the sense key set to ILLE-
GAL REQUEST, and the additional sense code
set to INVALID FIELD IN PARAMETER LIST.
Reservation holder’s Preempt the persistent reservation and 5.12.11.2.4.3
reservation key remove registrations.
Any other, non-zero Remove registrations. 5.12.11.2.5
reservation key

See figure 9 for a description of how a device server interprets a PREEMPT service action to determine its
actions (e.g., preempt the persistent reservation, remove registration, or both preempt the persistent
reservation and remove registration).

Working Draft SCSI Primary Commands - 4 (SPC-4) 149

T10/BSR INCITS 513 Revision 37 17 May 2014

PREEMPT service action

Requesting No RESERVATION
I_T nexus CONFLICT Done
registered? status

Yes

Valid
RESERVATION No
KEY & SERVICE ACTION
RESERVATION
a) Remove all other registrations
KEY?
Remove registrations b) Release persistent reservation
Yes pointed to by the SERVICE c) Create persistent reservation
ACTION RESERVATION KEY
using new type and scope
Existing No
persistent
reservation?
Yes

Yes SERVICE ACTION No

RESERVATION KEY
All is zero?
Registrants Yes
persistent
reservation?

No SERVICE ACTION No
RESERVATION KEY
is zero?
SERVICE ACTION
RESERVATION KEY No Yes
matches reservation key
of the persistent reser- ILLEGAL
vation holder? REQUEST
sense key
Yes
a) Remove registrations pointed to by Remove registrations
the SERVICE ACTION RESERVATION KEY pointed to by the SERVICE
b) Release persistent reservation ACTION RESERVATION KEY
c) Create persistent reservation using
new type and scope
Done Done

Done

Figure 9 — Device server interpretation of PREEMPT service action

150 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.12.11.2.4.2 Failed persistent reservation preempt

If the preempting I_T nexus’ PREEMPT service action or PREEMPT AND ABORT service action fails (e.g.,
repeated TASK SET FULL status, repeated BUSY status, SCSI transport protocol time-out, or time-out due to
the task set being blocked due to failed initiator port or failed SCSI initiator device), then the application client
may send a LOGICAL UNIT RESET task management function to the failing logical unit to remove blocking
commands and then resend the preempting service action.

5.12.11.2.4.3 Preempting persistent reservations and registration handling

An application client may preempt the persistent reservation with another persistent reservation by issuing a
PERSISTENT RESERVE OUT command with PREEMPT service action or PREEMPT AND ABORT service
action through a registered I_T nexus with the following parameters:

a) RESERVATION KEY field set to the value of the reservation key that is registered with the logical unit for
the I_T nexus;
b) SERVICE ACTION RESERVATION KEY field set to the value of the reservation key of the persistent
reservation to be preempted; and
c) TYPE field and SCOPE field set to define a new persistent reservation. The SCOPE and TYPE of the
persistent reservation created by the preempting I_T nexus may be different than those of the
persistent reservation being preempted.

If the SERVICE ACTION RESERVATION KEY field identifies a persistent reservation holder (see 5.12.10), the device
server shall perform a preempt by doing the following as an uninterrupted series of actions:

a) release the persistent reservation for the holder identified by the SERVICE ACTION RESERVATION KEY
field;
b) remove the registrations for all I_T nexuses identified by the SERVICE ACTION RESERVATION KEY field,
except the I_T nexus that is being used for the PERSISTENT RESERVE OUT command. If an all
registrants persistent reservation is present and the SERVICE ACTION RESERVATION KEY field is set to
zero, then all registrations shall be removed except for that of the I_T nexus that is being used for the
PERSISTENT RESERVE OUT command;
c) establish a persistent reservation for the preempting I_T nexus using the contents of the SCOPE and
TYPE fields;
d) process commands as defined in 5.12.1;
e) establish a unit attention condition for the initiator port associated with every I_T nexus that lost its
persistent reservation and/or registration, with the additional sense code set to REGISTRATIONS
PREEMPTED; and
f) if the type or scope has changed, then for every I_T nexus whose reservation key was not removed,
except for the I_T nexus on which the PERSISTENT RESERVE OUT command was received, the
device server shall establish a unit attention condition for the initiator port associated with that I_T
nexus, with the additional sense code set to RESERVATIONS RELEASED. If the type or scope have
not changed, then no unit attention condition(s) shall be established for this reason.

After the PERSISTENT RESERVE OUT command has been completed with GOOD status, new commands
are subject to the persistent reservation restrictions established by the preempting I_T nexus.

Working Draft SCSI Primary Commands - 4 (SPC-4) 151

T10/BSR INCITS 513 Revision 37 17 May 2014

The following commands shall be affected in a vendor specific manner either by the restrictions established by
the persistent reservation being preempted or by the restrictions established by the preempting I_T nexus:

a) a command received after the arrival, but before the completion of the PERSISTENT RESERVE OUT
command with the PREEMPT service action or the PREEMPT AND ABORT service action; or
b) a command in the dormant command state, blocked command state, or enabled command state (see
SAM-5) at the time the PERSISTENT RESERVE OUT command with the PREEMPT service action or
the PREEMPT AND ABORT service action is received.

Completion status shall be returned for each command unless it was aborted by a PERSISTENT RESERVE
OUT command with the PREEMPT AND ABORT service action and TAS bit set to zero in the Control mode
page (see 7.5.8).

If an all registrants persistent reservation is not present, it is not an error for the persistent reservation holder
to preempt itself (i.e., a PERSISTENT RESERVE OUT with a PREEMPT service action or a PREEMPT AND
ABORT service action with the SERVICE ACTION RESERVATION KEY value equal to the persistent reservation
holder’s reservation key that is received from the persistent reservation holder). In that case, the device server
shall establish the new persistent reservation and maintain the registration.

5.12.11.2.5 Removing registrations

If a registered reservation key does not identify a persistent reservation holder (see 5.12.10), an application
client may remove the registration(s) without affecting any persistent reservations by issuing a PERSISTENT
RESERVE OUT command with PREEMPT service action through a registered I_T nexus with the following
parameters:

a) RESERVATION KEY field set to the value of the reservation key that is registered for the I_T nexus; and
b) SERVICE ACTION RESERVATION KEY field set to match the reservation key of the registration or
registrations being removed.

If the SERVICE ACTION RESERVATION KEY field does not identify a persistent reservation holder or there is no
persistent reservation holder (i.e., there is no persistent reservation), then the device server shall perform a
preempt by doing the following in an uninterrupted series of actions:

a) remove the registrations for all I_T nexuses specified by the SERVICE ACTION RESERVATION KEY field;
b) ignore the contents of the SCOPE and TYPE fields;
c) process commands as defined in 5.12.1; and
d) establish a unit attention condition for the initiator port associated with every I_T nexus that lost its
registration other than the I_T nexus on which the PERSISTENT RESERVE OUT command was
received, with the additional sense code set to REGISTRATIONS PREEMPTED.

If a PERSISTENT RESERVE OUT with a PREEMPT service action or a PREEMPT AND ABORT service
action sets the SERVICE ACTION RESERVATION KEY field to a value that does not match any registered
reservation key, then the device server shall complete the command with RESERVATION CONFLICT status.

It is not an error for a PERSISTENT RESERVE OUT with a PREEMPT service action or a PREEMPT AND
ABORT service action to set the RESERVATION KEY and the SERVICE ACTION RESERVATION KEY to the same
value. However, no unit attention condition is established for the I_T nexus on which the PERSISTENT
RESERVE OUT command was received. The registration is removed.

152 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.12.11.2.6 Preempting and aborting

The application client’s request for and the device server’s responses to a PERSISTENT RESERVE OUT
command with PREEMPT AND ABORT service action are identical to the responses to a PREEMPT service
action (see 5.12.11.2.4) except for the additions described in this subclause. If no reservation conflict
occurred, the device server shall perform the following uninterrupted series of actions:

a) if the persistent reservation is not an all registrants type then:

A) if the TST field is set to 000b (see 7.5.8) and the faulted I_T nexus, if any, is not the I_T nexus
associated with the persistent reservation or registration being preempted, then the task set ACA
condition shall be processed as defined in SAM-5;
B) if the TST field is set to 000b and the faulted I_T nexus, if any, is the I_T nexus associated with the
persistent reservation or registration being preempted, then the PERSISTENT RESERVE OUT
command shall be processed without regard for the task set ACA condition; or
C) if the TST field is set to 001b, then the ACA condition shall be processed as defined in SAM-5;
b) perform the uninterrupted series of actions described for the PREEMPT service action (see
5.12.11.2.4);
c) all commands from the I_T nexus(es) associated with the persistent reservations or registrations
being preempted (i.e., preempted commands) except the PERSISTENT RESERVE OUT command
itself shall be aborted as defined in SAM-5;
d) for each copy operation (see 5.16.4.3) being processed:
A) the third-party copy command (see 5.16.3), if any, that is associated with that copy operation shall
be aborted as described in c); and
B) that copy operation shall be processed as a background copy operation and aborted as if a COPY
OPERATION ABORT command (see 6.3) has been received;
e) after the PERSISTENT RESERVE OUT command with PREEMPT AND ABORT service action has
completed, all new commands are subject to the persistent reservation restrictions established by the
preempting I_T nexus;
f) if the persistent reservation is not an all registrants type, then the device server shall clear any ACA
condition associated with an I_T nexus being preempted and shall abort any commands with an ACA
attribute received on that I_T nexus;
g) if the persistent reservation is an all registrants type, then:
A) if the service action reservation key is set to zero, the device server shall clear any ACA condition
and shall abort any commands with an ACA attribute; or
B) if the service action reservation key is not set to zero, the device server shall do the following for
any I_T nexus registered using the specified reservation key:
a) clear any ACA condition; and
b) abort any commands with an ACA attribute;
and
h) for logical units that implement the PREVENT ALLOW MEDIUM REMOVAL command (see SBC-3,
SSC-4, and SMC-3), the device server shall perform an action equivalent to the processing of a
PREVENT ALLOW MEDIUM REMOVAL command with the PREVENT field equal to zero received on
the I_T nexuses associated with the persistent reservation being preempted.

The actions described in this subclause shall be performed for all I_T nexuses that are registered with the
non-zero SERVICE ACTION RESERVATION KEY value, without regard for whether the preempted I_T nexuses hold
the persistent reservation. If the SERVICE ACTION RESERVATION KEY field is set to zero and an all registrants
persistent reservation is present, the device server shall abort all commands for all registered I_T nexuses.

Working Draft SCSI Primary Commands - 4 (SPC-4) 153

T10/BSR INCITS 513 Revision 37 17 May 2014

5.12.11.2.7 Clearing

Any application client may release the persistent reservation and remove all registrations from a device server
by issuing a PERSISTENT RESERVE OUT command with CLEAR service action through a registered I_T
nexus with the following parameter:

a) RESERVATION KEY field set to the value of the reservation key that is registered with the logical unit for
the I_T nexus.

In response to this request the device server shall perform a clear by doing the following as part of an
uninterrupted series of actions:

a) release the persistent reservation, if any;

b) remove all registration(s);
c) ignore the contents of the SCOPE and TYPE fields;
d) for logical units that implement the PREVENT ALLOW MEDIUM REMOVAL command (see SBC-3,
SSC-4, and SMC-3), the device server shall perform an action equivalent to the processing of a
PREVENT ALLOW MEDIUM REMOVAL command with the PREVENT field equal to zero received on
the I_T nexuses associated with the persistent reservation being cleared;
e) continue normal processing of any commands from any I_T nexus that have been accepted by the
device server as allowed (i.e., nonconflicting); and
f) establish a unit attention condition for the initiator port associated with every registered I_T nexus
other than the I_T nexus on which the PERSISTENT RESERVE OUT command with CLEAR service
action was received, with the additional sense code set to RESERVATIONS PREEMPTED.

NOTE 11 - Application clients should not use the CLEAR service action except during recovery operations
that are associated with a specific initiator port, since the effect of the CLEAR service action defeats the
persistent reservations features that protect data integrity.

5.12.11.3 Replacing lost reservations

A PERSISTENT RESERVE OUT command with the REPLACE LOST RESERVATION service action is used
to:

a) begin a recovery process for the lost persistent reservation that is managed by application clients; and
b) cause the device server to stop terminating commands due to a lost persistent reservation (see
5.12.5.4).

If the device server has not detected that persistent reservation information has been lost (see 5.12.5.4), then
the device server shall terminate a PERSISTENT RESERVE OUT command with the REPLACE LOST
RESERVATION service action with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID RELEASE OF PERSISTENT RESERVATION.

An application client may replace lost reservation information by issuing a PERSISTENT RESERVE OUT
command with the REPLACE LOST RESERVATION service action with the following parameters:

a) RESERVATION KEY field set to zero;

b) SERVICE ACTION RESERVATION KEY field set to the value of the new reservation key (i.e., the value used
to replace the lost reservation key value); and
c) TYPE field and SCOPE field set to define a new persistent reservation. The scope and type of the new
persistent reservation may be different than those of the lost persistent reservation.

154 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

To process a valid PERSISTENT RESERVE OUT command with the REPLACE LOST RESERVATION
service action the device server shall perform the following as an uninterrupted series of actions:

a) remove the prior registrations for all I_T nexuses, if any, without establishing unit attention conditions;
b) establish a registration for the I_T nexus that is being used for the PERSISTENT RESERVE OUT
command using the service action reservation key;
c) release any persistent reservations known to the device server;
d) establish a new persistent reservation for the I_T nexus that is being used for the PERSISTENT
RESERVE OUT command using the contents of the SCOPE and TYPE fields;
e) set the PRgeneration value to zero; and
f) stop terminating commands due to a lost persistent reservation (see 5.12.5.4).

After the PERSISTENT RESERVE OUT command with the REPLACE LOST RESERVATION service action
has been completed with GOOD status:

a) new commands are subject to the new persistent reservation restrictions established by the
command; and
b) until the APTPL bit is set to one in a PERSISTENT RESERVE OUT command with a REGISTER
service action or a REGISTER AND IGNORE EXISTING KEY service action that completes with
GOOD status, the persist through power loss capability is not enabled (see 5.12.5.2).

5.13 Security features

5.13.1 Security goals and threat model

5.13.1.1 Introduction

In many cases, the security goals and threat model used for the Internet are applicable to SCSI commands.
The Internet security goals and threat model found in RFC 3552 as they apply to SCSI are summarized in
5.13.1. Terms, concepts, and classes of security techniques that are defined in RFC 3552 are discussed
based on their RFC 3552 definitions without modification in this standard.

The security goals and threat model described in 5.13.1 are valid for all SCSI device types. Command
standards may modify this model to handle threats appropriate to specific device types.

5.13.1.2 Security goals

The overall goals of security may be divided into the following categories:

a) communications security (i.e., protecting communications); and

b) system security (e.g., protecting systems from unauthorized usage, inappropriate usage, and denial
of service).

These goals interact as a result of communications being carried out by systems, with access to those
systems provided through communications channels. A common methodology is to secure the
communications first and then provide secure access to systems over the secured communication channels.

Communication security is subdivided into the following primary areas of protection:

a) confidentiality: preventing unintended entities from seeing the data;

Working Draft SCSI Primary Commands - 4 (SPC-4) 155

T10/BSR INCITS 513 Revision 37 17 May 2014

b) cryptographic data integrity: ensuring that the data that arrives is identical to the data that was sent;
and
c) peer entity authentication: ensuring that the communicating endpoints are the intended peer
entities.

Data origin authentication (i.e., ensuring that the received data was sent by the authenticated peer) is the
combination of peer entity authentication and cryptographic data integrity.

Non Repudiation enhances data origin authentication with the ability to prove to a third party that the sender
sent the data that the receiver received.

Cryptographic data integrity is called data integrity in RFC 3552. The term cryptographic is added in this
standard to distinguish the class of integrity protection required to counter malicious attacks from the class of
integrity protection required to deal with random data corruption (e.g., caused by cosmic rays or electrical
noise). Mechanisms used to deal with random data corruption (e.g., parity bits and CRCs) have minimal value
against malicious attacks that are able to modify integrity checks to conceal their modifications to the data.
Cryptographic data integrity requires knowledge of a secret key in order to modify an integrity check without
that modification being detectable. Systems should provide a high level of assurance that an attacker is
unable to learn, guess, discover, or otherwise obtain the required secret key.

In addition to the primary areas, there is another area of control:

a) authorization: controlling what an entity is allowed to do. For communications security this is control
of the entities with which an entity is allowed to communicate.

A form of authorization is access control (i.e., controlling what an entity is allowed to access).

5.13.1.3 Threat model

Most secured systems are vulnerable to an attacker equipped with sufficient resources, time, and skills. In
order to make designing a security system practical, a threat model is defined to describe the capabilities that
an attacker is assumed to be able to deploy (e.g., knowledge, computing capability, and ability to control the
system).

The main purposes of a threat model are as follows:

a) to identify the threats of concern; and

b) to rule some threats explicitly out of scope.

Most security measures do not provide absolute assurance that an attack has not occurred. Rather, security
measures raise the difficulty of accomplishing the attack to beyond the attacker's assumed capabilities and/or
resources. Design of security measures that resist attackers with essentially unlimited capabilities (e.g.,
certain nation-states) is outside the scope of this standard. Security measures that are susceptible to a level of
capability available to some attackers may still be useful for deterring attackers who lack that level of
capability, especially when combined with non-technical security measures such as physical access controls.

The computational capability of an attacker is treated as a variable because that capability is inherently a
moving target as a result of more powerful processors. The computational capability of an attacker influences
design aspects (e.g., key length). Well designed security systems are agile in that they are able to operate not
only with different key lengths, but also with different cryptographic algorithms.

156 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The Internet threat model described in RFC 3552 is generally applicable to SCSI, and is specifically applicable
if Internet Protocols are used by the SCSI transport (e.g., iSCSI, Fibre Channel via FCIP, or Fibre Channel via
iFCP). The basic assumptions of the Internet threat model are:

a) end systems engaging in communication are not under the control of the attacker; and
b) the attacker is able to read any communicated data (e.g., data in an IU) and undetectably remove,
change, or inject forged IUs, including injection of IUs that appear to be from a known and/or trusted
system.

Communications security designs are based on an additional assumption that secrets (e.g., keys) used to
secure the communications are protected so that an attacker is unable to learn, guess, discover, or otherwise
obtain them. A consequence of this assumption is that attacks against secured communications are assumed
to begin without with advance knowledge of the secrets used to secure the communications.

5.13.1.4 Types of attacks

The following types of attacks are considered:

a) passive attacks (i.e., attacks that only require reading IUs); and
b) active attacks (i.e., attacks that require the attacker to change communication and/or engage in
communication).

More information on attack types is available in RFC 3552.

Simple passive attacks involve reading communicated data that the attacker was not intended to see (e.g.,
password, credit card number). More complex passive attacks involve post-processing the communicated
data (e.g., checking a challenge-response pair against a dictionary to see if a common word was used as a
password).

There are a wide variety of active attacks (e.g., spoofing, replay, insertion, deletion, known plaintext, and
modification of communications). Man-in-the-middle attacks are a class of active attacks that involve the
attacker inserting itself in the middle of communication, enabling it to intercept all communications without the
knowledge of the communicating parties for various purposes (e.g., insertion, deletion, replay, modification
and/or inspection via decryption of the communications).

5.13.1.5 SCSI security considerations

The application of communication security techniques (see RFC 3552) is defined by command standards.
This subclause describes specific design considerations in applying the threat model (see 5.13.1.3) to all
SCSI device types.

SCSI environments tend not to be fully connected (i.e., there are restrictions on the SCSI device servers with
which a SCSI application client is able to communicate) due to the following mechanisms:

a) physical and logical connectivity restrictions (e.g., in SCSI to SCSI gateways across different
transports);
b) LUN mapping and masking; and
c) transport zoning.

The resulting connectivity is more limited than the Internet security assumption that an off-path attacker is able
to transmit to an arbitrary victim (see RFC 3552).

SCSI security designs are also influenced by SCSI being a client-server distributed service model (see
SAM-5) that is realized over a number of different SCSI transport protocols and interconnects.

Working Draft SCSI Primary Commands - 4 (SPC-4) 157

T10/BSR INCITS 513 Revision 37 17 May 2014

Security functionality may be defined as part of a command set or at the SCSI transport level. Some SCSI
transport protocols (e.g., Fibre Channel and iSCSI) define security functionality that provides confidentiality,
cryptographic integrity, and peer entity authentication for all communicated data. However, there are situations
in which some or all of those mechanisms are not used and there are SCSI communications whose scope
spans more than one SCSI transport protocol (e.g., via a gateway between iSCSI and FCP). Security that is
defined by a command set is appropriate for such situations.

5.13.2 Security associations

5.13.2.1 Principles of SAs

Before an application client and device server begin applying security functions (e.g., data integrity checking,
data encryption) to messages (i.e., data that is transferred in either direction between them), they perform a
security protocol to create at least one SA (see 5.13.2.3). The result of the SA creation protocol is two sets of
SA parameters (see 5.13.2.2), one that is maintained by the application client and one that is maintained by
the device server.

In this model, SAs decouple the process of creating a security relationship from its usage in processing
security functions. This decoupling allows either the creation or the usage of an SA to be upgraded in
response to changing security threats without requiring both processes to be upgraded simultaneously.

Figure 10 shows the relationship between application clients and device servers with respect to SAs.

Application Client Device Server

SA Parameters SA Parameters
Table Table
DS_SAI 
One Set of SA
Parameters
AC_SAI  SA
One Set of SA On e
Parameters

Figure 10 — SA relationships

In both the application client and the device server, the SA parameters are modeled as being stored in an
indexed array and the SAI (i.e., the AC_SAI or the DS_SAI in figure 10) identifies one set of SA parameters
within that array. The application client and device server are not required to store the parameters for any
given SA in the same array locations. In order to support this implementation flexibility, a single SA is modeled
as having two different SAI values (i.e., one for the application client and one for the device server).

The device server shall maintain a single SA parameters table for all I_T nexuses.

SAs shall not be preserved across a power cycle, hard reset, or logical unit reset. SAs shall not be affected by
an I_T nexus loss.

158 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.13.2.2 SA parameters

Each SAI shall identify at least the SA parameters defined in table 74. Individual security protocols define how
the SA parameters are generated and/or used by that security protocol.

Table 74 — Minimum SA parameters (part 1 of 3)

Size (bytes) a

Name Description Min. Max. Scope b

SA parameters that identify and manage the SA.
The SAI used by the application client to identify the
AC_SAI 4 4 Public
SA. c
DS_SAI The SAI used by the device server to identify the SA. c 4 4 Public
The number of seconds that may elapse after the com-
pletion of an SA access operation (i.e., SA creation or
SA usage by a command) before the device server
should discard the state associated with this SA (e.g.,
TIMEOUT the SA parameters). If SA state is discarded because no 4 4 Public
SA access operations are received during the specified
interval, then the device server shall respond to further
attempts to access the SA as if the SA had never been
created. This parameter shall not be set to zero.
SA parameters that are incorporated in messages to prevent message replay attacks.
A sequence number that is incremented for each
response message received by an application client on
AC_SQN 8 8 Public
which a security function is performed and used to
detect replay attacks (see 5.13.1.4).
A sequence number that is incremented for each
request message received by a device server on which
DS_SQN 8 8 Public
a security function is performed and used to detect
replay attacks.
a These size values are guidelines. Specific security protocols may place more exacting size
requirements on SA parameters.
b
Public SA parameters may be transferred outside a SCSI device unencrypted. Secret SA parameters
shall not be transferred outside a SCSI device. Fields within a protocol specific SA parameter are
Shared or Secret as defined by the applicable SA creation protocol.
c
SAI values between 0 and 255, inclusive, are reserved.
d
Nonce SA parameters shall be at least half the size of the KEY_SEED SA parameter.
e The number of bits of entropy in the KEY_SEED SA parameter should be as close to the number of
bits in the KEY_SEED SA parameter as possible (see RFC 3766).

Working Draft SCSI Primary Commands - 4 (SPC-4) 159

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 74 — Minimum SA parameters (part 2 of 3)

Size (bytes) a

Name Description Min. Max. Scope b

SA parameters that are used by security functions to derive the secret keys that are applied to messages
(e.g., for encryption).
A random nonce value that is generated by the applica-
tion client and used as an input to the key derivation
AC_NONCE d 16 64 Public
security algorithm specified by the KDF_ID SA parame-
ter during the derivation of an encryption key.
A random nonce value that is generated by the device
d server and used as an input to the key derivation secu-
DS_NONCE 16 64 Public
rity algorithm specified by the KDF_ID SA parameter
during the derivation of an encryption key.
A value that is known only to the application client and
device server that are creating this SA that in combina-
tion with the applicable nonce is used to derive the
KEY_SEED e 16 64 Secret
KEYMAT SA parameter. The KEY_SEED SA parameter
shall be set to zero as part of completing the SA
creation function.
A security algorithm (see 5.13.8) coded value that iden-
KDF_ID tifies the KDF used by the application client and device 4 4 Public
server.
SA parameters that are used by security functions to secure messages between the application client and
device server.
A value that is known only to the application client and
device server that are participating in this SA that may
be subdivided into one or more key values that are used
KEYMAT 14 1 024 Secret
in security functions that secure messages. The con-
tents of KEYMAT depend on the USAGE_TYPE SA
parameter value.
a
These size values are guidelines. Specific security protocols may place more exacting size
requirements on SA parameters.
b Public SA parameters may be transferred outside a SCSI device unencrypted. Secret SA parameters
shall not be transferred outside a SCSI device. Fields within a protocol specific SA parameter are
Shared or Secret as defined by the applicable SA creation protocol.
c SAI values between 0 and 255, inclusive, are reserved.
d
Nonce SA parameters shall be at least half the size of the KEY_SEED SA parameter.
e
The number of bits of entropy in the KEY_SEED SA parameter should be as close to the number of
bits in the KEY_SEED SA parameter as possible (see RFC 3766).

160 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 74 — Minimum SA parameters (part 3 of 3)

Size (bytes) a

Name Description Min. Max. Scope b

SA parameters that are used by SA management functions.
A coded value (see table 75) that indicates how the SA
USAGE_TYPE 2 2 Public
is used.
Information associated with how the SA is used (e.g.,
cryptographic algorithms and key sizes). The contents
USAGE_DATA 0 1 024 Public
of USAGE_DATA depend on the USAGE_TYPE SA
parameter value.
SA data that is used in ways defined by the SA creation
Protocol
MGMT_DATA protocol to perform SA management functions (e.g., 0 1 024
specific
deletion of the SA).
a These size values are guidelines. Specific security protocols may place more exacting size
requirements on SA parameters.
b Public SA parameters may be transferred outside a SCSI device unencrypted. Secret SA parameters
shall not be transferred outside a SCSI device. Fields within a protocol specific SA parameter are
Shared or Secret as defined by the applicable SA creation protocol.
c
SAI values between 0 and 255, inclusive, are reserved.
d
Nonce SA parameters shall be at least half the size of the KEY_SEED SA parameter.
e
The number of bits of entropy in the KEY_SEED SA parameter should be as close to the number of
bits in the KEY_SEED SA parameter as possible (see RFC 3766).

The USAGE_TYPE SA parameter (see table 75) provides an indication of how the SA is to be used.

Table 75 — USAGE_TYPE SA parameter

USAGE_TYPE SA parameter

Code a Description Usage model Description Reference

0000h to 0080h Reserved

0081h Tape data encryption ESP-SCSI b None c SSC-4
0082h to 8000h Reserved
8001h CbCS authentication and ESP-SCSI b None c 5.13.6.7
credential encryption
8002h to FFFFh Reserved
a USAGE_TYPE values between 8000h and CFFFh inclusive place additional constraints on how an
SA is to be created as described in 7.7.3.5.14.
b
ESP-SCSI usage is defined in 5.13.7.
c
The USAGE DATA LENGTH field in the IKEv2-SCSI SAUT Cryptographic Algorithms payload (see
7.7.3.5.14) shall contain zero.

Working Draft SCSI Primary Commands - 4 (SPC-4) 161

T10/BSR INCITS 513 Revision 37 17 May 2014

5.13.2.3 Creating an SA

The SECURITY PROTOCOL IN command (see 6.40) and SECURITY PROTOCOL OUT command (see
6.41) security protocols shown in table 76 are used to create SAs. The process of creating an SA establishes
the SA parameter (see 5.13.2.2) values as follows:

a) initial values for:

A) AC_SQN set as described in 5.13.4.9; and
B) DS_SQN set as described in 5.13.4.9;
b) unchanging values for the lifetime of the SA:
A) AC_SAI;
B) DS_SAI;
C) TIMEOUT;
D) KDF_ID;
E) KEYMAT;
F) USAGE_TYPE;
G) USAGE_DATA; and
H) MGMT_DATA;
and
c) values that are zero (see 5.13.4.9) upon completion of SA creation:
A) KEY_SEED;
B) AC_NONCE; and
C) DS_NONCE.

Table 76 — Security protocols that create SAs

Security
Protocol
Code Description References

40h SA creation capabilities 7.7.2

41h IKEv2-SCSI 5.13.4 and 7.7.3

5.13.3 Key derivation functions

5.13.3.1 KDFs overview

A KDF produces KEYMAT from in input KEY_SEED and STRING as follows:

KEYMAT = KDF( KEY_SEED, STRING )

Where:
KEY_SEED is a SA Parameter (see 5.13.2.2); and
STRING is a specified sequence of bytes.

162 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 77 summarizes the KDFs defined by this standard.

Table 77 — KDFs summary

Security
Algorithm
Code
(see table 105) Description Reference

8002 0002h IKEv2-based iterative HMAC KDF based on SHA-1 5.13.3.3

8002 0005h IKEv2-based iterative HMAC KDF based on SHA-256 5.13.3.3
8002 0006h IKEv2-based iterative HMAC KDF based on SHA-384 5.13.3.3
8002 0007h IKEv2-based iterative HMAC KDF based on SHA-512 5.13.3.3
8002 0004h IKEv2-based iterative KDF based on AES-128 in XCBC mode 5.13.3.4

5.13.3.2 IKEv2-based iterative KDF

To produce a sufficient number of bits in KEYMAT, the IKEv2-based (see RFC 4306) iterative uses the
following equation:

KEYMAT = T1 || T2 || T3 || T4 || … || TN

Where:
T1 = KDF( KEY_SEED, STRING || 01h );
T2 = KDF( KEY_SEED, T1 || STRING || 02h );
T3 = KDF( KEY_SEED, T2 || STRING || 03h );
T4 = KDF( KEY_SEED, T3 || STRING || 04h );
… = …
TN = KDF( KEY_SEED, TN-1 || STRING || Nh );
KDF is the function defined in 5.13.3.1;
KEY_SEED is a SA Parameter (see 5.13.2.2); and
STRING is a specified sequence of bytes.

Protocols that use the IKEv2-based iterative KDF to generate KEYMAT should ensure that the number of
KEYMAT bits requested does not cause N to exceed 255. If N reaches 256, then:

1) the requested number of KEYMAT bits is not returned; and

2) the request to produce KEYMAT shall be terminated with an error.

5.13.3.3 HMAC-based KDFs

If the KDF_ID is one of those shown in table 78, the KDF is a combination of the:

a) HMAC function defined in FIPS 198-1 (see 2.6);

b) secure hash function shown in table 78 for the specified KDF_ID value; and
c) IKEv2-based iterative KDF technique (see 5.13.3.2).

The technique requires the following inputs from or related to the SA parameters:

a) AC_SAI;
b) DS_SAI;

Working Draft SCSI Primary Commands - 4 (SPC-4) 163

T10/BSR INCITS 513 Revision 37 17 May 2014

c) AC_NONCE;
d) DS_NONCE;
e) KEY_SEED; and
f) KEYMAT size, in bits.

The USAGE_TYPE SA parameter and USAGE_DATA SA parameter (see 5.13.2.2) specify the KEYMAT size
as part of the security protocol that performs SA creation (see 5.13.2.3).

The IKEv2-based iterative KDF technique (see 5.13.3.2) is applied with the following inputs:

a) IFUNC (see 5.13.3.2) is the HMAC function defined in FIPS 198-1 with the translation of inputs names
shown in table 78;
b) KEY_SEED is the KEY_SEED SA parameter; and
c) STRING contains the concatenated contents of the following SA parameters:
1) AC_NONCE;
2) DS_NONCE;
3) AC_SAI; and
4) DS_SAI.

Table 78 — HMAC-based KDFs

KDF_ID (see table 77)

FIPS 198-1 inputs
selected by KDF_ID 8002 0002h 8002 0005h 8002 0006h 8002 0007h

SHA-1 SHA-256 SHA-384 SHA-512

H (i.e., hash function)
(see table 79) (see table 79) (see table 79) (see table 79)
B (i.e., hash input block size) a 64 64 128 128
L (i.e., hash output block size) a, b 20 32 48 64
K (i.e., key) KEY_SEED SA parameter
text STRING as defined in this subclause and used in 5.13.3.2
a
In accordance with FIPS 198-1, all sizes are shown in bytes.
b
The HMAC-based KDFs defined by this standard do not truncate (i.e., FIPS 198-1 Lambda equals
the L shown in this table).

164 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Details of the hash functions that act as inputs to the FIPS 198-1 HMAC function are shown in table 79.

Table 79 — Hash functions used by HMAC based on KDF_ID

KDF_ID
(see table 77) Function Description

8002 0002h SHA-1 HMAC input H is the SHA-1 secure hash function defined in
FIPS 180-4 (see 2.6).
8002 0005h SHA-256 HMAC input H is the SHA-256 secure hash function defined in
FIPS 180-4.
8002 0006h SHA-384 HMAC input H is the SHA-384 secure hash function defined in
FIPS 180-4.
8002 0007h SHA-512 HMAC input H is the SHA-512 secure hash function defined in
FIPS 180-4.

5.13.3.4 AES-XCBC-PRF-128 IKEv2-based iterative KDF

If the KDF_ID is 8002 0004h, the KDF is a combination of:

a) the AES-XCBC-PRF-128 secure hash function defined in RFC 4434 (see 2.5) and RFC 3566; and
b) the IKEv2-based iterative KDF technique (see 5.13.3.2).

The technique requires the following inputs from or related to the SA parameters:

a) AC_SAI;
b) DS_SAI;
c) AC_NONCE;
d) DS_NONCE;
e) KEY_SEED; and
f) the number of KEYMAT bits that are to be produced.

The IKEv2-based iterative KDF (see 5.13.3.2) is applied with the following inputs:

a) IFUNC (see 5.13.3.2) is the AES-XCBC-PRF-128 secure hash function with the translation of inputs
names shown in table 80;
b) KEY_SEED is the KEY_SEED SA parameter; and
c) STRING contains the concatenated contents of the following SA parameters:
1) AC_NONCE;
2) DS_NONCE;
3) AC_SAI; and
4) DS_SAI.

Table 80 — RFC 3566 parameter translations for the KDF based on AES-XCBC-PRF-128

RFC 3566 Parameter Translation

K (i.e., key) KEY_SEED SA parameter

M (i.e., message) STRING as defined in this subclause and used in 5.13.3.2

Working Draft SCSI Primary Commands - 4 (SPC-4) 165

T10/BSR INCITS 513 Revision 37 17 May 2014

5.13.4 Using IKEv2-SCSI to create an SA

5.13.4.1 Overview

The IKEv2-SCSI protocol is a subset of the IKEv2 protocol (see RFC 4306) that this standard defines for use
in the creation and maintenance of an SA.

An IKEv2-SCSI SA creation transaction shall only be initiated by the application client.

The IKEv2-SCSI protocol creates the following pair of IKE SAs (see RFC 4306):

a) an SA that protects data transferred from the application client to the device server; and
b) an SA that protects data transferred from the device server to the application client.

An IKEv2-SCSI SA creation transaction consists of the following steps:

1) Device Server Capabilities step (see 5.13.4.5): The application client determines the device
server's cryptographic capabilities;
2) Key Exchange step (see 5.13.4.6): The application client and device server:
A) perform a key exchange;
B) determine SAIs;
C) generate the shared keys used for SA management (e.g., SA creation and deletion) (see
5.13.4.8); and
D) may complete the generation of the SA (see 5.13.4.9);
and
3) Authentication step (see 5.13.4.7): Unless omitted by application client and device server
negotiations in the previous steps, the application client and device server:
A) authenticate:
a) each other;
b) the key exchange; and
c) the capability selection;
and
B) complete the generation of the SA (see 5.13.4.9).

The values in the SECURITY PROTOCOL field and the SECURITY PROTOCOL SPECIFIC field in the SECURITY
PROTOCOL IN command (see 6.40) and SECURITY PROTOCOL OUT command (see 6.41) identify the step
of the IKEv2-SCSI protocol (see 7.7.3.2).

The Key Exchange step and the Authentication step depend on the results from the Device Server
Capabilities step in order to create an SA. During the Key Exchange step, the application client and device
server perform independent computations to construct the following sets of shared keys:

a) shared keys that are used by the Authentication step;

b) shared keys that are used by the Authentication step and to delete the SA; and
c) shared keys that are used by SCSI usage type specific operations that obtain security from the
generated SA.

More details about these shared keys are provided in 5.13.4.4.

An application client may or may not:

a) proceed to the Key Exchange step after the Device Server Capabilities step; or
b) perform a separate Device Server Capabilities step for each IKEv2-SCSI SA creation transaction.

166 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If the device server's capabilities have changed since the Device Server Capabilities step, the Authentication
step returns an error, and the Key Exchange step may return an error.

Changes in the device server’s capabilities do not take effect until at least one application client has been
notified of the new capabilities via the parameter data returned by the Device Server Capabilities step.

After a Device Server Capabilities step, the application client performs SA creation by sending a sequence of
two or four IKEv2-SCSI commands over a single I_T_L nexus to the device server. The following commands
constitute an IKEv2-SCSI CCS:

a) if the Authentication step is skipped (see 5.13.4.3.4):

1) a Key Exchange step SECURITY PROTOCOL OUT command (see 5.13.4.6.2); and
2) a Key Exchange step SECURITY PROTOCOL IN command (see 5.13.4.6.3);
or
b) if the Authentication step is performed:
1) a Key Exchange step SECURITY PROTOCOL OUT command (see 5.13.4.6.2);
2) a Key Exchange step SECURITY PROTOCOL IN command (see 5.13.4.6.3);
3) an Authentication step SECURITY PROTOCOL OUT command (see 5.13.4.7.2); and
4) an Authentication step SECURITY PROTOCOL IN command (see 5.13.4.7.3).

The device server shall process each command in the IKEv2-SCSI CCS to completion before returning status.
While a command in the IKEv2-SCSI CCS is being processed by the device server, the application client may
use the REQUEST SENSE command (see 5.13.5) to ascertain the device server’s progress for the command.

If an error is encountered, the device server or application client may abandon the IKEv2-SCSI CCS before
the SA is created (see 5.13.4.10).

The device server shall maintain state for the IKEv2-SCSI CCS on a given I_T_L nexus from the time the Key
Exchange step SECURITY PROTOCOL OUT command is completed with GOOD status until one of the
following occurs:

a) the IKEv2-SCSI CCS completes successfully;

b) the IKEv2-SCSI CCS is abandoned as described in 5.13.4.10;
c) the SA being created by the IKEv2-SCSI CCS is deleted as described in 5.13.4.11;
d) the number of seconds specified in the IKEV2-SCSI PROTOCOL TIMEOUT field of the IKEv2-SCSI Timeout
Values payload (see 7.7.3.5.15) in the Key Exchange step SECURITY PROTOCOL OUT parameter
data elapses and none of the following commands have been received:
A) the next command in the IKEv2-SCSI CCS; or
B) a REQUEST SENSE command;
or
e) one of the following event related SCSI device conditions (see SAM-5) occurs:
A) power cycle;
B) hard reset;
C) logical unit reset; or
D) I_T nexus loss.

If the device server receives a SECURITY PROTOCOL OUT command or SECURITY PROTOCOL IN
command with the SECURITY PROTOCOL field set to IKEv2-SCSI (i.e., 41h) on an I_T_L nexus other than the
one for which IKEv2-SCSI CCS state is being maintained, then:

a) an additional IKEv2-SCSI CCS may be started; or

b) the device server may terminate the command with CHECK CONDITION status, with the sense key
set to ABORTED COMMAND, and the additional sense code set to CONFLICTING SA CREATION
REQUEST.

Working Draft SCSI Primary Commands - 4 (SPC-4) 167

T10/BSR INCITS 513 Revision 37 17 May 2014

Except for the PERSISTENT RESERVE OUT command (see 5.12.4) and the cases described in this
subclause, a device server that is maintaining a IKEv2-SCSI CCS state on a particular I_T_L nexus shall not
alter its processing of new commands received on that I_T_L nexus.

If all of the following conditions are true:

a) the device server includes the following algorithm descriptors in the IKEv2-SCSI SA Creation
Capabilities payload (see 7.7.3.5.12) in the parameter data returned by the Device Server Capabilities
step SECURITY PROTOCOL IN command (see 5.13.4.5):
A) an SA_AUTH_OUT algorithm descriptor (see 7.7.3.6.6) with the ALGORITHM IDENTIFIER field set to
SA_AUTH_NONE; and
B) an SA_AUTH_IN algorithm descriptor (see 7.7.3.6.6) with the ALGORITHM IDENTIFIER field set to
SA_AUTH_NONE;
and
b) the application client sends the following algorithm descriptors to the device server in the IKEv2-SCSI
SA Cryptographic Algorithms payload (see 7.7.3.5.13) in the Key Exchange step SECURITY
PROTOCOL OUT command (see 5.13.4.6.2):
A) an SA_AUTH_OUT algorithm descriptor with the ALGORITHM IDENTIFIER field set to
SA_AUTH_NONE; and
B) an SA_AUTH_IN algorithm descriptor with the ALGORITHM IDENTIFIER field set to
SA_AUTH_NONE;

then:

a) the Authentication step is skipped;

b) the IKEv2-SCSI CCS consists of the two Key Exchange step commands;
c) the device server requires the IKEv2-SCSI SAUT Cryptographic Algorithms payload (see 7.7.3.5.14)
to be present in the parameter data sent by the Key Exchange step SECURITY PROTOCOL OUT
command;
d) the device server returns the IKEv2-SCSI SAUT Cryptographic Algorithms payload in the parameter
data returned by the Key Exchange step SECURITY PROTOCOL IN command; and
e) SA creation occurs upon the completion of the Key Exchange step.

Operation of an IKEv2-SCSI CCS depends on SA_AUTH_NONE being used in both the Authentication step
SECURITY PROTOCOL OUT command and the Authentication step SECUIRTY PROTOCOL IN command,
or SA_AUTH_NONE not being used by either command. Processing requirements placed on the SECURITY
PROTOCOL OUT command during the Key Exchange step (see 7.7.3.6.6) ensure that this dependency is
maintained.

If no other errors are detected and any of the following conditions are true:

a) the device server does not include an SA_AUTH_OUT algorithm descriptor with the ALGORITHM
IDENTIFIER field set to SA_AUTH_NONE in the IKEv2-SCSI SA Creation Capabilities payload in the
parameter data returned by the Device Server Capabilities step SECURITY PROTOCOL IN
command;
b) the device server does not include an SA_AUTH_IN algorithm descriptor with the ALGORITHM
IDENTIFIER field set to SA_AUTH_NONE in the IKEv2-SCSI SA Creation Capabilities payload in the
parameter data returned by the Device Server Capabilities step SECURITY PROTOCOL IN
command; or
c) the application client does not set the ALGORITHM IDENTIFIER field to SA_AUTH_NONE in the
SA_AUTH_OUT algorithm descriptor and the SA_AUTH_IN algorithm descriptor in the IKEv2-SCSI
SA Cryptographic Algorithms payload sent to the device server in the Key Exchange step SECURITY
PROTOCOL OUT command;

168 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

then:

a) the Authentication step is processed;

b) the IKEv2-SCSI CCS consists of the two Key Exchange step commands and two Authentication step
commands;
c) the device server requires the IKEv2-SCSI SAUT Cryptographic Algorithms payload to be absent
from the parameter data sent by the Key Exchange step SECURITY PROTOCOL OUT command;
d) the device server omits the IKEv2-SCSI SAUT Cryptographic Algorithms payload from the parameter
data returned by the Key Exchange step SECURITY PROTOCOL IN command;
e) the device server requires the IKEv2-SCSI SAUT Cryptographic Algorithms payload to be present in
the parameter data sent by the Authentication step SECURITY PROTOCOL OUT command;
f) the device server returns the IKEv2-SCSI SAUT Cryptographic Algorithms payload in the parameter
data returned by the Authentication step SECURITY PROTOCOL IN command; and
g) SA creation occurs upon the completion of the Authentication step.

SA participants should perform the Authentication step unless man-in-the-middle attacks (see 5.13.1.4) are
not of concern or are prevented by a means outside the scope of this standard (e.g., physical security of the
transport).

Omission of the Authentication step provides no defense against a man-in-the-middle adversary that is
capable of modifying SCSI commands. Such an adversary is able to insert itself as an intermediary on the
created SA without knowledge of the SA participants, thereby completely subverting the intended security.
Omission of the Authentication step is only appropriate in environments where the absence of such
adversaries is assured by other means (e.g., a direct physical connection between the systems on which the
application client and device server or use of end-to-end security in the SCSI transport protocol such as
FC-SP-2).

5.13.4.2 IKEv2-SCSI Protocol summary

This subclause summarizes the IKE-v2-SCSI payloads (see 7.7.3.5) that are exchanged between an
application client and a device server during all steps of an IKEv2-SCSI SA creation transaction using
message diagrams. Each IKEv2-SCSI step (see 5.13.4.1) is shown in a separate figure. The contents of a
payload (e.g., Key Exchange) may not be the same in both directions of transfer.

Figure 11 shows the Device Server Capabilities step (see 5.13.4.5). The Device Server Capabilities step
consists of a SECURITY PROTOCOL IN command carrying an IKEv2-SCSI SA Creation Capabilities payload
(see 7.7.3.5.12). The IKEv2-SCSI header is not used.

Application Client Device Server

IKEv2-SCSI SA Creation Capabilities

Key:
Parameter data transferred using a SECURITY
payload(s) PROTOCOL IN command (see 6.40)

payload Required payload

Figure 11 — IKEv2-SCSI Device Server Capabilities step

The IKEv2-SCSI SA Creation Capabilities payload indicates the device server's capabilities for SA creation.

Working Draft SCSI Primary Commands - 4 (SPC-4) 169

T10/BSR INCITS 513 Revision 37 17 May 2014

Figure 12 shows the Key Exchange step (see 5.13.4.6). The Key Exchange step consists of a SECURITY
PROTOCOL OUT command followed by a SECURITY PROTOCOL IN command.

Application Client Device Server

IKEv2-SCSI header — IKEv2-SCSI Timeout Values —

IKEv2-SCSI SA Cryptographic Algorithms — <<IKEv2-SCSI
SAUT Cryptographic Algorithms>> — Key Exchange — Nonce

IKEv2-SCSI header — IKEv2-SCSI Cryptographic Algorithms —

<<IKEv2-SCSI SAUT Cryptographic Algorithms>> —
Key Exchange — Nonce — [Certificate Request]

Key:
Parameter list data transferred using a SECURITY
payload(s) PROTOCOL OUT command (see 6.41)

Parameter data transferred using a SECURITY

payload(s) PROTOCOL IN command (see 6.40)
payload Required payload
[payload] Optional payload
<<payload>> Required if Authentication step skipped (see 5.13.4.1),
otherwise absent

Figure 12 — IKEv2-SCSI Key Exchange step

The IKEv2-SCSI Timeout Values payload (see 7.7.3.5.15) contains timeouts for SA creation and usage.

The IKEv2-SCSI SA Cryptographic Algorithms payloads (see 7.7.3.5.13) are used to select and agree on the
cryptographic algorithms used for creating the SA.

If the Authentication step is skipped (see 5.13.4.1), the IKEv2-SCSI SAUT Cryptographic Algorithms payloads
(see 7.7.3.5.14) are used to select and agree on usage of the SA and the cryptographic algorithms used by
the created SA. If the Authentication step is processed (i.e., not skipped), the SA usage and algorithms
selection is performed during the Authentication step.

The Key Exchange payload (see 7.7.3.5.3) and Nonce payload (see 7.7.3.5.8) are part of the key and nonce
exchanges that are used to generate the IKEv2-SCSI keys and SA keys.

The Certificate Request payload or payloads (see 7.7.3.5.6) enables the device server to request a certificate
from the application client. If the Authentication step is being skipped (see 5.13.4.1), the device server shall
not include any Certificate Request payloads in the parameter data. Use of the Certificate Request payload is
described in 5.13.4.3.3.4.

170 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Figure 13 shows the Authentication step (see 5.13.4.7). The Authentication step consists of a SECURITY
PROTOCOL OUT command followed by a SECURITY PROTOCOL IN command.

Application Client Device Server

IKEv2-SCSI header — Encrypted( Identification – Application

Client — IKEv2-SCSI SAUT Cryptographic Algorithms — [Certifi-
cate] — [Certificate Request] — [Notify] — Authentication )

IKEv2-SCSI header — Encrypted( Identification – Device Server

— IKEv2-SCSI SAUT Cryptographic Algorithms — [Certificate] —
Authentication )

Key:
Parameter list data transferred using a SECURITY
payload(s) PROTOCOL OUT command (see 6.41)

Parameter data transferred using a SECURITY

payload(s) PROTOCOL IN command (see 6.40)
payload Required payload
[payload] Optional payload

Figure 13 — IKEv2-SCSI Authentication step

An Encrypted payload (see 7.7.3.5.11) contains all other Authentication step payloads that are protected using
the cryptographic algorithms determined by the IKEv2-SCSI SA Cryptographic Algorithms payloads (see
7.7.3.5.13) in the Key Exchange step (see figure 12).

The Identification payloads (see 7.7.3.5.4) contain the identities to be authenticated. These identities are not
required to be SCSI names or identifiers.

The IKEv2-SCSI SAUT Cryptographic Algorithms payloads (see 7.7.3.5.14) are used to select and agree on
usage of the SA and the cryptographic algorithms used by the created SA.

The Certificate payload or payloads (see 7.7.3.5.5) respond to the Certificate Request payload(s) sent by the
device server in the Key Exchange step SECURITY PROTOCOL IN command.

The Certificate Request payload or payloads (see 7.7.3.5.6) allows an application client to request the delivery
of a Certificate payload (see 7.7.3.5.5) in the parameter data for the Authentication step SECURITY
PROTOCOL IN command (see 5.13.4.3.3.4).

The Notify payload (see 7.7.3.5.9) provides a means for the application client to inform the device server that
this is the only SA being used between them, and that the device server should discard state for any other
SAs created by the same application client.

The Authenticate payloads (see 7.7.3.5.7) authenticate not only the SA participants, but also the entire
protocol sequence (e.g., the Authenticate payloads prevent a man-in-the-middle attack from succeeding).

Working Draft SCSI Primary Commands - 4 (SPC-4) 171

T10/BSR INCITS 513 Revision 37 17 May 2014

Figure 14 shows the Delete operation (see 5.13.4.11). The Delete operation consists of a SECURITY
PROTOCOL OUT command.

Application Client Device Server

IKEv2-SCSI header — Encrypted( Delete )

Key:
Parameter list data transferred using a SECURITY
payload(s) PROTOCOL OUT command (see 6.41)

payload Required payload

Figure 14 — IKEv2-SCSI Delete operation

An Encrypted payload (see 7.7.3.5.11) contains the Delete payload that is protected using the cryptographic
algorithms determined by the IKEv2-SCSI SA Cryptographic Algorithms payloads (see 7.7.3.5.13) in the Key
Exchange step that was used to create the SA.

The Delete payload (see 7.7.3.5.10) specifies the SA to be deleted.

5.13.4.3 IKEv2-SCSI Authentication

5.13.4.3.1 Overview

IKEv2-SCSI authentication includes these security functions:

a) the application client and device server each establish an identity by demonstrating knowledge of a
secret authentication key associated with that identity;
b) the application client demonstrates knowledge of the current device server capability information; and
c) the application client and device server check the integrity of the current IKEv2-SCSI CCS.

An IKEv2 SCSI authentication algorithm accomplishes these functions by generating and verifying
authentication data based on a concatenation of bytes that includes device server capability information and
the specified portion of the IKEv2-SCSI parameter data (see 7.7.3.5.7) from the IKEv2-SCSI Key Exchange
step (see 5.13.4.6).

An authentication key associated with an identity is used to generate authentication data. IKEv2-SCSI
transfers the authentication data in the AUTHENTICATION DATA field of the IKEv2-SCSI Authentication payload
(see 7.7.3.5.7). The recipient of an IKEv2-SCSI Authentication payload uses a verification key associated with
the identity to verify the authentication data. The identity is:

a) transferred in the IDENTIFICATION DATA field of the appropriate IKEv2-SCSI Identification payload (see
7.7.3.5.4); or
b) obtained from a certificate transferred in the IKEv2-SCSI Certificate payload (see 7.7.3.5.5).

IKEv2-SCSI Authentication is bidirectional (i.e., both the application client and the device server authenticate).
IKEv2-SCSI Authentication is skipped when the application client and device server agree to do so during the
Key Exchange step (see 5.13.4.3.4).

172 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The following IKEv2-SCSI Authentication methods are defined:

a) pre-shared key (see 5.13.4.3.2): the authentication key is also used as the verification key; and
b) digital signature (see 5.13.4.3.3): the verification key and authentication key form a public/private
key pair. The authentication data is a digital signature based on asymmetric cryptography.

Certificates and the IKEv2-SCSI Certificate payload may be used to provide verification keys for digital
signatures to application clients and device servers.

5.13.4.3.2 Pre-shared key authentication

Pre-shared key authentication uses a single cryptographic algorithm to both generate and verify
authentication data. A pre-shared key is associated with an identity that is transferred in the IDENTIFICATION
DATA field of the appropriate Identification payload (see 7.7.3.5.4). The pre-shared key serves as both the
authentication key and the verification key for the identity.

NOTE 12 - A pre-shared key that is not kept secret may compromise the security properties of IKEv2-SCSI.

If pre-shared key authentication is used, then the pre-shared key is the key for the cryptographic algorithm.
Authentication data is generated by applying the cryptographic algorithm with this key to the input data (e.g.,
the applicable concatenation of bytes described in 7.7.3.5.7).

Verification of the authentication data shall consist of:

1) computing the expected contents of the AUTHENTICATION DATA field of the Authentication payload (see
7.7.3.5.7) using the input data and a verification key associated with the identity received in the
Identification payload (see 7.7.3.5.4); and
2) comparing the expected contents to the actual contents of the AUTHENTICATION DATA field.

Verification is successful if the expected contents match the actual contents, otherwise verification is not
successful.

The pre-shared key requirements in RFC 4306 shall apply to IKEv2-SCSI pre-shared keys, including the
following requirements on interfaces for provisioning pre-shared keys:

a) ASCII strings of at least 64 bytes shall be supported;

b) a null terminator shall not be added to any input before it is used as a pre-shared key;
c) a hexadecimal ASCII encoding of the pre-shared key shall be supported; and
d) ASCII encodings other than hexadecimal may be supported. Support for any such encoding shall
include specification of the algorithm for translating the encoding to a binary string as part of the
interface.

The following requirements for pre-shared keys apply in addition to those found in RFC 4306:

a) a pre-shared key shall be associated with one identity;

b) the same pre-shared key shall not be used to authenticate both an application client and a device
server;
c) the same pre-shared key should not be used for a group of application clients or a group of device
servers;
d) information about the size of the pre-shared key shall be stored at the same time that the pre-shared
key is stored; and
e) the means for provisioning pre-shared keys are outside the scope of this standard.

Working Draft SCSI Primary Commands - 4 (SPC-4) 173

T10/BSR INCITS 513 Revision 37 17 May 2014

5.13.4.3.3 Digital signature authentication

5.13.4.3.3.1 Overview

Digital signature authentication uses a matched pair of signature and verification cryptographic algorithms to
generate and verify authentication data that is a digital signature. A public/private key pair is associated with
an identity. The private key is used as the authentication key for the identity. The public key is used as the
verification key for the identity.

NOTE 13 - A private authentication key that is not kept secret may compromise the security properties of
IKEv2-SCSI.

If digital signature authentication is used, then the private key is the key for the signature algorithm. A digital
signature is generated by applying the signature algorithm with this private key to the input data (e.g., the
applicable concatenation of bytes described in 7.7.3.5.7).

Verification of the digital signature shall consist of using the public verification key associated with the identity
and the input data to verify the digital signature received as the contents of the AUTHENTICATION DATA field of
the Authentication payload (see 7.7.3.5.7). Verification is successful if the digital signature is a valid digital
signature over the input data, otherwise verification is not successful.

The means by which an application client or device server obtains a private authentication key are outside the
scope of this standard. An identity and associated public verification key are obtained as follows:

a) if certificates are used for digital signature authentication, then the identity and the associated public
verification key are obtained from a certificate transferred in the first the IKEv2-SCSI Certificate
payload (see 5.13.4.3.3.4); or
b) if certificates are not used for digital signature authentication, then the identity is transferred in the
IDENTIFICATION DATA field of the appropriate IKEv2-SCSI Identification payload (see 7.7.3.5.4) and the
public verification key may be:
A) transferred as a raw RSA key in an IKEv2-SCSI Certificate payload (see 7.7.3.5.5); or
B) obtained by means that are outside the scope of this standard.

If certificates are not used for digital signature authentication, the association between the identity and the
public key should be verified by means outside the scope of this standard.

5.13.4.3.3.2 Certificates and digital signature authentication

A certificate (see RFC 5280) is a data structure that contains:

a) an identity;
b) a public key for that identity;
c) additional relevant information that may constrain use of the public key;
d) the identity of a certification authority (see RFC 5280); and
e) a digital signature generated by that certification authority.

If the identity and associated public key used to verify a digital signature are obtained from a certificate, then
the certification path from the certificate to a trust anchor should be validated (see RFC 5280). If certification
path validation is not successful, verification of the digital signature for that identity shall fail independent of
whether the digital signature is valid.

The means by which an application client or device server obtains a trust anchor are outside the scope of this
standard.

174 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.13.4.3.3.3 Example of certificate use for digital signature authentication

An example of certificate use involves an application client or device server that trusts a certification authority.
Based on this trust, the public key of that certification authority is used to validate a certificate presented as
part of authentication. Successful validation of that certificate establishes that the public key in that certificate
is associated with the identity in the certificate. That public key is then used to verify the digital signature in the
Authentication payload (see 7.7.3.5.7).

In this example, providing a certificate as part of the IKEv2-SCSI Authentication step (see 5.13.4.7) allows a
single certification authority public key to serve as a trust anchor (see RFC 5280) for verification of digital
signatures for any identity that has been issued a certificate by that certification authority, so that a public key
for each identity does not have to be obtained by other means.

Validating a certificate includes multiple checks beyond verifying the signature, and the validation may
traverse a certification path composed of multiple certificates (see RFC 5280).

5.13.4.3.3.4 Handling of the Certificate Request payload and the Certificate payload

As detailed in this subclause, a Certificate Request payload (see 7.7.3.5.6) in one set of parameter data
requests the delivery of a Certificate payload (see 7.7.3.5.5) in the next set of parameter data transferred. The
purpose of these IKEv2-SCSI protocol elements is as follows:

a) each SA participant is allowed to require the delivery of a Certificate payload by the other SA
participant for use in authentication; and
b) each Certificate Request payload indicates the trust anchors list (see RFC 4306) used by the device
server or application client when PKI-based Authentication is being used with certificates that are not
self signed (see RFC 5280).

The presence of one or more Certificate Request payloads in the Key Exchange step SECURITY
PROTOCOL IN command (see 5.13.4.6.3) parameter data indicates that the device server requires the
application client to include a Certificate payload in the parameter list for the Authentication step SECURITY
PROTOCOL OUT command (see 5.13.4.7.2).

The presence of one or more Certificate Request payloads in the Authentication step SECURITY PROTOCOL
OUT command parameter list specifies that the application client requires the device server to return a
Certificate payload in the parameter data for the Authentication step SECURITY PROTOCOL IN command
(see 5.13.4.7.3).

If any Certificate payloads are included in the parameter data, the first Certificate payload shall contain the
public key used to verify the Authentication payload. Additional Certificate payloads may be used to assist in
establishing a certification path from the certificate in the first payload to a trust anchor (see RFC 4306 and
RFC 5280).

The application client and device server may use different authentication methods that require or do not
require the use of Certificate payloads. The presence or absence of Certificate Request payloads and
Certificate payloads may vary in any of the commands described in this subclause.

5.13.4.3.4 Constraints on skipping the Authentication step

In the Device Server Capabilities step (see 5.13.4.5), the parameter data returned by the SECURITY
PROTOCOL IN command (see 7.7.2.3.2) contains the IKEv2-SCSI SA Creation Algorithms payload (see
7.7.3.5.12) that contains one or more SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptors (see
7.7.3.6.6) and one or more SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptors.

Working Draft SCSI Primary Commands - 4 (SPC-4) 175

T10/BSR INCITS 513 Revision 37 17 May 2014

The device server shall allow the Authentication step to be omitted (see 5.13.4.1) if:

a) the ALGORITHM IDENTIFIER field is set to SA_AUTH_NONE (see 7.7.3.6.6) in one of the
SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptors returned in the Device Server
Capabilities step; and
b) the ALGORITHM IDENTIFIER field is set to SA_AUTH_NONE in one of the SA_AUTH_IN IKEv2-SCSI
cryptographic algorithm descriptors returned in the Device Server Capabilities step.

The methods for configuring a device server to return SA_AUTH_NONE are outside the scope of this
standard. Device servers shall not be manufactured to return SA_AUTH_NONE as an Authentication payload
authentication algorithm type in the Device Server Capabilities step.

In the Key Exchange step SECURITY PROTOCOL OUT command (see 5.13.4.6.2), the application client
requests that the Authentication step be omitted by setting the A L G O R I T H M I DE N T I F IE R field to
SA_AUTH_NONE in:

a) the SA_AUTH_OUT cryptographic algorithm descriptor in the IKEv2-SCSI SA Cryptographic

Algorithms payload (see 7.7.3.5.13); and
b) the SA_AUTH_IN cryptographic algorithm descriptor in the IKEv2-SCSI SA Cryptographic Algorithms
payload.

To ensure adequate SA security, the application client should not select the SA_AUTH_NONE value as an
Authentication payload authentication algorithm type unless:

a) an SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor and an SA_AUTH_IN

IKEv2-SCSI cryptographic algorithm descriptor from the Device Server Capabilities step indicates
SA_AUTH_NONE availability; and
b) the application client is configured to omit the Authentication step.

If SA_AUTH_NONE is used, IKEv2-SCSI has no protection against man-in-the-middle attacks. Enabling

return of the SA_AUTH_NONE authentication algorithm type in the Device Capabilities step, and allowing an
application client to select SA_AUTH_NONE in the Key Exchange step are administrative security policy
decisions that absence of authentication is acceptable. Such decisions should only be made in situations
where active attacks on IKEv2-SCSI are not of concern (e.g., direct attachment of a SCSI initiator device and
a SCSI target device, or an end-to-end secure service delivery subsystem such as Fibre Channel secured by
an end-to-end FC-SP-2 SA).

176 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.13.4.4 Summary of IKEv2-SCSI shared keys nomenclature and shared key sizes

The IKEv2-SCSI shared keys are named as shown in table 81.

Table 81 — IKEv2-SCSI shared key names and SA shared key names

SA parameter that
Name stores this shared key Description
Shared keys used only during Authentication step
Shared key used to construct the Authentication payload (see
SK_pi 7.7.3.5.7) for the SECURITY PROTOCOL OUT parameter list in the
shall not be stored in Authentication step (see 5.13.4.7.2).
any SA parameter Shared key used to construct the Authentication payload for the
SK_pr SECURITY PROTOCOL IN parameter data in the Authentication
step.
Shared keys used:
a) during IKEv2-SCSI SA creation and management; and
b) for bytes in a Data-Out Buffer or Data-In Buffer
Shared key used to integrity check the Encrypted payload in the
SECURITY PROTOCOL OUT parameter list in the:
MGMT_DATA
SK_ai a) Authentication step; and
b) IKEv2-SCSI Delete operation (see 5.13.4.11).
KEYMAT Shared key used to integrity check the contents of a Data-Out Buffer.
Shared key used to integrity check the Encrypted payload (see
MGMT_DATA 7.7.3.5.11) in the SECURITY PROTOCOL IN parameter data in the
SK_ar Authentication step (see 5.13.4.7.3).
KEYMAT Shared key used to integrity check the contents of a Data-In Buffer.
Shared key used to encrypt the Encrypted payload in the SECURITY
PROTOCOL OUT parameter list in the:
MGMT_DATA
SK_ei a) Authentication step; and
b) IKEv2-SCSI Delete operation.
KEYMAT Shared key used to encrypt the contents of a Data-Out Buffer.
Shared key used to encrypt the Encrypted payload in the SECURITY
MGMT_DATA
SK_er PROTOCOL IN parameter data in the Authentication step.
KEYMAT Shared key used to encrypt the contents of a Data-In Buffer.
Shared key used to construct the SA keys
Shared key material that is used as input to the KDF that generates
SK_d KEY_SEED
the KEYMAT SA parameter bytes for the SA.

Working Draft SCSI Primary Commands - 4 (SPC-4) 177

T10/BSR INCITS 513 Revision 37 17 May 2014

The sizes of the shared keys are determined as shown in table 82.

Table 82 — Shared key size determination

Shared key size determination

Name Separate encryption and Combined mode encryption and
integrity checking a, b integrity checking a, b
The shared key size is shown in table 553
SK_ai and for the value in the ALGORITHM IDENTIFIER field
of the INTEG IKEv2-SCSI cryptographic zero d
SK_ar c
algorithm descriptor (see 7.7.3.6.4) b.
The shared key size is the value in the KEY
The shared key size is the value in the KEY
LENGTH field of the ENCR IKEv2-SCSI
SK_er and LENGTH field of the ENCR IKEv2-SCSI
cryptographic algorithm descriptor plus the
SK_ei c cryptographic algorithm descriptor (see
number of salt bytes shown in table 549 (see
7.7.3.6.2) b.
7.7.3.6.2) b.
SK_pi and The shared key size is equal to the PRF output length (see table 551) associated with the
SK_pr c value in the ALGORITHM IDENTIFIER field of the PRF IKEv2-SCSI cryptographic algorithm
descriptor (see 7.7.3.6.3) in the IKEv2-SCSI SA Cryptographic Algorithms payload (see
SK_d 7.7.3.5.13).
a
The use of combined mode encryption and integrity checking is indicated by the AUTH_COMBINED
value in the ALGORITHM IDENTIFIER field in the INTEG IKEv2-SCSI cryptographic algorithm descriptor
(see 7.7.3.6.4).
b
For the shared keys used to create an SA, the algorithm descriptor is located in an IKEv2-SCSI SA
Cryptographic Algorithms payload (see 7.7.3.5.13). For the shared keys used after the SA is created
(i.e., the KEYMAT SA parameter), the algorithm descriptor is located in an IKEv2-SCSI SAUT
Cryptographic Algorithms payload (see 7.7.3.5.14).
c To accommodate two shared keys of the specified size, the shared key length shown is doubled for the

purposes of shared key generation.

d
In combined mode encryption and integrity checking, the SK_er and SK_ei are used for both encryption
and integrity checking.

5.13.4.5 Device Server Capabilities step

In the Device Server Capabilities step, the application client sends a SECURITY PROTOCOL IN command
(see 6.40) with the SECURITY PROTOCOL field set to SA creation capabilities (i.e., 40h) and the SECURITY
PROTOCOL SPECIFIC field set to 0101h.

The device server returns the SECURITY PROTOCOL IN parameter data specified by the SECURITY
PROTOCOL SPECIFIC field (see 7.7.2.2) and the parameter data (see 7.7.2.3.2) contains an IKEv2-SCSI SA
Creation Capabilities payload (see 7.7.3.5.12).

178 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

In the Device Server Capabilities step, the device server shall return parameter data containing the
IKEv2-SCSI cryptographic algorithm descriptors (see 7.7.3.6) in at least one complete row shown in table 83.

Table 83 — Device Server Capabilities step parameter data requirements

IKEv2-SCSI cryptographic algorithm descriptor

ENCR PRF INTEG D-H SA_AUTH_OUT SA_AUTH_IN

(see 7.7.3.6.2) (see 7.7.3.6.3) (see 7.7.3.6.4) (see 7.7.3.6.5) (see 7.7.3.6.6) (see 7.7.3.6.6)
The ALGORITHM The ALGORITHM The ALGORITHM The ALGORITHM The ALGORITHM The ALGORITHM
IDENTIFIER field IDENTIFIER field IDENTIFIER field IDENTIFIER field IDENTIFIER field IDENTIFIER field
set to set to set to set to set to set to
8001 0014h 8002 0005h F003 0001h 8004 000Eh 00F9 0001h 00F9 0001h
(i.e., AES-GCM) (i.e., IKEv2-use (i.e., AUTH_ (i.e., 2 048-bit (i.e., RSA (i.e., RSA
and the KEY based on COMBINED) MODP group Digital Digital
LENGTH field SHA-256) (finite field Signature) Signature)
set to 0010h D-H))
The ALGORITHM The ALGORITHM The ALGORITHM The ALGORITHM The ALGORITHM The ALGORITHM
IDENTIFIER field IDENTIFIER field IDENTIFIER field IDENTIFIER field IDENTIFIER field IDENTIFIER field
set to set to set to set to set to set to
8001 000Ch 8002 0007h 8003 000Eh 8004 0015h 00F9 000Bh 00F9 000Bh
(i.e., AES-CBC) (i.e., IKEv2-use (i.e., (i.e., 521-bit (i.e., ECDSA (i.e., ECDSA
and the KEY based on AUTH_HMAC_ random ECP with SHA-512 with SHA-512
LENGTH field set SHA-512) SHA2_ group) on the on the
to 0020h 512_256) P-521 curve) P-521 curve)

In the Device Server Capabilities step, the device server shall return parameter data containing one
SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor with the ALGORITHM IDENTIFIER field is set to
SA_AUTH_NONE and one SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptor with the ALGORITHM
IDENTIFIER field is set to SA_AUTH_NONE if any of the following are true:

a) the ALGORITHM IDENTIFIER field is set to SA_AUTH_NONE in one of the SA_AUTH_OUT IKEv2-SCSI
cryptographic algorithm descriptors returned in the Device Server Capabilities step; or
b) the ALGORITHM IDENTIFIER field is set to SA_AUTH_NONE in one of the SA_AUTH_IN IKEv2-SCSI
cryptographic algorithm descriptors returned in the Device Server Capabilities step.

The device server capabilities returned in the SECURITY PROTOCOL IN parameter data may be changed at
any time by means that are outside the scope of this standard, However, such changes shall not take effect
until at least one application client has been notified of the new capabilities in the parameter data returned by
the Device Server Capabilities step SECURITY PROTOCOL IN command. Management applications may
ensure that their device server capabilities changes take effect by sending a Device Server Capabilities step
SECURITY PROTOCOL IN command to the device server after the changes have been made.

If the device server capabilities change (i.e., upon completion of the processing for a Device Server
Capabilities step SECURITY PROTOCOL IN command that reported changed information in its parameter
data), then the device server shall establish a unit attention condition for the initiator port associated with
every I_T nexus except the I_T nexus on which the Device Server Capabilities step SECURITY PROTOCOL
IN command was received (see SAM-5), with the additional sense code set to SA CREATION CAPABILITIES
DATA HAS CHANGED.

The Device Server Capabilities step participates in the negotiation to skip the Authentication step as
described in 5.13.4.3.4.

Working Draft SCSI Primary Commands - 4 (SPC-4) 179

T10/BSR INCITS 513 Revision 37 17 May 2014

NOTE 14 - The Device Server Capabilities step has no IKEv2 exchange equivalent in RFC 4306. This step
replaces most of IKEv2's negotiation by having the application client obtain the supported capabilities from
the device server.

5.13.4.6 IKEv2-SCSI Key Exchange step

5.13.4.6.1 Overview

The Key Exchange step consists of a Diffie-Hellman key exchange with nonces (see RFC 4306) and is
accomplished as follows:

1) a SECURITY PROTOCOL OUT command (see 5.13.4.6.2);

2) a SECURITY PROTOCOL IN command (see 5.13.4.6.3); and
3) key exchange completion (see 5.13.4.6.4)

NOTE 15 - The Key Exchange step corresponds to the IKEv2 IKE_SA_INIT exchange in RFC 4306, except
that determination of device server capabilities has been moved to the Device Server Capabilities step.

5.13.4.6.2 Key Exchange step SECURITY PROTOCOL OUT command

To send its key exchange message to the device server, the application client sends a SECURITY
PROTOCOL OUT command (see 6.41) with the SECURITY PROTOCOL field set to IKEv2-SCSI (i.e., 41h) and
the SECURITY PROTOCOL SPECIFIC field set to 0102h. The parameter list consists of an IKEv2-SCSI header (see
7.7.3.4) and the following:

1) an IKEv2-SCSI Timeout Values payload (see 7.7.3.5.15);

2) an IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13);
3) if the Authentication step is skipped (see 5.13.4.1), an IKEv2-SCSI SAUT Cryptographic Algorithms
payload (see 7.7.3.5.14);
4) a Key Exchange payload (see 7.7.3.5.3); and
5) a Nonce payload (see 7.7.3.5.8).

The IKEv2-SCSI Timeout Values payload contains the inactivity timeouts that apply to this IKEv2-SCSI SA
creation transaction and the SA that is created.

The IKEv2-SCSI SA Cryptographic Algorithms payload selects the cryptographic algorithms from among
those returned in the Device Server Capabilities step (see 5.13.4.5) to be used in the creation of the SA.

If the Authentication step is skipped, the IKEv2-SCSI SAUT Cryptographic Algorithms payload contains the
following information about the SA to be created:

a) the cryptographic algorithms selected by the application client from among those returned in the
Device Server Capabilities step; and
b) the usage data (see 7.7.3.5.14), if any, that is specific to the SA.

If the application client is unable to select a set of algorithms that are appropriate for the intended creation and
usage of the SA, then the application client should not perform the Key Exchange step to request the creation
of an SA.

IKEv2-SCSI SA Cryptographic Algorithms payload error checking requirements that ensure a successful
negotiation of SA creation algorithms are described in 7.7.3.5.13 and 7.7.3.6.

IKEv2-SCSI SAUT Cryptographic Algorithms payload error checking requirements that ensure a successful
SA creation are described in 7.7.3.5.14 and 7.7.3.6.

180 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The Key Exchange payload contains the application client's Diffie-Hellman value.

The Nonce payload contains the application client's random nonce.

5.13.4.6.3 Key Exchange step SECURITY PROTOCOL IN command

If the Key Exchange step SECURITY PROTOCOL OUT command (see 5.13.4.6.2) completes with GOOD
status, then the application client sends a SECURITY PROTOCOL IN command (see 6.40) with the SECURITY
PROTOCOL field set to IKEv2-SCSI (i.e., 41h) and the SECURITY PROTOCOL SPECIFIC field set to 0102h to obtain
the device server's key exchange message.

The parameter data returned by the device server in response to the SECURITY PROTOCOL IN command
shall contain an IKEv2-SCSI header (see 7.7.3.4) and the following:

1) an IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13);

2) if the Authentication step is skipped (see 5.13.4.1), an IKEv2-SCSI SAUT Cryptographic Algorithms
payload (see 7.7.3.5.14);
3) a Key Exchange payload (see 7.7.3.5.3);
4) a Nonce payload (see 7.7.3.5.8); and
5) zero or more Certificate Request payloads (see 7.7.3.5.6).

As part of processing of the Key Exchange step SECURITY PROTOCOL IN command, the device server
shall:

a) associate the SECURITY PROTOCOL IN command to the last Key Exchange step SECURITY
PROTOCOL OUT command received on the I_T_L nexus. If the device server is maintaining state for
at least one IKEv2-SCSI CCS and the device server is unable to establish this association, then the
device server shall:
A) terminate the SECURITY PROTOCOL IN command with CHECK CONDITION status, with the
sense key set to NOT READY, and the additional sense code set to LOGICAL UNIT NOT READY,
SA CREATION IN PROGRESS; and
B) continue the IKEv2-SCSI CCS.
If the device is not maintaining state for at least one IKEv2-SCSI CSS, the device server shall
terminate the SECURITY PROTOCOL IN command with CHECK CONDITION status, with the sense
key set to ILLEGAL REQUEST, and the additional sense code set to COMMAND SEQUENCE
ERROR.
b) return the device server’s SAI in the IKEv2-SCSI header IKE_SA DEVICE SERVER SAI field;
c) return the IKEv2-SCSI SA Cryptographic Algorithms payload containing:
A) the SA creation cryptographic algorithms supplied by the application client in the Key Exchange
step SECURITY PROTOCOL OUT command parameter list; and
B) the device server's SAI in the SAI field (see 7.7.3.5.13);
d) if the Authentication step is skipped, return the IKEv2-SCSI SAUT Cryptographic Algorithms payload
containing:
A) the SA usage cryptographic algorithms supplied by the application client in the Key Exchange
step SECURITY PROTOCOL OUT command parameter list; and
B) the device server's SAI in the SAI field (see 7.7.3.5.14);
e) return information about the completed Diffie-Hellman exchange with the Key Exchange payload; and
f) return the device server’s random nonce in the Nonce payload.

If the Key Exchange step SECURITY PROTOCOL IN command (see 5.13.4.6.3) completes with GOOD
status, then the application client should copy the device server’s SAI from the IKE_SA DEVICE SERVER SAI field
in the IKEv2-SCSI header to the state it is maintaining for the IKEv2-SCSI CCS.

Working Draft SCSI Primary Commands - 4 (SPC-4) 181

T10/BSR INCITS 513 Revision 37 17 May 2014

Except for the SAI field, the application client should compare the fields in the IKEv2-SCSI SA Cryptographic
Algorithms payload and the IKEv2-SCSI SAUT Cryptographic Algorithms payload, if any, to the values sent in
the Key Exchange step SECURITY PROTOCOL OUT command (see 5.13.4.6.2). If the application client
detects differences in the contents of the payloads other than in the SAI field, then the application client should
abandon the IKEv2-SCSI CCS and notify the device server that the IKEv2-SCSI CCS is being abandoned as
described in 5.13.4.10.

5.13.4.6.4 Key Exchange step completion

Before completing the Key Exchange step SECURITY PROTOCOL IN command (see 5.13.4.6.3) with GOOD
status the device server shall complete the Key Exchange step as described in this subclause.

Upon receipt of GOOD status for the Key Exchange step SECURITY PROTOCOL IN command the
application client should complete the Key Exchange step as described in this subclause.

If the Key Exchange step does not end with the IKEv2-SCSI CCS being abandoned (see 5.13.4.10), then the
contents of the SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor and SA_AUTH_IN
IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.6) in the IKEv2-SCSI SA Cryptographic
Algorithms payload specify how the shared key exchanged by the Key Exchange step SECURITY
PROTOCOL OUT command and the Key Exchange step SECURITY PROTOCOL IN command is used to
generate additional shared keys as follows:

a) if the ALGORITHM IDENTIFIER field in both descriptors contain SA_AUTH_NONE, then the SA
participants generate the SA, including the generation of the shared keys used for SA management
(e.g., SA creation and management) and the shared keys used by the created SA as defined in
5.13.4.9; or
b) if the ALGORITHM IDENTIFIER field in both descriptors contain a value other than SA_AUTH_NONE,
then the SA participants generate shared keys (see 5.13.4.8.3) for the following:
A) seeding the Authentication step generation of the shared keys used by the created SA; and
B) SA creation and management.

5.13.4.6.5 After the Key Exchange step

Processing of the IKEv2-SCSI CCS subsequent to completion of the Key Exchange step (see 5.13.4.6.4)
depends on the contents of the SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor and
SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.6) in the IKEv2-SCSI SA
Cryptographic Algorithms payload as follows:

a) if the ALGORITHM IDENTIFIER field in both descriptors contain SA_AUTH_NONE, then processing of the
IKEv2-SCSI CCS is finished and the generated SA is ready for use; or
b) if the ALGORITHM IDENTIFIER field in both descriptors contain a value other than SA_AUTH_NONE,
then processing of the IKEv2-SCSI CCS continues as follows:
A) the Authentication step is performed (see 5.13.4.7); and
B) the SA participants generate the SA, including the generation of the shared keys used for SA
management and the shared keys used by the created SA as defined in 5.13.4.9.

5.13.4.7 IKEv2-SCSI Authentication step

5.13.4.7.1 Overview

The Authentication step performs the following functions:

a) authenticates both the application client and the device server;

b) protects the previous steps of the protocol; and

182 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

c) cryptographically binds the authentication and the previous steps to the created SA.

The Authentication step is accomplished as follows:

1) a SECURITY PROTOCOL OUT command (see 5.13.4.7.2); and

2) a SECURITY PROTOCOL IN command (see 5.13.4.7.3).

The parameter data for both commands shall be encrypted and integrity protected using the algorithms and
keys determined in the Key Exchange step (see 5.13.4.6).

NOTE 16 - The Authentication step corresponds to the IKEv2 IKE_AUTH exchange in RFC 4306.

5.13.4.7.2 Authentication step SECURITY PROTOCOL OUT command

To send its authentication message to the device server, the application client sends a SECURITY
PROTOCOL OUT command (see 6.41) with the SECURITY PROTOCOL field set to IKEv2-SCSI (i.e., 41h) and
the SECURITY PROTOCOL SPECIFIC field set to 0103h. The parameter data consists of the IKEv2-SCSI header
(see 7.7.3.4) and an Encrypted payload (see 7.7.3.5.11) that:

a) is integrity checked and encrypted in one of the following ways:

A) using separate algorithms as follows:
a) integrity checked using the following:
A) the algorithm specified by the INTEG IKEv2-SCSI algorithm descriptor (see 7.7.3.6.4) in
the IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13) from the Key
Exchange step (see 5.13.4.6); and
B) the SK_ai shared key (see 5.13.4.4);
and
b) encrypted using the following:
A) the algorithm specified by the ENCR IKEv2-SCSI algorithm descriptor (see 7.7.3.6.2) in
the IKEv2-SCSI SA Cryptographic Algorithms payload from the Key Exchange step; and
B) the SK_ei shared key (see 5.13.4.4);
or
B) using a combined integrity check and encryption algorithm that uses the following (i.e., if the
INTEG IKEv2-SCSI algorithm descriptor indicates AUTH_COMBINED):
a) the algorithm specified by the ENCR IKEv2-SCSI algorithm descriptor in the IKEv2-SCSI SA
Cryptographic Algorithms payload; and
b) the SK_ei shared key with additional salt bytes as described in 5.13.4.8.1 and table 82 (see
5.13.4.4);
and
b) contains the following:
1) an Identification – Application Client payload (see 7.7.3.5.4);
2) an IKEv2-SCSI SAUT Cryptographic Algorithms payload (see 7.7.3.5.14);
3) zero or more Certificate payloads (see 7.7.3.5.5);
4) zero or more Certificate Request payloads (see 7.7.3.5.6);
5) zero or one Notify payload (see 7.7.3.5.9); and
6) an Authentication payload (see 7.7.3.5.7).

Before performing any checks on data contained in the Encrypted payload, the device server shall validate the
SECURITY PROTOCOL OUT command parameter data as follows:

a) the device server shall compare the IKE_SA APPLICATION CLIENT SAI field and the IKE_SA DEVICE SERVER
SAI field in the IKEv2-SCSI header to the SAI values it is maintaining for the IKEv2-SCSI CCS, if any,
being maintained for the I_T_L nexus on which the SECURITY PROTOCOL OUT command was
received as described in 7.7.3.4; and

Working Draft SCSI Primary Commands - 4 (SPC-4) 183

T10/BSR INCITS 513 Revision 37 17 May 2014

b) the device server shall decrypt and check the integrity of the Encrypted payload as described in
7.7.3.5.11.4.

Errors detected during the decryption and integrity checking of the Encrypted payload shall be handled as
described in 7.7.3.8.2.

In the SECURITY PROTOCOL OUT command parameter list, the application client:

a) sends information about the SA usage and cryptographic algorithms;

b) sends its identity in the Identification – Application Client payload;
c) sends information proving knowledge of the secret corresponding to the application client's identity in
the Authentication payload; and
d) integrity protects the Key Exchange step and the Authentication step using the Authentication
payload.

The application client may include the Notify payload to send an initial contact notification to the device server.
If sent, the initial contact notification specifies that the application client has no stored state for any SAs with
the device server other than the SA that is being created.

In response to receipt of an initial contact notification, the device server should delete all other SAs that were
authenticated with a SECURITY PROTOCOL OUT command that contained the same Identification -
Application Client payload data as that which is present in the SECURITY PROTOCOL OUT command that
the device server is processing.

If the device server deletes other SAs in response to an initial contact notification, the device server shall do
so only after the successful completion of the Authentication step SECURITY PROTOCOL OUT command. If
an error occurs during the Authentication SECURITY PROTOCOL OUT command, the device server shall
ignore the initial contact notification.

If the device server is unable to proceed with SA creation for any reason (e.g., the verification of the
Authentication payload fails), then the device server shall terminate the SECURITY PROTOCOL OUT
command with CHECK CONDITION status, with the sense key set to ABORTED COMMAND, and the
additional sense code set to an appropriate value. The additional sense code AUTHENTICATION FAILED
shall be used if verification of the Authentication payload fails, or if authentication fails for any other reason.

5.13.4.7.3 Authentication step SECURITY PROTOCOL IN command

If the Authentication step SECURITY PROTOCOL OUT command (see 5.13.4.7.2) completes with GOOD
status, then the application client sends a SECURITY PROTOCOL IN command (see 6.40) with the SECURITY
PROTOCOL field set to IKEv2-SCSI (i.e., 41h) and the SECURITY PROTOCOL SPECIFIC field set to 0103h to obtain
the device server's authentication message. The parameter data consists of the IKEv2-SCSI header (see
7.7.3.4) and an Encrypted payload (see 7.7.3.5.11) that:

a) is integrity checked and encrypted in one of the following ways:

A) using separate algorithms as follows:
a) integrity checked using the following:
A) the algorithm specified by the INTEG IKEv2-SCSI algorithm descriptor (see 7.7.3.6.4) in
the IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13) from the Key
Exchange step (see 5.13.4.6); and
B) the SK_ar shared key (see 5.13.4.4);
and
b) encrypted using the following:
A) the algorithm specified by the ENCR IKEv2-SCSI algorithm descriptor (see 7.7.3.6.2) in
the IKEv2-SCSI SA Cryptographic Algorithms payload from the Key Exchange step; and

184 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

B) the SK_er shared key (see 5.13.4.4);

or
B) using a combined integrity check and encryption algorithm that uses the following (i.e., if the
INTEG IKEv2-SCSI algorithm descriptor indicates AUTH_COMBINED):
a) the algorithm specified by the ENCR IKEv2-SCSI algorithm descriptor in the IKEv2-SCSI SA
Cryptographic Algorithms payload from the Key Exchange step; and
b) the SK_er shared key with additional salt bytes as described in 5.13.4.8.1 and table 82 (see
5.13.4.4);
and
b) contains the following:
1) an Identification – Device Server payload (see 7.7.3.5.4);
2) an IKEv2-SCSI SAUT Cryptographic Algorithms payload (see 7.7.3.5.14);
3) zero or more Certificate payloads (see 5.13.4.3.3.4); and
4) an Authentication payload (see 7.7.3.5.7).

In the SECURITY PROTOCOL IN parameter data, the device server shall:

a) confirm information about the SA usage and cryptographic algorithms;

b) send its identity in the Identification – Device Server payload;
c) authenticate its identity; and
d) protect the integrity of the prior step messages using the Authentication payload.

Before completing the SECURITY PROTOCOL IN command with GOOD status, the device server shall
generate the SA as described in 5.13.4.9.

The application client should verify the Authentication payload as described in 7.7.3.5.7. The Certificate
payload(s) are used as part of this verification for PKI-based authentication. If the Authentication payload is
verified and no other error occurs, the application client should generate the SA as described in 5.13.4.9.

If the application client is unable to proceed with SA creation for any reason (e.g., the verification of the
Authentication payload fails), then the application client should:

a) not use the SA for any additional activities; and

b) notify the device server that the IKEv2-SCSI CCS is being abandoned as described in 5.13.4.10.

The application client should compare the fields in the IKEv2-SCSI SAUT Cryptographic Algorithms payload
to the values sent in the Authentication step SECURITY PROTOCOL OUT command (see 5.13.4.7.2). If the
application client detects differences in the contents of the payloads, the application client should abandon the
IKEv2-SCSI CCS and notify the device server that the IKEv2-SCSI CCS is being abandoned as described in
5.13.4.10.

5.13.4.8 Generating shared keys

5.13.4.8.1 Overview

If the Authentication step is skipped (see 5.13.4.1), then shared key generation is performed as described in
5.13.4.8.2 and is summarized as follows:

a) the shared keys for SA management (e.g., SA creation and deletion) are generated at the same time
as the shared keys used by the created SA; and
b) all the shared keys are generated during completion of the Key Exchange step (see 5.13.4.6.4).

Working Draft SCSI Primary Commands - 4 (SPC-4) 185

T10/BSR INCITS 513 Revision 37 17 May 2014

If the Authentication step is processed (i.e., not skipped), then shared key generation is performed as
described in 5.13.4.8.3 and is summarized as follows:

a) the shared keys for SA management (e.g., SA creation and deletion) are generated during the
completion of the Key Exchange step (see 5.13.4.6.4); and
b) the shared keys used by the created SA are generated during SA generation (see 5.13.4.9).

Regardless of when the SA management shared keys (e.g., used for SA creation and deletion) and shared
keys (see 5.13.4.4) used by the created SA are generated, the organization of the shared keys depends on
the type of encryption and integrity checking algorithm being used as follows:

a) if an encryption algorithm that requires separate integrity checking is used, then separate shared keys
are generated for each algorithm; or
b) if an encryption algorithm that includes integrity checking is used (i.e., if the ALGORITHM IDENTIFIER field
in the INTEG IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.4) contains
AUTH_COMBINED), then no shared keys are generated for the integrity checking algorithm but
additional key material is generated to act as salt bytes (see table 549 in 7.7.3.6.2) for the combined
mode encryption algorithm.

5.13.4.8.2 Generating shared keys when the Authentication step is skipped

If the Authentication step is skipped (see 5.13.4.1), then the shared keys for SA management are generated
at the same time as the shared keys for use by the created SA.

As part of completing the Key Exchange step (see 5.13.4.6.4), the SA participants generate all necessary
shared keys as follows:

1) generate SKEYSEED (see RFC 4306) as described in 5.13.4.8.4;

2) generate the shared keys used for SA management as described in 5.13.4.8.5;
3) as part of generating the SA (see 5.13.4.9) (i.e., as part of completing the Key Exchange step as
described in 5.13.4.6.4), generate the shared keys for use by the created SA as described in
5.13.4.8.6 and store them in the KEYMAT SA parameter.

5.13.4.8.3 Generating shared keys when the Authentication step is processed

If the Authentication step is not skipped (see 5.13.4.1), then:

1) the shared keys for SA management are generated during completion of the Key Exchange step (see
5.13.4.6.4) as follows;
1) generate SKEYSEED (see RFC 4306) as described in 5.13.4.8.4; and
2) generate the shared keys used for SA management as described in 5.13.4.8.5;
and
2) the shared keys for use by the created SA are generated during SA generation (see 5.13.4.9), near
the end of processing for the Authentication step (see 5.13.4.7) as described in 5.13.4.8.6 and store
them in the KEYMAT SA parameter.

5.13.4.8.4 Initializing shared key generation

5.13.4.8.4.1 Initializing for SA creation shared key generation

The SA parameters are initialized for the KDF function used to generate SA creation shared keys as follows:

1) generate the input to the PRF function by performing the last steps of the key exchange algorithm
selected by the ALGORITHM IDENTIFIER field in the D-H IKEv2-SCSI algorithm descriptor (see 7.7.3.6.5)

186 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

in the IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13) using at least the contents
of one of the following fields as inputs to those last steps:
A) the KEY EXCHANGE DATA field in the Key Exchange payload (see 7.7.3.5.3) in the Key Exchange
SECURITY PROTOCOL OUT command (see 5.13.4.6.2) parameter data; and
B) the KEY EXCHANGE DATA field in the Key Exchange payload in the Key Exchange SECURITY
PROTOCOL IN command (see 5.13.4.6.3) parameter data;
2) generate SKEYSEED (see RFC 4306) using the output from step 1) and the PRF selected by the
ALGORITHM IDENTIFIER field in the PRF IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.3)
in the IKEv2-SCSI SA Cryptographic Algorithms payload;
3) store the generated SKEYSEED value in the KEY_SEED SA parameter;
4) store the contents of the IKE_SA APPLICATION CLIENT SAI field from the IKEv2-SCSI Header (see
7.7.3.4) from the Key Exchange step SECURITY PROTOCOL IN command (see 5.13.4.6.3) in the
AC_SAI SA parameter;
5) store the contents of the IKE_SA DEVICE SERVER SAI field from the IKEv2-SCSI Header (see 7.7.3.4)
from the Key Exchange step SECURITY PROTOCOL IN command (see 5.13.4.6.3) in the DS_SAI
SA parameter;
6) store the contents of the NONCE DATA field from the Nonce payload (see 7.7.3.5.8) from the parameter
data for the Key Exchange step SECURITY PROTOCOL OUT command (see 5.13.4.6.2) in the
AC_NONCE SA parameter; and
7) store the contents of the NONCE DATA field from the Nonce payload (see 7.7.3.5.8) from the parameter
data for the Key Exchange step SECURITY PROTOCOL IN command (see 5.13.4.6.3) in the
DS_NONCE SA parameter.

5.13.4.8.4.2 Initializing for generation of shared keys used by the created SA

The SA parameters are initialized for the KDF function used to generate the shared keys that are used by the
created SA as follows:

1) store the SK_d value that was generated along with the other shared keys used in SA creation (see
5.13.4.8.5) in the KEY_SEED SA parameter;
2) store the contents of the IKE_SA APPLICATION CLIENT SAI field from the IKEv2-SCSI Header (see
7.7.3.4) from the Key Exchange step SECURITY PROTOCOL IN command (see 5.13.4.6.3) in the
AC_SAI SA parameter;
3) store the contents of the IKE_SA DEVICE SERVER SAI field from the IKEv2-SCSI Header (see 7.7.3.4)
from the Key Exchange step SECURITY PROTOCOL IN command (see 5.13.4.6.3) in the DS_SAI
SA parameter;
4) store the contents of the NONCE DATA field from the Nonce payload (see 7.7.3.5.8) from the parameter
data for the Key Exchange step SECURITY PROTOCOL OUT command (see 5.13.4.6.2) in the
AC_NONCE SA parameter; and
5) store the contents of the NONCE DATA field from the Nonce payload (see 7.7.3.5.8) from the parameter
data for the Key Exchange step SECURITY PROTOCOL IN command (see 5.13.4.6.3) in the
DS_NONCE SA parameter.

5.13.4.8.5 Generating shared keys used for SA management

The shared keys used for SA management (e.g., SA creation and deletion) are generated using the
SKEYSEED generated during initialization (see 5.13.4.8.4) and the steps described in this subclause.

Correct operation of SA management requires that the application client and device server use the same
value for each shared key. SA management operations attempted with different values for the same shared
key result in errors (e.g., integrity check errors).

Working Draft SCSI Primary Commands - 4 (SPC-4) 187

T10/BSR INCITS 513 Revision 37 17 May 2014

Which shared keys are generated for SA management depends on:

a) whether the encryption algorithm includes integrity checking as indicated by the contents of the
ALGORITHM IDENTIFIER field in the INTEG IKEv2-SCSI cryptographic algorithm descriptor (see
7.7.3.6.4) of the IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13), and
b) whether the Authentication step is skipped (see 5.13.4.1).

Using the contents of the initialized SA parameters (see 5.13.4.8.4.1), the INTEG ALGORITHM IDENTIFIER field,
and the KDF selected by the ALGORITHM IDENTIFIER field in the PRF IKEv2-SCSI cryptographic algorithm
descriptor in the IKEv2-SCSI SA Cryptographic Algorithms payload the following shared keys (see 5.13.4.4)
are generated in the order shown:

a) if the INTEG ALGORITHM IDENTIFIER field is not set to AUTH_COMBINED, then generate the following
shared keys (see 5.13.4.4):
A) if the Authentication step is not skipped, generate the following shared keys:
1) SK_d;
2) SK_ai;
3) SK_ar;
4) SK_ei;
5) SK_er;
6) SK_pi; and
7) SK_pr;
or
B) if the Authentication step is skipped, generate the following shared keys:
1) SK_d;
2) SK_ai;
3) SK_ar;
4) SK_ei; and
5) SK_er;
or
b) if the INTEG ALGORITHM IDENTIFIER field is set to AUTH_COMBINED, then generate the following
shared keys:
A) if the Authentication step is not skipped, generate the following shared keys:
1) SK_d;
2) SK_ei with additional salt bytes as described in 5.13.4.8.1 and table 82 (see 5.13.4.4);
3) SK_er with additional salt bytes as described in 5.13.4.8.1 and table 82 (see 5.13.4.4);
4) SK_pi; and
5) SK_pr;
or
B) if the Authentication step is skipped, generate the following shared keys:
1) SK_d;
2) SK_ei with additional salt bytes as described in 5.13.4.8.1 and table 82 (see 5.13.4.4); and
3) SK_er with additional salt bytes as described in 5.13.4.8.1 and table 82 (see 5.13.4.4).

The shared keys thus generated are combined with other data and stored in the MGMT_DATA SA parameter
as described in 5.13.4.9.

How to determine the sizes of the shared keys to be generated is summarized in table 82 (see 5.13.4.4).

5.13.4.8.6 Generating shared keys for use by the created SA

As part of completing the Authentication step and generating the SA (see 5.13.4.9), the SA participants
initialize the SA parameters for performing a KDF (see 5.13.4.8.4.2), and use the KDF selected by the
ALGORITHM IDENTIFIER field in the PRF IKEv2-SCSI cryptographic algorithm descriptor in the Key Exchange

188 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

step IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13) to generate the following shared keys
(see 5.13.4.4) in the order shown and store them in the KEYMAT SA parameter:

a) if the ALGORITHM IDENTIFIER field in the ENCR IKEv2-SCSI cryptographic algorithm descriptor (see
7.7.3.6.2) contains ENCR_NULL in the IKEv2-SCSI SAUT Cryptographic Algorithms payload (see
7.7.3.5.14), then generate the following shared keys:
1) SK_ai;
2) SK_ar;
and
b) if the ALGORITHM IDENTIFIER field in the ENCR IKEv2-SCSI cryptographic algorithm descriptor does not
contain ENCR_NULL in the IKEv2-SCSI SAUT Cryptographic Algorithms payload, then generate the
following shared keys:
A) if the ALGORITHM IDENTIFIER field in the INTEG IKEv2-SCSI cryptographic algorithm descriptor
(see 7.7.3.6.4) does not contain AUTH_COMBINED in the IKEv2-SCSI SAUT Cryptographic
Algorithms payload (see 7.7.3.5.14), then generate the following shared keys:
1) SK_ai;
2) SK_ar;
3) SK_ei; and
4) SK_er;
or
B) if the ALGORITHM IDENTIFIER field in the INTEG IKEv2-SCSI cryptographic algorithm descriptor
contains AUTH_COMBINED in the IKEv2-SCSI SAUT Cryptographic Algorithms payload, then
generate the following shared keys:
1) SK_ei with additional salt bytes as described in 5.13.4.8.1 and table 82 (see 5.13.4.4); and
2) SK_er with additional salt bytes as described in 5.13.4.8.1 and table 82 (see 5.13.4.4).

How to determine the sizes of the shared keys to be generated is summarized in table 82 (see 5.13.4.4).

5.13.4.9 IKEv2-SCSI SA generation

Depending on whether or not the Authentication step was skipped (see 5.13.4.1), the SA participants shall
generate shared keys as described in 5.13.4.8.

The SA participants shall initialize the SA parameters as follows:

1) KEYMAT shall be set as follows:

A) if the Authentication step is skipped, KEYMAT shall be set as described in 5.13.4.8.2; or
B) if the Authentication step is processed, KEYMAT shall be set as described in 5.13.4.8.3;
and
2) the other SA parameters shall be set as follows:
A) AC_SAI shall be set to the value in the IKE_SA APPLICATION CLIENT SAI field in the IKEv2-SCSI
header (see 7.7.3.4) in the Key Exchange step SECURITY PROTOCOL OUT command (see
5.13.4.6.2);
B) DS_SAI shall be set to the value in the IKE_SA DEVICE SERVER SAI field in the IKEv2-SCSI header
in the Key Exchange step SECURITY PROTOCOL IN command (see 5.13.4.6.3);
C) TIMEOUT shall be set to the IKEV2-SCSI SA INACTIVITY TIMEOUT field in the IKEv2-SCSI Timeout
Values payload (see 7.7.3.5.15) in the Key Exchange step SECURITY PROTOCOL OUT
command;
D) KDF_ID shall be set to the value in the ALGORITHM IDENTIFIER field in the PRF IKEv2-SCSI
cryptographic algorithm descriptor (see 7.7.3.6.3) in the IKEv2-SCSI SA Cryptographic
Algorithms payload (see 7.7.3.5.13);
E) AC_SQN shall be set to one;
F) DS_SQN shall be set to one;
G) AC_NONCE shall be set to zero;

Working Draft SCSI Primary Commands - 4 (SPC-4) 189

T10/BSR INCITS 513 Revision 37 17 May 2014

H) DS_NONCE shall be set to zero;

I) KEY_SEED shall be set to zero;
J) USAGE_TYPE shall be set to the value in the SA TYPE field in the IKEv2-SCSI SAUT
Cryptographic Algorithms payload (see 7.7.3.5.14) in the Key Exchange step SECURITY
PROTOCOL OUT command;
K) USAGE_DATA shall contain at least the following values from the IKEv2-SCSI SAUT
Cryptographic Algorithms payload (see 7.7.3.5.14) in either the Key Exchange step SECURITY
PROTOCOL OUT command or the Authentication step SECURITY PROTOCOL OUT command:
a) the ALGORITHM IDENTIFIER field and KEY LENGTH field from the ENCR IKEv2-SCSI
cryptographic algorithm descriptor (see 7.7.3.6.2);
b) the ALGORITHM IDENTIFIER field from the INTEG IKEv2-SCSI cryptographic algorithm
descriptor (see 7.7.3.6.4); and
c) the contents, if any, of the USAGE DATA field;
and
L) MGMT_DATA shall contain at least the following values:
a) from the IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13) in the Key
Exchange step SECURITY PROTOCOL OUT command:
A) the ALGORITHM IDENTIFIER field and KEY LENGTH field from the ENCR IKEv2-SCSI
cryptographic algorithm descriptor (see 7.7.3.6.2); and
B) the ALGORITHM IDENTIFIER field from the INTEG IKEv2-SCSI cryptographic algorithm
descriptor (see 7.7.3.6.4);
b) from the shared keys generated for SA management (see 5.13.4.8.5), the following shared
keys and salt bytes:
A) the value of SK_ai, if any;
B) the value of SK_ar, if any;
C) the value of SK_ei, with additional salt bytes, if any; and
D) the value of SK_er, with additional salt bytes, if any;
and
c) the next value of the MESSAGE ID field in the IKEv2-SCSI header.

NOTE 17 - The inclusion of the algorithm identifiers and key length in MGMT_DATA SA parameter enables
the SA to apply the same encryption and integrity algorithms that IKEv2-SCSI negotiated to future
IKEv2-SCSI SECURITY PROTOCOL OUT commands and IKEv2-SCSI SECURITY PROTOCOL IN
commands, if any.

5.13.4.10 Abandoning an IKEv2-SCSI CCS

The occurrence of errors in either the application client or the device server may require that an IKEv2-SCSI
CCS be abandoned.

A device server shall indicate that it has abandoned an IKEv2-SCSI CCS, if any, by terminating an
IKEv2-SCSI CCS command (see 5.13.4.1) received on the I_T_L nexus for which the IKEv2-SCSI CCS state

190 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

is being maintained with any combination of status and sense data other than those shown in table 84.

Table 84 — IKEv2-SCSI command terminations that do not abandon the CCS

Status Additional Sense

IKEv2-SCSI CCS command (Sense Key) Code Description
SECURITY PROTOCOL OUT GOOD n/a Indicates IKEv2-SCSI CCS is
SECURITY PROTOCOL IN (n/a) progressing as described in
this standard
Key Exchange step CHECK CONFLICTING SA At least one IKEv2-SCSI CCS
SECURITY PROTOCOL OUT CONDITION CREATION REQUEST is already active, and attempts
(see 5.13.4.6.2) (ABORTED to start another are blocked
COMMAND) until the first CCS completes
SECURITY PROTOCOL OUT CHECK LOGICAL UNIT NOT Device server is busy process-
SECURITY PROTOCOL IN CONDITION READY, SA CREATION ing another command in the
(NOT IN PROGRESS IKEv2-SCSI CCS associated
READY) with this I_T_L nexus or a dif-
ferent IKEv2-SCSI CCS asso-
ciated with a different I_T_L
nexus
SECURITY PROTOCOL IN CHECK INVALID FIELD IN CDB Incorrect SECURITY
CONDITION PROTOCOL IN CDB format
(ILLEGAL
Authentication step UNABLE TO Device server is unable to
REQUEST)
SECURITY PROTOCOL OUT DECRYPT decrypt the Encrypted payload
(see 5.13.4.7.2) PARAMETER LIST (see 7.7.3.5.11) or the integrity
check fails
SECURITY PROTOCOL OUT SA CREATION To adapt to possible denial of
PARAMETER VALUE service attacks, a condition for
REJECTED which the optimal response
includes an additional sense
code of SA CREATION
PARAMETER VALUE INVALID
and the abandonment of the
CCS is not causing the CCS
to be abandoned

As part of abandoning an IKEv2-SCSI CCS, the device server shall:

a) discard all maintained state (see 5.13.4.1); and

b) prepare to allow a future Key Exchange step SECURITY PROTOCOL OUT command received on
any I_T_L nexus to start a new IKEv2-SCSI CCS.

After a device server abandons an IKEv2-SCSI CCS, the device server shall respond to all new IKEv2-SCSI
protocol commands as if an IKEv2-SCSI CCS had never been started.

An application client should not abandon an IKEv2-SCSI CCS when the next command in the CCS is a
SECURITY PROTOCOL IN command. Instead, the application client should send the appropriate SECURITY
PROTOCOL IN command and then abandon the IKEv2-SCSI CCS.

Working Draft SCSI Primary Commands - 4 (SPC-4) 191

T10/BSR INCITS 513 Revision 37 17 May 2014

An application client should specify that it has abandoned an IKEv2-SCSI CCS by sending an IKEv2-SCSI
Delete operation (see 5.13.4.11) with application client SAI and device server SAI information that matches
that of the IKEv2-SCSI CCS being abandoned.

5.13.4.11 Deleting an IKEv2-SCSI SA

As part of deleting an SA, both sets of SA parameters (see 5.13.2.2) are deleted as follows:

1) the application client uses the information in its SA parameters to prepare an IKEv2-SCSI Delete
operation that requests deletion of the device server’s SA parameters;
2) the application client deletes its SA parameters and any associated data;
3) the application client sends the IKEv2-SCSI Delete operation prepared in step 1) to the device server;
4) in response to the IKEv2-SCSI Delete operation, the device server deletes its SA parameters and any
associated data.

The IKEv2-SCSI Delete operation is a SECURITY PROTOCOL OUT command with the SECURITY PROTOCOL
field set to IKEv2-SCSI (i.e., 41h) and the SECURITY PROTOCOL SPECIFIC field set to 0104h. The parameter data
consists of the IKEv2-SCSI header (see 7.7.3.4) and an Encrypted payload (see 7.7.3.5.11) that contains the
one Delete payload (see 7.7.3.5.10).

The Delete payload should conform to the requirements described in 7.7.3.5.10.

The device server shall process a valid Delete operation SECURITY PROTOCOL OUT command regardless
of whether or not IKEv2-SCSI CCS state is being maintained for the I_T_L nexus on which the command is
received.

The application client SAI and device server SAI information in a valid Delete operation may or may not
identify an IKEv2-SCSI CCS for which state is being maintained for the I_T_L nexus on which the command is
received (see 7.7.3.5.11).

5.13.5 Security progress indication

The cryptographic calculations required by some security protocols are capable of consuming significant
amounts of time in the device server. While cryptographic security calculations are in progress, the device
server shall provide pollable REQUEST SENSE data (see 5.10.2) with:

a) the sense key set to NOT READY;

b) the additional sense code set to LOGICAL UNIT NOT READY, SA CREATION IN PROGRESS; and
c) the PROGRESS INDICATION field set to indicate the progress of the device server in performing the
necessary cryptographic calculations.

The device server shall not use the progress indication to report the detailed progress of cryptographic
computations that take a variable amount of time based on their inputs. The device server may use the
progress indication to report synthetic progress that does not reveal the detailed progress of the computation
(e.g., divide a constant expected time for the computation by 10 and advance the progress indication in 10%
increments based on the elapsed time as compared to the expected time).

The requirements in this subclause apply to implementations of Diffie-Hellman computations and operations
involving any keys (e.g., RSA) that optimize operations on large numbers based on the values of inputs (e.g.,
a computational step may be skipped if a bit or set of bits in an input is zero). A progress indication that
advances based on the computation structure (e.g., count of computational steps) may reveal the time taken
by content-dependent portions of the computation, and reveal information about the inputs.

192 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.13.6 Command security

5.13.6.1 Overview

SCSI command security defines techniques for protecting against inadvertent or malicious misuse of SCSI
commands to gain unauthorized access to logical units.

The following classes are used to specify SCSI command security:

a) Secure CDB Originator class;

b) Security Manager class;
c) Enforcement Manager class; and
d) Secure CDB Processor class.

The relationship between those classes varies depending on the implemented security technique.

5.13.6.2 Secure CDB Originator class

The Secure CDB Originator class is a kind of application client that originates SCSI commands to which it has
attached a security CDB extension (see 4.2.4) that allows an enforcement manager to determine if the SCSI
command may be processed by the addressed logical unit.

The secure CDB originator interacts with the security manager to determine:

a) the types of the SCSI commands it is allowed to send to the Secure CDB processor; and
b) the content of the security CDB extension to be attached to the SCSI commands.

5.13.6.3 Secure CDB Processor class

The Secure CDB Processor class is a kind of device server that processes SCSI commands that have an
attached security extension, if an enforcement manager allows that type of SCSI command from the
originating application client to be processed.

The secure CDB processor determines if a SCSI command is allowed to be processed by communicating the
following information to the enforcement manager:

a) the CDB of the SCSI command to be processed; and

b) the security CDB extension, if any, attached to the SCSI command to be processed.

The secure CDB processor shall always allow the processing of the following commands when they do not
have an attached security CDB extension:

a) INQUIRY;
b) REPORT LUNS;
c) REPORT SUPPORTED OPERATION CODES;
d) REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS;
e) REPORT TARGET PORT GROUPS; and
f) REQUEST SENSE.

5.13.6.4 Enforcement Manager class

The Enforcement Manager class is either contained within a:

a) device server (i.e., has the same LUN as the secure CDB processor); or

Working Draft SCSI Primary Commands - 4 (SPC-4) 193

T10/BSR INCITS 513 Revision 37 17 May 2014

b) target device (e.g., has a W_LUN, or vendor specific presence in the SCSI target device).

The enforcement manager determines if the secure CDB processor is allowed to, or prevented from,
processing a SCSI command using security information received from the security manager.

If a secure CDB originator has not been authenticated, the enforcement manager shall not make
determinations about whether a command from that secure CDB originator is allowed or prevented.

5.13.6.5 Security Manager class

The Security Manager class communicates with the Secure CDB Originator class (see 5.13.6.2) and the
Enforcement Manager class (see 5.13.6.4) as shown in table 85.

Table 85 — Security Manager class relationships

Communications mechanism for …

Secure CDB Enforcement

Security Manager location Originator Manager
Via the SCSI domain’s
An application client located in the same Outside the scope of
service delivery sub-
SCSI device as the secure CDB originator this standard
system (see SAM-5)
Via the SCSI domain’s
A device server located in the same SCSI Outside the scope of
service delivery sub-
device as the secure CDB processor this standard
system (see SAM-5)
A SCSI device contained within the same Via the SCSI domain’s Via the SCSI domain’s
SCSI domain as the secure CDB originator service delivery sub- service delivery sub-
and the secure CDB processor a system (see SAM-5) system (see SAM-5)
Not a SCSI device, device server, or Outside the scope of Outside the scope of
application client this standard this standard
a This SCSI device is required to contain an application client and a device server (i.e., to
contain both a SCSI Initiator Port class (see SAM-5) and a SCSI Target Port class (see
SAM-5)).

The security manager:

a) maintains SCSI command security information for the SCSI domain (e.g., authorization and
authentication information);
b) delivers to the enforcement manager the security information required by the enforcement manager to
determine if the secure CDB processor is allowed to, or prevented from, processing a SCSI
command; and
c) responds to requests from authenticated secure CDB originators to send SCSI commands to a
secure CDB processor as follows:
A) if the secure CDB originator sends its authentication and an authorization request, then the
security manager responds with the authorization information necessary for the secure CDB
originator to generate security information to be attached to any authorized CDB that is sent to the
secure CDB processor; or
B) if the secure CDB originator sends its authentication, an authorization request, and the security
information to be attached to CDBs, then the security manager shall only accept the request if the
secure CDB originator is authorized to send the requested SCSI commands to the requested
secure CDB processor.

194 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.13.6.6 The relationship between SAs and command security

As defined by this standard, SAs provide the following forms of secure communications for selected portions
of selected CDB and command parameter data:

a) cryptographic data integrity provided by Message Authentication Code or Integrity Check Value; and
b) confidentially provided by data encryption.

The SAs defined by this standard do not apply to data communicated in the CDBs sent from the secure CDB
originator to the secure CDB processor. The function of securing CDBs is performed by the command security
features described in 5.13.6. Command security and SAs features may be used in concert to protect both the
CDB data and the parameter data.

Authorization information (see 5.13.6.5) includes associations between:

a) permissions to use certain commands and command options; and

b) secure CDB originator identities.

SAs provide a mechanism for satisfying the secure CDB originator authentication requirements placed on
enforcement managers (see 5.13.6.4). Every secure CDB originator that is authenticated using an SA is
required to be authenticated using a unique SA.

Some command security techniques (e.g., the CbCS technique described in 5.13.6.7) depend on an
established secure channel between a secure CDB originator and secure CDB processor. SAs provide a
mechanism for establishing such secure channels. If SAs are used in this manner, multiple secure CDB
originators may share a common SA; however, such SAs do not authenticate any specific secure CDB
originator.

5.13.6.7 Capability-based command security technique

5.13.6.7.1 Overview

CbCS is a credential-based system that manages access to a logical unit by the coordination between shared
keys and security parameters set by the CbCS management application client (see 5.13.6.7.4) and
credentials generated by the CbCS management device server (see 5.13.6.7.3). The mechanism for
coordination between the CbCS management device server and the CbCS management application client is
not defined in this standard.

The CbCS protocol enables centralized management of SCSI command security.

CbCS secures access to a logical unit or a volume (see SSC-4) by providing cryptographic integrity of
credentials that are added to commands sent to the logical unit. This cryptographic integrity is based on
mutual trust and key exchanges between the CbCS management device server, CbCS management
application client, and the enforcement manager.

Different levels of protection and security are achieved by using different CbCS methods. The following CbCS
methods are defined by this standard:

a) the BASIC CbCS method (see 5.13.6.7.8.2) provides protection against errors but does not prevent
unauthorized access caused by means of malicious attacks (e.g., identity spoofing and network
attacks); and
b) the CAPKEY CbCS method (see 5.13.6.7.8.3) enforces application client authentication and provides
cryptographic integrity of credentials. It protects against the following types of unauthorized access
attacks:

Working Draft SCSI Primary Commands - 4 (SPC-4) 195

T10/BSR INCITS 513 Revision 37 17 May 2014

A) Without cryptographic message integrity in the service delivery subsystem:

a) illegal use of credentials beyond their original scope and life span;
b) forging or stealing credentials; and
c) using malformed credentials;
and
B) with cryptographic message integrity in the service delivery subsystem:
a) network errors and malicious message modifications; and
b) message replay attacks.

CbCS also supports rapid revocation of credentials, per SCSI target device and per logical unit.

CbCS does not define task management function security.

CbCS (see figure 15) is composed of the following classes:

a) Security Manager class (see 5.13.6.7.2) that contains the following classes:
A) CbCS Management Device Server class (see 5.13.6.7.3); and
B) CbCS Management Application Client class (see 5.13.6.7.4);
b) SCSI Initiator Device class (see SAM-5) that contains the following class:
A) Secure CDB Originator class (see 5.13.6.7.5);
and
c) SCSI Target Device class (see SAM-5) that contains the following classes:
A) Secure CDB Processor class (see 5.13.6.7.6); and
B) Enforcement Manager class (see 5.13.6.7.7).

196 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Figure 15 shows the flow of transactions between the components of a CbCS capable SCSI domain.

Note: See SAM-5 0..1 1 1..* 1..*

for details on SCSI Target Device SCSI Device SCSI Domain
classes shown in
the shaded area.
1 1 1 1
1
Level 1 Hierarchical Logical Unit

1 SCSI Initiator Device

1..* 1
Logical Unit
1..*
1 Application Client

1
Device Server

0..1
Secure CDB Processor Secure CDB Originator Security Manager

Process CbCS information() Request CbCS capabilities() 1 1

1 Request CbCS capability keys()
1..* 1..*
requests authorization

delivers capabilities and shared keys

command validation

validates SCSI

1 1 1
commands
requests

CbCS Management Device Server

Decision database[1]
Authenticate secure CDB originator()
1

{Each instance of
a SCSI Target exchanges shared keys
0..1 0..1 Device class that
Enforcement Manager contains a secure
CDB processor 1 1
Exchange shared keys() shall contain at least CbCS Management Application Client
Receive security parameters() one enforcement
Validate SCSI command() manager.}
Exchange shared keys()
1..* Send security parameters()
1

Figure 15 — CbCS overview class diagram

Working Draft SCSI Primary Commands - 4 (SPC-4) 197

T10/BSR INCITS 513 Revision 37 17 May 2014

Each instance of CbCS shall contain:

a) one security manager that shall contain:

A) one CbCS management device server; and
B) one CbCS management application;
b) one or more SCSI initiator devices that shall contain:
A) one or more secure CDB originators;
and
c) one or more SCSI target devices that shall contain:
A) one secure CDB processor per logical unit; and
B) the following:
a) one enforcement manager per secure CDB processor;
b) one enforcement manager per SCSI target device; or
c) both.

5.13.6.7.2 Security Manager class

The Security Manager class for the CbCS technique manages access of secure CDB originators to logical
units or volumes (see SSC-4). The security manager uses a decision database to obtain the authorization
information required for deciding the type and duration of access granted to secure CDB originator to a given
logical unit or volume (see SSC-4). The security manager communicates with secure CDB originators to
provide them CbCS credentials (see 5.13.6.7.12), and with enforcement managers to exchange shared keys
(see 5.13.6.7.11) and send CbCS parameters (see 5.13.6.7.15).

The security manager may be located and may communicate with secure CDB originators and enforcement
managers as follows:

a) if the security manager is a SCSI device contained within the same SCSI domain as the secure CDB
originator and the enforcement manager, then the security manager shall contain an application client
and use the application client to communicate to the enforcement manager, and the security manager
shall contain a device server and use the device server to communicate with secure CDB originators;
b) if the security manager is an application client located in the same device as the secure CDB
originators, the security manager shall communicate to the enforcement manager via the SCSI
domain's service delivery subsystem, and the security manager may communicate with the secure
CDB originators by means outside the scope of this standard; and
c) if the security manager is a device server located in the same device as the secure CDB processor,
the security manager shall communicate to the secure CDB originators via the SCSI domain's service
delivery subsystem, and the security manager may communicate with the enforcement manager by
means outside the scope of this standard.

The security manager's device server is called the CbCS management device server (see 5.13.6.7.3). The
security manager's application client is called the CbCS management application client (see 5.13.6.7.4).

If the security manager is a SCSI device, the security manager shall perform CbCS management using the
CbCS management device server and the CbCS management application client as follows:

a) the CbCS management device server (see 5.13.6.7.3) provides access policy controls to secure CDB
originators using policy-coordinated CbCS capabilities; and
b) the CbCS management application client (see 5.13.6.7.4) prevents unsecured access to a logical unit
or a volume (see SSC-4) in concert with:
A) the CbCS management device server (see 5.13.6.7.3);
B) the enforcement manager; and
C) the secure CDB processor.

198 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

CbCS management is confined to the CbCS management application client and CbCS management device
server. The communication of CbCS management information may occur in a manner outside the scope of
this standard.

5.13.6.7.3 CbCS Management Device Server class

5.13.6.7.3.1 CbCS Management Device Server class overview

The CbCS Management Device Server class returns a CbCS capability and a CbCS capability key (i.e.,
Capability-Key) with each CbCS credential giving the secure CDB originator access to:

a) a specific logical unit; or

b) if requested, a specific volume mounted in a specific logical unit (see SSC-4).

This standard defines the RECEIVE CREDENTIAL command (see 6.26) that the secure CDB originator may
use to request a CbCS capability and a CbCS capability key from a CbCS management device server.

Commands to and responses from the CbCS management device server are protected by use of an SA
whose creation included the Authentication Step (see 6.26).

The CbCS management device server shall set the CBCS bit to zero in any Extended INQUIRY Data VPD
page (see 7.8.7) that it returns.

5.13.6.7.3.2 Decision Database attribute

The Decision Database attribute is used to obtain the authorization information required for deciding the type
and duration of access granted to a secure CDB originator for a given logical unit or volume (see SSC-4)
within a SCSI target device. CbCS Credentials are prepared by the CbCS management device server based
on the contents of that Decision Database attribute.

5.13.6.7.4 CbCS Management Application Client class

The CbCS Management Application Client class exchanges shared keys (see 5.13.6.7.11) with and sends
CbCS parameters (see 5.13.6.7.15) to the enforcement manager using SECURITY PROTOCOL OUT
commands (see 6.41) and SECURITY PROTOCOL IN commands (see 6.40) transferred over the SCSI
domain’s service delivery subsystem.

The CbCS capability keys are computed by the CbCS management device server using shared keys that are
shared between:

a) the enforcement manager;

b) the CbCS management application client; and
c) the CbCS management device server.

The shared keys are managed by the security manager.

5.13.6.7.5 Secure CDB Originator class

The Secure CDB Originator class requests CbCS capabilities and CbCS capability keys from the CbCS
management device server for a specific logical unit or volume (see SSC-4). The secure CDB originator
sends the CbCS capability and integrity check value to the logical unit's secure CDB processor as part of a
CbCS extended CDB as described in 5.13.6.7.16.

For more information on the Secure CDB Originator class see 5.13.6.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 199

T10/BSR INCITS 513 Revision 37 17 May 2014

5.13.6.7.6 Secure CDB Processor class

The Secure CDB Processor class:

a) receives a CbCS capability descriptor (see 6.26.2.3) from a secure CDB originator in a CbCS
extension descriptor (see 5.13.6.7.16);
b) requests the SCSI command be validated by the enforcement manager; and
c) if the Enforcement Manager validates the SCSI command, then the secure CDB processor processes
that SCSI command.

The secure CDB processor indicates that CbCS is applied to a logical unit by setting the CBCS bit to one in the
Extended INQUIRY Data VPD page (see 7.8.7). If the CBCS bit is set to one, the logical unit shall support the
following:

a) Extended CDBs (see 4.2.4);

b) CbCS extension type (see 5.13.6.7.16);
c) SECURITY PROTOCOL IN commands (see 6.40) specifying the CbCS security protocol (see 7.7.4);
and
d) SECURITY PROTOCOL OUT commands (see 6.41) specifying the CbCS security protocol (see
7.7.4).

For more information on the Secure CDB Processor class see 5.13.6.3.

5.13.6.7.7 Enforcement Manager class

The Enforcement Manager class:

a) receives shared keys (see 5.13.6.7.11) and CbCS parameters (see 5.13.6.7.15) from the CbCS
management application client;
b) authenticates the CbCS capability received from a secure CDB processor with an integrity check
value as described in 5.13.6.7.13.2;
c) validates SCSI commands sent by secure CDB originators as described in 5.13.6.7.13.2; and
d) if the CAPKEY CbCS method (see 5.13.6.7.8.3) is supported, supplies one security token (see
5.13.6.7.10) for each active I_T nexus to the secure CDB processor for delivery to the secure CDB
originator that is using that I_T nexus.

The enforcement manager may be contained within the secure CDB processor or within the SCSI target
device. If the enforcement manager is contained within the secure CDB processor, the shared keys and CbCS
parameters the enforcement manager uses pertain to that logical unit. If the enforcement manager is
contained within the SCSI target device, the shared keys and CbCS parameters the enforcement manager
uses pertain to the SCSI target device, and the SECURITY PROTOCOL well-known logical unit (see 8.5) is
used for the commands to exchange shared keys and set CbCS parameters.

If a shared key is stored in a well known logical unit then that key is shared between all logical units within the
SCSI target device but shall only used by a logical unit if there has been no shared key assigned to that logical
unit (i.e., a shared key assigned to a logical unit always overrides any shared key assigned to a well known
logical unit).

For more information on the Enforcement Manager class see 5.13.6.4.

200 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.13.6.7.8 CbCS methods

5.13.6.7.8.1 Overview

The CbCS methods defined by this standard are summarized in table 86.

Table 86 — CbCS methods

Level of security provided, including I_T

nexus security provided by SCSI transport
(e.g., FC-SP-2)
Protection provided by the
CbCS enforcement manager and Without With
method secure CDB processor I_T nexus security I_T nexus security
Protection against errors provided by Same protection as is
verifying that the CbCS capability allows No protection against provided by the SCSI
BASIC
processing, but no validation of the attacks transport on the I_T
authenticity of the CbCS capability. nexus
CbCS capability
authenticity assured
Protection against errors and some CbCS capability
and bound to an I_T
attacks by both verifying that the CbCS authenticity assured,
nexus; other network
CAPKEY capability allows processing, and vali- but still subject to net-
attacks (e.g., data pri-
dating the authenticity of the CbCS work attacks (e.g.,
vacy) thwarted by SCSI
capability. replay attacks)
transport security on
the I_T nexus

If a secure CDB processor receives a command for a logical unit that has CbCS enabled, the enforcement
manager shall validate the command as described in 5.13.6.7.13.2 before any other field in the CDB is
validated, including the operation code.

5.13.6.7.8.2 The BASIC CbCS method

The BASIC CbCS method validates that the CbCS capability authorizes the encapsulated command for each
CDB. This method provides centrally-managed policy-driven command access control mechanism that
enforces authorized access based on capabilities.

The BASIC CbCS method does not validate the authenticity of the CbCS capability.

Preparing CbCS credentials for the BASIC CbCS method does not require the knowledge of CbCS shared
keys and may be done by the secure CDB originator without coordination with the CbCS management device
server. In the CbCS extension descriptor (see 5.13.6.7.16):

a) the CbCS capability descriptor (see 6.26.2.3) CBCS METHOD field is set to BASIC;
b) the following CbCS capability descriptor fields are ignored:
A) the KEY VERSION field; and
B) the INTEGRITY CHECK VALUE ALGORITHM field;
and
c) the INTEGRITY CHECK VALUE field is set to zero.

The BASIC CbCS method controls access between the secure CDB originator and the secure CDB processor
without requiring authentication of the secure CDB originator. This method is sufficient for the secure CDB

Working Draft SCSI Primary Commands - 4 (SPC-4) 201

T10/BSR INCITS 513 Revision 37 17 May 2014

processor to request that the enforcement manager verify the CbCS capabilities sent by the secure CDB
originator.

5.13.6.7.8.3 The CAPKEY CbCS method

The CAPKEY CbCS method provides centrally-managed policy-driven command access control mechanism
that enforces authorized access based on capabilities.

In addition, the CAPKEY CbCS method assures the integrity and authenticity of the CbCS capability
transferred with each command.

The CAPKEY CbCS method provides for security of commands delivered to the secure CDB processor.
When used in conjunction with a secure service delivery subsystem, the method provides additional
protection against network attacks (see 5.13.6.7.8.1).

Each capability (see 5.13.6.7.13) is cryptographically associated with a capability key, and the pair is returned
to a secure CDB originator (see 5.13.6.7.5) in a credential (see 5.13.6.7.12) in response to a RECEIVE
CREDENTIAL command (see 6.26).

If the capability is associated with a specific command using a CbCS extension descriptor (see 5.13.6.7.16),
then an integrity check value is computed using the capability key and a CbCS security token (see
5.13.6.7.10). The enforcement manager (see 5.13.6.7.7) validates this integrity check value as described in
5.13.6.7.13.3.

5.13.6.7.9 CbCS trust assumptions

After the logical unit is trusted (i.e., after a secure CDB originator authenticates that it is communicating with a
specific logical unit), the secure CDB originator trusts the secure CDB processor and the enforcement
manager to do the following:

a) deny any access attempt from any application client that is not authorized by the security manager;
and
b) deny access from any application client that does not perform the CbCS protocols and functions
defined by this standard.

The CbCS management device server and the CbCS management application client are trusted after:

a) the CbCS management device server is authenticated by the secure CDB originator; and
b) the CbCS management application client is authenticated by the CbCS Enforcement Manager.

The CbCS management device server and the CbCS management application client are trusted to do the
following:

a) securely store long-lived shared keys and capability keys;

b) grant credentials to secure CDB originators according to access control policies that are outside the
scope of this standard; and
c) perform the defined security functions.

The service delivery subsystem between the secure CDB originator and the secure CDB processor is not
trusted. However, the CbCS security model for CbCS methods other than BASIC is defined so that commands
generated by the secure CDB originator are processed by the secure CDB processor only after the secure
CDB originator interacts with both the CbCS management device server and the secure CDB processor as
defined in this standard.

202 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The communications trust requirements shown in table 87 provide a basis for the CbCS trust assumptions.

Table 87 — CbCS communications trust requirement

CbCS cryptographic communications Requirement

For connections between trust requirements level
secure CDB originator and
Message integrity b Optional a
secure CDB processor
secure CDB originator and
Message confidentiality c and integrity b Mandatory
CbCS management application client
CbCS management application client and
enforcement manager Message integrity b Mandatory

CbCS management application client and

Message confidentiality c and integrity b Mandatory
CbCS management device server
a
If this requirement is not met, then the conditions that table 86 (see 5.13.6.7.8) show for an I_T
nexus without security apply.
b
Message integrity algorithms are those that table 105 (see 5.13.8) describes as integrity checking
(i.e., AUTH) algorithms.
c
Message confidentiality algorithms are those that table 105 (see 5.13.8) describes as encryption
algorithms.

5.13.6.7.10 CbCS security tokens

A CbCS security token is a random nonce that is at least eight bytes in length that is chosen by the
enforcement manager (see 5.13.6.7.7) and returned to a secure CDB originator (see 5.13.6.7.5) by the secure
CDB processor (see 5.13.6.7.6) in response to a SECURITY PROTOCOL IN command (see 6.40) with the
SECURITY PROTOCOL field set to 07h (i.e., CbCS) and the SECURITY PROTOCOL SPECIFIC field set to 3Fh (i.e., the
Security Token CbCS page) as described in 7.7.4.3.4.

The security token shall be unique to each instance of an I_T nexus known to the secure CDB processor and
enforcement manager. Security tokens shall be reset and maintained as described in this subclause.

Each security token shall contain at least as many bytes as the largest cipher block size for all the integrity
checking algorithms supported by the SCSI target device (see 7.7.4.3.3).

If a hard reset, logical unit reset, or I_T nexus loss is detected by the secure CDB processor, the enforcement
manager shall be notified of the event once for each affected I_T nexus. In response to such a notification the
enforcement manager shall discard the security token, if any, associated with the affected I_T nexus.

After a power on, the enforcement manager shall discard all security tokens, if any, that it had been
maintaining before the power on.

In response to a request for a security token for a given I_T nexus from the secure CDB processor, the
enforcement manager shall do one of the following:

a) return the security token value, if any, that is being maintained for the specified I_T nexus to the
secure CDB processor; or
b) if no security token is being maintained for the specified I_T nexus, then:
1) a security token shall be prepared;
2) the security token shall be returned to the secure CDB processor; and

Working Draft SCSI Primary Commands - 4 (SPC-4) 203

T10/BSR INCITS 513 Revision 37 17 May 2014

3) the security token shall be maintained in association with the specified I_T nexus until one of the
events described in this subclause causes it to be discarded.

5.13.6.7.11 CbCS shared keys

5.13.6.7.11.1 Overview

Cryptographic integrity checking for CbCS capabilities depends on the following hierarchy of shared keys that
is specific to the CbCS model:

1) a master key that is composed of:

A) an authentication key; and
B) a generation key;
and
2) up to 16 working keys whose values are generated from the generation key component of the master
key.

Each CbCS shared key set shall support:

a) one master key; and

b) at least two working keys.

Each CbCS shared key in a set has an associated identifier (see 5.13.6.7.11.2) that describes the CbCS
shared key to the objects that are managing it without revealing the CbCS shared key’s value.

Coordinated sets of CbCS shared keys that conform to this hierarchy are maintained by:

a) the CbCS management application client (see 5.13.6.7.4);

b) the CbCS management device server (see 5.13.6.7.3); and
c) the enforcement manager (see 5.13.6.7.7).

The mechanism for coordinating CbCS shared key sets between the CbCS management application client
and the CbCS management device server is outside the scope of this standard.

The following security protocols are provided by this standard for coordinating CbCS shared key sets between
the CbCS management application client and the enforcement manager:

a) a Diffie-Hellman key exchange protocol for changing all the components of the master key (see
5.13.6.7.11.4); and
b) mechanisms that invalidate a working key or set a working key based on the generation key
component of the current master key (see 5.13.6.7.11.5).

These key management protocols associate a key identifier with each shared key (i.e., master key or working
key). The CbCS management application client may use these key identifiers to describe the shared key in
some way (e.g., when the shared key was last refreshed or the intended use of the shared key). Key
identifiers shall not be used to contain shared key values.

Within any SCSI target device that contains an enforcement manager, sets of CbCS shared keys are
maintained as follows:

a) a separate set of per-logical unit CbCS shared keys for a logical unit that has CbCS enabled;
b) one target-wide set of CbCS shared keys that are accessible to all logical units that have CbCS
enabled; or
c) both a target-wide set of CbCS shared keys and per-logical unit sets of CbCS shared keys.

204 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The enforcement manager in any logical unit that has CbCS enabled shall have access to at least one set of
CbCS shared keys.

If an enforcement manager has access to both a target-wide set of CbCS shared keys and a per-logical unit
set of CbCS shared keys, then a working key defined in the per-logical unit set of CbCS shared keys, if any,
shall be used instead of the equivalent working key from the target-wide set of CbCS shared keys.

All CbCS shared keys should be retired from active use (i.e., set, changed, or discarded) often enough to
thwart key attacks. How often to retire CbCS shared keys from active use is outside the scope of this
standard.

The shared keys in a CbCS shared key set and the CbCS pages used to manage them between the CbCS
management application client and the enforcement manager are summarized in table 88.

Table 88 — Summary of CbCS shared keys

Data Capability
CbCS shared key Applicable CbCS page direction protection Reference
a In Working key 7.7.4.3.5
Master Current CbCS Parameters
Authentication, Set Master Key – Seed Exchange Out 7.7.4.5.5
and Set Master Key – Seed Exchange In Authentication 7.7.4.3.6
Generation Out key 7.7.4.5.6
Set Master Key – Change Master Key b
Current CbCS Parameters a In Working key 7.7.4.3.5
Working key Invalidate Key Authentication 7.7.4.5.3
Out
Set Key key 7.7.4.5.4
a
Only key identifiers are returned, not shared key values.
b The new authentication key computed during the seed exchange is the authentication key used for this
CbCS page.

5.13.6.7.11.2 CbCS shared key identifiers

CbCS shared key identifiers (see table 89) are set by the CbCS pages (see table 88 in 5.13.6.7.11.1) that
change the values of a CbCS shared key and reported by the Current CbCS Parameters CbCS page (see
7.7.4.3.5).

Table 89 — CbCS shared key identifier values

Value Description

0000 0000 0000 0000h a The associated CbCS shared key has not been modified since the
SCSI target device was manufactured
0000 0000 0000 0001h to The associated CbCS shared key has a valid value that has been
FFFF FFFF FFFF FFFDh set by the applicable CbCS page
FFFF FFFF FFFF FFFEh a The associated CbCS shared key does not have a valid value
FFFF FFFF FFFF FFFFh a The associated CbCS shared key is not supported
a
The use of this value in the CbCS pages that change CbCS shared key values is reserved.

Working Draft SCSI Primary Commands - 4 (SPC-4) 205

T10/BSR INCITS 513 Revision 37 17 May 2014

5.13.6.7.11.3 Specifying which CbCS shared key to change

The logical unit to which a SECURITY PROTOCOL IN command (see 6.40) or a SECURITY PROTOCOL
OUT command (see 6.41) that specifies one of the CbCS pages shown in table 88 (see 5.13.6.7.11.1) is
addressed determines which CbCS shared key is modified as follows:

a) if the command is addressed to the SECURITY PROTOCOL well known logical unit (see 8.5), then
the CbCS the target-wide (see 5.13.6.7.11.1) set of CbCS shared keys is modified; or
b) if the command is addressed to a logical unit that is not a well known logical unit, then the per-logical
unit (see 5.13.6.7.11.1) set of CbCS shared keys for the specified logical unit are modified.

5.13.6.7.11.4 Updating a CbCS master key

Both components of the CbCS master key (i.e., the authentication key and the generation key) are changed
using a single Diffie-Hellman exchange CCS as summarized in this subclause. Use of the Diffie-Hellman
exchange ensures forward secrecy of the master key.

The CbCS master key update CCS is composed of the following commands:

1) a SECURITY PROTOCOL OUT command processing the Set Master Key – Seed Exchange CbCS
page (see 7.7.4.5.5);
2) a SECURITY PROTOCOL IN command processing the Set Master Key – Seed Exchange CbCS
page (see 7.7.4.3.6); and
3) a SECURITY PROTOCOL OUT command processing the Set Master Key – Change Master Key
CbCS page (see 7.7.4.5.6).

NOTE 18 - The capability key used to access the two Set Master Key – Seed Exchange CbCS pages is
different from the capability key used to access the Set Master Key – Change Master Key CbCS page (see
5.13.6.7.12.3).

The device server shall maintain CCS state for only one CbCS master key update CCS for all I_T nexuses.
The device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to COMMAND SEQUENCE ERROR, if any of the
following conditions occur:

a) a command attempts to start a new CbCS master key update CCS while state is being maintained for
another; or
b) a sequence of CbCS master key update CCS commands other than the one shown in this subclause
is attempted.

The device server shall discard the CbCS master key update CCS state if any of the following occur:

a) a command in the CCS does not complete with GOOD status; or

b) the entire CbCS master key update CCS command sequence shown in this subclause is not
completed within ten seconds of the successful completion of processing for the SECURITY
PROTOCOL OUT command for the Set Master Key – Seed Exchange CbCS page.

5.13.6.7.11.5 Changing a CbCS working keys

A working key is invalidated using the Invalidate Key CbCS page (see 7.7.4.5.3) and set to a new value using
the Set Key CbCS page (see 7.7.4.5.4).

New working keys are computed based on the applicable master key and a random number seed.

206 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Working keys are tracked using CbCS shared key identifiers (see 5.13.6.7.11.2).

5.13.6.7.12 CbCS credentials

5.13.6.7.12.1 Overview

Each CbCS credential authorizes access to:

a) a logical unit; or
b) a specific volume (see SSC-4) mounted in a specific logical unit.

The applicability of CbCS credentials to the BASIC CbCS method (see 5.13.6.7.8.2) is outside the scope of
this standard.

The format of a CbCS credential is described in 6.26.2.2.

The primary components of a CbCS credential are as follows:

a) a CbCS capability whose format and preparation are described in 5.13.6.7.13; and
b) the CbCS capability key that is an integrity check value that is computed as follows:
A) if the credential is to be sent to a secure CDB originator (see 5.13.6.7.5), the CbCS capability key
is computed based on a working key as described in 5.13.6.7.12.2; or
B) if the credential is being prepared for use by the CbCS management application client (see
5.13.6.7.4), then the CbCS capability key is computed based on a working key or the master key
as described in 5.13.6.7.12.3.

Regardless of how it is computed, the CbCS capability key is used as follows:

a) by the secure CDB originator to prepare CbCS extension descriptors (see 5.13.6.7.16) sent to the
secure CDB processor (see 5.13.6.7.6);
b) by the CbCS management application client to prepare CbCS extension descriptors sent to the
enforcement manager (see 5.13.6.7.7); and
c) by the enforcement manager to validate the integrity of capabilities (see 5.13.6.7.13.3) in CbCS
extension descriptors received by the secure CDB processor.

5.13.6.7.12.2 CbCS capability key computations for the secure CDB originator

For credentials sent to the secure CDB originator (see 5.13.6.7.5), the CbCS capability key (see
5.13.6.7.12.1) is computed without knowledge of the command for which the CbCS capability key is being
prepared using the following inputs:

a) the integrity check value algorithm specified by the INTEGRITY CHECK VALUE ALGORITHM field (see
6.26.2.3) in the CbCS capability descriptor; and
b) the following inputs to this integrity check value algorithm:
A) all the bytes in the CbCS capability descriptor (see 6.26.2.3); and
B) the working key specified by the KEY VERSION field (see 6.26.2.3) in the CbCS capability
descriptor.

5.13.6.7.12.3 CbCS capability key computations for general use

The computation of the CbCS capability key depends on the command for which the CbCS capability key is
being computed as described in this subclause. This computation is more general than the computation
described in 5.13.6.7.12.2, but the computation produces the same results because the secure CDB

Working Draft SCSI Primary Commands - 4 (SPC-4) 207

T10/BSR INCITS 513 Revision 37 17 May 2014

originator should not be allowed to use the commands that produce the exceptional cases described in this
subclause.

The CbCS capability key computations described in this subclause are used:

a) for credentials that are to be used by the CbCS management application client (see 5.13.6.7.4); and
b) by the enforcement manager (see 5.13.6.7.7) when validating a CbCS capability descriptor (see
5.13.6.7.13).

When the enforcement manager is validating a CbCS capability descriptor, the command is determined by
inspecting the CDB that is being processed.

Based on the command associated with the credential, the CbCS capability key (see 5.13.6.7.12.1) is
computed using the following inputs:

a) the integrity check value algorithm specified by the INTEGRITY CHECK VALUE ALGORITHM field (see
6.26.2.3) in the CbCS capability descriptor; and
b) the following inputs to this integrity check value algorithm:
A) all the bytes in the CbCS capability descriptor (see 6.26.2.3); and
B) the following CbCS shared key:
a) if the command is a SECURITY PROTOCOL IN command (see 6.40) or a SECURITY
PROTOCOL OUT command (see 6.41) with the SECURITY PROTOCOL field set to 07h (i.e.,
CbCS) and the SECURITY PROTOCOL SPECIFIC field set to a value that is greater than CFFFh,
then the following shared key shall be used:
A) if the command does not access the Set Master Key - Change Key CbCS page (see
7.7.4.5.6), then the authentication key component of the master key (see 5.13.6.7.11) is
used; or
B) if the command accesses the Set Master Key - Change Key CbCS page, then the
authentication key component of the new master key (see 7.7.4.3.6) maintained in the
CbCS master key update CCS (see 5.13.6.7.11.4) is used;
or
b) if the command is not one of those described in step b) B) a), then the working key specified
by the KEY VERSION field (see 6.26.2.3) in the CbCS capability descriptor.

5.13.6.7.13 CbCS capability descriptors

5.13.6.7.13.1 Overview

CbCS capability descriptors are components of:

a) CbCS credentials (see 5.13.6.7.12); and

b) CbCS extension descriptors (see 5.13.6.7.16).

The format of a CbCS capability descriptor is described in 6.26.2.3.

CbCS capability descriptors contain:

a) information about what commands are allowed if the CbCS capability descriptor is associated with a
specific CDB via a CbCS extension descriptor;
b) information that identifies a specific logical unit or a specific volume (see SSC-4) mounted in a
specific logical unit to which the CbCS capability is bound;
c) a time limit on the validity of the CbCS capability descriptor;
d) information that the CbCS management application client (see 5.13.6.7.4) may use to invalidate one
or more CbCS capability descriptors before the time limit expires; and

208 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

e) information that the enforcement manager uses to cryptographically validate the CbCS capability
descriptor, if specified, as described in 5.13.6.7.13.

5.13.6.7.13.2 CbCS extension descriptor validation

The enforcement manager (see 5.13.6.7.7) shall validate the CbCS capability descriptor (see 6.26.2.3)
included in the CbCS extension descriptor (see 5.13.6.7.16). If the validation fails, the enforcement manager
shall interact with the secure CDB processor (see 5.13.6.7.6) in a way that causes the command containing
the CbCS extension descriptor to be terminated with the sense key set to ILLEGAL REQUEST, and the
additional sense code set to INVALID FIELD IN CDB.

The enforcement manager’s validation of a CbCS extension descriptor shall fail if any of the following
conditions occur:

1) a CbCS extension descriptor is not present on a command that table 90 (see 5.13.6.7.14) shows as
requiring a CbCS capability;
2) the command is one that table 90 (see 5.13.6.7.14) shows as never being allowed if CbCS is enabled;
3) the CBCS METHOD field is set to a value that is less than the value in the minimum CbCS method CbCS
parameter (see 5.13.6.7.15);
4) the CBCS METHOD field is set to a value that table 267 defines as reserved (see 6.26.2.3) or a value
that the enforcement manager does not support (see 7.7.4.3.3);
5) if the CBCS METHOD field is set to CAPKEY and the integrity validation described in 5.13.6.7.13.3 fails;
6) the DESIGNATION TYPE field is set to a value that table 266 defines as reserved (see 6.26.2.3);
7) the DESIGNATION TYPE field is set to 1h (i.e., logical unit designation descriptor), and the contents of the
DESIGNATION DESCRIPTOR field in which a logical unit name (see SAM-5) is indicated does not match
the addressed logical unit;
8) the DESIGNATION TYPE field is set to 2h (MAM attribute descriptor) and either of the following are true:
A) the ATTRIBUTE IDENTIFIER field in the DESIGNATION DESCRIPTOR field is set to any value other than
0401h (i.e., MEDIUM SERIAL NUMBER); or
B) the DESIGNATION DESCRIPTOR field contents do not match the MAM attribute of the volume that is
accessible via the addressed logical unit;
9) the CAPABILITY EXPIRATION TIME field is set to a non-zero value and the value in the CAPABILITY
EXPIRATION TIME field is less than (i.e., prior to) the current time in the clock CbCS parameter (see
5.13.6.7.15);
10) the POLICY ACCESS TAG field is set to a non-zero value that does not match the policy access tag CbCS
parameter (see 5.13.6.7.15); or
11) the command in the CDB field of the extended CDB (see 4.2.4) that contains the CbCS extension
descriptor is not allowed by the PERMISSIONS BIT MASK field (see 5.13.6.7.14).

5.13.6.7.13.3 CAPKEY CbCS method capability integrity validation

If the CbCS method is CAPKEY, the enforcement manager’s validation of a CbCS capability descriptor shall
fail the integrity tests if any of the situations described in this subclause occur.

Before attempting to cryptographically validate the integrity of the CbCS capability descriptor, the enforcement
manager shall fail the validation if any of the following conditions occur in the CbCS capability descriptor (see
6.26.2.3):

a) the KEY VERSION field specifies an invalid working key as follows:

A) the command is not a SECURITY PROTOCOL IN command (see 6.40) or a SECURITY
PROTOCOL OUT command (see 6.41) with the SECURITY PROTOCOL field set to 07h (i.e., CbCS)
and the SECURITY PROTOCOL SPECIFIC field set to a value that is greater than CFFFh (i.e., the KEY
VERSION field is ignored for these commands);

Working Draft SCSI Primary Commands - 4 (SPC-4) 209

T10/BSR INCITS 513 Revision 37 17 May 2014

B) the per-logical unit working key (see 5.13.6.7.11), if any, specified by the KEY VERSION field is
invalid (see 5.13.6.7.11.2); and
C) the target-wide working key (see 5.13.6.7.11), if any, specified by the KEY VERSION field is invalid
(see 5.13.6.7.11.2);
or
b) the INTEGRITY CHECK VALUE ALGORITHM field is set to a value that is:
A) not one of those that table 105 (see 5.13.8) lists as being an integrity checking (i.e., AUTH)
algorithm;
B) is AUTH_COMBINED; or
C) is a value that the enforcement manager does not support (see 7.7.4.3.3).

If no integrity checking configuration errors are found in the CbCS capability descriptor, the enforcement
manager shall:

1) compute the CbCS capability key for the CbCS capability descriptor as described in 5.13.6.7.12.3;
and
2) compute the expected contents of CbCS extension descriptor INTEGRITY CHECK VALUE field (see
5.13.6.7.16), using the following inputs:
A) the integrity check value algorithm specified by the INTEGRITY CHECK VALUE ALGORITHM field (see
6.26.2.3) in the CbCS capability descriptor; and
B) the following inputs to this integrity check value algorithm:
a) all the bytes in the security token (see 5.13.6.7.10) for the I_T nexus on which the command
was received as the string for which the integrity check value is to be computed; and
b) the CbCS capability key computed in step 1) as the cryptographic key.

The enforcement manager shall fail the validation if the contents of CbCS extension descriptor INTEGRITY
CHECK VALUE field do not match the computed expected contents of CbCS extension descriptor INTEGRITY
CHECK VALUE field.

5.13.6.7.14 Association between commands and permission bits

The PERMISSIONS BIT MASK field in the CbCS capability (see 6.26.2.3) specifies which commands are allowed
by the CbCS capability. When processing commands with the CbCS extension, the enforcement manager
shall verify that the bits applicable to the encapsulated SCSI command are all set to one in the PERMISSIONS
BIT MASK field before processing the command. The associations between commands and permission bits are

210 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

defined in table 90 and table 91 for commands defined in this standard.

Table 90 — Associations between commands and permissions (part 1 of 2)

PERMISSIONS BIT MASK bits a

DATA DATA PARM PARM SEC
Command READ WRITE READ WRITE MGMT RESRV MGMT
b
ACCESS CONTROL IN never allow
ACCESS CONTROL OUT never allow b
CHANGE ALIASES always allow c
COPY OPERATION ABORT never allow b
EXTENDED COPY(LID4) never allow b
EXTENDED COPY(LID1) never allow b
INQUIRY always allow c
LOG SELECT 1
LOG SENSE 1
MANAGEMENT PROTOCOL IN 1
MANAGEMENT PROTOCOL OUT 1
MODE SELECT(6) 1
MODE SELECT(10) 1
MODE SENSE(6) 1
MODE SENSE(10) 1
PERSISTENT RESERVE IN 1
PERSISTENT RESERVE OUT 1
READ ATTRIBUTE 1
READ BUFFER 1
READ MEDIA SERIAL NUMBER 1
c
RECEIVE COPY DATA(LID4) always allow
RECEIVE COPY DATA(LID1) never allow b
RECEIVE COPY OPERATING PARAMETERS never allow b
RECEIVE COPY FAILURE DETAILS(LID1) never allow b
RECEIVE COPY STATUS(LID4) always allow c
a
The command in the CDB field of the extended CDB (see 4.2.4) that contains the CbCS extension
descriptor shall be allowed only if all of the bits marked with a 1 in the row for that command are set
in the PERMISSIONS BIT MASK field of the CbCS capability in the CbCS extension descriptor. The
permissions bits represented by the empty cells in a row are ignored.
b
If the CBCS bit is set to one in the Extended INQUIRY Data VPD page (see 7.8.7), this command shall
never be allowed.
c
This command shall always be allowed regardless of whether the CbCS extension descriptor is present
and if the CbCS extension descriptor is present regardless of the value in the PERMISSIONS BIT MASK
field.

Working Draft SCSI Primary Commands - 4 (SPC-4) 211

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 90 — Associations between commands and permissions (part 2 of 2)

PERMISSIONS BIT MASK bits a

DATA DATA PARM PARM SEC
Command READ WRITE READ WRITE MGMT RESRV MGMT

RECEIVE COPY STATUS(LID1) never allow b

RECEIVE ROD TOKEN INFORMATION always allow c
RECEIVE CREDENTIAL always allow c
RECEIVE DIAGNOSTIC RESULTS 1
REMOVE I_T NEXUS never allow b
REPORT ALIASES always allow c
REPORT ALL ROD TOKENS always allow c
REPORT IDENTIFYING INFORMATION 1
REPORT LUNS always allow c
REPORT PRIORITY 1
c
REPORT SUPPORTED OPERATION CODES always allow
REPORT SUPPORTED TASK MANAGEMENT
always allow c
FUNCTIONS
REPORT TARGET PORT GROUPS always allow c
REPORT TIMESTAMP 1
REQUEST SENSE 1
SECURITY PROTOCOL IN see table 91
SECURITY PROTOCOL OUT see table 91
SEND DIAGNOSTIC 1
SET IDENTIFYING INFORMATION 1
SET PRIORITY 1
SET TARGET PORT GROUPS 1
SET TIMESTAMP 1 1
c
TEST UNIT READY always allow
WRITE ATTRIBUTE 1
WRITE BUFFER 1
a The command in the CDB field of the extended CDB (see 4.2.4) that contains the CbCS extension
descriptor shall be allowed only if all of the bits marked with a 1 in the row for that command are set
in the PERMISSIONS BIT MASK field of the CbCS capability in the CbCS extension descriptor. The
permissions bits represented by the empty cells in a row are ignored.
b
If the CBCS bit is set to one in the Extended INQUIRY Data VPD page (see 7.8.7), this command shall
never be allowed.
c
This command shall always be allowed regardless of whether the CbCS extension descriptor is present
and if the CbCS extension descriptor is present regardless of the value in the PERMISSIONS BIT MASK
field.

212 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The usage of the PERMISSIONS BIT MASK field for the SECURITY PROTOCOL IN command and the
SECURITY PROTOCOL OUT command depend on the following characteristics as shown in table 91:

a) the contents of the SECURITY PROTOCOL field; and

b) the contents of the SECURITY PROTOCOL SPECIFIC field.

Table 91 — Associations between security protocol commands and permissions

SECURITY
SECURITY PROTOCOL
PROTOCOL SPECIFIC
Command field field Description
SECURITY PROTOCOL IN 00h any Always allowed regardless of whether the CbCS
extension descriptor is present and if the CbCS
SECURITY PROTOCOL IN 07h 0000h to
extension descriptor is present regardless of the
003Fh
value in the PERMISSIONS BIT MASK field
SECURITY PROTOCOL IN 07h 0040h to Allowed only if the CbCS extension descriptor
FFFFh is present and the SEC MGMT bit is set to one in
SECURITY PROTOCOL OUT any any the PERMISSIONS BIT MASK field

Command standards may describe the associations between commands and permission bits for the
commands that they define. The processing requirements for those associations are the same as those
described in this standard.

5.13.6.7.15 CbCS parameters

5.13.6.7.15.1 Overview

CbCS parameters:

a) provide the CbCS Management Application Client class (see 5.13.6.7.4) with a means to control the
operation of the Enforcement Manager class (see 5.13.6.7.7);
b) allow the Secure CDB Processor class (see 5.13.6.7.6) to receive security tokens and other CbCS
information from the Enforcement Manager class; and
c) allow any application client to receive basic operational CbCS information from the Enforcement
Manager class.

CbCS parameters that are not changeable indicate which CbCS features and algorithms are supported. An
application client may retrieve the unchangeable CbCS parameters by using the SECURITY PROTOCOL IN
command to return the Unchangeable CbCS Parameters CbCS page (see 7.7.4.3.3).

Working Draft SCSI Primary Commands - 4 (SPC-4) 213

T10/BSR INCITS 513 Revision 37 17 May 2014

The CbCS parameters with values that change in response to various conditions are summarized in table 92.

Table 92 — Summary of changeable CbCS parameters

Data Capability
Parameter Support Applicable CbCS page direction protection Reference
CbCS parameters that are updated automatically based on I_T nexus
Security token See a Security Token In None 7.7.4.3.4
b
CbCS parameters that provide initial values for dynamically created logical units
Initial minimum Current CbCS Parameters In Working key 7.7.4.3.5
Optional
CbCS method Set Minimum CbCS Method c
Out Working key 7.7.4.5.2
Initial policy Current CbCS Parameters In Working key 7.7.4.3.5
Optional
access tag Set Policy Access Tag d Out Working key 7.7.4.5.1
CbCS parameters that affect the CbCS enforcement manager processing
Minimum CbCS Current CbCS Parameters In Working key 7.7.4.3.5
Mandatory
method Set Minimum CbCS Method c Out Working key 7.7.4.5.2
Policy Access Current CbCS Parameters In Working key 7.7.4.3.5
Mandatory
Tag Set Policy Access Tag d
Out Working key 7.7.4.5.1
Clock Mandatory Current CbCS Parameters In Working key 7.7.4.3.5
CbCS Shared
keys and CbCS
shared key See a see 5.13.6.7.11
identifiers
a
Mandatory if the CAPKEY CbCS method (see 5.13.6.7.8.3) is supported.
b SCSI target devices that do not dynamically create logical units may not implement these CbCS
parameters. Retrieving and setting these CbCS parameters is possible only if the SECURITY
PROTOCOL well known logical unit (see 8.5) is implemented. SCSI target devices that dynamically
create logical units but do not implement the SECURITY PROTOCOL well known logical unit shall
provide a means outside the scope of this standard for managing the values of these CbCS parameters.
c If a Set Minimum CbCS Method CbCS page is processed by the SECURITY PROTOCOL well known

logical unit, then the initial Minimum CbCS Method CbCS parameter is changed. If a Set Minimum
CbCS Method CbCS page is processed by any logical unit other than the SECURITY PROTOCOL well
known logical unit, then the minimum CbCS method CbCS parameter for that logical unit is changed.
d
If a Set Policy Access Tag CbCS page is processed by the SECURITY PROTOCOL well known logical
unit, then the initial policy access tag CbCS parameter is changed. If a Set Policy Access Tag CbCS
page is processed by any logical unit other than the SECURITY PROTOCOL well known logical unit,
then the policy access tag CbCS parameter for that logical unit is changed.

The security token CbCS parameter is described in 5.13.6.7.10.

The minimum CbCS method parameter indicates the minimum allowable CbCS method (see 5.13.6.7.8) to be
used in capabilities (see 6.26.2.3) processed by an enforcement manager (see 5.13.6.7.7). The initial
minimum CbCS method CbCS parameter provides an initial value for the minimum CbCS method CbCS
parameter for dynamically created logical units.

The policy access tag parameter indicates the allowable contents of the POLICY ACCESS TAG field in capabilities
(see 6.26.2.3) processed by an enforcement manager (see 5.13.6.7.7). The initial policy access tag CbCS

214 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

parameter provides an initial value for the policy access tag CbCS parameter for dynamically created logical
units.

The clock CbCS parameter indicates the time used by the enforcement manager (see 5.13.6.7.7) when
evaluating the contents of the CAPABILITY EXPIRATION TIME field in a capability (see 6.26.2.3). The clock CbCS
parameter is the timestamp (see 5.2) and its value is managed using the same mechanisms that are used to
manage a timestamp.

The CbCS shared keys and CbCS shared key identifiers are described in 5.13.6.7.11.

5.13.6.7.16 CbCS extension descriptor format

The CbCS extension descriptor (see table 93) allows the capability-based command security technique (see
5.13.6.7) to be used with a SCSI command via the parameters defined in this subclause. Support for the
CbCS extension descriptor is mandatory if the CBCS bit is set to one in the Extended INQUIRY Data VPD page
(see 7.8.7). If an extended CDB (see 4.2.4) includes a CbCS extension descriptor, the CDB field may contain
any CDB defined in this standard or any command standard.

Table 93 — CbCS extension descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 EXTENSION TYPE (40h)
1
2 Reserved
3
4
•• • CbCS capability descriptor (see 6.26.2.3)
75
76 (MSB)
•• • INTEGRITY CHECK VALUE
139 (LSB)

The EXTENSION TYPE field is defined in 4.2.4.2 and shall be set as shown in table 93 for the CbCS extension
descriptor.

The CbCS capability descriptor is defined in 6.26.2.3.

The contents of INTEGRITY CHECK VALUE field depend on the contents of the CBCS METHOD field in the CbCS
capability descriptor as follows:

a) if the CBCS METHOD field is not set to CAPKEY or a vendor specific value (see table 267 in 6.26.2.3),
then the INTEGRITY CHECK VALUE field is reserved;
b) if the CBCS METHOD field is set to a vendor specific value, then the contents of the INTEGRITY CHECK
VALUE field are vendor specific; or
c) if the CBCS METHOD field is set to CAPKEY, then the INTEGRITY CHECK VALUE field contains an integrity
check value that is computed using the integrity check value algorithm specified by the INTEGRITY
CHECK VALUE ALGORITHM field in the CbCS capability descriptor (see 6.26.2.3) and the following inputs
to the integrity check value algorithm:
A) all the bytes in the security token (see 5.13.6.7.10) for the I_T nexus on which the command is
being sent as the string for which the integrity check value is to be computed; and

Working Draft SCSI Primary Commands - 4 (SPC-4) 215

T10/BSR INCITS 513 Revision 37 17 May 2014

B) the CbCS capability key from the credential (see 5.13.6.7.12) in which the CbCS capability
descriptor was received by the secure CDB originator as the cryptographic key.

The enforcement manager shall validate the CbCS capability descriptor and the INTEGRITY CHECK VALUE field
as described in 5.13.6.7.13.2.

5.13.7 ESP-SCSI encapsulations for parameter data

5.13.7.1 Overview

Subclause 5.13.7 defines a method for transferring encrypted and/or integrity checked parameter data in
Data-In Buffers, Data-Out Buffers, variable length CDBs (see 4.2.3), and extended CDBs (see 4.2.4). This
method is based on the Encapsulating Security Payload (see RFC 4303) standard developed by the IETF.

NOTE 19 - Because of the constrained usage of ESP-SCSI parameter data in Data-In Buffers and/or
Data-Out Buffers, the method defined in this standard differs from the one found in RFC 4303.

5.13.7.2 ESP-SCSI required inputs

Prior to using the ESP-SCSI descriptors defined in 5.13.7, an SA shall be created (see 5.13.2.3) with SA
parameters that conform to the requirements defined in 5.13.2.2 and to the following:

a) the USAGE_TYPE SA parameter shall be set to a value for which ESP-SCSI usage is defined in table
75 (see 5.13.2.2);
b) the USAGE_DATA SA parameter shall contain at least the following:
A) the algorithm identifier and key length for the encryption algorithm (e.g., the ALGORITHM IDENTIFIER
field and KEY LENGTH field from the ENCR IKEv2-SCSI cryptographic algorithm descriptor (see
7.7.3.6.2) in the IKEv2-SCSI SAUT Cryptographic Algorithms payload (see 7.7.3.5.14) negotiated
by an IKEv2-SCSI SA creation protocol (see 5.13.4)); and
B) the algorithm identifier for the integrity algorithm (e.g., the ALGORITHM IDENTIFIER field from the
INTEG IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.4) in the IKEv2-SCSI SAUT
Cryptographic Algorithms payload (see 7.7.3.5.14) negotiated by an IKEv2-SCSI SA creation
protocol (see 5.13.4));
and
c) the KEYMAT SA parameter shall consist of the shared keys described in 5.13.4.8.6.

ESP-SCSI uses the following additional information derived from the contents of the USAGE_DATA SA
parameter:

a) the encryption algorithm identifier shall indicate:

A) the absence of encryption by being set to ENCR_NULL (see table 105 in 5.13.8);
B) the size of the initialization vector, if any (e.g., as shown in table 549 (see 7.7.3.6.2));
C) the size of the salt bytes, if any (e.g., as shown in table 549 (see 7.7.3.6.2)); and
D) for combined mode encryption algorithms, the size of the integrity check value (i.e., the
algorithm's MAC length as shown in table 549 (see 7.7.3.6.2));
and
b) the integrity algorithm identifier shall indicate:
A) the use of a combined mode encryption algorithm being set to AUTH_COMBINED (see table 105
in 5.13.8); and
B) for non-combined mode encryption algorithms, the size of the integrity check value (e.g., as
shown in table 553 (see 7.7.3.6.4)).

216 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Each shared key in KEYMAT shall be derived from the KDF generated bits in the order shown in 5.13.4.8.6.
The size of each of the shared keys in KEYMAT is determined by the negotiated encryption algorithm and
integrity algorithm as described in 5.13.4.4.

5.13.7.3 ESP-SCSI data format before encryption and after decryption

Before data bytes are encrypted and after they are decrypted, they have the format shown in table 94.

Table 94 — ESP-SCSI data format before encryption and after decryption

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • UNENCRYPTED BYTES
p-1
p
•• • PADDING BYTES
j-1
j PAD LENGTH (j-p)
j+1 MUST BE ZERO

The UNENCRYPTED BYTES field contains the bytes that are to be protected via encryption or that have been
decrypted.

Before encryption, the PADDING BYTES field contains zero to 255 bytes. The number of padding bytes is:

a) defined by the encryption algorithm; or

b) the number required to cause the length of all bytes prior to encryption (i.e., j+2) to be a whole
multiple of the alignment (see table 549 in 7.7.3.6.2) for the encryption algorithm being used.

The contents of the padding bytes are:

a) defined by the encryption algorithm; or

b) if the encryption algorithm does not define the padding bytes contents, a series of one byte binary
values starting at one and incrementing by one in each successive byte (i.e., 01h in the first padding
byte, 02h in the second padding byte, etc.).

If the encryption algorithm does not place requirements on the contents of the padding bytes option (i.e.,
option b)), then after decryption the contents of the padding bytes shall be verified to match the series of one
byte binary values described in this subclause. If this verification is not successful in a device server, the
device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, the additional sense code set to INVALID FIELD IN PARAMETER LIST, the SKSV bit set
to one, and SENSE KEY SPECIFIC field set to indicate the last byte in the encrypted data as defined in 4.5.2.4.2.
If this verification is not successful in an application client, the decrypted data should be ignored.

The PAD LENGTH field is set to the number of bytes in the PADDING BYTES field.

The MUST BE ZERO field is set to zero. After decryption, the contents of the MUST BE ZERO field shall be verified
to be zero. If this verification is not successful in a device server, the device server shall terminate the
command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, the additional
sense code set to INVALID FIELD IN PARAMETER LIST, the SKSV bit set to one, and SENSE KEY SPECIFIC field
set to indicate the last byte in the encrypted data as defined in 4.5.2.4.2. If this verification is not successful in

Working Draft SCSI Primary Commands - 4 (SPC-4) 217

T10/BSR INCITS 513 Revision 37 17 May 2014

an application client, the decrypted data should be ignored.

5.13.7.4 ESP-SCSI outbound data descriptors

5.13.7.4.1 Overview

If ESP-SCSI is used in a variable length CDB (see 4.2.3), an extended CDB (see 4.2.4), or parameter list data
that appears in a Data-Out Buffer, then the parameter list data contains one or more descriptors selected
based on the criteria shown in table 95.

Table 95 — ESP-SCSI outbound data descriptors

External Initialization
descriptor vector
Descriptor name length a present b Reference
No No 5.13.7.4.2.1
ESP-SCSI CDB
No Yes 5.13.7.4.2.2
No No 5.13.7.4.2.1
ESP-SCSI Data-Out Buffer
No Yes 5.13.7.4.2.2
ESP-SCSI Data-Out Buffer Yes No 5.13.7.4.3.1
without length Yes Yes 5.13.7.4.3.2
a
Yes means the data format defined for the Data-Out Buffer parameter data
includes a length for the ESP-SCSI descriptor.
b
See the USAGE_DATA SA parameter description in 5.13.7.2 for more
information about the initialization vector.

5.13.7.4.2 ESP-SCSI CDBs or Data-Out Buffer parameter lists including a descriptor length

5.13.7.4.2.1 Initialization vector absent

If the USAGE_DATA SA parameter (see 5.13.7.2) indicates an encryption algorithm whose initialization vector
size is zero, then the variable length CDB (see 4.2.3), extended CDB (see 4.2.4), or Data-Out Buffer

218 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

parameter list descriptor shown in table 96 contains the ESP-SCSI data.

Table 96 — ESP-SCSI CDBs or Data-Out Buffer parameter list descriptor without initialization vector

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
DESCRIPTOR LENGTH (n-1)
1 (LSB)
2
Reserved
3
4 (MSB)
•• • DS_SAI
7 (LSB)
8 (MSB)
•• • DS_SQN
15 (LSB)
16
•• • ENCRYPTED OR AUTHENTICATED DATA
i-1
i (MSB)
•• • INTEGRITY CHECK VALUE
n (LSB)

The DESCRIPTOR LENGTH field specifies the number of bytes that follow in the ESP-SCSI CDB or ESP-SCSI
Data-Out Buffer parameter list descriptor.

The DS_SAI field is set to the value in the DS_SAI SA parameter (see 5.13.2.2) for the SA that is being used to
prepare the ESP-SCSI CDB or ESP-SCSI Data-Out Buffer parameter list descriptor. If the DS_SAI value is not
known to the device server, the device server shall terminate the command with CHECK CONDITION status,
with the sense key set to ILLEGAL REQUEST, the additional sense code set to INVALID FIELD IN
PARAMETER LIST, the SKSV bit set to one, and SENSE KEY SPECIFIC field set as defined in 4.5.2.4.2.

The DS_SQN field should be set to one plus the value in the application client’s DS_SQN SA parameter (see
5.13.2.2) for the SA that is being used to prepare the ESP-SCSI CDB or ESP-SCSI Data-Out Buffer
parameter list descriptor. Before sending the ESP-SCSI CDB or ESP-SCSI Data-Out Buffer parameter list, the
application client should copy the contents of the DS_SQN field to its DS_SQN SA parameter.

The device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, the additional sense code set to INVALID FIELD IN PARAMETER LIST, the SKSV bit set
to one, and SENSE KEY SPECIFIC field set as defined in 4.5.2.4.2 if any of the following conditions occur:

a) the DS_SQN field is set to zero;

b) the value in the DS_SQN field is less than or equal to the value in the device server’s DS_SQN SA
parameter; or
c) the value in the DS_SQN field is greater than 32 plus the value in the device server’s DS_SQN SA
parameter.

If the DS_SQN SA parameter is equal to FFFF FFFF FFFF FFFFh, the device server shall delete the SA.

Working Draft SCSI Primary Commands - 4 (SPC-4) 219

T10/BSR INCITS 513 Revision 37 17 May 2014

The INITIALIZATION VECTOR field, if any, contains a value that is used as an input into the encryption algorithm
and/or integrity algorithm specified by the SA specified by the DS_SAI field. The INITIALIZATION VECTOR field is
not encrypted. The encryption algorithm and/or integrity algorithm may define additional requirements for the
INITIALIZATION VECTOR field.

The ENCRYPTED OR AUTHENTICATED DATA field contains:

a) if an encryption algorithm for the SA specified by the DS_SAI field is not ENCR_NULL, encrypted data
bytes for the following:
1) the bytes in the UNENCRYPTED BYTES field (see 5.13.7.3);
2) the bytes in the PADDING BYTES field (see 5.13.7.3);
3) the byte that is the PAD LENGTH field (see 5.13.7.3); and
4) the byte that is the MUST BE ZERO field (see 5.13.7.3);
or
b) otherwise, the unencrypted data bytes.

If the integrity algorithm for the SA specified by the DS_SAI field is AUTH_COMBINED (see 5.13.7.2), then the
AAD input to the encryption algorithm is composed of the following concatenated bytes:

1) the bytes in the DS_SAI field; and

2) the bytes in the DS_SQN field.

The INTEGRITY CHECK VALUE field contains a value that is computed as follows:

a) if the integrity algorithm is not AUTH_COMBINED, the integrity check value is computed using the
specified integrity algorithm with the following concatenated bytes as inputs:
1) the bytes in the DS_SAI field;
2) the bytes in the DS_SQN field;
3) the bytes in the INITIALIZATION VECTOR field, if any; and
4) the bytes in the ENCRYPTED OR AUTHENTICATED DATA field after encryption, if any, has been
performed;
or
b) if the integrity algorithm is AUTH_COMBINED, the integrity check value is computed as an additional
output of the specified encryption algorithm.

Upon receipt of ESP-SCSI CDB or ESP-SCSI Data-Out Buffer parameter data, the device server shall
compute an integrity check value for the ESP-SCSI CDB or ESP-SCSI Data-Out Buffer parameter data as
specified by the algorithms specified by the SA specified by the DS_SAI field using the inputs shown in this
subclause. If the computed integrity check value does not match the value in the INTEGRITY CHECK VALUE field,
the device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, the additional sense code set to INVALID FIELD IN PARAMETER LIST, the SKSV bit set
to one, and SENSE KEY SPECIFIC field set as defined in 4.5.2.4.2.

If the command is not terminated due to a sequence number error or a mismatch between the computed
integrity check value and the contents of the INTEGRITY CHECK VALUE field, then the device server shall copy
the contents of the received DS_SQN field to its DS_SQN SA parameter.

5.13.7.4.2.2 Initialization vector present

If the USAGE_DATA SA parameter indicates an encryption algorithm whose initialization vector size (i.e., s) is
greater than zero, then the variable length CDB (see 4.2.3), extended CDB (see 4.2.4), or Data-Out Buffer

220 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

parameter data descriptor shown in table 97 contains the ESP-SCSI data.

Table 97 — ESP-SCSI CDBs or Data-Out Buffer full parameter list descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
DESCRIPTOR LENGTH (n-1)
1 (LSB)
2
Reserved
3
4 (MSB)
•• • DS_SAI
7 (LSB)
8 (MSB)
•• • DS_SQN
15 (LSB)
16 (MSB)
•• • INITIALIZATION VECTOR
16+s-1 (LSB)
16+s
•• • ENCRYPTED OR AUTHENTICATED DATA
i-1
i (MSB)
•• • INTEGRITY CHECK VALUE
n (LSB)

The DESCRIPTOR LENGTH field, DS_SAI field, DS_SQN field, ENCRYPTED OR AUTHENTICATED DATA field, and
INTEGRITY CHECK VALUE field are defined in 5.13.7.4.2.1.

Working Draft SCSI Primary Commands - 4 (SPC-4) 221

T10/BSR INCITS 513 Revision 37 17 May 2014

5.13.7.4.3 ESP-SCSI Data-Out Buffer parameter lists for externally specified descriptor length

5.13.7.4.3.1 Initialization vector absent

If the USAGE_DATA SA parameter (see 5.13.7.2) indicates an encryption algorithm whose initialization vector
size is zero and the length of the ESP-SCSI Data-Out Buffer parameter list descriptor is specified in the same
parameter list that contains the descriptor, then the Data-Out Buffer parameter list descriptor shown in table
98 contains the ESP-SCSI data.

Table 98 — ESP-SCSI Data-Out Buffer parameter list descriptor without length and initialization vector

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • Reserved
3
4 (MSB)
•• • DS_SAI
7 (LSB)
8 (MSB)
•• • DS_SQN
15 (LSB)
16
•• • ENCRYPTED OR AUTHENTICATED DATA
i-1
i (MSB)
•• • INTEGRITY CHECK VALUE
n (LSB)

The DS_SAI field, DS_SQN field, ENCRYPTED OR AUTHENTICATED DATA field, and INTEGRITY CHECK VALUE field are
defined in 5.13.7.4.2.1.

222 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.13.7.4.3.2 Initialization vector present

If the USAGE_DATA SA parameter indicates an encryption algorithm whose initialization vector size (i.e., s) is
greater than zero and the length of the ESP-SCSI Data-Out Buffer parameter list descriptor is specified in the
same parameter list that contains the descriptor, then the Data-Out Buffer parameter list descriptor shown in
table 99 contains the ESP-SCSI data.

Table 99 — ESP-SCSI Data-Out Buffer parameter list descriptor without length

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • Reserved
3
4 (MSB)
•• • DS_SAI
7 (LSB)
8 (MSB)
•• • DS_SQN
15 (LSB)
16 (MSB)
•• • INITIALIZATION VECTOR
16+s-1 (LSB)
16+s
•• • ENCRYPTED OR AUTHENTICATED DATA
i-1
i (MSB)
•• • INTEGRITY CHECK VALUE
n (LSB)

The DS_SAI field, DS_SQN field, INITIALIZATION VECTOR field, ENCRYPTED OR AUTHENTICATED DATA field, and
INTEGRITY CHECK VALUE field are defined in 5.13.7.4.2.1.

5.13.7.5 ESP-SCSI Data-In Buffer parameter data descriptors

5.13.7.5.1 Overview

A device server shall transfer ESP-SCSI parameter data descriptors in a Data-In Buffer only in response to a
request that specifies an SA using the AC_SAI SA parameter and DS_SAI SA parameter values (see
5.13.2.2). If the specified combination of AC_SAI and DS_SAI values in a command that requests the transfer
of ESP-SCSI parameter data descriptors is not known to the device server, then the device server shall
terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, the
additional sense code set to INVALID FIELD IN PARAMETER LIST or to INVALID FIELD IN CDB, the SKSV bit
set to one, and SENSE KEY SPECIFIC field set as defined in 4.5.2.4.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 223

T10/BSR INCITS 513 Revision 37 17 May 2014

If ESP-SCSI is used in parameter data which appears in a Data-In Buffer, the parameter data contains one or
more descriptors selected based on the criteria shown in table 100.

Table 100 — ESP-SCSI Data-In Buffer parameter data descriptors

External Initialization
descriptor vector
Descriptor name length a present b Reference
No No 5.13.7.5.2.1
ESP-SCSI Data-In Buffer
No Yes 5.13.7.5.2.2
ESP-SCSI Data-In Buffer Yes No 5.13.7.5.3.1
without length Yes Yes 5.13.7.5.3.2
a
Yes means the data format defined for the Data-Out Buffer parameter data
includes a length for the ESP-SCSI descriptor.
b
See the USAGE_DATA SA parameter description in 5.13.7.2 for more
information about the initialization vector.

If ESP-SCSI parameter data descriptors are used in a Data-In Buffer, then the outbound data (see 5.13.7.4)
should include at least one ESP-SCSI descriptor using the same SA.

224 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.13.7.5.2 ESP-SCSI Data-In Buffer parameter data including a descriptor length

5.13.7.5.2.1 Initialization vector absent

If the USAGE_DATA SA parameter (see 5.13.7.2) indicates an encryption algorithm whose initialization vector
size is zero, then the Data-In Buffer parameter data descriptor shown in table 101 contains the ESP-SCSI
data.

Table 101 — ESP-SCSI Data-In Buffer parameter data descriptor without initialization vector

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
DESCRIPTOR LENGTH (n-1)
1 (LSB)
2
Reserved
3
4 (MSB)
•• • AC_SAI
7 (LSB)
8 (MSB)
•• • AC_SQN
15 (LSB)
16
•• • ENCRYPTED OR AUTHENTICATED DATA
i-1
i (MSB)
•• • INTEGRITY CHECK VALUE
n (LSB)

The DESCRIPTOR LENGTH field specifies the number of bytes that follow in the ESP-SCSI Data-In Buffer
parameter data descriptor.

The AC_SAI field is set to the value in the AC_SAI SA parameter (see 5.13.2.2) for the SA that is being used to
prepare the ESP-SCSI Data-In Buffer parameter data descriptor. If the AC_SAI value is not known to the
application client, the ESP-SCSI data-in parameter data descriptor should be ignored.

The AC_SQN field is set to one plus the value in the device server’s AC_SQN SA parameter (see 5.13.2.2) for
the SA that is being used to prepare the ESP-SCSI data-on buffer parameter data descriptor. Before sending
the ESP-SCSI Data-Out Buffer parameter list as part of a command that completes with GOOD status, the
device server shall copy the contents of the AC_SQN field to its AC_SQN SA parameter. The device server
shall not send two ESP-SCSI Data-Out Buffer parameter data descriptors that contain the same values in
AC_SAI field and AC_SQN field.

If the AC_SQN SA parameter is equal to FFFF FFFF FFFF FFFFh, the device server shall delete the SA after
the Data-In Buffer parameter data containing that value is sent.

Working Draft SCSI Primary Commands - 4 (SPC-4) 225

T10/BSR INCITS 513 Revision 37 17 May 2014

The application client should ignore the ESP-SCSI data-in parameter data descriptor if any of the following
occur:

a) the AC_SQN field is set to zero;

b) the value in the AC_SQN field is less than or equal to the value in the application client’s AC_SQN SA
parameter; or
c) the value in the AC_SQN field is greater than 32 plus the value in the application client’s AC_SQN SA
parameter.

The INITIALIZATION VECTOR field, if any, contains a value that is used as an input into the encryption algorithm
and/or integrity algorithm specified by the SA specified by the AC_SAI field. The INITIALIZATION VECTOR field is
not encrypted. The encryption algorithm and/or integrity algorithm may define additional requirements for the
INITIALIZATION VECTOR field.

The ENCRYPTED OR AUTHENTICATED DATA field contains:

a) if an encryption algorithm for the SA specified by the AC_SAI field is not ENCR_NULL, encrypted data
bytes for the following:
1) the bytes in the UNENCRYPTED BYTES field (see 5.13.7.3);
2) the bytes in the PADDING BYTES field (see 5.13.7.3);
3) the byte that is the PAD LENGTH field (see 5.13.7.3); and
4) the byte that is the MUST BE ZERO field (see 5.13.7.3);
or
b) otherwise, the unencrypted data bytes.

If the integrity algorithm for the SA specified by the AC_SAI field is AUTH_COMBINED (see 5.13.7.2), then the
AAD input to the encryption algorithm is composed of the following concatenated bytes:

1) the bytes in the AC_SAI field; and

2) the bytes in the AC_SQN field;

The INTEGRITY CHECK VALUE field contains a value that is computed as follows:

a) if the integrity algorithm is not AUTH_COMBINED, the integrity check value is computed using the
specified integrity algorithm with the following concatenated bytes as inputs:
1) the bytes in the AC_SAI field;
2) the bytes in the AC_SQN field;
3) the bytes in the INITIALIZATION VECTOR field, if any; and
4) the bytes in the ENCRYPTED OR AUTHENTICATED DATA field after encryption, if any, has been
performed;
or
b) if the integrity algorithms is AUTH_COMBINED, the integrity check value is computed as an additional
output of the specified encryption algorithm.

Upon receipt of ESP-SCSI Data-In Buffer parameter data, the application client should compute an integrity
check value for the ESP-SCSI parameter data as specified by the algorithms specified by the SA specified by
the AC_SAI field using the inputs shown in this subclause. If the computed integrity check value does not match
the value in the INTEGRITY CHECK VALUE field, the results returned by the command should be ignored.

The application client should copy the contents of the AC_SQN field to its AC_SQN SA parameter if all of the
following occur:

a) the command completed with GOOD status;

226 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

b) the ESP-SCSI data-in parameter data descriptor was not ignored due to inconsistency problems with
the AC_SQN field; and
c) the computed integrity check value matched the contents of the INTEGRITY CHECK VALUE field.

5.13.7.5.2.2 Initialization vector present

If the USAGE_DATA SA parameter indicates an encryption algorithm whose initialization vector size (i.e., s) is
greater than zero, then the Data-In Buffer parameter data descriptor shown in table 102 contains the
ESP-SCSI data.

Table 102 — ESP-SCSI Data-In Buffer full parameter data descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
DESCRIPTOR LENGTH (n-1)
1 (LSB)
2
Reserved
3
4 (MSB)
•• • AC_SAI
7 (LSB)
8 (MSB)
•• • AC_SQN
15 (LSB)
16 (MSB)
•• • INITIALIZATION VECTOR
16+s-1 (LSB)
16+s
•• • ENCRYPTED OR AUTHENTICATED DATA
i-1
i (MSB)
•• • INTEGRITY CHECK VALUE
n (LSB)

The DESCRIPTOR LENGTH field, AC_SAI field, AC_SQN field, ENCRYPTED OR AUTHENTICATED DATA field, and
field are defined in 5.13.7.5.2.1.
INTEGRITY CHECK VALUE

Working Draft SCSI Primary Commands - 4 (SPC-4) 227

T10/BSR INCITS 513 Revision 37 17 May 2014

5.13.7.5.3 ESP-SCSI Data-In Buffer parameter data for externally specified descriptor length

5.13.7.5.3.1 Initialization vector absent

If the USAGE_DATA SA parameter (see 5.13.7.2) indicates an encryption algorithm whose initialization vector
size is zero and the length of the ESP-SCSI Data-In Buffer parameter data descriptor is specified in the same
parameter data that contains the descriptor, then the Data-In Buffer parameter data descriptor shown in table
103 contains the ESP-SCSI data.

Table 103 — ESP-SCSI Data-In Buffer parameter data descriptor without length and initialization
vector

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • Reserved
3
4 (MSB)
•• • AC_SAI
7 (LSB)
8 (MSB)
•• • AC_SQN
15 (LSB)
16
•• • ENCRYPTED OR AUTHENTICATED DATA
i-1
i (MSB)
•• • INTEGRITY CHECK VALUE
n (LSB)

The AC_SAI field, AC_SQN field, ENCRYPTED OR AUTHENTICATED DATA field, and INTEGRITY CHECK VALUE field are
defined in 5.13.7.5.2.1.

228 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.13.7.5.3.2 Initialization vector present

If the USAGE_DATA SA parameter indicates an encryption algorithm whose initialization vector size (i.e., s) is
greater than zero and the length of the ESP-SCSI Data-In Buffer parameter data descriptor is specified in the
same parameter data that contains the descriptor, then the Data-In Buffer parameter data descriptor shown in
table 104 contains the ESP-SCSI data.

Table 104 — ESP-SCSI Data-In Buffer parameter data descriptor without length

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • Reserved
3
4 (MSB)
•• • AC_SAI
7 (LSB)
8 (MSB)
•• • AC_SQN
15 (LSB)
16 (MSB)
•• • INITIALIZATION VECTOR
16+s-1 (LSB)
16+s
•• • ENCRYPTED OR AUTHENTICATED DATA
i-1
i (MSB)
•• • INTEGRITY CHECK VALUE
n (LSB)

The AC_SAI field, AC_SQN field, INITIALIZATION VECTOR field, ENCRYPTED OR AUTHENTICATED DATA field, and
INTEGRITY CHECK VALUE field are defined in 5.13.7.5.2.1.

Working Draft SCSI Primary Commands - 4 (SPC-4) 229

T10/BSR INCITS 513 Revision 37 17 May 2014

5.13.8 Security algorithm codes

Table 105 lists the security algorithm codes used in security protocol parameter data.

Table 105 — Security algorithm codes (part 1 of 2)

Code Description Reference

Encryption algorithms
0001 000Ch CBC-AES-256-HMAC-SHA-1 IEEE 1619.1
0001 0010h CCM-128-AES-256 IEEE 1619.1
0001 0014h GCM-128-AES-256 IEEE 1619.1
0001 0016h XTS-AES-256-HMAC-SHA-512 IEEE 1619.1
8001 000Bh a ENCR_NULL 7.7.3.6.2
8001 000Ch a AES-CBC RFC 3602
a
8001 0010h AES-CCM with a 16-byte MAC RFC 4309
a
8001 0014h AES-GCM with a 16-byte MAC RFC 4106
8001 0400h to Vendor specific
8001 FFFFh
PRF and KDF algorithms b
8002 0002h a IKEv2-use based on SHA-1
8002 0004h a IKEv2-use based on AES-128 in CBC mode table 551
8002 0005h a
IKEv2-use based on SHA-256 (see 7.7.3.6.3)
a
8002 0007h IKEv2-use based on SHA-512
8002 0400h to Vendor specific
8002 FFFFh
Integrity checking (i.e., AUTH) algorithms
8003 0002h a AUTH_HMAC_SHA1_96 RFC 2404
a
8003 000Ch AUTH_HMAC_SHA2_256_128 RFC 4868
a
8003 000Eh AUTH_HMAC_SHA2_512_256 RFC 4868
F003 0000h AUTH_COMBINED 7.7.3.6.4
8003 0400h to Vendor specific
8003 FFFFh
a The lower order 16 bits of this code value are assigned to match an IANA assigned value, if any, for an
equivalent IKEv2 encryption algorithm and values of 800xh in the high order 16 bits have x selected to
match the IANA assigned IKEv2 transform type (e.g., 8001h – Encryption Algorithms, 8002h – PRFs
and KDFs).
b
PRFs are equivalent to the prf() functions defined in RFC 4306. KDFs are equivalent to the prf+()
functions defined in RFC 4306.
c
The low order 8 bits of this code value are assigned to match the AUTH METHOD field in the
Authentication payload (see 7.7.3.5.7).

230 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 105 — Security algorithm codes (part 2 of 2)

Code Description Reference

Diffie-Hellman algorithms
a
8004 000Eh 2 048-bit MODP group (finite field D-H) RFC 3526
8004 000Fh a 3 072-bit MODP group (finite field D-H) RFC 3526
8004 0010h a 4 096-bit MODP group (finite field D-H) RFC 3526
a
8004 0013h 256-bit random ECP group RFC 4753
8004 0015h a 521-bit random ECP group RFC 4753
8004 0400h to Vendor specific
8004 FFFFh
SA Authentication payload authentication algorithms
00F9 0000h c SA_AUTH_NONE 5.13.4.3.4 and 7.7.3.6.6
c
00F9 0001h RSA Digital Signature with SHA-1 RFC 4306
c
00F9 0002h Shared Key Message Integrity Code RFC 4306
00F9 0009h c ECDSA with SHA-256 on the P-256 curve RFC 4754
c
00F9 000Bh ECDSA with SHA-512 on the P-521 curve RFC 4754
00F9 00C9h to Vendor specific
00F9 00FFh
Other algorithms
0000 0000h to Restricted IANA
0000 FFFFh
All other values Reserved
a
The lower order 16 bits of this code value are assigned to match an IANA assigned value, if any, for an
equivalent IKEv2 encryption algorithm and values of 800xh in the high order 16 bits have x selected to
match the IANA assigned IKEv2 transform type (e.g., 8001h – Encryption Algorithms, 8002h – PRFs
and KDFs).
b
PRFs are equivalent to the prf() functions defined in RFC 4306. KDFs are equivalent to the prf+()
functions defined in RFC 4306.
c
The low order 8 bits of this code value are assigned to match the AUTH METHOD field in the
Authentication payload (see 7.7.3.5.7).

5.14 Self-test operations

5.14.1 Self-test types

The SEND DIAGNOSTIC command (see 6.42) provides methods for an application client to request that a
SCSI target device perform self test operations. This standard defines the following self-tests:

a) the default self-test (see 5.14.2);

b) the short self-test (see 5.14.3); and
c) the extended self-test (see 5.14.3).

Working Draft SCSI Primary Commands - 4 (SPC-4) 231

T10/BSR INCITS 513 Revision 37 17 May 2014

5.14.2 Default self-test

The default self-test is mandatory for all SCSI target device types that support the SEND DIAGNOSTIC
command. The operations performed for the default self-test are not defined by this standard (e.g., performing
no diagnostics and returning GOOD status is a valid default self-test). An application client requests that a
SCSI target device perform a default self-test by setting the SELFTEST bit to one in the SEND DIAGNOSTIC
command (see 6.42).

An application client may use the DEVOFFL bit and the UNITOFFL bit in the SEND DIAGNOSTIC command to
allow the device server to perform operations during a default self-test that affect conditions for one or more
logical units in the SCSI target device (e.g., if the DEVOFFL bit is set to one, then the device server may clear
established reservations while performing the test, and if the UNITOFFL bit is set to one, then the logical unit
may alter its medium while performing the test).

While a SCSI target device is performing a default self-test, the device server shall terminate all commands,
except INQUIRY commands, REPORT LUNS commands, and REQUEST SENSE commands, with CHECK
CONDITION status with the sense key set to NOT READY and the additional sense code set to LOGICAL
UNIT NOT READY, SELF-TEST IN PROGRESS. If the device server receives an INQUIRY command, a
REPORT LUNS command, or a REQUEST SENSE command while performing a default self-test, then the
device server shall process the command.

If the SCSI target device detects no errors during a default self-test, then the device server shall complete the
command with GOOD status. If the SCSI target device detects an error during the test, then the device server
shall terminate the command with CHECK CONDITION status with the sense key set to HARDWARE
ERROR and the additional sense code set to indicate the cause of the error.

5.14.3 The short self-test and extended self-test

An application client may request that a SCSI target device perform a short self-test or the extended self-test
by setting the SELFTEST bit to zero and specifying an appropriate value in the SELF-TEST CODE field in the
SEND DIAGNOSTIC command (see 6.42).

The criteria for the short self-test are that the test has one or more segments and completes in two minutes or
less. The criteria for the extended self-test are that the test has one or more segments and that the completion
time required by the SCSI target device to complete the extended self-test is reported in the EXTENDED
SELF-TEST COMPLETION MINUTES field in the Extended INQUIRY Data VPD page (see 7.8.7), the EXTENDED
SELF-TEST COMPLETION TIME field in the Control mode page (see 7.5.8), or both.

The tests performed in the segments are vendor specific and may be the same for the short self-test and the
extended self-test.

The following are examples of segments:

a) an electrical segment wherein the logical unit tests its own electronics. The tests in this segment are
vendor specific, but some examples of tests that may be included are:
A) a buffer RAM test;
B) a read/write circuitry test; and
C) a test of the read/write heads;
b) a seek/servo segment wherein a device tests it capability to find and servo on data tracks; and
c) a read/verify scan segment wherein a device performs read scanning of some or all of the medium
surface.

232 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.14.4 Self-test modes

5.14.4.1 Self-test modes overview

A foreground mode (see 5.14.4.2) and a background mode (see 5.14.4.3) are defined for the short self-test
and the extended self-test. An application client specifies the self-test mode by the value in the SELF-TEST
CODE field in the SEND DIAGNOSTIC command (see 6.42).

5.14.4.2 Foreground mode

If an application client specifies a self-test to be performed in the foreground mode, the device server shall
return status for the command after the self-test has been completed.

While a SCSI target device is performing a self-test in the foreground mode, the device server shall terminate
all commands, except INQUIRY commands, REPORT LUNS commands, and REQUEST SENSE commands,
with CHECK CONDITION status, with the sense key set to NOT READY, and the additional sense code set to
LOGICAL UNIT NOT READY, SELF-TEST IN PROGRESS. If the device server receives an INQUIRY
command, a REPORT LUNS command, or a REQUEST SENSE command while performing a self-test in the
foreground mode, then the device server shall process the command.

If a SCSI target device is performing a self-test in the foreground mode and an error occurs during the test,
then:

a) the SCSI target device shall abort the self-test; and

b) the device server is:
A) able to update the Self-Test Results log page (see 7.3.17), then the device server shall update the
Self-Test Results log page and terminate the SEND DIAGNOSTIC command with CHECK
CONDITION status, with the sense key set to HARDWARE ERROR, and the additional sense
code set to LOGICAL UNIT FAILED SELF-TEST. The application client may obtain additional
information about the failure by reading the Self-Test Results log page; or
B) unable to update the Self-Test Results log page, then the device server shall terminate the SEND
DIAGNOSTIC command with CHECK CONDITION status, with the sense key set to HARDWARE
ERROR, and the additional sense code set to LOGICAL UNIT UNABLE TO UPDATE
SELF-TEST LOG.

An application client may cause a SCSI target device to abort a self-test that is being performed in the
foreground mode by using a task management function (see SAM-5) (e.g., an ABORT TASK task
management function, a CLEAR TASK SET task management function) or a transport specific reset (e.g., a
hard reset event) (see SAM-5). In addition, a self-test being performed in the foreground mode shall be
terminated by an I_T nexus loss event or a power loss expected event (see SAM-5). If a SCSI target device
aborts a self-test that is being performed in the foreground mode based on the SCSI target device receiving a
task management function or a transport specific event, then the device server shall update the Self-Test
Results log page (see 7.3.17).

5.14.4.3 Background mode

If a device server receives a SEND DIAGNOSTIC command specifying a self-test to be performed in the
background mode, then:

a) the device server shall terminate the command if the CDB is invalid; or
b) the device server shall:
1) complete the command with GOOD status;
2) initialize the next self-test results log parameter in the Self-Test Results log page (see 7.3.17) by
setting:

Working Draft SCSI Primary Commands - 4 (SPC-4) 233

T10/BSR INCITS 513 Revision 37 17 May 2014

a) the SELF-TEST CODE field to the self-test code from the SEND DIAGNOSTIC command; and
b) the SELF-TEST RESULTS field to Fh;
and
3) begin the self-test.

An application client may request that a device server abort a self-test that is being performed in the
background mode by sending a SEND DIAGNOSTIC command with the SELF-TEST CODE field set to 100b (i.e.,
abort background self-test function). A SCSI target device shall not abort a self-test being performed in the
background mode as the result of an I_T nexus loss event (see SAM-5). A SCSI target device shall abort a
self-test being performed in the background mode as the result of a power loss expected event (see SAM-5).

While the SCSI target device is performing a self-test in the background mode, the device server shall
terminate with CHECK CONDITION status, with the sense key set to NOT READY and the additional sense
code to LOGICAL UNIT NOT READY, SELF-TEST IN PROGRESS any received SEND DIAGNOSTIC
command that meets any of the following criteria:

a) the SELFTEST bit is set to one; or

b) the SELF-TEST CODE field is set to a value other than 000b or 100b.

If the SCSI target device is performing a self-test in the background mode, and the device server receives any
command that requires suspension of the self-test to process, except those listed in table 106, then:

a) the device server shall suspend the self-test;

b) the device server shall begin processing the command within two seconds after the CDB has been
validated; and
c) after the command completes, the device server shall resume the self-test.

If the device server receives one of the commands listed in table 106, then the device server shall:

a) abort the self-test;

b) update the self-test log; and
c) begin processing the command within two seconds after the CDB has been validated.

Table 106 — Exception commands for background self-tests

Device type Command Reference

SEND DIAGNOSTIC (with SELF-TEST CODE field set to 100b) 6.42
All device types WRITE BUFFER (with the MODE field set to any download microcode
mode (see table 58 in 5.4)) 6.49
Direct access FORMAT UNIT
SBC-3
block START STOP UNIT
ERASE
Sequential
FORMAT MEDIUM SSC-4
access
LOAD UNLOAD
Object-based Any command with operation code 7Fh (i.e., all commands defined by
OSD
storage the OSD standard)
NOTE – Device types not listed in this table do not have commands that are exceptions for background
self-tests, other than those listed above for all device types.

234 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.14.4.4 Features common to foreground and background self-test modes

An application client may use a REQUEST SENSE command (see 6.39) to poll for progress indication at any
time during a self-test. The device server shall provide pollable REQUEST SENSE data (see 5.10.2) with the
sense key set to NOT READY, the additional sense code set to LOGICAL UNIT NOT READY, SELF-TEST IN
PROGRESS, and the PROGRESS INDICATION field set to indicate the progress of the self-test.

An application client may use the EBACKERR bit and the MRIE field in the Informational Exceptions Control
mode page (see applicable command standard) to control the reporting of errors that occur during a
background self-test operation.

An application client may obtain information about the 20 most recent self-tests, including the self-test in
progress, if any, by reading the Self-Test Results log page (see 7.3.17). With the exception of progress
indication, this is the only method for an application client to obtain information about self-tests performed in
the background mode unless an error occurs during the self-test.

Working Draft SCSI Primary Commands - 4 (SPC-4) 235

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 107 summarizes:

a) when a device server returns status after receipt of a self-test command;

b) how an application client may abort a self-test;
c) how a device server processes commands that are entered into the task set while a self-test is in
progress; and
d) how a self-test failure is reported.

Table 107 — Self-test mode summary

Self- When Processing of

test status is How to abort commands while a
mode returned the self-test self-test is in progress Self-test failure reporting
Fore- After the A task If the command is The device server terminates the
ground self-test management INQUIRY, REPORT LUNS SEND DIAGNOSTIC command with
is com- function or or REQUEST SENSE, CHECK CONDITION status, with the
plete reset event then process normally, sense key set to HARDWARE
that causes a otherwise, terminate with ERROR, and the additional sense
self-test to be CHECK CONDITION sta- code set to LOGICAL UNIT FAILED
aborted (see tus, with the sense key set SELF-TEST or LOGICAL UNIT
5.14.4.2) to NOT READY, and the UNABLE TO UPDATE SELF-TEST
additional sense code set LOG (see 5.14.4.2). a
to LOGICAL UNIT NOT
READY, SELF-TEST IN
PROGRESS.
Back- After the A SEND Process the command, An application client:
ground CDB is DIAG- except as described in a) checks the Self-Test Results
validated NOSTIC 5.14.4.3. log page (see 7.3.17) after the
command PROGRESS INDICATION field
with the returned in response to a
SELF-TEST REQUEST SENSE command
CODE field set indicates that the self-test is
to 100b complete; or
b) uses the EBACKERR bit and the
MRIE field (see applicable
command standard) to specify
a method of indicating that a
failure occurred. If a failure
occurs, then an additional
sense code of WARNING -
BACKGROUND SELF-TEST
FAILED shall be returned using
the method defined in the MRIE
field.
a
The device server shall not report an error until after the Self-Test Results log page is updated.

236 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.15 Target port group asymmetric access states

5.15.1 Target port group access overview

Logical units may be connected to one or more service delivery subsystems via multiple target ports (see
SAM-5). The access to logical units through the multiple target ports may be symmetrical (see 5.15.3) or
asymmetrical (see 5.15.2).

If referrals are supported (see SBC-3), then a logical unit accessed through a target port group may have
different target port group asymmetric access states based on the user data segments being accessed.

5.15.2 Asymmetric logical unit access

5.15.2.1 Introduction to asymmetric logical unit access

Asymmetric logical unit access occurs when the access characteristics of one port may differ from those of
another port. SCSI target devices with target ports implemented in separate physical units may designate
differing levels of access for the target ports associated with each logical unit. While commands and task
management functions (see SAM-5) may be routed to a logical unit through any target port, the performance
may not be optimal, and the allowable command set may be less complete than when the same commands
and task management functions are routed through a different target port. In addition, some target ports may
be in a state (e.g., offline) that is unique to that target port. If a failure on the path to one target port is detected,
the SCSI target device may perform automatic internal reconfiguration to make a logical unit accessible from a
different set of target ports or may be instructed by the application client to make a logical unit accessible from
a different set of target ports.

A target port characteristic called primary target port asymmetric access state (see 5.15.2.4) defines
properties of a target port and the allowable command set for a logical unit when commands and task
management functions are routed through the target port maintaining that state.

A primary target port group is defined as a set of target ports that are in the same primary target port
asymmetric access state at all times (i.e., a change in one target port’s primary target port asymmetric access
state implies an equivalent change in the primary target port asymmetric access state of all target ports in the
same primary target port group). A primary target port group asymmetric access state is defined as the
primary target port asymmetric access state common to the set of target ports in a primary target port group.
One target port is a member of at most one primary target port group for a logical unit group (see 7.8.6.9). The
grouping of target ports in a primary target port group is vendor specific.

A logical unit may have commands and task management functions routed through multiple primary target
port groups. Logical units support asymmetric logical unit access if different primary target port groups may be
in different primary target port group asymmetric access states. Support for asymmetric logical unit access
should not affect how the device server responds to unsupported commands or how the task manager
responds to unsupported task management functions.

An example of asymmetric logical unit access is a SCSI controller device with two separated controllers where
all target ports on one controller are in the same primary target port asymmetric access state with respect to a
logical unit and are members of the same primary target port group. Target ports on the other controller are
members of another primary target port group. The behavior of each primary target port group may be
different with respect to a logical unit, but all members of a single primary target port group are always in the
same primary target port group asymmetric access state with respect to a logical unit.

Working Draft SCSI Primary Commands - 4 (SPC-4) 237

T10/BSR INCITS 513 Revision 37 17 May 2014

An example of primary target port groups is shown in figure 16.

Logical Unit

Primary Primary
Target Port Target Port
Group 1 Group n
● ● ●
Target Target Target ● ● ●
Target
Port 1 Port 2 Port 10 Port n

Figure 16 — Primary target port group example

Another target port characteristic called secondary target port asymmetric access state (see 5.15.2.4)
indicates a condition that affects the way in which an individual target port participates in its assigned primary
target port group. All target ports, if any, in one secondary target port asymmetric access state are grouped
into a secondary target port group. Secondary target port groups have the following properties:

a) a target port in any secondary target port group also shall be in one primary target port group;
b) a change of secondary target port asymmetric access state for one target port shall not cause
changes in the secondary target port asymmetric access state of other target ports, if any, in the same
secondary target port group; and
c) a target port may be a member of zero or more secondary target port groups.

The term target port asymmetric access state represents both primary target port asymmetric access states
and secondary target port asymmetric access states. The term target port group represents both primary
target port groups and secondary target port groups.

5.15.2.2 Explicit and implicit asymmetric logical unit access

Asymmetric logical unit access may be managed explicitly by an application client using the REPORT
TARGET PORT GROUPS (see 6.37) command and SET TARGET PORT GROUPS (see 6.45) command.

Alternatively, asymmetric logical unit access may be managed implicitly by the SCSI target device based on
the type of transactions being routed through each target port and the internal configuration capabilities of the
primary target port group(s) through which the logical unit may be accessed. The logical units may attempt to
maintain full performance across the primary target port groups that are busiest and that show the most
reliable performance, allowing other primary target port groups to select a lower performance primary target
port asymmetric access state.

Implicit management of secondary target port asymmetric access states is based on the condition of an
individual target port and how such conditions affect that target port’s ability to participate in its assigned
primary target port group.

If both explicit and implicit asymmetric logical unit access management methods are implemented, the
precedence of one over the other is vendor specific.

238 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.15.2.3 Discovery of asymmetric logical unit access behavior

SCSI logical units with asymmetric logical unit access may be identified using the INQUIRY command. The
value in the target port group support (TPGS) field (see 6.6.2) indicates whether or not the logical unit supports
asymmetric logical unit access and if so whether implicit or explicit management is supported. The target port
asymmetric access states supported by a logical unit may be determined by the REPORT TARGET PORT
GROUPS command parameter data (see 6.37).

5.15.2.4 Target port asymmetric access states

5.15.2.4.1 Target port asymmetric access states overview

For all SCSI target devices that report in the INQUIRY data that they support asymmetric logical unit access,
all of the target ports in a primary target port group (see 5.15.2.1) shall be in the same primary target port
asymmetric access state with respect to the ability to route information to a logical unit. The primary target port
asymmetric access states are:

a) active/optimized;
b) active/non-optimized;
c) standby;
d) unavailable; and
e) logical block dependent.

Individual target ports may be in secondary target port groups (see 5.15.2.1) that have the following
secondary target port asymmetric access states:

a) offline.

5.15.2.4.2 Active/optimized state

The active/optimized state is a primary target port asymmetric access state. While commands and task
management functions are being routed through a target port in the active/optimized primary target port
asymmetric access state, the device server shall function (e.g., respond to commands) as specified in the
appropriate command standards. All target ports within a primary target port group should be capable of
immediately accessing the logical unit.

The SCSI target device shall participate in all task management functions as defined in SAM-5 and modified
by the applicable SCSI transport protocol standards.

5.15.2.4.3 Active/non-optimized state

The active/non-optimized state is a primary target port asymmetric access state. While commands and task
management functions are being routed through a target port in the active/non-optimized primary target port
asymmetric access state, the device server shall function as specified in the appropriate command standards.

The processing of some task management functions and commands, especially those involving data transfer
or caching, may operate with lower performance than they would if the target port were in the active/optimized
primary target port asymmetric access state.

The SCSI target device shall participate in all task management functions as defined in SAM-5 and modified
by the applicable SCSI transport protocol standards.

Working Draft SCSI Primary Commands - 4 (SPC-4) 239

T10/BSR INCITS 513 Revision 37 17 May 2014

5.15.2.4.4 Standby state

The standby state is a primary target port asymmetric access state. While being accessed through a target
port in the standby primary target port asymmetric access state, the device server shall support those of the
following commands that it supports while in the active/optimized primary target port asymmetric access state:

a) INQUIRY;
b) LOG SELECT;
c) LOG SENSE;
d) MODE SELECT;
e) MODE SENSE;
f) REPORT LUNS;
g) RECEIVE DIAGNOSTIC RESULTS;
h) SEND DIAGNOSTIC;
i) REPORT TARGET PORT GROUPS;
j) SET TARGET PORT GROUPS;
k) REQUEST SENSE;
l) PERSISTENT RESERVE IN;
m) PERSISTENT RESERVE OUT;
n) echo buffer modes of READ BUFFER; and
o) echo buffer modes of WRITE BUFFER.

The device server may support other commands while in the standby state.

The device server shall terminate commands that are not supported in the standby state with CHECK
CONDITION status, with the sense key set to NOT READY, and the additional sense code set to LOGICAL
UNIT NOT ACCESSIBLE, TARGET PORT IN STANDBY STATE.

The SCSI target device shall participate in all task management functions as defined in SAM-5 and modified
by the applicable SCSI transport protocol standards.

5.15.2.4.5 Unavailable state

The unavailable state is a primary target port asymmetric access state. While being accessed through a target
port in the unavailable primary target port asymmetric access state, the device server shall accept only a
limited set of commands. The unavailable primary target port asymmetric access state is intended for
situations where the target port accessibility to a logical unit may be severely constrained due to SCSI target
device limitations (e.g., hardware errors). Therefore it may not be possible to transition from the unavailable
state to the active/optimized state, the active/non-optimized state, or the standby state. The unavailable
primary target port asymmetric access state is also intended for minimizing any disruption when using the
downloading microcode modes of the WRITE BUFFER command (see 5.4).

While in the unavailable primary target port asymmetric access state, the device server shall support those of
the following commands that it supports while in the active/optimized state:

a) INQUIRY (the peripheral qualifier (see 6.6.2) shall be set to 001b);

b) REPORT LUNS;
c) REPORT TARGET PORT GROUPS;
d) SET TARGET PORT GROUPS;
e) REQUEST SENSE;
f) echo buffer modes of READ BUFFER;
g) echo buffer modes of WRITE BUFFER; and
h) download microcode mode of WRITE BUFFER.

240 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The device server may support other commands while in the unavailable state.

The device server shall terminate commands that are not supported in the unavailable state with CHECK
CONDITION status, with the sense key set to NOT READY, and the additional sense code set to LOGICAL
UNIT NOT ACCESSIBLE, TARGET PORT IN UNAVAILABLE STATE.

The SCSI target device is not required to participate in all task management functions (see SAM-5 and the
applicable SCSI transport protocol standards).

5.15.2.4.6 Offline state

The offline state is a secondary target port asymmetric access state. Target ports in the offline secondary
target port asymmetric access state are not accessible via the service delivery subsystem (e.g., during
maintenance, port replacement, port disabled, hot swap, or power failures that affect only a subset of target
ports). While in the offline secondary target port asymmetric state, the target port is not capable of receiving or
responding to any commands or task management functions.

The offline secondary target port asymmetric access state allows a device server to report that some target
ports are not capable of being accessed.

After access to the service delivery subsystem is enabled, the target port shall transition out of the offline
secondary target port asymmetric access state.

5.15.2.4.7 Logical block dependent state

The logical block dependent state is a primary target port asymmetric access state. The logical block
dependent state only occurs if the device server supports referrals (see 7.8.7).

The target port asymmetric access state for a user data segment shall be one of the following target port
asymmetric access states:

a) active/optimized;
b) active/non-optimized;
c) transitioning; or
d) unavailable.

An application client may determine the target port asymmetric access state for user data segments by issuing
a REPORT REFERRALS command (see SBC-3).

5.15.2.5 Transitions between target port asymmetric access states

The movement from one target port asymmetric access state to another is called a transition.

During a transition between target port asymmetric access states the device server shall respond to a
command in one of the following ways:

a) if during the transition the logical unit is inaccessible, then the transition is performed as a single
indivisible event and the device server shall respond by either returning BUSY status, or returning
CHECK CONDITION status, with the sense key set to NOT READY, and the sense code set to
LOGICAL UNIT NOT ACCESSIBLE, ASYMMETRIC ACCESS STATE TRANSITION; or

Working Draft SCSI Primary Commands - 4 (SPC-4) 241

T10/BSR INCITS 513 Revision 37 17 May 2014

b) if during the transition the target ports in a primary target port group are able to access the requested
logical unit, then:
A) the device server shall support those of the following commands that it supports while in the
active/optimized primary target port asymmetric access state:
a) INQUIRY;
b) REPORT LUNS;
c) REPORT TARGET PORT GROUPS;
d) REQUEST SENSE;
e) echo buffer modes of READ BUFFER; and
f) echo buffer modes of WRITE BUFFER;
B) the device server may support other commands when those commands are routed though a
target port that is transitioning between primary target port asymmetric access states;
C) the device server shall terminate commands that are not supported during a transition with
CHECK CONDITION status, with the sense key set to NOT READY, and the additional sense
code set to LOGICAL UNIT NOT ACCESSIBLE, ASYMMETRIC ACCESS STATE TRANSITION;
and
D) the SCSI target device is not required to participate in all task management functions.

If the transition was explicit to a supported target port asymmetric access state and it failed, then the device
server shall terminate the command with CHECK CONDITION status, with the sense key set to HARDWARE
ERROR, and the additional sense code set to SET TARGET PORT GROUPS COMMAND FAILED. If the
transition was to a primary target port asymmetric access state, the primary target port group that encountered
the error should complete a transition to the unavailable primary target port asymmetric access state.

If a target port asymmetric access state change occurred as a result of the failed transition, then the device
server shall establish a unit attention condition for the initiator port associated with every I_T nexus other than
the I_T nexus on which the SET TARGET PORT GROUPS command was received with the additional sense
code set to ASYMMETRIC ACCESS STATE CHANGED.

If the transition was implicit and it failed, then the device server shall establish a unit attention condition for the
initiator port associated with every I_T nexus with the additional sense code set to IMPLICIT ASYMMETRIC
ACCESS STATE TRANSITION FAILED.

An implicit CLEAR TASK SET task management function may be performed following a transition failure.

Once a transition is completed, the new target port asymmetric access state may apply to some or all
commands entered into the task set before the completion of the transition. The new target port asymmetric
access state shall apply to all commands received by the device server after completion of a transition.

If a transition is to the offline secondary target port asymmetric access state, communication with the service
delivery subsystem shall be terminated. This may result in commands being terminated and may cause
command timeouts to occur on the initiator.

After an implicit target port asymmetric access state change, a device server shall establish a unit attention
condition for the initiator port associated with every I_T nexus with the additional sense code set to
ASYMMETRIC ACCESS STATE CHANGED.

After an explicit target port asymmetric access state change, a device server shall establish a unit attention
condition with the additional sense code set to ASYMMETRIC ACCESS STATE CHANGED for the initiator
port associated with every I_T nexus other than the I_T nexus on which the SET TARGET PORT GROUPS
command was received.

242 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.15.2.6 Preference indicator

A device server may indicate one or more primary target port groups is a preferred primary target port group
for accessing a logical unit by setting the PREF bit to one in the target port group descriptor (see 6.37). The
preference indication is independent of the primary target port asymmetric access state.

An application client may use the PREF bit value in the target port group descriptor to influence the path
selected for a logical unit (e.g., a primary target port group in the standby primary target port asymmetric
access state with the PREF bit set to one may be chosen over a primary target port group in the
active/optimized primary target port asymmetric access state with the PREF bit set to zero).

The value of the PREF bit for a primary target port group may change whenever a primary target port
asymmetric access state changes.

5.15.2.7 Target port asymmetric access state reporting

Target port asymmetric access state information is reported in a target port group descriptor (see table 308) in
the parameter data returned by the REPORT TARGET PORT GROUPS command (see 6.37). Each target
port group descriptor indicates the asymmetric access state for all target ports contained in the indicated
target port group (i.e., all target ports described in the target port descriptors contained in the target port group
descriptor). A primary asymmetric access state (see table 309) applies to all logical units in the same logical
unit group (see 7.8.6.9).

The parameter data returned by each REPORT TARGET PORT GROUPS command is independent (e.g., the
device server may return different values in the ASYMMETRIC ACCESS STATE field (see table 308) for the same
target port group in the parameter data returned by REPORT TARGET PORT GROUPS commands received
through different target ports).

The information returned in the target port group descriptor that contains a target port descriptor with a relative
target port identifier that matches the relative target port identifier of the target port through which the
REPORT TARGET PORTS GROUP command is received shall be the current information.

EXAMPLE – An application client sends two REPORT TARGET PORT GROUPS commands to the logical unit shown in
figure 16. The commands are received via different target ports with target port identifiers 2 and 10. Although the
command that is received via the target port with relative target port identifier 2 returns the current information for the
target port group that contains the target port with relative target port identifier 2, the command may not return the current
information for the target port group that contains the target port with relative target port identifier 10. The converse is true
for the command that is received via the target port with relative target port identifier 10. Although the command that is
received via the target port with relative target port identifier 10 returns the current information for the target port group that
contains the target port with relative target port identifier 10, the command may not return the current information for the
target port group that contains the target port with relative target port identifier 2.

If an application client detects different parameter data returned by REPORT TARGET PORT GROUPS
commands for the same target port group (i.e., both current information and information that may not be
current), then the application client should use the current information.

5.15.2.8 Implicit asymmetric logical units access management

SCSI target devices with implicit asymmetric logical units access management are capable of using
mechanisms other than the SET TARGET PORT GROUPS command to set:

a) the primary target port asymmetric access state of a primary target port group; or
b) the secondary target port asymmetric access state of a target port that is a member of a primary
target port group.

Working Draft SCSI Primary Commands - 4 (SPC-4) 243

T10/BSR INCITS 513 Revision 37 17 May 2014

All logical units that report in the standard INQUIRY data (see 6.6.2) that they support asymmetric logical unit
access and support implicit asymmetric logical unit access (i.e., the TPGS field is set to 01b or 11b):

a) shall implement the INQUIRY command Device Identification VPD page designator type 4h (see
7.8.6.7) and designator type 5h (see 7.8.6.8);
b) shall support the REPORT TARGET PORT GROUPS command as described in 6.37; and
c) may implement the INQUIRY command Device Identification VPD page designator type 6h (see
7.8.6.9).

Implicit logical unit access state changes between primary target port asymmetric access states may be
disabled with the IALUAE bit in the Control Extension mode page (see 7.5.9).

5.15.2.9 Explicit asymmetric logical units access management

All logical units that report in the standard INQUIRY data (see 6.6.2) that they support asymmetric logical units
access and support explicit asymmetric logical unit access (i.e., the TPGS field is set to 10b or 11b):

a) shall implement the INQUIRY command Device Identification VPD page designator type 4h (see
7.8.6.7) and designator type 5h (see 7.8.6.8);
b) shall support the REPORT TARGET PORT GROUPS command as described in 6.37;
c) shall support the SET TARGET PORT GROUPS command as described in 6.45; and
d) may implement the INQUIRY command Device Identification VPD page designator type 6h (see
7.8.6.9).

5.15.2.10 Behavior after power on, hard reset, logical unit reset, and I_T nexus loss

For all SCSI target devices that report in the standard INQUIRY data (see 6.6.2) that they support only explicit
asymmetric logical unit access (i.e., the TPGS field is set to 10b), the target port shall preserve the primary
target port asymmetric access state during any power on, hard reset, logical unit reset, and I_T nexus loss.

5.15.2.11 Behavior of target ports that are not accessible from the service delivery subsystem

If the offline secondary target port asymmetric access state is supported and a subset of the target ports in a
primary target port group are not accessible via the service delivery subsystem (e.g., power failure), then
those ports may be reported in a primary target port group consistent with their primary target port asymmetric
access state and in the secondary target port group with the offline secondary target port asymmetric access
state.

5.15.3 Symmetric logical unit access

A device server that provides symmetrical access to a logical unit may use a subset of the asymmetrical
logical access features (see 5.15.2) to indicate this ability to an application client, providing an application
client a common set of commands to determine how to manage target port access to a logical unit.

Symmetrical logical unit access should be represented as follows:

a) the TPGS field in the standard INQUIRY data (see 6.6.2) indicates that implicit asymmetric access is
supported;
b) the REPORT TARGET PORT GROUPS command is supported; and
c) the REPORT TARGET PORT GROUPS parameter data indicates that the same state (e.g.,
active/optimized state) is in effect for all primary target port groups.

244 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.16 Third-party copies

5.16.1 General considerations for third-party copies

Third-party copy commands (see 5.16.3) cause a copy manager to perform copy operations (see 5.16.4.3)
that transfer data as follows:

a) from specified areas of the medium within a logical unit to different areas within the same logical unit;
b) from one logical unit to another within a SCSI target device; or
c) from one SCSI target device to another SCSI target device.

The transfers requested by a third-party copy command are managed by a copy manager (see 5.16.2) that is
contained in a logical unit (see SAM-5). The copy manager is responsible for transferring data from copy
sources to copy destinations (i.e., reading from the copy sources, buffering as needed, and writing to the copy
destinations).

Application clients and other copy managers request third-party copy operations by sending commands (see
5.16.3) to a copy manager for processing by that copy manager. Copy managers provide information about
their capabilities to application clients in the Third-party Copy VPD page (see 7.8.17).

A copy manager is not required to support all the third-party copy features described in 5.16, but if a copy
manager supports copies from one SCSI target device to another SCSI target device, then the copy manager
shall support copies from one logical unit to another logical unit within the same SCSI target device.

If a logical unit contains a copy manager that supports any of the commands described in 5.16.3, then the 3PC
bit shall be set to one in the standard INQUIRY data (see 6.6.2).

5.16.2 Copy manager model

A copy manager is:

a) a kind of device server that processes the commands described in 5.16.3 using foreground or
background copy operations (see 5.16.4.3); and
b) a kind of application client that sends commands to other device servers and copy managers,
possibly in other SCSI target devices, as necessary to perform the copy operation originated by a
third-party copy command (see 5.16.4.3).

If a copy manager interacts with a copy manger in another SCSI target device, these interactions may occur
over a SCSI transport protocol or over a non-SCSI transport.

Upon the successful completion of a copy operation (see 5.16.4.3), the copy manager shall have produced
the results specified by the command that originated the copy operation in accordance with this standard or
the applicable command standard (e.g., SBC-3 for the WRITE USING TOKEN command). To ensure
interoperability, this standard or the applicable command standard may place requirements on the copy
manager using terminology based on specific commands and parameter data (e.g., specific instances of the
EXTENDED COPY(LID4) command). These are only functional descriptions of the required copy manager
behavior. Any copy manager implementation that produces the specified results and does not violate
interoperability may be used.

Working Draft SCSI Primary Commands - 4 (SPC-4) 245

T10/BSR INCITS 513 Revision 37 17 May 2014

A copy manager may be contained in:

a) the same logical unit as the device server for a data storage device (e.g., a direct access block device
(see SBC-3) or sequential-access device (see SSC-4)); or
b) a standalone SCSI target device whose only purpose is to contain one or more logical units that
contain copy managers.

If the copy manager is contained in the same logical unit as the device server for a data storage device, then
the following requirements shall apply:

a) the PERIPHERAL DEVICE TYPE field in the standard INQUIRY data (see 6.6.2) shall indicate the device
type associated with the device server;
b) the copy manager shall have the same access to the data storage media associated with the logical
unit that contains the copy manager as any other application client for the purposes of processing
third-party copy commands and operations (see 5.16.3);
c) the copy manager shall be able to access all other device servers and copy managers located in the
same SCSI target device as the copy manager; and
d) the copy manager may or may not be able to access device servers and copy managers located in
other SCSI target devices.

If the copy manager is contained in a standalone SCSI target device whose only purpose is to contain logical
units that contain copy managers, then the following requirements shall apply:

a) the PERIPHERAL DEVICE TYPE field in the standard INQUIRY data (see 6.6.2) shall indicate that the
device is a processor type device (see SPC-2);
b) the device server may not implement any of the specialized processor device type commands (e.g.,
SEND); and
c) the copy manager shall be able to access device servers and copy managers in at least one other
SCSI target device for the purposes of processing third-party copy commands and operations.

Within a SCSI target device, a copy manager shall not have access to SCSI ports that are not accessible to
the device server in the same logical unit (e.g., due to restrictions imposed by asymmetric logical unit access
features (see 5.15.2)), but a copy manager may have access to non-SCSI data transports. As a result:

a) if a copy manager has access to only one SCSI port, then the copy operations performed by the copy
manager are limited to a single SCSI domain;
b) if a copy manager has access to multiple SCSI ports some of which are in different SCSI domains,
then the copy operations performed by the copy manager are limited to the accessible SCSI domains,
but may transfer data from one SCSI domain to another; or
c) if a copy manager has access to non-SCSI data transports, then the copy operations performed by
the copy manager may transfer data from one SCSI domain to another SCSI domain that is not
accessible to the device server associated with the copy manager.

In response to interactions with other copy managers, a copy manager may process requests for copy
operations even if the copy manager does not implement an equivalent third-party copy command (see
5.16.3).

EXAMPLE – Suppose a copy manager has access to a non-SCSI transport that transfers data in message IUs instead of
SCSI reads and writes. Even though no SCSI commands are performed, the copy manager is allowed to process a write
command as an EXTENDED COPY(LID4) command (see 6.4) with the data to be written contained in the inline data
portion of the parameter data. The copy manager is also allowed to process a read command as an EXTENDED
COPY(LID4) command that generates held data (see 5.16.4.5) followed by a RECEIVE COPY DATA(LID4) command
(see 6.20) to retrieve the held data. The same copy manager may indicate that it supports only the POPULATE TOKEN
command (see SBC-3), WRITE USING TOKEN command (see SBC-3), and RECEIVE ROD TOKEN INFORMATION

246 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

command (see 6.28 and SBC-3).

Figure 17 shows examples copy manager configurations and third-party copies they may perform.

Applica- Applica- Applica-

tion Client tion Client tion Client

Copy Copy Copy

Manager Manager Manager

Copy Copy
Manager Manager

Copy manager Copy managers Copy managers in

in logical unit in SCSI target device one SCSI domain

Applica-
tion Client
Applica-
tion Client
Copy Device Device
Manager Server Server Copy Copy
Manager Manager

Two copy managers in two SCSI domains

Standalone Copy Manager
connected by a non-SCSI transport
Key:
SCSI transport data storage media
non-SCSI transport
example third-party copy SCSI domain

Note - These elements are shown only

when needed for clarity.
Figure 17 — Examples of copy manager configurations

Working Draft SCSI Primary Commands - 4 (SPC-4) 247

T10/BSR INCITS 513 Revision 37 17 May 2014

5.16.3 Third-party copy commands

The commands processed by copy managers (i.e., third-party copy commands) are shown in table 108.

Table 108 — Third-party copy commands

Operation Command
Command code a type Reference
COPY OPERATION ABORT 83h/1Ch abort 6.3
EXTENDED COPY(LID4) 83h/01h originate 6.4
EXTENDED COPY(LID1) 83h/00h originate 6.5
POPULATE TOKEN 83h/10h originate SBC-3
RECEIVE COPY DATA(LID4) 84h/06h retrieve 6.20
RECEIVE COPY DATA(LID1) 84h/01h retrieve 6.21
b
RECEIVE COPY OPERATING PARAMETERS 84h/03h retrieve 6.22
RECEIVE COPY FAILURE DETAILS(LID1) 84h/04h retrieve 6.23
RECEIVE COPY STATUS(LID4) 84h/05h retrieve 6.24
RECEIVE COPY STATUS(LID1) 84h/00h retrieve 6.25
RECEIVE ROD TOKEN INFORMATION 84h/07h retrieve 6.28
REPORT ALL ROD TOKENS 84h/08h retrieve 6.31
WRITE USING TOKEN 83h/11h originate SBC-3
Reserved all others c
Key:
abort third-party copy command that aborts a specified copy operation
originate third-party copy command that requests the processing of a copy operation
retrieve third-party copy command that retrieves the results (e.g., status data or held data) for a
previously originated copy operation
a All copy manager commands are defined by a combination of operation code and service action.
The operation code value is shown preceding the slash and the service action value is shown
after the slash.
b
New operating parameters are no longer being added to the parameter data returned by the
RECEIVE COPY OPERATING PARAMETERS command. The Third-party Copy VPD page (see
7.8.17) provides the most complete information about how a copy manager operates and the
functions that it supports.
c
All service actions of operation code 83h and operation code 84h not shown in this table are
reserved.

248 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Copy manager support for third-party copy commands is optional, but support for some third-party copy
commands and features may require support for other third-party copy commands as shown in table 109.

Table 109 — Mandatory copy manager command support requirements

Optional command
features supported

Held R_TOKEN Copy manager support for the following

Supported command data a bitb
commands is mandatory
COPY OPERATION ABORT n/a n/a RECEIVE COPY STATUS(LID4)
EXTENDED COPY(LID4) n/a n/a RECEIVE COPY STATUS(LID4)
EXTENDED COPY(LID4) yes n/a RECEIVE COPY DATA(LID4)
EXTENDED COPY(LID1) n/a n/a RECEIVE OPERATING PARAMETERS
RECEIVE COPY FAILURE DETAILS(LID1)
RECEIVE COPY STATUS(LID1)
EXTENDED COPY(LID1) yes n/a RECEIVE COPY STATUS(LID1)
RECEIVE COPY DATA(LID1)
EXTENDED COPY(LID4) or n/a yes
RECEIVE ROD TOKEN INFORMATION
EXTENDED COPY(LID1)
POPULATE TOKEN n/a n/a
See SBC-3
WRITE USING TOKEN n/a n/a
a
Held data (see 5.16.4.5) refers to support for the ability to hold some or all of the data processed
by a copy operation for later transfer to the application client (e.g., support for the stream discard&
application client segment descriptor (see 6.4.6.8)).
b R_TOKEN bit refers to support for the ability to create ROD tokens that are later returned to the

application client (i.e., support for the R_TOKEN bit being set to one in the ROD CSCD descriptor
(see 6.4.5.9)).

If a copy manager supports a third-party copy command in which the IMMED bit, if any, is allowed to be set to
one, then the copy manager shall support the COPY OPERATION ABORT command (see 6.3).

5.16.4 Third-party copy command usage

5.16.4.1 Prior to sending a third-party copy command

Before the copy manager is instructed to transfer data, the application client requesting the data transfers
shall take any necessary actions required to prepare the copy sources and copy destinations (see 5.16.1).
Such preparatory actions include but are not limited to:

a) loading tapes;
b) sending media changer commands;
c) sending MODE SELECT commands, including MODE SELECT commands that:
A) disable reporting of recovered errors by a block CSCD by setting the PER bit to zero in the
Read-Write Error Recovery mode page (see SBC-3); and/or
B) disable reporting of thin provisioning threshold events by a block CSCD by setting the LBPERE bit
to zero in the Read-Write Error Recovery mode page;
d) sending persistent reservation commands; and/or
e) sending tape positioning commands.

Working Draft SCSI Primary Commands - 4 (SPC-4) 249

T10/BSR INCITS 513 Revision 37 17 May 2014

After all preparatory actions have been completed, the third-party copy command (e.g., the EXTENDED
COPY(LID4) command) should be sent to the copy manager to originate the copy operation (see 5.16.4.3).

5.16.4.2 List identifiers for third-party copy commands

A third-party copy command (see 5.16.3) may:

a) take a long time to complete;

b) have substantial command-specific data to return upon the completion of processing (e.g., held data
(see 5.16.4.4)); and
c) be processed as a background operation (e.g., in response to an IMMED bit being set to one (see
5.16.4.3)).

List identifiers allow an application client to specify the copy operation (see 5.16.4.3) for which a monitoring
function or management function is to be performed, as follows:

1) the application client specifies the list identifier by which a third-party copy operation is to be identified
in the command or parameter list that originates the copy operation; and
2) the application client specifies the same list identifier in any command that monitors or manages the
copy operation:
A) starting from the time the copy operation is originated; and
B) continuing until:
a) all data associated with the copy operation has been delivered to the application client; or
b) the application client specifies that the associated data is to be discarded.

List identifiers are specified in a LIST IDENTIFIER field whose location depends on the third-party command
being processed.

Unless otherwise specified, the LIST IDENTIFIER field contains a value that uniquely identifies a copy operation
among all those being processed that were received on a specific I_T nexus. If the copy manager detects a
duplicate list identifier value, then the copy manager shall terminate the originating third-party copy command
(see table 108 in 5.16.3) with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST,
and the additional sense code set to OPERATION IN PROGRESS.

The following LIST IDENTIFIER field formats are defined by this standard:

a) an 8-bit LIST IDENTIFIER field (e.g., the RECEIVE COPY STATUS(LID1) command (see 6.24)); and
b) a 32-bit LIST IDENTIFIER field (e.g., the RECEIVE COPY DATA(LID4) command (see 6.20)).

If a copy manager supports any third-party copy commands (see 5.16.3) that contain a 32-bit LIST IDENTIFIER
field, then the copy manager shall treat all list identifiers as 32-bit quantities, regardless of the field size used
to specify the list identifier (e.g., a list identifier of 000000FDh shall specify the same copy operation whether it
is present as FDh in an 8-bit field or as 000000FDh in a 32-bit field).

The results of specifying a list identifier from a third-party copy command that originates a copy operation (see
table 108 in 5.16.3) using 32-bit list identifier values in a third-party copy command that retrieves copy
operation data using an 8-bit list identifier are outside the scope of this standard.

5.16.4.3 Third-party copy commands and operations

Third-party copy commands that originate copy operations (see table 108 in 5.16.3) may support the IMMED bit
to allow the application client to specify that the processing of a copy operation continue after the processing
of the originating command has been completed.

250 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If a third-party copy command supports an IMMED bit and that IMMED bit is set to one, the copy manager:

1) shall return CHECK CONDTION status if any errors are detected in the CDB;
2) shall transfer all of the parameter list, if any, to the copy manager;
3) may validate the parameter list and return CHECK CONDITION status if errors are detected;
4) shall complete the command with GOOD status; and
5) shall complete processing of all specified copy operations as a background operation (see SAM-5).

A third-party copy command definition may place additional restrictions on the use of the IMMED bit.

If the IMMED bit is not supported by a command, then the copy manager shall process that command as if the
IMMED bit were set to zero.

If the IMMED bit, if any, is set to:

a) zero, then the copy manager shall not complete processing of the third-party copy command until the
copy manager has completed processing of the copy operation originated by the command (i.e., the
copy manager processes the copy operation in the foreground); or
b) one, then the copy manager may complete processing of the third-party copy command that
originated the copy operation before completing the copy operation (i.e., the copy manager processes
the copy operation in the background). Copy operations that are processed in the background shall
not generate deferred errors (see SAM-5) for the errors encountered, if any, during this processing.
Instead, the error information (e.g., status, sense key, additional sense code) shall be made available
to the application client through use of one of the commands described in 5.16.4.4.

5.16.4.4 Monitoring progress of and retrieving results from third-party copy commands

The RECEIVE COPY STATUS(LID4) command (see 6.24) returns information about the current processing
status of the copy operation (see 5.16.4.3) specified by the list identifier (see 5.16.4.2). The parameter data for
the following commands contain the parameter data for the RECEIVE COPY STATUS(LID4) command as a
header (i.e., the shared third-party copy status header):

a) RECEIVE COPY DATA(LID4) (see 6.24); and

b) RECEIVE ROD TOKEN INFORMATION (see 6.28).

The status information for a copy operation (see 5.16.4.3) shall be available at any time the copy operation is
in progress (i.e., whenever the COPY OPERATION STATUS field is set to 10h, 11h, or 12h).

After the completion of a copy operation (see 5.16.4.3) (i.e., whenever the COPY OPERATION STATUS field is set
to 01h, 02h, 03h, or 60h), the copy manager shall preserve all status information for that copy operation for a
vendor specific period of time. The copy manager shall discard the status information in which the COPY
OPERATION STATUS field is set to 01h, 02h, 03h, or 60h if:

a) another third-party copy command that originates a copy operation (see table 108 in 5.16.3) is
received on the same I_T nexus and the list identifier matches the list identifier associated with the
status information;
b) the copy manager detects a logical unit reset condition or I_T nexus loss condition (see SAM-5); or
c) the copy manager requires the resources used to preserve the status information.

The copy manager may discard the sense data in the status information in which the COPY OPERATION STATUS
field is set to 01h, 02h, 03h, or 60h after that data has been returned by a RECEIVE COPY STATUS(LID4)
command received on the same I_T nexus with a matching list identifier.

Working Draft SCSI Primary Commands - 4 (SPC-4) 251

T10/BSR INCITS 513 Revision 37 17 May 2014

The copy manager shall not discard the status information for a copy operation (see 5.16.4.3) in response to:

a) an ABORT TASK task management function (see SAM-5);

b) an ABORT TASK SET task management function;
c) a CLEAR TASK SET task management function;
d) a PERSISTENT RESERVE OUT command with PREEMPT AND ABORT service action (see 6.16);
or
e) a COPY OPERATION ABORT command (see 6.3).

In the parameter data for all the commands with the shared third-party copy status header, the contents of the
COPY OPERATION STATUS field (see table 252 in 6.24) indicate the current processing status of the specified
copy operation. Unless otherwise specified, the contents of the COPY OPERATION STATUS field are not affected
by whether the copy operation is being or was performed in the foreground or background.

Although the information provided is not as complete, the following commands allow the monitoring of
progress and retrieval of results for certain copy operations in a way that is compatible with SPC-3 but do not
return the shared third-party copy status header:

a) RECEIVE COPY STATUS(LID1) (see 6.25);

b) RECEIVE COPY DATA(LID1) (see 6.21); and
c) RECEIVE COPY FAILURE DETAILS(LID1) (see 6.23).

5.16.4.5 Held data

A copy operation may hold some or all of the data it processes for retrieval by the application client (e.g., the
processing defined for the EXTENDED COPY command streamstream&application client segment
descriptor (see 6.4.6.5)). Held data is retrieved using the RECEIVE COPY DATA(LID4) command (see 6.20)
or the RECEIVE COPY DATA(LID1) command (see 6.21).

If a copy manager supports any third-party copy commands (see 5.16.3) or an EXTENDED COPY command
copy function (see 6.4.6) capable of holding data for retrieval by the application client, then the copy manager:

a) shall support the RECEIVE COPY DATA(LID4) command, if any third-party copy commands are
supported that originate copy operations (see table 108 in 5.16.3) with 32-bit list identifiers (see
5.16.4.2);
b) shall support the RECEIVE COPY DATA(LID1) command, if any third-party copy commands are
supported that originate copy operations with 8-bit list identifiers;
c) shall support either the Third-party Copy VPD page Held Data descriptor (see 7.8.17.12) or the
RECEIVE COPY OPERATING PARAMETERS command (see 6.22); and
d) should support the Third-party Copy VPD page Held Data descriptor.

After the completion of a third-party copy command that originates a copy operation (see table 108 in 5.16.3),
the copy manager shall preserve all held data for a vendor specific period of time. The application client
should retrieve the held data (e.g., by sending a third-party copy command that retrieves the results of a
previously originated copy operation (see table 108 in 5.16.3)) as soon as possible after the completion of the
copy operation to ensure that the data is not discarded by the copy manager. The copy manager shall discard
the held data:

a) after all the held data for a specific copy operation has been successfully transferred to the application
client;
b) if a RECEIVE COPY DATA(LID4) command (see 6.20) or a RECEIVE COPY DATA(LID1) command
(see 6.21) has been received on the same I_T nexus with a matching list identifier (see 5.16.4.2), with
the ALLOCATION LENGTH field set to zero;

252 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

c) if another third-party copy command that originates a copy operation is received on the same I_T
nexus and the list identifier matches the list identifier associated with the held data;
d) if the copy manager detects a logical unit reset condition or I_T nexus loss condition (see SAM-5); or
e) if the copy manager requires the resources used to preserve the held data.

The copy manager shall not discard the held data in response to:

a) an ABORT TASK task management function (see SAM-5);

b) an ABORT TASK SET task management function;
c) a CLEAR TASK SET task management function;
d) a PERSISTENT RESERVE OUT command with PREEMPT AND ABORT service action (see 6.16);
or
e) a COPY OPERATION ABORT command (see 6.3).

The copy manager indicates the minimum amount of held data it supports in the HELD DATA LIMIT field that is
returned in:

a) the Held Data descriptor (see 7.8.17.12) in the Third-party Copy VPD page (see 7.8.17); or
b) the parameter data for a RECEIVE COPY OPERATING PARAMETERS command (see 6.22).

The HELD DATA LIMIT field indicates the length, in bytes, of the minimum amount of data the copy manager
shall hold for return to the application client. If the processing of a copy operation requires more data to be
held, the copy manager may discard some of the held data in a vendor specific manner that retains the held
bytes from the most recently processed portion of the copy operation. The discarding of held data bytes shall
not be considered an error.

The held data discarded (HDD) bit indicates whether held data has been discarded for the copy operation
specified by a list identifier (see 5.16.4.2). If the HDD bit is set to one, held data has been discarded. If the HDD
bit is set to zero, held data has not been discarded. The HDD bit is in the parameter data for:

a) the RECEIVE COPY DATA(LID4) command (see 6.20); and

b) the RECEIVE COPY STATUS(LID1) command (see 6.25).

5.16.4.6 Aborting third-party copy commands and copy operations

A task manager shall ensure that all commands and data transfers generated by a third-party copy operation
have been terminated and are no longer transferring data before allowing the completion of the task
management function or command (e.g., the PERSISTENT RESERVE OUT command with PREEMPT AND
ABORT service action) in response to the following causes for the termination of a third-party copy command:

a) an ABORT TASK task management function (see SAM-5);

b) an ABORT TASK SET task management function (see SAM-5);
c) a CLEAR TASK SET task management function (see SAM-5);
d) a PERSISTENT RESERVE OUT command with PREEMPT AND ABORT service action (see
5.12.11.2.6); and
e) other SCSI device conditions described in SAM-5 that abort copy operations.

Working Draft SCSI Primary Commands - 4 (SPC-4) 253

T10/BSR INCITS 513 Revision 37 17 May 2014

5.16.4.7 The COPY OPERATION ABORT command

Aborting a copy operation is not always possible with a task management function (e.g., a copy operation (see
5.16.4.3) that was originated by a third-party copy command with the IMMED bit set to one). The COPY
OPERATION ABORT command (see 6.3) provides an abort capability that is equivalent to an ABORT TASK
task management function for any copy operation that is able to be specified with a list identifier (see 5.16.4.2)
without regard for whether the copy operation is being performed in the foreground or background (see
5.16.4.3).

Before completing the COPY OPERATION ABORT command, the copy manager shall ensure that all
commands and data transfers generated by that copy operation have been terminated and are no longer
transferring data.

All foreground copy operations and background copy operations associated with the specified list identifier
shall be terminated with CHECK CONDITION status with the sense key set to COPY ABORTED and the
additional sense code set to COMMANDS CLEARED BY DEVICE SERVER (see 5.16.4.3).

5.16.5 Responses to the conditions that result from SCSI events

The effects on copy operations that are produced by the conditions that result from SCSI events (see SAM-5)
are shown in table 110.

Table 110 — Responses to the conditions that result from SCSI events

Condition that results from a SCSI event Effects of condition on copy operations
Power on All foreground and background copy operations shall be
Hard reset aborted as if a COPY OPERATION ABORT command
Logical unit reset (see 6.3) has been received for each copy operation.
Power loss expected
I_T nexus loss All foreground and background copy operations that
require access to the affected I_T Nexus shall be
aborted as if a COPY OPERATION ABORT command
has been received for each copy operation.

5.16.6 RODs and ROD tokens

5.16.6.1 RODs and ROD related tokens overview

A ROD provides a way to represent multiple bytes of data that may or may not be addressable as the content
of some media (e.g., one or more ranges of contiguous logical blocks that may be addressed as LBAs
or maintained as a point in time copy (see 5.16.6.2.3) of the contents of the specified LBA ranges). Each ROD
is created and maintained by a copy manager as specified by this standard.

The types of RODs are described in 5.16.6.2. The process of creating and populating a ROD is described in
5.16.6.3.

254 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

A ROD token is a token that a copy manager transfers to an application client to represent a specified ROD
outside the copy manager. Application clients may use ROD tokens as follows:

a) if a valid ROD token is received by the copy manager that created it, then that copy manager is able
to associate the ROD token with the original ROD and process the data represented by the ROD in
specified ways (e.g., the ways specified by segment descriptors in an EXTENDED COPY command);
b) if a ROD token is received by a copy manager other than the copy manager that created it, then the
receiving copy manager may be able to process the data that the ROD token represents by
communicating with the copy manager that created the ROD token. The communications between the
copy managers shall conform to the models described in this standard but are not required to use the
commands or data transfer mechanisms described in this standard; and
c) if a ROD token is transferred from one application client to another by a means outside the scope of
this standard, then the second application client may use the ROD token in any of the ways described
in this subclause.

The format of a ROD token is defined in 5.16.6.4. The interval of time during which the ROD token remains
valid is called the ROD token lifetime (see 5.16.6.7).

ROD management tokens (see 5.16.6.4) are used to manage (e.g., delete) ROD tokens.

Working Draft SCSI Primary Commands - 4 (SPC-4) 255

T10/BSR INCITS 513 Revision 37 17 May 2014

5.16.6.2 ROD types

5.16.6.2.1 ROD types overview

A copy manager uses the ROD types shown in table 111.

Table 111 — ROD types

Type codes
Type code Type code range defined by
ranges applicability this standard Description Reference
0000 0000h Copy manager 0000 0000h ROD type specified by command
internal ROD ROD token definition a
0000 0001h to Reserved
0000 FFFFh
0001 0000h to Any device type 0001 0000h Access upon reference 5.16.6.2.2
FEFF FFFFh 0080 0000h Point in time copy – default 5.16.6.2.3.2
0080 0001h Point in time copy 5.16.6.2.3.3
– change vulnerable
0080 0002h Point in time copy 5.16.6.2.3.4
– persistent
0080 FFFFh Point in time copy – any 5.16.6.2.3.5
all others Reserved
in this range
applicable
FF00 0000h to
Device type specific command
FFFF FFEFh
standard
FFFF FFF0h to Vendor specific ROD token body and ROD token extension (see 5.16.6.4 and
FFFF FFFFh 5.16.6.5)
a Some commands (e.g., an EXTENDED COPY command with the ROD CSCD descriptor (see 6.4.5.9)
in the parameter list (see 5.16.7.1)) use this ROD type code when processing a ROD token received by
the copy manager. Details of such usage are specific to the command.

If a third-party copy command requests the creation of a ROD and the copy manager does not have sufficient
resources to create or maintain the ROD, then the copy manager shall terminate the command with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
INSUFFICIENT RESOURCES TO CREATE ROD.

A copy manager shall indicate the types of RODs it supports in the Supported ROD Types third-party copy
descriptor (see 7.8.17.9) in the Third-party Copy VPD page.

5.16.6.2.2 Access upon reference type RODs

Access upon reference type RODs are RODs in which the bytes are represented by addressing information
(e.g., their LBAs for block devices). The copy manager that creates the ROD is not required to:

a) access the bytes until the ROD is used as a copy source or copy destination; or
b) maintain any specific data contents in association with the ROD.

256 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

An access upon reference type ROD shall remain valid as long as the addresses for the bytes remain valid
(e.g., a MODE SELECT command that decreases the number of logical blocks on a block device in a way that
eliminates one of the LBAs in an access upon reference type ROD causes the ROD to become invalid).
Invalidating a ROD in this way may cause it to become invalid before its specified lifetime (see 5.16.6.7) has
elapsed.

5.16.6.2.3 Point in time copy RODs

5.16.6.2.3.1 Point in time copy RODs overview

Point in time copy RODs are RODs for which the data returned when the ROD is used as a copy source is the
data that was present when the ROD was populated (see 5.16.6.3). The copy manager that creates the ROD
shall maintain the data that populates the ROD for as long as the ROD remains valid (see 5.16.6.7). The
method that the copy manager uses to maintain the data is outside the scope of this standard.

If the copy manager is unable to maintain the data that populates a point in time copy ROD, the copy manager
shall invalidate this type of ROD. Invalidating a ROD in this way may cause it to become invalid before its
specified lifetime (see 5.16.6.7) has elapsed.

If a third-party copy command that originates a copy operation (see table 108 in 5.16.3) specifies a point in
time copy ROD as a copy destination, then the copy manager shall terminate the copy operation (see
5.16.4.3) originated by the command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

5.16.6.2.3.2 Point in time copy – default type RODs

A point in time copy – default type ROD is a point in time copy ROD (see 5.16.6.2.3.1) for which the method
that maintains the data that populates the ROD is vendor specific.

5.16.6.2.3.3 Point in time copy – change vulnerable type RODs

A point in time copy – change vulnerable type ROD is a point in time copy ROD (see 5.16.6.2.3.1) for which
the copy manager shall create the ROD using the method that consumes the fewest resources without regard
for whether this increases the chance that the ROD may become invalid before its specified lifetime (see
5.16.6.7) has elapsed.

The copy manager may invalidate this type of ROD if the data that populated that ROD when it was created is
modified (e.g., by a write command) or becomes invalid (e.g., a MODE SELECT command decreases the
number of blocks on a logical blocks device in a way that eliminates one of the LBAs in the ROD).

5.16.6.2.3.4 Point in time copy – persistent type RODs

A point in time copy – persistent type ROD is a point in time copy ROD (see 5.16.6.2.3.1) for which the copy
manager shall maintain the data present when the ROD was populated for the ROD's specified lifetime (see
5.16.6.7) regardless of modifications to the data that populated the ROD when it was created.

A point in time copy – persistent type ROD may become invalidated before the specified lifetime for reasons
other than a modification to the data that populated the ROD when it was created (see 5.16.6.7).

Working Draft SCSI Primary Commands - 4 (SPC-4) 257

T10/BSR INCITS 513 Revision 37 17 May 2014

5.16.6.2.3.5 Point in time copy – any type RODs

A point in time copy – any type ROD is a point in time copy ROD (see 5.16.6.2.3.1) for which the copy
manager shall create the ROD using one of the following ROD types, in order of preference:

1) point in time copy – persistent (see 5.16.6.2.3.4); or

2) point in time copy – change vulnerable (see 5.16.6.2.3.3).

If a ROD token (see 5.16.6.4 and 5.16.6.5) is returned for a point in time copy – any type ROD, the value in
the ROD TOKEN field shall indicate the type of ROD the copy manager created (e.g., 0080 0001h for point in
time copy – change vulnerable).

5.16.6.3 Populating a ROD or ROD token

The content of a ROD is established when the ROD is populated. Details of how a ROD is populated are
defined by the command or commands that cause the ROD to become populated.

After a ROD is populated, it may be:

a) used by later processing steps defined by the command that caused the ROD to be populated (i.e.,
used inside the copy manager that created the ROD); or
b) used to create a ROD token (see 5.16.6.4) that may be used by application clients and copy
managers in the ways described in 5.16.6.1.

Commands are not required to provide a means to use a ROD inside the copy manager, but any ROD tokens
that a copy manager creates during the processing of a command shall be made available for transfer to the
application client using the RECEIVE ROD TOKEN INFORMATION command (see 6.28).

After the completion of a copy operation (see 5.16.4.3), the copy manager shall preserve all created ROD
tokens for a vendor specific period of time. The application client should retrieve the ROD tokens using the
RECEIVE ROD TOKEN INFORMATION command as soon as possible after the completion of the copy
operation to ensure that the data is not discarded by the copy manager. The copy manager shall discard the
parameter data for the created ROD tokens:

a) after all the ROD tokens created by a specific copy operation (see 5.16.4.3) have been transferred
without errors to the application client;
b) if a RECEIVE ROD TOKEN INFORMATION command has been received on the same I_T nexus with
a matching list identifier (see 5.16.4.2), with the ALLOCATION LENGTH field set to zero;
c) if another a third-party command that originates a copy operation (see table 108 in 5.16.3) is received
on the same I_T nexus and the list identifier matches the list identifier associated with the ROD
tokens;
d) if the copy manager detects a logical unit reset condition or I_T nexus loss condition (see SAM-5); or
e) if the copy manager requires the resources used to preserve the data.

The copy manager shall not discard the data returned by a RECEIVE ROD TOKEN INFORMATION command
in response to:

a) an ABORT TASK task management function (see SAM-5); or

b) a COPY OPERATION ABORT command (see 6.3).

The format of a ROD token is defined in 5.16.6.4. The interval of time during which the ROD token remains
valid is called the ROD token lifetime (see 5.16.6.7).

258 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If a third-party copy command attempts to populate a ROD with the same data more than one time (e.g.,
specifying the same LBA twice), then the copy manager shall terminate the copy operation (see 5.16.4.3)
originated by the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST,
and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

EXAMPLE 1 – The EXTENDED COPY(LID4) command (see 6.4) defines a CSCD descriptor that establishes an internal
ROD and segment descriptors that populate that ROD. The populated ROD may be used by other segment descriptors,
and may be returned as a ROD token using the methods described in this subclause.

EXAMPLE 2 – The POPULATE TOKEN command (see SBC-3) establishes and populates a ROD whose only use during
the processing of the POPULATE TOKEN command is in the creation of a ROD token that is returned using the methods
described in this subclause.

Working Draft SCSI Primary Commands - 4 (SPC-4) 259

T10/BSR INCITS 513 Revision 37 17 May 2014

5.16.6.4 ROD token format

The ROD token format is shown in table 112.

Table 112 — ROD token format

Bit
7 6 5 4 3 2 1 0
Byte
ROD token header
0 (MSB)
•• • ROD TYPE
3 (LSB)
4
Reserved
5
6 (MSB)
ROD TOKEN LENGTH (n-7)
7 (LSB)
ROD token body (if any)
8 (MSB)
•• • COPY MANAGER ROD TOKEN IDENTIFIER
15 (LSB)
16
•• • CREATOR LOGICAL UNIT DESCRIPTOR
47
48 (MSB)
•• • NUMBER OF BYTES REPRESENTED
63 (LSB)
64
•• • ROD token type specific data
95
ROD token extension (if any)
96
•• • Device type specific data
127
128
ROD token type and copy manager
•• •
specific data
n

Every ROD token shall include the ROD TYPE field and the ROD TOKEN LENGTH field. Except for the ROD TYPE
field and the ROD TOKEN LENGTH field, the definition for any ROD token format may not include the other fields
shown in table 112. The COPY MANAGER ROD TOKEN IDENTIFIER field, CREATOR LOGICAL UNIT DESCRIPTOR field,
NUMBER OF BYTES REPRESENTED field, and ROD token type specific data bytes shall be included in the ROD
token body if:

a) information about the ROD token is returned by the REPORT ALL ROD TOKENS command (see
6.31); or
b) any fields are defined in the ROD token extension.

260 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

EXAMPLE – The block device zero ROD token (see SBC-3) has a value selected from table 111 (see 5.16.6.2.1) in the
ROD TYPE field, and the ROD TOKEN LENGTH field set to 01F8h. All bytes in the ROD token body and ROD token extension
are reserved. This is a valid ROD token format because the block device zero ROD token is not returned by the REPORT
ALL ROD TOKENS command.

Commands that manage ROD tokens (e.g., the REPORT ALL ROD TOKENS command (see 6.31)) use a
ROD management token that consists of the ROD token header and the ROD token body in the ROD token
being managed (i.e., the ROD token extension is omitted in ROD management tokens). The ROD TOKEN
LENGTH field is not modified when a ROD management token is built from a ROD token (i.e., the ROD TOKEN
LENGTH field does not indicate the length of the ROD management token).

The ROD TYPE field (see table 111 in 5.16.6.2.1) indicates the use and content of the ROD token bytes that
follow the header.

The ROD TOKEN LENGTH field indicates the number of bytes that follow in the ROD token. The minimum size of
a ROD token shall be 512 bytes (i.e., the minimum value in the ROD TOKEN LENGTH field is 01F8h). Bytes in
unused ROD token fields shall be reserved (e.g., in a ROD token that does not include the ROD token body,
the bytes assigned to the COPY MANAGER ROD TOKEN IDENTIFIER field, CREATOR LOGICAL UNIT DESCRIPTOR field,
and NUMBER OF BYTES REPRESENTED field are reserved).

If present, the COPY MANAGER ROD TOKEN IDENTIFIER field contains a value that differentiates this ROD token
from all other valid ROD tokens created by and known to a specific copy manager. No two ROD tokens known
to a specific copy manager shall have the same value in the COPY MANAGER ROD TOKEN IDENTIFIER FIELD. After
a ROD token becomes invalid, the copy manager should not reuse the copy manager ROD token identifier
value from that ROD token in another ROD token for as long as possible, and shall not reuse that value until
at least 50 000 ROD tokens have been created by that copy manager.

If present, the CREATOR LOGICAL UNIT DESCRIPTOR field contains an Identification Descriptor CSCD descriptor
(see 6.4.5.6) for the logical unit that contains the copy manager that created the ROD token. That
Identification Descriptor CSCD descriptor shall contain a designation descriptor with the DESIGNATOR TYPE
field set to:

a) 2h (i.e., EUI-64-based); or
b) 3h (i.e., NAA).

If present, the NUMBER OF BYTES REPRESENTED field is set to the total number of bytes that the ROD
token represents. If the number of bytes represented by the ROD token is unknown or greater than
FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFEh, then the NUMBER OF BYTES REPRESENTED field shall be set
to FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFh. Command standards may define restrictions on the
contents of the NUMBER OF BYTES REPRESENTED field.

If present, the ROD token type specific data contains one or more fields whose contents are based on the
ROD token type.

If present, the device type specific data contains one or more fields whose contents are defined by the
command standard for the device type associated with the copy manager that created the ROD token.

If present, the ROD token type and copy manager specific data contains one or more fields whose contents
are dependent on the ROD token type and the copy manager that created the ROD token.

Working Draft SCSI Primary Commands - 4 (SPC-4) 261

T10/BSR INCITS 513 Revision 37 17 May 2014

5.16.6.5 Generic ROD tokens

5.16.6.5.1 Generic ROD token format

Unless a different format is defined, ROD tokens for the ROD types other than 00h (see table 111 in
5.16.6.2.1) have the format shown in table 113.

Table 113 — Generic ROD token format

Bit
7 6 5 4 3 2 1 0
Byte
ROD token header
0 (MSB)
•• • ROD TYPE
3 (LSB)
4
Reserved
5
6 (MSB)
ROD TOKEN LENGTH (n-7)
7 (LSB)
ROD token body
8 (MSB)
•• • COPY MANAGER ROD TOKEN IDENTIFIER
15 (LSB)
16
•• • CREATOR LOGICAL UNIT DESCRIPTOR
47
48 (MSB)
•• • NUMBER OF BYTES REPRESENTED
63 (LSB)
64
•• • Reserved
95
ROD token extension
96
•• • Device type specific data
127
128
•• • TARGET DEVICE DESCRIPTOR
t
t+1
•• • EXTENDED ROD TOKEN DATA
n

The ROD TYPE field is defined in 5.16.6.4 and the coded values that may be used in the ROD TYPE field are
defined in 5.16.6.2.1. The ROD TYPE field shall be set to one of the values shown in table 114. The ROD TYPE

262 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

field shall not be set to 0080_FFFFh (i.e., point in time copy – any) (see 5.16.6.2.3.5).

Table 114 — ROD TYPE field in generic ROD

TARGET DEVICE
ROD TOKEN DESCRIPTOR
LENGTHfield FIELD size ROD type
Code Description contents (in bytes) Reference
0001 0000h Access upon reference 01F8h 128 5.16.6.2.2
0080 0000h Point in time copy – default 01F8h 128 5.16.6.2.3.2
0080 0001h Point in time copy 01F8h 128 5.16.6.2.3.3
– change vulnerable
0080 0002h Point in time copy 01F8h 128 5.16.6.2.3.4
– persistent
all others see table 111 in 5.16.6.2.1

The ROD TOKEN LENGTH field is defined in 5.16.6.4, and shall be set to the value shown in table 114 based on
the contents of the ROD TYPE field.

The COPY MANAGER ROD TOKEN IDENTIFIER field, CREATOR LOGICAL UNIT DESCRIPTOR field, and NUMBER OF
BYTES REPRESENTEDfield are defined in 5.16.6.4.

The device type specific data is specified by the command standard for the peripheral device type indicated by
the CREATOR LOGICAL UNIT DESCRIPTOR field (see 5.16.6.4) (e.g., for peripheral device type 00h, see SBC-3).

The TARGET DEVICE DESCRIPTOR field contains a designation descriptor for the SCSI target device (see 7.8.6)
that contains the logical unit indicated by the descriptor in CREATOR LOGICAL UNIT DESCRIPTOR field. The
designation descriptor shall have the ASSOCIATION field set to 10b (i.e., SCSI target device) and the
DESIGNATOR TYPE field set to:

a) 2h (i.e., EUI-64-based);
b) 3h (i.e., NAA); or
c) 8h (i.e., SCSI name string).

The EXTENDED ROD TOKEN DATA field shall contain at least 256 bits of secure random number material (see
4.4) generated when the ROD token was created, and may contain information that is used by the copy
manager that created the ROD token to process the ROD token (e.g., an expiration time in a vendor specific
format). The EXTENDED ROD TOKEN DATA field should not contain data that enables an entity outside the SCSI
target device in which the ROD token was created to determine the data (e.g., LBAs or logical blocks) that the
ROD token represents.

Those portions of the EXTENDED ROD TOKEN DATA field that do not contain defined values should be set to
unpredictable random values. The contents of the EXTENDED ROD TOKEN DATA field may be defined to contain:

a) zero or more values that are based on the ROD represented by the generic ROD token (e.g., pointers,
expiration time); and
b) zero or more values used by the copy manger to determine whether the generic ROD token is valid
(e.g., cryptographic integrity check values, message authentication codes, digital signatures).

Working Draft SCSI Primary Commands - 4 (SPC-4) 263

T10/BSR INCITS 513 Revision 37 17 May 2014

5.16.6.5.2 Validating generic ROD tokens

5.16.6.5.2.1 Overview of validating generic ROD tokens

A copy manager shall ensure that a generic ROD token (see 5.16.6.5.1) is valid before performing any action
based on the contents of that ROD token. The determination of whether a generic ROD token is valid shall be
performed only by the copy manager that created that ROD token. If the processing copy manager is in the
same SCSI target device as the copy manager that created the ROD token, then the two copy managers may
exchange information using a method outside the scope of this standard to accomplish the required validation.

If a copy manager is unable to validate the generic ROD token, then no data shall be transferred by the
command that contains the invalid ROD token, and the copy operation (see 5.16.4.3) shall be terminated as
described in 5.16.6.5.2.3.

If a command containing a generic ROD token is processed by a copy manager that is not in the same SCSI
target device as the copy manager that created the ROD token, then the actions of the processing copy
manager depend on the contents of the REMOTE TOKENS field in the ROD Features third-party copy descriptor
(see 7.8.17.8) as follows:

a) if the REMOTE TOKENS field is set to 0h, the processing copy manager may consider the generic ROD
token to be invalid without contacting another copy manager (e.g., as a result of the processing copy
manager being unable to identify or contact the copy manager that created the ROD token) and
terminate the command that contains the ROD token as described in 5.16.6.5.2.3; or
b) if the REMOTE TOKENS field is not set to 0h, the processing copy manager shall:
1) use the information in the generic ROD token to locate the copy manager that created the ROD
token;
2) communicate the generic ROD token to the creating copy manager with a request to determine
the validity of the ROD token (e.g., send an EXTENDED COPY command with a verify CSCD
segment descriptor (see 6.4.6.9)); and
3) if the generic ROD token is invalid, the copy manager shall terminate the copy operation (see
5.16.4.3) as described in 5.16.6.5.2.3.

The process of determining the validity of a generic ROD token involves the following checks. A generic ROD
token:

a) shall be invalid if the contents the generic ROD token do not match the equivalent information stored
by the copy manager for any ROD token created by the copy manager as described in this subclause;
b) should be invalid if the generic ROD token lifetime has elapsed (see 5.16.6.7); and
c) may be invalid based on vendor specific tests.

The check for whether a generic ROD token matches a generic ROD token created by the copy manager may
use:

a) exact validation that detects all differences (e.g., by comparing the generic ROD token to copies of
valid generic ROD tokens saved by the copy manager when those generic ROD tokens were created)
to which the additional requirements stated in 5.16.6.5.2.2 do not apply; or
b) inexact validation that does not detect all differences (e.g., by comparing a hash of the generic ROD
token to hashes of valid generic ROD tokens) and implementation of the additional requirements
described in 5.16.6.5.2.2.

If a copy manager determines that a generic ROD token is invalid, the copy manager shall terminate the copy
operation (see 5.16.4.3) as described in 5.16.6.5.2.3.

264 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.16.6.5.2.2 Inexact validation of generic ROD tokens

A copy manager may use the SHA-256 secure hash function to:

a) compute a hash for each generic ROD token as part of creating that generic ROD token; and
b) compare the equivalent hash for any generic ROD token to be validated to the precomputed hash
values for each of the generic ROD tokens that the copy manager considers valid.

Any generic ROD token inexact validation process shall detect generic ROD tokens that were never created
by the copy manager with a certainty that is greater than or equal to that of SHA-256 hash (e.g., use of the
SHA-512 secure hash meets this requirement).

A copy manager that uses a secure hash function as the only means of generic ROD token validation is
exposed to collision attacks against that hash function. A more secure technique is to use the secure hash as
part of a keyed cryptographic integrity check (e.g., the HMAC SHA-256 message authentication code), with a
secret key that is confidential to the copy manager.

Copy managers shall not use any of the following computational techniques as the only means of generic
ROD token validation:

a) any form of CRC;

b) any form of arithmetic checksum;
c) an arithmetic hash that is not a secure hash; and
d) a secure hash with a known collision resistance that is less than that of SHA-256 (e.g., most secure
hash functions whose result contains less than 256 bits).

5.16.6.5.2.3 Validation errors for generic ROD tokens

If the copy manager determines that a generic ROD token is invalid, the copy manager shall:

a) not perform any of the data transfers requested by the command that specified the invalid ROD token;
b) terminate the copy operation (see 5.16.4.3); and
c) return an error using the method described in 5.16.4.3 with CHECK CONDITION status with the
sense key and additional sense code associated with the highest priority error detected from among
those shown in table 115.

Working Draft SCSI Primary Commands - 4 (SPC-4) 265

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 115 — Generic ROD token errors sorted by reporting importance

Error detected Sense key Additional sense code Priority

Internal inconsistency or corruption ILLEGAL REQUEST INVALID TOKEN Highest
problem in the generic ROD token OPERATION, TOKEN
format CORRUPT
Generic ROD token type that is not ILLEGAL REQUEST INVALID TOKEN
supported by the copy manager OPERATION,
UNSUPPORTED
TOKEN TYPE
Remote generic ROD token a and ILLEGAL REQUEST INVALID TOKEN
the REMOTE TOKENS field b is set OPERATION, REMOTE
to 0h TOKEN USAGE NOT
SUPPORTED
Remote generic ROD token a with COPY ABORTED COPY TARGET DEVICE
the REMOTE TOKENS field b not set to NOT REACHABLE
0h for which the copy manager is
unable to contact the copy manager
that created the ROD token
Remote generic ROD token a with sense key returned additional sense code
the REMOTE TOKENS field b not set to by creating copy returned by creating copy
0h for which the creating copy manager manager
manager returns an error
Generic ROD token with a lifetime ILLEGAL REQUEST INVALID TOKEN
that has expired or an inactivity OPERATION,
timeout that has been exceeded c TOKEN EXPIRED
Generic ROD token that does not ILLEGAL REQUEST INVALID TOKEN
match any valid generic ROD token OPERATION,
created by the copy manager TOKEN UNKNOWN
Generic ROD token that has been ILLEGAL REQUEST INVALID TOKEN
revoked by a system administrator c OPERATION,
TOKEN REVOKED
Generic ROD token that has been ILLEGAL REQUEST INVALID TOKEN
deleted in response to an application OPERATION, TOKEN
client request c DELETED
Generic ROD token that has an error ILLEGAL REQUEST INVALID TOKEN Lowest
not described elsewhere in this table OPERATION, CAUSE
NOT REPORTABLE
a
A remote generic ROD token is a generic ROD token that was created by a copy manager that is
not located in the same SCSI target device as the processing copy manager.
b
The REMOTE TOKENS field is in the ROD Features third-party copy descriptor (see 7.8.17.8).
c
See 5.16.6.7 for details about generic ROD tokens:
a) whose lifetime that has expired;
b) whose inactivity timeout that has been exceeded;
c) that have been revoked by a system administrator; or
d) that have been deleted in response to an application client request.

266 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.16.6.6 ROD token usage

If the ROD token lifetime is long enough to allow all of the following steps to be processed and no other factors
cause the ROD token to become invalid, then creation and use of the ROD token in multiple third-party copy
commands is accomplished as follows:

1) create one or more ROD token (see 5.16.7.5.2) in an initial third-party copy command (e.g.,
EXTENDED COPY(LID4) command (see 6.4) or POPULATE TOKEN command (see SBC-3));
2) retrieve the ROD tokens using the RECEIVE ROD TOKEN INFORMATION command (see 6.28); and
3) one or more subsequent third-party copy commands (e.g., EXTENDED COPY(LID4) command or
WRITE USING TOKEN command (see SBC-3)) may specify the ROD token in the parameter list.

Details of the how the EXTENDED COPY commands are used in the steps shown in this subclause are
described in 5.16.7.6. Details of the how the POPULATE TOKEN command and WRITE USING TOKEN
command are used in the steps shown in this subclause are described in SBC-3.

If a copy manager processes a third-party copy command that contains a valid ROD token in the parameter
list, then the handling of access to the ROD specified by the ROD token and to the data represented by that
ROD depends on the relationship of the copy manager that processes the command to the copy manager that
created the ROD token as show in table 116.

Table 116 — Copy manager relationships for processing ROD tokens

Relationship between REMOTE TOKENS

the copy manager that field a contents
processes the command returned by the
and the copy manager that processing copy
created the ROD token manager Description
The two copy managers are No errors shall be returned regarding access to the
n/a
the same valid ROD token's contents.
The processing copy manager shall:
a) communicate with the copy manager that
The two copy managers are in created the ROD token to access the data
n/a
the same SCSI target device that the ROD token represents; and
b) not return any errors regarding access to the
valid ROD token's contents.
The processing copy manager shall terminate the
0h copy operation (see 5.16.4.3) as described in
5.16.6.5.2.3.
The processing copy manager:
a) shall attempt to communicate with the
The two copy managers are in copy manager that created the ROD token
different SCSI target devices to access the data that the ROD token
not 0h represents; and
b) may return errors based on the inability
to locate or communicate with the copy
manager that created the ROD token
(see 5.16.6.5.2.3).
a The REMOTE TOKENS field is in the ROD Features third-party copy descriptor (see 7.8.17.8).

Working Draft SCSI Primary Commands - 4 (SPC-4) 267

T10/BSR INCITS 513 Revision 37 17 May 2014

A copy manager indicates that it is capable of communicating with a copy manager that is not located in the
same SCSI target device as itself by setting the REMOTE TOKENS field to a value other than 0h in the ROD
Features third-party copy descriptor (see 7.8.17.8).

Whenever one copy manager communicates with another copy manager to access the data that the ROD
token represents, the communication is modelled as the sending of EXTENDED COPY(LID4) commands (see
6.4) and RECEIVE COPY DATA(LID4) commands (see 6.20). However, any communication between copy
managers that accomplishes the equivalent of this result conforms to this standard.

EXAMPLE – The process by which one copy manager obtains all the bytes in a ROD may use an EXTENDED
COPY(LID4) command that contains the blockblock&application client segment descriptor (see 6.4.6.4) with a null block
device logical unit (see table 148 in 6.4.6.1) as the copy destination followed by a RECEIVE COPY RESULTS(LID4)
command that retrieves the held data.

In addition to converting a ROD token created by another copy manger to the data that the ROD token
represents, a copy manager may indicate that it is capable of communicating with another copy manager in
another SCSI target device for the purpose of creating a ROD token by setting the REMOTE TOKENS field to 6h
in the ROD Features third-party copy descriptor (see 7.8.17.8).

5.16.6.7 ROD token lifetime

When a ROD token is created, the copy manager that creates the ROD token assigns it a lifetime interval
based on inputs to the ROD token creation process (e.g., the REQUESTED ROD TOKEN LIFETIME field in the ROD
CSCD descriptor (see 6.4.5.9)) that is used as follows:

a) until the lifetime elapses, the copy manger should not make the ROD token invalid; and
b) after the lifetime elapses, the copy manager should invalidate the ROD token.

When a ROD token is created, the copy manager that creates the ROD token assigns it an inactivity timeout
that is based on inputs to the ROD token creation process (e.g., the REQUESTED ROD TOKEN INACTIVITY TIMEOUT
field in the ROD CSCD descriptor (see 6.4.5.9)) that is used as follows:

a) after the completion of a third-party copy command that originates a copy operation (see table 108 in
5.16.3) that specifies the ROD token, the copy manager should not make the ROD token invalid
before the inactivity timeout has expired; and
b) after the inactivity timeout has expired, the copy manager should invalidate the ROD token.

A ROD token may be invalidated for reasons other than its lifetime elapsing or inactivity timeout expiring,
including the following:

a) an application client request to delete a ROD token (e.g., setting the DEL_TKN bit to one in the ROD
CSCD descriptor (see 6.4.5.9) of an EXTENDED COPY command);
b) a ROD token cancellation made by the copy manager in response to operating conditions (e.g., point
in time copy (see 5.16.6.2.3) processing requirements, excessive writes to the represented data,
resource reclamation to create a new ROD token); and
c) a system administrator request to revoke a ROD token for management reasons.

If any of the conditions described in this subclause cause a ROD token to become invalid, then the copy
manager shall maintain a record of them for reporting purposes (see 5.16.6.5.2.3) for at least the lifetime of
the ROD token established at the time the ROD token was created, and should maintain the record for twice
the lifetime of the ROD token.

268 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.16.7 The EXTENDED COPY command

5.16.7.1 EXTENDED COPY parameter list

The EXTENDED COPY(LID4) command (see 6.4) and EXTENDED COPY(LID1) command (see 6.5) use a
parameter list with several elements to define a flexible interface to third-party copy functions (see figure 18).

Parameter List Parameter List Allowed References

Element Descriptions Elements Segment descriptors reference
CSCD descriptors to specify
General information and sizes of Header the copy source and copy
other parameter list elements destination logical unit.

Information used to locate and CSCD

verify the copy source and copy Segment descriptors reference
descriptors
destination logical units the inline data to transfer spec-
ified data (e.g., tape labels) to
the copy destination (see
Instructions for each copy Segment 6.4.6.6).
function to be performed descriptors
CSCD descriptors reference
the inline data for structures
Data used by CSCD descriptors (e.g., ROD tokens (see
or Segment descriptors, Inline
5.16.6)) that do not fit in a
often large sized fields data
CSCD descriptor.

Note – If a small amount of data needs to be transferred from the parameter list to the copy destination,
then the embedded data to stream device operation segment descriptor (see 6.4.6.7) may be more
efficient than referencing the inline data.

Figure 18 — EXTENDED COPY parameter list structure diagram

EXTENDED COPY parameter list elements that are not used are not included in the parameter list (e.g., the
length of the inline data element is zero if no inline data is referenced).

5.16.7.2 EXTENDED COPY command processing

To process an EXTENDED COPY command, the copy manager:

1) shall determine the global processing conditions for the command (e.g., the value of the IMMED bit
(see 6.4.2));
2) shall determine the first parameter list byte for each parameter list element shown in figure 18 (see
5.16.7.1) based on fields in the header;
3) may validate the contents of one or more CSCD descriptors (see 5.16.7.1) and terminate the
EXTENDED COPY command if errors are detected;
4) may validate the contents of one or more segment descriptors and terminate the EXTENDED COPY
command if errors are detected;
5) depending on the value of the IMMED bit in an EXTENDED COPY(LID4) command:
A) shall return command completion if the IMMED bit is set to one; or

Working Draft SCSI Primary Commands - 4 (SPC-4) 269

T10/BSR INCITS 513 Revision 37 17 May 2014

B) shall not return status for the command until the copy operation (see 5.16.4.3) is completed or
terminated if the IMMED bit is set to zero;
and
6) shall process the segment descriptors in the order in which they appear in the parameter list as
described in this subclause.

The copy functions performed by an EXTENDED COPY command are specified by the segment descriptors.
All other elements of the EXTENDED COPY parameter list (see 5.16.7.1) are present to support the segment
descriptors in their specification of the copy functions to be performed.

If a CSCD descriptor is referenced by a segment descriptor (see 5.16.7.1), the information in that CSCD
descriptor should be validated at the time the referencing segment descriptor is processed. The SCSI devices
participating in a SCSI domain may change between the time that processing of an EXTENDED COPY
command begins and the time that processing of a specific segment descriptor begins.

The copy manager shall perform the copy functions specified by the segment descriptors (see 5.16.7.1) using
a model in which commands are sent from the copy manager application client to local device servers and/or
remote device servers. The specific commands sent by the copy manager to the copy sources and copy
destinations while processing the segment descriptors are vendor specific. Upon successful completion of the
copy operation (see 5.16.4.3), all copy sources and copy destinations that are stream devices (see SSC-4)
shall be positioned at deterministic locations such that they may be repositioned to the same location by the
application client with appropriate commands.

During the processing of a segment descriptor, the copy manager may be required to:

a) manage the movement of data from a copy source to a copy destination as follows:
A) read source data by issuing data input commands to the copy source;
B) process data in a way that may designate data as destination data (i.e., data intended for transfer
to the copy destination); and
C) write some or all of the destination data to the copy destination;
b) manage the movement of a specified portion of the embedded data or inline data to a copy
destination as follows:
A) designate the specified portion of the embedded data or inline data as destination data intended
for transfer to the copy destination; and
B) write some or all of the destination data to the copy destination;
or
c) perform functions that are specific to the peripheral device type (e.g., writing filemarks) to a copy
destination.

As part of processing a segment descriptor, the copy manager may verify the information in a CSCD
descriptor’s device specific fields. However, while verifying the information, the copy manager shall not send
any commands that change the position of read/write media on the CSCD without repositioning the media to
its original position. Any errors encountered while verifying the information shall be processed as described in
5.16.7.4.

The number of blocks to read and write, the number of bytes to process, and the nature of processing are
determined by:

a) the segment descriptor type code;

b) the parameters of the segment descriptor; and
c) the amount of residual source or destination data retained from the previous segment, if any.

270 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Except as otherwise specified by particular segment descriptor type codes, the processing of a segment
descriptor is performed as follows:

a) just enough whole block reads shall be performed to supply, together with residual source data from
the previous segment or segments, the number of bytes to be processed;
b) processing consists of removing bytes from the source data and designating them as destination
data, without change; and
c) as many whole block writes as possible shall be performed with the destination data, including any
residual destination data from the previous segment or segments.

Any residual source data from the previous segment or segments shall be processed before any data read
from the copy source during processing of the current segment descriptor. Any residual destination data from
the previous segment or segments shall be written before any data processed during processing of the
current segment descriptor.

Segment descriptor processing requirements that are specific to one or more segment descriptor type codes
are described in table 117 and the referenced subclauses.

Table 117 — Segment descriptor type specific copy manager processing requirements (part 1 of 2)

Segment descriptor type code Reference Description

00h (i.e., blockstream) or 6.4.6.2 The number of bytes processed is determined by
0Bh (i.e., blockstream&application the BLOCK DEVICE NUMBER OF BLOCKS field for the
client) copy source (see applicable type code definition
subclauses for details). a
02h (i.e., blockblock) with DC=0 or 6.4.6.4
0Dh (i.e., blockblock&application
client) with DC=0
02h (i.e., blockblock) with DC=1 or 6.4.6.4 The number of blocks or the byte range specified
0Dh (i.e., blockblock&application shall be output to the copy destination. If residual
client) with DC=1 destination data is sufficient to perform the output,
01h (i.e., streamblock) or 6.4.6.3 then no data shall be processed. Otherwise, just as
0Ch (i.e., streamblock&application much data as needed shall be processed (which
client) may involve reading data from the copy source)
so that the destination data (which includes any
6.4.6.11 residual destination data from the previous
09h (i.e., streamblock<o>)
segment) is sufficient. a
03h (i.e., streamstream) or 6.4.6.5 The number of bytes specified in the segment
0Eh (i.e., streamstream&application descriptor shall be processed. a
client)
04h (i.e., inlinestream) 6.4.6.6 The specified number of bytes of inline or
embedded data shall be appended to the desti-
05h (i.e., embeddedstream) 6.4.6.7
nation data, and no source data shall be processed.
6.4.6.8 The specified number of bytes shall be removed
06h (i.e., streamdiscard)
from the source data and discarded.
a
For segment descriptor type codes 0Bh, 0Ch, 0Dh and 0Eh, a copy of the processed data shall also be
held for retrieval by the application client (see 5.16.4.5).

Working Draft SCSI Primary Commands - 4 (SPC-4) 271

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 117 — Segment descriptor type specific copy manager processing requirements (part 2 of 2)

Segment descriptor type code Reference Description

07h (i.e., verify CSCD operation) 6.4.6.9 No data shall be processed and no reads or writes
10h (i.e., filemarktape) 6.4.6.13 shall be performed on CSCDs. Residual source or
destination data, if any, shall be retained or
11h (i.e., spacetape) 6.4.6.14 discarded as if the CAT bit were set to one.
12h (i.e., locatetape) 6.4.6.15
14h (i.e., register persistent reserva- 6.4.6.17
tion key)
15h (i.e., Third party persistent reser- 6.4.6.18
vations source I_T nexus)
08h (i.e., block<o>stream) 6.4.6.10 The required blocks shall be read from the copy
source, the designated byte range shall be
extracted as source data, and the designated
number of bytes shall be processed starting with
residual source data, if any.
0Ah (i.e., block<o>block<o>) 6.4.6.12 The source byte range specified shall be read into
source data, the number of bytes specified shall be
moved from source data to destination data, and
the specified destination byte range shall be written
using destination data.
0Fh (i.e., streamdiscard&application 6.4.6.8 The specified number of bytes shall be removed
client) from the source data and held for retrieval by the
application client.
13h (i.e., <i>tape<i>tape) 6.4.6.16 The data movement, if any, shall not involve
16h (i.e., <i>block<i>block) 6.4.6.19 processing as described in this subclause. Residual
source or destination data, if any, shall not be used
BEh (i.e., RODblock ranges(n)) 6.4.6.20 and shall be retained or discarded as if the CAT bit
BFh (i.e., RODblock range(1)) 6.4.6.21 were set to one.
a
For segment descriptor type codes 0Bh, 0Ch, 0Dh and 0Eh, a copy of the processed data shall also be
held for retrieval by the application client (see 5.16.4.5).

The results are outside the scope of this standard if:

a) the copy source LBA range overlaps the copy destination LBA range;
b) both LBA ranges are in the same logical unit; and
c) both LBA ranges are specified in the same segment descriptor.

272 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Reads and writes shall be performed using whole block transfer lengths determined by the block size, transfer
length, or both. Therefore some source data may remain unprocessed and some destination data may not
have been transferred at the end of a segment. If so, the residue shall be handled according to the CAT bit in
the segment descriptor and the PAD bits of the source and destination target descriptors, as defined in table
118.

Table 118 — PAD and CAT bit definitions

PAD bit in

Source Destination
CSCD CSCD CAT
descriptor descriptor bit Copy manager action
0 or 1 0 or 1 1 Any residual source data shall be retained as source data for a subse-
quent segment descriptor. Any residual destination data shall be
retained as destination data for a subsequent segment descriptor. It
shall not be an error if either the source CSCD ID or destination CSCD
ID index in the subsequent segment descriptor does not match the
corresponding CSCD ID index with which residual data was originally
associated. If the CAT bit is set to one in the last segment descriptor in
the parameter data (see 5.16.7.1), then any residual data shall be
discarded and this shall not be considered an error.
1 1 0 Any residual source data shall be discarded. Any residual destination
data shall be padded with zeroes to make a whole block transfer. a
0 1 0 Any residual source data shall be processed as if the CAT bit is set to
one (i.e., discarded on the last segment and retained otherwise). Any
residual destination data shall be padded with zeroes to make a whole
block transfer. a
1 0 0 Any residual source or destination data shall be discarded.
0 0 0 If there is residual source or destination data, the copy manager shall
terminate the copy operation (see 5.16.4.3) with CHECK CONDITION
status, with the sense key set to COPY ABORTED, and the additional
sense code set to UNEXPECTED INEXACT SEGMENT.
a
If the CAT bit is set to zero in the segment descriptor and the PAD bit is set to one in the destination
CSCD descriptor, then the copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK
CONDITION status, with the sense key set to COPY ABORTED, and the additional sense code set to
UNEXPECTED INEXACT SEGMENT if any of the following conditions are met:
a) if any residual destination data is present after writing the designated byte range for a segment
descriptor of type 09h (i.e., streamblock <o>) or 0Ah (i.e., block<o>block<o>); or
b) if any residual destination data is present after the designated number of blocks have been written
for a segment descriptor of type 02h (i.e., blockblock) with DC set to one, 0Dh (i.e., block block&
application client) with DC set to one, 01h (i.e., streamblock) or 0Ch (i.e., streamblock&
application client).

Working Draft SCSI Primary Commands - 4 (SPC-4) 273

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 119 defines the PAD bit handling for segment descriptors that have either no copy source or no copy
destination.

Table 119 — PAD bit processing if there is no copy source or copy destination

Segment descriptor type code Reference Description

04h (i.e., inlinestream) 6.4.6.6 Processing shall be as if the PAD is set to
zero for the source CSCD descriptor.
05h (i.e., embeddedstream) 6.4.6.7
06h (i.e., streamdiscard) Processing shall be as if the PAD is set to
6.4.6.8
0Fh (i.e., streamdiscard&application client) zero for the destination CSCD descriptor.

5.16.7.3 EXTENDED COPY command errors detected before segment descriptor processing starts

Errors may occur during processing of an EXTENDED COPY command before the first segment descriptor is
processed or before status is returned due to an IMMED bit set to one. These errors include invalid parameters
in the CDB or parameter data, invalid segment descriptors, and inability of the copy manager to continue
operating. In the event of such an exception condition, the copy manager shall:

a) terminate the EXTENDED COPY command with CHECK CONDITION status;

b) set the sense key to a value that describes the exception condition (i.e., not COPY ABORTED); and
c) not return a value in the INFORMATION field (see 4.5.4).

5.16.7.4 EXTENDED COPY command errors detected during processing of segment descriptors

Errors may occur after the copy manager has begun processing segment descriptors or after status has been
returned due to an IMMED bit set to one. These errors include invalid parameters in segment descriptors,
invalid segment descriptors, unavailable CSCDs referenced by CSCD descriptors, inability of the copy
manager to continue operating, and errors reported by a CSCD. If a copy manager command to a CSCD
returns CHECK CONDITION status, the copy manager shall recover the sense data associated with the
exception condition and clear any ACA condition associated with the CHECK CONDITION status.

The copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with
the sense key set to COPY ABORTED, and the additional sense code set to COPY TARGET DEVICE NOT
REACHABLE if it is not possible to complete processing of a segment descriptor as a result of:

a) the copy manager being unable to establish communications with a CSCD;

b) the CSCD not responding to an INQUIRY command; or
c) the data returned to the copy manager in response to an INQUIRY command indicating an
unsupported logical unit.

If it is not possible to complete processing of a segment descriptor as a result of the data returned in response
to an INQUIRY command indicates a device type that does not match the type in the CSCD descriptor, then
the copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the
sense key set to COPY ABORTED, and the additional sense code set to INCORRECT COPY TARGET
DEVICE TYPE.

If the copy manager has sends a command other than INQUIRY to a CSCD while processing a copy
operation (see 5.16.4.3) and the CSCD either fails to respond with status or responds with status other than
BUSY, TASK SET FULL, ACA ACTIVE, or RESERVATION CONFLICT, then the copy manager shall terminate
the copy operation with CHECK CONDITION status, with the sense key set to COPY ABORTED, and the
additional sense code set to THIRD PARTY DEVICE FAILURE.

274 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If a CSCD completes a command from the copy manager with a status of BUSY, TASK SET FULL, ACA
ACTIVE, or RESERVATION CONFLICT, then the copy manager shall either retry the command or terminate
the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the sense key set to COPY
ABORTED, and the additional sense code set to THIRD PARTY DEVICE FAILURE.

NOTE 20 - The copy manager is assumed to employ a vendor specific retry policy that minimizes time
consuming repetition of retries.

NOTE 21 - RESERVATION CONFLICT status is listed only to give the copy manager leeway in multi-port
cases. The copy manager may have multiple initiator ports that are capable of reaching a CSCD, and a
persistent reservation may restrict access to a single I_T nexus. The copy manager may need to try access
from multiple initiator ports to find the correct I_T nexus.

If a CSCD responds to an input or output request with a GOOD status but less data than expected is
transferred, then the copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK
CONDITION status, with the sense key set to COPY ABORTED, and the additional sense code set to COPY
TARGET DEVICE DATA UNDERRUN. If an overrun is detected, then the copy manager shall terminate the
copy operation with CHECK CONDITION status, with the sense key set to COPY ABORTED, and the
additional sense code set to COPY TARGET DEVICE DATA OVERRUN.

After an exception condition is detected during segment descriptor processing:

a) the copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status,
with the sense key set to COPY ABORTED;
b) the copy manager shall return the segment number of the segment that was being processed at the
time of the exception in the third and fourth bytes of the COMMAND-SPECIFIC INFORMATION field (see
4.5.5). The segment number is based on the relative position of the segment descriptor in the
parameter list (see 5.16.7.1) (i.e., the first segment descriptor in the parameter list is assigned
descriptor number zero, the second is assigned one, etc.);
c) if any data has been written to the copy destination for the segment being processed at the time the
error occurred, then the copy manager shall return the residual count for the segment in the
INFORMATION field (see 4.5.4) using units of:
A) bytes if the destination CSCD descriptor contains:
a) 03h (i.e., processor device) in the PERIPHERAL DEVICE TYPE field; or
b) 01h (i.e., sequential-access device) in the PERIPHERAL DEVICE TYPE field and the FIXED bit is
set to zero in the device type specific parameters;
or
B) copy destination blocks for all other cases.
The residual count shall be computed by subtracting the number of bytes or blocks successfully
written during the processing of the current segment from the number of bytes or blocks which would
have been written if all commands had completed with GOOD status and all READ commands had
returned the full data length requested. While computing the residual count, the copy manager shall
include only the results of commands successfully completed by a copy destination (i.e., commands
completed by a copy destination with GOOD status or with CHECK CONDITION status and the EOM
bit set to one in the sense data). If the copy manager has used out of order transfers, then the residual
count shall be based only on the contiguous transfers completed without error starting at relative byte
zero of the segment (i.e., any successfully completed transfers farther from relative byte zero than the
first incomplete or unsuccessful transfer shall not contribute to the computation of the residual count).
If no data has been written to the copy destination for the segment being processed at the time the
error occurred, then the copy manager shall not return a value in the INFORMATION field (see 4.5.4).
Segment descriptors that do not specify a transfer count shall not have a valid residual count;
d) if the exception condition is reported by the copy source, then:
A) if fixed format sense data (see 4.5.3) is being returned, then the first byte of the
COMMAND-SPECIFIC INFORMATION field shall be set to the starting byte number, relative to the first

Working Draft SCSI Primary Commands - 4 (SPC-4) 275

T10/BSR INCITS 513 Revision 37 17 May 2014

byte of sense data, of an area that contains the status byte and sense data delivered to the copy
manager by the copy source. The status byte and sense data shall not be modified by the copy
manager. A zero value indicates that no status byte and sense data is being returned for the copy
source; or
B) if descriptor format sense data (see 4.5.2) is being returned, then the status byte and sense data
delivered to the copy manager by the copy source shall be returned in a forwarded sense data
descriptor (see 4.5.2.7) with the SOURCE field set to 1h. The status byte shall not be modified by
the copy manager. The sense data may be truncated by the copy manager but shall not be
modified in any other way. If the sense data is truncated, then the FSDT bit in the forwarded
additional sense data descriptor shall be set to one;
e) if the exception condition is reported by the copy destination, then:
A) if fixed format sense data (see 4.5.3) is being returned, then the second byte of the
COMMAND-SPECIFIC INFORMATION field shall be set to the starting byte number, relative to the first
byte of sense data, of an area that contains the status byte and sense data delivered to the copy
manager by the copy destination. The status byte and sense data shall not be modified by the
copy manager. A zero value indicates that no status byte and sense data is being returned for the
copy destination; or
B) if descriptor format sense data (see 4.5.2) is being returned, then the status byte and sense data
delivered to the copy manager by the copy destination shall be returned in a forwarded sense
data descriptor (see 4.5.2.7) with the SOURCE field set to 2h. The status byte shall not be modified
by the copy manager. The sense data may be truncated by the copy manager but shall not be
modified in any other way. If the sense data is truncated, then the FSDT bit in the forwarded
additional sense data descriptor shall be set to one;
f) if segment processing is terminated as a result of a CSCD is unreachable or as the result of a failure
in a command sent to a CSCD, then the sense key specific information shall be set as described in
4.5.2.4.5, with the FIELD POINTER field indicating the first byte of the CSCD descriptor that specifies the
CSCD;
g) if, during the processing of a segment descriptor, the copy manager detects an error in the segment
descriptor, then the sense key specific information shall be set as described in 4.5.2.4.5, with the
FIELD POINTER field indicating the byte in error. The FIELD POINTER field may be used to indicate an
offset into either the parameter data or the segment descriptor. The SD bit is used to differentiate
between these two cases. The SD bit shall be set to zero to indicate the FIELD POINTER field is set to an
offset from the start of the parameter data. The SD bit shall be set to one to indicate the FIELD POINTER
field is set to an offset from the start of the segment descriptor; and
h) if the LIST ID USAGE field is set to 00b or 10b in the parameter data (see 5.16.7.1), the copy manager
shall preserve information for:
A) the RECEIVE COPY FAILURE DETAILS(LID1) command (see 6.23), if supported. The preserved
information, if any, shall be discarded as described in 6.23; and
B) the:
a) RECEIVE COPY STATUS(LID4) command (see 6.24), if supported;
b) RECEIVE COPY DATA(LID4) command (see 6.20), if supported; and
c) RECEIVE ROD TOKEN INFORMATION command (see 6.28), if supported.
The preserved information, if any, shall be discarded as described in 6.24.

276 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

5.16.7.5 EXTENDED COPY considerations for RODs and ROD tokens

5.16.7.5.1 EXTENDED COPY command CSCD ROD identifiers

All ROD CSCD descriptors (see 6.4.5.9) create an identifier for the ROD that they describe. The identifier is
the CSCD descriptor ID (see table 148 in 6.4.6.1) for the ROD CSCD descriptor.

A ROD identifier identifies a ROD that is one of the following:

a) specified by segment descriptors that populate the ROD (see 5.16.7.5.2) in the EXTENDED COPY
parameter list (see 5.16.7.1); or
b) the conversion of a ROD token into an identifier using the following entries in the EXTENDED COPY
parameter list:
A) copying the ROD token to the inline data (see 5.16.7.1) in the EXTENDED COPY parameter list;
and
B) referencing the copied ROD token in a ROD CSCD descriptor in which the ROD TYPE field is set to
zero.

If the R_TOKEN bit is set to one in a ROD CSCD descriptor (see 6.4.5.9) in which the ROD TYPE field is not set
to zero, then the identified ROD is used to create a ROD token that is made available for transfer to the
application client using the RECEIVE ROD TOKEN INFORMATION command (see 6.28) and used as
described in 5.16.6.6.

After the copy manager finishes processing the copy operation (see 5.16.4.3) originated by an EXTENDED
COPY command, all the ROD identifiers created by that command shall become invalid.

If a ROD identifier becomes invalid (see 5.16.6.2.2, 5.16.6.2.3, and 5.16.6.7) before processing has been
completed for the copy operation (see 5.16.4.3) originated by the EXTENDED COPY command in which the
ROD identifier is defined, then any attempt to use the ROD as a copy source or copy destination shall cause
the copy manager shall terminate the copy operation as if an unreachable CSCD device had been
encountered (see 5.16.7.4).

5.16.7.5.2 Populating an EXTENDED COPY command ROD

If the ROD TYPE field (see 6.4.5.9) is not set to zero in the ROD CSCD descriptor, the following segment
descriptors are used to populate a ROD as described 5.16.6.3:

a) populate a ROD from one or more block device ranges (see 6.4.6.20); and
b) populate a ROD from one block device range (see 6.4.6.21).

If one of the segment descriptors listed in this subclause specifies the CSCD descriptor ID (see table 148 in
6.4.6.1) of the ROD CSCD descriptor as the copy destination and no errors are detected, then the specified
ROD is populated with the information associated with the ROD type (see 5.16.6.2) based on the contents of
the segment descriptor.

If the CSCD descriptor ID of a ROD CSCD descriptor in which the ROD TYPE field (see 6.4.5.9) is set to zero is
specified as the copy destination in one of the segment descriptors listed in this subclause, then the copy
manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the sense
key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.
The sense key specific data, if any, shall identify the CSCD descriptor ID in the segment descriptor as the field
that in error.

Working Draft SCSI Primary Commands - 4 (SPC-4) 277

T10/BSR INCITS 513 Revision 37 17 May 2014

Bytes shall be added to the ROD in the order that the segment descriptors are present in the EXTENDED
COPY parameter data (see 5.16.7.1). If a single segment descriptor specifies multiple ROD byte sources, the
bytes shall be added to the ROD in the order that the bytes are present in that segment descriptor.

The process of populating the ROD ends when:

a) the CSCD descriptor ID for the ROD CSCD descriptor is specified as a copy source or copy
destination in a segment descriptor that is not one of those listed in this subclause; or
b) processing of the copy operation (see 5.16.4.3) originated by the EXTENDED COPY command ends.

If one of the segment descriptors listed in this subclause specifies the CSCD descriptor ID of the ROD CSCD
descriptor as the copy destination after the process of populating the ROD has ended, then the copy manager
shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the sense key set to
COPY ABORTED, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

If the R_TOKEN bit is set to one in the ROD CSCD descriptor (see 6.4.5.9), then the copy manager shall create
a ROD token (see 5.16.6) for the populated ROD and prepare the ROD token for retrieval using the RECEIVE
ROD TOKEN INFORMATION command (see 6.28).

The copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with
the sense key set to COPY ABORTED, and the additional sense code set to INVALID FIELD IN PARAMETER
LIST if:

a) the value in PERIPHERAL DEVICE TYPE field of a copy source specified in a segment descriptor does not
match the value in the PERIPHERAL DEVICE TYPE field in ROD CSCD descriptor (see 6.4.5.9); or
b) characteristics (e.g., logical block length, protection information characteristics (see SBC-3))
associated with the data specified by a segment descriptor are incompatible with the characteristics
associated with the data specified by a previous segment descriptor, if any.

5.16.7.6 EXTENDED COPY command use of RODs when the peripheral device type is 00h
(i.e., block device)

The copy manager shall cause a ROD that was created by a copy manager associated with a logical unit
whose peripheral device type is 00h to function as a block device that:

a) exists only while the copy operation (see 5.16.4.3) originated by the EXTENDED COPY command is
being processed;
b) may be used by any segment descriptor (see 6.4.6.1) that operates on a block device as a:
A) copy source; or
B) copy destination, if allowed by the ROD type (see 5.16.6.2);
c) has the following block device characteristics:
A) a contiguous range of logical blocks;
B) LBAs numbered from zero to the number of logical blocks represented by the ROD (see
5.16.7.5.2) minus one;
C) data that matches the data that is in the ROD; and
D) characteristics that match those of the logical blocks that are represented by the ROD, including
at least the following:
a) a DISK BLOCK LENGTH field in the device type specific CSCD descriptor parameters (see
6.4.5.3) that is set to the logical block length of each logical block represented by the ROD;
and
b) protection information that matches the protection information of the logical blocks that are
represented by the ROD;
and

278 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

d) may have logical block provisioning information equivalent to the logical block provisioning
information of the logical blocks that are represented by the ROD (see 5.16.6).

5.16.7.7 EXTENDED COPY command interactions with aliases

An application client may use alias values to reference SCSI target devices or SCSI target ports in the
EXTENDED COPY command parameter list (see 5.16.7.1). The alias list provides a mechanism for eight-byte
third party identifier fields to reference a third party device or port whose name or addressing information is
longer than eight bytes.

EXAMPLE – An application may use the CHANGE ALIASES command (see 6.2) to establish an association between an
alias value and a SCSI target device or target port designation. Then, the application client may send an EXTENDED
COPY command containing in the parameter data an alias CSCD descriptor (see 6.4.5.7) that includes this alias value.

After the completion of the EXTENDED COPY command, an application should clear all associated alias
values from the device server's alias list by sending a CHANGE ALIASES command that requests association
of each alias value to a NULL DESIGNATION (see 6.2.4.2) alias format.

Working Draft SCSI Primary Commands - 4 (SPC-4) 279

T10/BSR INCITS 513 Revision 37 17 May 2014

6 Commands for all device types

6.1 Summary of commands for all device types

The operation codes for commands that apply to all device types are listed in table 120.

Table 120 — Commands for all device types (part 1 of 2)

Operation
Command code Support Reference
ACCESS CONTROL IN 86h O 8.3.2
ACCESS CONTROL OUT 87h O 8.3.3
CHANGE ALIASES A4h/0Bh a O 6.2
COPY OPERATION ABORT 83h/1Ch a O 6.3
EXTENDED COPY(LID4) 83h/01h a O 6.4
EXTENDED COPY(LID1) 83h/00h a O 6.5
INQUIRY 12h M 6.6
LOG SELECT 4Ch O 6.7
LOG SENSE 4Dh O 6.8
MANAGEMENT PROTOCOL IN A3h/10h a O 6.9
MANAGEMENT PROTOCOL OUT A4h/10h a O 6.10
MODE SELECT(6) 15h C 6.11
MODE SELECT(10) 55h C 6.12
MODE SENSE(6) 1Ah C 6.13
MODE SENSE(10) 5Ah C 6.14
PERSISTENT RESERVE IN 5Eh C 6.15
PERSISTENT RESERVE OUT 5Fh C 6.16
READ ATTRIBUTE 8Ch O 6.17
READ BUFFER 3Ch O 6.18
READ MEDIA SERIAL NUMBER ABh/01h a C 6.19
RECEIVE COPY DATA(LID4) 84h/06h a O 6.20
RECEIVE COPY DATA(LID1) 84h/01h a O 6.21
RECEIVE COPY OPERATING PARAMETERS 84h/03h a O 6.22
RECEIVE COPY FAILURE DETAILS(LID1) 84h/04h a O 6.23
RECEIVE COPY STATUS(LID4) 84h/05h a O 6.24
RECEIVE COPY STATUS(LID1) 84h/00h a O 6.25
RECEIVE CREDENTIAL 7Fh/1800h a O 6.26
RECEIVE DIAGNOSTIC RESULTS 1Ch O 6.27
RECEIVE ROD TOKEN INFORMATION 84h/07h a O 6.28
REMOVE I_T NEXUS A4h/0Ch a O 6.29
Type Key: C = Command support is defined in the applicable command standard.
M = Command support is mandatory.
O = Command support is optional.
A numeric ordered listing of operation codes is provided in F.3.
a
This command is defined by a combination of operation code and service action. The operation code
value is shown preceding the slash and the service action value is shown after the slash.
b
The following operation codes are obsolete: 16h, 17h, 18h, 39h, 3Ah, 40h, 56h, and 57h.

280 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 120 — Commands for all device types (part 2 of 2)

Operation
Command code Support Reference
a
REPORT ALIASES A3h/0Bh O 6.30
a
REPORT ALL ROD TOKENS 84h/08h O 6.31
REPORT IDENTIFYING INFORMATION A3h/05h a O 6.32
REPORT LUNS A0h M 6.33
a
REPORT PRIORITY A3h/0Eh O 6.34
REPORT SUPPORTED OPERATION CODES A3h/0Ch a O 6.35
a
REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS A3h/0Dh O 6.36
a
REPORT TARGET PORT GROUPS A3h/0Ah O 6.37
REPORT TIMESTAMP A3h/0Fh a O 6.38
REQUEST SENSE 03h C 6.39
SECURITY PROTOCOL IN A2h O 6.40
SECURITY PROTOCOL OUT B5h O 6.41
SEND DIAGNOSTIC 1Dh C 6.42
a
SET IDENTIFYING INFORMATION A4h/06h O 6.43
SET PRIORITY A4h/0Eh a O 6.44
a
SET TARGET PORT GROUPS A4h/0Ah O 6.45
a
SET TIMESTAMP A4h/0Fh O 6.46
TEST UNIT READY 00h M 6.47
WRITE ATTRIBUTE 8Dh O 6.48
WRITE BUFFER 3Bh C 6.49
Obsolete b
Type Key: C = Command support is defined in the applicable command standard.
M = Command support is mandatory.
O = Command support is optional.
A numeric ordered listing of operation codes is provided in F.3.
a This command is defined by a combination of operation code and service action. The operation code
value is shown preceding the slash and the service action value is shown after the slash.
b The following operation codes are obsolete: 16h, 17h, 18h, 39h, 3Ah, 40h, 56h, and 57h.

Working Draft SCSI Primary Commands - 4 (SPC-4) 281

T10/BSR INCITS 513 Revision 37 17 May 2014

6.2 CHANGE ALIASES command

6.2.1 CHANGE ALIASES command introduction

The CHANGE ALIASES command (see table 121) requests the device server to make changes to a list of
associations between eight-byte alias values and SCSI target device or SCSI target port designations that the
device server maintains. This command uses the MAINTENANCE OUT CDB format (see 4.2.2.3.4). A
designation contains a name and optional identifier information that specifies a SCSI target device or SCSI
target port (see 6.2.2). The alias list may be queried by the application client via the REPORT ALIASES
command (see 6.30). If the REPORT ALIASES command is supported, the CHANGE ALIASES command
shall also be supported.

Table 121 — CHANGE ALIASES command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A4h)
1 Reserved SERVICE ACTION (0Bh)
2
•• • Reserved
5
6 (MSB)
•• • PARAMETER LIST LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 121 for the CHANGE
ALIASES command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 121 for the CHANGE
ALIASES command.

The PARAMETER LIST LENGTH field specifies the length in bytes of the parameter data that shall be transferred
from the application client to the device server. A parameter list length value of zero specifies that no data
shall be transferred and no changes shall be made in the alias list.

The CONTROL byte is defined in SAM-5.

If the parameter list length results in the truncation of the header or any alias entry, the device server shall
make no changes to the alias list and shall terminate the command with CHECK CONDITION status, with the
sense key set to ILLEGAL REQUEST, and the additional sense code set to PARAMETER LIST LENGTH
ERROR.

On successful completion of a CHANGE ALIASES command, the device server shall maintain an association
of each assigned eight-byte alias value to the SCSI target device or SCSI target port designation. These
associations shall be cleared by a logical unit reset or I_T nexus loss. The device server shall maintain a
separate alias list for each I_T nexus.

282 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

A CHANGE ALIASES command may add, change, or remove entries from the alias list. Alias list entries not
referenced in the CHANGE ALIASES parameter data shall not be changed.

If the device server has insufficient resources to make all requested changes to the alias list, then the device
server shall make no changes to the alias list and shall terminate the command with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INSUFFICIENT
RESOURCES.

The parameter list for a CHANGE ALIASES command (see table 122) contains zero or more alias entries. If
the device server processes a CHANGE ALIASES command that contains at least one alias entry while there
exists any other enabled command that references an alias entry in the alias list, then the device server shall
terminate the CHANGE ALIASES command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to OPERATION IN PROGRESS.

Table 122 — CHANGE ALIASES parameter list

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • PARAMETER DATA LENGTH (n-3)
3 (LSB)
4
•• • Reserved
7
Alias entry list
8
•• • Alias entry (see 6.2.2) [first]

•
••

•• • Alias entry (see 6.2.2) [last]

n

The PARAMETER DATA LENGTH field should contain the number of bytes of alias entries, and shall be ignored by
the device server.

The format of an alias entry is described in 6.2.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 283

T10/BSR INCITS 513 Revision 37 17 May 2014

6.2.2 Alias entry format

One alias entry (see table 123) describes one alias reported via the REPORT ALIASES command (see 6.30)
or to be changed via the CHANGE ALIASES command.

Table 123 — Alias entry format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • ALIAS VALUE
7 (LSB)
8 PROTOCOL IDENTIFIER

9
Reserved
10
11 FORMAT CODE

12
Reserved
13
14 (MSB)
DESIGNATION LENGTH (n-15)
15 (LSB)
16
•• • DESIGNATION
n

The ALIAS VALUE field is set to the numeric alias value that the device server shall associate with the SCSI
target device or target port specified by the values in the PROTOCOL IDENTIFIER, FORMAT CODE and DESIGNATION
fields.

The PROTOCOL IDENTIFIER field (see table 124) specifies whether the alias entry designation is independent of
SCSI transport protocol and the SCSI transport protocol, if any, to which the alias entry applies.

Table 124 — Alias entry PROTOCOL IDENTIFIER field

Code Description Reference

00h to 0Fh Protocol specific designation 7.6.2
10h to 7Fh Reserved
80h Protocol independent designation 6.2.4
81h to FFh Reserved

The FORMAT CODE field contents combined with the PROTOCOL IDENTIFIER field contents defines the format of
the DESIGNATION field. The subclauses that describe each PROTOCOL IDENTIFIER field usage (see table 124)
define the applicable FORMAT CODE field values.

The DESIGNATION LENGTH field specifies the number of bytes of the DESIGNATION field. The DESIGNATION
LENGTHvalue shall be a multiple of four.

284 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The zero-padded (see 4.3.2) DESIGNATION field should designate a unique SCSI target device or target port
using the following:

a) a SCSI device name or a target port name;

b) zero or more target port identifiers; and
c) zero or more SCSI transport protocol specific identifiers.

6.2.3 Alias designation validation

The device server shall not validate any designation at the time of processing either the REPORT ALIASES or
CHANGE ALIASES command. Such validation shall occur only when the device server uses the alias list to
resolve an alias to a designation in the context of third-party commands (e.g., EXTENDED COPY) or any
other command that requires reference to the alias list.

If a designation identifies a unique SCSI target device or target port that is within a SCSI domain accessible to
the device server, then the designation is considered valid.

Based on the SCSI transport protocol specific requirements for a given designation format, a designation that
does not identify a unique SCSI target device or target port within the SCSI domains accessible to the device
server is considered invalid.

EXAMPLE 1 – A designation may be considered invalid if the device server has no ports on the SCSI domain of the
designated SCSI target device or target port.

A designation having both name and identifier information may be inconsistent if the device server is not able
to access the named SCSI target device or target port through one or more of the names or identifiers in the
designation. In such cases, the designation shall be processed as valid or invalid according to the SCSI
transport protocol specific requirements.

EXAMPLE 2 – In FCP-4, both an N_Port and World Wide Name for a SCSI port may be given in a designation. The
designation definition may require that the N_Port be that of the named port. In that case, the designation is invalid.
Alternatively, the designation definition may view the N_Port as a hint for the named FC Port accessible to the device
server through a different D_ID. In that case, the designation is valid and designates the named FC Port.

NOTE 22 - If only name information is provided in a designation, it is assumed that the device server has
access to a mechanism for resolving names to identifiers. Access to such a service is SCSI transport protocol
specific and vendor specific.

6.2.4 Alias entry protocol independent designations

6.2.4.1 Alias entry protocol independent designations overview

The protocol independent alias entry designations have the PROTOCOL IDENTIFIER field set to 80h and the
FORMAT CODE field set to one of the codes shown in table 125.

Table 125 — Protocol independent alias entry FORMAT CODE field

Designation Designation
Code Name Length (bytes) Contents Reference
00h NULL DESIGNATION 0 none 6.2.4.2
01h to FFh Reserved

Working Draft SCSI Primary Commands - 4 (SPC-4) 285

T10/BSR INCITS 513 Revision 37 17 May 2014

6.2.4.2 NULL DESIGNATION alias format

In response to an alias entry with the NULL DESIGNATION format, the device server shall remove the
specified alias value from the alias list. Application clients should use the NULL DESIGNATION format in a
CHANGE ALIASES command to remove inactive alias entries from the alias list if that alias entry is no longer
needed. The NULL DESIGNATION format shall not appear in REPORT ALIASES parameter data.

6.3 COPY OPERATION ABORT command

The COPY OPERATION ABORT command (see table 126) is a third-party copy command (see 5.16.3) that
requests the copy manager to abort the specified copy operation (see 5.16.4.3) as described in 5.16.4.7.
Whether the copy operation is being processed in the foreground or background, the effect of the COPY
OPERATION ABORT command is equivalent to an ABORT TASK task management function (see SAM-5 and
5.16.4.6).

Table 126 — COPY OPERATION ABORT command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (83h)
1 Reserved SERVICE ACTION (1Ch)
2 (MSB)
•• • LIST IDENTIFIER
5 (LSB)
6
•• • Reserved
14
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 126 for the COPY
OPERATION ABORT command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 126 for the COPY
OPERATION ABORT command.

The LIST IDENTIFIER field is defined in 5.16.4.2 and 6.4.3.2, and specifies the copy operation to be aborted. If
the copy manager is not processing a copy operation with the specified list identifier, the copy manager shall
terminate the COPY OPERATION ABORT command with CHECK CONDITION status, with the sense key set
to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

The CONTROL byte is defined in SAM-5.

286 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4 EXTENDED COPY(LID4) command

6.4.1 EXTENDED COPY(LID4) command introduction

The EXTENDED COPY(LID4) command (see table 127) is a third-party copy command (see 5.16.3) that
requests the copy manager to copy data from one set of copy sources (e.g., a set of source logical units) to a
set of copy destinations (e.g., a set of destination logical units). The transfers requested by an EXTENDED
COPY command are managed by a copy manager (see SAM-5 and 5.16.2).

Table 127 — EXTENDED COPY(LID4) command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (83h)
1 Reserved SERVICE ACTION (01h)
2
•• • Reserved
9
10 (MSB)
•• • PARAMETER LIST LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 127 for the EXTENDED
COPY(LID4) command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 127 for the EXTENDED
COPY(LID4) command.

The PARAMETER LIST LENGTH field is defined in 4.2.5.5. A parameter list length of zero specifies that the copy
manager shall not transfer any data or alter any internal state, and this shall not be considered an error. If the
parameter list length causes truncation of the parameter list, then the copy manager shall transfer no data and
shall terminate the EXTENDED COPY command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to PARAMETER LIST LENGTH ERROR.

The CONTROL byte is defined in SAM-5.

Working Draft SCSI Primary Commands - 4 (SPC-4) 287

T10/BSR INCITS 513 Revision 37 17 May 2014

6.4.2 EXTENDED COPY(LID4) parameter data

The format of the EXTENDED COPY(LID4) parameter list (see 5.16.7.1) is shown in table 128.

Table 128 — EXTENDED COPY(LID4) parameter list (part 1 of 2)

Bit
7 6 5 4 3 2 1 0
Byte
0 PARAMETER LIST FORMAT (01h)
1 Reserved STR LIST ID USAGE PRIORITY

2 (MSB)
HEADER CSCD DESCRIPTOR LIST LENGTH (0020h)
3 (LSB)
4
•• • Reserved
14
15 Reserved G_SENSE IMMED

16 HEADER CSCD DESCRIPTOR TYPE CODE (FFh)

17
18 Reserved
19
20 (MSB)
•• • LIST IDENTIFIER
23 (LSB)
24
•• • Reserved
41
42 (MSB)
CSCD DESCRIPTOR LIST LENGTH (n-47)
43 (LSB)
44 (MSB)
SEGMENT DESCRIPTOR LIST LENGTH (m-n)
45 (LSB)
46 (MSB)
INLINE DATA LENGTH (k-m)
47 (LSB)
CSCD descriptor list
48
•• • CSCD descriptor [ID 1] (see 6.4.5)
79
••
•
n-31
•• • CSCD descriptor [ID x] (see 6.4.5)
n

288 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 128 — EXTENDED COPY(LID4) parameter list (part 2 of 2)

Bit
7 6 5 4 3 2 1 0
Byte
Segment descriptor list
n+1
•• • Segment descriptor (see 6.4.6) [first]

•
•
•

•• • Segment descriptor (see 6.4.6) [last]

m
m+1
•• • Inline data
k

The PARAMETER LIST FORMAT field (see table 129) specifies the format of the EXTENDED COPY(LID4)
parameter list and shall be set as shown in table 128 for the EXTENDED COPY(LID4) command defined in
this standard.

Table 129 — PARAMETER LIST FORMAT field

Code Description
01h The format shown in table 128
all others Reserved

The STR bit is defined in 6.4.3.1.

The LIST ID USAGE field is defined in 6.4.3.2.

The PRIORITY field is defined in 6.4.3.3.

The HEADER CSCD DESCRIPTOR LIST LENGTH field shall be set as shown in table 128. For compatibility with
SPC-3, this field specifies the length of one CSCD descriptor (i.e., a target descriptor in SPC-3 terms) in which
the descriptor type is invalid. The EXTENDED COPY(LID4) command parameter list format replaces the one
descriptor with the fields shown in table 128.

The good with sense data (G_SENSE) bit specifies whether the copy manager is required to include sense data
with GOOD status. If the G_SENSE bit is set to zero, then the copy manager shall not include sense data with
any command that completes with GOOD status. If the G_SENSE bit is set to one and the copy manager
completes the EXTENDED COPY(LID4) command with GOOD status, then the copy manager shall include
sense data with the GOOD status in which the sense key is set to COMPLETED, the additional sense code is
set to EXTENDED COPY INFORMATION AVAILABLE, and the COMMAND-SPECIFIC INFORMATION field is set to
the number of segment descriptors the copy manager has processed.

The immediate ( IMMED ) bit specifies whether the copy manager returns status for the EXTENDED
COPY(LID4) command before the first segment descriptor is processed (see 5.16.7.2). Processing of the
IMMED bit is described in 5.16.4.3.

Working Draft SCSI Primary Commands - 4 (SPC-4) 289

T10/BSR INCITS 513 Revision 37 17 May 2014

The copy manager shall terminate the EXTENDED COPY(LID4) command with CHECK CONDITION status,
with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB if
the IMMED bit is set to one and:

a) the G_SENSE bit is set to one; or

b) the LIST ID USAGE field (see 6.4.3.2) is set to 11b.

For interoperability with the EXTENDED COPY command defined in SPC-3, the HEADER CSCD DESCRIPTOR
TYPE CODE field shall be set as shown in table 128.

The LIST IDENTIFIER field is defined in 6.4.3.2.

The CSCD DESCRIPTOR LIST LENGTH field is defined in 6.4.3.4.

The SEGMENT DESCRIPTOR LIST LENGTH field is defined in 6.4.3.5.

The INLINE DATA LENGTH field is defined in 6.4.3.6.

The CSCD descriptors are defined in 6.4.3.4 and 6.4.5.

The segment descriptors are defined in 6.4.3.5 and 6.4.6.

The inline data is defined in 6.4.3.6.

6.4.3 Shared EXTENDED COPY parameter list fields

6.4.3.1 STR bit

A sequential striped (STR) bit set to one specifies to the copy manager that the majority of the block device
references in the parameter list represent sequential access of several block devices that are striped. This
may be used by the copy manager to perform reads from a copy source block device at any time and in any
order during processing of an EXTENDED COPY command as described in 6.4.5.3. A STR bit set to zero
specifies to the copy manager that disk references, if any, may not be sequential.

290 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4.3.2 LIST IDENTIFIER field and LIST ID USAGE field

The LIST IDENTIFIER field identifies the copy operation (see 5.16.4.3) originated by the EXTENDED COPY
command to the copy manager as described in 5.16.4.2. The usage of the LIST IDENTIFIER field depends on the
EXTENDED COPY command being processed and contents of the LIST ID USAGE field as follows:

a) if the command being processed is an EXTENDED COPY(LID4) command (see 6.4), then the LIST ID
USAGE field specifies the usage of the LIST IDENTIFIER field as shown in table 130; and
b) if the command being processed is an EXTENDED COPY(LID1) command (see 6.5), then the LIST ID
USAGE field specifies the usage of the LIST IDENTIFIER field as shown in table 131.

Table 130 — LIST ID USAGE field for the EXTENDED COPY(LID4) command

Value Meaning
00b The contents of the LIST IDENTIFIER field are defined in 5.16.4.2.
The list identifier value may be used to abort (see 6.3) or to request status for a specific
command sent on a specific I_T nexus (e.g., using the RECEIVE COPY STATUS(LID4)
command (see 6.24)). The copy manager shall hold data, if any, for retrieval by the application
client as described in 5.16.4.5.
01b Reserved
10b The contents of the LIST IDENTIFIER field are defined in 5.16.4.2.
The list identifier value may be used to abort (see 6.3) or to request status for a specific
command sent on a specific I_T nexus (e.g., using the RECEIVE COPY STATUS(LID4)
command (see 6.24)). The copy manager may discard all held data (see 5.16.4.5) accessible to
the application client. If the application client requests delivery of data that has been discarded
as a result of the LIST ID USAGE field being set to 10b, then the copy manager shall respond as if
the EXTENDED COPY(LID4) command has not been processed.
11b If the LIST IDENTIFIER field is not set to zero, then the copy manager shall terminate the command
with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the
additional sense code set to INVALID FIELD IN PARAMETER LIST.
The copy manager shall discard all data accessible to the application client (e.g., using the
RECEIVE COPY STATUS(LID4) command (see 6.24)). If the application client requests delivery
of data that has been discarded as a result the LIST ID USAGE field being set to 11b then the copy
manager shall respond as if the EXTENDED COPY(LID4) command has not been processed.
If the parameter list contains any segment descriptors (see 6.4.6) that require data to be held for
the application client (e.g., the blockblock&application client segment descriptor (see 6.4.6.4)),
then the copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense
code set to INVALID FIELD IN PARAMETER LIST, and no segment descriptors shall be
processed (see 5.16.7.3).

Working Draft SCSI Primary Commands - 4 (SPC-4) 291

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 131 — LIST ID USAGE field for the EXTENDED COPY(LID1) command

Value SNLID bit a Meaning

00b 0 or 1 The contents of the LIST IDENTIFIER field are defined in 5.16.4.2.
The list identifier value may be used to abort (see 6.3) or to request status for a
specific command sent on a specific I_T nexus (e.g., using the RECEIVE COPY
STATUS(LID4) command (see 6.24)). The copy manager shall hold data, if any,
for retrieval by the application client as described in 5.16.4.5.
01b Reserved
10b 0 or 1 The contents of the LIST IDENTIFIER field are defined in 5.16.4.2.
The list identifier value may be used to abort (see 6.3) or to request status for a
specific command sent on a specific I_T nexus (e.g., using the RECEIVE COPY
STATUS(LID4) command (see 6.24)). The copy manager may discard all held
data (see 5.16.4.5) accessible to the application client. If the application client
requests delivery of data that has been discarded as a result of the LIST ID
USAGE field being set to 10b, then the copy manager shall respond as if the
EXTENDED COPY(LID1) command has not been processed.
11b 0 The copy manager shall:
a) terminate the command with CHECK CONDITION status with the sense
key set to ILLEGAL REQUEST, and the additional sense code set to
INVALID FIELD IN PARAMETER LIST; or
b) process the command as if the LIST ID USAGE field is set to 10b.
1 If the LIST IDENTIFIER field is not set to zero, the copy manager shall terminate
the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN
PARAMETER LIST.
The copy manager shall discard all data accessible to the application client
(e.g., using the RECEIVE COPY STATUS(LID4) command (see 6.24)). If the
application client requests delivery of data that has been discarded as a result
the LIST ID USAGE field being set to 11b then the copy manager shall respond as
if the EXTENDED COPY(LID1) command has not been processed.
If the parameter list contains any segment descriptors (see 6.4.6) that require
data to be held for the application client (e.g., the blockblock&application
client segment descriptor (see 6.4.6.4)), then the copy manager shall terminate
the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the
sense key set to ILLEGAL REQUEST, and the additional sense code set to
INVALID FIELD IN PARAMETER LIST, and no segment descriptors shall be
processed (see 5.16.7.3).
a
See the RECEIVE COPY OPERATING PARAMETERS command (see 6.22).

292 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

During the processing of a copy operation (see 5.16.4.3) originated by the EXTENDED COPY command with
the LIST ID USAGE field set to 00b or 10b, for any EXTENDED COPY command received into the task set the
copy manager shall:

a) not start a copy operation; and

b) terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST,
if:
a) the EXTENDED COPY command that does not have a copy operation being processed includes:
A) a LIST IDENTIFIER field set to a specific value (e.g., a LIST IDENTIFIER field set to 50h); and
B) a parameter list in one format (i.e., EXTENDED COPY(LID4) command parameter list format or
EXTENDED COPY(LID1) command parameter list format);
and
b) the copy operation being processed was originated by an EXTENDED COPY command that included:
A) a LIST IDENTIFIER field set to the same value (e.g., a LIST IDENTIFIER field set to 50h); and
B) a parameter list in the other format.

The copy manager may respond as if the EXTENDED COPY command had never been received, if an
EXTENDED COPY command that had the LIST ID USAGE field set to 10b or 11b in its parameter list is specified
by the LIST IDENTIFIER field in one of the following commands:

a) the RECEIVE COPY STATUS(LID4) command (see 6.24);

b) the RECEIVE COPY STATUS(LID1) command (see 6.25);
c) the RECEIVE COPY DATA(LID4) command (see 6.20);
d) the RECEIVE COPY DATA(LID1) command (see 6.21);
e) the RECEIVE COPY FAILURE DETAILS(LID1) command (see 6.23); and
f) the RECEIVE ROD TOKEN INFORMATION command (see 6.28).

6.4.3.3 PRIORITY field

The PRIORITY field specifies the priority of data transfers resulting from this EXTENDED COPY command
relative to data transfers resulting from other commands being processed by the device server contained
within the same logical unit as the copy manager. All commands other than third-party copy commands have
a priority of 1h. Priority 0h is the highest priority, with increasing values in the PRIORITY field indicating lower
priorities.

6.4.3.4 CSCD DESCRIPTOR LIST LENGTH field and CSCD descriptor list

The CSCD DESCRIPTOR LIST LENGTH field specifies the length in bytes of the CSCD descriptor list that follows
the parameter list header (see 5.16.7.1). An EXTENDED COPY command may reference one or more
CSCDs. Each CSCD is described by a CSCD descriptor (see 6.4.5).

The maximum number of CSCD descriptors permitted within a parameter list is indicated by the MAXIMUM
CSCD DESCRIPTOR COUNT field in the Third-party Copy VPD page Parameter Data descriptor (see 7.8.17.5),
and in the parameter data for the RECEIVE COPY OPERATING PARAMETERS command (see 6.22). If the
number of CSCD descriptors exceeds the allowed number, the copy manager shall terminate the command
with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense
code set to TOO MANY TARGET DESCRIPTORS.

6.4.3.5 SEGMENT DESCRIPTOR LIST LENGTH field and segment descriptor list

The SEGMENT DESCRIPTOR LIST LENGTH field specifies the length in bytes of the segment descriptor list that
follows the CSCD descriptors (see 5.16.7.1). See 6.4.6 for a detailed description of the segment descriptors.

Working Draft SCSI Primary Commands - 4 (SPC-4) 293

T10/BSR INCITS 513 Revision 37 17 May 2014

The maximum number of segment descriptors permitted within a parameter list is indicated by the MAXIMUM
SEGMENT DESCRIPTOR COUNT field in the Third-party Copy VPD page Parameter Data descriptor (see
7.8.17.5), and in the parameter data for the RECEIVE COPY OPERATING PARAMETERS command (see
6.22). If the number of segment descriptors exceeds the allowed number, the copy manager shall terminate
the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the
additional sense code set to TOO MANY SEGMENT DESCRIPTORS.

The maximum combined length of the CSCD descriptors and segment descriptors permitted within a
parameter list is indicated by the MAXIMUM DESCRIPTOR LIST LENGTH field in the Third-party Copy VPD page
Parameter Data descriptor (see 7.8.17.5), and in the parameter data for the RECEIVE COPY OPERATING
PARAMETERS command (see 6.22). If the combined length of the CSCD descriptors and segment
descriptors exceeds the allowed value, then the copy manager shall terminate the command with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
PARAMETER LIST LENGTH ERROR.

6.4.3.6 INLINE DATA LENGTH field and inline data

The INLINE DATA LENGTH field specifies the number of bytes of inline data, following the last segment descriptor
(see 5.16.7.1). A value of zero specifies that no inline data is present.

The inline data contains information that is available for:

a) reference by CSCD descriptors; or

b) transfer by the copy manager in response to segment descriptors.

6.4.4 Descriptor type codes

CSCD descriptors, the CSCD descriptor extension, and segment descriptors share a single set of code values
(see table 132) that identify the type of descriptor.

Table 132 — EXTENDED COPY descriptor type codes

Descriptor type Description Reference

00h to BFh Segment descriptors 6.4.6
C0h to DFh Vendor specific descriptors
E0h to FEh CSCD descriptors 6.4.5
a
FFh CSCD descriptor extension 6.4.5.2
a Use of this descriptor type code is reserved except in byte 32 of a 64-byte CSCD
descriptor (e.g., the IPv6 CSCD descriptor described in 7.6.3.9).

294 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4.5 CSCD descriptors

6.4.5.1 CSCD descriptors introduction

The descriptor type code (see table 132) values for CSCD descriptors are shown in table 133.

Table 133 — EXTENDED COPY CSCD descriptor type codes

Descriptor Size
type a Name (bytes) Reference
E0h Fibre Channel N_Port_Name CSCD descriptor 32 7.6.3.2
E1h Fibre Channel N_Port_ID CSCD descriptor 32 7.6.3.3
Fibre Channel N_Port_ID With N_Port_Name
E2h 32 7.6.3.4
Checking CSCD descriptor
E3h Parallel Interface T_L CSCD descriptor 32 7.6.3.5
E4h Identification Descriptor CSCD descriptor 32 6.4.5.6
E5h IPv4 CSCD descriptor 32 7.6.3.8
E6h Alias CSCD descriptor 32 6.4.5.7
E7h RDMA CSCD descriptor 32 7.6.3.7
E8h IEEE 1394 EUI-64 CSCD descriptor 32 7.6.3.6
E9h SAS Serial SCSI Protocol CSCD descriptor 32 7.6.3.10
EAh IPv6 CSCD descriptor 64 7.6.3.9
EBh IP Copy Service CSCD descriptor 64 6.4.5.8
ECh to FDh Reserved for CSCD descriptors
FEh ROD CSCD descriptor b 32 6.4.5.9
a
A copy manager may not support all CSCD descriptor types; however, the copy manager
shall list all supported CSCD descriptor types in the Third-party Copy VPD page Supported
Descriptors descriptor (see 7.8.17.6), and in the parameter data for the RECEIVE COPY
OPERATING PARAMETERS command (see 6.22).
b A copy manager that implements the ROD CSCD descriptor shall implement:

a) the following third-party copy descriptors in the Third-party Copy VPD page:
A) the ROD Features third-party copy descriptor (see 7.8.17.8); and
B) the Supported ROD Types third-party copy descriptor (see 7.8.17.9);
and
b) at least one of the following segment descriptors:
A) the Populate a ROD from one or more block device ranges (see 6.4.6.20); or
B) the Populate a ROD from one block device range (see 6.4.6.21).

Working Draft SCSI Primary Commands - 4 (SPC-4) 295

T10/BSR INCITS 513 Revision 37 17 May 2014

All CSCD descriptors (see table 134) are a multiple of 32 bytes in length and begin with a four-byte header
containing the DESCRIPTOR TYPE CODE field that specifies the format of the descriptor. If a copy manager
receives an unsupported descriptor type code in a CSCD descriptor, the copy manager shall terminate the
copy operation (see 5.16.4.3) with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to UNSUPPORTED TARGET DESCRIPTOR TYPE CODE.

Table 134 — CSCD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (E0h to FEh)
1 LU ID TYPE Obsolete PERIPHERAL DEVICE TYPE

2 (MSB)
RELATIVE INITIATOR PORT IDENTIFIER
3 (LSB)
4
•• • CSCD descriptor parameters
27
28
•• • Device type specific parameters
31
32
Zero or more CSCD descriptor extensions
•• •
(see 6.4.5.2)
n

The DESCRIPTOR TYPE CODE field is described in 6.4.4.

The LU ID TYPE field (see table 135) specifies the interpretation of the LU IDENTIFIER field in CSCD descriptors
that contain a LU IDENTIFIER field.

Table 135 — LU ID TYPE field

Code LU IDENTIFIER field contents Support Reference

00b Logical Unit Number Mandatory SAM-5
01b Proxy Token Optional 8.3.1.6.2
10b to 11b Reserved

If a copy manager receives an unsupported value in the LU ID TYPE field, the copy manager shall terminate the
copy operation (see 5.16.4.3) with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

If the LU ID TYPE field specifies that the LU IDENTIFIER field contains a logical unit number, then the LU IDENTIFIER
field specifies the logical unit within the SCSI device specified by other fields in the CSCD descriptor that shall
be the copy source or copy destination.

If the LU ID TYPE field specifies that the LU IDENTIFIER field contains a proxy token (see 8.3.1.6.2), then the copy
manager shall use the LU IDENTIFIER field contents to obtain proxy access rights to the logical unit associated
with the proxy token. The logical unit number that represents the proxy access rights shall be the copy source
or copy destination.

296 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The copy manager should obtain a LUN value for addressing this logical unit by sending an ACCESS
CONTROL OUT command with ASSIGN PROXY LUN service action (see 8.3.3.11) to the access controls
coordinator of the SCSI target device that is specified by other fields in the CSCD descriptor. The copy
manager shall use a LUN assigned on the basis of a proxy token only for those commands that are necessary
for the processing of the EXTENDED COPY command whose parameter data contains the proxy token. After
the copy manager has completed EXTENDED COPY commands involving a proxy token, the copy manager
should release the LUN value using an ACCESS CONTROL OUT command with RELEASE PROXY LUN
service action (see 8.3.3.12).

The copy manager shall only access proxy logical units if if the LU ID TYPE field is set to 01b. If the copy
manager receives a CSCD descriptor containing LU ID type 00b and a logical unit number matching a LUN
value that the copy manager has obtained using an ACCESS CONTROL OUT command with ASSIGN
PROXY LUN service action, then the copy manager shall terminate the copy operation (see 5.16.4.3) with
CHECK CONDITION status, with the sense key set to COPY ABORTED, and the additional sense code set to
COPY TARGET DEVICE NOT REACHABLE.

The PERIPHERAL DEVICE TYPE field is described in 6.6.2. The value in the PERIPHERAL DEVICE TYPE field (see
table 134) specifies the format of the device type specific parameters. The device type specific parameters
convey information specific to the type of device specified by the CSCD descriptor.

Table 136 lists the peripheral device type code values having formats defined for the device type specific
parameters in a CSCD descriptor. Peripheral device types with code values not listed in table 136 are
reserved in all PERIPHERAL DEVICE TYPE fields in the EXTENDED COPY parameter list.

Table 136 — Device type specific parameters in CSCD descriptors

Peripheral
Device Type Reference Description Name
00h, 05h, and 0Eh 6.4.5.3 Block devices Block
01h 6.4.5.4 Sequential-access devices Stream or Tape
03h 6.4.5.5 Processor devices a Stream
a This standard defines the use of the processor device type (i.e., 03h) (see
SPC-2) only for the interactions between copy managers.

The RELATIVE INITIATOR PORT IDENTIFIER field (see 4.3.4) specifies the relative port identifier of the initiator port
within the SCSI device that the copy manager shall use to access the logical unit described by the CSCD
descriptor, if such access requires use of an initiator port (i.e., if the logical unit is in the same SCSI device as
the copy manager, the RELATIVE INITIATOR PORT IDENTIFIER field is ignored). A RELATIVE INITIATOR PORT
IDENTIFIER field set to zero specifies that the copy manager may use any initiator port or ports within the SCSI
device.

CSCD descriptor extensions increase the length of a CSCD descriptor as described in 6.4.5.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 297

T10/BSR INCITS 513 Revision 37 17 May 2014

6.4.5.2 The CSCD descriptor extension

A CSCD descriptor (see 6.4.5.1) is extended by appending one or more CSCD descriptor extensions (see
table 137) to it. A CSCD descriptor extension is 32 bytes in length and begins with a one-byte header
containing the descriptor type code value that identifies the descriptor as a CSCD descriptor extension (i.e.,
FFh).

Table 137 — CSCD descriptor extension format

Bit
7 6 5 4 3 2 1 0
Byte
0 EXTENSION DESCRIPTOR TYPE CODE (FFh)
1
•• • CSCD descriptor specific information
31

The EXTENSION DESCRIPTOR TYPE CODE field is a descriptor type code value (see 6.4.4), and shall be set to the
value shown in table 137 for each CSCD descriptor extension.

The CSCD descriptor specific information contains data that extends the CSCD descriptor or CSCD descriptor
extension located adjacent to and preceding this CSCD descriptor extension.

If a SOURCE CSCD DESCRIPTOR ID field or a DESTINATION CSCD DESCRIPTOR ID field in a segment descriptor (see
6.4.6.1) references a CSCD descriptor extension (i.e, a descriptor with the descriptor type code set to FFh),
then the copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status,
with the sense key set to COPY ABORTED, and the additional sense code set to INVALID FIELD IN
PARAMETER LIST.

6.4.5.3 Device type specific CSCD descriptor parameters for block device types

The format for the device type specific CSCD descriptor parameters for block device types (i.e., device type
code values 00h, 05h, and 0Eh) is shown in table 138.

Table 138 — Device type specific CSCD descriptor parameters for block device types

Bit
7 6 5 4 3 2 1 0
Byte
28 Reserved PAD Reserved
29 (MSB)
30 DISK BLOCK LENGTH

31 (LSB)

The PAD bit is used in conjunction with the CAT bit (see 6.4.6.1) in the segment descriptor to determine what
action should be taken if a segment of the copy does not fit exactly into an integer number of destination
logical blocks (see 5.16.7.2).

The DISK BLOCK LENGTH field is set to the number of bytes in a logical block, excluding any protection
information (see SBC-3), for the logical unit being addressed.

If the DISK BLOCK LENGTH field is set to zero and the PERIPHERAL DEVICE TYPE field (see 6.4.5.1) is set to 00h,
then the copy manager shall determine the logical block length of the CSCD logical unit (e.g., by sending a

298 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

READ CAPACITY command (see SBC-3)), and use the result wherever the use of the DISK BLOCK LENGTH
field is required by this standard.

The copy manager may read ahead from copy sources of the block device type (i.e., the copy manager may
perform reads from a copy source block device at any time and in any order during processing of an
EXTENDED COPY command), provided that the relative order of writes and reads on the same logical blocks
within the same CSCD descriptor does not differ from their order in the segment descriptor list (see 5.16.7.1).

6.4.5.4 Device type specific CSCD descriptor parameters for sequential-access device types

The format for the device type specific CSCD descriptor parameters for the sequential-access device type
(i.e., device type code value 01h) operating in the implicit address mode (see SSC-4) is shown in table 139.

Table 139 — Device type specific CSCD descriptor parameters for sequential-access device types

Bit
7 6 5 4 3 2 1 0
Byte
28 Reserved PAD Reserved FIXED

29 (MSB)
30 STREAM BLOCK LENGTH

31 (LSB)

The contents of the FIXED bit and STREAM BLOCK LENGTH field are combined with the STREAM DEVICE TRANSFER
LENGTH FIELD in the segment descriptor to determine the length of the stream read or write as defined in table
140.

Table 140 — Stream device transfer lengths

FIXED STREAM BLOCK

bit LENGTH field Description
0 000000h Use variable length reads or writes. The number of bytes for each read or write
is specified by the STREAM DEVICE TRANSFER LENGTH field in the segment
descriptor.
000001h to The copy manager shall terminate the copy operation (see 5.16.4.3) with
FFFFFFh CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and
the additional sense code set to INVALID FIELD IN PARAMETER LIST.
1 000000h The copy manager shall terminate the copy operation (see 5.16.4.3) with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and
the additional sense code set to INVALID FIELD IN PARAMETER LIST
000001h to Use fixed record length reads or writes. The number of bytes for each read or
FFFFFFh write shall be the product of the STREAM BLOCK LENGTH field and the STREAM
DEVICE TRANSFER LENGTH field in the segment descriptor.

The PAD bit is used in conjunction with the CAT bit (see 5.16.7.2) in the segment descriptor to determine what
action should be taken if a segment of the copy does not fit exactly into an integer number of destination
logical blocks (see 5.16.7.2).

All read commands issued to sequential-access type devices shall have the SILI bit set to zero.

Working Draft SCSI Primary Commands - 4 (SPC-4) 299

T10/BSR INCITS 513 Revision 37 17 May 2014

The copy manager shall not read ahead from copy sources of the stream device type (i.e., the reads required
by a segment descriptor for which the copy source is a stream device shall not be started until all writes for
previous segment descriptors have completed).

6.4.5.5 Device type specific CSCD descriptor parameters for processor device types

The format for the device type specific CSCD descriptor parameters for the processor device type (i.e., device
type code value 03h) (see SPC-2) is shown in table 141.

Table 141 — Device type specific CSCD descriptor parameters for processor device types

Bit
7 6 5 4 3 2 1 0
Byte
28 Reserved PAD Reserved
29
•• • Reserved
31

The PAD bit is used in conjunction with the CAT bit (see 5.16.7.2) in the segment descriptor to determine what
action should be taken if a segment of the copy does not fit exactly into an integer number of EXTENDED
COPY(LID4) commands (see 6.4), EXTENDED COPY(LID1) commands (see 6.5), RECEIVE COPY
DATA(LID4) commands (see 6.20), or RECEIVE COPY DATA(LID1) commands (see 6.21).

If the processor device is a copy source, the number of bytes to be transferred by an EXTENDED COPY
command shall be specified by STREAM DEVICE TRANSFER LENGTH field in the segment descriptor. If the
processor device is a copy destination, the number of bytes to be transferred by an EXTENDED COPY
command and subsequent RECEIVE COPY DATA command shall be specified by STREAM DEVICE TRANSFER
LENGTH field in the segment descriptor.

300 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4.5.6 Identification Descriptor CSCD descriptor format

The CSCD descriptor format shown in table 142 requests the copy manager to locate a SCSI target device
and logical unit that returns a Device Identification VPD page (see 7.8.6) containing an Identification
descriptor having the specified values in the CODE SET field, ASSOCIATION field, DESIGNATOR TYPE field,
IDENTIFIER LENGTH field, and DESIGNATOR field. The copy manager may use any SCSI transport protocol (see
SAM-5), target port identifier (see SAM-5) and logical unit number (see SAM-5) values that result in matching
VPD field values to address the logical unit. If multiple combinations of SCSI transport protocols, target port
identifiers, and logical unit numbers access matching VPD field values, then the copy manager may use any
combination to address the logical unit and shall try other combinations in the event that one combination
becomes non-operational during the processing of an EXTENDED COPY command.

Table 142 — Identification Descriptor CSCD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (E4h)
1 LU ID TYPE Obsolete PERIPHERAL DEVICE TYPE

2 (MSB)
RELATIVE INITIATOR PORT IDENTIFIER
3 (LSB)
4 Reserved CODE SET

5 Reserved ASSOCIATION DESIGNATOR TYPE

6 Reserved
7 DESIGNATOR LENGTH

8
•• • DESIGNATOR
27
28
•• • Device type specific parameters
31

The DESCRIPTOR TYPE CODE field, PERIPHERAL DEVICE TYPE field, RELATIVE INITIATOR PORT IDENTIFIER field, and
the device type specific parameters are described in 6.4.5.1. The DESCRIPTOR TYPE CODE field shall be set as
shown in table 142 for the Identification Descriptor CSCD descriptor.

The LU ID TYPE field shall be ignored in the Identification Descriptor CSCD descriptor.

The CODE SET field contains a code set enumeration (see 4.3.3) that indicates the format of the DESIGNATOR
field.

The contents of the ASSOCIATION field, DESIGNATOR TYPE field, and DESIGNATOR LENGTH field are described in
7.8.6.1. The designator length shall be 20 or less.

The DESIGNATOR field is a fixed-length zero-padded (see 4.3.2) field that has the DESIGNATOR field format
defined in 7.8.6.

Some combinations of code set, association, designator type, designator length and designator do not
uniquely identify a logical unit to serve as a CSCD. The behavior of the copy manager if such combinations
are specified is outside the scope of this standard.

Working Draft SCSI Primary Commands - 4 (SPC-4) 301

T10/BSR INCITS 513 Revision 37 17 May 2014

6.4.5.7 Alias CSCD descriptor format

The CSCD descriptor format shown in table 143 requests the copy manager to locate a SCSI target port and
logical unit using the alias list designation associated with the specified alias value. The alias list is maintained
using the CHANGE ALIASES command (see 6.2).

Table 143 — Alias CSCD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (E6h)
1 LU ID TYPE Obsolete PERIPHERAL DEVICE TYPE

2 (MSB)
RELATIVE INITIATOR PORT IDENTIFIER
3 (LSB)
4
•• • LU IDENTIFIER
11
12
•• • ALIAS VALUE
19
20
•• • Reserved
27
28
•• • Device type specific parameters
31

The DESCRIPTOR TYPE CODE field, LU ID TYPE field, PERIPHERAL DEVICE TYPE field, RELATIVE INITIATOR PORT
IDENTIFIER field, and the device type specific parameters are described in 6.4.5.1. The DESCRIPTOR TYPE CODE
field shall be set as shown in table 143 for the Alias CSCD descriptor.

The ALIAS VALUE field specifies an alias value in the alias list as managed by the CHANGE ALIASES
command (see 6.2) and maintained by the device server.

When the copy manager first processes an Alias CSCD descriptor, it shall check the value of the ALIAS VALUE
field for a corresponding entry in the alias list. If the value is not in the alias list or the copy manager is unable
to validate the designation (see 6.2.3) associated with the alias value, then the copy manager shall terminate
the copy operation (see 5.16.4.3) because the CSCD is unreachable (see 5.16.7.4). An application client
generating EXTENDED COPY commands that include Alias CSCD descriptors in the parameter list is
responsible for providing a valid entry in the alias list using the CHANGE ALIASES command (see 6.2) prior to
sending the EXTENDED COPY command.

302 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4.5.8 IP Copy Service CSCD descriptor

The CSCD descriptor format shown in table 144 requests the copy manager to communicate with the copy
service specified in the IP ADDRESS field to locate the CSCD that returns a Device Identification VPD page (see
7.8.6) containing an Identification descriptor having the specified CODE SET field, ASSOCIATION field, DESIG-
NATOR TYPE field, DESIGNATOR LENGTH field, and DESIGNATOR field values.

The protocol used by the copy manager to communicate with the copy service is vendor specific.

Table 144 — IP Copy Service CSCD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (EBh)
1 LU ID TYPE Obsolete PERIPHERAL DEVICE TYPE

2 Reserved IPTYPE

3
•• • Reserved
11
12 (MSB)
•• • COPY SERVICE IP ADDRESS
27 (LSB)
28
Device type specific parameters
31
32 EXTENSION DESCRIPTOR TYPE CODE (FFh)
33
Reserved
35
36 (MSB)
COPY SERVICE PORT NUMBER
37 (LSB)
38 (MSB)
COPY SERVICE INTERNET PROTOCOL NUMBER
39 (LSB)
40 Reserved CODE SET

41 Reserved ASSOCIATION DESIGNATOR TYPE

42 Reserved
43 DESIGNATOR LENGTH

44
•• • DESIGNATOR
63

The DESCRIPTOR TYPE CODE field, PERIPHERAL DEVICE TYPE field, RELATIVE INITIATOR PORT IDENTIFIER field, and
the device type specific parameters are described in 6.4.5.1. The DESCRIPTOR TYPE CODE field shall be set as
shown in table 144 for the IP Copy Service CSCD descriptor.

The LU ID TYPE field shall be ignored in the IP Copy Service CSCD descriptor.

Working Draft SCSI Primary Commands - 4 (SPC-4) 303

T10/BSR INCITS 513 Revision 37 17 May 2014

If the IPTYPE bit is set to zero, the COPY SERVICE IP ADDRESS field shall contain a zero-padded IPv4 address
(see RFC 791). If the IPTYPE bit is set to one, the COPY SERVICE IP ADDRESS field shall contain a unicast IPv6
address (see RFC 4291).

The COPY SERVICE IP ADDRESS field is set to the IP address of the copy service in the format specified by the
IPTYPE bit.

The EXTENSION DESCRIPTOR TYPE CODE field is described in 6.4.5.2. If the EXTENSION DESCRIPTOR TYPE CODE
field does not contain the value shown in table 144, then the copy manager shall terminate the EXTENDED
COPY command with CHECK CONDITION status, with the sense key set to COPY ABORTED, and the
additional sense code set to INVALID FIELD IN PARAMETER LIST.

The COPY SERVICE PORT NUMBER field shall contain the TCP port number.

The COPY SERVICE INTERNET PROTOCOL NUMBER field shall contain an Internet protocol number.

The contents of the COPY SERVICE IP ADDRESS field, the COPY SERVICE PORT NUMBER field, and the COPY
SERVICE INTERNET PROTOCOL NUMBER field may be obtained from the network service descriptor with the
SERVICE TYPE field set to 06h (i.e., copy service) in the Management Network Addresses VPD page (see 7.8.8)
returned by the logical unit that returns a Device Identification VPD page (see 7.8.6) containing an
Identification descriptor having the specified CODE SET field, ASSOCIATION field, DESIGNATOR TYPE field,
DESIGNATOR LENGTH field, and DESIGNATOR field values.

The CODE SET field contains a code set enumeration (see 4.3.3) that indicates the format of the DESIGNATOR
field.

The contents of the ASSOCIATION field, DESIGNATOR TYPE field, and DESIGNATOR LENGTH field are described in
7.8.6.1. The designator length shall be 20 or less.

The DESIGNATOR field is a fixed-length zero-padded (see 4.3.2) field that has the DESIGNATOR field format
defined in 7.8.6.

Some combinations of code set, association, designator type, designator length and designator do not
uniquely identify a logical unit to serve as a CSCD. The behavior of the copy manager if such combinations
are specified is outside the scope of this standard.

304 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4.5.9 ROD CSCD descriptor

The CSCD descriptor format shown in table 145 requests the copy manager to use the specified ROD as a
copy source or copy destination. If the ROD represents no data when the copy manager begins processing
the EXTENDED COPY command (e.g., the ROD TYPE field is not set to zero), then the copy manager shall
allow the ROD to be populated as defined in 5.16.7.5.2. If a segment descriptor attempts to use an
unpopulated ROD as a copy source or copy destination, then the copy manager shall terminate the copy
operation (see 5.16.4.3) as if an unreachable CSCD had been encountered (see 5.16.7.4).

Table 145 — ROD CSCD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (FEh)
1 LU ID TYPE Obsolete PERIPHERAL DEVICE TYPE

2 (MSB)
RELATIVE INITIATOR PORT IDENTIFIER
3 (LSB)
4 (MSB)
ROD PRODUCER CSCD DESCRIPTOR ID
5 (LSB)
6
Reserved
7
8 (MSB)
•• • ROD TYPE
11 (LSB)
12 (MSB)
•• • REQUESTED ROD TOKEN LIFETIME
15 (LSB)
16 (MSB)
•• • REQUESTED ROD TOKEN INACTIVITY TIMEOUT
19 (LSB)
20
Reserved
21
22 Reserved R_TOKEN

23 Reserved DEL_TKN

24 (MSB)
•• • ROD TOKEN OFFSET
27 (LSB)
28
•• • Device type specific parameters
31

The DESCRIPTOR TYPE CODE field, PERIPHERAL DEVICE TYPE field, RELATIVE INITIATOR PORT IDENTIFIER field, and
the device type specific parameters are described in 6.4.5.5. The DESCRIPTOR TYPE CODE field shall be set as
shown in table 145 for the ROD CSCD descriptor.

Working Draft SCSI Primary Commands - 4 (SPC-4) 305

T10/BSR INCITS 513 Revision 37 17 May 2014

The LU ID TYPE field shall be ignored in the ROD CSCD descriptor.

If the ROD TYPE field is set to zero, then:

a) the PERIPHERAL DEVICE TYPE field shall be ignored; and

b) the peripheral device type of the ROD CSCD descriptor shall be the peripheral device type specified
by the ROD token that is specified by the ROD TOKEN OFFSET field.

The ROD PRODUCER CSCD DESCRIPTOR ID field specifies the CSCD device (see table 150 in 6.4.6.1) that
contains the logical unit that contains the copy manager that:

a) created the ROD token that is specified by the ROD TOKEN OFFSET field, if the ROD TYPE field is set to
zero; or
b) creates the ROD token that is created during processing of the EXTENDED COPY command, if the
ROD TYPE field is not set to zero.

The ROD TYPE field (see table 111 in 5.16.6.2.1) specifies the type of ROD being populated or referenced by a
ROD token.

For all ROD types (see 5.16.6.2), access to the bytes within a ROD is established by specifying:

a) the identifier of a ROD CSCD descriptor that describes the ROD for the duration of the copy operation
(see 5.16.4.3) originated by an EXTENDED COPY command; or
b) that a ROD token be created that allows the copy manager that creates the ROD token creator to
identify and access the bytes represented by the ROD across multiple third-party copy commands.

Methods are available to create a ROD token from a ROD identifier and create a ROD identifier from a ROD
token (see 5.16.7.5.1).

Fields in the ROD CSCD descriptor and fields in the ROD Features third-party copy descriptor (see 7.8.17.8)
in the Third-party Copy VPD page that affect the processing of the ROD PRODUCER CSCD DESCRIPTOR ID field

306 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

are shown in table 146.

Table 146 — Inputs that affect the processing of the ROD PRODUCER CSCD DESCRIPTOR ID field

ROD
PRODUCER
CSCD REMOTE
DESCRIPTOR R_TOKEN ROD TYPE TOKENS
a
ID field bit field field Description
n/a 1 zero n/a the command shall be terminated b
FFFFh 0 n/a n/a process the command
1 not zero n/a process the command
F800h 0 or 1 not zero n/a the command shall be terminated b
0 zero n/a process the command
local c
zero 0h remote ROD tokens not supported d
remote c 4h process the command
e
Others 0 not zero 0h remote ROD tokens not supported d
4h the command shall be terminated b
zero 0h remote ROD tokens not supported d
4h process the command
1 not zero 0h remote ROD tokens not supported d
4h remote ROD token creation not supported f
6h process the command
a
Refers to the REMOTE TOKENS field is in the ROD Features third-party copy descriptor (see 7.8.17.8).
Remote tokens values not shown in this table are n/a.
b The copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status,
with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN
PARAMETER LIST.
c Processing depends on the copy manager that created the ROD token specified by the ROD TOKEN
OFFSET field as follows:
a) local: a ROD token created by a copy manager that is contained within the same SCSI target
device that is processing the copy operation originated by the EXTENDED COPY command; or
b) remote: a ROD token created by a copy manager that is not contained within the same SCSI target
device that is processing the copy operation originated by the EXTENDED COPY command.
d
The copy manager shall terminate the copy operation with CHECK CONDITION status, with the sense
key set to ILLEGAL REQUEST, and the additional sense code set to INVALID TOKEN OPERATION,
REMOTE ROD TOKEN USAGE NOT SUPPORTED.
e Any other CSCD descriptor ID (i.e., not FFFFh and not F800h) that specifies a logical unit not contained
within the same SCSI target device as the processing copy manager.
f The copy manager shall terminate the copy operation with CHECK CONDITION status, with the sense
key set to ILLEGAL REQUEST, and the additional sense code set to INVALID TOKEN OPERATION,
REMOTE ROD TOKEN CREATION NOT SUPPORTED.

If the copy manager is unable to process the requested activities with the remote copy manager specified by
the ROD PRODUCER CSCD DESCRIPTOR ID field necessary to use or create a remote ROD token, then the copy

Working Draft SCSI Primary Commands - 4 (SPC-4) 307

T10/BSR INCITS 513 Revision 37 17 May 2014

manager shall terminate the copy operation (see 5.16.4.3) as if an unreachable CSCD device had been
encountered (see 5.16.7.4).

If the R_TOKEN bit is set to one, the REQUESTED ROD TOKEN LIFETIME field specifies the number of seconds the
ROD token should remain valid (see 5.16.6.7).

If the REQUESTED ROD TOKEN LIFETIME field specifies a number of seconds that is less than the value in the
MINIMUM TOKEN LIFETIME field in the ROD Features third-party copy descriptor (see 7.8.17.8), then the copy
manager shall use the value in the MINIMUM TOKEN LIFETIME field. If the REQUESTED ROD TOKEN LIFETIME field
specifies a number of seconds that is greater than the value in the MAXIMUM TOKEN LIFETIME field in the ROD
Features third-party copy descriptor, then the copy manager shall terminate the copy operation (see 5.16.4.3)
with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense
code set to INVALID FIELD IN PARAMETER LIST.

If the R_TOKEN bit is set to zero and the REQUESTED ROD TOKEN LIFETIME field is not set to zero, then the copy
manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the sense
key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

If the R_TOKEN bit is set to one, the REQUESTED ROD TOKEN INACTIVITY TIMEOUT field specifies number of
seconds that the copy manager should wait for the next third-party copy command that specifies the ROD
token, if any, before invalidating that ROD token (see 5.16.6.7).

If the REQUESTED ROD TOKEN INACTIVITY TIMEOUT field specifies zero seconds, then the copy manager shall not
invalidate the ROD token due to the lack of its active use. If the REQUESTED ROD TOKEN INACTIVITY TIMEOUT
field specifies a number of seconds that is greater than the value in the MAXIMUM TOKEN INACTIVITY TIMEOUT
field in the ROD Features third-party copy descriptor (see 7.8.17.8), then the copy manager shall terminate
the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

If the R_TOKEN bit is set to zero and the REQUESTED ROD TOKEN INACTIVITY TIMEOUT field is not set to zero, then
the copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the
sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER
LIST.

Processing of the R_TOKEN bit depends on the value in the ROD TYPE field as follows:

a) If the ROD TYPE field is not set to zero, the R_TOKEN bit specifies whether a ROD token is to be
returned for the ROD created during processing of the EXTENDED COPY command as follows:
A) if the R_TOKEN bit is set to zero, a ROD token shall not be returned; or
B) if the R_TOKEN bit is set to one and table 146 does not require termination of the EXTENDED
COPY command with an error, then a ROD token shall be made available for retrieval using the
RECEIVE ROD TOKEN INFORMATION command (see 6.28);
or
b) if the ROD TYPE field is set to zero, the processing of the R_TOKEN bit shall be as shown in table 146.

If the LIST ID USAGE field (see 6.4.3.2) is set to a value other than 00b or 10b and the R_TOKEN bit is set to one,
then the copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status,
with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN
PARAMETER LIST.

The delete token ( DEL _ TKN ) bit specifies whether the ROD token, if any, specified by the ROD CSCD
descriptor should be deleted (see 5.16.6.7) when processing of the EXTENDED COPY command is complete

308 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

as shown in table 147.

Table 147 — DEL_TKN bit processing

DEL_TKN ROD TYPE

bit field ROD token created by Description
0 n/a n/a Processing of the command shall not cause the
ROD token, if any, to be deleted.
1 zero processing copy manager or The copy manager should delete the ROD token
a copy manager in the same after processing of the command has been
SCSI target device as the completed.
copy manager that created
the ROD token
a copy manager in different The copy manager may communicate with the copy
SCSI target device from the manager that created the ROD token to cause the
copy manager that created ROD token to be deleted after processing of the
the ROD token command has been completed.
not zero n/a The copy manager shall terminate the copy
operation (see 5.16.4.3) with CHECK CONDITION
status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set
to INVALID FIELD IN PARAMETER LIST.

If the ROD TYPE field is set to zero, the value in the ROD TOKEN OFFSET field is added to the location of the first
byte of inline data in the EXTENDED COPY parameter list (see 5.16.7.1) to locate the ROD token (see 5.16.6)
to be accessed via this ROD CSCD descriptor. If the ROD TYPE field is not set to zero and the ROD TOKEN
OFFSET field is not set to zero, then the copy manager shall terminate the copy operation (see 5.16.4.3) with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set
to INVALID FIELD IN PARAMETER LIST.

Working Draft SCSI Primary Commands - 4 (SPC-4) 309

T10/BSR INCITS 513 Revision 37 17 May 2014

6.4.6 Segment descriptors

6.4.6.1 Segment descriptors introduction

The descriptor type code (see table 132) values assigned to segment descriptors are shown in table 148.

Table 148 — EXTENDED COPY segment descriptor type codes (part 1 of 2)

Descriptor
type
code a Reference Description b Name b
00h 6.4.6.2 Copy from block device to stream device blockstream
01h 6.4.6.3 Copy from stream device to block device streamblock
02h 6.4.6.4 Copy from block device to block device blockblock
03h 6.4.6.5 Copy from stream device to stream device streamstream
04h 6.4.6.6 Copy inline data to stream device inlinestream
05h 6.4.6.7 Copy embedded data to stream device embeddedstream
06h 6.4.6.8 Read from stream device and discard streamdiscard
07h 6.4.6.9 Verify CSCD
08h 6.4.6.10 Copy block device with offset to stream device block<o>stream
09h 6.4.6.11 Copy stream device to block device with offset streamblock<o>
Copy block device with offset to block device with
0Ah 6.4.6.12 block<o>block<o>
offset
Copy from block device to stream device and hold a blockstream&
0Bh 6.4.6.2
copy of processed data for the application client c application client
Copy from stream device to block device and hold a streamblock&
0Ch 6.4.6.3
copy of processed data for the application client c application client
Copy from block device to block device and hold a blockblock&
0Dh 6.4.6.4
copy of processed data for the application client c application client
Copy from stream device to stream device and
hold a copy of processed data for the application streamstream&
0Eh 6.4.6.5
application client
client c
Read from stream device and hold a copy of streamdiscard&
0Fh 6.4.6.8
processed data for the application client c application client
a
A copy manager may not support all segment descriptor types. However, the copy manager shall list
all supported segment descriptor types in the Third-party Copy VPD page Supported Descriptors
descriptor (see 7.8.17.6), and in the parameter data for the RECEIVE COPY OPERATING
PARAMETERS command (see 6.22).
b Block devices are those with peripheral device type codes 00h (i.e, direct access block), 05h (i.e.,

CD/DVD), and 0Eh (i.e., simplified direct-access). Stream devices are those devices with peripheral
device type codes 01h (i.e., sequential-access) and 03h (i.e., processor). Sequential-access stream
(i.e., tape) devices are those with peripheral device type code 01h. See 6.6.2 for peripheral device type
code definitions.
c The application client uses the RECEIVE COPY DATA(LID4) command (see 6.20) or RECEIVE COPY

DATA(LID1) command (see 6.21) to retrieve data held for it by the copy manager (see 5.16.4.5).

310 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 148 — EXTENDED COPY segment descriptor type codes (part 2 of 2)

Descriptor
type
code a Reference Description b Name b
10h 6.4.6.13 Write filemarks to sequential-access device filemarktape
Space records or filemarks on sequential-access
11h 6.4.6.14 spacetape
device
12h 6.4.6.15 Locate on sequential-access device locatetape
13h 6.4.6.16 Tape device image copy <i>tape<i>tape
14h 6.4.6.17 Register persistent reservation key
Third party persistent reservations source I_T
15h 6.4.6.18
nexus
16h 6.4.6.19 Block device image copy <i>block<i>block
17h to
Reserved
BDh
BEh 6.4.6.20 Populate ROD from one or more block ranges RODblock ranges(n)
BFh 6.4.6.21 Populate ROD from one block range RODblock range(1)
a
A copy manager may not support all segment descriptor types. However, the copy manager shall list
all supported segment descriptor types in the Third-party Copy VPD page Supported Descriptors
descriptor (see 7.8.17.6), and in the parameter data for the RECEIVE COPY OPERATING
PARAMETERS command (see 6.22).
b Block devices are those with peripheral device type codes 00h (i.e, direct access block), 05h (i.e.,

CD/DVD), and 0Eh (i.e., simplified direct-access). Stream devices are those devices with peripheral
device type codes 01h (i.e., sequential-access) and 03h (i.e., processor). Sequential-access stream
(i.e., tape) devices are those with peripheral device type code 01h. See 6.6.2 for peripheral device type
code definitions.
c
The application client uses the RECEIVE COPY DATA(LID4) command (see 6.20) or RECEIVE COPY
DATA(LID1) command (see 6.21) to retrieve data held for it by the copy manager (see 5.16.4.5).

Working Draft SCSI Primary Commands - 4 (SPC-4) 311

T10/BSR INCITS 513 Revision 37 17 May 2014

Segment descriptors (see table 149) begin with an eight byte header.

Table 149 — Segment descriptor header

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (00h to 3Fh)
1 Reserved DC CAT

2 (MSB)
DESCRIPTOR LENGTH (n-3)
3 (LSB)
4 (MSB)
SOURCE CSCD DESCRIPTOR ID
5 (LSB)
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8
•• • Segment descriptor parameters
n

The DESCRIPTOR TYPE CODE field is described in 6.4.4. If a copy manager receives an unsupported descriptor
type code in a segment descriptor, the copy manager shall terminate the copy operation (see 5.16.4.3) with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set
to UNSUPPORTED SEGMENT DESCRIPTOR TYPE CODE.

The destination count (DC) bit is only applicable to segment descriptors with descriptor type code values of
02h and 0Dh (see 6.4.6.4). The DC bit shall be ignored for all other segment descriptors.

The CAT bit is described in 5.16.7.2.

The DESCRIPTOR LENGTH field is set to the length in bytes of the fields that follow the DESCRIPTOR LENGTH field
in the segment descriptor.

312 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The SOURCE CSCD DESCRIPTOR ID field (see table 150) specifies the copy source.

The DESTINATION CSCD DESCRIPTOR ID field (see table 150) specifies the copy destination.

Table 150 — CSCD descriptor ID values

Code Description

0000h a The copy source or copy destination is specified by the contents of the CSCD
descriptor whose location in the EXTENDED COPY command parameter list
0001h to 07FFh b (see 5.16.7.1) is computed as follows:
16 + (code  32)
where code is 0000h to 07FFh as shown in this table
C000h The copy source or copy destination is a null logical unit b whose peripheral
device type is 00h (i.e., block)
C001h The copy source or copy destination is a null logical unit b whose peripheral
device type is 01h (i.e., stream)
F800h c The copy source or copy destination is the logical unit specified by the ROD
token specified in the ROD CSCD descriptor (see 6.4.5.9) that has this value in
its ROD PRODUCER CSCD DESCRIPTOR ID field.
FFFFh The copy source or copy destination is the logical unit that contains the copy
manager (see SAM-5) that is processing the EXTENDED COPY command
(i.e., the logical unit to which the EXTENDED COPY command was sent)
all others Reserved
a
If a SOURCE CSCD DESCRIPTOR ID field or a DESTINATION CSCD DESCRIPTOR ID field is set to this value,
the copy manager may terminate the copy operation (see 5.16.4.3) with CHECK CONDITION
status (see 6.4.2).
b
A null logical unit is a logical unit that has a specified peripheral device type to which the copy
manager is not allowed to send any SCSI commands. If the processing of a segment descriptor
requires sending a SCSI command to a source device or destination device specified to be a null
logical unit, then the copy manager shall terminate the copy operation (see 5.16.4.3) as if an
unreachable CSCD had been encountered (see 5.16.7.4). Null logical units are useful for
processing the residual data from previous segment descriptors without affecting any media (e.g.,
a segment descriptor of type 06h stream device to discard with the SOURCE CSCD DESCRIPTOR ID
field set to C002h, the BYTE COUNT field set to zero, the CAT bit set to zero, and the PAD bit set to
one may be used to discard all residual data).
c
If this code appears in any field other than the ROD PRODUCER CSCD DESCRIPTOR ID field in the ROD
CSCD descriptor, then the copy manager shall terminate the copy operation (see 5.16.4.3) as if an
unreachable CSCD had been encountered (see 5.16.7.4).

If a segment descriptor format does not require a SOURCE CSCD DESCRIPTOR ID field or a DESTINATION CSCD
DESCRIPTOR ID field, then that field is reserved.

If the CSCD specified by a SOURCE CSCD DESCRIPTOR ID field or a DESTINATION CSCD DESCRIPTOR ID field is not
accessible to the copy manager, then the copy manager shall terminate the copy operation (see 5.16.4.3) with
CHECK CONDITION status, with the sense key set to COPY ABORTED, and the additional sense code set to
UNREACHABLE COPY TARGET.

Working Draft SCSI Primary Commands - 4 (SPC-4) 313

T10/BSR INCITS 513 Revision 37 17 May 2014

6.4.6.2 Block device to stream device functions

The segment descriptor format shown in table 151 is used by the copy functions that move data from a block
device to a stream device.

Table 151 — Block device to stream device segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (00h or 0Bh)
1 Reserved CAT

2 (MSB)
DESCRIPTOR LENGTH (0014h)
3 (LSB)
4 (MSB)
SOURCE CSCD DESCRIPTOR ID
5 (LSB)
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 Reserved
9 (MSB)
10 STREAM DEVICE TRANSFER LENGTH

11 (LSB)
12 Reserved
13 Reserved
14 (MSB)
BLOCK DEVICE NUMBER OF BLOCKS
15 (LSB)
16 (MSB)
•• • BLOCK DEVICE LOGICAL BLOCK ADDRESS
23 (LSB)

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1.

For descriptor type code 00h (i.e., blockstream) or descriptor type code 0Bh (i.e., blockstream&application
client), the copy manager shall copy the data from the copy source block device specified by the SOURCE CSCD
DESCRIPTOR ID field to the copy destination stream device specified by the DESTINATION CSCD DESCRIPTOR ID
field using the logical blocks starting at the location specified by the BLOCK DEVICE LOGICAL BLOCK ADDRESS
field. As many logical blocks shall be read as necessary to process (see 5.16.7.2) a number of bytes equal to
the contents of the DISK BLOCK LENGTH field in the CSCD descriptor for the source device times the contents of
the BLOCK DEVICE NUMBER OF BLOCKS field. The data shall be written to the stream device starting at the
current position of the media.

For descriptor type code 0Bh (i.e., blockstream&application client), the copy manager also shall hold a copy
of the processed data for delivery to the application client upon completion of the copy operation (see
5.16.4.3) originated by the EXTENDED COPY command as described in 5.16.4.5.

The CAT bit is described in 5.16.7.2.

314 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The DESCRIPTOR LENGTH field is described in 6.4.6.1, and shall be set as shown in table 151 for descriptor type
code 00h (i.e., blockstream) and descriptor type code 0Bh (i.e., blockstream&application client).

The SOURCE CSCD DESCRIPTOR ID field and DESTINATION CSCD DESCRIPTOR ID field are described in 6.4.6.1.

The STREAM DEVICE TRANSFER LENGTH field specifies the amount of data to be written by each write command
sent to the copy destination stream device. See 6.4.5.4 for a description of how data in the STREAM DEVICE
TRANSFER LENGTH field in the segment descriptor interacts with data in the STREAM BLOCK LENGTH field in the
device type specific CSCD descriptor parameters for the copy destination sequential-access device type.

The BLOCK DEVICE NUMBER OF BLOCKS field specifies the length, in copy source logical blocks, of data to be
processed (see 5.16.7.2) in the segment. A value of zero shall not be considered an error. No data shall be
processed, but any residual destination data retained from a previous segment shall be written if possible to
the destination in whole block transfers. A value of zero shall not modify the handling of residual data.

The BLOCK DEVICE LOGICAL BLOCK ADDRESS field specifies the starting logical block address on the copy source
block device for this segment.

6.4.6.3 Stream device to block device functions

The segment descriptor format shown in table 152 is used by the copy functions that move data from a stream
device to a block device.

Table 152 — Stream device to block device segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (01h or 0Ch)
1 Reserved CAT

2 (MSB)
DESCRIPTOR LENGTH (0014h)
3 (LSB)
4 (MSB)
SOURCE CSCD DESCRIPTOR ID
5 (LSB)
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 Reserved
9 (MSB)
10 STREAM DEVICE TRANSFER LENGTH

11 (LSB)
12 Reserved
13 Reserved
14 (MSB)
BLOCK DEVICE NUMBER OF BLOCKS
15 (LSB)
16 (MSB)
•• • BLOCK DEVICE LOGICAL BLOCK ADDRESS
23 (LSB)

Working Draft SCSI Primary Commands - 4 (SPC-4) 315

T10/BSR INCITS 513 Revision 37 17 May 2014

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1.

For descriptor type code 01h (i.e., streamblock) or descriptor type code 0Ch (i.e., streamblock&application
client), the copy manager shall copy the data from the copy source stream device specified by the SOURCE
CSCD DESCRIPTOR ID field to the copy destination block device specified by the DESTINATION CSCD DESCRIPTOR
ID field using the stream data starting at the current position of the stream device. The data shall be written to
logical blocks starting at the location specified by the BLOCK DEVICE LOGICAL BLOCK ADDRESS field and
continuing for the number of logical blocks specified in the BLOCK DEVICE NUMBER OF BLOCKS field.

For descriptor type code 0Ch (i.e., streamblock&application client), the copy manager also shall hold a copy
of the processed data for delivery to the application client upon completion of the copy operation (see
5.16.4.3) originated by the EXTENDED COPY command as described in 5.16.4.5.

The CAT bit is described in 5.16.7.2.

The DESCRIPTOR LENGTH field is described in 6.4.6.1, and shall be set as shown in table 152 for descriptor type
code 01h (i.e., streamblock) and descriptor type code 0Ch (i.e., streamblock&application client).

The SOURCE CSCD DESCRIPTOR ID field and DESTINATION CSCD DESCRIPTOR ID field are described in 6.4.6.1.

The STREAM DEVICE TRANSFER LENGTH field specifies the amount of data to be read from the copy source
stream device by each read command. See 6.4.5.4 for a description of how data in the STREAM DEVICE
TRANSFER LENGTH field in the segment descriptor interacts with data in the STREAM BLOCK LENGTH field in the
device type specific CSCD descriptor parameters for the copy source sequential-access device type.

The BLOCK DEVICE NUMBER OF BLOCKS field specifies the number logical blocks to be written by the segment. A
value of zero specifies that no logical blocks shall be written in this segment. This shall not be considered an
error.

The BLOCK DEVICE LOGICAL BLOCK ADDRESS field specifies the starting logical block address on the copy
destination block device for this segment.

316 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4.6.4 Block device to block device functions

The segment descriptor format shown in table 153 is used by the copy functions that move data from a block
device to a block device.

Table 153 — Block device to block device segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (02h or 0Dh)
1 Reserved DC CAT

2 (MSB)
DESCRIPTOR LENGTH (0018h)
3 (LSB)
4 (MSB)
SOURCE CSCD DESCRIPTOR ID
5 (LSB)
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 Reserved
9 Reserved
10 (MSB)
BLOCK DEVICE NUMBER OF BLOCKS
11 (LSB)
12 (MSB)
•• • SOURCE BLOCK DEVICE LOGICAL BLOCK ADDRESS
19 (LSB)
20 (MSB)
DESTINATION BLOCK DEVICE LOGICAL BLOCK
•• •
ADDRESS
27 (LSB)

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1.

For descriptor type code 02h (i.e., blockblock) or descriptor type code 0Dh (i.e., blockblock&application
client), the copy manager shall copy the data from the copy source block device specified by the SOURCE CSCD
DESCRIPTOR ID field to the copy destination block device specified by the DESTINATION CSCD DESCRIPTOR ID field
using the logical blocks starting at the location specified by the SOURCE BLOCK DEVICE LOGICAL BLOCK ADDRESS
field. The data shall be written to logical blocks starting at the location specified by the DESTINATION BLOCK
DEVICE LOGICAL BLOCK ADDRESS field.

If the destination count (DC) bit is set to zero, then:

a) as many logical blocks shall be read as necessary to process (see 5.16.7.2) a number of bytes equal
to the contents of the DISK BLOCK LENGTH field in the CSCD descriptor for the copy source device
times the contents of the BLOCK DEVICE NUMBER OF BLOCKS field; and
b) as many writes as possible shall be performed using any residual destination data from the previous
segment and the data processed in this segment.

Working Draft SCSI Primary Commands - 4 (SPC-4) 317

T10/BSR INCITS 513 Revision 37 17 May 2014

If the DC bit is set to one, then:

a) the number of logical blocks specified by the BLOCK DEVICE NUMBER OF BLOCKS field shall be written to
the copy destination block device;
b) as many bytes shall be processed (see 5.16.7.2) as necessary for these writes to be performed; and
c) as many logical blocks shall be read as necessary to supply the data to be processed.

For descriptor type code 0Dh (i.e., blockblock&application client), the copy manager also shall hold a copy
of the processed data for delivery to the application client upon completion of the copy operation (see
5.16.4.3) originated by the EXTENDED COPY command as described in 5.16.4.5.

The CAT bit is described in 5.16.7.2.

The DC bit specifies whether the BLOCK DEVICE NUMBER OF BLOCKS field refers to the copy source or copy
destination. A DC bit set to zero specifies that the BLOCK DEVICE NUMBER OF BLOCKS field refers to the copy
source. A DC bit set to one specifies that the BLOCK DEVICE NUMBER OF BLOCKS field refers to the copy
destination.

The DESCRIPTOR LENGTH field shall is described in 6.4.6.16.3.7.1, and shall be set as shown in table 153 for
descriptor type code 02h (i.e., blockblock) and descriptor type code 0Dh (i.e., blockblock&application
client).

The SOURCE CSCD DESCRIPTOR ID field and DESTINATION CSCD DESCRIPTOR ID field are described in 6.4.6.1.

If the DC bit is set to zero, the BLOCK DEVICE NUMBER OF BLOCKS field specifies the number of logical blocks to
be processed. If the DC bit is set to one, the BLOCK DEVICE NUMBER OF BLOCKS field specifies the number of
logical blocks to be written to the copy destination.

If the DC bit is set to zero, a BLOCK DEVICE NUMBER OF BLOCKS field set to zero specifies that:

a) no source logical blocks shall be read and no source data shall be processed;
b) any residual destination data from a previous segment shall be written if possible to the destination in
whole logical block transfers; and
c) any residual data shall be processed as described in 5.16.7.2.

If the DC bit set to one, a BLOCK DEVICE NUMBER OF BLOCKS field set to zero specifies that:

a) no destination logical blocks shall be written; and

b) the only processing to be performed is that any residual source data or destination data from the
previous segment shall be processed as residual data as described in 5.16.7.2.

The SOURCE BLOCK DEVICE LOGICAL BLOCK ADDRESS field specifies the copy source logical block address from
which the reading of data shall start.

The DESTINATION BLOCK DEVICE LOGICAL BLOCK ADDRESS field specifies the copy destination logical block
address to which the writing of data shall begin.

318 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4.6.5 Stream device to stream device functions

The segment descriptor format shown in table 154 is used by the copy functions that move data from a stream
device to a stream device.

Table 154 — Stream device to stream device segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (03h or 0Eh)
1 Reserved CAT

2 (MSB)
DESCRIPTOR LENGTH (0010h)
3 (LSB)
4 (MSB)
SOURCE CSCD DESCRIPTOR ID
5 (LSB)
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 Reserved
9 (MSB)
10 SOURCE STREAM DEVICE TRANSFER LENGTH

11 (LSB)
12 Reserved
13 (MSB)
14 DESTINATION STREAM DEVICE TRANSFER LENGTH

15 (LSB)
16 (MSB)
•• • BYTE COUNT
19 (LSB)

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1.

For descriptor type code 03h (i.e., streamstream) or descriptor type code 0Eh (i.e.,
streamstream&application client), the copy manager shall copy the data from the copy source stream device
specified by the SOURCE CSCD DESCRIPTOR ID field to the destination copy stream device specified by the
DESTINATION CSCD DESCRIPTOR ID field. Data shall be read from the copy source stream device starting at the
current position of the copy source stream device. Data shall be written to the copy destination stream device
starting at the current position of the copy destination stream device. The BYTE COUNT field defines the number
of bytes to be processed (see 5.16.7.2) by the copy manager. The copy manager shall perform reads as
necessary to supply the source data, and as many writes as possible using the destination data.

For descriptor type code 0Eh (i.e., streamstream&application client), the copy manager also shall hold a
copy of the processed data for delivery to the application client upon completion of the copy operation (see
5.16.4.3) originated by the EXTENDED COPY command as described in 5.16.4.5.

The CAT bit is described in 5.16.7.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 319

T10/BSR INCITS 513 Revision 37 17 May 2014

The DESCRIPTOR LENGTH field is described in 6.4.6.1, and shall be set as shown in table 154 for descriptor type
code 03h (i.e., streamstream) and descriptor type code 0Eh (i.e., streamstream&application client).

The SOURCE CSCD DESCRIPTOR ID field and DESTINATION CSCD DESCRIPTOR ID field are described in 6.4.6.1.

The SOURCE STREAM DEVICE TRANSFER LENGTH field specifies the amount of data to be read from the copy
source stream device by each read command. See 6.4.5.4 for a description of how data in the SOURCE STREAM
DEVICE TRANSFER LENGTH field in the segment descriptor interacts with data in the STREAM BLOCK LENGTH field
in the device type specific CSCD descriptor parameters for the copy source sequential-access device type.

The DESTINATION STREAM DEVICE TRANSFER LENGTH field specifies the amount of data to be written to the copy
destination stream device by each write command. See 6.4.5.4 for a description of how data in the
DESTINATION STREAM DEVICE TRANSFER LENGTH field in the segment descriptor interacts with data in the STREAM
BLOCK LENGTH field in the device type specific CSCD descriptor parameters for the copy destination
sequential-access device type.

The BYTE COUNT field specifies the number of bytes that shall be processed (see 5.16.7.2) for this segment
descriptor. A value of zero shall not be considered an error, and specifies that no source data shall be read
and no source data shall be processed. However, a value of zero specifies that any residual destination data
from a previous segment shall be written if possible to the copy destination in whole-block transfers, and any
residual data shall be processed as described in 5.16.7.2.

320 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4.6.6 Inline data to stream device function

The segment descriptor format shown in table 155 requests the copy manager to write inline data from the
EXTENDED COPY parameter list to a stream device.

Table 155 — Inline data to stream device segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (04h)
1 Reserved CAT

2 (MSB)
DESCRIPTOR LENGTH (0010h)
3 (LSB)
4 Reserved
5 Reserved
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 Reserved
9 (MSB)
10 STREAM DEVICE TRANSFER LENGTH

11 (LSB)
12 (MSB)
•• • INLINE DATA OFFSET
15 (LSB)
16 (MSB)
•• • INLINE DATA NUMBER OF BYTES
19 (LSB)

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1, and shall be set as shown in table 155 for
the inline data to stream device segment descriptor.

Descriptor type code 04h (i.e., inlinestream) requests the copy manager to write inline data to a copy
destination stream device. The inline data shall be read from the inline data in the EXTENDED COPY
parameter list (see 5.16.7.1). The data shall be written to the copy destination stream device specified by the
DESTINATION CSCD DESCRIPTOR ID field starting at the current position of the stream device. Any residual
destination data from a previous segment descriptor shall be written before the data of the current segment
descriptor. Any residual source data from a previous segment descriptor shall not be processed (see
5.16.7.2), and shall be processed as residual source data.

The CAT bit is described in 5.16.7.2.

The DESCRIPTOR LENGTH field is described in 6.4.6.1, and shall be set as shown in table 155 for descriptor type
code 04h (i.e., inlinestream).

The DESTINATION CSCD DESCRIPTOR ID field is described in 6.4.6.1.

Working Draft SCSI Primary Commands - 4 (SPC-4) 321

T10/BSR INCITS 513 Revision 37 17 May 2014

The STREAM DEVICE TRANSFER LENGTH field specifies the amount of data to be written to the copy destination
stream device by each write command. See 6.4.5.4 for a description of how data in the STREAM DEVICE
TRANSFER LENGTH field in the segment descriptor interacts with data in the STREAM BLOCK LENGTH field in the
device type specific CSCD descriptor parameters for the copy destination sequential-access device type.

The value in the INLINE DATA OFFSET field is added to the location of the first byte of inline data in the
EXTENDED COPY parameter list (see 5.16.7.1) to locate the first byte of inline data to be written to the copy
destination stream device. The INLINE DATA OFFSET value shall be a multiple of 4.

The INLINE DATA NUMBER OF BYTES field specifies the number of bytes of inline data that are to be transferred to
the copy destination stream device. A value of zero shall not be considered an error.

If the sum of the INLINE DATA OFFSET and the INLINE DATA NUMBER OF BYTES values exceeds the value in the
INLINE DATA LENGTH field (see 6.4.3.6), then the copy manager shall terminate the copy operation (see
5.16.4.3) with CHECK CONDITION status, with the sense key set to COPY ABORTED, and the additional
sense code set to INLINE DATA LENGTH EXCEEDED.

6.4.6.7 Embedded data to stream device function

The segment descriptor format shown in table 156 requests the copy manager to write embedded data from
the segment descriptor to a stream device.

Table 156 — Embedded data to stream device segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (05h)
1 Reserved CAT

2 (MSB)
DESCRIPTOR LENGTH (n-3)
3 (LSB)
4 Reserved
5 Reserved
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 Reserved
9 (MSB)
10 STREAM DEVICE TRANSFER LENGTH

11 (LSB)
12 (MSB)
EMBEDDED DATA NUMBER OF BYTES
13 (LSB)
14
Reserved
15
16
•• • EMBEDDED DATA
n

322 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1, and shall be set as shown in table 156 for
the embedded data to stream device segment descriptor.

Descriptor type code 05h (i.e., embeddedstream) requests the copy manager to write embedded data from
the segment descriptor to a copy destination stream device. The embedded data shall be read from the
segment descriptor. The data shall be written to the copy destination stream device specified by the
DESTINATION CSCD DESCRIPTOR ID field starting at the current position of the copy destination stream device.
Any residual destination data from a previous segment descriptor shall be written before the data of the
current segment descriptor. Any residual source data from a previous segment descriptor shall not be
processed (see 5.16.7.2), and shall be processed as residual source data.

The CAT bit is described in 5.16.7.2.

The DESCRIPTOR LENGTH field is described in 6.4.6.1. The value in the DESCRIPTOR LENGTH field shall be a
multiple of 4.

The DESTINATION CSCD DESCRIPTOR ID field is described in 6.4.6.1.

The STREAM DEVICE TRANSFER LENGTH field specifies the amount of data to be written to the copy destination
stream device by each write command. See 6.4.5.4 for a description of how data in the STREAM DEVICE
TRANSFER LENGTH field in the segment descriptor interacts with data in the STREAM BLOCK LENGTH field in the
device type specific CSCD descriptor parameters for the copy destination sequential-access device type.

The EMBEDDED DATA NUMBER OF BYTES field specifies the number of bytes of embedded data that are to be
transferred to the copy destination stream device. A value of zero shall not be considered an error. If the value
in the EMBEDDED DATA NUMBER OF BYTES field is greater than the value in the DESCRIPTOR LENGTH field minus
12, then the copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status,
with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN
PARAMETER LIST.

The EMBEDDED DATA field is a zero-padded (see 4.3.2) field whose length is a multiple of 4 that specifies the
embedded data to be copied to the copy destination stream device.

Working Draft SCSI Primary Commands - 4 (SPC-4) 323

T10/BSR INCITS 513 Revision 37 17 May 2014

6.4.6.8 Stream device to discard functions

The segment descriptor format shown in table 157 requests the copy manager to read data from a stream
device and not transfer it to any copy destination.

Table 157 — Stream device to discard segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (06h or 0Fh)
1 Reserved CAT

2 (MSB)
DESCRIPTOR LENGTH (000Ch)
3 (LSB)
4 (MSB)
SOURCE CSCD DESCRIPTOR ID
5 (LSB)
6 Reserved
7 Reserved
8 Reserved
9 (MSB)
10 STREAM DEVICE TRANSFER LENGTH

11 (LSB)
12 (MSB)
•• • NUMBER OF BYTES
15 (LSB)

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1.

For descriptor type code 06h (i.e., streamdiscard) or descriptor type code 0Fh (i.e.,
streamdiscard&application client), the copy manager shall read data as necessary from the copy source
stream device specified by the SOURCE CSCD DESCRIPTOR ID field starting at the current position of the copy
source stream device. The number of bytes specified by the NUMBER OF BYTES field shall be removed from the
source data, starting with any residual source data from the previous segment.

For descriptor type code 06h (i.e., streamdiscard) the removed data shall be discarded and not written to
any copy destination.

For descriptor type code 0Fh (i.e., streamdiscard&application client) the removed data shall be held for
delivery to the application client upon completion of the copy operation (see 5.16.4.3) originated by the
EXTENDED COPY command as described in 5.16.4.5.

The CAT bit is described in 5.16.7.2.

The DESCRIPTOR LENGTH field is described in 6.4.6.1, shall be set as shown in table 157 for descriptor type
code 0Fh (i.e., streamdiscard&application client) and descriptor type code 0Fh (i.e.,
streamdiscard&application client).

The DESTINATION CSCD DESCRIPTOR ID field is described in 6.4.6.1.

324 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The SOURCE STREAM DEVICE TRANSFER LENGTH field specifies the amount of data to be read from the copy
source stream device on each read command. See 6.4.5.4 for a description of how data in the SOURCE
STREAM DEVICE TRANSFER LENGTH field in the segment descriptor interacts with data in the STREAM BLOCK
LENGTH field in the device type specific CSCD descriptor parameters for the copy source sequential-access
device type.

The NUMBER OF BYTES field specifies the number of bytes to be removed from the source data.

6.4.6.9 Verify CSCD function

The segment descriptor format shown in table 158 requests the copy manager to verify the accessibility of a
CSCD.

Table 158 — Verify CSCD segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (07h)
1 Reserved
2 (MSB)
DESCRIPTOR LENGTH (0008h)
3 (LSB)
4 (MSB)
SOURCE CSCD DESCRIPTOR ID
5 (LSB)
6
Reserved
7
8 Reserved TUR

9
•• • Reserved
11

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1, and shall be set as shown in table 158 for
the verify CSCD segment descriptor.

Descriptor type code 07h requests the copy manager to verify the accessibility of the CSCD specified by the
SOURCE CSCD DESCRIPTOR ID field.

The DESCRIPTOR LENGTH field is described in 6.4.6.1, and shall be set as shown in table 158 for the verify
CSCD segment descriptor.

The SOURCE CSCD DESCRIPTOR ID field is described in 6.4.6.1.

Support for a value of one in the test unit ready (TUR) bit is optional. If setting the TUR bit to one is supported
and the TUR bit is set to one, then a TEST UNIT READY command (see 6.47) shall be used to determine the
readiness of the CSCD. If setting the TUR to one is not supported and the TUR bit is set to one, the copy
manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the sense
key set to COPY ABORTED, and the additional sense code set to INVALID FIELD IN PARAMETER LIST. The
sense key specific information shall be set as described in 5.16.7.4. If the TUR bit is set to zero, then the
accessibility should be verified without disturbing established unit attention conditions or ACA conditions (e.g.,
using the INQUIRY command (see 6.6)).

Working Draft SCSI Primary Commands - 4 (SPC-4) 325

T10/BSR INCITS 513 Revision 37 17 May 2014

If the SOURCE CSCD DESCRIPTOR ID field specifies a ROD CSCD descriptor (see 6.4.5.9), the copy manager
shall ignore the TUR bit and shall process the Verify CSCD segment descriptor based on the contents of ROD
TYPE field as follows:

a) if the ROD TYPE field is set to zero, the copy manager shall verify the accessibility as follows:
A) if the ROD token was created by the copy manager that is processing the Verify CSCD segment
descriptor, then the ROD token shall be validated as described in 5.16.6.5.2;
B) if the ROD token was created by a copy manager in the same SCSI target device as the copy
manager that is processing the Verify CSCD segment descriptor, then the creating copy manager
shall be requested to validate the ROD token as described in 5.16.6.5.2; and
C) if the ROD token was created by a copy manager in a SCSI target device other than the SCSI
target device that contains the copy manager that is processing the Verify CSCD segment
descriptor, then the validation of the ROD token depends on the contents of the REMOTE TOKENS
field in the ROD Features third-party copy descriptor (see 7.8.17.8) as follows:
a) if the REMOTE TOKENS field is set to 0h, the copy manager shall terminate the copy operation
(see 5.16.4.3) with CHECK CONDITION status with the sense key set to ILLEGAL
REQUEST and the additional sense code set to INVALID TOKEN OPERATION, REMOTE
TOKEN USAGE NOT SUPPORTED; or
b) if the REMOTE TOKENS field is not set to 0h, the processing copy manager shall request the
copy manager that created the ROD token to validate it;
or
b) if the ROD TYPE field is not set to zero, the processing copy manager shall ignore the Verify CSCD
segment descriptor. This shall not be considered an error.

326 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4.6.10 Block device with offset to stream device function

The segment descriptor format shown in table 159 requests the copy manager to move data from a block
device with a byte offset to a stream device.

Table 159 — Block device with offset to stream device segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (08h)
1 Reserved CAT

2 (MSB)
DESCRIPTOR LENGTH (0018h)
3 (LSB)
4 (MSB)
SOURCE CSCD DESCRIPTOR ID
5 (LSB)
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 Reserved
9 (MSB)
10 STREAM DEVICE TRANSFER LENGTH

11 (LSB)
12 (MSB)
•• • NUMBER OF BYTES
15 (LSB)
16 (MSB)
•• • BLOCK DEVICE LOGICAL BLOCK ADDRESS
23 (LSB)
24 Reserved
25 Reserved
26 (MSB)
BLOCK DEVICE BYTE OFFSET
27 (LSB)

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1, and shall be set as shown in table 159 for
the block device with offset to stream device segment descriptor.

Descriptor type code 08h (i.e., block<o>stream) requests the copy manager to copy the data from the copy
source block device specified by the SOURCE CSCD DESCRIPTOR ID field to the copy destination stream device
specified by the DESTINATION CSCD DESCRIPTOR ID field using data starting at the location specified by the
BLOCK DEVICE BYTE OFFSET field in the logical block specified by the BLOCK DEVICE LOGICAL BLOCK ADDRESS
field and continuing for the number of bytes specified in the NUMBER OF BYTES field. The data shall be written to
the copy destination stream device starting at the current position of the media.

The CAT bit is described in 5.16.7.2.

The DESCRIPTOR LENGTH field is described in 6.4.6.1, and shall be set as shown in table 159 for the block
device with offset to stream device segment descriptor.

Working Draft SCSI Primary Commands - 4 (SPC-4) 327

T10/BSR INCITS 513 Revision 37 17 May 2014

The SOURCE CSCD DESCRIPTOR ID field and DESTINATION CSCD DESCRIPTOR ID field are described in 6.4.6.1.

The STREAM DEVICE TRANSFER LENGTH field specifies the amount of data to be written by each write command
sent to the copy destination stream device. See 6.4.5.4 for a description of how data in the STREAM DEVICE
TRANSFER LENGTH field in the segment descriptor interacts with data in the STREAM BLOCK LENGTH field in the
device type specific CSCD descriptor parameters for the copy destination sequential-access device type.

The NUMBER OF BYTES field specifies the number bytes to be read. A value of zero specifies that no bytes shall
be transferred in this segment. This shall not be considered an error.

The BLOCK DEVICE LOGICAL BLOCK ADDRESS field specifies the starting logical block address on the copy source
block device for this segment.

The BLOCK DEVICE BYTE OFFSET field specifies the offset into the first copy source logical block at which to
begin reading bytes.

328 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4.6.11 Stream device to block device with offset function

The segment descriptor format shown in table 160 requests the copy manager to move data from a stream
device to a block device with a byte offset.

Table 160 — Stream device with offset to block device segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (09h)
1 Reserved CAT

2 (MSB)
DESCRIPTOR LENGTH (0018h)
3 (LSB)
4 (MSB)
SOURCE CSCD DESCRIPTOR ID
5 (LSB)
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 Reserved
9 (MSB)
10 STREAM DEVICE TRANSFER LENGTH

11 (LSB)
12 (MSB)
•• • NUMBER OF BYTES
15 (LSB)
16 (MSB)
•• • BLOCK DEVICE LOGICAL BLOCK ADDRESS
23 (LSB)
24 Reserved
25 Reserved
26 (MSB)
BLOCK DEVICE BYTE OFFSET
27 (LSB)

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1, and shall be set as shown in table 160 for
the stream device with offset to block device segment descriptor.

Descriptor type code 09h (i.e., streamblock<o>) requests the copy manager to copy the data from the copy
source stream device specified by the SOURCE CSCD DESCRIPTOR ID field to the copy destination block device
specified by the DESTINATION CSCD DESCRIPTOR ID field using the stream data starting at the current position of
the copy source stream device. The data shall be written starting at the location specified by the BLOCK DEVICE
BYTE OFFSET field in the logical block specified by the BLOCK DEVICE LOGICAL BLOCK ADDRESS field and
continuing for the number of bytes specified in the NUMBER OF BYTES field.

Working Draft SCSI Primary Commands - 4 (SPC-4) 329

T10/BSR INCITS 513 Revision 37 17 May 2014

The content of the starting logical block on the copy destination block device before the starting offset shall be
preserved. The content on the ending logical block on the copy destination block device beyond the end of the
transfer shall be preserved. The copy manager may implement this function by reading the starting and
ending logical blocks, modifying a portion of the logical blocks as required, and writing the full logical blocks to
the copy destination block device.

The CAT bit is described in 5.16.7.2.

The DESCRIPTOR LENGTH field is described in 6.4.6.1, and shall be set as shown in table 160 for the stream
device with offset to block device segment descriptor.

The SOURCE CSCD DESCRIPTOR ID field and DESTINATION CSCD DESCRIPTOR ID field are described in 6.4.6.1.

The STREAM DEVICE TRANSFER LENGTH field specifies the amount of data to be read from the copy source
stream device by each read command. See 6.4.5.4 for a description of how data in the STREAM DEVICE
TRANSFER LENGTH field in the segment descriptor interacts with data in the STREAM BLOCK LENGTH field in the
device type specific CSCD descriptor parameters for the copy source sequential-access device type.

The NUMBER OF BYTES field specifies the number bytes to be read. A value of zero specifies that no bytes shall
be transferred in this segment. This shall not be considered an error.

The BLOCK DEVICE LOGICAL BLOCK ADDRESS field specifies the starting logical block address on the copy
destination block device for this segment.

The BLOCK DEVICE BYTE OFFSET field specifies the offset into the first destination logical block at which to begin
writing data to the copy destination block device.

330 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4.6.12 Block device with offset to block device with offset function

The segment descriptor format shown in table 161 requests the copy manager to move data from a block
device with a byte offset to a block device with a byte offset.

Table 161 — Block device with offset to block device with offset segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (0Ah)
1 Reserved CAT

2 (MSB)
DESCRIPTOR LENGTH (001Ch)
3 (LSB)
4 (MSB)
SOURCE CSCD DESCRIPTOR ID
5 (LSB)
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 (MSB)
•• • NUMBER OF BYTES
11 (LSB)
12 (MSB)
•• • SOURCE BLOCK DEVICE LOGICAL BLOCK ADDRESS
19 (LSB)
20 (MSB)
DESTINATION BLOCK DEVICE LOGICAL BLOCK
•• •
ADDRESS
27 (LSB)
28 (MSB)
SOURCE BLOCK DEVICE BYTE OFFSET
29 (LSB)
30 (MSB)
DESTINATION BLOCK DEVICE BYTE OFFSET
31 (LSB)

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1, and shall be set as shown in table 161 for
the block device with offset to block device with offset segment descriptor.

Descriptor type code 0Ah (i.e., block<o>block<o>) requests the copy manager to copy the data from the
copy source block device specified by the SOURCE CSCD DESCRIPTOR ID field to the copy destination block
device specified by the DESTINATION CSCD DESCRIPTOR ID field using data starting at the location specified by
the source BLOCK DEVICE BYTE OFFSET field in the logical block specified by the SOURCE BLOCK DEVICE LOGICAL
BLOCK ADDRESS field and continuing for the number of bytes specified in the NUMBER OF BYTES field. The data
shall be written to the copy destination block device starting at the location specified by the DESTINATION BLOCK
DEVICE BYTE OFFSET field in the logical block specified by the DESTINATION BLOCK DEVICE LOGICAL BLOCK
ADDRESS field.

The content of the starting logical block on the copy destination block device before the starting offset shall be
preserved. The content on the ending logical block on the copy destination block device beyond the end of the
transfer shall be preserved. The copy manager may implement this operation by reading the starting and

Working Draft SCSI Primary Commands - 4 (SPC-4) 331

T10/BSR INCITS 513 Revision 37 17 May 2014

ending logical blocks, modifying a portion of the logical blocks as required, and writing the full logical blocks on
the copy destination block device.

The CAT bit is described in 5.16.7.2.

The DESCRIPTOR LENGTH field is described in 6.4.6.1, and shall be set as shown in table 161 for the block
device with offset to block device with offset segment descriptor.

The SOURCE CSCD DESCRIPTOR ID field and DESTINATION CSCD DESCRIPTOR ID field are described in 6.4.6.1.

The NUMBER OF BYTES field specifies the number bytes to be read. A value of zero specifies that no bytes shall
be transferred in this segment. This shall not be considered an error.

The SOURCE BLOCK DEVICE LOGICAL BLOCK ADDRESS field specifies the starting address on the copy source
block device for this segment.

The DESTINATION BLOCK DEVICE LOGICAL BLOCK ADDRESS field specifies the starting logical block address on the
copy destination block device for this segment.

The SOURCE BLOCK DEVICE BYTE OFFSET field specifies the offset into the first copy source logical block at
which to begin reading bytes.

The DESTINATION BLOCK DEVICE BYTE OFFSET field specifies the offset into the first copy destination logical
block at which to begin writing data to the copy destination block device.

6.4.6.13 Write filemarks function

The segment descriptor format shown in table 162 requests the copy manager to write filemarks on the
destination tape device.

Table 162 — Write filemarks segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (10h)
1 Reserved
2 (MSB)
DESCRIPTOR LENGTH (0008h)
3 (LSB)
4 Reserved
5 Reserved
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 Reserved Obsolete W_IMMED

9 (MSB)
10 FILEMARK COUNT

11 (LSB)

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1, and shall be set as shown in table 162 for
the write filemarks segment descriptor.

332 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Descriptor type code 10h (i.e., filemarktape) requests the copy manager to write filemarks to the copy
destination tape device specified by the DESTINATION CSCD DESCRIPTOR ID field starting at the current position
of the copy destination tape device. If the PERIPHERAL DEVICE TYPE field in the CSCD descriptor specified by
the DESTINATION CSCD DESCRIPTOR ID field does not contain 01h, then the copy manager shall terminate the
copy operation (see 5.16.4.3) with CHECK CONDITION status, with the sense key set to COPY ABORTED,
and the additional sense code set to INVALID OPERATION FOR COPY SOURCE OR DESTINATION.

The DESCRIPTOR LENGTH field is described in 6.4.6.1, and shall be set as shown in table 162 for the write
filemarks segment descriptor.

The DESTINATION CSCD DESCRIPTOR ID field is described in 6.4.6.1.

If the write immediate (W_IMMED) bit in the segment descriptor is set to one, the copy manager shall send a
WRITE FILEMARKS command to the copy destination tape device with the IMMED bit set to one. If the
W _ IMMED bit is set to zero, the copy manager shall send a WRITE FILEMARKS command to the copy
destination tape device with the IMMED bit set to zero.

The FILEMARK COUNT field contents in the WRITE FILEMARKS command sent to the copy destination tape
device shall be set to the value in the FILEMARK COUNT field in the segment descriptor.

6.4.6.14 Space function

The segment descriptor format shown in table 163 requests the copy manager to send a SPACE command
(see SSC-4) to the destination tape device.

Table 163 — Space segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (11h)
1 Reserved
2 (MSB)
DESCRIPTOR LENGTH (0008h)
3 (LSB)
4 Reserved
5 Reserved
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 Reserved CODE

9 (MSB)
10 COUNT

11 (LSB)

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1, and shall be set as shown in table 163 for
the space segment descriptor.

Working Draft SCSI Primary Commands - 4 (SPC-4) 333

T10/BSR INCITS 513 Revision 37 17 May 2014

Descriptor type code 11h (i.e., spacetape) requests the copy manager to send a SPACE command to the
copy destination tape device specified by the DESTINATION CSCD DESCRIPTOR ID field. If the PERIPHERAL DEVICE
TYPE field in the CSCD descriptor specified by the DESTINATION CSCD DESCRIPTOR ID field does not contain 01h,
then the copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status,
with the sense key set to COPY ABORTED, and the additional sense code set to INVALID OPERATION FOR
COPY SOURCE OR DESTINATION.

The DESCRIPTOR LENGTH field is described in 6.4.6.1, and shall be set as shown in table 163 for the space
segment descriptor.

The DESTINATION CSCD DESCRIPTOR ID field is described in 6.4.6.1.

The CODE field and COUNT field contents in the SPACE command sent to the copy destination tape device
shall be set to the values in the CODE field and COUNT field in the segment descriptor. The PARAMETER LENGTH
field, if any, shall be set to zero (i.e., implicit mode) or 16 (i.e., explicit mode). All other fields in the SPACE
command sent to the copy destination tape device that affect the positioning of the tape shall be set to zero.

6.4.6.15 Locate function

The segment descriptor format shown in table 164 requests the copy manager to send a LOCATE command
(see SSC-4) to the destination tape device.

Table 164 — Locate segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (12h)
1 Reserved
2 (MSB)
DESCRIPTOR LENGTH (0008h)
3 (LSB)
4
Reserved
5
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 (MSB)
•• • LOGICAL OBJECT IDENTIFIER
11 (LSB)

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1, and shall be set as shown in table 164 for
the locate segment descriptor.

Descriptor type code 12h (i.e., locatetape) requests the copy manager to send a LOCATE command to the
copy destination tape device specified by the DESTINATION CSCD DESCRIPTOR ID field. If the PERIPHERAL DEVICE
TYPE field in the CSCD descriptor specified by the DESTINATION CSCD DESCRIPTOR ID field does not contain 01h,
then the copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status,
with the sense key set to COPY ABORTED, and the additional sense code set to INVALID OPERATION FOR
COPY SOURCE OR DESTINATION.

The DESCRIPTOR LENGTH field is described in 6.4.6.1, and shall be set as shown in table 164 for the locate
segment descriptor.

334 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The DESTINATION CSCD DESCRIPTOR ID field is described in 6.4.6.1.

The LOGICAL OBJECT IDENTIFIER field contents in the LOCATE command sent to the copy destination tape
device shall be set to the value in the LOGICAL OBJECT IDENTIFIER field in the segment descriptor. All other fields
in the LOCATE command sent to the copy destination tape device that affect the positioning of the tape shall
be set to zero.

NOTE 23 - The restrictions described in this subclause for the LOCATE command limit the function to locating
logical block identifiers in the current tape partition.

6.4.6.16 Tape device image copy function

The segment descriptor format shown in table 165 requests the copy manager to perform an image copy from
the copy source tape device to the copy destination tape device.

Table 165 — Tape device image copy segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (13h)
1 Reserved
2 (MSB)
DESCRIPTOR LENGTH (0008h)
3 (LSB)
4 (MSB)
SOURCE CSCD DESCRIPTOR ID
5 (LSB)
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 (MSB)
•• • COUNT
11 (LSB)

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1 and shall be set as shown in table 165 for
the tape device image copy segment descriptor.

Descriptor type code 13h (i.e., <i>tape<i>tape) requests the copy manager to create a compatible image of
the copy source specified by the SOURCE CSCD DESCRIPTOR ID field on the copy destination specified by the
DESTINATION CSCD DESCRIPTOR ID field beginning at the current positions of the copy source and the copy
destination. If the PERIPHERAL DEVICE TYPE field in the CSCD descriptor specified by the SOURCE CSCD
DESCRIPTOR ID field or the DESTINATION CSCD DESCRIPTOR ID field does not contain 01h, then the copy manager
shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the sense key set to
COPY ABORTED, and the additional sense code set to INVALID OPERATION FOR COPY SOURCE OR
DESTINATION.

The DESCRIPTOR LENGTH field is described in 6.4.6.1 and shall be set as shown in table 165 for descriptor type
code 13h (i.e., <i>tape<i>tape).

The SOURCE CSCD DESCRIPTOR ID field and DESTINATION CSCD DESCRIPTOR ID field are described in 6.4.6.1.

A COUNT field set to zero specifies that the tape image copy function shall not terminate due to any number of
consecutive filemarks. Other error or exception conditions (e.g., early-warning, end-of-partition on the copy

Working Draft SCSI Primary Commands - 4 (SPC-4) 335

T10/BSR INCITS 513 Revision 37 17 May 2014

destination) may cause the copy manager to terminate the copy operation (see 5.16.4.3) prior to completion.
If this occurs, the residue shall not be calculated and the INFORMATION field in the sense data shall be set to
zero.

A COUNT field not set to zero specifies that the tape image copy function shall be terminated if the specified
number of consecutive filemarks are copied.

The tape image copy operation terminates when:

a) the copy source encounters an end-of-partition as defined by the copy source;

b) the copy source encounters an end-of-data as defined by the copy source (i.e., BLANK CHECK
sense key); or
c) the copy manager has copied the number of consecutive filemarks specified in the COUNT field from
the copy source to the copy destination.

6.4.6.17 Register persistent reservation key function

The segment descriptor format shown in table 166 requests the copy manager to register an I_T nexus using
the reservation key (see 5.12.7) specified by the RESERVATION KEY field with the logical unit specified by the
DESTINATION CSCD DESCRIPTOR ID field.

Table 166 — Register persistent reservation key segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (14h)
1 Reserved
2 (MSB)
DESCRIPTOR LENGTH (0018h)
3 (LSB)
4 Reserved
5 Reserved
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 (MSB)
•• • RESERVATION KEY
15 (LSB)
16 (MSB)
•• • SERVICE ACTION RESERVATION KEY
23 (LSB)
24
•• • Reserved
27

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1, and shall be set as shown in table 166 for
the register persistent reservation key segment descriptor.

Descriptor type code 14h requests the copy manager to register an I_T nexus using the reservation key
specified by the RESERVATION KEY field with the logical unit specified by the DESTINATION CSCD DESCRIPTOR ID

336 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

field using a PERSISTENT RESERVE OUT command with a REGISTER service action (see 6.16.2).

The DESCRIPTOR LENGTH field is described in 6.4.6.1, and shall be set as shown in table 166 for the register
persistent reservation key segment descriptor.

The DESTINATION CSCD DESCRIPTOR ID field is described in 6.4.6.1.

The RESERVATION KEY field and SERVICE ACTION RESERVATION KEY field contents in the PERSISTENT
RESERVE OUT command sent to the copy destination shall be copied from the RESERVATION KEY field and
SERVICE ACTION RESERVATION KEY field in the segment descriptor.

The application client sending an EXTENDED COPY command that contains a register persistent reservation
key segment descriptor may be required to remove the reservation key held by the copy manager as
described in 5.12.11 prior to sending the EXTENDED COPY command.

6.4.6.18 Third party persistent reservations source I_T nexus function

The segment descriptor format shown in table 167 requests the copy manager to send a PERSISTENT
RESERVE OUT command with REGISTER AND MOVE service action (see 5.12.8) with the specified I_T
nexus after all other segment descriptors have been processed. If an error is detected any time after receiving
a third party persistent source reservation I_T nexus segment descriptor, then the PERSISTENT RESERVE
OUT command REGISTER AND MOVE service action shall be processed before the copy operation (see
5.16.4.3) originated by the EXTENDED COPY command is completed.

This segment descriptor should be placed at or near the beginning of the list of segment descriptors to assure
the copy manager processes the PERSISTENT RESERVE OUT command with REGISTER AND MOVE
service action in the event of an error that terminates the processing of segment descriptors. If an error is
detected in a segment descriptor and third party persistent reservations source I_T nexus segment descriptor
has not been processed, then the copy manager shall not send a PERSISTENT RESERVE OUT command
with REGISTER AND MOVE service action.

Placing more than one source third party persistent reservations source I_T nexus segment descriptor in the
list of descriptors is not an error. All source third party persistent reservations source I_T nexus segment

Working Draft SCSI Primary Commands - 4 (SPC-4) 337

T10/BSR INCITS 513 Revision 37 17 May 2014

descriptors known to the copy manager shall be processed after all other segment descriptors have been
processed.

Table 167 — Third party persistent reservations source I_T nexus segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (15h)
1 Reserved
2 (MSB)
DESCRIPTOR LENGTH (n-3)
3 (LSB)
4 Reserved
5 Reserved
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 (MSB)
•• • RESERVATION KEY
15 (LSB)
16 (MSB)
•• • SERVICE ACTION RESERVATION KEY
23 (LSB)
24 Reserved
25 Reserved UNREG APTPL

26 (MSB)
RELATIVE TARGET PORT IDENTIFIER
27 (LSB)
28 (MSB)
•• • TRANSPORTID LENGTH (n-31)
31 (LSB)
32
•• • TransportID
n

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1, and shall be set as shown in table 167 for
the third party persistent reservations source I_T nexus segment descriptor.

Descriptor type code 15h requests the copy manager to send PERSISTENT RESERVE OUT command with
REGISTER AND MOVE service action (see 6.16) to the target port specified by the DESTINATION CSCD
DESCRIPTOR ID field.

The DESCRIPTOR LENGTH field is described in 6.4.6.1. The value in the DESCRIPTOR LENGTH field shall be a
multiple of 4.

The DESTINATION CSCD DESCRIPTOR ID field is described in 6.4.6.1.

If the PERIPHERAL DEVICE TYPE field in the CSCD descriptor specified by the DESTINATION CSCD DESCRIPTOR ID
field does not contain 01h, then the copy manager shall terminate the copy operation (see 5.16.4.3) with

338 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

CHECK CONDITION status, with the sense key set to COPY ABORTED, and the additional sense code set to
INVALID OPERATION FOR COPY SOURCE OR DESTINATION.

Bytes eight to n of the third party persistent reservations source I_T nexus segment descriptor shall be sent as
the parameter list (see 6.16.4) for the PERSISTENT RESERVE OUT command with REGISTER AND MOVE
service action.

For a description of the RESERVATION KEY field, SERVICE ACTION RESERVATION KEY field, UNREG bit, APTPL bit,
RELATIVE TARGET PORT IDENTIFIER field, TRANSPORTID LENGTH field, and TransportID, see 6.16.4.

6.4.6.19 Block device image copy function

The segment descriptor format shown in table 168 requests the copy manager to perform an image copy from
the copy source block device to the copy destination block device.

Table 168 — Block device image copy segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (16h)
1 Reserved
2 (MSB)
DESCRIPTOR LENGTH (0018h)
3 (LSB)
4 (MSB)
SOURCE CSCD DESCRIPTOR ID
5 (LSB)
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 (MSB)
•• • STARTING SOURCE LOGICAL BLOCK ADDRESS
15 (LSB)
16 (MSB)
•• • STARTING DESTINATION LOGICAL BLOCK ADDRESS
23 (LSB)
24 (MSB)
•• • NUMBER OF LOGICAL BLOCKS
27 (LSB)

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1 and shall be set as shown in table 168 for
the block device image copy segment descriptor.

Descriptor type code 16h (i.e., <i>block<i>block) requests the copy manager to copy logical blocks from the
copy source block device specified by the SOURCE CSCD DESCRIPTOR ID field to the copy destination block
device specified by the DESTINATION CSCD DESCRIPTOR ID field while preserving the characteristics (e.g., logical
block length protection information) associated with each logical block.

Working Draft SCSI Primary Commands - 4 (SPC-4) 339

T10/BSR INCITS 513 Revision 37 17 May 2014

The copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with
the sense key set to COPY ABORTED, and the additional sense code set to INCORRECT COPY TARGET
DEVICE TYPE if:

a) the DISK BLOCK LENGTH field in the device type specific CSCD descriptor parameters (see 6.4.5.3) for
the copy source is not equal to DISK BLOCK LENGTH field in the device type specific CSCD descriptor
parameters for the copy destination; or
b) the protection information characteristics for the copy source are not the same as the protection
information characteristics for the copy destination.

While copying logical blocks from the copy source to the copy destination, the copy manager shall preserve
the protection information.

While copying logical blocks from the copy source to the copy destination, the copy manager should preserve
the logical block provisioning information, if any. If the copy manager detects differences between the logical
block provisioning characteristics for the copy source and the logical block provisioning characteristics for the
copy destination that prevent the preservation of logical block provisioning information (see SBC-3), then the
copy manager may terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the
sense key set to COPY ABORTED, and the additional sense code set to INCORRECT COPY TARGET
DEVICE TYPE.

The DESCRIPTOR LENGTH field is described in 6.4.6.1, and shall be set as shown in table 168 for descriptor type
code 16h (i.e., <i>block<i>block).

The SOURCE CSCD DESCRIPTOR ID field and DESTINATION CSCD DESCRIPTOR ID field are described in 6.4.6.1.

The STARTING SOURCE LOGICAL BLOCK ADDRESS field specifies the first logical block to read from the copy
source block device.

The STARTING DESTINATION LOGICAL BLOCK ADDRESS field specifies the first logical block to write on the copy
destination block device.

The NUMBER OF LOGICAL BLOCKS field specifies the number of logical blocks to copy. If the NUMBER OF LOGICAL
BLOCKS field is set to zero, the copy manager shall use FFFF FFFF FFFF FFFFh as the number of logical
blocks to copy.

The copy manager shall copy logical blocks from the copy source to the copy destination beginning at the
specified logical block addresses until:

a) the specified number of logical blocks are copied;

b) the maximum logical block address on the copy source is reached; or
c) the maximum logical block address on the copy destination is reached.

The <i>block<i>block copy function shall be considered a success regardless of which limit on the number
of logical blocks copied caused the function to end.

340 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4.6.20 Populate a ROD from one or more block ranges function

The segment descriptor format shown in table 169 requests the copy manager to add one or more ranges
from the copy source block device to the end of the ROD that is specified as the copy destination. The copy
manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the sense
key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST if:

a) the PERIPHERAL DEVICE TYPE field in the specified copy source CSCD descriptor is not set to 00h (i.e.,
block device);
b) the PERIPHERAL DEVICE TYPE field in the specified copy destination CSCD descriptor is not set to 00h
(i.e., block device);
c) the SOURCE CSCD DESCRIPTOR ID field is not set to FFFFh (i.e., the logical unit that contains the copy
manager);
d) the copy destination CSCD descriptor is not a ROD CSCD descriptor (see 6.4.5.9);
e) the ROD TYPE field in the copy destination CSCD descriptor is set to zero; or
f) the same LBA is specified in more than one range descriptor (see 5.16.6.3).

Table 169 — Populate a ROD from one or more block ranges segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (BEh)
1 Reserved
2 (MSB)
DESCRIPTOR LENGTH (n-3)
3 (LSB)
4 (MSB)
SOURCE CSCD DESCRIPTOR ID
5 (LSB)
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8
•• • Reserved
12
13 RANGE DESCRIPTOR TYPE

14 (MSB)
RANGE DESCRIPTORS LENGTH (n-15)
15 (LSB)
Range descriptors
16
•• • Range descriptor [first]

•
••

•• • Range descriptor [last]

n

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1 and shall be set as shown in table 169 for
the Populate a ROD from one or more block ranges segment descriptor.

Working Draft SCSI Primary Commands - 4 (SPC-4) 341

T10/BSR INCITS 513 Revision 37 17 May 2014

Descriptor type code BEh (i.e., RODblock ranges(n)) requests the copy manager to add the ranges
specified in the segment descriptor from the copy source specified by the SOURCE CSCD DESCRIPTOR ID field to
the end of the ROD specified by the DESTINATION CSCD DESCRIPTOR ID field.

The DESCRIPTOR LENGTH field is described in 6.4.6.1.

The SOURCE CSCD DESCRIPTOR ID field and DESTINATION CSCD DESCRIPTOR ID field are described in 6.4.6.1.

The RANGE DESCRIPTOR TYPE field specifies the format of all range descriptors.

Table 170 — RANGE DESCRIPTOR TYPE field

Code Description Reference

01h Four gibi-block range descriptor table 171
all others Reserved

The RANGE DESCRIPTORS LENGTH field specifies the number of bytes of range descriptors that follow.

If the RANGE DESCRIPTOR TYPE field is set to 01h, each range descriptor (see table 171) has the format
specified by the RANGE DESCRIPTOR TYPE field.

Table 171 — Populate a ROD four gibi-block range descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • LOGICAL BLOCK ADDRESS
7 (LSB)
8 (MSB)
•• • NUMBER OF LOGICAL BLOCKS
11 (LSB)
12
•• • Reserved
15

The LOGICAL BLOCK ADDRESS field specifies the first LBA from the copy source to be added to the copy
destination ROD.

The NUMBER OF LOGICAL BLOCKS field specifies the number of consecutive LBAs from the copy source to be
added to the copy destination ROD.

342 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.4.6.21 Populate a ROD from one block range function

The segment descriptor format shown in table 172 requests the copy manager to add one range from the
copy source block device to the end of the ROD that is specified as the copy destination. The copy manager
shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST if:

a) the PERIPHERAL DEVICE TYPE field in the specified copy source CSCD descriptor is not set to 00h (i.e.,
block device);
b) the PERIPHERAL DEVICE TYPE field in the specified copy destination CSCD descriptor is not set to 00h
(i.e., block device);
c) the SOURCE CSCD DESCRIPTOR ID field is not set to FFFFh (i.e., the logical unit that contains the copy
manager);
d) the copy destination CSCD descriptor is not a ROD CSCD descriptor (see 6.4.5.9); or
e) the ROD TYPE field in the copy destination CSCD descriptor is set to zero.

Table 172 — Populate a ROD from one block range segment descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (BFh)
1 Reserved
2 (MSB)
DESCRIPTOR LENGTH (0010h)
3 (LSB)
4 (MSB)
SOURCE CSCD DESCRIPTOR ID
5 (LSB)
6 (MSB)
DESTINATION CSCD DESCRIPTOR ID
7 (LSB)
8 (MSB)
•• • LOGICAL BLOCK ADDRESS
15 (LSB)
16 (MSB)
•• • NUMBER OF LOGICAL BLOCKS
19 (LSB)

The DESCRIPTOR TYPE CODE field is described in 6.4.4 and 6.4.6.1 and shall be set as shown in table 172 for
the Populate a ROD from one block range segment descriptor.

Descriptor type code BFh (i.e., RODblock range(1)) requests the copy manager to add the range specified
in the segment descriptor from the copy source specified by the SOURCE CSCD DESCRIPTOR ID field to the end
of the ROD specified by the DESTINATION CSCD DESCRIPTOR ID field.

The DESCRIPTOR LENGTH field is described in 6.4.6.1, and shall be set as shown in table 172 for descriptor type
code BEh (i.e., RODblock range(1)).

The SOURCE CSCD DESCRIPTOR ID field and DESTINATION CSCD DESCRIPTOR ID field are described in 6.4.6.1.

The LOGICAL BLOCK ADDRESS field specifies the first LBA from the copy source to be added to the copy
destination ROD.

Working Draft SCSI Primary Commands - 4 (SPC-4) 343

T10/BSR INCITS 513 Revision 37 17 May 2014

The NUMBER OF LOGICAL BLOCKS field specifies the number of consecutive LBAs from the copy source to be
added to the copy destination ROD.

6.5 EXTENDED COPY(LID1) command

The EXTENDED COPY(LID1) command (see table 173) is an SPC-3 compatible third-party copy command
(see 5.16.3) that requests the copy manager to copy data from one set of copy sources (e.g., a set of source
logical units) to a set of copy destinations (e.g., a set of destination logical units).

Table 173 — EXTENDED COPY(LID1) command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (83h)
1 Reserved SERVICE ACTION (00h)
2
•• • Reserved
9
10 (MSB)
•• • PARAMETER LIST LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 173 for the EXTENDED
COPY(LID1) command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 173 for the EXTENDED
COPY(LID1) command.

The PARAMETER LIST LENGTH field is defined in 6.4.1.

The CONTROL byte is defined in SAM-5.

344 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The format of the EXTENDED COPY(LID1) parameter list is shown in table 174.

Table 174 — EXTENDED COPY(LID1) parameter list

Bit
7 6 5 4 3 2 1 0
Byte
0 LIST IDENTIFIER

1 Reserved STR LIST ID USAGE PRIORITY

2 (MSB)
CSCD DESCRIPTOR LIST LENGTH (n-15)
3 (LSB)
4
•• • Reserved
7
8 (MSB)
SEGMENT DESCRIPTOR LIST LENGTH (m-n)
11 (LSB)
12 (MSB)
INLINE DATA LENGTH (k-m)
15 (LSB)
CSCD descriptor list
16
•• • CSCD descriptor (see 6.4.5) [ID 1]
47
••
•
n-31
•• • CSCD descriptor (see 6.4.5) [ID x]
n
Segment descriptor list
n+1
•• • Segment descriptor (see 6.4.6) [first]
n+1+l
••
•

•• • Segment descriptor (see 6.4.6) [last]

m
m+1
•• • Inline data
k

The LIST IDENTIFIER field is defined in 6.4.3.2.

The STR bit is defined in 6.4.3.1.

The LIST ID USAGE field is defined in 6.4.3.2.

The PRIORITY field is defined in 6.4.3.3.

Working Draft SCSI Primary Commands - 4 (SPC-4) 345

T10/BSR INCITS 513 Revision 37 17 May 2014

The CSCD DESCRIPTOR LIST LENGTH field is defined in 6.4.3.4.

The SEGMENT DESCRIPTOR LIST LENGTH field is defined in 6.4.3.5.

The INLINE DATA LENGTH field is defined in 6.4.3.6.

The CSCD descriptors are defined in 6.4.3.4 and 6.4.5.

The segment descriptors are defined in 6.4.3.5 and 6.4.6.

The inline data is defined in 6.4.3.6.

346 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.6 INQUIRY command

6.6.1 INQUIRY command introduction

The INQUIRY command (see table 175) requests the device server to return information regarding the logical
unit and SCSI target device.

Table 175 — INQUIRY command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (12h)
1 Reserved Obsolete EVPD

2 PAGE CODE

3 (MSB)
ALLOCATION LENGTH
4 (LSB)
5 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 175 for the INQUIRY
command.

An enable vital product data (EVPD) bit set to one specifies that the device server shall return the vital product
data specified by the PAGE CODE field (see 7.8). If the device server does not implement the requested vital
product data page, then the device server shall terminate the command with CHECK CONDITION status, with
the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

An EVPD bit set to zero specifies that the device server shall return the standard INQUIRY data (see 6.6.2). If
the PAGE CODE field is not set to zero and the EVPD bit is set to zero, then the device server shall terminate the
command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID FIELD IN CDB.

If the EVPD bit is set to one, the PAGE CODE field specifies which page of vital product data information the
device server shall return (see 7.8).

The ALLOCATION LENGTH field is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

In response to an INQUIRY command received by an incorrect logical unit, the SCSI target device shall return
the INQUIRY data with the peripheral qualifier set to the value defined in 6.6.2. The device server shall
terminate an INQUIRY command with CHECK CONDITION status only if the device server is unable to return
the requested INQUIRY data.

If an INQUIRY command is received from an initiator port for which the device server has a pending unit
attention condition (i.e., before the device server reports CHECK CONDITION status), then the device server
shall perform the INQUIRY command and shall not clear the unit attention condition (see SAM-5).

The device server should be able to process the INQUIRY command even when an error occurs that prohibits
normal command completion.

Working Draft SCSI Primary Commands - 4 (SPC-4) 347

T10/BSR INCITS 513 Revision 37 17 May 2014

INQUIRY data (i.e., standard INQUIRY data (see 6.6.2) and all VPD pages (see 7.8)) should be returned even
though the device server is not ready for other commands. Standard INQUIRY data, the Extended INQUIRY
Data VPD page (see 7.8.7), and the Device Identification VPD page (see 7.8.6) should be available without
incurring any media access delays. If reporting INQUIRY data requires a delay (e.g., the device server stores
some of the standard INQUIRY data or VPD data on the media), then the device server may return ASCII
spaces (20h) in ASCII fields and zeros in other fields until the data is available from the media.

INQUIRY data may change as the SCSI target device and its logical units perform their initialization sequence.

EXAMPLE – Logical units may provide a minimum command set from nonvolatile memory until they load the final firmware
from the media. After the firmware has been loaded, more options may be supported and therefore different INQUIRY data
may be returned.

If INQUIRY data changes for any reason, the device server shall establish a unit attention condition for the
initiator port associated with every I_T nexus (see SAM-5), with the additional sense code set to INQUIRY
DATA HAS CHANGED.

NOTE 24 - The INQUIRY command may be used by an application client after a hard reset or power on
condition to determine the device types for system configuration.

6.6.2 Standard INQUIRY data

The standard INQUIRY data (see table 176) shall contain at least 36 bytes.

Table 176 — Standard INQUIRY data format (part 1 of 2)

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 RMB LU_CONG Reserved

2 VERSION

3 Reserved Reserved NORMACA HISUP RESPONSE DATA FORMAT (2h)

4 ADDITIONAL LENGTH (n-4)
5 SCCS ACC TPGS 3PC Reserved PROTECT

6 Obsolete ENCSERV VS MULTIP Obsolete Reserved Reserved ADDR16 a

a a
7 Obsolete Reserved WBUS16 SYNC Obsolete Reserved CMDQUE VS
8 (MSB)
•• • T10 VENDOR IDENTIFICATION
15 (LSB)
16 (MSB)
•• • PRODUCT IDENTIFICATION
31 (LSB)
32 (MSB)
•• • PRODUCT REVISION LEVEL
35 (LSB)

348 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 176 — Standard INQUIRY data format (part 2 of 2)

Bit
7 6 5 4 3 2 1 0
Byte
36
•• • Vendor specific
55
a a a
56 Reserved CLOCKING QAS IUS

57 Reserved
58 (MSB)
VERSION DESCRIPTOR 1
59 (LSB)
••
•
72 (MSB)
VERSION DESCRIPTOR 8
73 (LSB)
74
•• • Reserved
95
Vendor specific parameters
96
•• • Vendor specific
n
a
The meanings of these fields are specific to SPI-5 (see 6.6.3). For SCSI transport protocols other than
the SCSI Parallel Interface, these fields are reserved.

The PERIPHERAL QUALIFIER field and PERIPHERAL DEVICE TYPE field identify the peripheral device connected to
the logical unit. If the SCSI target device is not capable of supporting a peripheral device connected to this
logical unit, the device server shall set these fields to 7Fh (i.e., PERIPHERAL QUALIFIER field set to 011b and
PERIPHERAL DEVICE TYPE field set to 1Fh).

Working Draft SCSI Primary Commands - 4 (SPC-4) 349

T10/BSR INCITS 513 Revision 37 17 May 2014

The PERIPHERAL QUALIFIER field is defined in table 177.

Table 177 — PERIPHERAL QUALIFIER field

Qualifier Description
000b A peripheral device having the indicated peripheral device type is connected to this
logical unit. If the device server is unable to determine whether or not a peripheral
device is connected, then the device server also shall use this peripheral qualifier. This
peripheral qualifier does not indicate that the peripheral device connected to the logi-
cal unit is ready for access.
001b A peripheral device having the indicated peripheral device type is not connected to this
logical unit. However, the device server is capable of supporting the indicated periph-
eral device type on this logical unit.
010b Reserved
011b The device server is not capable of supporting a peripheral device on this logical unit.
For this peripheral qualifier the peripheral device type shall be set to 1Fh. All other
peripheral device type values are reserved for this peripheral qualifier.
100b to 111b Vendor specific

The peripheral device type is defined in table 178.

Table 178 — Peripheral device type (part 1 of 2)

Code Reference a Description

00h SBC-3 Direct access block device (e.g., magnetic disk)
01h SSC-4 Sequential-access device (e.g., magnetic tape)
02h SSC Printer device
03h SPC-2 Processor device
04h SBC Write-once device (e.g., some optical disks)
05h MMC-6 CD/DVD device
06h Obsolete
07h SBC Optical memory device (e.g., some optical disks)
08h SMC-3 Media changer device (e.g., jukeboxes)
09h Obsolete
0Ah to 0Bh Obsolete
0Ch SCC-2 Storage array controller device (e.g., RAID)
0Dh SES-2 Enclosure services device
0Eh RBC Simplified direct-access device (e.g., magnetic disk)
0Fh OCRW Optical card reader/writer device
10h Reserved
11h OSD-2 Object-based Storage Device
12h ADC-3 Automation/Drive Interface
a
All standards are subject to revision, and parties to agreements based on this standard are
encouraged to investigate the possibility of applying the most recent editions of the listed
standards.
b
All well known logical units use the same peripheral device type code.

350 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 178 — Peripheral device type (part 2 of 2)

Code Reference a Description

13h clause 9 Security manager device
14h ZBC Host managed zoned block device
15h to 1Dh Reserved
1Eh clause 8 Well known logical unit b
1Fh Unknown or no device type
a All standards are subject to revision, and parties to agreements based on this standard are
encouraged to investigate the possibility of applying the most recent editions of the listed
standards.
b All well known logical units use the same peripheral device type code.

A removable medium (RMB) bit set to zero indicates that the medium is not removable. A RMB bit set to one
indicates that the medium is removable.

A logical unit conglomerate (LU_CONG) bit set to zero indicates that the logical unit is not part of a logical unit
conglomerate (see SAM-5). A LU_CONG bit set to one indicates that the logical unit is part of a logical unit
conglomerate.

The VERSION field indicates the implemented version of this standard and is defined in table 179.

Table 179 — VERSION field

Code Description
00h The device server does not claim conformance to any standard.
01h to 02h Obsolete
03h The device server complies to ANSI INCITS 301-1997 (a withdrawn standard).
04h The device server complies to ANSI INCITS 351-2001 (SPC-2).
05h The device server complies to ANSI INCITS 408-2005 (SPC-3).
06h The device server complies to this standard.
07h Reserved
08h to 0Ch Obsolete
0Dh to 3Fh Reserved
40h to 44h Obsolete
45h to 47h Reserved
48h to 4Ch Obsolete
4Dh to 7Fh Reserved
80h to 84h Obsolete
85h to 87h Reserved
88h to 8Ch Obsolete
8Dh to FFh Reserved

The Normal ACA Supported (NORMACA) bit set to one indicates that the device server supports a NACA bit set
to one in the CDB CONTROL byte and supports the ACA task attribute (see SAM-5). A NORMACA bit set to zero
indicates that the device server does not support a NACA bit set to one and does not support the ACA task
attribute.

Working Draft SCSI Primary Commands - 4 (SPC-4) 351

T10/BSR INCITS 513 Revision 37 17 May 2014

A historical support (HISUP) bit set to zero indicates the SCSI target device does not use the LUN structures
described in SAM-5. A H I S UP bit set to one indicates the SCSI target device uses the LUN structures
described in SAM-5.

The RESPONSE DATA FORMAT field (see table 180) indicates the format of the standard INQUIRY data and shall
be set as shown in table 176.

Table 180 — RESPONSE DATA FORMAT field

Code Description
00h to 01h Obsolete
02h The response data format complies to this standard.
all other values Reserved

The ADDITIONAL LENGTH field indicates the length in bytes of the remaining standard INQUIRY data. The
contents of the ADDITIONAL LENGTH field are not altered based on the allocation length (see 4.2.5.6).

An SCC Supported (SCCS) bit set to one indicates that the SCSI target device contains an embedded storage
array controller component that is addressable through this logical unit. See SCC-2 for details about storage
array controller devices. An SCCS bit set to zero indicates that no embedded storage array controller
component is addressable through this logical unit.

An Access Controls Coordinator (ACC) bit set to one indicates that the SCSI target device contains an access
controls coordinator that is addressable through this logical unit. An ACC bit set to zero indicates that no
access controls coordinator is addressable through this logical unit. If the SCSI target device contains an
access controls coordinator that is addressable through any logical unit other than the ACCESS CONTROLS
well known logical unit (see 8.3), then the ACC bit shall be set to one for LUN 0.

The contents of the target port group support (TPGS) field (see table 181) indicate the support for asymmetric
logical unit access (see 5.15).

Table 181 — TPGS field

Code Description
00b The logical unit does not support asymmetric logical unit access or supports a form of asymmet-
ric access that is vendor specific. Neither the REPORT TARGET GROUPS command nor the
SET TARGET PORT GROUPS command is supported.
01b The logical unit supports only implicit asymmetric logical unit access (see 5.15.2.8). The logical
unit is capable of changing target port asymmetric access states without a SET TARGET PORT
GROUPS command. The REPORT TARGET PORT GROUPS command is supported and the
SET TARGET PORT GROUPS command is not supported.
10b The logical unit supports only explicit asymmetric logical unit access (see 5.15.2.9). The logical
unit only changes target port asymmetric access states as requested with the SET TARGET
PORT GROUPS command. Both the REPORT TARGET PORT GROUPS command and the
SET TARGET PORT GROUPS command are supported.
11b The logical unit supports both explicit and implicit asymmetric logical unit access. Both the
REPORT TARGET PORT GROUPS command and the SET TARGET PORT GROUPS
commands are supported.

A third-party copy (3PC) bit set to one indicates that the logical unit supports third-party copy commands (see
5.16.3). A 3PC bit set to zero indicates that the logical unit does not support third-party copy commands.

352 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

A PROTECT bit set to zero indicates that the logical unit does not support protection information. A PROTECT bit
set to one indicates that the logical unit supports:

a) type 1 protection, type 2 protection, or type 3 protection (see SBC-3); or

b) logical block protection (see SSC-4).

More information about the type of protection the logical unit supports is available in the SPT field (see 7.8.7).

An Enclosure Services (ENCSERV) bit set to one indicates that the SCSI target device contains an embedded
enclosure services component that is addressable through this logical unit. See SES-3 for details about
enclosure services. An ENCSERV bit set to zero indicates that no embedded enclosure services component is
addressable through this logical unit.

A multiple SCSI port (MULTIP) bit set to one indicates that the logical unit is in a SCSI target device with
multiple SCSI target ports (see SAM-5). A MULTIP bit set to zero indicates that the logical unit is in a SCSI
target device with a single SCSI target port.

The CMDQUE bit shall be set to one indicating that the logical unit supports the command management model
defined in SAM-5.

The T10 VENDOR IDENTIFICATION field contains eight bytes of left-aligned ASCII data (see 4.3.1) identifying the
manufacturer of the logical unit. The T10 vendor identification shall be one assigned by INCITS. A list of
assigned T10 vendor identifications is in Annex G and on the T10 web site (http://www.t10.org).

NOTE 25 - The T10 web site (http://www.t10.org) provides a convenient means to request an identification
code.

The PRODUCT IDENTIFICATION field contains 16 bytes of left-aligned ASCII data (see 4.3.1) that identifies the
product and is defined by the manufacturer.

The PRODUCT REVISION LEVEL field contains four bytes of left-aligned ASCII data that identifies the product
revision and is defined by the manufacturer.

Working Draft SCSI Primary Commands - 4 (SPC-4) 353

T10/BSR INCITS 513 Revision 37 17 May 2014

The VERSION DESCRIPTOR fields provide for identifying up to eight standards to which the SCSI target device
and/or logical unit claim conformance. The value in each VERSION DESCRIPTOR field shall be selected from
table 182. All version descriptor values not listed in table 182 are reserved. Technical Committee T10 of
INCITS maintains an electronic copy of the information in table 182 on its world wide web site
(http://www.t10.org/). In the event that the T10 world wide web site is no longer active, the information may be
accessible on the INCITS world wide web site (http://www.incits.org), the ANSI world wide web site
(http://www.ansi.org), the IEC site (http://www.iec.ch/), the ISO site (http://www.iso.ch/), or the ISO/IEC JTC 1
web site (http://www.jtc1.org/). It is recommended that the first version descriptor be used for the SCSI archi-
tecture standard, followed by the physical transport standard if any, followed by the SCSI transport protocol
standard, followed by the appropriate SPC-x version, followed by the device type command set, followed by a
secondary command set if any.

Table 182 — Version descriptor values (part 1 of 12)

Version
Descriptor
Standard Value
ACS-2 (no version claimed) 1761h
ACS-2 ANSI INCITS 482-2013 1762h
ACS-3 (no version claimed) 1765h
ADC (no version claimed) 03C0h
ADC ANSI INCITS 403-2005 03D7h
ADC T10/1558-D revision 7 03D6h
ADC T10/1558-D revision 6 03D5h
ADC-2 (no version claimed) 04A0h
ADC-2 ANSI INCITS 441-2008 04ACh
ADC-2 T10/1741-D revision 7 04A7h
ADC-2 T10/1741-D revision 8 04AAh
ADC-3 (no version claimed) 0500h
ADC-3 ANSI INCITS 497-2012 050Ah
ADC-3 T10/1895-D revision 04 0502h
ADC-3 T10/1895-D revision 05 0504h
ADC-3 T10/1895-D revision 05a 0506h
ADP (no version claimed) 09C0h
ADT (no version claimed) 09E0h
ADT ANSI INCITS 406-2005 09FDh
ADT T10/1557-D revision 14 09FAh
ADT T10/1557-D revision 11 09F9h
ADT-2 (no version claimed) 0A20h
ADT-2 ANSI INCITS 472-2011 0A2Bh
ADT-2 T10/1742-D revision 06 0A22h
ADT-2 T10/1742-D revision 08 0A27h
ADT-2 T10/1742-D revision 09 0A28h
ATA/ATAPI-6 (no version claimed) 15E0h
ATA/ATAPI-6 ANSI INCITS 361-2002 15FDh
A numeric ordered listing of the version descriptor value assignments is provided in F.9.

354 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 182 — Version descriptor values (part 2 of 12)

Version
Descriptor
Standard Value
ATA/ATAPI-7 (no version claimed) 1600h
ATA/ATAPI-7 ISO/IEC 24739 161Eh
ATA/ATAPI-7 ANSI INCITS 397-2005 161Ch
ATA/ATAPI-7 T13/1532-D revision 3 1602h
ATA/ATAPI-8 ATA8-AAM (no version claimed) 1620h
ATA/ATAPI-8 ATA8-AAM ANSI INCITS 451-2008 1628h
ATA/ATAPI-8 ATA8-APT Parallel Transport (no version claimed) 1621h
ATA/ATAPI-8 ATA8-AST Serial Transport (no version claimed) 1622h
ATA/ATAPI-8 ATA8-ACS ATA/ATAPI Command Set (no version claimed) 1623h
ATA/ATAPI-8 ATA8-ACS ANSI INCITS 452-2009 w/ Amendment 1 162Ah
BCC (no version claimed) 0380h
EPI (no version claimed) 0B20h
EPI ANSI INCITS TR-23 1999 0B3Ch
EPI T10/1134 revision 16 0B3Bh
Fast-20 (no version claimed) 0AC0h
Fast-20 ANSI INCITS 277-1996 0ADCh
Fast-20 T10/1071 revision 06 0ADBh
FC 10GFC (no version claimed) 0EA0h
FC 10GFC ISO/IEC 14165-116 0EA3h
FC 10GFC ANSI INCITS 364-2003 0EA2h
FC 10GFC ISO/IEC 14165-116 with AM1 0EA5h
FC 10GFC ANSI INCITS 364-2003 with AM1 ANSI INCITS 364/AM1-2007 0EA6h
FC-AL (no version claimed) 0D40h
FC-AL ANSI INCITS 272-1996 0D5Ch
FC-AL-2 (no version claimed) 0D60h
FC-AL-2 ISO/IEC 14165-122 with AM1 & AM2 0D65h
FC-AL-2 ANSI INCITS 332-1999 with AM1-2003 & AM2-2006 0D63h
FC-AL-2 ANSI INCITS 332-1999 with Amnd 2 AM2-2006 0D64h
FC-AL-2 ANSI INCITS 332-1999 with Amnd 1 AM1-2003 0D7Dh
FC-AL-2 ANSI INCITS 332-1999 0D7Ch
FC-AL-2 T11/1133-D revision 7.0 0D61h
FC-DA (no version claimed) 12E0h
FC-DA ISO/IEC 14165-341 12E9h
FC-DA ANSI INCITS TR-36 2004 12E8h
FC-DA T11/1513-DT revision 3.1 12E2h
FC-DA-2 (no version claimed) 12C0h
FC-DA-2 INCITS TR-49 2012 12C9h
FC-DA-2 T11/1870DT revision 1.04 12C3h
A numeric ordered listing of the version descriptor value assignments is provided in F.9.

Working Draft SCSI Primary Commands - 4 (SPC-4) 355

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 182 — Version descriptor values (part 3 of 12)

Version
Descriptor
Standard Value
FC-DA-2 T11/1870DT revision 1.06 12C5h
FC-FLA (no version claimed) 1320h
FC-FLA ANSI INCITS TR-20 1998 133Ch
FC-FLA T11/1235 revision 7 133Bh
FC-FS (no version claimed) 0DA0h
FC-FS ISO/IEC 14165-251 0DBDh
FC-FS ANSI INCITS 373-2003 0DBCh
FC-FS T11/1331-D revision 1.2 0DB7h
FC-FS T11/1331-D revision 1.7 0DB8h
FC-FS-2 (no version claimed) 0E00h
FC-FS-2 ANSI INCITS 242-2007 with AM1 ANSI INCITS 242/AM1-2007 0E03h
FC-FS-2 ANSI INCITS 242-2007 0E02h
FC-FS-3 (no version claimed) 0EE0h
FC-FS-3 ANSI INCITS 470-2011 0EEBh
FC-FS-3 T11/1861-D revision 0.9 0EE2h
FC-FS-3 T11/1861-D revision 1.0 0EE7h
FC-FS-3 T11/1861-D revision 1.10 0EE9h
FC-FS-4 (no version claimed) 0F60h
FC-LS (no version claimed) 0E20h
FC-LS ANSI INCITS 433-2007 0E29h
FC-LS T11/1620-D revision 1.62 0E21h
FC-LS-2 (no version claimed) 0F00h
FC-LS-2 ANSI INCITS 477-2011 0F07h
FC-LS-2 T11/2103-D revision 2.11 0F03h
FC-LS-2 T11/2103-D revision 2.21 0F05h
FC-LS-3 (no version claimed) 0F80h
FCP (no version claimed) 08C0h
FCP ANSI INCITS 269-1996 08DCh
FCP T10/0993-D revision 12 08DBh
FC-PH (no version claimed) 0D20h
FC-PH ANSI INCITS 230-1994 0D3Bh
FC-PH ANSI INCITS 230-1994 with Amnd 1 ANSI INCITS 230/AM1-1996 0D3Ch
FC-PH-3 (no version claimed) 0D80h
FC-PH-3 ANSI INCITS 303-1998 0D9Ch
FC-PI (no version claimed) 0DC0h
FC-PI ANSI INCITS 352-2002 0DDCh
FC-PI-2 (no version claimed) 0DE0h
FC-PI-2 ANSI INCITS 404-2006 0DE4h
A numeric ordered listing of the version descriptor value assignments is provided in F.9.

356 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 182 — Version descriptor values (part 4 of 12)

Version
Descriptor
Standard Value
FC-PI-2 T11/1506-D revision 5.0 0DE2h
FC-PI-3 (no version claimed) 0E60h
FC-PI-3 ANSI INCITS 460-2011 0E6Eh
FC-PI-3 T11/1625-D revision 2.0 0E62h
FC-PI-3 T11/1625-D revision 2.1 0E68h
FC-PI-3 T11/1625-D revision 4.0 0E6Ah
FC-PI-4 (no version claimed) 0E80h
FC-PI-4 ANSI INCITS 450-2009 0E88h
FC-PI-4 T11/1647-D revision 8.0 0E82h
FC-PI-5 (no version claimed) 0F20h
FC-PI-5 ANSI INCITS 479-2011 0F2Eh
FC-PI-5 T11/2118-D revision 2.00 0F27h
FC-PI-5 T11/2118-D revision 3.00 0F28h
FC-PI-5 T11/2118-D revision 6.00 0F2Ah
FC-PI-5 T11/2118-D revision 6.10 0F2Bh
FC-PI-6 (no version claimed) 0F40h
FC-PLDA (no version claimed) 1340h
FC-PLDA ANSI INCITS TR-19 1998 135Ch
FC-PLDA T11/1162 revision 2.1 135Bh
FCP-2 (no version claimed) 0900h
FCP-2 ANSI INCITS 350-2003 0917h
FCP-2 T10/1144-D revision 8 0918h
FCP-2 T10/1144-D revision 4 0901h
FCP-2 T10/1144-D revision 7 0915h
FCP-2 T10/1144-D revision 7a 0916h
FCP-3 (no version claimed) 0A00h
FCP-3 ISO/IEC 14776-223 0A1Ch
FCP-3 ANSI INCITS 416-2006 0A11h
FCP-3 T10/1560-D revision 4 0A0Fh
FCP-3 T10/1560-D revision 3f 0A07h
FCP-4 (no version claimed) 0A40h
FCP-4 ANSI INCITS 481-2012 0A46h
FCP-4 T10/1828-D revision 01 0A42h
FCP-4 T10/1828-D revision 02 0A44h
FCP-4 T10/1828-D revision 02b 0A45h
FC-SCM (no version claimed) 12A0h
FC-SCM INCITS TR-47 2012 12AAh
FC-SCM T11/1824DT revision 1.0 12A3h
A numeric ordered listing of the version descriptor value assignments is provided in F.9.

Working Draft SCSI Primary Commands - 4 (SPC-4) 357

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 182 — Version descriptor values (part 5 of 12)

Version
Descriptor
Standard Value
FC-SCM T11/1824DT revision 1.1 12A5h
FC-SCM T11/1824DT revision 1.4 12A7h
FC-SP (no version claimed) 0E40h
FC-SP ANSI INCITS 426-2007 0E45h
FC-SP T11/1570-D revision 1.6 0E42h
FC-SP-2 (no version claimed) 0EC0h
FC-Tape (no version claimed) 1300h
FC-Tape ANSI INCITS TR-24 1999 131Ch
FC-Tape T11/1315 revision 1.17 131Bh
FC-Tape T11/1315 revision 1.16 1301h
IEEE 1394 (no version claimed) 14A0h
ANSI IEEE 1394-1995 14BDh
IEEE 1394a (no version claimed) 14C0h
IEEE 1394b (no version claimed) 14E0h
IEEE 1667 (no version claimed) FFC0h
IEEE 1667-2006 FFC1h
IEEE 1667-2009 FFC2h
iSCSI (no version claimed) 0960h
iSCSI (versions as described via RFC 7144) 0961h to
097Fh
MMC (no version claimed) 0140h
MMC ANSI INCITS 304-1997 015Ch
MMC T10/1048-D revision 10a 015Bh
MMC-2 (no version claimed) 0240h
MMC-2 ANSI INCITS 333-2000 025Ch
MMC-2 T10/1228-D revision 11a 025Bh
MMC-2 T10/1228-D revision 11 0255h
MMC-3 (no version claimed) 02A0h
MMC-3 ANSI INCITS 360-2002 02B8h
MMC-3 T10/1363-D revision 10g 02B6h
MMC-3 T10/1363-D revision 9 02B5h
MMC-4 (no version claimed) 03A0h
MMC-4 ANSI INCITS 401-2005 03BFh
MMC-4 T10/1545-D revision 3 03BDh
MMC-4 T10/1545-D revision 3d 03BEh
MMC-4 T10/1545-D revision 5 03B0h
MMC-4 T10/1545-D revision 5a 03B1h
MMC-5 (no version claimed) 0420h
A numeric ordered listing of the version descriptor value assignments is provided in F.9.

358 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 182 — Version descriptor values (part 6 of 12)

Version
Descriptor
Standard Value
MMC-5 T10/1675-D revision 04 0432h
MMC-5 ANSI INCITS 430-2007 0434h
MMC-5 T10/1675-D revision 03 042Fh
MMC-5 T10/1675-D revision 03b 0431h
MMC-6 (no version claimed) 04E0h
MMC-6 ANSI INCITS 468-2010 + MMC-6/AM1 ANSI INCITS 468-2010/AM 1 04E7h
MMC-6 ANSI INCITS 468-2010 04E6h
MMC-6 T10/1836-D revision 02b 04E3h
MMC-6 T10/1836-D revision 02g 04E5h
OCRW (no version claimed) 0280h
OCRW ISO/IEC 14776-381 029Eh
OSD (no version claimed) 0340h
OSD ANSI INCITS 400-2004 0356h
OSD T10/1355-D revision 10 0355h
OSD T10/1355-D revision 0 0341h
OSD T10/1355-D revision 7a 0342h
OSD T10/1355-D revision 8 0343h
OSD T10/1355-D revision 9 0344h
OSD-2 (no version claimed) 0440h
OSD-2 ANSI INCITS 458-2011 0448h
OSD-2 T10/1729-D revision 4 0444h
OSD-2 T10/1729-D revision 5 0446h
OSD-3 (no version claimed) 0560h
PQI (no version claimed) 2200h
PQI T10/BSR INCITS 490 revision 6 2204h
PQI T10/BSR INCITS 490 revision 7 2206h
PQI-2 (no version claimed) 2240h
RBC (no version claimed) 0220h
RBC ANSI INCITS 330-2000 023Ch
RBC T10/1240-D revision 10a 0238h
SAM (no version claimed) 0020h
SAM ANSI INCITS 270-1996 003Ch
SAM T10/0994-D revision 18 003Bh
SAM-2 (no version claimed) 0040h
SAM-2 ISO/IEC 14776-412 005Eh
SAM-2 ANSI INCITS 366-2003 005Ch
SAM-2 T10/1157-D revision 24 0055h
SAM-2 T10/1157-D revision 23 0054h
A numeric ordered listing of the version descriptor value assignments is provided in F.9.

Working Draft SCSI Primary Commands - 4 (SPC-4) 359

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 182 — Version descriptor values (part 7 of 12)

Version
Descriptor
Standard Value
SAM-3 (no version claimed) 0060h
SAM-3 ANSI INCITS 402-2005 0077h
SAM-3 T10/1561-D revision 14 0076h
SAM-3 T10/1561-D revision 7 0062h
SAM-3 T10/1561-D revision 13 0075h
SAM-4 (no version claimed) 0080h
SAM-4 ISO/IEC 14776-414 0092h
SAM-4 ANSI INCITS 447-2008 0090h
SAM-4 T10/1683-D revision 13 0087h
SAM-4 T10/1683-D revision 14 008Bh
SAM-5 (no version claimed) 00A0h
SAM-5 T10/2104-D revision 4 00A2h
SAS (no version claimed) 0BE0h
SAS ANSI INCITS 376-2003 0BFDh
SAS T10/1562-D revision 05 0BFCh
SAS T10/1562-D revision 01 0BE1h
SAS T10/1562-D revision 03 0BF5h
SAS T10/1562-D revision 04 0BFAh
SAS T10/1562-D revision 04 0BFBh
SAS-1.1 (no version claimed) 0C00h
SAS-1.1 ISO/IEC 14776-151 0C12h
SAS-1.1 ANSI INCITS 417-2006 0C11h
SAS-1.1 T10/1601-D revision 9 0C07h
SAS-1.1 T10/1601-D revision 10 0C0Fh
SAS-2 (no version claimed) 0C20h
SAS-2 ANSI INCITS 457-2010 0C2Ah
SAS-2 T10/1760-D revision 14 0C23h
SAS-2 T10/1760-D revision 15 0C27h
SAS-2 T10/1760-D revision 16 0C28h
SAS-2.1 (no version claimed) 0C40h
SAS-2.1 ANSI INCITS 478-2011 0C4Eh
SAS-2.1 ANSI INCITS 478-2011 w/ Amnd 1 ANSI INCITS 478/AM1-2014 0C4Fh
SAS-2.1 T10/2125-D revision 04 0C48h
SAS-2.1 T10/2125-D revision 06 0C4Ah
SAS-2.1 T10/2125-D revision 07 0C4Bh
SAS-3 (no version claimed) 0C60h
SAS-3 T10/BSR INCITS 519 revision 05a 0C63h
SAS-3 T10/BSR INCITS 519 revision 06 0C65h
A numeric ordered listing of the version descriptor value assignments is provided in F.9.

360 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 182 — Version descriptor values (part 8 of 12)

Version
Descriptor
Standard Value
SAS-4 (no version claimed) 0C80h
SAT (no version claimed) 1EA0h
SAT ANSI INCITS 431-2007 1EADh
SAT T10/1711-D revision 9 1EABh
SAT T10/1711-D revision 8 1EA7h
SAT-2 (no version claimed) 1EC0h
SAT-2 ANSI INCITS 465-2010 1ECAh
SAT-2 T10/1826-D revision 06 1EC4h
SAT-2 T10/1826-D revision 09 1EC8h
SAT-3 (no version claimed) 1EE0h
SAT-3 T10/BSR INCITS 517 revision 4 1EE2h
SAT-4 (no version claimed) 1F00h
SBC (no version claimed) 0180h
SBC ANSI INCITS 306-1998 019Ch
SBC T10/0996-D revision 08c 019Bh
SBC-2 (no version claimed) 0320h
SBC-2 ISO/IEC 14776-322 033Eh
SBC-2 ANSI INCITS 405-2005 033Dh
SBC-2 T10/1417-D revision 16 033Bh
SBC-2 T10/1417-D revision 5a 0322h
SBC-2 T10/1417-D revision 15 0324h
SBC-3 (no version claimed) 04C0h
SBC-3 T10/BSR INCITS 514 revision 35 04C3h
SBC-3 T10/BSR INCITS 514 revision 36 04C5h
SBC-4 (no version claimed) 0600h
SBP-2 (no version claimed) 08E0h
SBP-2 ANSI INCITS 325-1998 08FCh
SBP-2 T10/1155-D revision 04 08FBh
SBP-3 (no version claimed) 0980h
SBP-3 ANSI INCITS 375-2004 099Ch
SBP-3 T10/1467-D revision 5 099Bh
SBP-3 T10/1467-D revision 1f 0982h
SBP-3 T10/1467-D revision 3 0994h
SBP-3 T10/1467-D revision 4 099Ah
SCC (no version claimed) 0160h
SCC ANSI INCITS 276-1997 017Ch
SCC T10/1047-D revision 06c 017Bh
SCC-2 (no version claimed) 01E0h
A numeric ordered listing of the version descriptor value assignments is provided in F.9.

Working Draft SCSI Primary Commands - 4 (SPC-4) 361

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 182 — Version descriptor values (part 9 of 12)

Version
Descriptor
Standard Value
SCC-2 ANSI INCITS 318-1998 01FCh
SCC-2 T10/1125-D revision 04 01FBh
SES (no version claimed) 01C0h
SES ANSI INCITS 305-1998 01DCh
SES T10/1212-D revision 08b 01DBh
SES ANSI INCITS 305-1998 w/ Amendment ANSI INCITS.305/AM1-2000 01DEh
SES T10/1212 revision 08b w/ Amendment ANSI INCITS.305/AM1-2000 01DDh
SES-2 (no version claimed) 03E0h
SES-2 ISO/IEC 14776-372 03F2h
SES-2 ANSI INCITS 448-2008 03F0h
SES-2 T10/1559-D revision 16 03E1h
SES-2 T10/1559-D revision 19 03E7h
SES-2 T10/1559-D revision 20 03EBh
SES-3 (no version claimed) 0580h
SFSC (no version claimed) 05E0h
SIP (no version claimed) 08A0h
SIP ANSI INCITS 292-1997 08BCh
SIP T10/0856-D revision 10 08BBh
SMC (no version claimed) 01A0h
SMC ISO/IEC 14776-351 01BEh
SMC ANSI INCITS 314-1998 01BCh
SMC T10/0999-D revision 10a 01BBh
SMC-2 (no version claimed) 02E0h
SMC-2 ANSI INCITS 382-2004 02FEh
SMC-2 T10/1383-D revision 7 02FDh
SMC-2 T10/1383-D revision 5 02F5h
SMC-2 T10/1383-D revision 6 02FCh
SMC-3 (no version claimed) 0480h
SMC-3 ANSI INCITS 484-2012 0486h
SMC-3 T10/1730-D revision 15 0482h
SMC-3 T10/1730-D revision 16 0484h
SOP (no version claimed) 21E0h
SOP T10/BSR INCITS 489 revision 4 21E4h
SOP T10/BSR INCITS 489 revision 5 21E6h
SOP-2 (no version claimed) 2220h
SPC (no version claimed) 0120h
SPC ANSI INCITS 301-1997 013Ch
SPC T10/0995-D revision 11a 013Bh
A numeric ordered listing of the version descriptor value assignments is provided in F.9.

362 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 182 — Version descriptor values (part 10 of 12)

Version
Descriptor
Standard Value
SPC-2 (no version claimed) 0260h
SPC-2 ISO/IEC 14776-452 0278h
SPC-2 ANSI INCITS 351-2001 0277h
SPC-2 T10/1236-D revision 20 0276h
SPC-2 T10/1236-D revision 12 0267h
SPC-2 T10/1236-D revision 18 0269h
SPC-2 T10/1236-D revision 19 0275h
SPC-3 (no version claimed) 0300h
SPC-3 ISO/IEC 14776-453 0316h
SPC-3 ANSI INCITS 408-2005 0314h
SPC-3 T10/1416-D revision 7 0301h
SPC-3 T10/1416-D revision 21 0307h
SPC-3 T10/1416-D revision 22 030Fh
SPC-3 T10/1416-D revision 23 0312h
SPC-4 (no version claimed) 0460h
SPC-4 T10/BSR INCITS 513 revision 16 0461h
SPC-4 T10/BSR INCITS 513 revision 18 0462h
SPC-4 T10/BSR INCITS 513 revision 23 0463h
SPC-4 T10/BSR INCITS 513 revision 36 0466h
SPC-4 T10/BSR INCITS 513 revision 37 0468h
SPC-5 (no version claimed) 05C0h
SPI (no version claimed) 0AA0h
SPI ANSI INCITS 253-1995 0ABAh
SPI T10/0855-D revision 15a 0AB9h
SPI ANSI INCITS 253-1995 with SPI Amnd ANSI INCITS 253/AM1-1998 0ABCh
SPI T10/0855-D revision 15a with SPI Amnd revision 3a 0ABBh
SPI-2 (no version claimed) 0AE0h
SPI-2 ANSI INCITS 302-1999 0AFCh
SPI-2 T10/1142-D revision 20b 0AFBh
SPI-3 (no version claimed) 0B00h
SPI-3 ANSI INCITS 336-2000 0B1Ch
SPI-3 T10/1302-D revision 14 0B1Ah
SPI-3 T10/1302-D revision 10 0B18h
SPI-3 T10/1302-D revision 13a 0B19h
SPI-4 (no version claimed) 0B40h
SPI-4 ANSI INCITS 362-2002 0B56h
SPI-4 T10/1365-D revision 7 0B54h
SPI-4 T10/1365-D revision 9 0B55h
A numeric ordered listing of the version descriptor value assignments is provided in F.9.

Working Draft SCSI Primary Commands - 4 (SPC-4) 363

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 182 — Version descriptor values (part 11 of 12)

Version
Descriptor
Standard Value
SPI-4 T10/1365-D revision 10 0B59h
SPI-5 (no version claimed) 0B60h
SPI-5 ANSI INCITS 367-2003 0B7Ch
SPI-5 T10/1525-D revision 6 0B7Bh
SPI-5 T10/1525-D revision 3 0B79h
SPI-5 T10/1525-D revision 5 0B7Ah
SPL (no version claimed) 20A0h
SPL ISO/IEC 14776-261:2012 20AAh
SPL ANSI INCITS 476-2011 20A7h
SPL ANSI INCITS 476-2011 + SPL AM1 INCITS 476/AM1 2012 20A8h
SPL T10/2124-D revision 6a 20A3h
SPL T10/2124-D revision 7 20A5h
SPL-2 (no version claimed) 20C0h
SPL-2 ANSI INCITS 505-2013 20C8h
SPL-2 T10/BSR INCITS 505 revision 4 20C2h
SPL-2 T10/BSR INCITS 505 revision 5 20C4h
SPL-3 (no version claimed) 20E0h
SPL-3 T10/BSR INCITS 492 revision 6 20E4h
SPL-3 T10/BSR INCITS 492 revision 7 20E6h
SPL-4 (no version claimed) 2100h
SRP (no version claimed) 0940h
SRP ANSI INCITS 365-2002 095Ch
SRP T10/1415-D revision 16a 0955h
SRP T10/1415-D revision 10 0954h
SSA-PH2 (no version claimed) 1360h
SSA-PH2 ANSI INCITS 293-1996 137Ch
SSA-PH2 T10.1/1145-D revision 09c 137Bh
SSA-PH3 (no version claimed) 1380h
SSA-PH3 ANSI INCITS 307-1998 139Ch
SSA-PH3 T10.1/1146-D revision 05b 139Bh
SSA-S2P (no version claimed) 0880h
SSA-S2P ANSI INCITS 294-1996 089Ch
SSA-S2P T10.1/1121-D revision 07b 089Bh
SSA-S3P (no version claimed) 0860h
SSA-S3P ANSI INCITS 309-1998 087Ch
SSA-S3P T10.1/1051-D revision 05b 087Bh
SSA-TL1 (no version claimed) 0840h
SSA-TL1 ANSI INCITS 295-1996 085Ch
A numeric ordered listing of the version descriptor value assignments is provided in F.9.

364 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 182 — Version descriptor values (part 12 of 12)

Version
Descriptor
Standard Value
SSA-TL1 T10.1/0989-D revision 10b 085Bh
SSA-TL2 (no version claimed) 0820h
SSA-TL2 ANSI INCITS 308-1998 083Ch
SSA-TL2 T10.1/1147-D revision 05b 083Bh
SSC (no version claimed) 0200h
SSC ANSI INCITS 335-2000 021Ch
SSC T10/0997-D revision 22 0207h
SSC T10/0997-D revision 17 0201h
SSC-2 (no version claimed) 0360h
SSC-2 ANSI INCITS 380-2003 037Dh
SSC-2 T10/1434-D revision 9 0375h
SSC-2 T10/1434-D revision 7 0374h
SSC-3 (no version claimed) 0400h
SSC-3 ANSI INCITS 467-2011 0409h
SSC-3 T10/1611-D revision 04a 0403h
SSC-3 T10/1611-D revision 05 0407h
SSC-4 (no version claimed) 0520h
SSC-4 ANSI INCITS 516-2013 0527h
SSC-4 T10/BSR INCITS 516 revision 2 0523h
SSC-4 T10/BSR INCITS 516 revision 3 0525h
SSC-5 (no version claimed) 05A0h
SST (no version claimed) 0920h
SST T10/1380-D revision 8b 0935h
UAS (no version claimed) 1740h
UAS T10/2095-D revision 02 1743h
UAS T10/2095-D revision 04 1747h
UAS ANSI INCITS 471-2010 1748h
UAS-2 (no version claimed) 1780h
Universal Serial Bus Specification, Revision 1.1 1728h
Universal Serial Bus Specification, Revision 2.0 1729h
USB Mass Storage Class Bulk-Only Transport, Revision 1.0 1730h
ZBC (no version claimed) 0620h
Version Descriptor Not Supported or No Standard Identified 0000h
Reserved All others
A numeric ordered listing of the version descriptor value assignments is provided in F.9.

Working Draft SCSI Primary Commands - 4 (SPC-4) 365

T10/BSR INCITS 513 Revision 37 17 May 2014

6.6.3 SCSI Parallel Interface specific INQUIRY data

As shown in table 176, portions of bytes 6 and 7 and all of byte 56 of the standard INQUIRY data shall be
used only by SCSI target devices that implement the SCSI Parallel Interface. For details on how the
SPI-specific fields relate to the SCSI Parallel Interface see SPI-n (where n is 2 or greater). Table 183 shows
the SPI-specific standard INQUIRY fields.

Table 183 — SPI-specific standard INQUIRY bits

Bit
7 6 5 4 3 2 1 0
Byte
6 n/a a ADDR16

7 n/a a WBUS16 SYNC n/a a Obsolete n/a a

•
••

56 Reserved CLOCKING QAS IUS

a
The meanings of these bits and fields are not specific to SPI-5. See table 176 for their definitions.

A wide SCSI address 16 (ADDR16) bit set to one indicates that the SCSI target device supports 16-bit wide
SCSI addresses. An ADDR16 bit set to zero indicates that the SCSI target device does not support 16-bit wide
SCSI addresses.

A wide bus 16 ( WBUS16 ) bit set to one indicates that the SCSI target device supports 16-bit wide data
transfers. A WBUS16 bit set to zero indicates that the SCSI target device does not support 16-bit wide data
transfers.

A synchronous transfer (SYNC) bit set to one indicates that the SCSI target device supports synchronous data
transfer. A SYNC bit set to zero indicates the SCSI target device does not support synchronous data transfer.

Table 184 defines the relationships between the ADDR16 bit and the WBUS16 bit.

Table 184 — Maximum logical device configuration table

ADDR16 WBUS16 Description

0 0 8-bit wide data path on a single cable with
8 SCSI IDs supported
0 1 16-bit wide data path on a single cable
with 8 SCSI IDs supported
1 1 16-bit wide data path on a single cable
with 16 SCSI IDs supported

366 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The CLOCKING field shall not apply to asynchronous transfers and is defined in table 185.

Table 185 — CLOCKING field

Code Description
00b Indicates the target port supports only ST (see SPI-5)
01b Indicates the target port supports only DT (see SPI-5)
10b Reserved
11b Indicates the target port supports ST and DT

A quick arbitration and selection supported (QAS) bit set to one indicates that the target port supports quick
arbitration and selection (see SPI-5). A QAS bit set to zero indicates that the target port does not support quick
arbitration and selection.

An information units supported (IUS) bit set to one indicates that the SCSI target device supports information
unit transfers (see SPI-5). A IUS bit set to zero indicates that the SCSI target device does not support
information unit transfers.

Working Draft SCSI Primary Commands - 4 (SPC-4) 367

T10/BSR INCITS 513 Revision 37 17 May 2014

6.7 LOG SELECT command

6.7.1 Introduction

The LOG SELECT command (see table 186) requests the device server to manage the specified statistical
information maintained by the SCSI target device about the SCSI target device or its logical units. Device
servers that implement the LOG SELECT command shall also implement the LOG SENSE command.
Structures in the form of log parameters within log pages (see 7.3) are defined to manage the log data. The
LOG SELECT command provides a method for sending zero or more log pages in the command's parameter
list.

Table 186 — LOG SELECT command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (4Ch)
1 Reserved PCR SP

2 PC PAGE CODE

3 SUBPAGE CODE

4
•• • Reserved
6
7 (MSB)
PARAMETER LIST LENGTH
8 (LSB)
9 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 186 for the LOG SELECT
command.

The parameter code reset (PCR) bit specifies whether the device server shall set parameters to their vendor
specific default values (e.g., zero) as described in table 189.

The save parameters (SP ) bit specifies whether the device server shall save parameters to non-volatile
memory as described in table 189.

368 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The page control (PC) field specifies which values the device server shall process for bounded data counter
log parameters (see 7.3.2.2.2.2) and unbounded data counter log parameters (see 7.3.2.2.2.3) in response to
a LOG SELECT command as described in table 187. The PC field shall be ignored for ASCII format list log
parameters (see 7.3.2.2.2.4) and binary format list log parameters (see 7.3.2.2.2.5).

Table 187 — Page control (PC) field

Value Description
00b Threshold values a
01b Cumulative values a
10b Default threshold values
11b Default cumulative values
a
In order of preference, the threshold values and cumulative values for data counter parameters are:
1) the current values if there has been an update to a cumulative parameter value (e.g., by a LOG
SELECT command or by a device specific event) in the specified page or pages since the last
logical unit reset occurred;
2) the saved values, if saved parameters are implemented, current values have been saved, and
an update has not occurred since the last logical unit reset; and
3) the vendor specific default values, if saved values are not available or not implemented.

When evaluated together, the combination of the values in the PCR bit, the SP bit, and the PC field specify the
actions that a SCSI target device performs while processing a LOG SELECT command.

If the PARAMETER LIST LENGTH field is set to zero, the PAGE CODE field and SUBPAGE CODE field specify the log
page or log pages to which the other CDB fields apply (see 6.7.2).

The device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB, if:

a) the PARAMETER LIST LENGTH field is set to a value other than zero, and:
A) the PAGE CODE field is set to a value other than zero; or
B) the SUBPAGE CODE field is set to a value other than zero.

The PARAMETER LIST LENGTH field specifies the length in bytes of the parameter list that shall be located in the
Data-Out Buffer.

If the PARAMETER LIST LENGTH field is set to a value other than zero, the actions that a SCSI target device
performs after receiving a LOG SELECT command are determined by the values in the PCR bit, the SP bit, and
the PC field as described in table 351 (see 7.3.2.1).

If the PARAMETER LIST LENGTH field is set to zero, no log pages shall be transferred. This condition shall not be
considered an error. The LOG SELECT command shall be processed as described in 6.7.2.

The CONTROL byte is defined in SAM-5.

Working Draft SCSI Primary Commands - 4 (SPC-4) 369

T10/BSR INCITS 513 Revision 37 17 May 2014

6.7.2 Processing LOG SELECT when the parameter list length is zero

If the PARAMETER LIST LENGTH field is set to zero (i.e., when there is no parameter data being sent with a LOG
SELECT command), then the SCSI target device responds by processing the log parameter values as
described in this subclause.

The PAGE CODE field and SUBPAGE CODE field (see table 188) specify the log page or log pages to which the
other CDB fields apply (see table 189).

Table 188 — PAGE CODE field and SUBPAGE CODE field

PAGE CODE SUBPAGE CODE

field field Description
00h 00h All log parameters in all log pages a
00h to 3Fh 01h to FEh All log parameters in the log page specified by the page code and
subpage code
00h to 3Fh FFh All log parameters in the log pages specified by page code and all
subpage codes
01h to 3Fh 00h All log parameters in the log page specified by the page code
a This is equivalent to the LOG SELECT command operation specified by SPC-3.

Table 189 defines the meaning of the combinations of values for the PCR bit, the SP bit, and the PC field.

Table 189 — PCR bit, SP bit, and PC field meanings when parameter list length is zero (part 1 of 3)

PC SP PC
R bit fiel
bit d Description
0b 0b 0xb This is not an error. The device server shall make no changes to any log parameter
values and shall not save any values to non-volatile media.
0b 1b 00b The device server shall make no changes to any log parameter values and shall
process the saving of current parameter values as follows:
a) if the values are current threshold data counter parameters, then:
A) if the device server implements saving of the current threshold values, then
the device server shall save all current threshold values to non-volatile
media; or
B) if the device server does not implement saving of the current threshold
values, then the device server shall terminate the command a.
or
b) if the values are current list parameters, then:
A) if the device server implements saving of the current list parameters, then
the device server shall save all current list parameters to non-volatile
media; or
B) if the device server does not implement saving of the current list
parameters, then the device server shall terminate the command a.
a
The device server shall terminate the command with CHECK CONDITION status, with the sense key
set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.
b Vendor specific default threshold values and vendor specific default cumulative values may be zero.

370 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 189 — PCR bit, SP bit, and PC field meanings when parameter list length is zero (part 2 of 3)

PC SP PC
R bit fiel
bit d Description
0b 1b 01b The device server shall make no change to any log parameter values and shall
process the saving of current parameter values as follows:
a) if the values are current cumulative data counter parameters, then:
A) if the device server implements saving of the current cumulative values,
then the device server shall save all current cumulative values to
non-volatile media; or
B) if the device server does not implement saving of the current cumulative
values, then the device server shall terminate the command a.
or
b) if the values are current list parameters, then:
A) if the device server implements saving of the current list parameters, then
the device server shall save all current list parameters to non-volatile
media; or
B) if the device server does not implement saving of the current list
parameters, then the device server shall terminate the command a.
0b xb 10b The device server shall set all current threshold values to the vendor specific default
threshold values b and shall not save any values to non-volatile media.
0b xb 11b The device server shall set all current cumulative values to the vendor specific default
cumulative values b and shall not save any values to non-volatile media.
1b 0b xxb The device server shall:
1) set all current threshold values to the vendor specific default threshold
values b;
2) set all current cumulative values to the vendor specific default cumulative
values b;
3) set all list parameters to their vendor specific default values; and
4) not save any values to non-volatile media.
1b 1b 00b The device server shall process the saving of current threshold values as follows:
a) if the device server implements saving of the current threshold values, then the
device server shall:
1) save all current threshold values to non-volatile media;
Note: Device servers compliant with SPC-3 may save the log parameter values to
non-volatile media after setting the log parameter values instead of before setting
the log parameter values.
2) set all current threshold values to the vendor specific default threshold
values b;
3) set all current cumulative values to the vendor specific default cumulative
values b, and
4) set all list parameters to their vendor specific default values.
or
b) if the device server does not implement saving of the current threshold values,
then the device server shall terminate the command a.
a
The device server shall terminate the command with CHECK CONDITION status, with the sense key
set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.
b
Vendor specific default threshold values and vendor specific default cumulative values may be zero.

Working Draft SCSI Primary Commands - 4 (SPC-4) 371

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 189 — PCR bit, SP bit, and PC field meanings when parameter list length is zero (part 3 of 3)

PC SP PC
R bit fiel
bit d Description
1b 1b 01b The device server shall process the saving of current cumulative values as follows:
a) if the device server implements saving of the current cumulative values, then
the device server shall:
1) save all current cumulative values to non-volatile media;
Note: Device servers compliant with SPC-3 may save the log parameter values to
non-volatile media after setting the log parameter values instead of before setting
the log parameter values.
2) set all current threshold values to the vendor specific default threshold
values b;
3) set all current cumulative values to the vendor specific default cumulative
values b, and
4) set all list parameters to their vendor specific default values.
or
b) if the device server does not implement saving of the current cumulative
values, then the device server shall terminate the command a.
1b 1b 1xb The device server shall:
1) set all current threshold values to the vendor specific default threshold
values b;
2) set all current cumulative values to the vendor specific default cumulative
values b;
3) set all list parameters to their vendor specific default values; and
4) not save any values to non-volatile media.
a The device server shall terminate the command with CHECK CONDITION status, with the sense key
set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.
b
Vendor specific default threshold values and vendor specific default cumulative values may be zero.

The current cumulative values may be updated by the device server as defined for the specific log page or by
the application client using the LOG SELECT command. The current threshold values may only be modified
by the application client via the LOG SELECT command.

NOTE 26 - Log pages or log parameters that are not available may become available at some later time (e.g.,
after the logical unit has become ready).

372 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.8 LOG SENSE command

The LOG SENSE command (see table 190) requests the device server to return statistical or other operational
information maintained by the SCSI target device about the SCSI target device or its logical units. It is a
complementary command to the LOG SELECT command.

Table 190 — LOG SENSE command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (4Dh)
1 Reserved Obsolete SP

2 PC PAGE CODE

3 SUBPAGE CODE

4 Reserved
5 (MSB)
PARAMETER POINTER
6 (LSB)
7 (MSB)
ALLOCATION LENGTH
8 (LSB)
9 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 190 for the LOG SENSE
command.

An save parameters (SP) bit set to zero specifies the device server shall perform the specified LOG SENSE
command and shall not save any log parameters.

An SP bit set to one specifies that the device server shall perform the specified LOG SENSE command and
shall save all log parameters identified as saveable by the DS bit (see 7.3) to a nonvolatile, vendor specific
location. If the SP bit is set to one and the logical unit does not implement saving log parameters, the device
server shall terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

The PC field shall be ignored for ASCII format list log parameters (see 7.3.2.2.2.4) and binary format list log
parameters (see 7.3.2.2.2.5).

For bounded data counter log parameters (see 7.3.2.2.2.2) and unbounded data counter log parameters (see
7.3.2.2.2.3), the page control (PC) field (see table 187 in 6.7.1) specifies which log parameter values are to be
returned by a device server in response to a LOG SENSE command.

For ASCII format list log parameters (see 7.3.2.2.2.4) and binary format list log parameters (see 7.3.2.2.2.5),
the PC field shall be ignored. If the parameters specified by the PAGE CODE field and SUBPAGE CODE field in the
CDB are list parameters, then the parameter values returned by a device server in response to a LOG SENSE
command are determined as follows in order of preference:

1) the current list log parameter values, if there has been an update to a list log parameter value (e.g., by
a LOG SELECT command or by a device specific event) in the specified page or pages since the last
logical unit reset occurred;

Working Draft SCSI Primary Commands - 4 (SPC-4) 373

T10/BSR INCITS 513 Revision 37 17 May 2014

2) the saved list log parameter values, if saved log parameters are implemented and an update has not
occurred since the last logical unit reset; and
3) the vendor specific default list log parameter values, if saved values are not available or not
implemented and an update has not occurred since the last logical unit reset.

The PAGE CODE field and SUBPAGE CODE field specify which log page of data is being requested (see 7.3). If the
log page specified by the page code and subpage code combination is reserved or not implemented, then the
device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

The PARAMETER POINTER field allows the application client to request parameter data beginning from a specific
parameter code to the maximum allocation length or the maximum parameter code supported by the logical
unit, whichever is less. If the PARAMETER POINTER field is set to:

a) 0000h, then the device server shall begin the transfer of the parameter data with the log parameter
having the lowest parameter code that is implemented by the device server for the specified log page;
b) a value specifying the parameter code of a log parameter implemented by the device server for the
specified log page, then the device server shall begin the transfer of the parameter data with the log
parameter having the specified code;
c) a value that does not specify a parameter code implemented by the device server for the specified log
page but is less than the largest parameter code implemented by the device server, then the device
server shall begin the transfer of the parameter data with the log parameter implemented by the
device server that has the next largest parameter code after the specified value; or
d) a value greater than the largest parameter code implemented by the device server for the specified
log page, then the device server shall terminate the command with CHECK CONDITION status, with
the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN
CDB.

Log parameters within the specified log page shall be transferred in ascending order according to parameter
code.

The ALLOCATION LENGTH field is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

374 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.9 MANAGEMENT PROTOCOL IN command

6.9.1 MANAGEMENT PROTOCOL IN command description

The MANAGEMENT PROTOCOL IN command (see table 191) requests the device server to return
management protocol information (see 6.9.2) or the results of one or more MANAGEMENT PROTOCOL OUT
commands (see 6.10).

Table 191 — MANAGEMENT PROTOCOL IN command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A3h)
1 Reserved SERVICE ACTION (10h)
2 MANAGEMENT PROTOCOL

3
•• • MANAGEMENT PROTOCOL SPECIFIC1
5
6 (MSB)
•• • ALLOCATION LENGTH
9 (LSB)
10 MANAGEMENT PROTOCOL SPECIFIC2

11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 191 for the MANAGEMENT
PROTOCOL IN command.

The MANAGEMENT PROTOCOL field (see table 192) specifies which management protocol is being used.

Table 192 — MANAGEMENT PROTOCOL field in MANAGEMENT PROTOCOL IN command

Code Description Reference

00h Management protocol information 6.9.2
01h to 2Fh Reserved
30h to 35h Defined by the SNIA 3.1.168
36h to EFh Reserved
F0h to FFh Vendor Specific

The contents of the MANAGEMENT PROTOCOL SPECIFIC1 field and MANAGEMENT PROTOCOL SPECIFIC2 field depend
on the protocol specified by the MANAGEMENT PROTOCOL field (see table 192).

The ALLOCATION LENGTH field is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

Indications of data overrun or underrun and the mechanism, if any, for processing retries depend on the
protocol specified by the MANAGEMENT PROTOCOL field (see table 192).

Working Draft SCSI Primary Commands - 4 (SPC-4) 375

T10/BSR INCITS 513 Revision 37 17 May 2014

Any association between a previous MANAGEMENT PROTOCOL OUT command and the data transferred by
a MANAGEMENT PROTOCOL IN command depends on the protocol specified by the MANAGEMENT
PROTOCOL field (see table 192). If the device server has no data to transfer (e.g., the results for any previous
MANAGEMENT PROTOCOL OUT commands are not yet available), then the device server may transfer data
indicating it has no other data to transfer.

The format of the data transferred depends on the protocol specified by the MANAGEMENT PROTOCOL field (see
table 192).

The device server shall retain data resulting from a MANAGEMENT PROTOCOL OUT command, if any, until
one of the following events is processed:

a) transfer of the data via a MANAGEMENT PROTOCOL IN command from the same I_T_L nexus as
defined by the protocol specified by the MANAGEMENT PROTOCOL field (see table 192);
b) logical unit reset (see SAM-5); or
c) I_T nexus loss (see SAM-5) associated with the I_T nexus that sent the MANAGEMENT PROTOCOL
OUT command.

6.9.2 Management protocol information description

6.9.2.1 Overview

The management protocol information management protocol (i.e., the MANAGEMENT PROTOCOL field set to 00h
in a MANAGEMENT PROTOCOL IN command) returns management protocol related information from the
logical unit. A MANAGEMENT PROTOCOL IN command in which the MANAGEMENT PROTOCOL field is set to
00h is not associated with any previous MANAGEMENT PROTOCOL OUT command and shall be processed
without regard for whether a MANAGEMENT PROTOCOL OUT command has been processed.

If the MANAGEMENT PROTOCOL IN command is supported, the MANAGEMENT PROTOCOL value of 00h shall
be supported as defined in this standard.

6.9.2.2 CDB description

If the MANAGEMENT PROTOCOL field is set to 00h in a MANAGEMENT PROTOCOL IN command, the
MANAGEMENT PROTOCOL SPECIFIC1 field is reserved and the MANAGEMENT PROTOCOL SPECIFIC2 field (see table
193) contains a single numeric value as defined in 3.6.

Table 193 — MANAGEMENT PROTOCOL SPECIFIC2 field for MANAGEMENT PROTOCOL IN protocol 00h

Code Description Support Reference

00h Supported management protocol list Mandatory 6.9.2.3
01h to FFh Reserved

All other CDB fields for MANAGEMENT PROTOCOL IN command shall meet the requirements stated in
6.9.1.

Each time a MANAGEMENT PROTOCOL IN command with the MANAGEMENT PROTOCOL field set to 00h is
received, the device server shall transfer the data defined 6.9.2.3 starting with byte 0.

376 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.9.2.3 Supported management protocols list description

If the MANAGEMENT PROTOCOL field is set to 00h and the MANAGEMENT PROTOCOL SPECIFIC2 field is set to 00h in
a MANAGEMENT PROTOCOL IN command, then the parameter data shall have the format shown in table
194.

Table 194 — Supported management protocols MANAGEMENT PROTOCOL IN parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • Reserved
5
6 (MSB) SUPPORTED MANAGEMENT PROTOCOL LIST LENGTH
7 (n-7) (LSB)
Supported management protocol list
8 SUPPORTED MANAGEMENT PROTOCOL (00h) [first]
•
••

n SUPPORTED MANAGEMENT PROTOCOL [last]

The SUPPORTED MANAGEMENT PROTOCOL LIST LENGTH field indicates the total length, in bytes, of the supported
management protocol list that follows.

Each SUPPORTED MANAGEMENT PROTOCOL field in the supported management protocols list shall contain one
of the management protocol values supported by the logical unit. The values shall be listed in ascending order
starting with 00h.

Working Draft SCSI Primary Commands - 4 (SPC-4) 377

T10/BSR INCITS 513 Revision 37 17 May 2014

6.10 MANAGEMENT PROTOCOL OUT command

The MANAGEMENT PROTOCOL OUT command (see table 195) is used to send data to the logical unit. The
data sent specifies one or more operations to be performed by the logical unit. The format and function of the
operations depends on the contents of the MANAGEMENT PROTOCOL field (see table 195). Depending on the
protocol specified by the MANAGEMENT PROTOCOL field, the application client may use the MANAGEMENT
PROTOCOL IN command (see 6.9) to retrieve data derived from these operations.

Table 195 — MANAGEMENT PROTOCOL OUT command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A4h)
1 Reserved SERVICE ACTION (10h)
2 MANAGEMENT PROTOCOL

3
•• • MANAGEMENT PROTOCOL SPECIFIC1
5
6 (MSB)
•• • PARAMETER LIST LENGTH
9 (LSB)
10 MANAGEMENT PROTOCOL SPECIFIC2

11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 195 for the MANAGEMENT
PROTOCOL OUT command.

The MANAGEMENT PROTOCOL field (see table 196) specifies which management protocol is being used.

Table 196 — MANAGEMENT PROTOCOL field in MANAGEMENT PROTOCOL OUT command

Code Description Reference

00h to 2Fh Reserved
30h to 35h Defined by the SNIA 3.1.168
36h to EFh Reserved
F0h to FFh Vendor Specific

The contents of the MANAGEMENT PROTOCOL SPECIFIC1 field and MANAGEMENT PROTOCOL SPECIFIC2 field depend
on the protocol specified by the MANAGEMENT PROTOCOL field (see table 196).

The PARAMETER LIST LENGTH field is defined in 4.2.5.5.

The CONTROL byte is defined in SAM-5.

378 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Any association between a MANAGEMENT PROTOCOL OUT command and a subsequent MANAGEMENT
PROTOCOL IN command depends on the protocol specified by the MANAGEMENT PROTOCOL field (see table
196). Each management protocol shall define whether:

a) the device server shall complete the command with GOOD status as soon as it determines the data
has been correctly received. An indication that the data has been processed is obtained by sending a
MANAGEMENT PROTOCOL IN command and processing the parameter data that is returned; or
b) the device server shall complete the command with GOOD status only after the data has been
successfully processed and an associated MANAGEMENT PROTOCOL IN command is not required.

The format of the data transferred depends on the protocol specified by the MANAGEMENT PROTOCOL field (see
table 196).

6.11 MODE SELECT(6) command

The MODE SELECT(6) command (see table 197) requests the device server to set the specified medium,
logical unit, or peripheral device parameters. Device servers that implement the MODE SELECT(6) command
shall also implement the MODE SENSE(6) command. Application clients should issue MODE SENSE(6) prior
to each MODE SELECT(6) to determine supported mode pages, page lengths, and other parameters.

NOTE 27 - Implementations should migrate from the MODE SELECT(6) command to the MODE
SELECT(10) command.

Table 197 — MODE SELECT(6) command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (15h)
1 Reserved PF Reserved SP

2
Reserved
3
4 PARAMETER LIST LENGTH

5 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 197 for the MODE
SELECT(6) command.

If an application client sends a MODE SELECT command that changes any parameters applying to other I_T
nexuses, then the device server shall establish a unit attention condition (see SAM-5) for the initiator port
associated with every I_T nexus except the I_T nexus on which the MODE SELECT command was received,
with the additional sense code set to MODE PARAMETERS CHANGED.

A page format (PF) bit set to zero specifies that all parameters after the block descriptors are vendor specific.
A PF bit set to one specifies that the MODE SELECT parameters following the header and block descriptor(s)
are structured as pages of related parameters (see 7.5).

A save pages (SP) bit set to zero specifies that the device server shall perform the specified MODE SELECT
operation and shall not save any mode pages. If the device server supports only saved mode pages (i.e., the
device server does not support a distinction between current mode pages and saved mode pages) and the SP
bit is set to zero, then the device server shall terminate the command with CHECK CONDITION status, with

Working Draft SCSI Primary Commands - 4 (SPC-4) 379

T10/BSR INCITS 513 Revision 37 17 May 2014

the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB. An SP
bit set to one specifies that the device server shall perform the specified MODE SELECT operation and shall
save to a nonvolatile vendor specific location all the saveable mode pages including any sent in the parameter
list. Mode pages that are saved are specified by the parameter saveable (PS) bit in each mode page (see 7.5).
If the PS bit is set to one in the MODE SENSE data, then the mode page shall be saveable by issuing a MODE
SELECT command with the SP bit set to one. If the logical unit does not implement saved mode pages and the
SP bit is set to one, then the device server shall terminate the command with CHECK CONDITION status, with
the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

The PARAMETER LIST LENGTH field specifies the length in bytes of the mode parameter list that shall be
contained in the Data-Out Buffer. A parameter list length of zero specifies that the Data-Out Buffer shall be
empty. This condition shall not be considered an error.

If the parameter list length results in the truncation of any mode parameter header, mode parameter block
descriptor(s), or mode page, then the device server shall terminate the command with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to PARAMETER
LIST LENGTH ERROR.

The CONTROL byte is defined in SAM-5.

The mode parameter list for the MODE SELECT command and MODE SENSE command is defined in 7.5.
Parts of each mode parameter list are defined in a device-type dependent manner. Definitions for the parts of
each mode parameter list that are unique for each device-type may be found in the applicable command
standards.

The device server shall terminate the MODE SELECT command with CHECK CONDITION status, set the
sense key to ILLEGAL REQUEST, set the additional sense code to INVALID FIELD IN PARAMETER LIST,
and shall not change any mode parameters in response to any of the following conditions:

a) if the application client sets any field that is reported as not changeable by the device server to a value
other than the current value of the mode parameter;
b) if the application client sets any field in the mode parameter header or block descriptor(s) to an
unsupported value;
c) if an application client sends a mode page with a page length not equal to the page length returned by
the MODE SENSE command for that mode page;
d) if the application client sends an unsupported value for a mode parameter and rounding is not
implemented for that mode parameter; or
e) if the application client sets any reserved field in the mode parameter list to a non-zero value and the
device server checks reserved fields.

If the application client sends a value for a mode parameter that is outside the range supported by the device
server and rounding is implemented for that mode parameter, then the device server handles the condition by
either:

a) rounding the parameter to an acceptable value and terminating the command as described in 5.8; or
b) terminating the command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

A device server may alter any mode parameter in any mode page, even those reported as non-changeable,
as a result of changes to other mode parameters.

380 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The device server validates the non-changeable mode parameters against the current values that existed for
those mode parameters prior to the MODE SELECT command.

NOTE 28 - The current values calculated by the device server may affect the application client's operation.
The application client may issue a MODE SENSE command after each MODE SELECT command, to
determine the current values.

6.12 MODE SELECT(10) command

The MODE SELECT(10) command (see table 198) requests the device server to set the specified medium,
logical unit, or peripheral device parameters. See the MODE SELECT(6) command (6.11) for a description of
the fields and operation of this command. Application clients should issue MODE SENSE(10) prior to each
MODE SELECT(10) to determine supported mode pages, page lengths, and other parameters. Device
servers that implement the MODE SELECT(10) command shall also implement the MODE SENSE(10)
command.

Table 198 — MODE SELECT(10) command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (55h)
1 Reserved PF Reserved SP

2
•• • Reserved
6
7 (MSB)
PARAMETER LIST LENGTH
8 (LSB)
9 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 198 for the MODE
SELECT(10) command.

The CONTROL byte is defined in SAM-5.

See the MODE SELECT(6) command (6.11) for a description of the other fields and operation of this
command.

Working Draft SCSI Primary Commands - 4 (SPC-4) 381

T10/BSR INCITS 513 Revision 37 17 May 2014

6.13 MODE SENSE(6) command

6.13.1 MODE SENSE(6) command introduction

The MODE SENSE(6) command (see table 199) requests the device server to return the specified medium,
logical unit, or peripheral device parameters. It is a complementary command to the MODE SELECT(6)
command. Device servers that implement the MODE SENSE(6) command shall also implement the MODE
SELECT(6) command.

NOTE 29 - Implementations should migrate from the MODE SENSE(6) command to the MODE SENSE(10)
command.

Table 199 — MODE SENSE(6) command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (1Ah)
1 Reserved DBD Reserved
2 PC PAGE CODE

3 SUBPAGE CODE

4 ALLOCATION LENGTH

5 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 199 for the MODE
SENSE(6) command.

A disable block descriptors (DBD) bit set to zero specifies that the device server may return zero or more block
descriptors in the MODE SENSE parameter data (see 7.5). A DBD bit set to one specifies that the device
server shall not return any block descriptors in the MODE SENSE parameter data.

The page control (PC) field specifies the type of mode parameter values to be returned in the mode pages.
The PC field is defined in table 200.

Table 200 — Page control (PC) field

Code Type of parameter Reference

00b Current values 6.13.2
01b Changeable values 6.13.3
10b Default values 6.13.4
11b Saved values 6.13.5

The PC field only affects the mode parameters within the mode pages. The PS bit, SPF bit, PAGE CODE field,
SUBPAGE CODE field, and PAGE LENGTH field should return current values (i.e., as if PC is set to 00b). The mode
parameter header and mode parameter block descriptor should return current values.

Some SCSI target devices may not distinguish between current mode parameters and saved mode
parameters and report identical values in response to a PC field of either 00b or 11b. See also the description
of the SP bit in the MODE SELECT command (see 6.11).

382 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The PAGE CODE field and SUBPAGE CODE field (see table 201) specify which mode pages and subpages to
return.

Table 201 — Mode page code usage in MODE SENSE commands for all devices

Page Code Subpage Code Description

00h vendor specific Vendor specific
01h to 3Eh 00h See specific device types (i.e., page_0 mode page format
(see 7.5.7))
01h to DFh See specific device types (i.e., sub_page mode page format
(see 7.5.7))
E0h to FEh Vendor specific (i.e., sub_page mode page format (see 7.5.7))
FFh Return all supported subpages for the specified device specific
mode page in the page_0 mode page format for subpage 00h and
in the sub_page mode page format for subpages 01h to FEh
3Fh 00h Return all subpage 00h mode pages in page_0 mode page format
01h to FEh Reserved
FFh Return all subpages for all mode pages in the page_0 mode page
format for subpage 00h and in the sub_page mode page format for
subpages 01h to FEh

The ALLOCATION LENGTH field is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

An application client may request any one or all of the supported mode pages from the device server. If the
device server receives a MODE SENSE command with a page code value or subpage code value that is not
implemented by the logical unit, then the device server shall terminate the command with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
INVALID FIELD IN CDB.

If an application client requests all supported mode pages, the device server shall return the supported pages
in ascending page code order beginning with mode page 01h. If mode page 00h is implemented, the device
server shall return mode page 00h after all other mode pages have been returned.

If the PC field and the PAGE CODE field are both set to zero, the device server should return a mode parameter
header and block descriptor, if applicable.

The mode parameter list for all device types for MODE SELECT commands and MODE SENSE commands is
defined in 7.5. Parts of the mode parameter list are specifically defined for each device type. Definitions for the
parts of each mode parameter list that are unique for each device-type may be found in the applicable
command standards.

Working Draft SCSI Primary Commands - 4 (SPC-4) 383

T10/BSR INCITS 513 Revision 37 17 May 2014

6.13.2 Current values

A PC field value of 00b requests that the device server return the current values of the mode parameters. The
current values returned are:

a) the current values of the mode parameters established by the last successful MODE SELECT
command;
b) the saved values of the mode parameters if a MODE SELECT command has not successfully
completed since the mode parameters were restored to their saved values (see 6.11); or
c) the default values of the mode parameters if a MODE SELECT command has not successfully
completed since the mode parameters were restored to their default values (see 6.11).

6.13.3 Changeable values

A PC field value of 01b requests that the device server return a mask denoting those mode parameters that
are changeable. In the mask, the bits in the fields of the mode parameters that are changeable all shall be set
to one and the bits in the fields of the mode parameters that are non-changeable (i.e., defined by the logical
unit) all shall be set to zero.

If the logical unit does not implement changeable parameters mode pages and the device server receives a
MODE SENSE command with 01b in the PC field, then the device server shall terminate the command with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set
to INVALID FIELD IN CDB.

An attempt to change a non-changeable mode parameter using the MODE SELECT command results in an
error condition (see 6.11).

The application client should issue a MODE SENSE command with the PC field set to 01b and the PAGE CODE
field set to 3Fh to determine which mode pages are supported, which mode parameters within the mode
pages are changeable, and the supported length of each mode page prior to issuing any MODE SELECT
commands.

6.13.4 Default values

A PC field value of 10b requests that the device server return the default values of the mode parameters.
Unsupported parameters shall be set to zero. Default values should be accessible even if the logical unit is not
ready.

6.13.5 Saved values

A PC field value of 11b requests that the device server return the saved values of the mode parameters. Mode
parameters not supported by the logical unit shall be set to zero. If saved values are not implemented, the
device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to SAVING PARAMETERS NOT SUPPORTED.

The method of saving parameters is vendor specific. The parameters are preserved such that they are
retained while the device is powered down. All saveable mode pages should be considered saved if a MODE
SELECT command issued with the SP bit set to one has completed with a GOOD status or after the successful
completion of a FORMAT UNIT command.

384 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.13.6 Initial responses

After a logical unit reset, the device server shall respond in the following manner:

a) if default values are requested, return the default values;

b) if saved values are requested, return valid restored mode parameters, or restore the mode
parameters and report them. If the saved values of the mode parameters are not able to be accessed,
the device server shall terminate the command with CHECK CONDITION status, with the sense key
set to NOT READY. If saved parameters are not implemented, respond as defined in 6.13.5; or
c) if current values are requested and the current values have been received as part of a MODE
SELECT command, then the current values shall be returned. If the current values have not been
received as part of a MODE SELECT command, the device server shall return:
A) the saved values, if saving is implemented and saved values are available; or
B) the default values.

6.14 MODE SENSE(10) command

The MODE SENSE(10) command (see table 202) requests the device server to return the specified medium,
logical unit, or peripheral device parameters. It is a complementary command to the MODE SELECT(10)
command. Device servers that implement the MODE SENSE(10) command shall also implement the MODE
SELECT(10) command.

Table 202 — MODE SENSE(10) command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (5Ah)
1 Reserved LLBAA DBD Reserved
2 PC PAGE CODE

3 SUBPAGE CODE

4
•• • Reserved
6
7 (MSB)
ALLOCATION LENGTH
8 (LSB)
9 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 202 for the MODE
SENSE(10) command.

If the Long LBA Accepted (LLBAA) bit is set to one, the device server is allowed to return parameter data with
the LONGLBA bit equal to one (see 7.5.5). If LLBAA bit is set to zero, the LONGLBA bit shall be zero in the
parameter data returned by the device server.

The CONTROL byte is defined in SAM-5.

See the MODE SENSE(6) command (6.13) for a description of the other fields and operation of this
command.

Working Draft SCSI Primary Commands - 4 (SPC-4) 385

T10/BSR INCITS 513 Revision 37 17 May 2014

6.15 PERSISTENT RESERVE IN command

6.15.1 PERSISTENT RESERVE IN command introduction

The PERSISTENT RESERVE IN command (see table 203) requests the device server to return information
about persistent reservations and reservation keys (i.e., registrations) that are active within a device server.
This command is used in conjunction with the PERSISTENT RESERVE OUT command (see 6.16).

Table 203 — PERSISTENT RESERVE IN command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (5Eh)
1 Reserved SERVICE ACTION

2
•• • Reserved
6
7 (MSB)
ALLOCATION LENGTH
8 (LSB)
9 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 203 for the PERSISTENT
RESERVE IN command.

The SERVICE ACTION field is defined in 4.2.5.2. The service action codes for the PERSISTENT RESERVE IN
command are defined in table 204.

Table 204 — PERSISTENT RESERVE IN service action codes

Code Name Description Reference

00h READ KEYS Returns all registered reservation keys 6.15.2
(i.e., registrations) as described in
5.12.6.2
01h READ RESERVATION Returns the current persistent reserva- 6.15.3
tions as described in 5.12.6.3
02h REPORT CAPABILITIES Returns capability information 6.15.4
03h READ FULL STATUS Returns complete information about 6.15.5
all registrations and the persistent
reservations, if any
04h to 1Fh Reserved Reserved

The ALLOCATION LENGTH field is defined in 4.2.5.6. The PERSISTENT RESERVE IN parameter data includes a
length field that indicates the number of parameter data bytes that follow in the parameter data. The allocation
length should be set to a value large enough to include the length field for the specified service action.

The CONTROL byte is defined in SAM-5.

386 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.15.2 READ KEYS service action

The READ KEYS service action requests the device server to return a parameter list containing a header and
a list of each currently registered I_T nexus’ reservation key. If multiple I_T nexuses have registered with the
same key, then that key value shall be listed multiple times, once for each such registration.

For more information on READ KEYS see 5.12.6.2.

The format for the parameter data provided in response to a PERSISTENT RESERVE IN command with the
READ KEYS service action is shown in table 205.

Table 205 — PERSISTENT RESERVE IN parameter data for READ KEYS

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • PRGENERATION
3 (LSB)
4 (MSB)
•• • ADDITIONAL LENGTH (n-7)
7 (LSB)
Reservation key list
8 (MSB)
•• • Reservation key [first]
15 (LSB)
•
••

n-7 (MSB)
•• • Reservation key [last]
n (LSB)

The Persistent Reservations Generation (PRGENERATION) field shall contain the value of a 32-bit wrapping
counter that the device server shall update (e.g., increment) during the processing of any PERSISTENT
RESERVE OUT command as described in table 216 (see 6.16.2). The PRgeneration value shall not be
updated by a PERSISTENT RESERVE IN command or by a PERSISTENT RESERVE OUT command that is
terminated due to an error or reservation conflict. Regardless of the APTPL bit value the PRgeneration value
shall be set to zero by a power on.

The ADDITIONAL LENGTH field indicates the number of bytes in the Reservation key list. The contents of the
ADDITIONAL LENGTHfield are not altered based on the allocation length (see 4.2.5.6).

The reservation key list contains the eight byte reservation keys for all I_T nexuses that have been registered
(see 5.12.7).

Working Draft SCSI Primary Commands - 4 (SPC-4) 387

T10/BSR INCITS 513 Revision 37 17 May 2014

6.15.3 READ RESERVATION service action

6.15.3.1 READ RESERVATION service action operation

The READ RESERVATION service action requests the device server to return parameter data that contains a
header (see table 206) or the persistent reservation, if any, that is present in the device server (see table 207).

For more information on READ RESERVATION see 5.12.6.3.

If no persistent reservation is held, the format for the parameter data provided in response to a PERSISTENT
RESERVE IN command with the READ RESERVATION service action is shown in table 206.

Table 206 — Format of PERSISTENT RESERVE IN parameter data for READ RESERVATION with
no reservation held

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • PRGENERATION
3 (LSB)
4 (MSB)
•• • ADDITIONAL LENGTH (00000000h)
7 (LSB)

The PRGENERATION field shall be as defined for the PERSISTENT RESERVE IN command with READ KEYS
service action parameter data (see 6.15.2).

The ADDITIONAL LENGTH field shall be set to zero (see table 206), indicating that no persistent reservation is
held.

388 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If a persistent reservation is held, the format for the parameter data provided in response to a PERSISTENT
RESERVE IN command with the READ RESERVATION service action is shown in table 207.

Table 207 — Format of PERSISTENT RESERVE IN parameter data for READ RESERVATION with
a reservation held

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • PRGENERATION
3 (LSB)
4 (MSB)
•• • ADDITIONAL LENGTH (00000010h)
7 (LSB)
8 (MSB)
•• • RESERVATION KEY
15 (LSB)
16
•• • Obsolete
19
20 Reserved
21 SCOPE TYPE

22
Obsolete
23

The PRGENERATION field shall be as defined for the PERSISTENT RESERVE IN command with READ KEYS
service action parameter data.

The ADDITIONAL LENGTH field indicates the number of bytes that follow and shall be set as shown in table 207.
The contents of the ADDITIONAL LENGTH field are not altered based on the allocation length (see 4.2.5.6).

The RESERVATION KEY field shall indicate the reservation key under which the persistent reservation is held
(see 5.12.10).

The SCOPE field shall be set to LU_SCOPE (see 6.15.3.2).

The TYPE field shall indicate the persistent reservation type (see 6.15.3.3) specified in the PERSISTENT
RESERVE OUT command that created the persistent reservation.

The obsolete fields in bytes 16 to 19, byte 22, and byte 23 were defined in SPC-2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 389

T10/BSR INCITS 513 Revision 37 17 May 2014

6.15.3.2 Persistent reservations scope

The SCOPE field (see table 208) shall be set to LU_SCOPE, specifying that the persistent reservation applies
to the entire logical unit.

Table 208 — Persistent reservation SCOPE field

Code Name Description

0h LU_SCOPE Persistent reservation applies to the full logical unit
1h to 2h Obsolete
3h to Fh Reserved

The LU_SCOPE scope shall be implemented by all device servers that implement PERSISTENT RESERVE
OUT.

390 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.15.3.3 Persistent reservations type

The TYPE field (see table 209) specifies the characteristics of the persistent reservation being established for
all logical blocks within the logical unit. Table 66 (see 5.12.1) defines the persistent reservation types under
which each command defined in this standard is processed. Each other command standard defines the
persistent reservation types under which each command defined in that command standard is processed.

Table 209 — Persistent reservation TYPE field

Code Name Description

0h Obsolete
1h Write Access Restrictions: Some commands (e.g., media-access write
Exclusive commands) are only allowed for the persistent reservation holder (see
5.12.10).
Persistent Reservation Holder: There is only one persistent reservation
holder.
2h Obsolete
3h Exclusive Access Restrictions: Some commands (e.g., media-access commands)
Access are only allowed for the persistent reservation holder (see 5.12.10).
Persistent Reservation Holder: There is only one persistent reservation
holder.
4h Obsolete
5h Write Access Restrictions: Some commands (e.g., media-access write
Exclusive – commands) are only allowed for registered I_T nexuses.
Registrants Persistent Reservation Holder: There is only one persistent reservation
Only holder (see 5.12.10).
6h Exclusive Access Restrictions: Some commands (e.g., media-access commands)
Access – are only allowed for registered I_T nexuses.
Registrants Persistent Reservation Holder: There is only one persistent reservation
Only holder (see 5.12.10).
7h Write Access Restrictions: Some commands (e.g., media-access write
Exclusive – commands) are only allowed for registered I_T nexuses.
All Persistent Reservation Holder: Each registered I_T nexus is a persistent
Registrants reservation holder (see 5.12.10).
8h Exclusive Access Restrictions: Some commands (e.g., media-access commands)
Access – are only allowed for registered I_T nexuses.
All Persistent Reservation Holder: Each registered I_T nexus is a persistent
Registrants reservation holder (see 5.12.10).
9h to Fh Reserved

Working Draft SCSI Primary Commands - 4 (SPC-4) 391

T10/BSR INCITS 513 Revision 37 17 May 2014

6.15.4 REPORT CAPABILITIES service action

The REPORT CAPABILITIES service action requests the device server to return information on persistent
reservation features.

The format for the parameter data provided in response to a PERSISTENT RESERVE IN command with the
REPORT CAPABILITIES service action is shown in table 210.

Table 210 — PERSISTENT RESERVE IN parameter data for REPORT CAPABILITIES

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
LENGTH (0008h)
1 (LSB)
2 RLR_C Reserved CRH SIP_C ATP_C Reserved PTPL_C

3 TMV ALLOW COMMANDS Reserved PTPL_A

4
PERSISTENT RESERVATION TYPE MASK
5
6
Reserved
7

The LENGTH field indicates the length in bytes of the parameter data and shall be set as shown in table 210 in
the parameter data for a PERSISTENT RESERVE IN command with the REPORT CAPABILITIES service
action. The contents of the LENGTH field are not altered based on the allocation length (see 4.2.5.6).

A replace lost reservation capable ( RLR _ C) bit set to one indicates that the device server supports the
REPLACE LOST RESERVATION service action in the PERSISTENT RESERVE OUT command. An RLR_C
bit set to zero indicates that the device server does not support the REPLACE LOST RESERVATION service
action in the PERSISTENT RESERVE OUT command. If the RLR_C bit is set to zero then the device server
shall not terminate any commands with CHECK CONDITION status with the sense key set to DATA
PROTECT and the additional sense code set to PERSISTENT RESERVATION INFORMATION LOST (see
5.12.5.4).

A compatible reservation handling (CRH) bit set to one indicates that the device server supports the exceptions
to the SPC-2 RESERVE commands and RELEASE commands described in 5.12.3. A CRH bit set to zero
indicates that RESERVE commands and RELEASE commands are processed as defined in SPC-2.

A specify initiator ports capable (SIP_C) bit set to one indicates that the device server supports the SPEC_I_PT
bit in the PERSISTENT RESERVE OUT command parameter data (see 6.16.3). An SIP_C bit set to zero
indicates that the device server does not support the SPEC_I_PT bit in the PERSISTENT RESERVE OUT
command parameter data.

An all target ports capable (ATP_C) bit set to one indicates that the device server supports the ALL_TG_PT bit in
the PERSISTENT RESERVE OUT command parameter data. An ATP_C bit set to zero indicates that the
device server does not support the ALL_TG_PT bit in the PERSISTENT RESERVE OUT command parameter
data.

A persist through power loss capable (PTPL_C) bit set to one indicates that the device server supports the
persist through power loss capability (see 5.12.5) for persistent reservations and the APTPL bit in the

392 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

PERSISTENT RESERVE OUT command parameter data. An PTPL_C bit set to zero indicates that the device
server does not support the persist through power loss capability.

A type mask valid (TMV) bit set to one indicates that the PERSISTENT RESERVATION TYPE MASK field contains a
bit map indicating which persistent reservation types are supported by the device server. A TMV bit set to zero
indicates that the PERSISTENT RESERVATION TYPE MASK field shall be ignored.

The ALLOW COMMANDS field (see table 211) indicates whether certain commands are allowed through certain
types of persistent reservations.

Table 211 — ALLOW COMMANDS field (part 1 of 3)

Code Description
No information is provided about whether certain commands are allowed through certain types
000b
of persistent reservations.
The device server allows the TEST UNIT READY command (see table 66 in 5.12.1) through
Write Exclusive type reservations and Exclusive Access type reservations.
The device server does not provide information about whether the following commands are
allowed through Write Exclusive type reservations:
a) MODE SENSE;
b) READ ATTRIBUTE;
c) READ BUFFER;
001b d) RECEIVE COPY DATA(LID1);
e) RECEIVE COPY OPERATING PARAMETERS;
f) RECEIVE COPY FAILURE DETAILS(LID1);
g) RECEIVE COPY STATUS(LID1);
h) RECEIVE DIAGNOSTIC RESULTS;
i) REPORT SUPPORTED OPERATION CODES;
j) REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS; and
k) READ DEFECT DATA (see SBC-3).
The device server allows the TEST UNIT READY command through Write Exclusive type
reservations and Exclusive Access type reservations.
The device server does not allow:
a) the following commands through Write Exclusive type reservations:
A) MODE SENSE;
B) READ ATTRIBUTE;
C) READ BUFFER;
D) RECEIVE DIAGNOSTIC RESULTS;
E) REPORT SUPPORTED OPERATION CODES;
010b
F) REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS; and
G) READ DEFECT DATA (see SBC-3);
and
b) the following commands through Write Exclusive type reservations or Exclusive Access
type reservations:
A) RECEIVE COPY DATA(LID1);
B) RECEIVE COPY OPERATING PARAMETERS;
C) RECEIVE COPY FAILURE DETAILS(LID1); and
D) RECEIVE COPY STATUS(LID1).

Working Draft SCSI Primary Commands - 4 (SPC-4) 393

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 211 — ALLOW COMMANDS field (part 2 of 3)

Code Description
The device server allows:
a) the TEST UNIT READY command through Write Exclusive type reservations and
Exclusive Access type reservations; and
b) the following commands through Write Exclusive type reservations:
A) MODE SENSE;
B) READ ATTRIBUTE;
C) READ BUFFER;
D) RECEIVE DIAGNOSTIC RESULTS;
011b E) REPORT SUPPORTED OPERATION CODES;
F) REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS; and
G) READ DEFECT DATA (see SBC-3).
The device server does not allow the following commands through Write Exclusive type
reservations or Exclusive Access type reservations:
a) RECEIVE COPY DATA(LID1);
b) RECEIVE COPY OPERATING PARAMETERS;
c) RECEIVE COPY FAILURE DETAILS(LID1); and
d) RECEIVE COPY STATUS(LID1).
The device server allows:
a) the following commands through Write Exclusive and Exclusive Access persistent
reservations:
A) TEST UNIT READY;
B) RECEIVE COPY DATA(LID1);
C) RECEIVE COPY OPERATING PARAMETERS;
D) RECEIVE COPY FAILURE DETAILS(LID1); and
E) RECEIVE COPY STATUS(LID1);
100b and
b) the following commands through Write Exclusive persistent reservations:
A) MODE SENSE;
B) READ ATTRIBUTE;
C) READ BUFFER;
D) RECEIVE DIAGNOSTIC RESULTS; and
E) REPORT SUPPORTED OPERATION CODES; and
F) REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS;
G) READ DEFECT DATA (see SBC-3).

394 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 211 — ALLOW COMMANDS field (part 3 of 3)

Code Description
The device server allows:
a) the following commands through Write Exclusive and Exclusive Access persistent
reservations:
A) TEST UNIT READY;
B) RECEIVE COPY DATA(LID1);
C) RECEIVE COPY OPERATING PARAMETERS;
D) RECEIVE COPY FAILURE DETAILS(LID1);
E) RECEIVE COPY STATUS(LID1);
101b F) REPORT SUPPORTED OPERATION CODES; and
G) REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS;
and
b) the following commands through Write Exclusive persistent reservations:
A) MODE SENSE;
B) READ ATTRIBUTE;
C) READ BUFFER;
D) RECEIVE DIAGNOSTIC RESULTS; and
E) READ DEFECT DATA (see SBC-3).
all others Reserved

A Persist Through Power Loss Activated (PTPL_A) bit set to one indicates that the persist through power loss
capability is activated (see 5.12.5). A PTPL_A bit set to zero indicates that the persist through power loss
capability is not activated.

The PERSISTENT RESERVATION TYPE MASK field (see table 212) contains a bit map that indicates the persistent
reservation types that are supported by the device server.

Table 212 — Persistent Reservation Type Mask format

Bit
7 6 5 4 3 2 1 0
Byte
4 WR_EX_AR EX_AC_RO WR_EX_RO Reserved EX_AC Reserved WR_EX Reserved
5 Reserved EX_AC_AR

A Write Exclusive – All Registrants (WR_EX_AR) bit set to one indicates that the device server supports the
Write Exclusive – All Registrants persistent reservation type. An WR_EX_AR bit set to zero indicates that the
device server does not support the Write Exclusive – All Registrants persistent reservation type.

An Exclusive Access – Registrants Only (EX_AC_RO) bit set to one indicates that the device server supports
the Exclusive Access – Registrants Only persistent reservation type. An EX_AC_RO bit set to zero indicates
that the device server does not support the Exclusive Access – Registrants Only persistent reservation type.

A Write Exclusive – Registrants Only (WR_EX_RO) bit set to one indicates that the device server supports the
Write Exclusive – Registrants Only persistent reservation type. An WR_EX_RO bit set to zero indicates that the
device server does not support the Write Exclusive – Registrants Only persistent reservation type.

An Exclusive Access (EX_AC) bit set to one indicates that the device server supports the Exclusive Access
persistent reservation type. An EX_AC bit set to zero indicates that the device server does not support the
Exclusive Access persistent reservation type.

Working Draft SCSI Primary Commands - 4 (SPC-4) 395

T10/BSR INCITS 513 Revision 37 17 May 2014

A Write Exclusive ( WR_ EX ) bit set to one indicates that the device server supports the Write Exclusive
persistent reservation type. An WR_EX bit set to zero indicates that the device server does not support the
Write Exclusive persistent reservation type.

An Exclusive Access – All Registrants (EX_AC_AR) bit set to one indicates that the device server supports the
Exclusive Access – All Registrants persistent reservation type. An EX_AC_AR bit set to zero indicates that the
device server does not support the Exclusive Access – All Registrants persistent reservation type.

6.15.5 READ FULL STATUS service action

The READ FULL STATUS service action requests the device server to return a parameter list describing the
registration status and persistent reservation status of each currently registered I_T nexus for the logical unit.

For more information on READ FULL STATUS see 5.12.6.4.

The format for the parameter data provided in response to a PERSISTENT RESERVE IN command with the
READ FULL STATUS service action is shown in table 213.

Table 213 — PERSISTENT RESERVE IN parameter data for READ FULL STATUS

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • PRGENERATION
3 (LSB)
4 (MSB)
•• • ADDITIONAL LENGTH (n-7)
7 (LSB)
Full status descriptors
8
•• • Full status descriptor (see table 214) [first]

••
•

•• • Full status descriptor (see table 214) [last]

n

The PRGENERATION field shall be as defined for the PERSISTENT RESERVE IN command with READ KEYS
service action parameter data (see 6.15.2).

The ADDITIONAL LENGTH field indicates the number of bytes that follow in the full status descriptors. The
contents of the ADDITIONAL LENGTH field are not altered based on the allocation length (see 4.2.5.6).

396 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The format of the full status descriptors is shown in table 214. Each full status descriptor describes one or
more registered I_T nexuses. The device server shall return persistent reservations status information for
every registered I_T nexus.

Table 214 — PERSISTENT RESERVE IN full status descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • RESERVATION KEY
7 (LSB)
8
•• • Reserved
11
12 Reserved ALL_TG_PT R_HOLDER

13 SCOPE TYPE

14
•• • Reserved
17
18 (MSB)
RELATIVE TARGET PORT IDENTIFIER
19 (LSB)
20 (MSB)
•• • ADDITIONAL DESCRIPTOR LENGTH (n-23)
23 (LSB)
24
•• • TransportID
n

The RESERVATION KEY field contains the reservation key.

A Reservation Holder (R_HOLDER) bit set to one indicates that all I_T nexuses described by this full status
descriptor are registered and are persistent reservation holders (see 5.12.10). A R_HOLDER bit set to zero
indicates that all I_T nexuses described by this full status descriptor are registered but are not persistent
reservation holders.

An All Target Ports (ALL_TG_PT) bit set to zero indicates that this full status descriptor represents a single I_T
nexus. An ALL_TG_PT bit set to one indicates that:

a) this full status descriptor represents all the I_T nexuses that are associated with both:
A) the initiator port specified by the TransportID; and
B) every target port in the SCSI target device;
b) all the I_T nexuses are registered with the same reservation key; and
c) all the I_T nexuses are either reservation holders or not reservation holders as indicated by the
R_HOLDER bit.

The device server is not required to return a full status descriptor with the ALL_TG_PT bit set to one. Instead, it
may return separate full status descriptors for each I_T nexus.

Working Draft SCSI Primary Commands - 4 (SPC-4) 397

T10/BSR INCITS 513 Revision 37 17 May 2014

If the R_HOLDER bit is set to one (i.e., if the I_T nexus described by this full status descriptor is a reservation
holder), then the SCOPE field and the TYPE field are as defined in the READ RESERVATION service action
parameter data (see 6.15.3). If the R_HOLDER bit is set to zero, the contents of the SCOPE field and the TYPE
field are not defined by this standard.

If the ALL_TG_PT bit is set to zero, the RELATIVE TARGET PORT IDENTIFIER field (see 4.3.4) is set to the relative
port identifier of the target port that is part of the I_T nexus described by this full status descriptor. If the
ALL_TG_PT bit is set to one, the contents of the RELATIVE TARGET PORT IDENTIFIER field are not defined by this
standard.

The ADDITIONAL DESCRIPTOR LENGTH field indicates the number of bytes that follow in the descriptor (i.e., the
size of the TransportID).

The TransportID specifies a TransportID (see 7.6.4) identifying the initiator port that is part of the I_T nexus or
I_T nexuses described by this full status descriptor.

6.16 PERSISTENT RESERVE OUT command

6.16.1 PERSISTENT RESERVE OUT command introduction

The PERSISTENT RESERVE OUT command (see table 215) requests the device server to perform a service
action that adds, removes, or manages a persistent reservation for the logical unit for the exclusive or shared
use of one or more I_T nexuses.

I_T nexuses performing PERSISTENT RESERVE OUT service actions are identified by a registered
reservation key provided by the application client. An application client may use the PERSISTENT RESERVE
IN command to obtain the reservation key, if any, for the I_T nexus holding a persistent reservation and may
use the PERSISTENT RESERVE OUT command to preempt that persistent reservation.

Table 215 — PERSISTENT RESERVE OUT command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (5Fh)
1 Reserved SERVICE ACTION

2 SCOPE TYPE

3
Reserved
4
5 (MSB)
•• • PARAMETER LIST LENGTH
8 (LSB)
9 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 215 for the PERSISTENT
RESERVE OUT command.

The SERVICE ACTION field is defined in 4.2.5.2 and 6.16.2.

398 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If a PERSISTENT RESERVE OUT command is attempted, but there are insufficient device server resources
to complete the operation, the device server shall terminate the command with CHECK CONDITION status,
with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INSUFFICIENT
REGISTRATION RESOURCES.

The PERSISTENT RESERVE OUT command contains fields that specify a persistent reservation service
action, the intended scope of the persistent reservation, and the restrictions caused by the persistent
reservation. The SCOPE field and TYPE field are defined in 6.15.3.2 and 6.15.3.3. If a SCOPE field specifies a
scope that is not implemented, the device server shall terminate the command with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN
CDB.

Fields contained in the PERSISTENT RESERVE OUT parameter list specify the information required to
perform a particular persistent reservation service action.

The PARAMETER LIST LENGTH field specifies the number of bytes of parameter data for the PERSISTENT
RESERVE OUT command.

The parameter list shall be 24 bytes in length and the PARAMETER LIST LENGTH field shall contain 24 (i.e., 18h),
if the following conditions are true:

a) the SPEC_I_PT bit (see 6.16.3) is set to zero; and

b) the service action is not REGISTER AND MOVE.

If the SPEC_I_PT bit is set to zero, the service action is not REGISTER AND MOVE, and the parameter list
length is not 24, then the device server shall terminate the command with CHECK CONDITION status, with
the sense key set to ILLEGAL REQUEST, and the additional sense code set to PARAMETER LIST LENGTH
ERROR.

If the parameter list length is larger than the device server is able to process, the device server should
terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and
the additional sense code set to PARAMETER LIST LENGTH ERROR.

The CONTROL byte is defined in SAM-5.

Working Draft SCSI Primary Commands - 4 (SPC-4) 399

T10/BSR INCITS 513 Revision 37 17 May 2014

6.16.2 PERSISTENT RESERVE OUT service actions and parameter list formats

As part of processing the PERSISTENT RESERVE OUT service actions, the device server shall increment
the PRgeneration value as defined in table 216.

The PERSISTENT RESERVE OUT command service actions are defined in table 216.

Table 216 — PERSISTENT RESERVE OUT service action codes

PRGENERATION
field Parameter
Code Name Description incremented list format
00h REGISTER Register a reservation key with the device Yes Basic
server (see 5.12.7) or unregister a reser- (see 6.16.3)
vation key (see 5.12.11.2.3).
01h RESERVE Creates a persistent reservation having a No Basic
specified SCOPE and TYPE (see 5.12.9). (see 6.16.3)
The SCOPE and TYPE of a persistent reser-
vation are defined in 6.15.3.2 and
6.15.3.3.
02h RELEASE Releases the selected persistent reser- No Basic
vation (see 5.12.11.2.2). (see 6.16.3)
03h CLEAR Clears all reservation keys (i.e., registra- Yes Basic
tions) and all persistent reservations (see (see 6.16.3)
5.12.11.2.7).
04h PREEMPT Preempts persistent reservations and/or Yes Basic
removes registrations (see 5.12.11.2.4). (see 6.16.3)
05h PREEMPT Preempts persistent reservations and/or Yes Basic
AND ABORT removes registrations and aborts all (see 6.16.3)
commands for all preempted I_T nexuses
(see 5.12.11.2.4 and 5.12.11.2.6).
06h REGISTER Register a reservation key with the device Yes Basic
AND IGNORE server (see 5.12.7) or unregister a reser- (see 6.16.3)
EXISTING KEY vation key (see 5.12.11.2.3).
07h REGISTER Register a reservation key for another I_T Yes Register and
AND MOVE nexus with the device server and move an move
existing persistent reservation to that I_T (see 6.16.4)
nexus (see 5.12.8)
08h REPLACE Replace lost persistent reservation infor- No a Basic
LOST mation (see 5.12.11.3). (see 6.16.3)
RESERVATION
09h to Reserved
1Fh
a The processing of a REPLACE LOST RESERVATION service action does not increment the
PRGENERATION field. Instead, the PRGENERATION field is set to zero (see 5.12.11.3).

400 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 217 summarizes which fields are set by the application client and interpreted by the device server for
each service action and scope value.

Table 217 — PERSISTENT RESERVE OUT service actions and valid parameters (part 1 of 2)

Parameters (part 1 of 2)

SERVICE ACTION
Allowed Parameter RESERVATION RESERVATION
Service action SCOPE list format TYPE KEY KEY APTPL

Basic
REGISTER ignored ignored valid valid valid
(see 6.16.3)
REGISTER
Basic
AND IGNORE ignored ignored ignored valid valid
(see 6.16.3)
EXISTING KEY
Basic
RESERVE LU_SCOPE valid valid ignored ignored
(see 6.16.3)
Basic
RELEASE LU_SCOPE valid valid ignored ignored
(see 6.16.3)
Basic
CLEAR ignored ignored valid ignored ignored
(see 6.16.3)
Basic
PREEMPT LU_SCOPE valid valid valid ignored
(see 6.16.3)
PREEMPT Basic
LU_SCOPE valid valid valid ignored
AND ABORT (see 6.16.3)
Register and
REGISTER
LU_SCOPE move valid valid valid valid
AND MOVE
(see 6.16.4)
REPLACE
Basic
LOST LU_SCOPE valid valid valid ignored
(see 6.16.3)
RESERVATION

Working Draft SCSI Primary Commands - 4 (SPC-4) 401

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 217 — PERSISTENT RESERVE OUT service actions and valid parameters (part 2 of 2)

Parameters (part 2 of 2)

Allowed Parameter
Service action SCOPE list format ALL_TG_PT SPEC_I_PT UNREG

Basic
REGISTER ignored valid valid n/a
(see 6.16.3)
REGISTER
Basic
AND IGNORE ignored valid invalid n/a
(see 6.16.3)
EXISTING KEY
Basic
RESERVE LU_SCOPE ignored invalid n/a
(see 6.16.3)
Basic
RELEASE LU_SCOPE ignored invalid n/a
(see 6.16.3)
Basic
CLEAR ignored ignored invalid n/a
(see 6.16.3)
Basic
PREEMPT LU_SCOPE ignored invalid n/a
(see 6.16.3)
PREEMPT Basic
LU_SCOPE ignored invalid n/a
AND ABORT (see 6.16.3)
Register and
REGISTER
LU_SCOPE move n/a n/a valid
AND MOVE
(see 6.16.4)
REPLACE
Basic
LOST LU_SCOPE invalid invalid n/a
(see 6.16.3)
RESERVATION

402 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.16.3 Basic PERSISTENT RESERVE OUT parameter list

The parameter list format shown in table 218 shall be used by the PERSISTENT RESERVE OUT command
with all service actions except the REGISTER AND MOVE service action. All fields shall be sent, even if the
field is not required for the specified service action and scope values.

Table 218 — PERSISTENT RESERVE OUT parameter list

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • RESERVATION KEY
7 (LSB)
8 (MSB)
•• • SERVICE ACTION RESERVATION KEY
15 (LSB)
16
•• • Obsolete
19
20 Reserved SPEC_I_PT ALL_TG_PT Reserved APTPL

21 Reserved
22
Obsolete
23
24
•• • Additional parameter data
n

The obsolete fields in bytes 16 to 19, byte 22 and byte 23 were defined in SPC-2.

The RESERVATION KEY field contains an eight byte value provided by the application client to the device server
to identify the I_T nexus that is the source of the PERSISTENT RESERVE OUT command. The device server
shall verify that the contents of the RESERVATION KEY field in a PERSISTENT RESERVE OUT command
parameter data matches the registered reservation key for the I_T nexus from which the command was
received, except for:

a) the REGISTER AND IGNORE EXISTING KEY service action where the RESERVATION KEY field shall
be ignored;
b) the REGISTER service action for an unregistered I_T nexus where the RESERVATION KEY field shall
contain zero; and
c) the REPLACE LOST RESERVATION service action where the RESERVATION KEY field shall contain
zero.

Except as noted in this subclause, if a PERSISTENT RESERVE OUT command specifies a RESERVATION KEY
field other than the reservation key registered for the I_T nexus, then the device server shall complete the
command with RESERVATION CONFLICT status. Except as noted in this subclause, the reservation key of
the I_T nexus shall be verified to be correct regardless of the SERVICE ACTION and SCOPE field values.

Working Draft SCSI Primary Commands - 4 (SPC-4) 403

T10/BSR INCITS 513 Revision 37 17 May 2014

The SERVICE ACTION RESERVATION KEY field contains information associated with the following service actions:

a) REGISTER;
b) REGISTER AND IGNORE EXISTING KEY;
c) PREEMPT;
d) PREEMPT AND ABORT; and
e) REPLACE LOST RESERVATION.

The SERVICE ACTION RESERVATION KEY field is ignored for the following service actions:

a) RESERVE;
b) RELEASE; and
c) CLEAR.

For the REGISTER service action and REGISTER AND IGNORE EXISTING KEY service action, the SERVICE
ACTION RESERVATION KEYfield contains:

a) the new reservation key to be registered in place of the registered reservation key; or
b) zero to unregister the registered reservation key.

For the PREEMPT service action and PREEMPT AND ABORT service action, the SERVICE ACTION
RESERVATION KEY field contains the reservation key of:

a) the registrations to be removed; and

b) if the SERVICE ACTION RESERVATION KEY field identifies a persistent reservation holder (see 5.12.10),
then the persistent reservations to be preempted.

For the REPLACE LOST RESERVATION service action, the SERVICE ACTION RESERVATION KEY field contains
the new reservation key to be registered

If the Specify Initiator Ports (SPEC_I_PT) bit is set to zero, the device server shall apply the registration only to
the I_T nexus that sent the PERSISTENT RESERVE OUT command. If the SPEC_I_PT bit is set to one for any
service action except the REGISTER service action, then the device server shall terminate the command with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set
to INVALID FIELD IN PARAMETER LIST. If the SPEC_I_PT bit is set to one for the REGISTER service action,
then the additional parameter data (see table 219) shall include a list of transport IDs and the device server

404 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

shall also apply the registration to the I_T nexus for each initiator port specified by a TransportID. If a regis-
tration fails for any initiator port (e.g., if the logical unit does not have enough resources available to hold the
registration information), then no registrations shall be made and the command shall be terminated with
CHECK CONDITION status.

Table 219 — PERSISTENT RESERVE OUT specify initiator ports additional parameter data

Bit
7 6 5 4 3 2 1 0
Byte
24
•• • TRANSPORTID PARAMETER DATA LENGTH (n-27)
27
TransportIDs list
28
•• • TransportID [first]

•
••

•• • TransportID [last]
n

The TRANSPORTID PARAMETER DATA LENGTH field specifies the number of bytes of TransportIDs that follow.

If:

a) the value in the PARAMETER LIST LENGTH field in the CDB does not include all of the additional
parameter list bytes specified by the TRANSPORTID PARAMETER DATA LENGTH field; or
b) the value in the TRANSPORTID PARAMETER DATA LENGTH field results in the truncation of a TransportID,

then the device server:

a) shall terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST; and
b) should set the additional sense code to PARAMETER LIST LENGTH ERROR.

The format of a TransportID is defined in 7.6.4.

The All Target Ports (ALL_TG_PT) bit is valid only for the REGISTER service action and the REGISTER AND
IGNORE EXISTING KEY service action, and shall be ignored for all other service actions. If the device server
receives a REGISTER service action or a REGISTER AND IGNORE EXISTING KEY service action with the
ALL_TG_PT bit set to one, then the device server shall create the specified registration on all target ports in the
SCSI target device known to the device server (i.e., as if the same registration request had been received
individually through each target port). If the device server receives a REGISTER service action or a
REGISTER AND IGNORE EXISTING KEY service action with the ALL_TG_PT bit set to zero, then the device
server shall apply the registration only to the target port through which the PERSISTENT RESERVE OUT
command was received. If a device server that does not support an ALL_TG_PT bit set to one receives that
value in a REGISTER service action or a REGISTER AND IGNORE EXISTING KEY service action, then the
device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

Working Draft SCSI Primary Commands - 4 (SPC-4) 405

T10/BSR INCITS 513 Revision 37 17 May 2014

The Activate Persist Through Power Loss (APTPL) bit is:

a) valid only for the REGISTER service action and REGISTER AND IGNORE EXISTING KEY service
action; and
b) shall be ignored for all other service actions.

If a device server that does not support an APTPL bit set to one detects that value in a REGISTER service
action or a REGISTER AND IGNORE EXISTING KEY service action, then the device server shall terminate
the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the
additional sense code set to INVALID FIELD IN PARAMETER LIST.

If the last valid APTPL bit value processed by the device server is zero, the loss of power in the SCSI target
device shall release the persistent reservation for the logical unit and remove all registered reservation keys
(see 5.12.7). If the last valid APTPL bit value processed by the device server is one, the logical unit shall retain
any persistent reservation(s) that may be present and all reservation keys (i.e., registrations) for all I_T
nexuses even if power is lost (see 5.12.5).

6.16.4 Parameter list for the PERSISTENT RESERVE OUT command with REGISTER AND MOVE
service action

The parameter list format shown in table 220 shall be used by the PERSISTENT RESERVE OUT command
with REGISTER AND MOVE service action.

Table 220 — PERSISTENT RESERVE OUT with REGISTER AND MOVE service action parameter list

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • RESERVATION KEY
7 (LSB)
8 (MSB)
•• • SERVICE ACTION RESERVATION KEY
15 (LSB)
16 Reserved
17 Reserved UNREG APTPL

18 (MSB)
RELATIVE TARGET PORT IDENTIFIER
19 (LSB)
20 (MSB)
•• • TRANSPORTID LENGTH (n-23)
23 (LSB)
24
•• • TransportID
n

The RESERVATION KEY field contains an eight byte value provided by the application client to the device server
to identify the I_T nexus that is the source of the PERSISTENT RESERVE OUT command. The device server
shall verify that the contents of the RESERVATION KEY field in a PERSISTENT RESERVE OUT command
parameter data matches the registered reservation key for the I_T nexus from which the command was

406 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

received. If a PERSISTENT RESERVE OUT command specifies a RESERVATION KEY field other than the
reservation key registered for the I_T nexus, then the device server shall complete the command with
RESERVATION CONFLICT status.

The SERVICE ACTION RESERVATION KEY field contains the reservation key to be registered to the specified I_T
nexus.

If a device server that does not support an Activate Persist Through Power Loss (APTPL) bit set to one detects
that value in a REGISTER AND MOVE service action, then the device server shall terminate the command
with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense
code set to INVALID FIELD IN PARAMETER LIST.

If the last valid APTPL bit value processed by the device server is zero, the loss of power in the SCSI target
device shall release the persistent reservation for the logical unit and remove all registered reservation keys
(see 5.6.5). If the last valid APTPL bit value processed by the device server is one, the logical unit shall retain
any persistent reservation(s) that may be present and all reservation keys (i.e., registrations) for all I_T
nexuses even if power is lost (see 5.12.5).

An unregister (UNREG) bit set to zero specifies that the device server shall not unregister the I_T nexus on
which the PERSISTENT RESERVE OUT command REGISTER AND MOVE service action was received. An
UNREG bit set to one specifies that the device server shall unregister the I_T nexus on which the PERSISTENT
RESERVE OUT command REGISTER AND MOVE service action was received.

The RELATIVE TARGET PORT IDENTIFIER field (see 4.3.4) specifies the relative port identifier of the target port in
the I_T nexus to which the persistent reservation is to be moved.

The TRANSPORTID LENGTH field specifies the number of bytes of the TransportID that follow, shall be a
minimum of 24 bytes, and shall be a multiple of four.

The TransportID specifies the initiator port in the I_T nexus to which the persistent reservation is to be moved.
The format of the TransportID is defined in 7.6.4.

If:

a) the value in the PARAMETER LIST LENGTH field in the CDB does not include all of the parameter list
bytes specified by the TRANSPORTID LENGTH field; or
b) the value in the TRANSPORTID LENGTH field results in the truncation of a TransportID.

then the device server:

a) shall terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST; and
b) should set the additional sense code to PARAMETER LIST LENGTH ERROR.

Working Draft SCSI Primary Commands - 4 (SPC-4) 407

T10/BSR INCITS 513 Revision 37 17 May 2014

6.17 READ ATTRIBUTE command

6.17.1 READ ATTRIBUTE command introduction

The READ ATTRIBUTE command (see table 221) requests the device server to read attribute information
from medium auxiliary memory.

Table 221 — READ ATTRIBUTE command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (8Ch)
1 Reserved SERVICE ACTION

2
•• • Restricted (see SMC-3)
4
5 LOGICAL VOLUME NUMBER

6 Reserved
7 PARTITION NUMBER

8 (MSB)
FIRST ATTRIBUTE IDENTIFIER
9 (LSB)
10 (MSB)
•• • ALLOCATION LENGTH
13 (LSB)
14 Reserved CACHE

15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 221 for the READ
ATTRIBUTE command.

408 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The SERVICE ACTION field is defined in 4.2.5.2. The service action codes defined for the READ ATTRIBUTE
command are shown in table 222.

Table 222 — READ ATTRIBUTE service action codes

Code Name Description Reference

00h ATTRIBUTE VALUES Return attribute values. 6.17.2
01h ATTRIBUTE LIST Return a list of available attribute identifiers, identifi- 6.17.3
ers that are in the read only state or in the
read/write state (see 5.7).
02h LOGICAL VOLUME LIST Return a list of known logical volume numbers. 6.17.4
03h PARTITION LIST Return a list of known partition numbers. 6.17.5
04h Restricted SMC-3
05h SUPPORTED ATTRI- Return a list of supported attribute identifiers, identi- 6.17.6
BUTES fiers that are in the read only state, in the read/write
state, or in the nonexistent state (see 5.7).
06h to 1Fh Reserved

The LOGICAL VOLUME NUMBER field specifies a logical volume (e.g., the medium auxiliary memory storage for
one side of a double sided medium) within the medium auxiliary memory. The number of logical volumes of
the medium auxiliary memory shall equal the number of logical volumes of the attached medium. If the
medium only has a single logical volume, then its logical volume number shall be zero.

The PARTITION NUMBER field specifies a partition (see SSC-4) within a logical volume. The number of partitions
of the medium auxiliary memory shall equal the number of partitions of the attached medium. If the medium
only has a single partition, then its partition number shall be zero.

If the combination of logical volume number and partition number is not valid, the device server shall terminate
the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the
additional sense code set to INVALID FIELD IN CDB.

The FIRST ATTRIBUTE IDENTIFIER field specifies the attribute identifier of the first attribute to be returned. If the
specified attribute is in the unsupported state or nonexistent state (see 5.7), the device server shall terminate
the READ ATTRIBUTE command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

The ALLOCATION LENGTH field is defined in 4.2.5.6. that the device server shall

Caching of either a subset or the complete set of attribute information from the most recently mounted
medium may be supported as cached attribute information. If cached attribute information is supported the
device server shall:

a) support the CACHE bit being set to one; and

b) clear cached attribute information at the start of a medium load.

A CACHE bit set to one specifies that the device server may return cached attribute information. A CACHE bit set
to zero specifies that the device server shall not return cached attribute information.

Working Draft SCSI Primary Commands - 4 (SPC-4) 409

T10/BSR INCITS 513 Revision 37 17 May 2014

If medium auxiliary memory is not accessible, the device server shall return the status defined in table 223.

Table 223 — Status to be returned if medium auxiliary memory is not accessible

CACHE Medium Cached attribute Sense

bit state information Status Key Additional sense code
CHECK NOT
present ignored MEDIUM NOT PRESENT
CONDITION READY
0b LOGICAL UNIT NOT READY,
CHECK MEDIUM
not present ignored AUXILIARY MEMORY NOT
CONDITION ERROR
ACCESSIBLE
NO NO ADDITIONAL SENSE
available GOOD
SENSE INFORMATION
present
CHECK NOT
not available MEDIUM NOT PRESENT
CONDITION READY
1b NO NO ADDITIONAL SENSE
available GOOD
SENSE INFORMATION
not present LOGICAL UNIT NOT READY,
CHECK MEDIUM
not available AUXILIARY MEMORY NOT
CONDITION ERROR
ACCESSIBLE

If the medium auxiliary memory is not operational, the device server shall terminate the READ ATTRIBUTE
command with CHECK CONDITION status, with the sense key set to MEDIUM ERROR, and the additional
sense code set to AUXILIARY MEMORY READ ERROR.

If a medium is mounted and the medium auxiliary memory is accessible, the CACHE bit shall be ignored.

The CONTROL byte is defined in SAM-5.

The format of parameter data returned by the READ ATTRIBUTE command depends on the service action
specified.

410 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.17.2 ATTRIBUTE VALUES service action

The READ ATTRIBUTE command with ATTRIBUTE VALUES service action returns parameter data
containing the attributes that are in the read only state or read/write state (see 5.7) specified by the PARTITION
NUMBER field, LOGICAL VOLUME NUMBER field, and FIRST ATTRIBUTE IDENTIFIER field in the CDB. The parameter
data shall contain the requested attributes in ascending numerical order by attribute identifier value and in the
format shown in table 224.

Table 224 — READ ATTRIBUTE with ATTRIBUTE VALUES service action parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • AVAILABLE DATA (n-3)
3 (LSB)
Attribute(s)
4
•• • Attribute (see 7.4.1) [first]

•
••

•• • Attribute (see 7.4.1) [last]

n

The AVAILABLE DATA field shall contain the number of bytes of attribute information in the parameter data. The
contents of the AVAILABLE DATA field are not altered based on the allocation length (see 4.2.5.6).

The format of the attributes is described in 7.4.1.

Working Draft SCSI Primary Commands - 4 (SPC-4) 411

T10/BSR INCITS 513 Revision 37 17 May 2014

6.17.3 ATTRIBUTE LIST service action

The READ ATTRIBUTE command with ATTRIBUTE LIST service action returns parameter data containing
the attribute identifiers for the attributes that are in the read only state or in the read/write state (see 5.7) in the
specified partition number and volume number. The contents of FIRST ATTRIBUTE IDENTIFIER field in the CDB
shall be ignored. The parameter data shall contain the requested attribute identifiers in ascending numerical
order by attribute identifier value and in the format shown in table 225.

Table 225 — READ ATTRIBUTE with ATTRIBUTE LIST service action parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • AVAILABLE DATA (n-3)
3 (LSB)
Attribute identifiers
4 (MSB)
ATTRIBUTE IDENTIFIER [first]
5 (LSB)
••
•
n-1 (MSB)
ATTRIBUTE IDENTIFIER [last]
n (LSB)

The AVAILABLE DATA field shall contain the number of bytes of attribute identifiers in the parameter data. The
contents of the AVAILABLE DATA field are not altered based on the allocation length (see 4.2.5.6).

An ATTRIBUTE IDENTIFIER field is returned for each attribute that is in the read only state or in the read/write
state (see 5.7) in the specified partition number and volume number. See 7.4.2 for a description of the
attribute identifier values.

6.17.4 LOGICAL VOLUME LIST service action

The READ ATTRIBUTE command with LOGICAL VOLUME LIST service action returns parameter data (see
table 226) identifying the supported number of logical volumes. The contents of LOGICAL VOLUME NUMBER field,
PARTITION NUMBER field, and FIRST ATTRIBUTE IDENTIFIER field in the CDB shall be ignored.

Table 226 — READ ATTRIBUTE with LOGICAL VOLUME LIST service action parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
AVAILABLE DATA (0002h)
1 (LSB)
2 FIRST LOGICAL VOLUME NUMBER

3 NUMBER OF LOGICAL VOLUMES AVAILABLE

The AVAILABLE DATA field shall set as shown in table 226 for the parameter data returned by a READ
ATTRIBUTE command with LOGICAL VOLUME LIST service action. The contents of the AVAILABLE DATA field
are not altered based on the allocation length (see 4.2.5.6).

412 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The FIRST LOGICAL VOLUME NUMBER field indicates the first volume available. Logical volume numbering should
start at zero.

The NUMBER OF LOGICAL VOLUMES AVAILABLE field indicates the number of volumes available.

6.17.5 PARTITION LIST service action

The READ ATTRIBUTE command with PARTITION LIST service action returns parameter data (see table
227) identifying the number of partitions supported in the specified logical volume number. The contents of
PARTITION NUMBER field and FIRST ATTRIBUTE IDENTIFIER field in the CDB shall be ignored.

Table 227 — READ ATTRIBUTE with PARTITION LIST service action parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
AVAILABLE DATA (0002h)
1 (LSB)
2 FIRST PARTITION NUMBER

3 NUMBER OF PARTITIONS AVAILABLE

The AVAILABLE DATA field shall set as shown in table 227 for the parameter data returned by a READ
ATTRIBUTE command with PARTITION LIST service action. The contents of the AVAILABLE DATA field are not
altered based on the allocation length (see 4.2.5.6).

The FIRST PARTITION NUMBER field indicates the first partition available on the specified logical volume number.
Partition numbering should start at zero.

The NUMBER OF PARTITIONS AVAILABLE field indicates the number of partitions available on the specified logical
volume number.

Working Draft SCSI Primary Commands - 4 (SPC-4) 413

T10/BSR INCITS 513 Revision 37 17 May 2014

6.17.6 SUPPORTED ATTRIBUTES service action

The READ ATTRIBUTE command with SUPPORTED ATTRIBUTES service action returns parameter data
containing the attribute identifiers for the attributes that are supported by the device server in the specified
partition number and volume number. The contents of FIRST ATTRIBUTE IDENTIFIER field in the CDB shall be
ignored. The parameter data shall contain the requested attribute identifiers in ascending numerical order by
attribute identifier value and in the format shown in table 228.

Table 228 — READ ATTRIBUTE with SUPPORTED ATTRIBUTES service action parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • AVAILABLE DATA (n-3)
3 (LSB)
Attribute identifiers
4 (MSB)
ATTRIBUTE IDENTIFIER [first]
5 (LSB)
••
•
n-1 (MSB)
ATTRIBUTE IDENTIFIER [last]
n (LSB)

The AVAILABLE DATA field shall contain the number of bytes of attribute identifiers in the parameter data. The
contents of the AVAILABLE DATA field are not altered based on the allocation length (see 4.2.5.6).

For each attribute that is in the read only state, in the read/write state, or in the nonexistent state (see 5.7) in
the specified partition number and volume number:

a) an attribute identifier (see 7.4.2) is returned for device type attributes (see 7.4.2.2), medium type
attributes (see 7.4.2.3), and host type attributes defined in the applicable command standards; and
b) if vendor specific host type attributes (see 7.4.2.1) are supported, then an attribute identifier is
returned for the first supported vendor specific host type attribute and attribute identifiers may be
returned for other supported vendor specific host type attributes.

6.18 READ BUFFER command

6.18.1 READ BUFFER command introduction

The READ BUFFER command (see table 229) is used in conjunction with the WRITE BUFFER command for:

a) testing logical unit buffer memory;

b) testing the integrity of the service delivery subsystem;
c) downloading microcode (see 5.4); and
d) retrieving error history.

414 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 229 — READ BUFFER command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (3Ch)
1 Reserved MODE

2 BUFFER ID

3 (MSB)
4 BUFFER OFFSET

5 (LSB)
6 (MSB)
7 ALLOCATION LENGTH

8 (LSB)
9 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 229 for the READ BUFFER
command.

The function of this command and the meaning of fields within the CDB depend on the contents of the MODE
field. The MODE field is defined in table 230.

Table 230 — READ BUFFER MODE field

Code Description References

00h Obsolete
01h Vendor specific 6.18.2
02h Data 6.18.3
03h Descriptor 6.18.4
04h to 09h Reserved
0Ah Read data from echo buffer 6.18.5
0Bh Echo buffer descriptor 6.18.6
0Ch to 19h Reserved
1Ah Obsolete
1Bh Reserved
1Ch Error history 5.5 and 6.18.7
1Dh to 1Fh Reserved

The MODE field may be processed as specifying a service action by the REPORT SUPPORTED OPERATION
CODES command (see 6.35).

If the MODE field is not set to 01h (i.e., vendor specific), the ALLOCATION LENGTH field is defined in 4.2.5.6.

Working Draft SCSI Primary Commands - 4 (SPC-4) 415

T10/BSR INCITS 513 Revision 37 17 May 2014

The CONTROL byte is defined in SAM-5.

6.18.2 Vendor specific mode (01h)

In this mode, the meanings of the BUFFER ID field, BUFFER OFFSET field, and ALLOCATION LENGTH field are not
specified by this standard.

6.18.3 Data mode (02h)

In this mode, the device server returns parameter data that contains logical unit buffer data. The BUFFER ID
field specifies a buffer within the logical unit from which data shall be transferred. The manufacturer assigns
buffer ID codes to buffers within the logical unit. Buffer ID zero shall be supported. If more than one buffer is
supported, then additional buffer ID codes shall be assigned contiguously, beginning with one. Buffer ID code
assignments for the READ BUFFER command with data mode shall be the same as for the WRITE BUFFER
command with data mode (see 6.49.3). If an unsupported buffer ID code is selected, the device server shall
terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and
the additional sense code set to INVALID FIELD IN CDB.

The BUFFER OFFSET field specifies the byte offset within the specified buffer from which data shall be
transferred. The application client should conform to the offset boundary requirements returned in the READ
BUFFER descriptor (see 6.18.4). If the device server is unable to accept the specified buffer offset, the device
server shall terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

NOTE 30 - The buffer is shared by all application clients and I_T nexuses. If one application client writes the
buffer, a second application client writes the buffer, and then the first application client reads the buffer, then
the read may or may not retrieve the data from the second application client.

6.18.4 Descriptor mode (03h)

In this mode, the device server returns parameter data that contains a maximum of four bytes of READ
BUFFER descriptor information. The BUFFER OFFSET field is reserved in this mode. The allocation length
should be set to four or greater. The READ BUFFER descriptor is defined as shown in table 231.

Table 231 — READ BUFFER descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 OFFSET BOUNDARY

1 (MSB)
2 BUFFER CAPACITY

3 (LSB)

For READ BUFFER commands, the OFFSET BOUNDARY field (see table 232) applies to the following modes:

a) data (i.e., 02h) (see 6.18.3); and

b) error history (i.e., 1Ch) (see 6.18.7).

416 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

For WRITE BUFFER commands, the OFFSET BOUNDARY field (see table 232) applies to the following modes:

a) data (i.e., 02h) (see 6.49.3);

b) download microcode with offsets and activate (i.e., 06h) (see 6.49.6);
c) download microcode with offsets, save, and activate (i.e., 07h) (see 6.49.7);
d) download microcode with offsets, select activation events, save, and defer activate (i.e., 0Dh) (see
6.49.9); and
e) download microcode with offsets, save, and defer activate (i.e., 0Eh) (see 6.49.10).

For data mode (i.e., 02h), the boundary alignment indicated by the OFFSET BOUNDARY field applies only to the
buffer specified by the BUFFER ID field. For modes other than data to which the OFFSET BOUNDARY field applies,
the boundary alignment applies regardless of the buffer specified by the BUFFER ID field.

Table 232 — OFFSET BOUNDARY field

Code Description
00h to FEh Multiples of 2code (e.g., 00h means multiples of 1 byte or no offset restrictions,
01h means multiples of 2 bytes or even offsets, 02h means multiples of 4 bytes)
FFh 000000h is the only supported buffer offset

The BUFFER CAPACITY field indicates the maximum size in bytes of the buffer specified by the BUFFER ID field
for:

a) the READ BUFFER command with data mode (i.e., 02h); and
b) the WRITE BUFFER command with data mode (i.e., 02h).

6.18.5 Read data from echo buffer mode (0Ah)

In this mode, the device server returns parameter data that contains the echo buffer (i.e., parameter list data
sent to the device server by the most recent WRITE BUFFER command with the MODE field set to write data to
echo buffer (see 6.49.8) received on the same I_T nexus). The device server shall return the same number of
bytes of data as was received during the processing of the prior WRITE BUFFER command with the MODE
field set to write data to echo buffer, limited by the allocation length (see 4.2.5.6).

The BUFFER ID field and BUFFER OFFSET field are ignored in this mode.

If the device server has not received a WRITE BUFFER command with the mode set to write data to echo
buffer received on this I_T nexus since the last logical unit reset condition (see SAM-5) and completed that
command without an error, then the device server shall terminate the READ BUFFER command with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
COMMAND SEQUENCE ERROR. If the data in the echo buffer has been overwritten as the result of a WRITE
BUFFER command received on another I_T nexus and the device server supports error reporting on echo
buffer overwrites (i.e., the EBOS bit is set to one in the echo buffer descriptor (see 6.18.6)), then the device
server shall terminate the READ BUFFER command with CHECK CONDITION status, with the sense key set
to ABORTED COMMAND, and the additional sense code set to ECHO BUFFER OVERWRITTEN.

After a WRITE BUFFER command with the mode set to write data to echo buffer has completed without an
error, the application client may send multiple READ BUFFER commands with the mode set to read data from
echo buffer in order to read the echo buffer data multiple times.

Working Draft SCSI Primary Commands - 4 (SPC-4) 417

T10/BSR INCITS 513 Revision 37 17 May 2014

6.18.6 Echo buffer descriptor mode (0Bh)

In this mode, the device server returns parameter data that contains a maximum of four bytes of READ
BUFFER descriptor information for the echo buffer. If there is an echo buffer is not implemented, the device
server shall return all zeros in the READ BUFFER descriptor. The BUFFER ID field and BUFFER OFFSET field are
reserved in this mode. The allocation length should be set to four or greater. The echo buffer descriptor is
defined as shown in table 233.

Table 233 — Echo buffer descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 Reserved EBOS

1 Reserved
2 Reserved (MSB)
3 BUFFER CAPACITY (LSB)

If the echo buffer is implemented, the echo buffer descriptor shall be implemented.

An echo buffer overwritten supported (EBOS) bit set to one indicates either:

a) the device server returns the ECHO BUFFER OVERWRITTEN additional sense code if the data
being read from the echo buffer is not the data previously written by the same I_T nexus, or
b) the device server ensures echo buffer data returned to each I_T nexus is the same as that previously
written by that I_T nexus.

An EBOS bit set to zero specifies that the echo buffer may be overwritten by any intervening command
received on any I_T nexus.

The BUFFER CAPACITY field shall contain the size of the echo buffer in bytes aligned to a four-byte boundary.
The maximum echo buffer size is 4 096 bytes.

A READ BUFFER command with the mode set to echo buffer descriptor may be used to determine the echo
buffer capacity and supported features before a WRITE BUFFER command with the mode set to write data to
echo buffer (see 6.49.8) is sent.

6.18.7 Error history mode (1Ch)

6.18.7.1 Error history overview

This mode is used to manage and retrieve error history (see 5.5).

If the device server is unable to process a READ BUFFER command with the MODE field set to 1Ch, the device
server shall terminate the READ BUFFER command with CHECK CONDITION status, with the sense key set
to ILLEGAL REQUEST, and the additional sense code set to COMMAND SEQUENCE ERROR.

418 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The BUFFER ID field (see table 234) specifies the action that the device server shall perform, and the parameter
data, if any, that the device server shall return.

Table 234 — Error history BUFFER ID field

Error history
Buffer I_T nexus
Code Description offset constrained Reference
00h Return error history directory 0000h Yes 6.18.7.2
01h Return error history directory and create 0000h Yes 6.18.7.2
new error history snapshot
02h Return error history directory and 0000h No 6.18.7.2
establish new error history I_T nexus
03h Return error history directory, establish 0000h No 6.18.7.2
new error history I_T nexus, and create
new error history snapshot
04h to 0Fh Reserved Yes
10h to EFh Return error history 0000h to Yes 6.18.7.3
FFFFh
F0h to FDh Reserved Yes
FEh Clear error history I_T nexus Ignored Yes 6.18.7.4
FFh Clear error history I_T nexus and release Ignored Yes 6.18.7.5
error history snapshot

The device server shall terminate the READ BUFFER command with CHECK CONDITION status with the
sense key set to ILLEGAL REQUEST and the additional sense code set to OPERATION IN PROGRESS if the
device server receives a READ BUFFER command:

a) with the MODE field set to 1Ch;

b) with the BUFFER ID field set to a value that table 234 shows as constrained by error history I_T nexus;
c) if an error history I_T nexus exists and the command is received from an I_T nexus that is different
than that I_T nexus; and
d) an error history snapshot exists.

The BUFFER OFFSET field specifies the byte offset from the start of the buffer specified by the BUFFER ID field
from which the device server shall return data. The application client should conform to the offset boundary
requirements indicated in the READ BUFFER descriptor (see 6.18.4). If the buffer offset is not one of those
shown in table 234 or the device server is unable to accept the specified buffer offset, then the device server
shall terminate the READ BUFFER command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

Working Draft SCSI Primary Commands - 4 (SPC-4) 419

T10/BSR INCITS 513 Revision 37 17 May 2014

6.18.7.2 Error history directory

Whenever allowed by established error history I_T nexus constraints (see 6.18.7.1), if any, all error history
directory device server actions return an error history directory (see table 236). Some error history directory
device server actions also discard the existing error history snapshot and create a new error history snapshot
(see table 235).

Table 235 — Summary of error history directory device server actions

Error history snapshot

Establish new
BUFFER ID error history Preserved
field I_T nexus (if exists) Created
00h No a Yes No b
01h No a No Yes
02h Yes Yes No b
03h Yes No Yes
a
If no error history I_T nexus is established, a new one is established.
b
If no error history snapshot exists, a new one is created.

The error history directory is defined in table 236.

Table 236 — Error history directory

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • T10 VENDOR IDENTIFICATION
7 (LSB)
8 VERSION

9 Reserved EHS_RETRIEVED EHS_SOURCE CLR_SUP

10
•• • Reserved
29
30 (MSB)
DIRECTORY LENGTH (n-31)
31 (LSB)
Error history directory list
32
Error history directory entry
•• •
(see table 239) [first]
39
••
•
n-7
Error history directory entry
•• •
(see table 239) [last]
n

420 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The T10 VENDOR IDENTIFICATION field contains eight bytes of left-aligned ASCII data (see 4.3.1) identifying the
manufacturer of the logical unit. The T10 vendor identification shall be one assigned by INCITS. A list of
assigned T10 vendor identifications is in Annex G and on the T10 web site (http://www.t10.org).

NOTE 31 - The T10 VENDOR IDENTIFICATION field may contain a different value than the VENDOR IDENTIFICATION
field in the standard INQUIRY data (see 6.6.2) (e.g., this field may indicate a disk drive component
manufacturer while the standard INQUIRY data indicates the original equipment manufacturer).

The VERSION field indicates the version and format of the vendor specific error history. The VERSION field is
assigned by the manufacturer indicated in the T10 VENDOR IDENTIFICATION field.

The error history retrieved (EHS_RETRIEVED) field (see table 237) indicates whether a clear error history device
server action has been requested for the error history snapshot. EHS_RETRIEVED field shall be set to 00b or
10b when the error history snapshot is created.

Table 237 — EHS_RETRIEVED field

Code Description
00b No information
01b The error history I_T nexus has requested buffer ID FEh (i.e., clear
error history I_T nexus) or buffer ID FFh (i.e., clear error history I_T
nexus and release snapshot) for the current error history snapshot.
10b An error history I_T nexus has not requested buffer ID FEh (i.e., clear
error history I_T nexus) or buffer ID FFh (i.e., clear error history I_T
nexus and release snapshot) for the current error history snapshot.
11b Reserved

The error history source (EHS_SOURCE) field (see table 238) indicates the source of the error history snapshot.

Table 238 — EHS_SOURCE field

Code Description
00b The error history snapshot was created by the device server and was not created due to
processing a READ BUFFER command.
01b Error history snapshot was created due to processing of the current READ BUFFER command
10b Error history snapshot was created due to processing of a previous READ BUFFER command
11b Reserved

A clear support ( CLR _SUP ) bit set to one indicates that the CLR bit is supported in the WRITE BUFFER
command download error history mode (see 6.49.12). A CLR_SUP bit set to zero indicates that the CLR bit is
not supported.

The DIRECTORY LENGTH field indicates the number of bytes that follow in the error history directory list. This
value shall not be altered even if the allocation length is not sufficient to transfer the entire error history
directory list.

Working Draft SCSI Primary Commands - 4 (SPC-4) 421

T10/BSR INCITS 513 Revision 37 17 May 2014

The error history directory list contains an error history directory entry (see table 239) for each supported
buffer ID in the range of 00h to EFh. The first entry shall be for buffer ID 00h and the entries shall be in order
of ascending buffer IDs. The supported buffer IDs are not required to be contiguous. There shall not be any
entries for buffer IDs greater than or equal to F0h.

Table 239 — Error history directory entry

Bit
7 6 5 4 3 2 1 0
Byte
0 SUPPORTED BUFFER ID

1
•• • Reserved
3
4 (MSB)
•• • MAXIMUM AVAILABLE LENGTH
7 (LSB)

The SUPPORTED BUFFER ID field indicates the error history buffer ID associated with this entry.

The MAXIMUM AVAILABLE LENGTH field indicates the maximum number of data bytes contained in the buffer
indicated by the SUPPORTED BUFFER ID field. The actual number of bytes available for transfer may be smaller.

6.18.7.3 Error history data buffer

Unless an error is encountered, the device server shall return parameter data that contains error history in a
vendor specific format from the error history snapshot from the specified buffer at the specified buffer offset.

If the device server receives a READ BUFFER command with the MODE field set to 1Ch from the established
error history I_T nexus and the BUFFER ID field is set to a value that the error history directory (see 6.18.7.2)
shows as not supported, then the device server shall terminate the command with CHECK CONDITION
status with the sense key set to ILLEGAL REQUEST and the additional sense code set to INVALID FIELD IN
CDB.

If the value in the BUFFER OFFSET field is not supported, the device server shall terminate the command with
CHECK CONDITION status with the sense key set to ILLEGAL REQUEST and the additional sense code set
to INVALID FIELD IN CDB.

The amount of error history in the specified buffer shall be less than or equal to the number of bytes indicated
by the MAXIMUM AVAILABLE LENGTH field in the error history directory (see 6.18.7.2).

6.18.7.4 Clear error history I_T nexus

If the BUFFER ID field is set to FEh, the device server shall:

a) clear the error history I_T nexus, if any; and

b) not transfer any data.

6.18.7.5 Clear error history I_T nexus and release snapshot

If the BUFFER ID field is set to FFh, the device server shall:

a) clear the error history I_T nexus, if any,

422 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

b) release the error history snapshot, if any; and

c) not transfer any data.

6.19 READ MEDIA SERIAL NUMBER command

The READ MEDIA SERIAL NUMBER command (see table 240) requests the device server to return the
current media serial number. This command uses the SERVICE ACTION IN(12) CDB format (see 4.2.2.3.5).

Table 240 — READ MEDIA SERIAL NUMBER command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (ABh)
1 Reserved SERVICE ACTION (01h)
2
•• • Reserved
5
6 (MSB)
•• • ALLOCATION LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 240 for the READ MEDIA
SERIAL NUMBER command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 240 for the READ MEDIA
SERIAL NUMBER command.

The ALLOCATION LENGTH field is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

The READ MEDIA SERIAL NUMBER parameter data format is shown in table 241.

Table 241 — READ MEDIA SERIAL NUMBER parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • MEDIA SERIAL NUMBER LENGTH ((4n)-4)
3 (LSB)
4
•• •
MEDIA SERIAL NUMBER
(4n)-
1

Working Draft SCSI Primary Commands - 4 (SPC-4) 423

T10/BSR INCITS 513 Revision 37 17 May 2014

The MEDIA SERIAL NUMBER LENGTH field shall contain the number of bytes in the MEDIA SERIAL NUMBER field.
The media serial number length shall be a multiple of four. The contents of the MEDIA SERIAL NUMBER LENGTH
field are not altered based on the allocation length (see 4.2.5.6).

The MEDIA SERIAL NUMBER field shall contain the vendor specific serial number of the media currently installed.
If the number of bytes in the vendor specific serial number is not a multiple of four, then up to three bytes
containing zero shall be appended to the highest numbered bytes of the MEDIA SERIAL NUMBER field.

If the media serial number is not available (e.g., the currently installed media has no valid media serial
number), then the MEDIA SERIAL NUMBER LENGTH field shall be set to zero.

If the media serial number is not accessible as a result of there is no media present, the device server shall
terminate the command with CHECK CONDITION status, with the sense key set to NOT READY, and the
additional sense code set to MEDIUM NOT PRESENT.

6.20 RECEIVE COPY DATA(LID4) command

The RECEIVE COPY DATA(LID4) command (see table 242) is a third-party copy command (see 5.16.3) that
requests the copy manager to return the held data (see 5.16.4.5), if any, for the copy operation (see 5.16.4.3)
specified by the LIST IDENTIFIER field (see 5.16.4.2) in the CDB.

Table 242 — RECEIVE COPY DATA(LID4) command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (84h)
1 Reserved SERVICE ACTION (06h)
2 (MSB)
•• • LIST IDENTIFIER
5 (LSB)
6
•• • Reserved
9
10 (MSB)
•• • ALLOCATION LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 242 for the RECEIVE COPY
DATA(LID4) command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 242 for the RECEIVE COPY
DATA(LID4) command.

The LIST IDENTIFIER field is defined in 5.16.4.2 and 6.4.3.2, and specifies the copy operation (see 5.16.4.3)
about which information is to be transferred. The receive command shall return information from the copy
operation that was received on the same I_T nexus with a list identifier that matches the list identifier specified

424 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

in the RECEIVE COPY RESULTS command's CDB. If no copy operation known to the copy manager has a
matching list identifier, the copy manager shall terminate the RECEIVE COPY DATA(LID4) command with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set
to INVALID FIELD IN CDB.

The ALLOCATION LENGTH field is defined in 4.2.5.6. The actual length of the parameter data is available in the
AVAILABLE DATA field in the parameter data.

The CONTROL byte is defined in SAM-5.

Working Draft SCSI Primary Commands - 4 (SPC-4) 425

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 243 shows the format of the parameter data for the RECEIVE COPY DATA(LID4) command.

Table 243 — Parameter data for the RECEIVE COPY DATA(LID4) command

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • AVAILABLE DATA (n-3)
3 (LSB)
4 Reserved RESPONSE TO SERVICE ACTION

5 HDD COPY OPERATION STATUS

6 (MSB)
OPERATION COUNTER
7 (LSB)
8 (MSB)
•• • ESTIMATED STATUS UPDATE DELAY
11 (LSB)
12 EXTENDED COPY COMPLETION STATUS

13 LENGTH OF THE SENSE DATA FIELD (X-31)

14 SENSE DATA LENGTH

15 TRANSFER COUNT UNITS

16 (MSB)
•• • TRANSFER COUNT
23 (LSB)
24 (MSB)
SEGMENTS PROCESSED
25 (LSB)
26
•• • Reserved
31
32
•• • SENSE DATA
x
x+1 (MSB)
•• • HELD DATA LENGTH (n-(x+4))
x+4 (LSB)
x+5
•• • HELD DATA
n

The copy manager shall not discard the data returned by a RECEIVE COPY DATA(LID4) command in
response to an ABORT TASK task management function (see SAM-5) or a COPY OPERATION ABORT
command (see 6.3).

The AVAILABLE DATA field, RESPONSE TO SERVICE ACTION field, COPY OPERATION STATUS field, OPERATION
COUNTER field, ESTIMATED STATUS UPDATE DELAY field, EXTENDED COPY COMPLETION STATUS field, LENGTH OF
THE SENSE DATA FIELD field, SENSE DATA LENGTH field, TRANSFER COUNT UNITS field, TRANSFER COUNT field,

426 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

SEGMENTS PROCESSED field, and SENSE DATA field are defined in 6.24.

The held data discarded (HDD) bit indicates whether held data has been discarded as described in 5.16.4.5.

If the COPY OPERATION STATUS field is set to a value that table 252 (see 6.24) describes as meaning the
operation completed without errors, then the HELD DATA LENGTH field indicates the number of bytes that follow
in the HELD DATA field. If the COPY OPERATION STATUS field is not set to a value that table 252 describes as
meaning the operation completed without errors, then the HELD DATA LENGTH field shall be set to zero.

The HELD DATA field contains the held data (see 5.16.4.5) for the copy operation (see 5.16.4.3) specified by the
list identifier in the CDB (see 5.16.4.2). Unless the copy manager’s held data limit (see 5.16.4.5) is exceeded,
the first byte held (i.e., the oldest byte held) in response to the copy operation (e.g., the first segment
descriptor in the EXTENDED COPY parameter list prescribing the holding of data) is returned in the first byte
in the HELD DATA field. The last byte held (i.e., the newest byte held) in response to the copy operation (e.g.,
the last segment descriptor in the EXTENDED COPY parameter list prescribing the holding of data) is
returned in the last byte in the HELD DATA field.

6.21 RECEIVE COPY DATA(LID1) command

The RECEIVE COPY DATA(LID1) command (see table 244) is an SPC-3 compatible third-party copy
command (see 5.16.3) that requests the copy manager to return the held data (see 5.16.4.5), if any, for the
copy operation (see 5.16.4.3) specified by the LIST IDENTIFIER field (see 5.16.4.2) in the CDB.

Table 244 — RECEIVE COPY DATA(LID1) command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (84h)
1 Reserved SERVICE ACTION (01h)
2 LIST IDENTIFIER

3
•• • Reserved
9
10 (MSB)
•• • ALLOCATION LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 244 for the RECEIVE COPY
DATA(LID1) command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 244 for the RECEIVE COPY
DATA(LID1) command.

The LIST IDENTIFIER field and ALLOCATION LENGTH field are defined in 6.20.

Working Draft SCSI Primary Commands - 4 (SPC-4) 427

T10/BSR INCITS 513 Revision 37 17 May 2014

The copy manager shall terminate the RECEIVE COPY DATA(LID1) command with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN
CDB if:

a) no copy operation known to the copy manager has a list identifier that matches the LIST IDENTIFIER
field in the CDB; or
b) if the LIST IDENTIFIER field in the CDB specifies a copy operation that still is being processed by the
copy manager.

The CONTROL byte is defined in SAM-5.

Table 245 shows the format of the parameter data for the RECEIVE COPY DATA(LID1) command.

Table 245 — Parameter data for the RECEIVE COPY DATA(LID1) command

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • AVAILABLE DATA (n-3)
3 (LSB)
4
•• • HELD DATA
n

The AVAILABLE DATA field shall contain the number of bytes of held data that follow. The contents of the
AVAILABLE DATA field are not altered based on the allocation length (see 4.2.5.6).

The HELD DATA field is defined in 6.20.

428 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.22 RECEIVE COPY OPERATING PARAMETERS command

The RECEIVE COPY OPERATING PARAMETERS command (see table 246) is an SPC-3 compatible
third-party copy command (see 5.16.3) that requests the copy manager to return the operating parameters for
the EXTENDED COPY command. The Third-party Copy VPD page (see 7.8.17) provides the same
information as the RECEIVE COPY OPERATING PARAMETERS command and additional copy manager
support information.

Table 246 — RECEIVE COPY OPERATING PARAMETERS command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (84h)
1 Reserved SERVICE ACTION (03h)
2
•• • Reserved
9
10 (MSB)
•• • ALLOCATION LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 246 for the RECEIVE COPY
OPERATING PARAMETERS command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 246 for the RECEIVE COPY
OPERATING PARAMETERS command.

The CONTROL byte is defined in SAM-5.

Table 247 shows the format of the parameter data for the RECEIVE COPY OPERATING PARAMETERS
command. If the Third-party Copy VPD page (see 7.8.17) is supported, the values in the RECEIVE COPY
OPERATING PARAMETERS parameter data fields shall be the same as the values in the equivalent fields in
the Third-party Copy VPD page.

Table 247 — Parameter data for the RECEIVE COPY OPERATING PARAMETERS command (part 1 of 2)

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • AVAILABLE DATA (n-3)
3 (LSB)
4 Reserved SNLID

5
6 Reserved
7

Working Draft SCSI Primary Commands - 4 (SPC-4) 429

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 247 — Parameter data for the RECEIVE COPY OPERATING PARAMETERS command (part 2 of 2)

Bit
7 6 5 4 3 2 1 0
Byte
8 (MSB)
MAXIMUM CSCD DESCRIPTOR COUNT
9 (LSB)
10 (MSB)
MAXIMUM SEGMENT DESCRIPTOR COUNT
11 (LSB)
12 (MSB)
•• • MAXIMUM DESCRIPTOR LIST LENGTH
15 (LSB)
16 (MSB)
•• • MAXIMUM SEGMENT LENGTH
19 (LSB)
20 (MSB)
•• • MAXIMUM INLINE DATA LENGTH
23 (LSB)
24 (MSB)
•• • HELD DATA LIMIT
27 (LSB)
28 (MSB)
•• • MAXIMUM STREAM DEVICE TRANSFER SIZE
31 (LSB)
32
Reserved
33
34 (MSB)
TOTAL CONCURRENT COPIES
35 (LSB)
36 MAXIMUM CONCURRENT COPIES

37 DATA SEGMENT GRANULARITY (log 2)

38 INLINE DATA GRANULARITY (log 2)
39 HELD DATA GRANULARITY (log 2)
40
41 Reserved
42
43 IMPLEMENTED DESCRIPTOR LIST LENGTH (n-43)
44
List of implemented descriptor type codes
•• •
(ordered)
n

The AVAILABLE DATA field shall contain the number of bytes following the AVAILABLE DATA field in the parameter
data. The contents of the AVAILABLE DATA field are not altered based on the allocation length (see 4.2.5.6).

430 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

A supports no list identifier (SNLID) bit set to one indicates the copy manager supports an EXTENDED COPY
command parameter list in which the LIST ID USAGE field is set to 11b and the LIST IDENTIFIER field is set to zero
as described in 6.4.3.2. A SNLID bit set to zero indicates the copy manager does not support an EXTENDED
COPY command parameter list (see 5.16.7.1) in which the LIST ID USAGE field is set to 11b.

The MAXIMUM CSCD DESCRIPTOR COUNT field indicates the maximum number of CSCD descriptors that the
copy manager allows in an EXTENDED COPY command parameter list (see 5.16.7.1).

The MAXIMUM SEGMENT COUNT field indicates the maximum number of segment descriptors that the copy
manager allows in an EXTENDED COPY command parameter list (see 5.16.7.1).

The MAXIMUM DESCRIPTOR LIST LENGTH field indicates the maximum length, in bytes, of the CSCD descriptor
list and segment descriptor list that the copy manager allows in an EXTENDED COPY command parameter
list (see 5.16.7.1).

The MAXIMUM SEGMENT LENGTH field indicates the length, in bytes, of the largest amount of data that the copy
manager supports writing via a single segment. Bytes introduced as a result of the PAD bit being set to one
(see 5.16.7.2) are not counted towards this limit. A value of zero indicates that the copy manager places no
limits on the amount of data written by a single segment.

The MAXIMUM INLINE DATA LENGTH field indicates the length, in bytes, of the largest amount of inline data (see
6.4.3.6) that the copy manager supports in an EXTENDED COPY parameter list (see 5.16.7.1). The MAXIMUM
INLINE DATA LENGTH field shall be set to zero if the copy manager does not support descriptor type code 04h
(see 6.4.6.6).

The HELD DATA LIMIT field indicates the length, in bytes, of the minimum amount of data the copy manager
shall hold for return to the application client as described in 5.16.4.5.

If the SNLID bit is set to one, the TOTAL CONCURRENT COPIES field indicates the maximum number of
EXTENDED COPY commands with the LIST ID USAGE field set to 00b, 10b, or 11b that are supported for
concurrent processing by the copy manager. If the SNLID bit is set to zero, the TOTAL CONCURRENT COPIES field
shall be set to zero.

The MAXIMUM CONCURRENT COPIES field indicates the maximum number of EXTENDED COPY commands with
the LIST ID USAGE field set to 00b or 10b that are supported for concurrent processing by the copy manager. If
the SNLID bit is set to one, the contents of the TOTAL CONCURRENT COPIES field shall be greater than or equal to
the contents of the MAXIMUM CONCURRENT COPIES field.

Each EXTENDED COPY command with the LIST ID USAGE field set to 00b or 10b reduces the number of
EXTENDED COPY commands with the LIST ID USAGE field set to 11b that may be processed concurrently.
However, the converse may not be true (e.g., when the number of outstanding EXTENDED COPY commands
with the LIST ID USAGE field set to 11b exceeds the difference between the total concurrent copies and
maximum concurrent copies).

The DATA SEGMENT GRANULARITY field indicates the length of the smallest data block that the copy manager
permits in a non-inline segment descriptor (i.e., segment descriptors with type codes other than 04h). The
amount of data transferred by a single segment descriptor shall be a multiple of the granularity. The DATA
SEGMENT GRANULARITY value is expressed as a power of two. Bytes introduced as a result of the PAD bit being
set to one (see 5.16.7.2) are not counted towards the data length granularity.

The INLINE DATA GRANULARITY field indicates the length of the of the smallest block of inline data that the copy
manager permits being written by a segment descriptor containing the 04h descriptor type code (see 6.4.6.6).
The amount of inline data written by a single segment descriptor shall be a multiple of the granularity. The
INLINE DATA GRANULARITY value is expressed as a power of two. Bytes introduced as a result of the PAD bit

Working Draft SCSI Primary Commands - 4 (SPC-4) 431

T10/BSR INCITS 513 Revision 37 17 May 2014

being set to one (see 5.16.7.2) are not counted towards the length granularity.

If the copy manager encounters a data or inline segment descriptor that violates either the data segment
granularity or the inline data granularity, then the copy manager shall terminate the copy operation (see
5.16.4.3) with CHECK CONDITION status, with the sense key set to COPY ABORTED, and the additional
sense code set to COPY SEGMENT GRANULARITY VIOLATION.

The HELD DATA GRANULARITY field indicates the length of the smallest block of held data (see 5.16.4.5) that the
copy manager shall transfer to the application client in response to a RECEIVE COPY DATA(LID4) command
(see 6.20) or a RECEIVE COPY DATA(LID1) command (see 6.21). The amount of data held by the copy
manager in response to any one function (e.g., one segment descriptor (see 6.4.6)) in a copy operation (see
5.16.4.3) shall be a multiple of this granularity. The HELD DATA GRANULARITY value is expressed as a power of
two.

The MAXIMUM STREAM DEVICE TRANSFER SIZE field indicates the maximum transfer size, in bytes, supported for
stream devices.

The IMPLEMENTED DESCRIPTOR LIST LENGTH field indicates the length, in bytes, of the list of implemented
descriptor type codes.

The list of implemented descriptor type codes contains one byte for each segment or CSCD DESCRIPTOR TYPE
CODE value (see 6.4.5) supported by the copy manager, with a unique supported DESCRIPTOR TYPE CODE value
in each byte. The DESCRIPTOR TYPE CODE values shall appear in the list in ascending numerical order.

6.23 RECEIVE COPY FAILURE DETAILS(LID1) command

The RECEIVE COPY FAILURE DETAILS(LID1) command (see table 248) is an SPC-3 compatible third-party
copy command (see 5.16.3) that requests the copy manager to return details of the segment processing
failure, if any, that caused termination of the EXTENDED COPY(LID1) command specified by the LIST
IDENTIFIER field in the CDB.

Table 248 — RECEIVE COPY FAILURE DETAILS(LID1) command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (84h)
1 Reserved SERVICE ACTION (04h)
2 LIST IDENTIFIER

3
•• • Reserved
9
10 (MSB)
•• • ALLOCATION LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 248 for the RECEIVE COPY
FAILURE DETAILS(LID1) command.

432 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 248 for the RECEIVE COPY
FAILURE DETAILS(LID1) command.

The LIST IDENTIFIER field and ALLOCATION LENGTH field are defined in 6.20.

The copy manager shall terminate the RECEIVE COPY FAILURE DETAILS(LID1) command with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
INVALID FIELD IN CDB if:

a) no EXTENDED COPY(LID1) command known to the copy manager has a list identifier that matches
the LIST IDENTIFIER field in the CDB; or
b) if the LIST IDENTIFIER field in the CDB specifies an EXTENDED COPY(LID1) command that still is
being processed by the copy manager.

The CONTROL byte is defined in SAM-5.

Table 249 shows the format of the parameter data for the RECEIVE COPY FAILURE DETAILS(LID1)
command.

Table 249 — Parameter data for the RECEIVE COPY FAILURE DETAILS(LID1) command

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • AVAILABLE DATA (n-3)
3 (LSB)
4
•• • Reserved
55
56 EXTENDED COPY COMMAND STATUS

57 Reserved
58 (MSB)
SENSE DATA LENGTH (n-59)
59 (LSB)
60
•• • SENSE DATA
n

If processing of an EXTENDED COPY(LID1) command is aborted and processing of a segment descriptor is

incomplete, then the copy manager shall preserve details about the progress in processing of that descriptor.
These details enable the application client to obtain information it needs to determine the state in which
CSCDs (e.g., stream devices) have been positioned by incomplete processing.

The application client should issue a RECEIVE COPY FAILURE DETAILS(LID1) command as soon as
possible after the failure of the EXTENDED COPY(LID1) command to ensure that the information is not
discarded by the copy manager. The copy manager shall discard the failed segment details:

a) after all failed segment details held for a specific EXTENDED COPY(LID1) command have been
successfully transferred to the application client;
b) if a RECEIVE COPY FAILURE DETAILS(LID1) command has been received on the same I_T nexus
with a matching list identifier, with the ALLOCATION LENGTH field set to zero;

Working Draft SCSI Primary Commands - 4 (SPC-4) 433

T10/BSR INCITS 513 Revision 37 17 May 2014

c) if another EXTENDED COPY(LID1) command is received on the same I_T nexus using the same list
identifier;
d) if the copy manager detects a logical unit reset condition or I_T nexus loss condition (see SAM-5); or
e) if the copy manager requires the resources used to preserve the data.

The AVAILABLE DATA field shall contain the number of bytes of failed segment details that follow. If no failed
segment details data is available for the specified list identifier then the AVAILABLE DATA field shall be set to
zero and no data beyond the AVAILABLE DATA field shall be transferred. The contents of the AVAILABLE DATA
field are not altered based on the allocation length (see 4.2.5.6).

The COPY COMMAND STATUS field contains the status value that was returned for the EXTENDED COPY(LID1)
command specified by the LIST IDENTIFIER field in the CDB.

The SENSE DATA LENGTH field indicates how many bytes of sense data are present in the SENSE DATA field.

The SENSE DATA field contains a copy of the sense data that the copy manager prepared as part of terminating
the EXTENDED COPY(LID1) command indicated by the list identifier with CHECK CONDITION status.

6.24 RECEIVE COPY STATUS(LID4) command

The RECEIVE COPY STATUS(LID4) command (see table 250) is a third-party copy command (see 5.16.3)
that requests the copy manager to return the status information (see 5.16.4.4) for the copy operation (see
5.16.4.3) specified by the LIST IDENTIFIER field (see 5.16.4.2) in the CDB.

Table 250 — RECEIVE COPY STATUS(LID4) command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (84h)
1 Reserved SERVICE ACTION (05h)
2 (MSB)
•• • LIST IDENTIFIER
5 (LSB)
6
•• • Reserved
9
10 (MSB)
•• • ALLOCATION LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 250 for the RECEIVE COPY
STATUS(LID4) command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 250 for the RECEIVE COPY
STATUS(LID4) command.

434 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The LIST IDENTIFIER field and ALLOCATION LENGTH field are defined in 6.20.

If no copy operation known to the copy manager has a list identifier that matches the contents of the LIST
IDENTIFIER field, then the copy manager shall terminate the RECEIVE COPY STATUS(LID4) command with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set
to INVALID FIELD IN CDB.

The CONTROL byte is defined in SAM-5.

Table 251 shows the format of the parameter data for the RECEIVE COPY STATUS(LID4) command.

Table 251 — Parameter data for the RECEIVE COPY STATUS(LID4) command

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • AVAILABLE DATA (n-3)
3 (LSB)
4 Reserved RESPONSE TO SERVICE ACTION

5 Reserved COPY OPERATION STATUS

6 (MSB)
OPERATION COUNTER
7 (LSB)
8 (MSB)
•• • ESTIMATED STATUS UPDATE DELAY
11 (LSB)
12 EXTENDED COPY COMPLETION STATUS

13 LENGTH OF THE SENSE DATA FIELD (X-31)

14 SENSE DATA LENGTH

15 TRANSFER COUNT UNITS

16 (MSB)
•• • TRANSFER COUNT
23 (LSB)
24 (MSB)
SEGMENTS PROCESSED
25 (LSB)
26
•• • Reserved
31
32
•• • SENSE DATA
x

The AVAILABLE DATA field shall contain the number of bytes that follow in the parameter data. The contents of
the AVAILABLE DATA field are not altered based on the allocation length (see 4.2.5.6).

The RESPONSE TO SERVICE ACTION field indicates the value in the SERVICE ACTION field of the third-party copy
command (see 5.16.3) specified by the LIST IDENTIFIER field in the CDB.

Working Draft SCSI Primary Commands - 4 (SPC-4) 435

T10/BSR INCITS 513 Revision 37 17 May 2014

The COPY OPERATION STATUS field indicates the status of the copy operation (see 5.16.4.3) specified by the
field in the CDB as defined in table 252.
LIST IDENTIFIER

Table 252 — COPY OPERATION STATUS field

Operation
completed
Code Meaning without errors
01h Operation completed without errors Yes
02h Operation completed with errors No
a
03h Operation completed without errors but with partial ROD token Yes
usage (e.g., the residual is negative (see SBC-3))
04h Operation completed without errors but with residual data b Yes
c
10h Operation in progress, foreground or background unknown No
11h Operation in progress in foreground (see 5.16.4.3) No
12h Operation in progress in background (see 5.16.4.3) No
60h Operation terminated (e.g., by the preemption of a persistent No
reservation (see 5.9.11.5) or by a COPY OPERATION ABORT
command (see 6.3))
all others Reserved
a
If the third-party copy command that originated the copy operation is an EXTENDED COPY
command, then the COPY OPERATION STATUS field shall never be set to 03h.
b
The copy manager has determined that the application client should verify that all requested
data transfers have been performed.
c Codes 11h and 12h should be used instead of this code whenever possible.

The OPERATION COUNTER field contains a wrapping counter of the number of SCSI commands, or equivalent,
that the copy manager has sent to a copy source or copy destination as part of processing the copy operation
(see 5.16.4.3) specified by the LIST IDENTIFIER field in the CDB, and for which the copy manager has received
one of the following completion status values:

a) GOOD;
b) CONDITION MET; or
c) CHECK CONDITION with the sense key set to RECOVERED ERROR.

The ESTIMATED STATUS UPDATE DELAY field indicates the number of milliseconds that the copy manager
recommends that the application client wait before sending another RECEIVE COPY STATUS(LID4)
command on the same I_T nexus with the same list identifier. If a RECEIVE COPY STATUS(LID4) command
is received sooner than the indicated time, the copy manager may return the same parameter data that was
returned in response to the previous RECEIVE COPY STATUS(LID4) command. If the COPY OPERATION
STATUS field is set to 01h, 02h, 03h, 04h, or 60h, then the ESTIMATED STATUS UPDATE DELAY field shall be set to
FFFF FFFEh. If the ESTIMATED STATUS UPDATE DELAY field is set to FFFF FFFFh, then the copy manager is
unable to recommend a delay interval.

436 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The EXTENDED COPY COMPLETION STATUS field indicates the status code (see SAM-5), if any, established for
the completed copy operation (see 5.16.4.3) specified by the LIST IDENTIFIER field and is affected by the
contents of the COPY OPERATION STATUS field as shown in table 253. If the IMMED bit, if any, (see 5.16.4.3) is set
to one in the third-party copy command that originated the copy operation, then the contents of the EXTENDED
COPY COMPLETION STATUS field may be different than the status returned by the originating third-party copy
command.

Table 253 — EXTENDED COPY COMPLETION STATUS field contents based on COPY OPERATION STATUS field

COPY OPERATION
STATUS field contents EXTENDED COPY COMPLETION STATUS field contents
10h, 11h, or 12h The EXTENDED COPY COMPLETION STATUS field is reserved.
01h, 02h, 03h, or 04h The EXTENDED COPY COMPLETION STATUS field indicates the status code (see
SAM-5) established for the completed copy operation specified by the LIST
IDENTIFIER field.

60h The EXTENDED COPY COMPLETION STATUS field shall be set to TASK
ABORTED (see SAM-5).

The LENGTH OF THE SENSE DATA FIELD field indicates the number of bytes in the SENSE DATA field. The LENGTH
field shall be set to zero or a multiple of four.
OF THE SENSE DATA FIELD

If the COPY OPERATION STATUS field is set to 10h, 11h, 12h, or 60h, then the SENSE DATA LENGTH field shall be
set to zero. If the COPY OPERATION STATUS field is set to 01h, 02h, 03h, or 04h, then the SENSE DATA LENGTH
field indicates the number of bytes in the SENSE DATA field that contain sense data. The value in the SENSE
DATA LENGTH field shall be less than or equal to the value in the LENGTH OF THE SENSE DATA FIELD field (e.g.,
the SENSE DATA field may contain pad bytes that are counted in the LENGTH OF THE SENSE DATA FIELD field but
not in the SENSE DATA LENGTH field).

The TRANSFER COUNT UNITS field indicates the units for the TRANSFER COUNT field as shown in table 254.

Table 254 — COPY STATUS TRANSFER COUNT UNITS field

Multiplier to convert
Code Meaning a TRANSFER COUNT field to bytes

00h Bytes 1
01h Kibibytes 210 (i.e., 1 024)
02h Mebibytes 220
03h Gibibytes 230
04h Tebibytes 240
05h Pebibytes 250
06h Exbibytes 260
F1h n/a logical block length of copy destination
all others Reserved
a See 3.5.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 437

T10/BSR INCITS 513 Revision 37 17 May 2014

The TRANSFER COUNT field indicates the amount of data written to a copy destination for the copy operation
(see 5.16.4.3) specified by the LIST IDENTIFIER field prior to the time at which the copy manager processed the
RECEIVE COPY STATUS(LID4) command. If data has been written to the copy destination in an order other
than what the command specified (e.g., if concurrent processing of multiple segment descriptors has resulted
in some data being written out of order), then the TRANSFER COUNT field shall indicate only those bytes that
have been written in strict order conformance with what the command specified.

The SEGMENTS PROCESSED field indicates the number of segments the copy manager has processed for the
copy operation (see 5.16.4.3) specified by the LIST IDENTIFIER field including the segment currently being
processed. The SEGMENTS PROCESSED field shall be set to zero if:

a) the copy manager has not yet begun processing segment descriptors; or
b) the RESPONSE TO SERVICE ACTION field indicates a third-party copy command that does not support
segment descriptors.

6.25 RECEIVE COPY STATUS(LID1) command

The RECEIVE COPY STATUS(LID1) command (see table 255) is an SPC-3 compatible third-party copy
command (see 5.16.3) that requests the copy manager to return the status information for the copy operation
(see 5.16.4.3) specified by the LIST IDENTIFIER field (see 5.16.4.2) in the CDB.

Table 255 — RECEIVE COPY STATUS(LID1) command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (84h)
1 Reserved SERVICE ACTION (00h)
2 LIST IDENTIFIER

3
•• • Reserved
9
10 (MSB)
•• • ALLOCATION LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 255 for the RECEIVE COPY
STATUS(LID1) command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 255 for the RECEIVE COPY
STATUS(LID1) command.

The LIST IDENTIFIER field and ALLOCATION LENGTH field are defined in 6.20.

If no copy operation known to the copy manager has a list identifier that matches the contents of the LIST
IDENTIFIER field, then the copy manager shall terminate the RECEIVE COPY STATUS(LID1) command with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set
to INVALID FIELD IN CDB.

438 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The CONTROL byte is defined in SAM-5.

Table 256 shows the format of the parameter data for the RECEIVE COPY STATUS(LID1) command.

Table 256 — Parameter data for the RECEIVE COPY STATUS(LID1) command

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • AVAILABLE DATA (00000008h)
3 (LSB)
4 HDD COPY COMMAND STATUS

5 (MSB)
SEGMENTS PROCESSED
6 (LSB)
7 TRANSFER COUNT UNITS

8 (MSB)
•• • TRANSFER COUNT
11 (LSB)

After the completion of a copy operation (see 5.16.4.3), the copy manager shall preserve all data returned by
the RECEIVE COPY STATUS(LID1) command for a vendor specific period of time. The copy manager shall
discard the RECEIVE COPY STATUS(LID1) command parameter data if:

a) a RECEIVE COPY STATUS(LID1) command is received on the same I_T nexus with a matching list
identifier;
b) another third-party copy command that originates a copy operation (see table 108 in 5.16.3) is
received on the same I_T nexus and the list identifier matches the list identifier associated with the
data preserved for the RECEIVE COPY STATUS(LID1) command;
c) the copy manager detects a logical unit reset condition or I_T nexus loss condition (see SAM-5); or
d) the copy manager requires the resources used to preserve the data.

The AVAILABLE DATA field shall contain the number of bytes that follow in the parameter data, and shall be set
as shown in table 256 for the RECEIVE COPY STATUS(LID1) command. The contents of the AVAILABLE DATA
field are not altered based on the allocation length (see 4.2.5.6).

The held data discarded (HDD) bit indicates whether held data has been discarded as described in 5.16.4.5.

The COPY COMMAND STATUS field is set to the current status of the third-party copy command (see 5.16.3)
specified by the LIST IDENTIFIER field in the CDB as defined in table 257.

Table 257 — COPY COMMAND STATUS field

Code Meaning
00h Operation in progress
01h Operation completed without errors
02h Operation completed with errors
03h to 7Fh Reserved

The SEGMENTS PROCESSED field, TRANSFER COUNT UNITS field, and TRANSFER COUNT field are defined in 6.24.

Working Draft SCSI Primary Commands - 4 (SPC-4) 439

T10/BSR INCITS 513 Revision 37 17 May 2014

6.26 RECEIVE CREDENTIAL command

6.26.1 RECEIVE CREDENTIAL command description

6.26.1.1 Overview

The RECEIVE CREDENTIAL command (see table 258) requests a security manager device server (e.g., a
CbCS management device server (see 5.13.6.7.3)) to return a credential to a secure CDB originator (see
5.13.6.2) (e.g., for use in the CbCS extension descriptor (see 5.13.6.7.16) of a CDB).

Table 258 — RECEIVE CREDENTIAL command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (7Fh)
1 CONTROL

2
•• • Reserved
6
7 ADDITIONAL CDB LENGTH (n-7)
8 (MSB)
SERVICE ACTION (1800h)
9 (LSB)
10 (MSB)
ALLOCATION LENGTH
11 (LSB)
12 (MSB)
•• • AC_SAI
15 (LSB)
16
•• • ENCRYPTED REQUEST DESCRIPTOR
n

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 258 for the RECEIVE
CREDENTIAL command.

The ADDITIONAL CDB LENGTH field is defined in 4.2.3.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 258 for the RECEIVE
CREDENTIAL command.

The ALLOCATION LENGTH field is defined in 4.2.5.6.

The AC_SAI field is set to the value of the AC_SAI SA parameter (see 5.13.2.2) for the SA to be used to
encrypt the parameter data as described in 6.26.2.1.

The ENCRYPTED REQUEST DESCRIPTOR field shall contain an ESP-SCSI CDB descriptor (see 5.13.7.4). Before
encryption and after decryption, the UNENCRYPTED BYTES field (see 5.13.7.3) that are used to compute the

440 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

ENCRYPTED OR AUTHENTICATED DATA field (see 5.13.7.4) contents shall have the format shown in table 259.

Table 259 — RECEIVE CREDENTIAL command unencrypted bytes format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
CREDENTIAL REQUEST TYPE
1 (LSB)
2
•• • CREDENTIAL REQUEST DESCRIPTOR
n

The CREDENTIAL REQUEST TYPE field (see table 260) specifies type of credential being requested and the
format of the CREDENTIAL REQUEST DESCRIPTOR field.

Table 260 — CREDENTIAL REQUEST TYPE field

Code Description Reference

0001h CbCS logical unit 6.26.1.2
0002h CbCS logical unit and volume 6.26.1.3
all other codes Reserved

The CREDENTIAL REQUEST DESCRIPTOR field specifies information that describes the requested credential (see
table 260).

The CONTROL byte is defined in SAM-5.

If return of the requested credential is not permitted, the device server shall terminate the command with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set
to ACCESS DENIED - NO ACCESS RIGHTS.

The DS_SAI field in the ENCRYPTED REQUEST DESCRIPTOR field is set to the value of the DS_SAI SA parameter
(see 5.13.2.2) for the SA to be used to encrypt the unencrypted bytes and the parameter data as described.

If the device server is not maintaining an SA with an AC_SAI SA parameter that matches the AC_SAI field
contents and a DS_SAI SA parameter that matches the DS_SAI field contents, then the device server shall
terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and
the additional sense code set to INVALID FIELD IN CDB.

If the device server is maintaining the SA specified by the AC_SAI field and the DS_SAI field, then the SA shall
be verified for use by this RECEIVE CREDENTIAL command as follows:

a) the USAGE_TYPE SA parameter (see 5.13.2.2) shall be verified to be equal to 82h (i.e., CbCS
authentication and credential encryption; and
b) the USAGE_DATA SA parameter (see 5.13.2.2) shall be verified not to contain an ALGORITHM
IDENTIFIER field (see 7.7.3.6) that is set to ENCR_NULL based on the contents the IKEv2-SCSI SAUT
Cryptographic Algorithm payload (see 7.7.3.5.14) for the ENCR algorithm type (see 7.7.3.6.2) during
creation of the SA (see 5.13.2.3).

Working Draft SCSI Primary Commands - 4 (SPC-4) 441

T10/BSR INCITS 513 Revision 37 17 May 2014

If any of these SA verifications fails, the device server shall terminate the command with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN
CDB.

6.26.1.2 CbCS logical unit credential request descriptor

If the CREDENTIAL REQUEST TYPE field is set to 0001h (i.e., CbCS logical unit), the format of the CREDENTIAL
REQUEST DESCRIPTOR field is as shown in table 261.

Table 261 — CbCS logical unit credential request descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • DESIGNATION DESCRIPTOR
19

The format of the DESIGNATION DESCRIPTOR field is defined in table 590 (see 7.8.6.1). The device server shall
terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and
the additional sense code set to INVALID FIELD IN CDB if any of the fields in the DESIGNATION DESCRIPTOR
field are set as follows:

a) the DESIGNATOR TYPE field is set to any value other than 3h (i.e., NAA);
b) the ASSOCIATION field is set to any value other than 00b (i.e., logical unit) or 10b (i.e., SCSI target
device); or
c) the DESIGNATOR LENGTH field is set to a value that is larger than 16.

6.26.1.3 CbCS logical unit and volume credential request descriptor

If the CREDENTIAL REQUEST TYPE field is set to 0002h (i.e., CbCS logical unit and volume), the format of the
CREDENTIAL REQUEST DESCRIPTOR field is as shown in table 262.

Table 262 — CbCS logical unit and volume credential request descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • DESIGNATION DESCRIPTOR
19
20
•• • MAM ATTRIBUTE
56

The format of the DESIGNATION DESCRIPTOR field is defined in table 590 (see 7.8.6.1). The device server shall
terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and
the additional sense code set to INVALID FIELD IN CDB if any of the fields in the DESIGNATION DESCRIPTOR
field are set as follows:

a) the DESIGNATOR TYPE field is set to any value other than 3h (i.e., NAA);
b) the ASSOCIATION field is set to any value other than 00b (i.e., logical unit) or 10b (i.e., SCSI target
device); or
c) the DESIGNATOR LENGTH field is set to a value that is larger than 16.

442 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The format of the MAM ATTRIBUTE field is defined in table 440 (see 7.4.1). If the ATTRIBUTE IDENTIFIER field in the
MAM ATTRIBUTE field is set to any value other than 0401h (i.e., MEDIUM SERIAL NUMBER), then the device
server shall terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

6.26.2 RECEIVE CREDENTIAL parameter data

6.26.2.1 RECEIVE CREDENTIAL parameter data encryption

The RECEIVE CREDENTIAL parameter data shall be one of the ESP-SCSI Data-In Buffer descriptors shown
in table 100 (see 5.13.7.5.1). The SA specified by the AC_SAI field and the DS_SAI field in the CDB shall be
used to construct the ESP-SCSI Data-In Buffer descriptor as described in 5.13.7.5.

Before processing the parameter data, the application client should validate and decrypt the ESP-SCSI
Data-In Buffer descriptor as described in 5.13.7.5. If any errors are detected by the validation and decryption
processing, the parameter data should be ignored.

6.26.2.2 RECEIVE CREDENTIAL decrypted parameter data

Before encryption and after decryption, the UNENCRYPTED BYTES field (see 5.13.7.3) that are used to compute
the ENCRYPTED OR AUTHENTICATED DATA field (see 5.13.7.5) contents shall contain a CbCS credential (see
table 263).

Table 263 — CbCS credential format

Bit
7 6 5 4 3 2 1 0
Byte
0 Reserved CREDENTIAL FORMAT (1h)
1 Reserved
2 (MSB)
CREDENTIAL LENGTH (n-3)
3 (LSB)
4 (MSB)
CAPABILITY LENGTH (k-5)
5 (LSB)
6
•• • CbCS capability descriptor (see 6.26.2.3)
k
k+1 (MSB)
•• • CAPABILITY KEY LENGTH (n-(k-4))
k+4 (LSB)
k+5
•• • CAPABILITY KEY
n

Working Draft SCSI Primary Commands - 4 (SPC-4) 443

T10/BSR INCITS 513 Revision 37 17 May 2014

The CREDENTIAL FORMAT field (see table 264) indicates the format of the credential.

Table 264 — Credential format values

Value Description
0h Reserved
1h The format defined by this standard
2h to Fh Reserved

The CREDENTIAL LENGTH field indicates the number of bytes that follow in the credential including the capability
length, the CbCS capability descriptor, the capability key length, and the capability key.

The CAPABILITY LENGTH field indicates the number of bytes that follow in the capability.

The contents of the CbCS capability descriptor are defined in 6.26.2.3.

The CAPABILITY KEY LENGTH field indicates the number of bytes that follow in the capability key.

The CAPABILITY KEY field contains an integrity check value that is computed and used as described in
5.13.6.7.12.

444 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.26.2.3 CbCS capability descriptor

6.26.2.3.1 Overview

A CbCS capability descriptor (see table 265) specifies the commands that are allowed by the CbCS extension
descriptor in which it appears.

Table 265 — CbCS capability descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESIGNATION TYPE KEY VERSION

1 CBCS METHOD

2 (MSB)
•• • CAPABILITY EXPIRATION TIME
7 (LSB)
8 (MSB)
•• • INTEGRITY CHECK VALUE ALGORITHM
11 (LSB)
12
•• • PERMISSIONS BIT MASK
15
16 (MSB)
•• • POLICY ACCESS TAG
19 (LSB)
20
•• • DESIGNATION DESCRIPTOR
57
58
•• • DISCRIMINATOR
71

The DESIGNATION TYPE field (see table 266) specifies the format of the Designation descriptor.

Table 266 — DESIGNATION TYPE field

Code Description DESIGNATION DESCRIPTOR

field format reference
0h Reserved
1h Logical unit designation descriptor 6.26.2.3.2
2h MAM attribute designation descriptor 6.26.2.3.3
3h to Fh Reserved

The KEY VERSION field specifies which working key (see 5.13.6.7.11), is being used to compute the capability
key (see 5.13.6.7.12) for this CbCS capability.

Working Draft SCSI Primary Commands - 4 (SPC-4) 445

T10/BSR INCITS 513 Revision 37 17 May 2014

The CBCS METHOD field (see table 267) specifies the CbCS method used by this CbCS capability.

Table 267 — CBCS METHOD field

Code CbCS method Reference

00h BASIC 5.13.6.7.8.2
01h CAPKEY 5.13.6.7.8.3
02h to EFh Reserved
F0h to FEh Vendor specific
FFh Reserved

The CAPABILITY EXPIRATION TIME field specifies expiration time of this CbCS capability as the number of
milliseconds that have elapsed since midnight, 1 January 1970 UT. If the CAPABILITY EXPIRATION TIME field is
set to zero, this CbCS capability does not have an expiration time.

If the CAPABILITY EXPIRATION TIME field is not set to zero, then:

a) the clock maintained by the CbCS management device server (see 5.13.6.7.3) should be
synchronized with the clock maintained by the enforcement manager (see 5.13.6.7.7). The method for
synchronizing the clocks is outside the scope of this standard. However, the protocol should be
implemented in a secure manner (e.g., it should not be possible for an adversary to set the clock in
the SCSI device or in the secure CDB processor backwards to enable the reuse of expired CbCS
credentials). The value in the enforcement manager’s clock is available in the Current CbCS
Parameters CbCS page (see 7.7.4.3.5) to assist in this synchronization;
b) the CbCS management device server should set the CAPABILITY EXPIRATION TIME field to a value that is
at least an order of magnitude larger than the allowed deviation between the clocks.

The INTEGRITY CHECK VALUE ALGORITHM field specifies the algorithm used to compute the capability key and
other integrity check values for this CbCS capability. The value in the INTEGRITY CHECK VALUE ALGORITHM field
is selected from the codes that the Unchangeable CbCS Parameters CbCS page (see 7.7.4.3.3) lists as
supported integrity check value algorithms.

The PERMISSIONS BIT MASK field (see table 268) specifies the permissions allowed by this CbCS capability.
More than one permissions bit may be set. The relationship between commands and bits in the PERMISSIONS
BIT MASK field is defined in for the commands defined by this standard and in the command standard that
defines commands for a specific device type.

Table 268 — PERMISSIONS BIT MASK field format

Bit
7 6 5 4 3 2 1 0
Byte
0 DATA READ DATA WRITE PARM READ PARM WRITE SEC MGMT RESRV MGMT PHY ACC

1
Reserved
2
3 Restricted (see applicable command standard)

A DATA READ bit set to zero indicates a command has no read permission for user data and protection
information, if any. A DATA READ bit set to one indicates a command has permission to read user data and
protection information, if any.

446 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

A DATA WRITE bit set to zero indicates a command has no write permission for user data and protection
information, if any. A DATA WRITE bit set to one indicates a command has permission to write user data and
protection information, if any.

A parameter data read ( PARM READ ) bit set to zero indicates a command has no parameter data read
permission. A PARM READ bit set to one indicates a command has permission to read parameter data.

A parameter data write ( PARM WRITE ) bit set to zero indicates a command has no parameter data write
permission. A PARM WRITE bit set to one indicates a command has permission to write parameter data.

A security management ( SEC MGMT) bit set to zero indicates a command has no security management
permission. A SEC MGMT bit set to one indicates a command has security management permission.

A reservation (RESRV) bit set to zero indicates a command has no persistent reservation permission. A RESRV
bit set to one indicates a command has permission to make or modify persistent reservations.

A management (MGMT) bit set to zero indicates a command has no storage management permission. A MGMT
bit set to one indicates a command has storage management permission. Storage management is outside the
scope of this standard.

A physical access (PHY ACC) bit set to zero indicates a command has no permission to affect physical access
to the logical unit or volume (see SSC-4 or SMC-3). A PHY ACC bit set to one indicates a command has
permission to affect physical access to the logical unit or volume.

If the POLICY ACCESS TAG field is set to a value other than zero, the policy access tag attribute of the logical unit
(see 5.13.6.7.15) is compared to the POLICY ACCESS TAG field contents as part of validating the CbCS
capability (see 5.13.6.7.13.2). If the POLICY ACCESS TAG field is set to zero, then no comparison is made.

The DESIGNATION DESCRIPTOR field is used during the validation of the CbCS capability (see 5.13.6.7.13.2) to
ensure that the command is being addressed to the correct logical unit or volume (see SSC-4 or SMC-3). The
format of the DESIGNATION DESCRIPTOR field is defined by the value in the DESIGNATION TYPE field as described
in table 266.

If the CREDENTIAL REQUEST TYPE field in a RECEIVE CREDENTIAL command is set to 0001h (i.e., CbCS
logical unit), then the DESIGNATION DESCRIPTOR field shall contain a logical unit designation descriptor that
matches the DESIGNATION DESCRIPTOR field (see 6.26.1.2) in the CREDENTIAL REQUEST DESCRIPTOR field in the
CDB. If the CREDENTIAL REQUEST TYPE field in a RECEIVE CREDENTIAL command is set to 0002h (i.e., CbCS
logical unit and volume), then the DESIGNATION DESCRIPTOR field shall contain a MAM attribute designation
descriptor that matches the MAM ATTRIBUTE field (see 6.26.1.3) in the CREDENTIAL REQUEST DESCRIPTOR field in
the CDB.

The DISCRIMINATOR field provides uniqueness to the CbCS capability descriptor and may be used to limit the
delegation or prevent leakage of the CbCS capability to other application clients. The CbCS management
device server (see 5.13.6.7.3) shall not return the same CbCS capability descriptor to two secure CDB
originators.

The enforcement manager (see 5.13.6.7.7) shall validate each CbCS capability descriptor received as
described in 5.13.6.7.13.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 447

T10/BSR INCITS 513 Revision 37 17 May 2014

6.26.2.3.2 Logical unit designation descriptor format

If the DESIGNATION TYPE field is set to 0001h (i.e., logical unit designation descriptor), then the format of the
DESIGNATION DESCRIPTOR field is as shown in table 269.

Table 269 — Logical unit designation descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • DESIGNATION DESCRIPTOR
19
20
•• • Reserved
37

The format of the DESIGNATION DESCRIPTOR field is defined in table 590 (see 7.8.6.1) with the following
additional requirements:

a) the DESIGNATOR TYPE field shall contain 3h (i.e., NAA);

b) the ASSOCIATION field shall 00b (i.e., logical unit); and
c) the DESIGNATOR LENGTH field shall set to a value that is smaller than 17.

6.26.2.3.3 Volume designation descriptors

If the DESIGNATION TYPE field is set to 0002h (i.e., volume unit designation descriptor), then the format of the
DESIGNATION DESCRIPTOR field is as shown in table 270.

Table 270 — Volume designation descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • MAM ATTRIBUTE
36
37 Reserved

The format of the MAM ATTRIBUTE field is defined in table 440 (see 7.4.1) with the following additional
requirements:

a) the MAM ATTRIBUTE field shall contain 0401h (i.e., MEDIUM SERIAL NUMBER); and
b) the ATTRIBUTE LENGTH field shall contain 0020h.

448 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.27 RECEIVE DIAGNOSTIC RESULTS command

The RECEIVE DIAGNOSTIC RESULTS command (see table 271) requests the device server to return data
based on the most recent SEND DIAGNOSTIC command (see 6.42) or a diagnostic page specified by the
PAGE CODE field.

Table 271 — RECEIVE DIAGNOSTIC RESULTS command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (1Ch)
1 Reserved PCV

2 PAGE CODE

3 (MSB)
ALLOCATION LENGTH
4 (LSB)
5 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 271 for the RECEIVE
DIAGNOSTIC RESULTS command.

A page code valid (PCV) bit set to zero specifies that the device server return parameter data based on the
most recent SEND DIAGNOSTIC command (e.g., the diagnostic page with the same page code as that
specified in the most recent SEND DIAGNOSTIC command). The response to a RECEIVE DIAGNOSTIC
RESULTS command with the PCV bit set to zero is vendor specific if:

a) the most recent SEND DIAGNOSTIC command was not a SEND DIAGNOSTIC command defining
parameter data to return;
b) a RECEIVE DIAGNOSTIC RESULTS command with a PCV bit set to one has been processed since
the last SEND DIAGNOSTIC command was processed; or
c) no SEND DIAGNOSTIC command with the PF bit set to one defining parameter data to return has
been processed since power on, hard reset, or logical unit reset.

A page code valid (PCV) bit set to one specifies that the device server return the diagnostic page specified in
the PAGE CODE field. Page code values are defined in 7.2 or in another command standard.

NOTE 32 - Logical units compliant with SPC-2 may transfer more than one diagnostic page in the parameter
data if the PCV bit is set to zero and the previous SEND DIAGNOSTIC command sent more than one
diagnostic page in the parameter list.

NOTE 33 - To ensure that the diagnostic command information is not destroyed by a command sent from
another I_T nexus, the logical unit should be reserved.

The ALLOCATION LENGTH field is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

See 7.2 for RECEIVE DIAGNOSTIC RESULTS diagnostic page format definitions.

Working Draft SCSI Primary Commands - 4 (SPC-4) 449

T10/BSR INCITS 513 Revision 37 17 May 2014

6.28 RECEIVE ROD TOKEN INFORMATION command

The RECEIVE ROD TOKEN INFORMATION command (see table 272) is a third-party copy command (see
5.16.3) that requests the copy manager to return all the ROD tokens (see 5.16.6.1) created during the copy
operation (see 5.16.4.3) specified by the LIST IDENTIFIER field (see 5.16.4.2) in the CDB.

Table 272 — RECEIVE ROD TOKEN INFORMATION command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (84h)
1 Reserved SERVICE ACTION (07h)
2 (MSB)
•• • LIST IDENTIFIER
5 (LSB)
6
•• • Reserved
9
10 (MSB)
•• • ALLOCATION LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 272 for the RECEIVE ROD
TOKEN INFORMATION command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 272 for the RECEIVE ROD
TOKEN INFORMATION command.

The LIST IDENTIFIER field and ALLOCATION LENGTH field are defined in 6.20.

If no copy operation known to the copy manager has a list identifier that matches the contents of the LIST
IDENTIFIER field, then the copy manager shall terminate the RECEIVE ROD TOKEN INFORMATION command
with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense
code set to INVALID FIELD IN CDB.

The CONTROL byte is defined in SAM-5.

450 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 273 shows the format of the parameter data for the RECEIVE ROD TOKEN INFORMATION command.

Table 273 — Parameter data for the RECEIVE ROD TOKEN INFORMATION command

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • AVAILABLE DATA (n-3)
3 (LSB)
4 Reserved RESPONSE TO SERVICE ACTION

5 Reserved COPY OPERATION STATUS

6 (MSB)
OPERATION COUNTER
7 (LSB)
8 (MSB)
•• • ESTIMATED STATUS UPDATE DELAY
11 (LSB)
12 EXTENDED COPY COMPLETION STATUS

13 LENGTH OF THE SENSE DATA FIELD (X-31)

14 SENSE DATA LENGTH

15 TRANSFER COUNT UNITS

16 (MSB)
•• • TRANSFER COUNT
23 (LSB)
24 (MSB)
SEGMENTS PROCESSED
25 (LSB)
26
•• • Reserved
31
32
•• • SENSE DATA
x
x+1
•• • ROD TOKEN DESCRIPTORS LENGTH (n-(x+4))
x+4
ROD token descriptors
x+5
•• • ROD token descriptor (see table 274) [first]

••
•

•• • ROD token descriptor (see table 274) [last]

n

Working Draft SCSI Primary Commands - 4 (SPC-4) 451

T10/BSR INCITS 513 Revision 37 17 May 2014

The AVAILABLE DATA field, RESPONSE TO SERVICE ACTION field, COPY OPERATION STATUS field, OPERATION
COUNTER field, ESTIMATED STATUS UPDATE DELAY field, EXTENDED COPY COMPLETION STATUS field, LENGTH OF
THE SENSE DATA FIELD field, SENSE DATA LENGTH field, TRANSFER COUNT UNITS field, TRANSFER COUNT field,
SEGMENTS PROCESSED field, and SENSE DATA field are defined in 6.24.

If the COPY OPERATION STATUS field is set to a value that table 252 (see 6.24) describes as meaning the
operation completed without errors, then the ROD TOKEN DESCRIPTORS LENGTH field indicates the number of
bytes that follow in ROD token descriptors. If the COPY OPERATION STATUS field is not set to a value that table
252 (see 6.24) describes as meaning the operation completed without errors, then the ROD TOKEN
DESCRIPTORS LENGTH field shall be set to zero.

If the COPY OPERATION STATUS field is set to 01h or 03h, then each ROD token descriptor (see table 274) shall
contain one ROD token created by the copy operation whose service action is indicated by the RESPONSE TO
SERVICE ACTION field.

Table 274 — ROD token descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
ID FOR CREATING ROD CSCD DESCRIPTOR
1 (LSB)
2
•• • ROD TOKEN
n

If the RESPONSE TO SERVICE ACTION field is set to 00h or 01h (i.e., if the ROD tokens being returned were
created by an EXTENDED COPY command), then the ID FOR CREATING ROD CSCD DESCRIPTOR field indicates
the CSCD descriptor ID for the ROD CSCD descriptor in which the R_TOKEN bit was set to one resulting in the
creation of the ROD token contained in the ROD TOKEN field (i.e., the value any segment descriptor that caused
the ROD to be populated had in its DESTINATION CSCD DESCRIPTOR ID field). If the RESPONSE TO SERVICE ACTION
field does not contain 00h or 01h (i.e., if the ROD tokens being returned were created by a command other
than the EXTENDED COPY command), then the ID FOR CREATING ROD CSCD DESCRIPTOR field is reserved.

The ROD TOKEN field contains a ROD token (see 5.16.6.4) created by the copy manager.

6.29 REMOVE I_T NEXUS command

The REMOVE I_T NEXUS command (see table 275) requests the device server to establish an I_T nexus
loss (see SAM-5) for the logical unit containing the device server for each specified I_T nexus. This command
uses the MAINTENANCE OUT CDB format (see 4.2.2.3.4).

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 275 for the REMOVE I_T
NEXUS command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 275 for the REMOVE I_T
NEXUS command.

The PARAMETER LIST LENGTH field specifies the length in bytes of the parameter data that shall be transferred
from the application client to the device server. A parameter list length value of zero specifies that no data
shall be transferred and no I_T nexuses shall be removed.

452 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 275 — REMOVE I_T NEXUS command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A4h)
1 Reserved SERVICE ACTION (0Ch)
2
•• • Reserved
5
6 (MSB)
•• • PARAMETER LIST LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The CONTROL byte is defined in SAM-5.

If the parameter list length results in the truncation of the header or any I_T nexus descriptor, then the device
server:

a) shall not remove any I_T nexuses; and

b) shall terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to PARAMETER LIST LENGTH ERROR.

Table 276 shows the format of the REMOVE I_T NEXUS parameter list.

Table 276 — REMOVE I_T NEXUS parameter list format

Bit
7 6 5 4 3 2 1 0
Byte
0
Reserved
1
2 (MSB)
I_T NEXUS DESCRIPTOR LIST LENGTH (n-3)
3 (LSB)
I_T nexus descriptor list
4
•• • I_T nexus descriptor [first]

••
•

•• • I_T nexus descriptor [last]

n

The I_T NEXUS DESCRIPTOR LIST LENGTH field specifies the length in bytes of the I_T nexus descriptor list.

Working Draft SCSI Primary Commands - 4 (SPC-4) 453

T10/BSR INCITS 513 Revision 37 17 May 2014

The I_T nexus descriptor list contains one or more I_T nexus descriptors (see table 277). The I_T nexus
descriptors may appear in the I_T nexus descriptor list in any order. The device server shall process the I_T
nexus descriptors in order. The device server shall ignore any I_T nexus descriptor that describes an I_T
nexus not known to the logical unit.

The device server shall not remove any I_T nexuses and shall terminate the command with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
INVALID FIELD IN PARAMETER LIST if any of the I_T nexus descriptors describe:

a) the same I_T nexus as the one through which the REMOVE I_T NEXUS command is received; or
b) an I_T nexus that does not support the I_T NEXUS RESET task management function.

Table 277 — I_T nexus descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
RELATIVE TARGET PORT IDENTIFIER
1 (LSB)
2 (MSB)
TRANSPORTID LENGTH (n-3)
3 (LSB)
4
•• • TRANSPORTID
n

The RELATIVE TARGET PORT IDENTIFIER field (see 4.3.4) specifies the relative target port identifier of the target
port of the I_T nexus to be reset.

The TRANSPORTID LENGTH field specifies the length in bytes of the TRANSPORTID field.

The TRANSPORTID field specifies a TransportID (see 7.6.4) identifying the initiator port of the I_T nexus to be
reset.

454 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.30 REPORT ALIASES command

The REPORT ALIASES command (see table 278) requests the device server to return the alias list. This
command uses the MAINTENANCE IN CDB format (see 4.2.2.3.3). The alias list is managed using the
CHANGE ALIASES command (see 6.2). If the CHANGE ALIASES command is supported, the REPORT
ALIASES command shall also be supported.

Table 278 — REPORT ALIASES command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A3h)
1 Reserved SERVICE ACTION (0Bh)
2
•• • Reserved
5
6 (MSB)
•• • ALLOCATION LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 278 for the REPORT
ALIASES command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 278 for the REPORT
ALIASES command.

The ALLOCATION LENGTH field is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

Working Draft SCSI Primary Commands - 4 (SPC-4) 455

T10/BSR INCITS 513 Revision 37 17 May 2014

The parameter data for a REPORT ALIASES command (see table 279) contains zero or more alias entries.

Table 279 — REPORT ALIASES parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • ADDITIONAL LENGTH (n-3)
3 (LSB)
4 Reserved
5 Reserved
6 (MSB)
NUMBER OF ALIASES
7 (LSB)
Alias entry list
8
•• • Alias entry (see 6.2.2) [first]

••
•

•• • Alias entry (see 6.2.2) [last]

n

The ADDITIONAL LENGTH field indicates the number of bytes in the remaining parameter data. The contents of
the ADDITIONAL LENGTH field are not altered based on the allocation length (see 4.2.5.6).

The NUMBER OF ALIASES field indicates the number of alias entries in the alias list and shall not be changed if
the CDB contains an insufficient allocation length.

The parameter data shall include one alias entry for each alias in the alias list. The format of an alias entry is
described in 6.2.2.

456 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.31 REPORT ALL ROD TOKENS command

The REPORT ALL ROD TOKENS command (see table 280) is a third-party copy command (see 5.16.3) that
requests the copy manager to return a ROD management token (see 5.16.6.4) for each ROD token that was
created by and is known to the copy manager.

Table 280 — REPORT ALL ROD TOKENS command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (84h)
1 Reserved SERVICE ACTION (08h)
2
•• • Reserved
9
10 (MSB)
•• • ALLOCATION LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 280 for the REPORT ALL
ROD TOKENS command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 280 for the REPORT ALL
ROD TOKENS command.

The ALLOCATION LENGTH field is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

In response to the REPORT ALL ROD TOKENS command, the copy manager shall return one or more ROD
management tokens. Each ROD management token shall represent a ROD token that:

a) has fields defined in the ROD token body;

b) was created by the copy manager that is processing the REPORT ALL ROD TOKENS command; and
c) is known to that copy manager.

Working Draft SCSI Primary Commands - 4 (SPC-4) 457

T10/BSR INCITS 513 Revision 37 17 May 2014

The format of the REPORT ALL ROD TOKENS parameter data is shown in table 281.

Table 281 — Parameter data for the REPORT ALL ROD TOKENS command

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • AVAILABLE DATA (n-3)
3 (LSB)
4
•• • Reserved
7
ROD management token list
8
•• • ROD management token [first]
103
•
••

n-95
•• • ROD management token [last]
n

The AVAILABLE DATA field shall contain the number of bytes that follow in the parameter data. The contents of
the AVAILABLE DATA field are not altered based on the allocation length (see 4.2.5.6).

Each ROD management token is a 96-byte token that contains the fields described in 5.16.6.4, and
represents a ROD token that meets the criteria described in this subclause.

6.32 REPORT IDENTIFYING INFORMATION command

6.32.1 REPORT IDENTIFYING INFORMATION command overview

The REPORT IDENTIFYING INFORMATION command (see table 282) requests the device server to return
identifying information (see 5.6). This command uses the MAINTENANCE IN CDB format (see 4.2.2.3.3). The
REPORT IDENTIFYING INFORMATION command is an extension to the REPORT PERIPHERAL
DEVICE/COMPONENT DEVICE IDENTIFIER service action of the MAINTENANCE IN command defined in
SCC-2.

The device server shall return the same identifying information regardless of the I_T nexus being used to
transfer the identifying information.

458 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Processing a REPORT IDENTIFYING INFORMATION command may require the enabling of a nonvolatile
memory within the logical unit. If the nonvolatile memory is not ready, the device server shall terminate the
command with CHECK CONDITION status, and not wait for the nonvolatile memory to become ready. The
sense key shall be set to NOT READY and the additional sense code shall be set as described in table 336
(see 6.47). This information should allow the application client to determine the action required to cause the
device server to become ready.

Table 282 — REPORT IDENTIFYING INFORMATION command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A3h)
1 Reserved SERVICE ACTION (05h)
2
Reserved
3
4
Restricted (see SCC-2)
5
6 (MSB)
•• • ALLOCATION LENGTH
9 (LSB)
10 IDENTIFYING INFORMATION TYPE Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 282 for the REPORT
IDENTIFYING INFORMATION command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 282 for the REPORT
IDENTIFYING INFORMATION command.

The ALLOCATION LENGTH field is defined in 4.2.5.6.

The IDENTIFYING INFORMATION TYPE field (see table 283) specifies the type of identifying information to be
returned. If the specified identifying information type is not implemented by the device server, the device
server shall terminate the command with CHECK CONDITION status with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

Table 283 — IDENTIFYING INFORMATION TYPE field

Code Description Reference

0000000b Peripheral device identifying information (see 5.6). 6.32.2
0000010b Peripheral device text identifying information (see 5.6). 6.32.2
1111110b Identifying information supported – The parameter data contains a list of 6.32.3
supported identifying information types and the maximum length of each.
xxxxxx1b Restricted SCC-2
All other Reserved

The CONTROL byte is defined in SAM-5.

Working Draft SCSI Primary Commands - 4 (SPC-4) 459

T10/BSR INCITS 513 Revision 37 17 May 2014

6.32.2 Peripheral device identifying information parameter data

The peripheral device identifying information parameter data format (see table 284) is used if the IDENTIFYING
INFORMATION TYPE field is set to 0000000b or 0000010b.

Table 284 — Peripheral device identifying information parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0
Reserved
1
2 (MSB)
IDENTIFYING INFORMATION LENGTH (n-3)
3 (LSB)
4
•• • IDENTIFYING INFORMATION
n

The IDENTIFYING INFORMATION LENGTH field indicates the length in bytes of the IDENTIFYING INFORMATION field.
The contents of the IDENTIFYING INFORMATION LENGTH field are not altered based on the allocation length (see
4.2.5.6).

The IDENTIFYING INFORMATION field contains the peripheral device identifying information that has the specified
identifying information type (see 6.32.1).

6.32.3 Identifying information supported parameter data

The identifying information supported parameter data format (see table 285) is used if the IDENTIFYING
INFORMATION TYPE field is set to 1111110b.

Table 285 — Identifying information supported parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0
Reserved
1
2 (MSB)
IDENTIFYING INFORMATION LENGTH (n-3)
3 (LSB)
Identifying information descriptor list
4
Identifying information descriptor [first]
•• •
(see table 286)
7
••
•
n-3
Identifying information descriptor [last]
•• •
(see table 286)
n

460 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The IDENTIFYING INFORMATION LENGTH field indicates the length in bytes of the identifying information descriptor
list. The contents of the IDENTIFYING INFORMATION LENGTH field are not altered based on the allocation length
(see 4.2.5.6).

The identifying information descriptor list contains an identifying information descriptor (see table 286) for
each identifying information type supported by the device server. The identifying information descriptors shall
be sorted in increasing order based on the value in the IDENTIFYING INFORMATION TYPE field.

Table 286 — Identifying information descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 IDENTIFYING INFORMATION TYPE Reserved
1 Reserved
2 (MSB)
MAXIMUM IDENTIFYING INFORMATION LENGTH
3 (LSB)

The IDENTIFYING INFORMATION TYPE field indicates the identifying information type (see table 283) associated
with the descriptor.

The MAXIMUM IDENTIFYING INFORMATION LENGTH field indicates the maximum number of bytes supported for the
identifying information type indicated the value in the IDENTIFYING INFORMATION TYPE field.

Working Draft SCSI Primary Commands - 4 (SPC-4) 461

T10/BSR INCITS 513 Revision 37 17 May 2014

6.33 REPORT LUNS command

The REPORT LUNS command (see table 287) requests the device server to return the peripheral device
logical unit inventory accessible to the I_T nexus. The logical unit inventory returned to the application client is
a list that shall include the logical unit numbers of all logical units having a PERIPHERAL QUALIFIER value of 000b
(see 6.6.2) based on the SELECT REPORT field. Logical unit numbers for logical units with PERIPHERAL QUALIFIER
values other than 000b and 011b may be included in the logical unit inventory. Logical unit numbers for logical
units with a PERIPHERAL QUALIFIER value of 011b shall not be included in the logical unit inventory.

Table 287 — REPORT LUNS command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A0h)
1 Reserved
2 SELECT REPORT

3
•• • Reserved
5
6 (MSB)
•• • ALLOCATION LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 287 for the REPORT LUNS
command.

The SELECT REPORT field (see table 288) specifies the types of logical unit addresses that shall be reported.

Table 288 — SELECT REPORT field (part 1 of 2)

Code Description
00h The list shall contain the logical units accessible to the I_T nexus with the following
addressing methods (see SAM-5):
a) simple logical unit addressing method;
b) logical unit addressing method;
c) peripheral device addressing method;
d) flat space addressing method;
e) extended flat space addressing method; and
f) long extended flat space addressing method.
If there are no logical units to report, the LUN LIST LENGTH field shall be set to zero.
01h The list shall contain only well known logical units, if any. If there are no well known
logical units, the LUN LIST LENGTH field shall be zero.
02h The list shall contain all logical units accessible to the I_T nexus.

462 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 288 — SELECT REPORT field (part 2 of 2)

Code Description
10h If the device server processing the command is in LUN 0 or the REPORT LUNS
well-known logical unit, then the list shall contain only administrative logical units
(see SAM-5).
The LUN LIST LENGTH field shall be set to zero if the device server processing the
command is not in:
a) LUN 0; or
b) the REPORT LUNS well-known logical unit.
If there are no logical units to report, the LUN LIST LENGTH field shall be set to zero.
11h If the device server processing the command is in LUN 0 or the REPORT LUNS
well-known logical unit, then the list shall contain only:
a) administrative logical units (see SAM-5);
b) logical units with the logical unit addressing method at level 1; and
c) logical units with single level LUN structure with the following addressing methods
(see SAM-5):
A) peripheral device addressing method;
B) flat space addressing method;
C) extended flat space addressing method; and
D) long extended flat space addressing method.
The LUN LIST LENGTH field shall be set to zero if the device server processing the
command is not in:
a) LUN 0; or
b) the REPORT LUNS well-known logical unit.
If there are no logical units to report, the LUN LIST LENGTH field shall be set to zero.
12h If the device server processing the command is in an administrative logical unit, the
list shall contain:
a) the logical unit processing the command; and
b) subsidiary logical units that are contained in the same logical unit conglomerate
that contains the logical unit processing the command.
The LUN LIST LENGTH field shall be set to zero if the device server processing the
command is not in an administrative logical unit.
If there are no logical units to report, the LUN LIST LENGTH field shall be set to zero.
F8h to FFh Vendor specific
all others Reserved

The ALLOCATION LENGTH field is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

The REPORT LUNS command shall return CHECK CONDITION status only if the device server is unable to
return the requested report of the logical unit inventory.

If a REPORT LUNS command is received from an I_T nexus with a pending unit attention condition (i.e.,
before the device server reports CHECK CONDITION status), then the device server shall perform the
REPORT LUNS command (see SAM-5).

The REPORT LUNS parameter data should be returned even though the device server is not ready for other
commands. The report of the logical unit inventory should be available without incurring any media access
delays. If the device server is not ready with the logical unit inventory or if the inventory list is null for the
requesting I_T nexus and the SELECT REPORT field set to 02h, then the device server shall provide a default

Working Draft SCSI Primary Commands - 4 (SPC-4) 463

T10/BSR INCITS 513 Revision 37 17 May 2014

logical unit inventory that contains at least LUN 0 or the REPORT LUNS well known logical unit (see 8.2). A
non-empty peripheral device logical unit inventory that does not contain either LUN 0 or the REPORT LUNS
well known logical unit is valid.

If a REPORT LUNS command is received for a logical unit that the SCSI target device does not support and
the device server is not capable of returning the logical unit inventory, then the device server shall terminate
the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the
additional sense code set to LOGICAL UNIT NOT SUPPORTED.

The device server shall report those devices in the logical unit inventory using the format shown in table 289.

Table 289 — REPORT LUNS parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • LUN LIST LENGTH (n-7)
3 (LSB)
4
•• • Reserved
7
LUN list
8
•• • LUN [first]
15
•
••

n-7
•• • LUN [last]
n

The LUN LIST LENGTH field shall contain the length in bytes of the LUN list. The LUN list length is the number of
logical unit numbers in the logical unit inventory multiplied by eight. The contents of the LUN LIST LENGTH field
are not altered based on the allocation length (see 4.2.5.6).

464 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.34 REPORT PRIORITY command

The REPORT PRIORITY command (see table 290) requests the device server to return the command
priorities (see SAM-5) that have been assigned to one or more I_T nexuses associated with the logical unit
(i.e., I_T_L nexuses). This command uses the MAINTENANCE IN CDB format (see 4.2.2.3.3).

Table 290 — REPORT PRIORITY command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A3h)
1 Reserved SERVICE ACTION (0Eh)
2 PRIORITY REPORTED Reserved
3
•• • Reserved
5
6 (MSB)
•• • ALLOCATION LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 290 for the REPORT
PRIORTY command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 290 for the REPORT
PRIORTY command.

The PRIORITY REPORTED field (see table 291) specifies the information to be returned in the parameter data.

Table 291 — PRIORITY REPORTED field

Code Description
00b Only the priority for the I_T nexus on which the command was
received shall be reported in the REPORT PRIORITY parameter data.
01b The priority for each I_T nexus that is not set to the initial command
priority shall be reported in the REPORT PRIORITY parameter data.
10b to 11b Reserved

The ALLOCATION LENGTH field is defined in 4.2.5.6. The allocation length should be at least four.

The CONTROL byte is defined in SAM-5.

Working Draft SCSI Primary Commands - 4 (SPC-4) 465

T10/BSR INCITS 513 Revision 37 17 May 2014

The format of the parameter data for the REPORT PRIORITY command is shown in table 292.

Table 292 — REPORT PRIORITY parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • PRIORITY PARAMETER DATA LENGTH (n-3)
3 (LSB)
Priority descriptors
4
•• • Priority descriptor (see table 293) [first]

•
••

•• • Priority descriptor (see table 293) [last]

n

The PRIORITY PARAMETER DATA LENGTH field indicates the number of bytes of parameter data that follow. The
contents of the PRIORITY PARAMETER DATA LENGTH field are not altered based on the allocation length (see
4.2.5.6).

Each priority descriptor (see table 293) contains priority information for a single I_T_L nexus.

Table 293 — Priority descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 Reserved CURRENT PRIORITY

1 Reserved
2 (MSB)
RELATIVE TARGET PORT IDENTIFIER
3 (LSB)
4 Reserved
5 Reserved
6 (MSB)
ADDITIONAL DESCRIPTOR LENGTH (n-7)
7 (LSB)
8
•• • TransportID
n

The CURRENT PRIORITY field indicates the priority assigned to the I_T_L nexus represented by this descriptor. If
the PRIORITY REPORTED field in this command is set to 00b and the priority for the I_T_L nexus associated with
this command is set to the initial command priority, then the CURRENT PRIORITY field shall be set to zero. The
priority assigned to an I_T_L nexus may be used as a command priority for commands received via that I_T_L
nexus (see SAM-5).

466 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The RELATIVE TARGET PORT IDENTIFIER field (see 4.3.4) indicates the relative port identifier of the target port
that is part of the I_T_L nexus to which the current priority applies.

The ADDITIONAL DESCRIPTOR LENGTH field indicates the number of bytes that follow in the descriptor (i.e., the
size of the TransportID).

The TransportID specifies a TransportID (see 7.6.4) identifying the initiator port that is part of the I_T_L nexus
to which the current priority applies.

6.35 REPORT SUPPORTED OPERATION CODES command

6.35.1 REPORT SUPPORTED OPERATION CODES command introduction

The REPORT SUPPORTED OPERATION CODES command (see table 294) requests the device server to
return information on commands the addressed logical unit supports. This command uses the
MAINTENANCE IN CDB format (see 4.2.2.3.3). An application client may request a list of all operation codes
and service actions supported by the logical unit or the command support data for a specific command.

Table 294 — REPORT SUPPORTED OPERATION CODES command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A3h)
1 Reserved SERVICE ACTION (0Ch)
2 RCTD Reserved REPORTING OPTIONS

3 REQUESTED OPERATION CODE

4 (MSB)
REQUESTED SERVICE ACTION
5 (LSB)
6 (MSB)
•• • ALLOCATION LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 294 for the REPORT
SUPPORTED OPERATION CODES command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 294 for the REPORT
SUPPORTED OPERATION CODES command.

A return command timeouts descriptor (RCTD) bit set to one specifies that the command timeouts descriptor
(see 6.35.4) shall be included in each command descriptor (see 6.35.2) that is returned or in the
one_command parameter data (see 6.35.3) that is returned. A RCTD bit set to zero specifies that the command
timeouts descriptor shall not be returned.

Working Draft SCSI Primary Commands - 4 (SPC-4) 467

T10/BSR INCITS 513 Revision 37 17 May 2014

The REPORTING OPTIONS field (see table 295) specifies the information to be returned in the parameter data.

Table 295 — REPORT SUPPORTED OPERATION CODES REPORTING OPTIONS field

Parameter data
Code Description reference
000b A list of all operation codes and service actions a supported by the logical 6.35.2
unit shall be returned in the all_commands parameter data format. The
REQUESTED OPERATION CODE field and REQUESTED SERVICE ACTION field
shall be ignored.
001b The command support data for the operation code specified in the 6.35.3
REQUESTED OPERATION CODE field shall be returned in the one_command
parameter data format. The REQUESTED SERVICE ACTION field shall be
ignored. If the REQUESTED OPERATION CODE field specifies an operation
code for which the device server implements service actions a, then the
device server shall terminate the command with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID FIELD IN CDB.
010b The command support data for the operation code and service action a 6.35.3
specified in the REQUESTED OPERATION CODE field and REQUESTED SERVICE
ACTION field shall be returned in the one_command parameter data format.
If the REQUESTED OPERATION CODE field specifies an operation code for
which the device server does not implement service actions a, then the
device server shall terminate the command with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID FIELD IN CDB.
011b The command support data for the operation code and service action a 6.35.3
specified in the REQUESTED OPERATION CODE field and REQUESTED SERVICE
ACTION field shall be returned in the one_command parameter data format.
If:
a) the operation code specified by the REQUESTED OPERATION CODE
field specifies an operation code for which the device server does
not implement service actions, the REQUESTED SERVICE ACTION field
is set to 00h, and the command is supported; or
b) the operation code specified by the REQUESTED OPERATION CODE
field specifies an operation code for which the device server imple-
ments service actions and the value in the REQUESTED SERVICE
ACTION field is supported,
then the command support data shall indicate that the command is
supported (i.e., the SUPPORT field (see table 298) is set to 011b or 101b).
Otherwise, the command support data shall indicate that the command is
not supported (i.e., the SUPPORT field is set to 001b).
100b to Reserved
111b
a
The device server should also process the following fields in the following commands as specifying
service actions (i.e., the specified field should be processed as a SERVICE ACTION field):
a) the MODE field in the READ BUFFER command (see 6.18); and
b) the MODE field in the WRITE BUFFER command (see 6.49).

The REQUESTED OPERATION CODE field specifies the operation code of the command to be returned in the
one_command parameter data format (see 6.35.3).

468 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The REQUESTED SERVICE ACTION field specifies the service action of the command to be returned in the
one_command parameter data format.

The ALLOCATION LENGTH field is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

6.35.2 All_commands parameter data format

The REPORT SUPPORTED OPERATION CODES all_commands parameter data format (see table 296)
begins with a four-byte header that contains the length in bytes of the parameter data followed by a list of
supported commands. Each command descriptor contains information about a single supported command
CDB (i.e., one operation code and service action combination, or one non-service-action operation code). The
list of command descriptors shall contain all commands supported by the logical unit.

Table 296 — All_commands parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • COMMAND DATA LENGTH (n-3)
3 (LSB)
Command descriptors
4
•• • Command descriptor (see table 297) [first]

•
••

•• • Command descriptor (see table 297) [last]

n

The COMMAND DATA LENGTH field indicates the length in bytes of the command descriptor list. The contents of
the COMMAND DATA LENGTH field are not altered based on the allocation length (see 4.2.5.6).

Working Draft SCSI Primary Commands - 4 (SPC-4) 469

T10/BSR INCITS 513 Revision 37 17 May 2014

Each command descriptor (see table 297) contains information about a single supported command CDB.

Table 297 — Command descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE

1 Reserved
2 (MSB)
SERVICE ACTION
3 (LSB)
4 Reserved
5 Reserved CTDP SERVACTV

6 (MSB)
CDB LENGTH
7 (LSB)
8
•• • Command timeouts descriptor, if any (see 6.35.4)
19

The OPERATION CODE field indicates the operation code of a command supported by the logical unit.

The SERVICE ACTION field indicates a supported service action of the supported operation code indicated by
the OPERATION CODE field. If the operation code indicated in the OPERATION CODE field does not have any
service actions, the SERVICE ACTION field shall be set to 00h.

A command timeouts descriptor present (CTDP) bit set to one indicates that the command timeouts descriptor
(see 6.35.4) is included in this command descriptor. A CTDP bit set to zero indicates that the command
timeouts descriptor is not included in this command descriptor.

A service action valid (SERVACTV) bit set to zero indicates the operation code indicated by the OPERATION CODE
field does not have service actions and the SERVICE ACTION field contents are reserved. A SERVACTV bit set to
one indicates the operation code indicated by the OPERATION CODE field has service actions and the contents
of the SERVICE ACTION field are valid.

The CDB LENGTH field indicates the length of the command CDB in bytes for the operation code indicated in the
OPERATION CODE field, and if the SERVACTV bit is set to one the service action indicated by the SERVICE ACTION
field.

The command timeouts descriptor is described in 6.35.4.

470 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.35.3 One_command parameter data format

The REPORT SUPPORTED OPERATION CODES one_command parameter data format (see table 298)
contains information about the CDB and a usage map for bits in the CDB for the command specified by the
REPORTING OPTIONS field, REQUESTED OPERATION CODE field, and REQUESTED SERVICE ACTION field in the
REPORT SUPPORTED OPERATION CODES CDB.

Table 298 — One_command parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0 Reserved
1 CTDP Reserved SUPPORT

2 (MSB)
CDB SIZE (n-3)
3 (LSB)
4
•• • CDB USAGE DATA
n
n+1
•• • Command timeouts descriptor, if any (see 6.35.4)
n+12

A command timeouts descriptor present (CTDP) bit set to one indicates that the command timeouts descriptor
(see 6.35.4) is included in the parameter data. A CTDP bit set to zero indicates that the command timeouts
descriptor is not included in the parameter data.

The SUPPORT field is defined in table 299.

Table 299 — SUPPORT values

Support Description
000b Data about the requested SCSI command is not currently available. No data after
byte one is valid. A subsequent request for command support data may be suc-
cessful.
001b The device server does not support the requested command. Data after byte one is
undefined.
010b Reserved
011b The device server supports the requested command in conformance with a SCSI
standard. The parameter data format conforms to the definition in table 298.
100b Reserved
101b The device server supports the requested command in a vendor specific manner.
The parameter data format conforms to the definition in table 298.
110b to 111b Reserved

The CDB SIZE field indicates the size of the CDB USAGE DATA field in the parameter data, and the number of
bytes in the CDB for command being queried (i.e., the command specified by the REPORTING OPTIONS field,
REQUESTED OPERATION CODE field, and REQUESTED SERVICE ACTION field in the REPORT SUPPORTED
OPERATION CODES CDB).

Working Draft SCSI Primary Commands - 4 (SPC-4) 471

T10/BSR INCITS 513 Revision 37 17 May 2014

The CDB USAGE DATA field contains information about the CDB for the command being queried. The first byte
of the CDB USAGE DATA field shall contain the operation code for the command being queried. If the command
being queried contains a service action, then that service action code shall be placed in the CDB USAGE DATA
field in the same location as the SERVICE ACTION field of the command CDB. All other bytes of the CDB USAGE
DATA field shall contain a usage map for bits in the CDB for the command being queried.

The bits in the usage map shall have a one-for-one correspondence to the CDB for the command being
queried. If the device server evaluates a bit in the CDB for the command being queried, the usage map shall
contain a one in the corresponding bit position. If the device server ignores or treats as reserved a bit in the
CDB for the command being queried, the usage map shall contain a zero in the corresponding bit position.
The usage map bits for a given CDB field all shall have the same value (e.g., if any bit representing part of a
field is set to one, all bits for the field shall be set to one).

For example, the CDB usage bit map for the REPORT SUPPORTED OPERATION CODES command is: A3h,
0Ch, 87h, FFh, FFh, FFh, FFh, FFh, FFh, FFh, 00h, 07h. This example assumes that the logical unit only
supports the low-order three bits of the CDB CONTROL byte. The first byte contains the operation code, and the
second byte contains three reserved bits and the service action. The remaining bytes contain the usage map.

The command timeouts descriptor is described in 6.35.4.

6.35.4 Command timeouts descriptor

6.35.4.1 Overview

The command timeouts descriptor (see table 300) contains timeout information for commands supported by
the logical unit based on the time from the start of processing for the command to its reported completion.

Values contained in the command timeouts descriptor do not include times that are outside the control of the
device server (e.g., prior commands with the IMMED bit set to one in the CDB, concurrent commands from the
same or different I_T nexuses, manual unloads, power on self tests, prior aborted commands, commands that
force cache synchronization, delays in the service delivery subsystem, time in the task set before the start of
processing).

For commands that cause a change in power condition (see 5.11), values contained in the command timeouts
descriptor do not include the power condition transition time (e.g., the time to spinup rotating media).

Values contained in the command timeouts descriptor should not be used to compare products.

472 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 300 — Command timeouts descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
DESCRIPTOR LENGTH (000Ah)
1 (LSB)
2 Reserved
3 COMMAND SPECIFIC

4 (MSB)
•• • NOMINAL COMMAND PROCESSING TIMEOUT
7 (LSB)
8 (MSB)
•• • RECOMMENDED COMMAND TIMEOUT
11 (LSB)

The DESCRIPTOR LENGTH field indicates the number of bytes that follow in the command timeouts descriptor.
The contents of the DESCRIPTOR LENGTH field are not altered based on the allocation length (see 4.2.5.6).

The COMMAND SPECIFIC field contains timeout information that is defined for a specific command (e.g., the
WRITE BUFFER command (see 6.35.4.2)). If no command specific timeout information is defined by this or
the applicable command standard the COMMAND SPECIFIC field is reserved.

A non-zero value in the NOMINAL COMMAND PROCESSING TIMEOUT field indicates the minimum amount of time in
seconds the application client should wait prior to querying for the progress of the command identified by the
parameter data that contains this command timeouts descriptor. A value of zero in the NOMINAL COMMAND
PROCESSING TIMEOUT field indicates that no timeout is indicated.

NOTE 34 - The value contained in the NOMINAL COMMAND PROCESSING TIMEOUT field may include time
required for typical device error recovery procedures expected to occur on a regular basis.

A non-zero value in the RECOMMENDED COMMAND TIMEOUT field specifies the recommended time in seconds
the application client should wait prior to timing out the command identified by the parameter data that
contains this command timeouts descriptor. A value of zero in the RECOMMENDED COMMAND TIMEOUT field
indicates that no time is indicated.

The device server should set the recommended command timeout to a value greater than or equal to the
nominal command processing timeout.

6.35.4.2 WRITE BUFFER command timeouts descriptor COMMAND SPECIFIC field usage

For the WRITE BUFFER command (see 6.49), the COMMAND SPECIFIC field usage is reserved for all modes
except the following:

a) download microcode mode (04h);

b) download microcode and save mode (05h);
c) download microcode with offsets mode (06h);
d) download microcode with offsets and save mode (07h);
e) download microcode with offsets, select activation events, save, and defer activate mode (0Dh) only if
the microcode is activated by an event other than the activate deferred microcode mode;

Working Draft SCSI Primary Commands - 4 (SPC-4) 473

T10/BSR INCITS 513 Revision 37 17 May 2014

f) download microcode with offsets, save, and defer activate mode (0Eh) only if the microcode is
activated by an event other than an activate deferred microcode mode; and
g) activate deferred microcode mode (0Fh).

If the command timeouts descriptor describes one of the WRITE BUFFER modes listed in this subclause,
then the COMMAND SPECIFIC field indicates the maximum time, in one second increments, that access to the
SCSI device is limited or not possible through any SCSI ports associated with a logical unit that processes a
WRITE BUFFER command that specifies one of the named modes. A value of zero in the COMMAND SPECIFIC
field indicates that no maximum time is indicated.

6.36 REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS command

The REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS command (see table 301) requests the
device server to return on task management functions (see SAM-5) the addressed logical unit supports. This
command uses the MAINTENANCE IN CDB format (see 4.2.2.3.3).

Table 301 — REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A3h)
1 Reserved SERVICE ACTION (0Dh)
2 REPD Reserved
3
•• • Reserved
5
6 (MSB)
•• • ALLOCATION LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 301 for the REPORT
SUPPORTED TASK MANAGEMENT FUNCTIONS command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 301 for the REPORT
SUPPORTED TASK MANAGEMENT FUNCTIONS command.

A return extended parameter data ( REPD ) bit set to one specifies that the task management timeout
information shall be included in the parameter data that is returned. A REPD bit set to zero specifies that the
task management timeout information shall not be returned.

The ALLOCATION LENGTH field is defined in 4.2.5.6. The allocation length should be at least four.

The CONTROL byte is defined in SAM-5.

474 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The format of the parameter data for the REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS
command depends on the value of the REPD bit as follows:

a) if the REPD bit is set to zero, the REPORT SUPPORTED TASK MANAGEMENT FUNCTION
parameter data returned is shown in table 302; and
b) if the REPD bit is set to one, the REPORT SUPPORTED TASK MANAGEMENT FUNCTION
parameter data returned is shown in table 303.

The REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS basic parameter data format is shown in
table 302.

Table 302 — REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS basic parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0 ATS ATSS CACAS CTSS LURS QTS Obsolete Obsolete
1 Reserved QAES QTSS ITNRS

2 Reserved
3 REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS ADDITIONAL DATA LENGTH (00h)

The REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS extended parameter data format is shown
in table 303.

Table 303 — REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS extended parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0 ATS ATSS CACAS CTSS LURS QTS Obsolete Obsolete
1 Reserved QAES QTSS ITNRS

2 Reserved
3 REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS ADDITIONAL DATA LENGTH (0Ch)
4 Reserved TMFTMOV

5 Reserved
6 ATTS ATSTS CACATS CTSTS LURTS QTTS Reserved Reserved
7 Reserved QAETS QTSTS ITNRTS

8 (MSB)
•• • TASK MANAGEMENT FUNCTIONS LONG TIMEOUT
11 (LSB)
12 (MSB)
•• • TASK MANAGEMENT FUNCTIONS SHORT TIMEOUT
15 (LSB)

An ABORT TASK supported (ATS) bit set to one indicates the ABORT TASK task management function (see
SAM-5) is supported by the logical unit. An ATS bit set to zero indicates the ABORT TASK task management
function is not supported.

Working Draft SCSI Primary Commands - 4 (SPC-4) 475

T10/BSR INCITS 513 Revision 37 17 May 2014

An ABORT TASK SET supported (ATSS) bit set to one indicates the ABORT TASK SET task management
function (see SAM-5) is supported by the logical unit. An ATSS bit set to zero indicates the ABORT TASK SET
task management function is not supported.

A CLEAR ACA supported (CACAS) bit set to one indicates the CLEAR ACA task management function (see
SAM-5) is supported by the logical unit. A CACAS bit set to zero indicates the CLEAR ACA task management
function is not supported.

A CLEAR TASK SET supported (CTSS) bit set to one indicates the CLEAR TASK SET task management
function (see SAM-5) is supported by the logical unit. A CTSS bit set to zero indicates the CLEAR TASK SET
task management function is not supported.

A LOGICAL UNIT RESET supported ( LURS ) bit set to one indicates the LOGICAL UNIT RESET task
management function (see SAM-5) is supported by the logical unit. An LURS bit set to zero indicates the
LOGICAL UNIT RESET task management function is not supported.

A QUERY TASK supported (QTS) bit set to one indicates the QUERY TASK task management function (see
SAM-5) is supported by the logical unit. A QTS bit set to zero indicates the QUERY TASK task management
function is not supported.

A QU ERY ASY NCHR ON OUS EVENT supported ( Q A E S ) bit set to one indicates the QUERY
ASYNCHRONOUS EVENT task management function (see SAM-5) is supported by the logical unit. A QAES
bit set to zero indicates the QUERY ASYNCHRONOUS EVENT task management function is not supported.

A QUERY TASK SET supported (QTSS) bit set to one indicates the QUERY TASK SET task management
function (see SAM-5) is supported by the logical unit. A QTSS bit set to zero indicates the QUERY TASK SET
task management function is not supported.

An I_T NEXUS RESET supported (ITNRS) bit set to one indicates the I_T NEXUS RESET task management
function (see SAM-5) is supported by the logical unit. An ITNRS bit set to zero indicates the I_T NEXUS
RESET task management function is not supported.

The REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS ADDITIONAL DATA LENGTH field indicates the number of
bytes that follow in the parameter data. The contents of the REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS
ADDITIONAL DATA LENGTH field are not altered based on the allocation length (see 4.2.5.6).

A task management function timeouts valid ( TMFTMOV) bit set to one indicates the contents of the TASK
MANAGEMENT FUNCTIONS SHORT TIMEOUT field and TASK MANAGEMENT FUNCTIONS LONG TIMEOUT field are valid.
A TMFTMOV bit set to zero indicates the contents of the TASK MANAGEMENT FUNCTIONS SHORT TIMEOUT field and
TASK MANAGEMENT FUNCTIONS LONG TIMEOUT field are not valid and should be ignored.

An ABORT TASK timeout selector (ATTS) bit set to one indicates that the value in the TASK MANAGEMENT
FUNCTIONS SHORT TIMEOUT field applies to the ABORT TASK task management function. An ATTS bit set to
zero indicates that the value in the TASK MANAGEMENT FUNCTIONS LONG TIMEOUT field applies to the ABORT
TASK task management function.

An ABORT TASK SET timeout selector (ATSTS) bit set to one indicates that the value in the TASK MANAGEMENT
FUNCTIONS SHORT TIMEOUT field applies to the ABORT TASK SET task management function. An ATSTS bit set
to zero indicates that the value in the TASK MANAGEMENT FUNCTIONS LONG TIMEOUT field applies to the ABORT
TASK SET task management function.

A CLEAR ACA timeout selector (CACATS) bit set to one indicates that the value in the TASK MANAGEMENT
FUNCTIONS SHORT TIMEOUTfield applies to the CLEAR ACA task management function. A CACATS bit set to

476 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

zero indicates that the value in the TASK MANAGEMENT FUNCTIONS LONG TIMEOUT field applies to the CLEAR
ACA task management function.

A CLEAR TASK SET timeout selector (CTSTS) bit set to one indicates that the value in the TASK MANAGEMENT
FUNCTIONS SHORT TIMEOUT field applies to the CLEAR TASK SET task management function. A CTSTS bit set
to zero indicates that the value in the TASK MANAGEMENT FUNCTIONS LONG TIMEOUT field applies to the CLEAR
TASK SET task management function.

A LOGICAL UNIT RESET timeout selector ( LURTS ) bit set to one indicates that the value in the TASK
MANAGEMENT FUNCTIONS SHORT TIMEOUT field applies to the LOGICAL UNIT RESET task management
function. A LURTS bit set to zero indicates that the value in the TASK MANAGEMENT FUNCTIONS LONG TIMEOUT
field applies to the LOGICAL UNIT RESET task management function.

A QUERY TASK timeout selector (QTTS) bit set to one indicates that the value in the TASK MANAGEMENT
FUNCTIONS SHORT TIMEOUT field applies to the QUERY TASK task management function. A QTTS bit set to zero
indicates that the value in the TASK MANAGEMENT FUNCTIONS LONG TIMEOUT field applies to the QUERY TASK
task management function.

A QUERY ASYNCHRONOUS EVENT timeout selector (QAETS) bit set to one indicates that the value in the
TASK MANAGEMENT FUNCTIONS SHORT TIMEOUT field applies to the QUERY ASYNCHRONOUS EVENT task
management function. A QAETS bit set to zero indicates that the value in the TASK MANAGEMENT FUNCTIONS
LONG TIMEOUT field applies to the QUERY ASYNCHRONOUS EVENT task management function.

A QUERY TASK SET timeout selector (QTSTS) bit set to one indicates that the value in the TASK MANAGEMENT
FUNCTIONS SHORT TIMEOUT field applies to the QUERY TASK SET task management function. A QTSTS bit set
to zero indicates that the value in the TASK MANAGEMENT FUNCTIONS LONG TIMEOUT field applies to the QUERY
TASK SET task management function.

An I_T NEXUS RESET timeout selector ( ITNRTS ) bit set to one indicates that the value in the TASK
MANAGEMENT FUNCTIONS SHORT TIMEOUT field applies to the I_T NEXUS RESET task management function.
An ITNRTS bit set to zero indicates that the value in the TASK MANAGEMENT FUNCTIONS LONG TIMEOUT field
applies to the I_T NEXUS RESET task management function.

If the TMFTMOV bit is set to one and the TASK MANAGEMENT FUNCTIONS LONG TIMEOUT field is not set to zero,
then the contents of the TASK MANAGEMENT FUNCTIONS LONG TIMEOUT field indicate the recommended time in
100 millisecond increments that the application client should wait prior to timing out a task management
function for which the applicable selector bit is set to zero. If the TMFTMOV bit is set to zero or the TASK
MANAGEMENT FUNCTIONS LONG TIMEOUT field is set to zero, then the recommended timeout is unspecified for
any task management function for which the applicable selector bit is set to zero.

If the TMFTMOV bit is set to one and the TASK MANAGEMENT FUNCTIONS SHORT TIMEOUT field is not set to zero,
then the contents of the TASK MANAGEMENT FUNCTIONS SHORT TIMEOUT field indicate the recommended time in
100 millisecond increments that the application client should wait prior to timing out a task management
function for which the applicable selector bit is set to one. If the TMFTMOV bit is set to zero or the TASK
MANAGEMENT FUNCTIONS SHORT TIMEOUT field is set to zero, then the recommended timeout is unspecified for
any task management function for which the applicable selector bit is set to one.

Working Draft SCSI Primary Commands - 4 (SPC-4) 477

T10/BSR INCITS 513 Revision 37 17 May 2014

6.37 REPORT TARGET PORT GROUPS command

The REPORT TARGET PORT GROUPS command (see table 304) requests the device server to return target
port group information. This command uses the MAINTENANCE IN CDB format (see 4.2.2.3.3). This
command shall be supported by logical units that report in the standard INQUIRY data (see 6.6.2) that they
support asymmetric logical unit access (i.e., return a non-zero value in the TPGS field).

Table 304 — REPORT TARGET PORT GROUPS command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A3h)
1 PARAMETER DATA FORMAT SERVICE ACTION (0Ah)
2
•• • Reserved
5
6 (MSB)
•• • ALLOCATION LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 304 for the REPORT
TARGET PORT GROUPS command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 304 for the REPORT
TARGET PORT GROUPS command.

The PARAMETER DATA FORMAT field (see table 305) specifies the requested format for the parameter data
returned by the REPORT TARGET PORT GROUPS command. The device server may ignore the PARAMETER
DATA FORMAT field. If the device server ignores the PARAMETER DATA FORMAT field, the device server shall
return the parameter data format defined in table 306.

Table 305 — PARAMETER DATA FORMAT field

Code Description Reference

000b Length only header parameter data format table 306
001b Extended header parameter data format table 307
010b to 111b Reserved

The ALLOCATION LENGTH field is defined in 4.2.5.6.

The CONTROL byte is defined in SAM-5.

Returning REPORT TARGET PORT GROUPS parameter data may require the enabling of a nonvolatile
memory. If the nonvolatile memory is not ready, the device server shall terminate the command with CHECK
CONDITION status, rather than wait for the nonvolatile memory to become ready. The sense key shall be set
to NOT READY and the additional sense code shall be set as described in table 336 (see 6.47).

478 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The length only header format of the parameter data for the REPORT TARGET PORT GROUPS command is
shown in table 306.

Table 306 — Length only header parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • RETURN DATA LENGTH (n-3)
3 (LSB)
Target port group descriptor list
4
•• • Target port group descriptor (see table 308) [first]

•
••

•• • Target port group descriptor (see table 308) [last]

n

The RETURN DATA LENGTH field indicates the length in bytes of the list of target port group descriptors. The
contents of the RETURN DATA LENGTH field are not altered based on the allocation length (see 4.2.5.6).

There shall be one target port group descriptor (see table 308) for each target port group.

Working Draft SCSI Primary Commands - 4 (SPC-4) 479

T10/BSR INCITS 513 Revision 37 17 May 2014

The extended header format of the parameter data for the REPORT TARGET PORT GROUPS command is
shown in table 307.

Table 307 — Extended header parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • RETURN DATA LENGTH (n-3)
3 (LSB)
4 Reserved RTPG_FMT (001b) Reserved
5 IMPLICIT TRANSITION TIME

6
Reserved
7
Target port group descriptor list
8
•• • Target port group descriptor (see table 308) [first]

••
•

•• • Target port group descriptor (see table 308) [last]

n

The RETURN DATA LENGTH field indicates the length in bytes of the list of target port groups. The contents of the
RETURN DATA LENGTH field are not altered based on the allocation length (see 4.2.5.6).

The report target port groups format (RTPG_FMT) field indicates the returned parameter data format and shall
be set as shown in table 307 for the extended header parameter data format.

The IMPLICIT TRANSITION TIME field indicates the minimum amount of time in seconds the application client
should wait prior to timing out an implicit state transition (see 5.15.2.2). A value of zero indicates that the
implicit transition time is not specified.

480 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

There shall be one target port group descriptor (see table 308) for each target port group.

Table 308 — Target port group descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 PREF RTPG_FMT (000b) ASYMMETRIC ACCESS STATE

1 T_SUP O_SUP Reserved LBD_SUP U_SUP S_SUP AN_SUP AO_SUP

2 (MSB)
TARGET PORT GROUP
3 (LSB)
4 Reserved
5 STATUS CODE

6 Vendor specific
7 TARGET PORT COUNT

Target port descriptor list

8
•• • Target port descriptor (see table 311) [first]
11
••
•
n-3
•• • Target port descriptor (see table 311) [last]
n

A preferred target port (PREF) bit set to one indicates that the primary target port group is a preferred primary
target port group for accessing the addressed logical unit (see 5.15.2.6). A PREF bit set to zero indicates the
primary target port group is not a preferred primary target port group.

The RTPG_FMT field indicates the returned parameter data format and shall be set as shown in table 308 for
the target port group descriptor format.

The ASYMMETRIC ACCESS STATE field (see table 309) contains the target port group's target port asymmetric
access state (see 5.15.2.7).

Table 309 — ASYMMETRIC ACCESS STATE field

Code State Type (see 5.15.2.1) Reference

0h Active/optimized Primary 5.15.2.4.2
1h Active/non-optimized Primary 5.15.2.4.3
2h Standby Primary 5.15.2.4.4
3h Unavailable Primary 5.15.2.4.5
4h Logical block dependent Primary 5.15.2.4.7
5h to Dh Reserved
Eh Offline Secondary 5.15.2.4.6
Fh Transitioning between states Primary 5.15.2.5

Working Draft SCSI Primary Commands - 4 (SPC-4) 481

T10/BSR INCITS 513 Revision 37 17 May 2014

If any of the T_SUP bit, O_SUP bit, LBD_SUP bit, U_SUP bit, S_SUP bit, AN_SUP bit, or AO_SUP bit are set to one,
then the T_SUP bit, O_SUP bit, LBD_SUP bit, U_SUP bit, S_SUP bit, AN_SUP bit, and AO_SUP bit are as defined in
this standard. If the T_SUP bit, O_SUP bit, U_SUP bit, S_SUP bit, AN_SUP bit, and AO_SUP bit are all set to zero,
then which target port asymmetric access states are supported is vendor specific.

A transitioning supported (T _SUP) bit set to one indicates that the device server supports returning the
ASYMMETRIC ACCESS STATE field set to Fh (i.e., transitioning between states). A T_SUP bit set to zero indicates
that the device server does not return an ASYMMETRIC ACCESS STATE field set to Fh.

An offline supported (O_SUP) bit set to one indicates that the offline secondary target port asymmetric access
state is supported. A O_SUP bit set to zero indicates that the offline secondary target port asymmetric access
state is not supported.

A logical block dependent (LBD_SUP) bit set to one indicates that the logical block dependent primary target
port asymmetric access state is supported. An LBD _ SUP bit set to zero indicates that the logical block
dependent primary target port asymmetric access state is not supported.

An unavailable supported (U_SUP) bit set to one indicates that the unavailable primary target port asymmetric
access state is supported. A U _ SUP bit set to zero indicates that the unavailable primary target port
asymmetric access state is not supported.

A standby supported (S_SUP) bit set to one indicates that the standby primary target port asymmetric access
state is supported. An S_SUP bit set to zero indicates that the standby primary target port asymmetric access
state is not supported.

An active/non-optimized supported (AN_SUP) bit set to one indicates that the active/non-optimized primary
target port asymmetric access state is supported. An AN _ SUP bit set to zero indicates that the
active/non-optimized primary target port asymmetric access state is not supported.

An active/optimized supported (AO_SUP) bit set to one indicates that the active/optimized primary target port
asymmetric access state is supported. An AO_SUP bit set to zero indicates that the active/optimized primary
target port asymmetric access state is not supported.

The TARGET PORT GROUP field contains an identification of the target port group (see 5.15) described by this
target port group descriptor. Target port group information is also returned in the Device Identification VPD
page (see 7.8.6).

The STATUS CODE field (see table 310) indicates why a target port group may be in a specific target port
asymmetric access state.

Table 310 — STATUS CODE field

Code Description
00h No status available.
01h The target port asymmetric access state altered by SET
TARGET PORT GROUPS command.
02h The target port asymmetric access state altered by implicit
asymmetrical logical unit access behavior.
03h to FFh Reserved

482 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The TARGET PORT COUNT field indicates the number of target ports that are in that target port group and the
number of target port descriptors in the target port group descriptor. Every target port group shall contain at
least one target port. The target port group descriptor shall include one target port descriptor for each target
port in the target port group.

The format of each target port descriptor is shown in table 311.

Table 311 — Target port descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0
Reserved
1
2 (MSB)
RELATIVE TARGET PORT IDENTIFIER
3 (LSB)

The RELATIVE TARGET PORT IDENTIFIER field (see 4.3.4) indicates a relative port identifier of a target port in the
target port group.

6.38 REPORT TIMESTAMP command

The REPORT TIMESTAMP command (see table 312) requests the device server to return the current value of
a device clock (see 5.2). This command uses the MAINTENANCE IN CDB format (see 4.2.2.3.3).

Table 312 — REPORT TIMESTAMP command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A3h)
1 Reserved SERVICE ACTION (0Fh)
2
•• • Reserved
5
6 (MSB)
•• • ALLOCATION LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 312 for the REPORT
TIMESTAMP command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 312 for the REPORT
TIMESTAMP command.

The ALLOCATION LENGTH field is defined in 4.2.5.6.

Working Draft SCSI Primary Commands - 4 (SPC-4) 483

T10/BSR INCITS 513 Revision 37 17 May 2014

The CONTROL byte is defined in SAM-5.

The format for the parameter data for the REPORT TIMESTAMP command is shown in table 313.

Table 313 — REPORT TIMESTAMP parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
TIMESTAMP PARAMETER DATA LENGTH (000Ah)
1 (LSB)
2 Reserved TIMESTAMP ORIGIN

3 Reserved
4 (MSB)
•• • TIMESTAMP
9 (LSB)
10 Reserved
11 Reserved

The TIMESTAMP PARAMETER DATA LENGTH field indicates the number of bytes of parameter data that follow. The
contents of the TIMESTAMP PARAMETER DATA LENGTH field are not altered based on the allocation length (see
4.2.5.6).

The TIMESTAMP ORIGIN field indicates the most recent event that initialized the returned device clock using the
values shown in table 57 (see 5.2).

The TIMESTAMP field contains the current value of a device clock (see 5.2).

6.39 REQUEST SENSE command

The REQUEST SENSE command (see table 314) requests the device server to return parameter data that
contains sense data (see 4.5).

Table 314 — REQUEST SENSE command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (03h)
1 Reserved DESC

2
Reserved
3
4 ALLOCATION LENGTH

5 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 314 for the REQUEST
SENSE command.

484 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The descriptor format (DESC) bit (see table 315) specifies which sense data format the device server shall
return in the parameter data.

Table 315 — DESC bit

Code Descriptor format sense Description

data supported?
The device server shall return fixed format sense data (see
0b yes or no
4.5.3) in the parameter data.
The device server shall return descriptor format sense data
yes
(see 4.5.2) in the parameter data.
The device server shall return no parameter data and shall
1b terminate the REQUEST SENSE command with CHECK
no CONDITION status with the sense key set to ILLEGAL
REQUEST and the additional sense code set to INVALID
FIELD IN CDB.
Note: Device servers that are compliant with SPC-3 are capable of ignoring a DESC bit that is set to one.

The ALLOCATION LENGTH field is defined in 4.2.5.6. Application clients should request 252 bytes of sense data
to ensure they retrieve all the sense data. If fewer than 252 bytes are requested, sense data may be lost since
the REQUEST SENSE command with any allocation length clears the sense data.

The CONTROL byte is defined in SAM-5.

Sense data shall be available and cleared under the conditions defined in SAM-5.

Upon completion of the REQUEST SENSE command, the logical unit shall be in the same power condition
(see 5.11) that was active before the REQUEST SENSE command was received. A REQUEST SENSE
command shall not reset any power condition timers.

The device server shall return CHECK CONDITION status for a REQUEST SENSE command only to report
exception conditions specific to the REQUEST SENSE command itself. Examples of conditions that cause a
REQUEST SENSE command to return CHECK CONDITION status are:

a) an invalid field value is detected in the CDB;

b) the device server does not support the REQUEST SENSE command (see 4.2.1);
c) the initiator port that sent the REQUEST SENSE command is pending enrollment for access controls
(see 8.3.1.7) and no other sense data is available to return;
d) an unrecovered error is detected by a SCSI target port; or
e) a malfunction prevents return of the sense data.

If a REQUEST SENSE command is terminated with CHECK CONDITION status, then:

a) any parameter data that is transferred is invalid (i.e., the parameter data does not contain sense data);
and
b) if the REQUEST SENSE command was received on an I_T nexus with a pending unit attention
condition (i.e., before the device server reports CHECK CONDITION status), then the device server
shall not clear the pending unit attention condition (see SAM-5).

The REQUEST SENSE command shall be capable of being processed to completion with GOOD status in
any power condition (see 5.11). However, some implementations may require a level of power consumption

Working Draft SCSI Primary Commands - 4 (SPC-4) 485

T10/BSR INCITS 513 Revision 37 17 May 2014

that is higher than associated with the current power condition in any other circumstance. Details of how much
power processing a REQUEST SENSE command requires is outside the scope of this standard.

Except as described elsewhere in this subclause, the device server shall process a REQUEST SENSE
command as follows:

1) return applicable sense data in the parameter data as follows:

1) if the logical unit that reports a peripheral qualifier of 011b or 001b in its standard INQUIRY data
(see 6.6.2), then return parameter data containing sense data with the sense key set to ILLEGAL
REQUEST and the additional sense code shall be set to LOGICAL UNIT NOT SUPPORTED;
2) if the logical unit that reports a peripheral qualifier of 000b in its standard INQUIRY data because
it has a peripheral device connected but is not ready for access, then return parameter data
containing sense data appropriate to the condition that is making the logical unit not operational;
3) if the REQUEST SENSE command was received on an I_T nexus with a pending unit attention
condition, then return parameter data containing sense data for the unit attention and clear the
unit attention condition as described in SAM-5;
4) if a recovered error occurs during the processing of the REQUEST SENSE command, then return
parameter data containing sense data with the sense key set to RECOVERED ERROR;
5) if deferred error sense data (see 4.5.7) is available, then return parameter data containing sense
data for the deferred error;
6) return pollable sense data (see 5.10.2), if any; or
7) return parameter data containing sense data with the sense key set to NO SENSE and the
additional sense code set to NO ADDITIONAL SENSE INFORMATION;
and
2) complete the REQUEST SENSE command with GOOD status.

Device servers shall return at least 18 bytes of parameter data in response to a REQUEST SENSE command
if the allocation length is 18 or greater and the DESC bit is set to zero. Application clients may determine how
much sense data has been returned by examining the ALLOCATION LENGTH field in the CDB and the ADDITIONAL
SENSE LENGTH field in the sense data. Device servers shall not adjust the additional sense length to reflect
truncation if the allocation length is less than the sense data available.

486 Working Draft SCSI Primary Commands - 4 (SPC-4)

T10/BSR INCITS 513 Revision 37 17 May 2014

6.40 SECURITY PROTOCOL IN command

The SECURITY PROTOCOL IN command (see table 316) requests the device server to return security
protocol information (see 7.7.1) or the results of one or more SECURITY PROTOCOL OUT commands (see
6.41).

Table 316 — SECURITY PROTOCOL IN command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A2h)
1 SECURITY PROTOCOL

2
SECURITY PROTOCOL SPECIFIC
3
4 INC_512 Reserved
5 Reserved
6 (MSB)
•• • ALLOCATION LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 316 for the SECURITY
PROTOCOL IN command.

488 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The SECURITY PROTOCOL field (see table 317) specifies which security protocol is being used.

Table 317 — SECURITY PROTOCOL field in SECURITY PROTOCOL IN command

Code Description Reference

00h Security protocol information 7.7.1
01h to 06h Defined by TCG 3.1.179
07h CbCS 7.7.4
08h to 1Fh Reserved
20h Tape Data Encryption SSC-4
21h Data Encryption Configuration ADC-3
22h to 3Fh Reserved
40h SA Creation Capabilities 7.7.2
41h IKEv2-SCSI 7.7.3
42h to EAh Reserved
EBh Defined by SCSA 3.1.147
ECh JEDEC Universal Flash Storage UFS
EDh SDcard TrustedFlash Security 3.1.148
Systems Specification 1.1.3
EEh Authentication in Host Attachments IEEE 1667
of Transient Storage Devices
EFh ATA Device Server Password SAT-3
F0h to FFh Vendor Specific

The contents of the SECURITY PROTOCOL SPECIFIC field are defined by the protocol specified by the SECURITY
PROTOCOL field (see table 317).

A 512 increment (INC_512) bit set to one specifies that the ALLOCATION LENGTH field (see 4.2.5.6) expresses the
maximum number of bytes available to receive data in increments of 512 bytes (e.g., a value of one means
512 bytes, two means 1 024 bytes, etc.). Pad bytes may or may not be appended to meet this length. Pad
bytes shall have a value of 00h. An INC_512 bit set to zero specifies that the ALLOCATION LENGTH field
expresses the maximum number of bytes available to receive data in increments of one byte.

Indications of data overrun or underrun and the mechanism, if any, for processing retries are defined by the
protocol specified by the SECURITY PROTOCOL field (see table 317).

The CONTROL byte is defined in SAM-5.

Any association between a previous SECURITY PROTOCOL OUT command and the data transferred by a
SECURITY PROTOCOL IN command depends on the protocol specified by the SECURITY PROTOCOL field (see
table 317). If the device server has no data to transfer (e.g., the results for any previous SECURITY
PROTOCOL OUT commands are not yet available), then the device server may transfer data indicating it has
no other data to transfer.

The format of the data transferred depends on the protocol specified by the SECURITY PROTOCOL field (see
table 317).

Working Draft SCSI Primary Commands - 4 (SPC-4) 489

T10/BSR INCITS 513 Revision 37 17 May 2014

The device server shall retain data resulting from a SECURITY PROTOCOL OUT command, if any, until one
of the following events is processed:

a) transfer of the data via a SECURITY PROTOCOL IN command from the same I_T_L nexus as
defined by the protocol specified by the SECURITY PROTOCOL field (see table 317);
b) logical unit reset (see SAM-5); or
c) I_T nexus loss (see SAM-5) associated with the I_T nexus that sent the SECURITY PROTOCOL
OUT command.

6.41 SECURITY PROTOCOL OUT command

The SECURITY PROTOCOL OUT command (see table 318) requests the device server to process the
specified parameter list using the specified security protocol. Depending on the protocol specified by the
SECURITY PROTOCOL field, the application client may use the SECURITY PROTOCOL IN command (see 6.40)
to retrieve data that results from the processing of one or more SECURITY PROTOCOL OUT commands.

Table 318 — SECURITY PROTOCOL OUT command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (B5h)
1 SECURITY PROTOCOL

2
SECURITY PROTOCOL SPECIFIC
3
4 INC_512 Reserved
5 Reserved
6 (MSB)
•• • TRANSFER LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 318 for the SECURITY
PROTOCOL OUT command.

490 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The SECURITY PROTOCOL field (see table 319) specifies which security protocol is being used.

Table 319 — SECURITY PROTOCOL field in SECURITY PROTOCOL OUT command

Code Description Reference

00h Reserved
01h to 06h Defined by TCG 3.1.179
07h CbCS 7.7.4
08h to 1Fh Reserved
20h Tape Data Encryption SSC-4
21h Data Encryption Configuration ADC-3
22h to 40h Reserved
41h IKEv2-SCSI 7.7.3
42h to EAh Reserved
EBh Defined by SCSA 3.1.147
ECh JEDEC Universal Flash Storage UFS
EDh SDcard TrustedFlash Security 3.1.148
Systems Specification 1.1.3
EEh Authentication in Host Attachments IEEE 1667
of Transient Storage Devices
EFh ATA Device Server Password SAT-3
F0h to FFh Vendor Specific

The contents of the SECURITY PROTOCOL SPECIFIC field are defined by the protocol specified by the SECURITY
PROTOCOL field (see table 319).

A 512 increment (INC_512) bit set to one specifies that the TRANSFER LENGTH field (see 4.2.5.4) expresses the
number of bytes to be transferred in increments of 512 bytes (e.g., a value of one means 512 bytes, two
means 1 024 bytes, etc.). Pad bytes shall be appended as needed to meet this requirement. Pad bytes shall
have a value of 00h. A INC_512 bit set to zero specifies that the TRANSFER LENGTH field indicates the number of
bytes to be transferred.

The CONTROL byte is defined in SAM-5.

Any association between a SECURITY PROTOCOL OUT command and a subsequent SECURITY
PROTOCOL IN command is defined by the protocol specified by the SECURITY PROTOCOL field (see table 319).
Each protocol shall define whether:

a) the device server shall complete the command with GOOD status as soon as it determines the data
has been correctly received. An indication that the data has been processed is obtained by sending a
SECURITY PROTOCOL IN command and receiving the results in the associated data transfer; or
b) the device server shall complete the command with GOOD status only after the data has been
successfully processed and an associated SECURITY PROTOCOL IN command is not required.

The format of the data transferred depends on the protocol specified by the SECURITY PROTOCOL field (see
table 319).

Working Draft SCSI Primary Commands - 4 (SPC-4) 491

T10/BSR INCITS 513 Revision 37 17 May 2014

6.42 SEND DIAGNOSTIC command

The SEND DIAGNOSTIC command (see table 320) requests the device server to perform diagnostic
operations on the SCSI target device, on the logical unit, or on both. Logical units that support this command
shall support, at a minimum, the default self-test feature (i.e., the SELFTEST bit equal to one and a parameter
list length of zero).

Table 320 — SEND DIAGNOSTIC command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (1Dh)
1 SELF-TEST CODE PF Reserved SELFTEST DEVOFFL UNITOFFL
2 Reserved
3 (MSB)
PARAMETER LIST LENGTH
4 (LSB)
5 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 320 for the SEND
DIAGNOSTIC command.

492 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The SELF-TEST CODE field is defined in table 321 and further described in table 322.

Table 321 — SELF-TEST CODE field

Code Name Description

000b This value is used if an operation not described in this table is being
requested (see table 322).
001b Background The device server shall start its short self-test (see 5.14.3) in the background
short self-test mode (see 5.14.4.3).
010b Background The device server shall start its extended self-test (see 5.14.3) in the back-
extended self-test ground mode (see 5.14.4.3).
011b Reserved
100b Abort background If the SCSI target device is performing a self-test in the background mode
self-test (see 5.14.4.3), then the device server shall abort the self-test. If the target
device is performing a self-test in the foreground mode, then the device
server shall process the command as described in 5.14.4.2. a If the target
device is not performing a self-test, then the device server shall terminate
the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD
IN CDB.
101b Foreground The device server shall start its short self-test (see 5.14.3) in the foreground
short self-test mode (see 5.14.4.2).
110b Foreground The device server shall start its extended self-test (see 5.14.3) in the fore-
extended self-test ground mode (see 5.14.4.2).
111b Reserved
a
Device servers compliant with SPC-3 may terminate the command with CHECK CONDITION status
with the sense key set to ILLEGAL REQUEST and the additional sense code set to INVALID FIELD IN
CDB.

The page format (PF) bit (see table 322) specifies the format of any parameter list sent by the application client
for a SEND DIAGNOSTIC command and may specify the format of the parameter data, if any, returned by the
device server in response to a subsequent RECEIVE DIAGNOSTIC RESULTS command (see 6.27).

NOTE 35 - Logical units compliant with SPC-2 may transfer more than one diagnostic page in the SEND
DIAGNOSTIC command’s parameter list and by doing so may request that more than one diagnostic page be
sent in the RECEIVE DIAGNOSTIC RESULTS command’s parameter data.

The self-test (SELFTEST) bit (see table 322) specifies whether the device server shall perform the default
self-test (see 5.14.2).

A SCSI target device offline (DEVOFFL) bit set to one specifies that the device server may perform a default
self-test (see 5.14.2) that affects any logical unit in the SCSI target device (e.g., by alteration of reservations,
log parameters, or sense data). A D EV O FF L bit set to zero specifies that, after the device server has
completed a default self-test specified in the SEND DIAGNOSTIC command, no logical unit shall exhibit any
effects resulting from the device server’s processing the SEND DIAGNOSTIC command that are detectable
by any application client. If the SELFTEST bit is set to zero, the device server shall ignore the DEVOFFL bit.

A unit offline (UNITOFFL) bit set to one specifies that the device server may perform a default self-test (see
5.14.2) that affects the user accessible medium on the logical unit (e.g., write operations to the user
accessible medium or repositioning of the medium on sequential access devices). A UNITOFFL bit set to zero

Working Draft SCSI Primary Commands - 4 (SPC-4) 493

T10/BSR INCITS 513 Revision 37 17 May 2014

specifies that, after the device server has completed a default self-test specified in the SEND DIAGNOSTIC
command, the user accessible medium shall exhibit no effects resulting from the device server’s processing
the SEND DIAGNOSTIC command that are detectable by any application client. If the SELFTEST bit is set to
zero, the device server shall ignore the UNITOFFL bit.

The PARAMETER LIST LENGTH field (see table 322) specifies the length in bytes of the parameter list that shall
be transferred from the application client Data-Out Buffer to the device server. A parameter list length of zero
specifies that no data shall be transferred. This condition shall not be considered an error.

The CONTROL byte is defined in SAM-5.

494 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 322 defines:

a) the combinations of values for the SELF-TEST CODE field, the PF bit, if supported, the SELFTEST bit, and
the PARAMETER LIST LENGTH field; and
b) under which conditions the DEVOFFL bit and the UNITOFFL bit, if supported, may be used and under
which conditions these bits are ignored.

Table 322 — The meanings of the SELF-TEST CODE field, the PF bit, the SELFTEST bit, and the
PARAMETER LIST LENGTH field (part 1 of 4)

SELF- PARA-
TEST SELF METER LIST
CODE PF TEST LENGTH
field bit bit field Description a, b
000b 0 0 0000h The device server shall complete the command with GOOD status.
The device server shall transfer the amount of vendor specific
parameter list specified by the PARAMETER LIST LENGTH field.
If the parameter list is valid and requests that the device server
perform a diagnostic operation c, then:
a) if the operation succeeds, the device server shall complete the
command with GOOD status;
b) if the operation fails, then the device server shall terminate the
command with CHECK CONDITION status with the sense key
set to HARDWARE ERROR and the additional sense code set
to the appropriate value to describe the failure; and
c) if parameter data is required to be returned by the device server
000b 0 0 0000h for the operation, then a subsequent RECEIVE DIAGNOSTIC
RESULTS command (see 6.27) determines the device server’s
response.
If the parameter list is valid and does not request the device server to
perform a diagnostic operation, then the device server processes the
vendor specific data. A subsequent RECEIVE DIAGNOSTIC
RESULTS command may be required for an application client to
determine the device server’s response.
If the parameter list is not valid, the device server shall terminate
the command with CHECK CONDITION status with the sense key set
to ILLEGAL REQUEST and the additional sense code set to INVALID
FIELD IN PARAMETER LIST.
a
Each description assumes that all other bits and fields in the CDB that are not defined for a particular
case are valid. If, in any case, some other bit or field in the CDB is not valid, the device server shall
terminate the command with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST
and the additional sense code set to INVALID FIELD IN CDB.
b The device server shall ignore the DEVOFFL bit and the UNITOFFL bit in all cases where their use is not

included in the description.

c Before beginning any self-test, the device server shall:

a) stop all running power condition timers;

b) not stop any process that results in a background function occuring (e.g., not stop any timers or
counters associated with background functions); and
c) after completing this command, the device server shall reinitialize and restart all enabled power
condition timers.

Working Draft SCSI Primary Commands - 4 (SPC-4) 495

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 322 — The meanings of the SELF-TEST CODE field, the PF bit, the SELFTEST bit, and the
PARAMETER LIST LENGTH field (part 2 of 4)

SELF- PARA-
TEST SELF METER LIST
CODE PF TEST LENGTH
field bit bit field Description a, b
The device server shall perform its default self-test, and if supported,
use the values in the DEVOFFL bit and the UNITOFFL bit for processing
the self-test.
If the self-test succeeds, the device server shall complete the
000b 0 1 0000h command with GOOD status.
If the self-test fails, the device server shall terminate the command with
CHECK CONDITION status with the sense key set to HARDWARE
ERROR and the additional sense code set to the appropriate value to
describe the failure.
The device server shall terminate the command with CHECK CONDI-
000b 0 1 0000h TION status with the sense key set to ILLEGAL REQUEST and the
additional sense code set to INVALID FIELD IN CDB.
The device server shall:
a) complete the command with GOOD status; and
b) if requested by a subsequent RECEIVE DIAGNOSTIC
RESULTS command, then:
000b 1 0 0000h A) if the PF bit is supported by the device server, return a single
diagnostic page (see 7.2) as specified by the command; or
B) if the PF bit is not supported by the device server, return
vendor specific parameter data as specified by the
command.
a Each description assumes that all other bits and fields in the CDB that are not defined for a particular
case are valid. If, in any case, some other bit or field in the CDB is not valid, the device server shall
terminate the command with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST
and the additional sense code set to INVALID FIELD IN CDB.
b
The device server shall ignore the DEVOFFL bit and the UNITOFFL bit in all cases where their use is not
included in the description.
c
Before beginning any self-test, the device server shall:
a) stop all running power condition timers;
b) not stop any process that results in a background function occuring (e.g., not stop any timers or
counters associated with background functions); and
c) after completing this command, the device server shall reinitialize and restart all enabled power
condition timers.

496 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 322 — The meanings of the SELF-TEST CODE field, the PF bit, the SELFTEST bit, and the
PARAMETER LIST LENGTH field (part 3 of 4)

SELF- PARA-
TEST SELF METER LIST
CODE PF TEST LENGTH
field bit bit field Description a, b
The device server shall transfer the amount of parameter list specified
by the PARAMETER LIST LENGTH field.
If the PF bit is supported by the device server, then:
a) the parameter list shall be a single diagnostic page; and
b) if the specified parameter list length results in the truncation of
the diagnostic page (e.g., the parameter list length is less than
the page length indicated by the diagnostic page), then the
device server shall terminate the command with CHECK
CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID
FIELD IN CDB.
If the PF bit is not supported by the device server, the parameter list is
vendor specific.
If the parameter list is valid and requests that the device server
perform a diagnostic operation c, then:
a) if the operation succeeds, the device server shall complete the
command with GOOD status;
000b 1 0 0000h
b) if the operation fails, the device server shall terminate the
command with CHECK CONDITION status with the sense key
set to HARDWARE ERROR and the additional sense code set
to the appropriate value to describe the failure; and
c) if parameter data is required to be returned by the device server
for the operation, then a subsequent RECEIVE DIAGNOSTIC
RESULTS command (see 6.27) determines the device server’s
response.
If the parameter list is valid and does not request the device server to
perform a diagnostic operation, then the device server processes the
data as defined in 7.2. A subsequent RECEIVE DIAGNOSTIC
RESULTS command may be required for an application client to
determine the device server’s response.
If the parameter list is not valid, the device server shall terminate
the command with CHECK CONDITION status with the sense key set
to ILLEGAL REQUEST and the additional sense code set to INVALID
FIELD IN PARAMETER LIST.
a
Each description assumes that all other bits and fields in the CDB that are not defined for a particular
case are valid. If, in any case, some other bit or field in the CDB is not valid, the device server shall
terminate the command with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST
and the additional sense code set to INVALID FIELD IN CDB.
b The device server shall ignore the DEVOFFL bit and the UNITOFFL bit in all cases where their use is not

included in the description.

c Before beginning any self-test, the device server shall:

a) stop all running power condition timers;

b) not stop any process that results in a background function occuring (e.g., not stop any timers or
counters associated with background functions); and
c) after completing this command, the device server shall reinitialize and restart all enabled power
condition timers.

Working Draft SCSI Primary Commands - 4 (SPC-4) 497

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 322 — The meanings of the SELF-TEST CODE field, the PF bit, the SELFTEST bit, and the
PARAMETER LIST LENGTH field (part 4 of 4)

SELF- PARA-
TEST SELF METER LIST
CODE PF TEST LENGTH
field bit bit field Description a, b
The device server shall terminate the command with CHECK CONDI-
000b 1 1 n/a TION status with the sense key set to ILLEGAL REQUEST and the
additional sense code set to INVALID FIELD IN CDB.
000b 0 0 0000h The device server shall perform the operation defined in table 321. c
000b 0 0 0000h The device server shall terminate the command with CHECK CONDI-
TION status with the sense key set to ILLEGAL REQUEST and the
000b 0 1 n/a additional sense code set to INVALID FIELD IN CDB.
The device server shall perform the operation defined in table 321. c
If the device server supports the PF bit, the device server shall return a
single diagnostic page as specified by the subsequent RECEIVE
000b 1 0 0000h DIAGNOSTIC RESULTS command, if any.
If the device server does not support the PF bit, the device server shall
return vendor specific data for a subsequent RECEIVE DIAGNOSTIC
RESULTS command, if any.
000b 1 0 0000h The device server shall terminate the command with CHECK CONDI-
TION status with the sense key set to ILLEGAL REQUEST and the
000b 1 1 n/a additional sense code set to INVALID FIELD IN CDB.
a Each description assumes that all other bits and fields in the CDB that are not defined for a particular
case are valid. If, in any case, some other bit or field in the CDB is not valid, the device server shall
terminate the command with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST
and the additional sense code set to INVALID FIELD IN CDB.
b
The device server shall ignore the DEVOFFL bit and the UNITOFFL bit in all cases where their use is not
included in the description.
c
Before beginning any self-test, the device server shall:
a) stop all running power condition timers;
b) not stop any process that results in a background function occuring (e.g., not stop any timers or
counters associated with background functions); and
c) after completing this command, the device server shall reinitialize and restart all enabled power
condition timers.

498 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.43 SET IDENTIFYING INFORMATION command

The SET IDENTIFYING INFORMATION command (see table 323) requests the device server to set
identifying information (see 5.6) in the logical unit to the value specified in the SET IDENTIFYING
INFORMATION parameter list. This command uses the MAINTENANCE OUT CDB format (see 4.2.2.3.4).
The SET IDENTIFYING INFORMATION command is an extension to the SET PERIPHERAL
DEVICE/COMPONENT DEVICE IDENTIFIER service action of the MAINTENANCE OUT command defined
in SCC-2.

Processing a SET IDENTIFYING INFORMATION command may require the enabling of a nonvolatile
memory within the logical unit. If the nonvolatile memory is not ready, the device server shall terminate the
command with CHECK CONDITION status, and not wait for the nonvolatile memory to become ready. The
sense key shall be set to NOT READY and the additional sense code shall be set as described in table 336
(see 6.47). This information should allow the application client to determine the action required to cause the
device server to become ready.

On successful completion of a SET IDENTIFYING INFORMATION command that changes identifying

information saved by the logical unit, the device server shall establish a unit attention condition (see SAM-5)
for the initiator port associated with every I_T nexus except the I_T nexus on which the SET IDENTIFYING
INFORMATION command was received, with the additional sense code set to DEVICE IDENTIFIER
CHANGED.

Table 323 — SET IDENTIFYING INFORMATION command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A4h)
1 Reserved SERVICE ACTION (06h)
2
Reserved
3
4
Restricted (see SCC-2)
5
6 (MSB)
•• • PARAMETER LIST LENGTH
9 (LSB)
10 IDENTIFYING INFORMATION TYPE Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 323 for the SET
IDENTIFYING INFORMATION command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 323 for the SET
IDENTIFYING INFORMATION command.

The PARAMETER LIST LENGTH field specifies the length in bytes of the identifying information that shall be
transferred from the application client to the device server. A parameter list length of zero specifies that no
data shall be transferred, and that subsequent REPORT IDENTIFYING INFORMATION commands shall
return the IDENTIFYING INFORMATION LENGTH field set to zero for the specified identifying information type.

Working Draft SCSI Primary Commands - 4 (SPC-4) 499

T10/BSR INCITS 513 Revision 37 17 May 2014

The IDENTIFYING INFORMATION TYPE field (see table 324) specifies the identifying information type to be set. If
the specified identifying information type is not implemented by the device server, then the device server shall
terminate the command with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST, and
the additional sense code set to INVALID FIELD IN CDB.

Table 324 — IDENTIFYING INFORMATION TYPE field

Code Description
0000000b Peripheral device identifying information (see 5.6).

If the PARAMETER LIST LENGTH field is set to a value greater than the maximum length of the
peripheral device identifying information supported by the device server (see 5.6), then the
device server shall terminate the command with CHECK CONDITION status with the sense
key set to ILLEGAL REQUEST and the additional sense code set to INVALID FIELD IN
CDB.
0000010b Peripheral device text identifying information (see 5.6).

If the PARAMETER LIST LENGTH field is set to a value greater than the maximum length of the
peripheral device text identifying information (see 5.6) supported by the device server, then
the device server shall terminate the command with CHECK CONDITION status with the
sense key set to ILLEGAL REQUEST and the additional sense code set to INVALID FIELD
IN CDB.

If the IDENTIFYING INFORMATION field does not contain a null-terminated (see 4.3.2) UTF-8
format string, then the device server shall terminate the command with CHECK CONDI-
TION status with the sense key set to ILLEGAL REQUEST and the additional sense code
set to INVALID FIELD IN PARAMETER LIST.
xxxxxx1b Restricted (see SCC-2)
All others Reserved

The CONTROL byte is defined in SAM-5.

The SET IDENTIFYING INFORMATION parameter list (see table 325) contains the identifying information to
be set by the device server.

Table 325 — SET IDENTIFYING INFORMATION parameter list

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • IDENTIFYING INFORMATION
n

The IDENTIFYING INFORMATION field specifies the identifying information to be set for the specified identifying
information type (see 5.6).

Upon successful completion of a SET IDENTIFYING INFORMATION command, the identifying information
that is saved by the logical unit shall persist through logical unit resets, hard resets, power loss, I_T nexus
losses, media format operations, and media replacement.

500 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.44 SET PRIORITY command

The SET PRIORITY command (see table 326) requests the device server to set the command priority (see
SAM-5) for commands received on the specified I_T nexus.. This command uses the MAINTENANCE OUT
CDB format (see 4.2.2.3.4). The command priority set by this command shall remain in effect until one of the
following occurs:

a) another SET PRIORITY command is received;

b) hard reset;
c) logical unit reset; or
d) power on.

The command priority set by this command shall not be affected by an I_T nexus loss.

Table 326 — SET PRIORITY command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A4h)
1 Reserved SERVICE ACTION (0Eh)
2 I_T_L NEXUS TO SET Reserved
3
•• • Reserved
5
6 (MSB)
•• • PARAMETER LIST LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 326 for the SET PRIORITY
command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 326 for the SET PRIORITY
command.

Working Draft SCSI Primary Commands - 4 (SPC-4) 501

T10/BSR INCITS 513 Revision 37 17 May 2014

The I_T_L NEXUS TO SET field (see table 327) specifies the I_T_L nexus and the location of the priority value to
be assigned to that I_T_L nexus.

Table 327 — I_T_L NEXUS TO SET field

Code Description
00b The priority for the I_T_L nexus associated with this command shall be set to the value con-
tained in the PRIORITY TO SET field in the SET PRIORITY parameter list (see table 328). All fields
in the SET PRIORITY parameter list except the PRIORITY TO SET field shall be ignored.
If the parameter list length is zero, the device server shall terminate the command with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense
code set to PARAMETER LIST LENGTH ERROR.
01b The priority for the I_T_L nexus specified by the logical unit that is processing this command, the
RELATIVE TARGET PORT IDENTIFIER field, and the TransportID in the SET PRIORITY parameter list
(see table 328) shall be set to the value specified by the PRIORITY TO SET field in the SET PRIOR-
ITY parameter list.
If the parameter list length results in the truncation of the RELATIVE TARGET PORT IDENTIFIER field,
the ADDITIONAL DESCRIPTOR LENGTH field, or the TransportID, then the device server shall termi-
nate the command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to PARAMETER LIST LENGTH ERROR.
On successful completion of a SET PRIORITY command the device server shall establish a unit
attention condition (see SAM-5) for the initiator port associated with the I_T nexus specified by
the TransportID and the RELATIVE TARGET PORT IDENTIFIER field, with the additional sense code
set to PRIORITY CHANGED.
10b The priority value specified in the INITIAL COMMAND PRIORITY field of the Control Extension mode
page (see 7.5.9) shall be used for all I_T_L nexuses associated with the logical unit that is pro-
cessing this command regardless of any prior priority. The contents of the SET PRIORITY
parameter list shall be ignored.
On successful completion of a SET PRIORITY command the device server shall establish a unit
attention condition (see SAM-5) for the initiator port associated with every other I_T_L nexus,
with the additional sense code set to PRIORITY CHANGED.
11b Reserved

The PARAMETER LIST LENGTH field specifies the length in bytes of the SET PRIORITY parameter list (see table
328) that shall be contained in the Data-Out Buffer. A parameter list length of zero specifies that the Data-Out
Buffer shall be empty. This condition shall not be considered an error.

The CONTROL byte is defined in SAM-5.

502 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The format of the parameter data for the SET PRIORITY command is shown in table 328.

Table 328 — SET PRIORITY parameter list format

Bit
7 6 5 4 3 2 1 0
Byte
0 Reserved PRIORITY TO SET

1 Reserved
2 (MSB)
RELATIVE TARGET PORT IDENTIFIER
3 (LSB)
4 Reserved
5 Reserved
6 (MSB)
ADDITIONAL LENGTH (n-7)
7 (LSB)
8
•• • TransportID
n

The PRIORITY TO SET field specifies the priority to be assigned to the I_T_L nexus specified by the I_T_L NEXUS
TO SET field in the CDB. The value in the PRIORITY TO SET field shall be returned in subsequent REPORT
PRIORITY commands (see 6.34) until one of the conditions described in this subclause occurs. A priority to
set value of zero specifies the I_T_L nexus specified by the I_T_L NEXUS TO SET field shall be set to the value
specified in the INITIAL COMMAND PRIORITY field of the Control Extension mode page (see 7.5.9). The contents
of the I_T_L NEXUS TO SET field may specify that the PRIORITY TO SET field shall be ignored.

The RELATIVE TARGET PORT IDENTIFIER field (see 4.3.4) specifies the relative port identifier of the target port that
is part of the I_T_L nexus for which the priority is to be set. The contents of the I_T_L NEXUS TO SET field may
specify that the RELATIVE TARGET PORT IDENTIFIER field shall be ignored.

The ADDITIONAL LENGTH field specifies the number of bytes that follow in the SET PRIORITY parameter list
(i.e., the size of the TransportID).

The TransportID specifies a TransportID (see 7.6.4) identifying the initiator port that is part of the I_T_L nexus
for which the priority is to be set. The contents of the I _ T _ L NEXUS TO SET field may specify that the
TRANSPORTID field shall be ignored.

6.45 SET TARGET PORT GROUPS command

The SET TARGET PORT GROUPS command (see table 329) requests the device server to set the primary
target port asymmetric access state of all of the target ports in the specified primary target port groups and/or
the secondary target port asymmetric access state of the specified target ports. This command uses the
MAINTENANCE OUT CDB format (see 4.2.2.3.4). See 5.15 for details regarding the transition between target
port asymmetric access states. This command is mandatory for all logical units that report in the standard

Working Draft SCSI Primary Commands - 4 (SPC-4) 503

T10/BSR INCITS 513 Revision 37 17 May 2014

INQUIRY data (see 6.6.2) that they support explicit asymmetric logical units access (i.e., the TPGS field is set
to either 10b or 11b).

Table 329 — SET TARGET PORT GROUPS command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A4h)
1 Reserved SERVICE ACTION (0Ah)
2
•• • Reserved
5
6 (MSB)
•• • PARAMETER LIST LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 329 for the SET TARGET
PORT GROUPS command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 329 for the SET TARGET
PORT GROUPS command.

The PARAMETER LIST LENGTH field specifies the length in bytes of the target port group management
parameters that shall be transferred from the application client to the device server. A parameter list length of
zero specifies that no data shall be transferred, and that no change shall be made in the target port
asymmetric access state of any target port groups or target ports. If the specfied parameter list length is not
supported, the device server shall terminate the command with CHECK CONDITION status, with the sense
key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

The CONTROL byte is defined in SAM-5.

The allowable values to which target port asymmetric access states may be set is vendor specific and should
be reported in the REPORT TARGET PORT GROUP parameter data (see 6.37).

Primary target port groups that are not specified in a parameter list may change primary target port
asymmetric access states as a result of the SET TARGET PORT GROUPS command. This shall not be
considered an implicit target port asymmetric access state change.

If a SET TARGET PORT GROUPS command attempts to establish an invalid combination of target port
asymmetric access states or attempts to establish an unsupported target port asymmetric access state, then
the device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

How a SET TARGET PORT GROUPS command is completed with success depends upon which of the
following conditions apply:

a) if the transition is treated as a single indivisible event (see 5.15.2.5), the SET TARGET PORT
GROUPS command shall not complete until the transition to the requested state has completed; or

504 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

b) if the transition is not treated as a single indivisible event (i.e., the device server supports other
commands (see 5.15.2.5) when those commands are routed though a target port that is transitioning
between target port asymmetric access states), then the SET TARGET PORT GROUPS command
may complete before the transition into the requested state has completed.

How a SET TARGET PORT GROUPS command is terminated with an error depends upon which of the
following conditions apply:

a) if the processing of a SET TARGET PORT GROUPS command requires the enabling of a nonvolatile
memory and the nonvolatile memory is not ready, then the device server shall terminate the command
with CHECK CONDITION status, rather than wait for the logical unit to become ready. The sense key
shall be set to NOT READY and the additional sense code shall be set as described in table 336 (see
6.47); or
b) if a failure occurred before the transition was completed, the device server shall terminate the
command with CHECK CONDITION status, with the sense key set to HARDWARE ERROR, and the
additional sense code set to SET TARGET PORT GROUPS COMMAND FAILED.

If two SET TARGET PORT GROUPS commands are processed concurrently, the target port asymmetric
access state change behavior is vendor specific. A SCSI target device should not process multiple SET
TARGET PORT GROUPS concurrently.

The SET TARGET PORT GROUPS parameter data format is shown in table 330.

Table 330 — SET TARGET PORT GROUPS parameter list format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • Reserved
3
Set target port group descriptor list
4
Set target port group descriptor (see table 331)
•• •
[first]
7
••
•
n-3
Set target port group descriptor (see table 331)
•• •
[last]
n

The format of the set target port group descriptor is defined in table 331.

Table 331 — Set target port group descriptor parameter list

Bit
7 6 5 4 3 2 1 0
Byte
0 Reserved ASYMMETRIC ACCESS STATE

1 Reserved
2 (MSB)
TARGET PORT GROUP OR TARGET PORT
3 (LSB)

Working Draft SCSI Primary Commands - 4 (SPC-4) 505

T10/BSR INCITS 513 Revision 37 17 May 2014

If the ASYMMETRIC ACCESS STATE field (see table 332) specifies a primary target port asymmetric access state,
then all the target ports in the specified target port group shall transition to the specified state (see 5.15.2.5). If
the ASYMMETRIC ACCESS STATE field specifies a secondary target port asymmetric access state, then the
specified target port shall transition to the specified state.

Table 332 — ASYMMETRIC ACCESS STATE field

Value State (see 5.15.2.4) Type (see 5.15.2.1)

0h Active/optimized Primary
1h Active/non-optimized Primary
2h Standby Primary
3h Unavailable Primary
4h Illegal Request a
5h to Dh Reserved
Eh Offline Secondary
a
Fh Illegal Request
a
If the ASYMMETRIC ACCESS STATE field in any target port group descriptor
contains 04h or Fh, then the device server shall terminate the command with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST,
and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

If the ASYMMETRIC ACCESS STATE field (see table 332) specifies a primary target port asymmetric access state,
then the TARGET PORT GROUP OR TARGET PORT field specifies a primary target port group for which the primary
target port asymmetric access state shall be changed. If the ASYMMETRIC ACCESS STATE field specifies a
secondary target port asymmetric access state, then the TARGET PORT GROUP OR TARGET PORT field specifies
the relative target port identifier of the target port for which the secondary target port asymmetric access state
shall be changed.

506 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.46 SET TIMESTAMP command

The SET TIMESTAMP command (see table 333) requests the device server to initialize a device clock (see
5.2) if the SCSIP bit is set to one in the Control Extension mode page (see 7.5.9). If the SCSIP bit is set to zero,
the device server shall terminate the SET TIMESTAMP command with CHECK CONDITION status, with the
sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB. This
command uses the MAINTENANCE OUT CDB format (see 4.2.2.3.4).

Table 333 — SET TIMESTAMP command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (A4h)
1 Reserved SERVICE ACTION (0Fh)
2
•• • Reserved
5
6 (MSB)
•• • PARAMETER LIST LENGTH
9 (LSB)
10 Reserved
11 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 333 for the SET
TIMESTAMP command.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 333 for the SET TIMESTAMP
command.

The PARAMETER LIST LENGTH field specifies the length in bytes of the SET TIMESTAMP parameters that shall
be transferred from the application client to the device server. A parameter list length of zero specifies that no
data shall be transferred, and that no change shall be made to a device clock.

The CONTROL byte is defined in SAM-5.

Working Draft SCSI Primary Commands - 4 (SPC-4) 507

T10/BSR INCITS 513 Revision 37 17 May 2014

The format for the parameter list for the SET TIMESTAMP command is shown in table 334.

Table 334 — SET TIMESTAMP parameter list format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • Reserved
3
4 (MSB)
•• • TIMESTAMP
9 (LSB)
10
Reserved
11

The TIMESTAMP field specifies the value to which a device clock shall be initialized (see 5.2). The timestamp
should be the number of milliseconds that have elapsed since midnight, 1 January 1970 UT. If the most
significant byte in the TIMESTAMP field is greater than F0h, the device server shall terminate the command with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set
to INVALID FIELD IN PARAMETER LIST.

On successful completion of a SET TIMESTAMP command the device server shall establish a unit attention
condition for the initiator port associated with every I_T nexus except the I_T nexus on which the SET
TIMESTAMP command was received (see SAM-5), with the additional sense code set to TIMESTAMP
CHANGED.

6.47 TEST UNIT READY command

The TEST UNIT READY command (see table 335) requests the device server to indicate whether the logical
unit is ready. The device server shall not initiate a self-test as a result of processing this command. If the
logical unit is able to accept an appropriate medium-access command without returning CHECK CONDITION
status, then the device server shall complete this command with GOOD status. If the logical unit is unable to
become operational or is in a state such that an application client action (e.g., a START UNIT command) is
required to make the logical unit ready, then the device server shall terminate this command with CHECK
CONDITION status, with the sense key set to NOT READY.

Table 335 — TEST UNIT READY command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (00h)
1
•• • Reserved
4
5 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 335 for the TEST UNIT
READY command.

508 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The CONTROL byte is defined in SAM-5.

Table 336 defines the suggested CHECK CONDITION status responses to the TEST UNIT READY
command. Other conditions (e.g., deferred errors, reservations, or target port asymmetric access state
changes) may result in other responses (e.g., GOOD status, CHECK CONDITION status, BUSY status, or
RESERVATION CONFLICT status, each with or without other sense key and additional sense code values).

Table 336 — Preferred TEST UNIT READY responses

Status Sense Key Additional Sense Code

CHECK CONDITION ILLEGAL REQUEST LOGICAL UNIT NOT SUPPORTED
CHECK CONDITION NOT READY LOGICAL UNIT DOES NOT RESPOND
TO SELECTION
CHECK CONDITION NOT READY MEDIUM NOT PRESENT
CHECK CONDITION NOT READY LOGICAL UNIT NOT READY,
CAUSE NOT REPORTABLE
CHECK CONDITION NOT READY LOGICAL UNIT IS IN PROCESS
OF BECOMING READY
CHECK CONDITION NOT READY LOGICAL UNIT NOT READY,
INITIALIZING COMMAND REQUIRED
CHECK CONDITION NOT READY LOGICAL UNIT NOT READY,
MANUAL INTERVENTION REQUIRED
CHECK CONDITION NOT READY LOGICAL UNIT NOT READY,
FORMAT IN PROGRESS
CHECK CONDITION NOT READY LOGICAL UNIT NOT READY,
SANITIZE IN PROGRESS

Working Draft SCSI Primary Commands - 4 (SPC-4) 509

T10/BSR INCITS 513 Revision 37 17 May 2014

6.48 WRITE ATTRIBUTE command

The WRITE ATTRIBUTE command (see table 337) requests the device server to write the specified attributes
to medium auxiliary memory. Device servers that implement the WRITE ATTRIBUTE command shall also
implement the READ ATTRIBUTE command (see 6.17). Application clients should issue READ ATTRIBUTE
commands prior to using this command to discover device server support for medium auxiliary memory.

Table 337 — WRITE ATTRIBUTE command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (8Dh)
1 Reserved WTC

2
3 Restricted (see SMC-3)
4
5 LOGICAL VOLUME NUMBER

6 Reserved
7 PARTITION NUMBER

8
Reserved
9
10 (MSB)
•• • PARAMETER LIST LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 337 for the WRITE
ATTRIBUTE command.

The write-through cache (WTC) bit set to one specifies the attributes in the parameter list shall be synchronized
with the medium auxiliary memory during the processing of the WRITE ATTRIBUTE command and GOOD
status shall not be returned until the attributes have been synchronized with the medium auxiliary memory.
The WTC bit is set to zero specifies no requirement related to the attributes in the parameter list being
synchronized with the medium auxiliary memory during the processing of the WRITE ATTRIBUTE command.

The LOGICAL VOLUME NUMBER field specifies a logical volume (e.g., the medium auxiliary memory storage for
one side of a double sided medium) within the medium auxiliary memory. The number of logical volumes of
the medium auxiliary memory shall equal that of the attached medium. If the medium only has a single logical
volume, then its logical volume number shall be zero.

The PARTITION NUMBER field specifies a partition (see SSC-4) within a logical volume. The number of partitions
of the medium auxiliary memory shall equal that of the attached medium. If the medium only has a single
partition, then its partition number shall be zero.

If the combination of logical volume number and partition number is not valid, the device server shall terminate
the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the
additional sense code set to INVALID FIELD IN CDB.

510 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The PARAMETER LIST LENGTH field specifies the length in bytes of the parameter list contained in the Data-Out
Buffer. A parameter list length of zero specifies that no parameter list is present; this shall not be considered
an error. If the parameter list length results in the truncation of an attribute, the WRITE ATTRIBUTE command
shall be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the
additional sense code set to PARAMETER LIST LENGTH ERROR.

The CONTROL byte is defined in SAM-5.

The parameter list shall have the format shown in table 338. Attributes should be sent in ascending numerical
order. If the attributes are not in order, then no attributes shall be changed and the device server shall
terminate the WRITE ATTRIBUTE command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

Table 338 — WRITE ATTRIBUTE parameter list format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • PARAMETER DATA LENGTH (n-3)
3 (LSB)
Attribute(s)
4
•• • Attribute (see 7.4.1) [first]

•
••

•• • Attribute (see 7.4.1) [last]

n

The PARAMETER DATA LENGTH field should contain the number of bytes of attribute data and shall be ignored by
the device server.

The format of the attributes is described in 7.4.1.

If there is not enough space to write the attributes to the medium auxiliary memory, then no attributes shall be
changed and the device server shall terminate the WRITE ATTRIBUTE command with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to AUXILIARY
MEMORY OUT OF SPACE.

If the medium auxiliary memory is not accessible as a result of there being no medium present, then no
attributes shall be changed and the device server shall terminate the WRITE ATTRIBUTE command with
CHECK CONDITION status, with the sense key set to NOT READY, and the additional sense code set to
MEDIUM NOT PRESENT.

If the medium is present but the medium auxiliary memory is not accessible, then no attributes shall be
changed and the device server shall terminate the WRITE ATTRIBUTE command with CHECK CONDITION
status, with the sense key set to MEDIUM ERROR, and the additional sense code set to LOGICAL UNIT NOT
READY, AUXILIARY MEMORY NOT ACCESSIBLE.

Working Draft SCSI Primary Commands - 4 (SPC-4) 511

T10/BSR INCITS 513 Revision 37 17 May 2014

If the medium auxiliary memory is not operational (e.g., bad checksum), the device server shall terminate the
WRITE ATTRIBUTE command with CHECK CONDITION status, with the sense key set to MEDIUM ERROR,
and the additional sense code set to AUXILIARY MEMORY WRITE ERROR.

If the WRITE ATTRIBUTE command parameter list contains an attribute with an ATTRIBUTE LENGTH field (see
7.4.1) set to zero, then one of the following actions shall occur:

a) if the attribute state is unsupported or read only (see 5.7), then no attributes shall be changed and the
device server shall terminate the WRITE ATTRIBUTE command with CHECK CONDITION status,
with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD
IN PARAMETER LIST;
b) if the attribute state is read/write, the attribute shall be changed to the nonexistent state. This attribute
shall not be returned in response to a READ ATTRIBUTE command and shall not be included in the
parameter data returned by a READ ATTRIBUTE command with ATTRIBUTE LIST service action; or
c) if the attribute state is nonexistent, the attribute in the WRITE ATTRIBUTE command parameter list
shall be ignored; this shall not be considered an error.

No attributes shall be changed, the WRITE ATTRIBUTE command shall be terminated with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
INVALID FIELD IN PARAMETER LIST if the parameter list contains any of the following:

a) an attempt to change an attribute in the read only state (see 5.7);

b) an attribute with incorrect ATTRIBUTE LENGTH field (see 7.4.1) contents; or
c) an attribute with unsupported ATTRIBUTE VALUE field (see 7.4.1) contents.

512 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

6.49 WRITE BUFFER command

6.49.1 WRITE BUFFER command introduction

The WRITE BUFFER command (see table 339) is used in conjunction with the READ BUFFER command for:

a) testing logical unit buffer memory;

b) testing the integrity of the service delivery subsystem;
c) downloading microcode (see 5.4); and
d) downloading application client error history (see 5.5).

Table 339 — WRITE BUFFER command

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (3Bh)
1 MODE SPECIFIC MODE

2 BUFFER ID

3 (MSB)
4 BUFFER OFFSET

5 (LSB)
6 (MSB)
7 PARAMETER LIST LENGTH

8 (LSB)
9 CONTROL

This command shall not alter any medium of the logical unit if the data mode or the combined header and data
mode is specified.

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 339 for the WRITE BUFFER
command.

The usage of the MODE SPECIFIC field depends on the value in the MODE field.

Working Draft SCSI Primary Commands - 4 (SPC-4) 513

T10/BSR INCITS 513 Revision 37 17 May 2014

The function of this command and the meaning of fields within the CDB depend on the contents of the MODE
field. The MODE field is defined in table 340.

Table 340 — WRITE BUFFER MODE field

Code Description Reference

00h Obsolete
01h Vendor specific 6.49.2
02h Data 6.49.3
03h Reserved
04h Download microcode and activate 5.4 and 6.49.4
05h Download microcode, save, and activate 5.4 and 6.49.5
06h Download microcode with offsets and activate 5.4 and 6.49.6
07h Download microcode with offsets, save, and activate 5.4 and 6.49.7
08h to 09h Reserved
0Ah Write data to echo buffer 6.49.8
0Bh to 0Ch Reserved
0Dh Download microcode with offsets, select activation events, 5.4 and 6.49.9
save, and defer activate
0Eh Download microcode with offsets, save, and defer activate 5.4 and 6.49.10
0Fh Activate deferred microcode 5.4 and 6.49.11
10h to 19h Reserved
1Ah Obsolete
1Bh Obsolete
1Ch Download application client error history 5.5 and 6.49.12
1Dh to 1Fh Reserved

The MODE field may be processed as specifying a service action by the REPORT SUPPORTED OPERATION
CODES command (see 6.35).

The CONTROL byte is defined in SAM-5.

6.49.2 Vendor specific mode (01h)

In this mode, the MODE SPECIFIC field is reserved.

The meaning of the BUFFER ID field, BUFFER OFFSET field, and PARAMETER LIST LENGTH field are not specified by
this standard.

6.49.3 Data mode (02h)

In this mode, the Data-Out Buffer contains buffer data destined for the logical unit. The BUFFER ID field
identifies a specific buffer within the logical unit. The manufacturer assigns buffer ID codes to buffers within
the logical unit. Buffer ID zero shall be supported. If more than one buffer is supported, then additional buffer

514 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

ID codes shall be assigned contiguously, beginning with one. If an unsupported buffer ID code is selected, the
device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

The MODE SPECIFIC field is reserved.

The BUFFER OFFSET field specifies the location in the buffer to which the data is written. The application client
should conform to the offset boundary requirements returned in the READ BUFFER descriptor (see 6.18.4). If
the device server is unable to process the specified buffer offset, the device server shall terminate the
command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID FIELD IN CDB.

The PARAMETER LIST LENGTH field specifies the maximum number of bytes that shall be transferred from the
Data-Out Buffer to be stored in the specified buffer beginning at the buffer offset. The application client should
specify a parameter list length plus the buffer offset that does not exceed the capacity of the specified buffer.
The capacity of the buffer is indicated by the BUFFER CAPACITY field in the READ BUFFER descriptor (see
6.18.4). If the BUFFER OFFSET field and PARAMETER LIST LENGTH field specify a transfer in excess of the buffer
capacity, then the device server shall terminate the command with CHECK CONDITION status, with the
sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

6.49.4 Download microcode and activate mode (04h)

In this mode, microcode shall be transferred to the device server and activated (see 5.4).

The MODE SPECIFIC field is reserved.

The BUFFER ID field, BUFFER OFFSET field, and PARAMETER LIST LENGTH field are vendor specific.

6.49.5 Download microcode, save, and activate mode (05h)

In this mode, microcode shall be transferred to the device server, saved to nonvolatile storage, and activated
(see 5.4) based on the setting of the ACTIVATE MICROCODE field in the Extended INQUIRY VPD page (see
7.8.7).

The MODE SPECIFIC field is reserved.

The BUFFER ID field, BUFFER OFFSET field, and PARAMETER LIST LENGTH field are vendor specific.

6.49.6 Download microcode with offsets and activate mode (06h)

In this mode, microcode shall be transferred to the device server using one or more WRITE BUFFER
commands and activated (see 5.4).

The MODE SPECIFIC field is reserved.

The BUFFER ID field specifies a buffer within the logical unit. The manufacturer assigns buffer ID codes to
buffers within the logical unit. A buffer ID value of zero shall be supported. If more than one buffer is
supported, then additional buffer ID codes shall be assigned contiguously, beginning with one. If an
unsupported buffer ID code is specified, the device server shall terminate the command with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
INVALID FIELD IN CDB.

Working Draft SCSI Primary Commands - 4 (SPC-4) 515

T10/BSR INCITS 513 Revision 37 17 May 2014

The BUFFER OFFSET field specifies the location in the buffer to which the microcode is written. The application
client shall send only commands that conform to the offset boundary requirements returned in the READ
BUFFER descriptor (see 6.18.4). If the device server is unable to process the specified buffer offset, the
device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

The PARAMETER LIST LENGTH field specifies the maximum number of bytes that shall be present in the
Data-Out Buffer to be stored in the specified buffer beginning at the buffer offset. The application client should
specify a parameter list length plus the buffer offset that does not exceed the capacity of the specified buffer. If
the BUFFER OFFSET field and PARAMETER LIST LENGTH field specify a transfer in excess of the buffer capacity,
then the device server shall terminate the command with CHECK CONDITION status, with the sense key set
to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

6.49.7 Download microcode with offsets, save, and activate mode (07h)

In this mode, microcode shall be transferred to the device server using one or more WRITE BUFFER
commands, saved to nonvolatile storage, and activated (see 5.4) based on the setting of the ACTIVATE
MICROCODE field in the Extended INQUIRY VPD page (see 7.8.7).

The BUFFER ID field, BUFFER OFFSET field, and PARAMETER LIST LENGTH field are defined in the download
microcode with offsets mode (see 6.49.6).

6.49.8 Write data to echo buffer mode (0Ah)

In this mode the device server transfers data from the application client and stores it in an echo buffer. An
echo buffer is assigned in the same manner by the device server as it would for a write operation. Data shall
be aligned on four-byte boundaries.

The BUFFER ID and BUFFER OFFSET fields shall be ignored in this mode.

NOTE 36 - It is recommended that the logical unit assign echo buffers on a per I_T nexus basis to limit the
number of exception conditions that may occur if there is more than one I_T nexus present.

Upon successful completion of a WRITE BUFFER command the data shall be preserved in the echo buffer
unless there is an intervening command to any logical unit in which case the data may be changed.

The PARAMETER LIST LENGTH field specifies the maximum number of bytes that shall be transferred from the
Data-Out Buffer to be stored in the echo buffer. The application client should specify a parameter list length
that does not exceed the capacity of the echo buffer. The capacity of the echo buffer is indicated by the
BUFFER CAPACITY field in the READ BUFFER echo buffer descriptor (see 6.18.6). If the PARAMETER LIST
LENGTH field specifies a transfer in excess of the buffer capacity, the device server shall terminate the
command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID FIELD IN CDB.

6.49.9 Download microcode with offsets, select activation, save, and defer activate mode (0Dh)

In this mode, microcode shall be transferred to the device server using one or more WRITE BUFFER
commands, saved to nonvolatile storage, and considered deferred (see 5.4). The deferred microcode shall be
activated and no longer considered deferred if a WRITE BUFFER command with the activate deferred
microcode mode (0Fh) is processed (see 6.49.11).

516 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The MODE SPECIFIC field (see table 341) specifies additional events that shall be used to activate the deferred
microcode.

Table 341 — MODE SPECIFIC field

Bit 7 6 5 …

PO_ACT HR_ACT VSE_ACT …

If the power on activate (PO_ACT) bit is set to one, then deferred microcode shall be activated and no longer
considered deferred if a power on occurs. If the PO_ACT bit is set to zero, then deferred microcode shall not be
activated if a power on occurs.

If the hard reset activate (HR_ACT) bit is set to one, then deferred microcode shall be activated and no longer
considered deferred if a hard reset occurs. If the HR_ACT bit is set to zero, then deferred microcode shall not
be activated if a hard reset occurs.

If the vendor specific event activate (VSE_ACT) bit is set to one, then deferred microcode shall be activated and
no longer considered deferred if a vendor specific event occurs. If the VSE_ACT bit is set to zero, then deferred
microcode shall not be activated if a vendor specific event occurs.

The supported activation events shall be reported in the POA_SUP bit, HRA_SUP bit, and VSA_SUP bit in the
Extended INQUIRY VPD page (see 7.8.7). If the MODE SPECIFIC field specifies an activation event that is not
supported (e.g., if the PO_ACT bit is set to one and the POA_SUP bit is set to zero), then the device server shall
terminate the command CHECK CONDITION status with the sense key set to ILLEGAL REQUEST and the
additional sense code set to INVALID FIELD IN CDB.

The BUFFER ID field, BUFFER OFFSET field, and PARAMETER LIST LENGTH field are defined in the download
microcode with offsets mode (see 6.49.6).

6.49.10 Download microcode with offsets, save, and defer activate mode (0Eh)

In this mode, microcode shall be transferred to the device server using one or more WRITE BUFFER
commands, saved to nonvolatile storage, and considered deferred (see 5.4).

The deferred microcode shall be activated and no longer considered deferred if any one of the following
occurs:

a) a power on;
b) a hard reset;
c) a START STOP UNIT command is processed (see SBC-3);
d) a FORMAT UNIT command is processed (see SBC-3); or
e) a WRITE BUFFER command with the activate deferred microcode mode (0Fh) is processed (see
6.49.11).

The MODE SPECIFIC field, BUFFER ID field, BUFFER OFFSET field, and PARAMETER LIST LENGTH field are defined in
the download microcode with offsets mode (see 6.49.6).

Working Draft SCSI Primary Commands - 4 (SPC-4) 517

T10/BSR INCITS 513 Revision 37 17 May 2014

6.49.11 Activate deferred microcode mode (0Fh)

In this mode, deferred microcode, if any, that has been saved using one of the modes list in this subclause
shall be activated and no longer considered deferred (see 5.4). The modes that save deferred microcode are:

a) the download microcode with offsets, select activation events, save, and defer activate mode (0Dh)
(see 6.49.9); and
b) the download microcode with offsets, save, and defer activate mode (0Eh) (see 6.49.10).

The MODE SPECIFIC field is reserved.

The the BUFFER ID field, the BUFFER OFFSET field, and PARAMETER LIST LENGTH field shall be ignored in this
mode.

If there is no deferred microcode that has been saved using one of the modes list in this subclause, the device
server shall terminate the WRITE BUFFER command with CHECK CONDITION status, with the sense key
set to ILLEGAL REQUEST, and the additional sense code set to COMMAND SEQUENCE ERROR.

6.49.12 Download application client error history mode (1Ch)

In this mode the device server transfers application client error history from the application client and stores it
in the error history (see 5.5). The format of the application client error history parameter list is defined in table
342.

The MODE SPECIFIC field is reserved.

The BUFFER ID field and BUFFER OFFSET field shall be ignored in this mode.

Upon successful completion of a WRITE BUFFER command, the information contained in the application
client error history parameter list shall be appended to the application client error history in a format
determined by the logical unit.

The PARAMETER LIST LENGTH field specifies the length in bytes of the application client error history parameter
list that shall be transferred from the application client to the device server. If the PARAMETER LIST LENGTH field
specifies a transfer that exceeds the error history capacity, the device server shall terminate the command
with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense
code set to INVALID FIELD IN CDB.

518 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The device server shall not return an error based on the contents of any of the field values defined in table 342
except:

a) the CLR bit;

b) the ERROR LOCATION LENGTH field; and
c) the APPLICATION CLIENT ERROR HISTORY LENGTH field.

Table 342 — Application client error history parameter list format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • T10 VENDOR IDENTIFICATION
7 (LSB)
8 (MSB)
ERROR TYPE
9 (LSB)
10 Reserved CLR

11 Reserved
12 (MSB)
•• • TIMESTAMP
17 (LSB)
18
Reserved
19
20 Reserved CODE SET

21 ERROR LOCATION FORMAT

22 (MSB)
ERROR LOCATION LENGTH (m-25)
23 (LSB)
24 (MSB)
APPLICATION CLIENT ERROR HISTORY LENGTH (n-m)
25 (LSB)
26 (MSB)
•• • ERROR LOCATION
m (LSB)
m+1
•• • APPLICATION CLIENT ERROR HISTORY
n

The T10 VENDOR IDENTIFICATION field contains eight bytes of left-aligned ASCII data (see 4.3.1) identifying the
manufacturer providing the application client error history. The T10 vendor identification shall be one assigned
by INCITS. A list of assigned T10 vendor identifications is in Annex G and on the T10 web site
(http://www.t10.org).

Working Draft SCSI Primary Commands - 4 (SPC-4) 519

T10/BSR INCITS 513 Revision 37 17 May 2014

The ERROR TYPE field (see table 343) specifies the error detected by the application client.

Table 343 — ERROR TYPE field

Code Description
0000h No error specified by the application client.
0001h An unknown error was detected by the application client.
0002h The application client detected corrupted data.
0003h The application client detected a permanent error.
0004h The application client detected a service response of
SERVICE DELIVERY OR TARGET FAILURE (see SAM-5).

0005h to 7FFFh Reserved

8000h to FFFFh Vendor specific

If the CLR_SUP bit is set to one in the error history directory parameter data (see 6.18.7.2), a CLR bit set to one
specifies that the device server shall:

a) clear the portions of the error history that the device server allows to be cleared; and
b) ignore any application client error history specified in the parameter list.

If the CLR_SUP bit is set to one in the error history directory parameter data, a CLR bit set to zero specifies that
the device server shall:

a) not clear the error history; and

b) process all application client error history specified in the parameter list.

If the CLR_SUP bit is set to zero in the error history directory parameter data, the device server shall ignore the
CLR bit.

The TIMESTAMP field should contain:

a) a time based on the timestamp reported by the REPORT TIMESTAMP command, if the device server
supports a device clock (see 5.2);
b) the number of milliseconds that have elapsed since midnight, 1 January 1970 UT; or
c) zero, if the application client is not able to determine the UT of the log entry.

The CODE SET field contains a code set enumeration (see 4.3.3) that indicates the format of the APPLICATION
CLIENT ERROR HISTORY field.

520 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The ERROR LOCATION FORMAT field (see table 344) specifies the format of the ERROR LOCATION field.

Table 344 — ERROR LOCATION FORMAT field

Code Description
00h No error history location specified by the application client.
01h For block devices (see SBC-3 and RBC), the ERROR LOCATION field specifies
the logical block address associated the specified application client error
history. For other peripheral device types, this code is reserved.
02h to 7Fh Reserved
80h to FFh Vendor specific

The ERROR LOCATION LENGTH field specifies the length of the ERROR LOCATION field. The ERROR LOCATION
LENGTH field value shall be a multiple of four. An ERROR LOCATION LENGTH field set to zero specifies that there
is no error location information.

The APPLICATION CLIENT ERROR HISTORY LENGTH field specifies the length of the APPLICATION CLIENT ERROR
HISTORY field. The APPLICATION CLIENT ERROR HISTORY LENGTH field value shall be a multiple of four. An
APPLICATION CLIENT ERROR HISTORY field set to zero specifies that there is no vendor specific information.

The ERROR LOCATION field specifies the location at which the application client detected the error, in the format
specified by the ERROR LOCATION FORMAT field.

The APPLICATION CLIENT ERROR HISTORY field specifies vendor specific application client error history (see
5.5.1).

Working Draft SCSI Primary Commands - 4 (SPC-4) 521

T10/BSR INCITS 513 Revision 37 17 May 2014

7 Parameters for all device types

7.1 Overview

Parameters for all device types are defined in this clause as follows:

a) diagnostic parameters are defined in 7.2;

b) log parameters are defined in 7.3;
c) medium auxiliary memory attributes are defined in 7.4;
d) mode parameters are defined in 7.5;
e) protocol specific parameters are defined in 7.6;
f) security parameters are defined in 7.7; and
g) vital product data parameters are defined in 7.8.

7.2 Diagnostic parameters

7.2.1 Summary of diagnostic page codes

The page code assignments for diagnostic pages are summarized in table 345.

Table 345 — Summary of diagnostic page codes

Diagnostic page description Page code Reference

Defined by SES-3 for: 01h to 2Fh SES-3
a) standalone enclosure services devices (i.e., logical
units with the PERIPHERAL DEVICE TYPE field set to
0Dh in standard INQUIRY data (see 6.6.2)); and
b) attached enclosure services devices (i.e., logical
units with the ENCSERV bit set to one in standard
INQUIRY data).
Protocol Specific 3Fh 7.2.3
Supported Diagnostic Pages 00h 7.2.4
Restricted (see applicable command standard) 40h to 7Fh
Vendor specific a

Reserved All other codes

A numeric ordered listing of diagnostic page codes is provided in F.4.
a
The following page codes are vendor specific: 80h to FFh.

7.2.2 Diagnostic page format for all device types

This subclause describes the diagnostic page structure and the diagnostic pages that are applicable to all
SCSI devices. Diagnostic pages specific to each device type are described in the command standard that
applies to that device type.

A SEND DIAGNOSTIC command (see 6.42) with a PF bit set to one specifies that the SEND DIAGNOSTIC
parameter list consists of a single diagnostic page and that the data returned by the subsequent RECEIVE

522 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

DIAGNOSTIC RESULTS command (see 6.27) that has the PCV bit set to zero. If the PF bit is supported in the
SEND DIAGNOSTIC command (see 6.42), a SEND DIAGNOSTIC command with a PF bit set to one specifies
that the subsequent RECEIVE DIAGNOSTIC RESULTS command shall use the diagnostic page format
defined in table 346. A RECEIVE DIAGNOSTIC RESULTS command with a PCV bit set to one specifies that
the device server return a diagnostic page using the format defined in table 346.

Table 346 — Diagnostic page format

Bit
7 6 5 4 3 2 1 0
Byte
0 PAGE CODE

1 Page code specific

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4
•• • Diagnostic parameters
n

Each diagnostic page defines:

a) a function or operation that the device server shall perform as a result of a SEND DIAGNOSTIC
command; or
b) the information being returned as a result of a RECEIVE DIAGNOSTIC RESULTS command with the
PCV bit equal to one.

The diagnostic parameters contain data that is formatted according to the page code specified.

The PAGE CODE field (see 7.2.1) identifies the diagnostic page.

The PAGE LENGTH field indicates the number of bytes that follow in the diagnostic parameters. If the application
client sends a SEND DIAGNOSTIC command with a parameter list containing a PAGE LENGTH field that results
in the truncation of any parameter, then the device server shall terminate the command with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
INVALID FIELD IN PARAMETER LIST.

The diagnostic parameters are defined for each diagnostic page code. The diagnostic parameters within a
diagnostic page may be defined differently in a SEND DIAGNOSTIC command than in a RECEIVE
DIAGNOSTIC RESULTS command.

Working Draft SCSI Primary Commands - 4 (SPC-4) 523

T10/BSR INCITS 513 Revision 37 17 May 2014

7.2.3 Protocol Specific diagnostic page

The Protocol Specific diagnostic page (see table 347) provides access to SCSI transport protocol specific
diagnostic parameters.

Table 347 — Protocol Specific diagnostic page

Bit
7 6 5 4 3 2 1 0
Byte
0 PAGE CODE (3Fh)
1 Reserved PROTOCOL IDENTIFIER

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4
SCSI transport protocol specific
•• •
diagnostic parameters
n

The PAGE CODE field is described in 7.2.2, and shall be set to 3Fh to indicate a Protocol Specific diagnostic
page follows.

The PROTOCOL IDENTIFIER field contains one of the values shown in table 479 (see 7.6.1) to identify the SCSI
transport protocol standard that defines the SCSI transport protocol specific diagnostic parameters.

The PAGE LENGTH field specifies the length in bytes of the following supported page list.

The SCSI transport protocol specific diagnostic parameters are defined by the SCSI transport protocol
standard that corresponds to the value in the PROTOCOL IDENTIFIER field.

7.2.4 Supported Diagnostic Pages diagnostic page

The Supported Diagnostic Pages diagnostic page (see table 348) returns the list of diagnostic pages
implemented by the device server. This diagnostic page shall be implemented if the device server implements
the diagnostic page format option of the SEND DIAGNOSTIC command and RECEIVE DIAGNOSTIC
RESULTS commands.

Table 348 — Supported Diagnostic Pages diagnostic page

Bit
7 6 5 4 3 2 1 0
Byte
0 PAGE CODE (00h)
1 Reserved
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4
•• • SUPPORTED PAGE LIST
n

524 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The definition of this diagnostic page for the SEND DIAGNOSTIC command includes only the first four bytes.
If the PAGE LENGTH field is not zero, the device server shall terminate the SEND DIAGNOSTIC command with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set
to INVALID FIELD IN PARAMETER LIST.

This diagnostic page specifies that the device server shall make available the list of all supported diagnostic
pages to be returned by a subsequent RECEIVE DIAGNOSTIC RESULTS command.

The definition of this diagnostic page for the RECEIVE DIAGNOSTIC RESULTS command includes the list of
diagnostic pages supported by the device server.

The PAGE CODE field is described in 7.2.2, and shall be set to 00h to indicate a Supported Diagnostics Pages
diagnostic page follows.

The PAGE LENGTH field indicates the length in bytes of the following supported page list.

The SUPPORTED PAGE LIST field shall contain a list of all diagnostic page codes, one per byte, implemented by
the device server in ascending order beginning with page code 00h.

Working Draft SCSI Primary Commands - 4 (SPC-4) 525

T10/BSR INCITS 513 Revision 37 17 May 2014

7.3 Log parameters

7.3.1 Summary of log page codes

The page code assignments for log pages are summarized in table 349.

Table 349 — Summary of log page codes

Log page name Page code Subpage code Reference

Application Client 0Fh 00h 7.3.4
Buffer Over-Run/Under-Run 01h 00h 7.3.5
Cache Memory Statistics 19h 20h 7.3.6
General Statistics and Performance 19h 00h 7.3.7
Group Statistics and Performance (1 to 31) 19h 01h to 1Fh 7.3.8
Informational Exceptions 2Fh 00h 7.3.9
Last n Deferred Errors or Asynchronous Events 0Bh 00h 7.3.10
Last n Error Events 07h 00h 7.3.11
Non-Medium Error 06h 00h 7.3.12
Power Condition Transitions 1Ah 00h 7.3.13
a
Protocol Specific Port 18h 00h to FEh 7.3.14
Read Error Counters 03h 00h 7.3.15
Read Reverse Error Counters 04h 00h 7.3.16
Self-Test Results 10h 00h 7.3.17
Start-Stop Cycle Counter 0Eh 00h 7.3.18
Supported Log Pages 00h 00h 7.3.19
Supported Log Pages and Subpages 00h FFh 7.3.20
Supported Subpages 01h to 3Fh FFh 7.3.21
Temperature 0Dh 00h 7.3.22
Verify Error Counters 05h 00h 7.3.23
Write Error Counters 02h 00h 7.3.24
08h to 0Ah 00h to FEh
0Ch 00h to FEh
Restricted (see applicable protocol standard)
11h to 17h 00h to FEh
1Bh to 2Eh 00h to FEh
Vendor specific b

Reserved All other codes

A numeric ordered listing of log pages codes and subpage codes is provided in F.5.
a
Each SCSI transport protocol standard may define a different name for these log pages.
b Page codes 30h to 3Eh each with subpage codes 00h to FEh are vendor specific.

526 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.3.2 Log page structure and log parameter structure for all device types

7.3.2.1 Log page structure

This subclause describes the log page structure that is applicable to all SCSI devices. Log pages specific to
each device type are described in the command standard that applies to that device type. The LOG SELECT
command (see 6.7) supports the ability to send zero or more log pages. The LOG SENSE command (see 6.8)
returns the log page specified by the combination of the PAGE CODE field and SUBPAGE CODE field in the CDB.

Each log page begins with a four-byte page header followed by zero or more variable length log parameters
defined for that log page. The log page format is shown in table 350.

Table 350 — Log page format

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF PAGE CODE

1 SUBPAGE CODE

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Log parameter(s)
4
Log parameter (see 7.3.2.2) [first]
•• •
(Length x)
x+3
••
•
n-y+1
Log parameter (see 7.3.2.2) [last]
•• •
(Length y)
n

For the LOG SENSE command (see 6.8), the DS bit indicates whether log parameters in this log page are
saved if the SP bit is set to one in the CDB. If the DS bit is set to zero, the log parameters are saved if the SP bit
is set to one. If the DS bit is set to one, the log parameters are not saved. For the LOG SELECT command
(see 6.7), the disable save (DS) bit operates in conjunction with the PCR bit, the SP bit, the PC field, and the
PARAMETER LIST LENGTH field in the CDB.

If the subpage format (SPF) bit is set to zero, the SUBPAGE CODE field shall contain 00h. If the SPF bit is set to
one, the SUBPAGE CODE field shall contain a value between 01h and FFh.

The PAGE CODE field indicates the number of the log page (see 7.3.1) that is being transferred.

The SUBPAGE CODE field indicates the subpage number of the log page (see 7.3.1) that is being transferred.

If an application client specifies values in the PAGE CODE field and SUBPAGE CODE field for a log page that is
reserved or not implemented by the device server, then the device server shall terminate the LOG SELECT
command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID FIELD IN PARAMETER LIST.

If the PARAMETER LIST LENGTH field in a LOG SELECT command contains zero, the meanings for the PCR bit,
SP bit, and PC field are defined in 6.7.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 527

T10/BSR INCITS 513 Revision 37 17 May 2014

If the PARAMETER LIST LENGTH field in a LOG SELECT command contains a non-zero value (i.e., if a parameter
list is being sent with the LOG SELECT command), then table 351 defines the meaning for the combinations
of values for:

a) the PCR bit, the SP bit, and the PC field in the LOG SELECT command (see 6.7.1);
b) the DS bit in the log page header (see table 350); and
c) the PARAMETER CODE field and the FORMAT AND LINKING field in each log parameter (see 7.3.2.2.1).

Table 351 — LOG SELECT PCR bit, SP bit, and DS bit meanings when parameter list length is not zero

PCR SP DS
bit bit bit Description
0b 0b xb The device server shall set the specified values a to the values in the parameter list and
shall not save any values to non-volatile media.
0b 1b 0b The device server shall set the specified values a to the values in the parameter list and
shall process the optional saving of log parameter values as follows:
a) if default data counter values are specified (see table 187 in 6.7.1), no values
shall be saved;
b) if values other than default data counter values are specified and the device
server implements saving of the specified values a, then the device server shall
save the specified values a in the parameter list to non-volatile media; or
c) if values other than default values are specified and the device server does not
implement saving of one or more of the specified values a, then the device server
shall terminate the command with CHECK CONDITION status, with the sense
key set to ILLEGAL REQUEST, and the additional sense code set to INVALID
FIELD IN PARAMETER LIST.
0b 1b 1b The device server shall set the specified values a to the values in the parameter list and
shall not save any values in the specified log page to non-volatile media.
1b xb xb The device server shall terminate the command with CHECK CONDITION status, with
the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID
FIELD IN CDB.
a The specified parameters are determined by the PARAMETER CODE field contents (see 7.3.2.2.1) in the
LOG SELECT parameter data as well as by the PC field contents (see table 187 in 6.7.1) in the LOG
SELECT CDB.

The PAGE LENGTH field indicates the length in bytes of the log parameters that follow. If the application client
sends a log page length that results in the truncation of any parameter, the device server shall terminate the
command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID FIELD IN PARAMETER LIST.

528 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.3.2.2 Log parameter structure

7.3.2.2.1 Introduction

Most log pages contain one or more data structures called log parameters (see table 352). Log parameters
may be data counters of a particular event(s), the conditions under which certain operations were performed,
or list parameters that contain a character string or binary description related to a particular event.

Each log parameter begins with a four-byte parameter header followed by one or more bytes of parameter
value data.

Table 352 — Log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE
1 (LSB)
Parameter control byte (see 7.3.2.2.2)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (n-3)

4 (MSB)
•• • PARAMETER VALUE
n (LSB)

The PARAMETER CODE field identifies the log parameter being transferred. The device server shall return the
log parameters in a log page in ascending order based on the value in their PARAMETER CODE field.

If an application client specifies a value in the PARAMETER CODE field in the LOG SELECT command parameter
data that is reserved or not implemented by the logical unit, then the device server shall terminate the
command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID FIELD IN PARAMETER LIST.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are collectively referred to as the
parameter control byte. The bits and fields in the parameter control byte are described in 7.3.2.2.2.

The PARAMETER LENGTH field specifies the length in bytes of the PARAMETER VALUE field. If the application client
specifies a parameter length that results in the truncation of the PARAMETER VALUE field, then the device server
shall terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST,
and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

If the application client sends a value in a PARAMETER VALUE field that is outside the range supported by the
logical unit, and rounding is implemented for that parameter, then the device server may:

a) round to an acceptable value and terminate the command as described in 5.8; or

b) terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

If the parameter data for one LOG SELECT command contains more than one log page and the log pages are
not in ascending order by page code value then subpage code value, then the device server shall terminate
the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the
additional sense code set to INVALID FIELD IN PARAMETER LIST.

Working Draft SCSI Primary Commands - 4 (SPC-4) 529

T10/BSR INCITS 513 Revision 37 17 May 2014

If the parameter data for one LOG SELECT command contains more than one log parameter in any one log
page and the log parameters are not in ascending order by parameter code value, then the device server shall
terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and
the additional sense code set to INVALID FIELD IN PARAMETER LIST.

Application clients should send LOG SENSE commands prior to sending LOG SELECT commands to
determine supported log pages and page lengths.

The SCSI target device may provide independent sets of log parameters for each logical unit or for each
combination of logical units and I_T nexuses. If the SCSI target device does not support independent sets of
log parameters and any log parameters are changed that affect other I_T nexuses, then the device server
shall establish a unit attention condition (see SAM-5) for the initiator port associated with every I_T nexus
except the I_T nexus on which the LOG SELECT command was received, with the additional sense code set
to LOG PARAMETERS CHANGED.

7.3.2.2.2 Parameter control byte

7.3.2.2.2.1 Introduction

The bits and fields in the parameter control byte are described in 7.3.2.2.2.

For cumulative log parameter values, indicated by the PC field (see table 187 in 6.7.1) of the LOG SELECT
command and LOG SENSE command, the disable update (DU) bit is defined as follows:

a) DU set to zero indicates that the device server shall update the log parameter value to reflect all
events that should be noted by that parameter; or
b) DU set to one indicates that the device server shall not update the log parameter value except in
response to a LOG SELECT command that specifies a new value for the parameter.

NOTE 37 - While updating cumulative log parameter values, a device server may use volatile memory to hold
these values until a LOG SELECT command or LOG SENSE command is received with an SP bit set to one
or a vendor specific event occurs. As a result the updated cumulative log parameter values may be lost if a
power cycle occurs.

If the PC field (see table 187 in 6.7.1) indicates that threshold values or default values are being processed,
then the device server shall:

a) set the DU bit to zero, if a LOG SENSE command is being processed; and
b) ignore the DU bit, if a LOG SELECT command is being processed.

Regardless of the value in the PC field, the device server shall process ASCII format list log parameters (see
7.3.2.2.2.4) and binary format list log parameters (see 7.3.2.2.2.5) by:

a) setting the DU bit to zero, if a LOG SENSE command is being processed; and
b) ignoring the DU bit, if a LOG SELECT command is being processed.

A target save disable (TSD) bit set to zero indicates that the logical unit implicitly saves the log parameter at
vendor specific intervals. This implicit saving operation shall be done frequently enough to ensure that the
cumulative parameter values retain statistical significance (i.e., across power cycles). A TSD bit set to one
indicates that either the logical unit does not implicitly save the log parameter or implicit saving of the log
parameter has been disabled individually by an application client setting the TSD bit to one. An application
client may disable the implicit saving for all log parameters without changing any TSD bits using the GLTSD bit
in the Control mode page (see 7.5.8).

530 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

An enable threshold comparison (ETC) bit set to one indicates that a comparison to the threshold value is
performed whenever the cumulative value is updated. An ETC bit set to zero indicates that a comparison is not
performed. The value of the ETC bit is the same for cumulative and threshold parameters.

The threshold met criteria (TMC) field (see table 353) defines the basis for comparison of the cumulative value
and threshold value. The TMC field is valid only if the ETC bit is set to one. The value of the TMC field is the
same for cumulative parameters and threshold parameters.

Table 353 — Threshold met criteria (TMC) field

Code Basis for comparison

00b Every update of the cumulative value
01b Cumulative value equal to threshold value
10b Cumulative value not equal to threshold value
11b Cumulative value greater than threshold value

If the ETC bit is set to one and the result of the comparison is true, the device server shall establish a unit
attention condition (see SAM-5) for the initiator port associated with every I_T nexus, with the additional sense
code set to THRESHOLD CONDITION MET.

The FORMAT AND LINKING field (see table 354) indicates the type of log parameter.

Table 354 — FORMAT AND LINKING field

Code Log parameter type Reference

00b Bounded data counter 7.3.2.2.2.2
01b ASCII format list 7.3.2.2.2.4
10b Bounded data counter or 7.3.2.2.2.2 or
unbounded data counter 7.3.2.2.2.3
11b Binary format list 7.3.2.2.2.5

Working Draft SCSI Primary Commands - 4 (SPC-4) 531

T10/BSR INCITS 513 Revision 37 17 May 2014

7.3.2.2.2.2 Parameter control byte values for bounded data counter parameters

The device server shall return parameter control byte values associated with LOG SENSE commands and
process parameter control byte values associated with LOG SELECT commands as shown in table 355 for
any log parameter that is defined to be a bounded data counter log parameter.

Table 355 — Parameter control byte values for bounded data counter parameters

Value associated with

LOG LOG
Field SENSE SELECT
or bit commands commands Description
If the DU bit is set to zero, the device server shall update the log
parameter value to reflect all events that should be noted by that
DU 0 or 1 0 or 1 parameter. If the DU bit is set to one, the device server shall not
update the log parameter value except in response to a LOG
SELECT command that specifies a new value for the parameter.
If the TSD bit is set to zero, the device server shall save the log
parameter to its medium at vendor specific intervals. If the TSD bit
TSD 0 or 1 0 or 1
is set to one, the device server shall save the log parameter to its
medium.
If the ETC bit is set to one, a comparison to the threshold value is
ETC 0 or 1 0 or 1 performed whenever the cumulative value is updated. If the ETC
bit is set to zero, a comparison shall not be performed.
The TMC field (see table 353 in 7.3.2.2.2.1) defines the basis for
TMC any any comparison of the cumulative and threshold values. The TMC
field is valid only if the ETC bit is set to one.

FORMAT The log parameter is a data counter (see table 354 in 7.3.2.2.2.1)
AND 00b or 10b 00b or 10b and the handling of a parameter that reaches its maximum value
LINKING is described in this subclause

If a LOG SELECT command contains a bounded data counter log parameter in which the parameter control
byte values differ from those shown in table 355, then the device server shall terminate the command with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set
to INVALID FIELD IN PARAMETER LIST.

Each bounded data counter log parameter contains one saturating counter that is:

a) associated with one or more events; and

b) incremented whenever one of these events occurs.

In a bounded data counter log parameter, if the counter has associated with it a vendor specific maximum
value, then upon reaching this maximum value, the data counter shall not be incremented (i.e., its value does
not wrap).

In a bounded data counter log parameter, if the counter reaches its maximum value (i.e., saturates), the
device server shall:

a) set the DU bit to one;

b) handle other bounded data counter log parameters in the log page based on the contents of the
FORMAT AND LINKING field in each other log parameter as follows:

532 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

A) if the FORMAT AND LINKING field is set to 00b, then that other log parameter shall stop incrementing
until reinitialized by a LOG SELECT command; or
B) if the FORMAT AND LINKING field is set to 10b, then that other log parameter shall not stop
incrementing, but may be reinitialized by a LOG SELECT command.
and
c) not alter the handling of other log parameters in the log page that are:
A) unbounded data counter log parameters (see 7.3.2.2.2.3);
B) ASCII format list log parameters (see 7.3.2.2.2.4); and
C) binary format list log parameters (see 7.3.2.2.2.5).

The processing of a command shall not be altered as a result of the counter in a bounded data counter log
parameter reaching its maximum value (i.e., saturates). If the RLEC bit is set to one in the Control mode page
(see 7.5.8) and the processing of a command encounters no exception conditions other than the counter in a
bounded data counter log parameter reaching its maximum value, then the device server shall terminate the
command with CHECK CONDITION status, with the sense key set to RECOVERED ERROR, and the
additional sense code set to LOG COUNTER AT MAXIMUM.

7.3.2.2.2.3 Parameter control byte values for unbounded data counter parameters

The device server shall return parameter control byte values associated with LOG SENSE commands and
process parameter control byte values associated with LOG SELECT commands as shown in table 356 for
any log parameter that is defined to be an unbounded data counter log parameter.

Table 356 — Parameter control byte values for unbounded data counter parameters

Value associated with

LOG LOG
Field SENSE SELECT
or bit commands commands Description
If the DU bit is set to zero, the device server shall update the log
parameter value or values to reflect all events that should be
noted by that parameter. If the DU bit is set to one, the device
DU 0 or 1 0 or 1
server shall not update the log parameter value or values except
in response to a LOG SELECT command that specifies a new
value for the parameter.
If the TSD bit is set to zero, the device server shall save the log
parameter to its medium at vendor specific intervals. If the TSD bit
TSD 0 or 1 0 or 1
is set to one, the device server shall save the log parameter to its
medium.
Threshold comparisons are not performed for unbounded data
ETC 0 0
counter parameters
Threshold comparisons are not performed for unbounded data
TMC 00b ignored
counter parameters

FORMAT The log parameter is a data counter for which saturation of

AND 10b 10b another log parameter does not affect the incrementing of this log
LINKING parameter (see table 354 in 7.3.2.2.2.1).

If a LOG SELECT command contains an unbounded data counter log parameter in which the parameter
control byte values differ from those shown in table 356, then the device server shall terminate the command
with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense
code set to INVALID FIELD IN PARAMETER LIST.

Working Draft SCSI Primary Commands - 4 (SPC-4) 533

T10/BSR INCITS 513 Revision 37 17 May 2014

Each unbounded data counter log parameter contains one or more saturating counters or wrapping counters.
The description of each counter field in the log parameter defines when the device server modifies the
contents of the counter that is transferred in that field.

Changes in an unbounded data counter (e.g., a counter reaching saturation or another maximum value) shall
not affect the handling of other log parameters in the log page. The processing of a command and the status
returned by that command shall not be altered as a result of a counter in an unbounded data counter log
parameter saturating or reaching its maximum value.

The device server shall not change the value in the DU bit in an unbounded data counter log parameter unless
requested to do so by a LOG SELECT command.

7.3.2.2.2.4 Parameter control byte values for ASCII format list log parameters

The device server shall return parameter control byte values associated with LOG SENSE commands and
process parameter control byte values associated with LOG SELECT commands as shown in table 357 for
any log parameter that is defined to be an ASCII format (see 4.3.1) list log parameter.

Table 357 — Parameter control byte values for ASCII format list log parameters

Value associated with

LOG LOG
Field SENSE SELECT
or bit commands commands Description
DU 0 ignored The DU bit is not defined for list parameters.
If the TSD bit is set to zero, the device server shall save the log
parameter to its medium at vendor specific intervals. If the TSD bit
TSD 0 or 1 0 or 1
is set to one, the device server shall save the log parameter to its
medium.
ETC 0 0 Threshold comparisons are not performed for list parameters.
TMC 00b ignored Threshold comparisons are not performed for list parameters.
FORMAT The log parameter is an ASCII format list parameter (see table
AND 01b 01b
LINKING 354 in 7.3.2.2.2.1).

If a LOG SELECT command contains an ASCII format list log parameter in which the parameter control byte
values differ from those shown in table 357, then the device server shall terminate the command with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
INVALID FIELD IN PARAMETER LIST.

534 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.3.2.2.2.5 Parameter control byte values for binary format list log parameters

The device server shall return parameter control byte values associated with LOG SENSE commands and
process parameter control byte values associated with LOG SELECT commands as shown in table 358 for
any log parameter that is defined to be a binary format list log parameter.

Table 358 — Parameter control byte values for binary format list log parameters

Value associated with

LOG LOG
Field SENSE SELECT
or bit commands commands Description
DU 0 ignored The DU bit is not defined for list parameters.
If the TSD bit is set to zero, the device server shall save the log
parameter to its medium at vendor specific intervals. If the TSD bit
TSD 0 or 1 0 or 1
is set to one, the device server shall save the log parameter to its
medium.
ETC 0 0 Threshold comparisons are not performed for list parameters.
TMC 00b ignored Threshold comparisons are not performed for list parameters.
FORMAT The log parameter is an binary format list parameter (see table
AND 11b 11b
LINKING 354 in 7.3.2.2.2.1).

If a LOG SELECT command contains a binary format list log parameter in which the parameter control byte
values differ from those shown in table 358, then the device server shall terminate the command with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
INVALID FIELD IN PARAMETER LIST.

7.3.3 Resetting and setting log parameters

In a LOG SELECT command, an application client may specify that:

a) all the parameters in a log page or pages are to be reset (i.e., the PCR bit is set to one and the
PARAMETER LIST LENGTH field is set to zero); or
b) individual parameters in log page are to be changed to specified new values (i.e., the PCR bit is set to
zero and the PARAMETER LIST LENGTH field is not set to zero).

The device server handling of these requests to reset or change the cumulative value of a log parameter
depends on the log parameter that is being reset or changed. The keywords that describe how the device

Working Draft SCSI Primary Commands - 4 (SPC-4) 535

T10/BSR INCITS 513 Revision 37 17 May 2014

server handles these requests are defined in table 359.

Table 359 — Keywords for resetting or changing log parameter cumulative values

Device server handling when

Keyword PCR bit is set to one a PCR bit is set to zero b

Always Reset the log parameter Change the log parameter cumulative value.
cumulative value.
Reset Only Reset the log parameter If any changes are requested in the PARAMETER VALUE field
cumulative value. of the log parameter cumulative value, then:
a) terminate the command with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST,
Never Do not reset the log and the additional sense code set to INVALID FIELD
parameter cumulative value. IN PARAMETER LIST; and
Table 189 (see 6.7.1) b) do not make any requested changes in any field in
describes error conditions any log parameter cumulative value in any log page.
that may apply.
a
If the PCR bit is set to one and the PARAMETER LIST LENGTH field is not set to zero, the device server shall
terminate the LOG SELECT command (see table 351 in 7.3.2.1).
b
If the PCR bit is set to zero and the PARAMETER LIST LENGTH field is set to zero, no log parameters are
changed (see 6.7.2).

7.3.4 Application Client log page

7.3.4.1 Overview

Using the format shown in table 361, the Application Client log page provides a place for application clients to
store information. The parameter codes for the Application Client log page are listed in table 360.

Table 360 — Application Client log page parameter codes

Resettable or
Parameter code Description Changeable a Reference Support
0000h to 003Fh Mandatory
General Usage Application Client Always 7.3.4.2
0040h to 0FFFh Optional
all others Reserved
a
The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.

536 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The Application Client log page has the format shown in table 361.

Table 361 — Application Client log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (0Fh)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Application client log parameters
4
Application client log parameter (see 7.3.4.2)
•• •
[first]

••
•

Application client log parameter (see 7.3.4.2)

•• •
[last]
n

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 361 for the Application Client log
page.

Each application client log parameter contains the information described in 7.3.4.2.

7.3.4.2 General Usage Application Client log parameter

The General Usage Application Client log parameter has the format shown in table 362. This information may
be used to describe the system configuration and system problems, but the specific definition of the data is
application client specific.

Table 362 — General Usage Application Client log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (see table 360)
1 (LSB)
Parameter control byte – binary format list log parameter (see 7.3.2.2.2.5)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (FCh)

4
•• • GENERAL USAGE PARAMETER BYTES
255

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 360 for the General
Usage Application Client log parameter.

Working Draft SCSI Primary Commands - 4 (SPC-4) 537

T10/BSR INCITS 513 Revision 37 17 May 2014

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a binary format list log parameter (see 7.3.2.2.2.5) for the General Usage
Application Client log parameter.

The contents of the GENERAL USAGE PARAMETER BYTES field represent data sent to the device server in a
previous LOG SELECT command. If a previous LOG SELECT command has not occurred, the contents of
the GENERAL USAGE PARAMETER BYTES field are vendor specific.

7.3.5 Buffer Over-Run/Under-Run log page

7.3.5.1 Overview

Using the format shown in table 364, the Buffer Over-Run/Under-Run log page defines bounded data
counters that record the number of buffer over-runs or under-runs detected by the device server. The
parameter codes for the Buffer Over-Run/Under-Run log page are listed in table 363.

Table 363 — Buffer Over-Run/Under-Run log page parameter codes (part 1 of 2)

Incremented once per:

Parameter Over- or Experienced Problem Resettable or

code a Under-run by (or during) detected Changeable b Reference Support
0000h Under-run
Undefined
0001h Over-run
0020h Under-run
A command
0021h Over-run
Undefined Reset Only 7.3.5.2 At least one c
0040h Under-run
An I_T nexus
0041h Over-run
0080h Under-run
A unit of time d
0081h Over-run
0002h Under-run
Undefined
0003h Over-run
0022h Under-run
A command Service
0023h Over-run delivery
subsystem
Reset Only 7.3.5.2 At least one c
0042h Under-run
An I_T nexus busy
0043h Over-run
0082h Under-run
A unit of time d
0083h Over-run
a See SPC-2 for a description of how these parameter codes are derived.
b
The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.
c If the Buffer Over-Run/Under-Run log page is supported, at least one of the parameter codes listed in

this table shall be supported.

d
The size of the unit of time is vendor specific.

538 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 363 — Buffer Over-Run/Under-Run log page parameter codes (part 2 of 2)

Incremented once per:

Parameter Over- or Experienced Problem Resettable or

code a Under-run by (or during) detected Changeable b Reference Support
0004h Under-run
Undefined
0005h Over-run
0024h Under-run
A command
0025h Over-run Transfer
rate too Reset Only 7.3.5.2 At least one c
0044h Under-run slow
An I_T nexus
0045h Over-run
0084h Under-run
A unit of time d
0085h Over-run
all others Reserved
a
See SPC-2 for a description of how these parameter codes are derived.
b
The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.
c
If the Buffer Over-Run/Under-Run log page is supported, at least one of the parameter codes listed in
this table shall be supported.
d
The size of the unit of time is vendor specific.

A buffer over-run or under-run may occur if a SCSI initiator device does not transfer data to or from the logical
unit’s buffer fast enough to keep up with reading or writing the media. A buffer over-run condition may occur
during a read operation if a buffer full condition prevents continued transfer of data from the media to the
buffer. A buffer under-run condition may occur during a write operation if a buffer empty condition prevents
continued transfer of data to the media from the buffer.

Working Draft SCSI Primary Commands - 4 (SPC-4) 539

T10/BSR INCITS 513 Revision 37 17 May 2014

The Buffer Over-Run/Under-Run log page has the format shown in table 364.

Table 364 — Buffer Over-Run/Under-Run log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (01h)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Buffer over-run/under-run log parameters
4
Buffer Over-run/Under-run log parameter
•• •
(see 7.3.5.2) [first]

••
•

Buffer Over-run/Under-run log parameter

•• •
(see 7.3.5.2) [last]
n

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 364 for the Buffer
Over-Run/Under-Run log page.

Each Buffer Over-run/Under-run log parameter contains the information described in 7.3.5.2.

7.3.5.2 Buffer Over-run/Under-run log parameter

The Buffer Over-run/Under-run log parameter has the format shown in table 365.

Table 365 — Buffer Over-run/Under-run log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (see table 363)
1 (LSB)
Parameter control byte – bounded data counter log parameter (see 7.3.2.2.2.2)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (n-3)

4 (MSB)
•• • OVER-RUN/UNDER-RUN COUNTER
n (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 363 for the Buffer
Over-run/Under-run log parameter log parameter.

540 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a bounded data counter log parameter (see 7.3.2.2.2.2) for the Buffer
Over-run/Under-run log parameter log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1.

The OVER-RUN/UNDER-RUN COUNTER field contains the value for the counter described by the contents of the
PARAMETER CODE field.

Each counter contains the total number of times buffer over-run or under-run conditions have occurred since
the last time the counter was reset. The counter shall be incremented for each occurrence of a buffer
under-run or over-run condition and may be incremented more than once for multiple occurrences during the
processing of a single command.

7.3.6 Cache Memory Statistics log page

7.3.6.1 Overview

Using the format shown in table 368, the Cache Memory Statistics log page contains statistics and
performance results identified by the parameter codes listed in table 366.

Table 366 — Cache Memory Statistics log page parameter codes

Parameter Resettable or
code Description Changeable a Reference Support
0001h Read Cache Memory Hits Reset Only 7.3.6.2
0002h Reads To Cache Memory Reset Only 7.3.6.3
0003h Write Cache Memory Hits Reset Only 7.3.6.4
At least one b
0004h Writes From Cache Memory Reset Only 7.3.6.5
0005h Time From Last Hard Reset Never 7.3.6.6
0006h Time Interval Never 7.3.6.7
all others Reserved
a The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.
b
If the Cache Memory Statistics log page is supported, at least one of the parameter codes listed in this
table shall be supported.

The Cache Memory Statistics log page provides the following statistics and performance results associated
with the addressed logical unit:

a) Cache Memory Statistics log parameters:

A) number of read cache memory hits;
B) number of reads to cache memory;
C) number of write cache memory hits; and
D) number of writes from cache memory;
b) Hard Reset log parameter:
A) time from last hard reset (see SAM-5);
and
c) Time Interval log parameter:
A) time interval.

Working Draft SCSI Primary Commands - 4 (SPC-4) 541

T10/BSR INCITS 513 Revision 37 17 May 2014

In the Cache Memory Statistics log page, read commands and write commands are those shown in table 367.

Table 367 — Cache Memory Statistics log page commands

Read commands a Write commands a

READ(10) SYNCHRONIZE CACHE(10)
READ(12) SYNCHRONIZE CACHE(16)
READ(16) WRITE(10)
READ(32) WRITE(12)
PRE-FETCH(10) WRITE(16)
PRE-FETCH(16) WRITE(32)
WRITE AND VERIFY(10)
WRITE AND VERIFY(12)
WRITE AND VERIFY(16)
WRITE AND VERIFY(32)
a
All commands in this column are defined in SBC-3.

The Cache Memory Statistics log page has the format shown in table 368.

Table 368 — Cache Memory Statistics log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (1b) PAGE CODE (19h)
1 SUBPAGE CODE (20h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Cache memory statistics log parameters
4
Cache memory statistics log parameter
•• •
(see table 366) [first]

••
•

Cache memory statistics log parameter

•• •
(see table 366) [last]
n

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 368 for the Cache Memory
Statistics log page.

The contents of each cache memory statistics log parameter depends on the value in its PARAMETER CODE
field (see table 366).

542 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.3.6.2 Read Cache Memory Hits log parameter

The Read Cache Memory Hits log parameter has the format shown in table 369.

Table 369 — Read Cache Memory Hits log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0001h)
1 (LSB)
Parameter control byte – bounded data counter log parameter (see 7.3.2.2.2.2)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (08h)

4 (MSB)
•• • NUMBER OF READ CACHE MEMORY HITS
11 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 369 for the Read
Cache Memory Hits log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a bounded data counter log parameter (see 7.3.2.2.2.2) for the Read Cache
Memory Hits log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 369 for the Read
Cache Memory Hits log parameter.

The NUMBER OF READ CACHE MEMORY HITS field indicates the number of read commands (see table 367 in
7.3.6.1) received on an I_T nexus that resulted in:

a) user data being read from cache memory; and

b) no user data read from the medium before the read command being processed is completed.

The NUMBER OF READ CACHE MEMORY HITS field shall not be modified as a result of any read command that
contains an FUA bit (see SBC-3) set to one or an FUA_NV bit (see SBC-2) set to one.

The contents of the NUMBER OF READ CACHE MEMORY HITS field shall be set to zero as part of processing a hard
reset condition (see SAM-5).

Working Draft SCSI Primary Commands - 4 (SPC-4) 543

T10/BSR INCITS 513 Revision 37 17 May 2014

7.3.6.3 Reads To Cache Memory log parameter

The Reads To Cache Memory log parameter has the format shown in table 370.

Table 370 — Reads To Cache Memory log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0002h)
1 (LSB)
Parameter control byte – bounded data counter log parameter (see 7.3.2.2.2.2)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (08h)

4 (MSB)
•• • NUMBER OF READS TO CACHE MEMORY
11 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 370 for the Reads To
Cache Memory log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a bounded data counter log parameter (see 7.3.2.2.2.2) for the Reads To Cache
Memory log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 370 for the Reads To
Cache Memory log parameter.

The NUMBER OF READS TO CACHE MEMORY field indicates the number of read commands (see table 367 in
7.3.6.1) that move user data from the medium to cache memory.

The NUMBER OF READS TO CACHE MEMORY field shall not be modified as a result of any read command that
contains an FUA bit (see SBC-3) set to one or an FUA_NV bit (see SBC-2) set to one.

The contents of the NUMBER OF READS TO CACHE MEMORY field shall be set to zero as part of processing a hard
reset condition (see SAM-5).

544 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.3.6.4 Write Cache Memory Hits log parameter

The Write Cache Memory Hits log parameter has the format shown in table 371.

Table 371 — Write Cache Memory Hits log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0003h)
1 (LSB)
Parameter control byte – bounded data counter log parameter (see 7.3.2.2.2.2)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (08h)

4 (MSB)
•• • NUMBER OF WRITES FROM CACHE MEMORY
11 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 371 for the Write
Cache Memory Hits log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a bounded data counter log parameter (see 7.3.2.2.2.2) for the Writes From
Cache Memory log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 371 for the Write
Cache Memory Hits log parameter.

The NUMBER OF WRITES FROM CACHE MEMORY field indicates the number of write commands (see table 367 in
7.3.6.1) received on an I_T nexus that resulted in:

a) user data being written to cache memory; and

b) no user data written to the medium before the write command being processed is completed.

The NUMBER OF WRITES FROM CACHE MEMORY field shall not be modified as a result of any write command that
contains an FUA bit (see SBC-3) set to one or an FUA_NV bit (see SBC-2) set to one.

The contents of the NUMBER OF WRITES FROM CACHE MEMORY field shall be set to zero as part of processing a
hard reset condition (see SAM-5).

Working Draft SCSI Primary Commands - 4 (SPC-4) 545

T10/BSR INCITS 513 Revision 37 17 May 2014

7.3.6.5 Writes From Cache Memory log parameter

The Writes From Cache Memory log parameter has the format shown in table 372.

Table 372 — Writes From Cache Memory log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0004h)
1 (LSB)
Parameter control byte – bounded data counter log parameter (see 7.3.2.2.2.2)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (08h)

4 (MSB)
•• • NUMBER OF WRITES FROM CACHE MEMORY
11 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 372 for the Writes From
Cache Memory log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a bounded data counter log parameter (see 7.3.2.2.2.2) for the Writes From
Cache Memory log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 372 for the Writes
From Cache Memory log parameter.

The NUMBER OF WRITES FROM CACHE MEMORY field indicates the number of write commands (see table 367 in
7.3.6.1) that move user data from cache memory to the medium.

The NUMBER OF WRITES FROM CACHE MEMORY field shall not be modified as a result of any write command that
contains an FUA bit (see SBC-3) set to one or an FUA_NV bit (see SBC-2) set to one.

The contents of the NUMBER OF WRITES FROM CACHE MEMORY field shall be set to zero as part of processing a
hard reset condition (see SAM-5).

546 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.3.6.6 Time From Last Hard Reset log parameter

The Time From Last Hard Reset log parameter has the format shown in table 373.

Table 373 — Time From Last Hard Reset log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0005h)
1 (LSB)
Parameter control byte – bounded data counter log parameter (see 7.3.2.2.2.2)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (08h)

4 (MSB)
•• • LAST HARD RESET INTERVALS
11 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 373 for the Time From
Last Hard Reset log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a bounded data counter log parameter (see 7.3.2.2.2.2) for the Time From Last
Hard Reset log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 373 for the Time
From Last Hard Reset log parameter.

The LAST HARD RESET INTERVALS field indicates the number of time intervals that have occurred since a hard
reset was processed by the logical unit.

The time since a hard reset was processed by the logical unit is calculated as follows:

time = (time intervals since last hard reset  time interval)

where:

time intervals since last hard reset is the contents of the LAST HARD RESET INTERVALS field; and

time interval is the value represented in the time interval descriptor of the Time Interval log parameter
(see table 374 in 7.3.6.7).

Working Draft SCSI Primary Commands - 4 (SPC-4) 547

T10/BSR INCITS 513 Revision 37 17 May 2014

7.3.6.7 Time Interval log parameter

The Time Interval log parameter has the format shown in table 374.

Table 374 — Time Interval log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE
1 (LSB)
Parameter control byte – binary format list log parameter (see 7.3.2.2.2.5)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (08h)

4
•• • Time interval descriptor (see table 375)
11

The PARAMETER CODE field is described in 7.3.2.2.1. A PARAMETER CODE field set to:

a) 0003h identifies the log parameter being transferred as the Time Interval log parameter in the General
Statistics and Performance log page (see 7.3.7); or
b) 0006h identifies the log parameter being transferred as the Time Interval log parameter in the Cache
Memory Statistics log page (see 7.3.6).

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a binary format list log parameter (see 7.3.2.2.2.5) for the log parameters
described in this subclause.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 374 for the log
parameters described in this subclause.

The time interval descriptor (see table 375) contains the time interval in seconds used in various time interval
fields in:

a) the Time From Last Hard Reset log parameter (see 7.3.6.6);
b) the General Access Statistics and Performance log parameter (see 7.3.7.2);
c) the Force Unit Access Statistics and Performance log parameter (see 7.3.7.4);
d) the Group n Statistics and Performance log parameter (see 7.3.8.2); and
e) the Group n Force Unit Access Statistics and Performance log parameter (see 7.3.8.3).

Table 375 — Time interval descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • EXPONENT
3 (LSB)
4 (MSB)
•• • INTEGER
7 (LSB)

548 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The EXPONENT field contains the negative power of 10 exponent to multiply with the INTEGER field (e.g., a value
of 9 represents 10-9)

When multiplied by the exponent, the INTEGER field contains the value that represents one time interval (e.g., a
value of 5 in the INTEGER field and a value of 9 in the EXPONENT field represents a time interval of 510-9
seconds or 5 nanoseconds).

7.3.7 General Statistics and Performance log pages

7.3.7.1 Overview

Using the format shown in table 378, the General Statistics and Performance log page collects statistics and
performance information for all read CDBs and write CDBs based on the parameter codes listed in table 376.

Table 376 — General Statistics and Performance log page parameter codes

Parameter Resettable or
code Description Changeable a Reference Support
0001h General Access Statistics and
Reset Only 7.3.7.2 Mandatory
Performance
0002h Idle Time Reset Only 7.3.7.3 Mandatory
0003h Time Interval Never 7.3.6.7 Mandatory
0004h Force Unit Access Statistics and
Reset Only 7.3.7.4 Optional
Performance
all others Reserved
a
The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.

The General Statistics and Performance log page provides the following statistics and performance results
associated to the addressed logical unit:

a) Statistics and Performance log parameters:

A) number of read commands;
B) number of write commands;
C) number of read logical blocks transferred by a target port;
D) number of write logical blocks transferred by a target port;
E) read command processing time;
F) write command processing time;
G) sum of the command weights of the read commands plus write commands;
H) sum of the weighted command time of the read commands plus write commands;
b) Idle Time log parameter:
A) idle time;
c) Time Interval log parameter:
A) time interval;
and
d) Force Unit Access Statistics and Performance log parameters:
A) number of read commands with the FUA bit (see SBC-3) set to one;
B) number of write commands with the FUA bit set to one;
C) number of read commands with the FUA_NV bit (see SBC-2) set to one;
D) number of write commands with the FUA_NV bit set to one; and
E) read command with the FUA bit set to one processing intervals;

Working Draft SCSI Primary Commands - 4 (SPC-4) 549

T10/BSR INCITS 513 Revision 37 17 May 2014

F) write command with the FUA bit set to one processing intervals;
G) read command with the FUA_NV bit set to one processing intervals; and
H) write command with the FUA_NV bit set to one processing intervals.

In the General Statistics and Performance log page and the Group Statistics and Performance (n) log pages
(see 7.3.8), read commands and write commands are those shown in table 377.

Table 377 — Statistics and Performance log pages commands

Read commands a Write commands a

POPULATE TOKEN WRITE USING TOKEN
READ(10) UNMAP
READ(12) WRITE(10)
READ(16) WRITE(12)
READ(32) WRITE(16)
WRITE(32)
WRITE AND VERIFY(10)
WRITE AND VERIFY(12)
WRITE AND VERIFY(16)
WRITE AND VERIFY(32)
a
See SBC-3.

The General Statistics and Performance log page has the format shown in table 378.

Table 378 — General Statistics and Performance log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (19h)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
General statistics and performance log parameters
4
General statistics and performance log
•• •
parameter (see table 376) [first]

••
•

General statistics and performance log

•• •
parameter (see table 376) [last]
n

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 378 for the General Statistics and
Performance log page.

The contents of each general statistics and performance log parameter depends on the value in its PARAMETER
CODE field (see table 376).

550 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.3.7.2 General Access Statistics and Performance log parameter

The General Access Statistics and Performance log parameter has the format shown in table 379.

Table 379 — General Access Statistics and Performance log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0001h)
1 (LSB)
Parameter control byte – unbounded data counter log parameter (see 7.3.2.2.2.3)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (40h)

4 (MSB)
•• • NUMBER OF READ COMMANDS
11 (LSB)
12 (MSB)
•• • NUMBER OF WRITE COMMANDS
19 (LSB)
20 (MSB)
•• • NUMBER OF LOGICAL BLOCKS RECEIVED
27 (LSB)
28 (MSB)
•• • NUMBER OF LOGICAL BLOCKS TRANSMITTED
35 (LSB)
36 (MSB)
•• • READ COMMAND PROCESSING INTERVALS
43 (LSB)
44 (MSB)
•• • WRITE COMMAND PROCESSING INTERVALS
51 (LSB)
52 (MSB)
WEIGHTED NUMBER OF READ COMMANDS
•• •
PLUS WRITE COMMANDS
59 (LSB)
60 (MSB)
WEIGHTED READ COMMAND PROCESSING
•• •
PLUS WRITE COMMAND PROCESSING
67 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 379 for the General
Access Statistics and Performance log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for an unbounded data counter log parameter (see 7.3.2.2.2.3) for the General
Access Statistics and Performance log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 379 for the General
Access Statistics and Performance log parameter.

Working Draft SCSI Primary Commands - 4 (SPC-4) 551

T10/BSR INCITS 513 Revision 37 17 May 2014

The NUMBER OF READ COMMANDS field indicates the number of read commands (see table 377 in 7.3.7.1)
received by the logical unit.

The NUMBER OF WRITE COMMANDS field indicates the number of write commands (see table 377 in 7.3.7.1)
received by the logical unit.

The NUMBER OF LOGICAL BLOCKS RECEIVED field indicates the number of logical blocks received by any SCSI
target port for the logical unit as a result of write commands (see table 377 in 7.3.7.1).

The NUMBER OF LOGICAL BLOCKS TRANSMITTED field indicates the number of logical blocks transmitted by any
SCSI target port for the logical unit as a result of read commands (see table 377 in 7.3.7.1).

The READ COMMAND PROCESSING INTERVALS field indicates the cumulative number of time intervals (see
7.3.6.7) spent by the logical unit processing read commands (see table 377 in 7.3.7.1).

The WRITE COMMAND PROCESSING INTERVALS field indicates the cumulative number of time intervals (see
7.3.6.7) spent by the logical unit processing write commands (see table 377 in 7.3.7.1).

If command priority is supported (see SAM-5), then the WEIGHTED NUMBER OF READ COMMANDS PLUS WRITE
COMMANDS field indicates the cumulative command weight of the read commands and write commands (see
table 377 in 7.3.7.1) processed by the logical unit.

Command weight is calculated as follows:

command weight = (360 360  command priority)

where:

command priority is as defined in SAM-5. However, if the computed command priority is zero, then
the command priority shall be set to seven (i.e., a mid-range command priority value).

If command priority is not supported, then the WEIGHTED NUMBER OF READ COMMANDS PLUS WRITE COMMANDS
field shall be set to zero.

If command priority is supported (see SAM-5), then the WEIGHTED READ COMMAND PROCESSING PLUS WRITE
COMMAND PROCESSING field indicates the cumulative weighted command time of the time intervals (see
7.3.6.7) spent processing read commands and write commands (see table 377 in 7.3.7.1) by the logical unit.

Weighted command time is calculated as follows:

weighted command time = (time increments processing the command  time interval)
 (360 360  command priority)

where:

time increments processing a command is the number of time intervals from the time the task
manager places the command into a task set until the device server sends a SCSI transport protocol
service response for the command;

time interval is the value represented in the TIME INTERVAL DESCRIPTOR field of the Time Interval log
parameter (see 7.3.6.7), and

command priority is as defined in SAM-5. However, if the computed command priority is zero, then
the command priority time shall be set to seven (i.e., a mid-range command priority value).

552 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If command priority is not supported, then the WEIGHTED READ COMMAND PROCESSING PLUS WRITE COMMAND
PROCESSING field shall be set to zero.

7.3.7.3 Idle Time log parameter

The Idle Time log parameter has the format shown in table 380.

Table 380 — Idle Time log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0002h)
1 (LSB)
Parameter control byte – unbounded data counter log parameter (see 7.3.2.2.2.3)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (08h)

4 (MSB)
•• • IDLE TIME INTERVALS
11 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 380 for the Idle Time
log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for an unbounded data counter log parameter (see 7.3.2.2.2.3) for the Idle Time log
parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 380 for the Idle Time
log parameter.

The IDLE TIME INTERVALS field indicates the cumulative number of idle times spent while there are no
commands in the task set and there are no commands being processed by the logical unit.

Idle time is calculated as follows:

idle time = (time increments not processing commands  time interval)

where:

time increments not processing commands is the number of time intervals while there are no
commands in the task set and the device server has sent a SCSI transport protocol service response
for all commands being processed (i.e., there are no commands to be processed or being processed);
and

time interval is the value represented in the time interval descriptor of the Time Interval log parameter
(see 7.3.6.7).

Working Draft SCSI Primary Commands - 4 (SPC-4) 553

T10/BSR INCITS 513 Revision 37 17 May 2014

7.3.7.4 Force Unit Access Statistics and Performance log parameter

The Force Unit Access Statistics and Performance log parameter has the format shown in table 381.

Table 381 — Force Unit Access Statistics and Performance log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0004h)
1 (LSB)
Parameter control byte – unbounded data counter log parameter (see 7.3.2.2.2.3)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (40h)

4 (MSB)
•• • NUMBER OF READ FUA COMMANDS
11 (LSB)
12 (MSB)
•• • NUMBER OF WRITE FUA COMMANDS
19 (LSB)
20 (MSB)
•• • NUMBER OF READ FUA_NV COMMANDS
27 (LSB)
28 (MSB)
•• • NUMBER OF WRITE FUA_NV COMMANDS
35 (LSB)
36 (MSB)
•• • READ FUA COMMAND PROCESSING INTERVALS
43 (LSB)
44 (MSB)
•• • WRITE FUA COMMAND PROCESSING INTERVALS
51 (LSB)
52 (MSB)
•• • READ FUA_NV COMMAND PROCESSING INTERVALS
59 (LSB)
60 (MSB)
•• • WRITE FUA_NV COMMAND PROCESSING INTERVALS
67 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 381 for the Force Unit
Access Statistics and Performance log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for an unbounded data counter log parameter (see 7.3.2.2.2.3) for the Force Unit
Access Statistics and Performance log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 381 for the Force
Unit Access Statistics and Performance log parameter.

554 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The NUMBER OF READ FUA COMMANDS field indicates the number of read commands (see table 377 in 7.3.7.1)
with the FUA bit (see SBC-3) set to one received by the logical unit.

The NUMBER OF WRITE FUA COMMANDS field indicates the number of write commands (see table 377 in 7.3.7.1)
with the FUA bit (see SBC-3) set to one received by the logical unit.

The NUMBER OF READ FUA_NV COMMANDS field indicates the number of read commands (see table 377 in
7.3.7.1) with the FUA_NV bit (see SBC-2) set to one received by the logical unit.

The NUMBER OF WRITE FUA_NV COMMANDS field indicates the number of write commands (see table 377 in
7.3.7.1) with the FUA_NV bit (see SBC-2) set to one received by the logical unit.

The READ FUA COMMAND PROCESSING INTERVALS field indicates the cumulative number of time intervals (see
7.3.6.7) spent by the logical unit processing read commands (see table 377 in 7.3.7.1) with the FUA bit (see
SBC-3) set to one.

The WRITE FUA COMMAND PROCESSING INTERVALS field indicates the cumulative number of time intervals (see
7.3.6.7) spent by the logical unit processing write commands (see table 377 in 7.3.7.1) with the FUA bit (see
SBC-3) set to one.

The READ FUA_NV COMMAND PROCESSING INTERVALS field indicates the cumulative number of time intervals
(see 7.3.6.7) spent by the logical unit processing read commands (see table 377 in 7.3.7.1) with the FUA_NV
bit (see SBC-2) set to one.

The WRITE FUA_NV COMMAND PROCESSING INTERVALS field indicates the cumulative number of time intervals
(see 7.3.6.7) spent by the logical unit processing write commands (see table 377 in 7.3.7.1) with the FUA_NV
bit (see SBC-2) set to one.

7.3.8 Group Statistics and Performance (n) log pages

7.3.8.1 Overview

Using the format shown in table 383, Group Statistics and Performance (n) log pages collect statistics and
performance information for the group number specified in a read CDB or a write CDB based on the
parameter codes listed in table 382.

Table 382 — Group Statistics and Performance log page parameter codes

Parameter Resettable or
code Description Changeable a Reference Support
0001h Group n Statistics and Performance Reset Only 7.3.8.2 Mandatory
0004h Group n Force Unit Access Statistics
Reset Only 7.3.8.3 Optional
and Performance
all others Reserved
a
The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.

The Group Statistics and Performance (n) log pages provide the following statistics and performance results
associated to the addressed logical unit and the GROUP NUMBER field:

a) Statistics and Performance log parameters:

A) number of read commands;

Working Draft SCSI Primary Commands - 4 (SPC-4) 555

T10/BSR INCITS 513 Revision 37 17 May 2014

B) number of write commands;

C) number of read logical blocks transferred by a target port;
D) number of write logical blocks transferred by a target port;
E) read command processing time;
F) write command processing time;
and
b) Force Unit Access Statistics and Performance log parameters:
A) number of read commands with the FUA bit (see SBC-3) set to one;
B) number of write commands with the FUA bit set to one;
C) number of read commands with the FUA_NV bit (see SBC-2) set to one;
D) number of write commands with the FUA_NV bit set to one;
E) read command with the FUA bit set to one processing intervals;
F) write command with the FUA bit set to one processing intervals;
G) read command with the FUA_NV bit set to one processing intervals; and
H) write command with the FUA_NV bit set to one processing intervals.

In the Group Statistics and Performance (n) log pages, read commands and write commands are those shown
in table 377 (see 7.3.7.1).

The Group Statistics and Performance (n) log pages provide logging of statistics and performance of read and
write operations based on group numbers. There are 31 Group Statistics and Performance (n) log pages one
for each group number. The statistics and performance information associated with each group number is
collected in the corresponding Group Statistics and Performance (n) log page (e.g., operations associated
with group number 16 are logged in the Group Statistics and Performance (16) log page).

Each Group Statistics and Performance (n) log page has the format shown in table 383.

Table 383 — Group Statistics and Performance (n) log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (1b) PAGE CODE (19h)
1 SUBPAGE CODE (01h to 1Fh) (see table 384) a
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Group statistics and performance log parameters
4
General statistics and performance log
•• •
parameter (see table 382) [first]

••
•

General statistics and performance log

•• •
parameter (see table 382) [last]
n
a
The log parameter associated with the specific group number as specified by the value of n is collected
in the corresponding log parameter (e.g., the count of read commands with the GROUP NUMBER field set
to 9 is logged in the GROUP N NUMBER OF READ COMMANDS field in the Group n Statistics and
Performance log parameter of the Group Statistics and Performance (9) log page).

556 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 383 for the Group Statistics and
Performance (n) log pages.

The SUBPAGE CODE field (see table 384) associates the Group Statistics and Performance (n) log page being
transferred with the contents of the GROUP NUMBER field in a read command CDB or write command CDB (see
table 377 in 7.3.7.1 and SBC-3).

Table 384 — Group Statistics and Performance (n) subpage codes (part 1 of 2)

Subpage code Log page name a Group number b

01h Group Statistics and Performance (1) 00001b
02h Group Statistics and Performance (2) 00010b
03h Group Statistics and Performance (3) 00011b
04h Group Statistics and Performance (4) 00100b
05h Group Statistics and Performance (5) 00101b
06h Group Statistics and Performance (6) 00110b
07h Group Statistics and Performance (7) 00111b
08h Group Statistics and Performance (8) 01000b
09h Group Statistics and Performance (9) 01001b
0Ah Group Statistics and Performance (10) 01010b
0Bh Group Statistics and Performance (11) 01011b
0Ch Group Statistics and Performance (12) 01100b
0Dh Group Statistics and Performance (13) 01101b
0Eh Group Statistics and Performance (14) 01110b
0Fh Group Statistics and Performance (15) 01111b
10h Group Statistics and Performance (16) 10000b
11h Group Statistics and Performance (17) 10001b
12h Group Statistics and Performance (18) 10010b
13h Group Statistics and Performance (19) 10011b
14h Group Statistics and Performance (20) 10100b
15h Group Statistics and Performance (21) 10101b
a The statistics and performance information associated with a group number is
collected in the corresponding Group Statistics and Performance (n) log page
(e.g., operations associated with group number 10000b are logged in the
Group Statistics and Performance (16) log page).
b
The GROUP NUMBER field is from the read command CDB or the write
command CDB (see table 377 in 7.3.7.1 and SBC-3).

Working Draft SCSI Primary Commands - 4 (SPC-4) 557

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 384 — Group Statistics and Performance (n) subpage codes (part 2 of 2)

Subpage code Log page name a Group number b

16h Group Statistics and Performance (22) 10110b
17h Group Statistics and Performance (23) 10111b
18h Group Statistics and Performance (24) 11000b
19h Group Statistics and Performance (25) 11001b
1Ah Group Statistics and Performance (26) 11010b
1Bh Group Statistics and Performance (27) 11011b
1Ch Group Statistics and Performance (28) 11100b
1Dh Group Statistics and Performance (29) 11101b
1Eh Group Statistics and Performance (30) 11110b
1Fh Group Statistics and Performance (31) 11111b
a The statistics and performance information associated with a group number is
collected in the corresponding Group Statistics and Performance (n) log page
(e.g., operations associated with group number 10000b are logged in the
Group Statistics and Performance (16) log page).
b
The GROUP NUMBER field is from the read command CDB or the write
command CDB (see table 377 in 7.3.7.1 and SBC-3).

The contents of each group statistics and performance log parameter depends on the value in its PARAMETER
CODE field (see table 382).

558 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.3.8.2 Group n Statistics and Performance log parameter

The Group n Statistics and Performance log parameter has the format shown in table 385.

Table 385 — Group n Statistics and Performance log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0001h)
1 (LSB)
Parameter control byte – unbounded data counter log parameter (see 7.3.2.2.2.3)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (30h)

4 (MSB)
•• • GROUP N NUMBER OF READ COMMANDS
11 (LSB)
12 (MSB)
•• • GROUP N NUMBER OF WRITE COMMANDS
19 (LSB)
20 (MSB)
•• • GROUP N NUMBER OF LOGICAL BLOCKS RECEIVED
27 (LSB)
28 (MSB)
GROUP N NUMBER OF LOGICAL BLOCKS
•• •
TRANSMITTED
35 (LSB)
36 (MSB)
•• • GROUP N READ COMMAND PROCESSING INTERVALS
43 (LSB)
44 (MSB)
•• • GROUP N WRITE COMMAND PROCESSING INTERVALS
51 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 385 for the Group n
Statistics and Performance log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for an unbounded data counter log parameter (see 7.3.2.2.2.3) for the Group n
Statistics and Performance log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 385 for the Group n
Statistics and Performance log parameter.

The GROUP N NUMBER OF READ COMMANDS field indicates the number of read commands (see table 377 in
7.3.7.1) received by the logical unit.

The GROUP N NUMBER OF WRITE COMMANDS field indicates the number of write commands (see table 377 in
7.3.7.1) received by the logical unit.

Working Draft SCSI Primary Commands - 4 (SPC-4) 559

T10/BSR INCITS 513 Revision 37 17 May 2014

The GROUP N NUMBER OF LOGICAL BLOCKS RECEIVED field indicates the number of logical blocks received by
any SCSI target port for the logical unit as a result of write commands (see table 377 in 7.3.7.1).

The GROUP N NUMBER OF LOGICAL BLOCKS TRANSMITTED field indicates the number of logical blocks transmitted
by any SCSI target port for the logical unit as a result of read commands (see table 377 in 7.3.7.1).

The GROUP N READ COMMAND PROCESSING INTERVALS field indicates the cumulative number of time intervals
spent by the logical unit processing read commands (see table 377 in 7.3.7.1). Time intervals are defined in
the Time Interval log parameter (see 7.3.6.7) as returned in the General Statistics and Performance log page
(see 7.3.7).

The GROUP N WRITE COMMAND PROCESSING INTERVALS field indicates the cumulative number of time intervals
spent by the logical unit processing write commands (see table 377 in 7.3.7.1). Time intervals are defined in
the Time Interval log parameter (see 7.3.6.7) as returned in the General Statistics and Performance log page
(see 7.3.7).

560 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.3.8.3 Group n Force Unit Access Statistics and Performance log parameter

The Group n Force Unit Access Statistics and Performance log parameter has the format shown in table 386.

Table 386 — Group n Force Unit Access Statistics and Performance log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0004h)
1 (LSB)
Parameter control byte – unbounded data counter log parameter (see 7.3.2.2.2.3)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (40h)

4 (MSB)
•• • GROUP N NUMBER OF READ FUA COMMANDS
11 (LSB)
12 (MSB)
•• • GROUP N NUMBER OF WRITE FUA COMMANDS
19 (LSB)
20 (MSB)
•• • GROUP N NUMBER OF READ FUA_NV COMMANDS
27 (LSB)
28 (MSB)
•• • GROUP N NUMBER OF WRITE FUA_NV COMMANDS
35 (LSB)
36 (MSB)
GROUP N READ FUA COMMAND PROCESSING
•• •
INTERVALS
43 (LSB)
44 (MSB)
GROUP N WRITE FUA COMMAND PROCESSING
•• •
INTERVALS
51 (LSB)
52 (MSB)
GROUP N READ FUA_NV COMMAND PROCESSING
•• •
INTERVALS
59 (LSB)
60 (MSB)
GROUP N WRITE FUA_NV COMMAND PROCESSING
•• •
INTERVALS
67 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 386 for the Group n
Force Unit Access Statistics and Performance log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for an unbounded data counter log parameter (see 7.3.2.2.2.3) for the Group n
Force Unit Access Statistics and Performance log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 386 for the Group n
Force Unit Access Statistics and Performance log parameter.

Working Draft SCSI Primary Commands - 4 (SPC-4) 561

T10/BSR INCITS 513 Revision 37 17 May 2014

The GROUP N NUMBER OF READ FUA COMMANDS field indicates the number of read commands (see table 377 in
7.3.7.1) with the FUA bit (see SBC-3) set to one received by the logical unit.

The GROUP N NUMBER OF WRITE FUA COMMANDS field indicates the number of write commands (see table 377 in
7.3.7.1) with the FUA bit (see SBC-3) set to one received by the logical unit.

The GROUP N NUMBER OF READ FUA_NV COMMANDS field indicates the number of read commands (see table
377 in 7.3.7.1) with the FUA_NV bit (see SBC-2) set to one received by the logical unit.

The GROUP N NUMBER OF WRITE FUA_NV COMMANDS field indicates the number of write commands (see table
377 in 7.3.7.1) with the FUA_NV bit (see SBC-2) set to one received by the logical unit.

The GROUP N READ FUA COMMAND PROCESSING INTERVALS field indicates the cumulative number of time
intervals spent by the logical unit processing read commands (see table 377 in 7.3.7.1) with the FUA bit (see
SBC-3) set to one. Time intervals are defined in the Time Interval log parameter (see 7.3.6.7) as returned in
the General Statistics and Performance log page (see 7.3.7).

The GROUP N WRITE FUA COMMAND PROCESSING INTERVALS field indicates the cumulative number of time
intervals spent by the logical unit processing write commands (see table 377 in 7.3.7.1) with the FUA bit (see
SBC-3) set to one. Time intervals are defined in the Time Interval log parameter (see 7.3.6.7) as returned in
the General Statistics and Performance log page (see 7.3.7).

The GROUP N READ FUA_NV COMMAND PROCESSING INTERVALS field indicates the cumulative number of time
intervals spent by the logical unit processing read commands (see table 377 in 7.3.7.1) with the FUA_NV bit
(see SBC-2) set to one. Time intervals are defined in the Time Interval log parameter (see 7.3.6.7) as returned
in the General Statistics and Performance log page (see 7.3.7).

The GROUP N WRITE FUA_NV COMMAND PROCESSING INTERVALS field indicates the cumulative number of time
intervals spent by the logical unit processing write commands (see table 377 in 7.3.7.1) with the FUA_NV bit
(see SBC-2) set to one. Time intervals are defined in the Time Interval log parameter (see 7.3.6.7) as returned
in the General Statistics and Performance log page (see 7.3.7).

7.3.9 Informational Exceptions log page

7.3.9.1 Overview

Using the format shown in table 388, the Informational Exceptions log page returns details about informational
exceptions identified by the parameter codes listed in table 387.

Table 387 — Informational Exceptions log page parameter codes

Resettable or
Parameter code Description Changeable a Reference Support
0000h Informational Exceptions General Reset Only 7.3.9.2 Mandatory
0001h to FFFFh Vendor specific
a
The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.

562 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The Informational Exceptions log page has the format shown in table 388.

Table 388 — Informational Exceptions log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (2Fh)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Informational exceptions log parameters
4
Informational exceptions log parameter
•• •
(see table 387) [first]

••
•

Informational exceptions log parameter

•• •
(see table 387) [last]
n

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 388 for the Informational
Exceptions log page.

The contents of each informational exceptions log parameter depends on the value in its PARAMETER CODE
field (see table 387).

7.3.9.2 Informational Exceptions General log parameter

The Informational Exceptions General log parameter has the format shown in table 389.

Table 389 — Informational Exceptions General log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0000h)
1 (LSB)
Parameter control byte – binary format list log parameter (see 7.3.2.2.2.5)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (n-3)

4 INFORMATIONAL EXCEPTION ADDITIONAL SENSE CODE

5 INFORMATIONAL EXCEPTION ADDITIONAL SENSE CODE QUALIFIER

6 MOST RECENT TEMPERATURE READING

7
•• • Vendor specific
n

Working Draft SCSI Primary Commands - 4 (SPC-4) 563

T10/BSR INCITS 513 Revision 37 17 May 2014

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 389 for the
Informational Exceptions General log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a binary format list log parameter (see 7.3.2.2.2.5) for the Informational
Exceptions General log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1. The parameter length shall be at least 04h.

If the INFORMATIONAL EXCEPTION ADDITIONAL SENSE CODE field is set to zero, no informational exception
condition exists and contents of the INFORMATIONAL EXCEPTION ADDITIONAL SENSE CODE QUALIFIER field are
unspecified. If the INFORMATIONAL EXCEPTION ADDITIONAL SENSE CODE field is set to a value other than zero, an
informational exception condition exists that has an additional sense code indicated by INFORMATIONAL
EXCEPTION ADDITIONAL SENSE CODE field and an ADDITIONAL SENSE CODE QUALIFIER field indicated by the
INFORMATIONAL EXCEPTION ADDITIONAL SENSE CODE QUALIFIER field.

The MOST RECENT TEMPERATURE READING field indicates the temperature in degrees Celsius of the SCSI target
device at the time the LOG SENSE command is performed. Temperatures equal to or less than zero degrees
Celsius shall be indicated by a value of zero. If the device server is unable to detect a valid temperature as a
result of a sensor failure or other condition, then the value returned shall be FFh. The temperature should be
reported with an accuracy of plus or minus three Celsius degrees while the device is operating at a steady
state within the environmental limits specified for the device.

7.3.10 Last n Deferred Errors or Asynchronous Events log page

7.3.10.1 Overview

Using the format shown in table 391, the Last n Deferred Errors or Asynchronous Events log page provides
one or more Deferred Error or Asynchronous Event log parameters (see 7.3.10.2). The number of Deferred
Error or Asynchronous Event log parameters supported (i.e., n) is vendor specific. The parameter codes for
the Last n Deferred Errors or Asynchronous Events log page are listed in table 390.

Table 390 — Last n Deferred Errors or Asynchronous Events log page parameter codes

Resettable or
Parameter code Description Changeable a Reference Support
0000h Deferred Error or Mandatory
Reset Only 7.3.10.2
0001h to FFFFh Asynchronous Event Optional
a
The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.

564 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The Last n Deferred Errors or Asynchronous Events log page has the format shown in table 391.

Table 391 — Last n Deferred Errors or Asynchronous Events log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (0Bh)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Deferred error or asynchronous event log parameters
4
Deferred error or asynchronous event log
•• •
parameter (see 7.3.10.2) [first]

••
•

Deferred error or asynchronous event log

•• •
parameter (see 7.3.10.2) [last]
n

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 391 for the Last n Deferred Errors
or Asynchronous Events log page.

The contents of each deferred error or asynchronous event log parameter are described in 7.3.10.2. The
device server shall assign parameter codes to log parameters as follows:

a) if the vendor specific number of supported deferred error or asynchronous event log parameters has
not been exceeded, then the parameter code in each log parameter shall indicate the relative time at
which the deferred error or asynchronous event occurred. A higher parameter code indicates that the
deferred error or asynchronous event occurred at a more recent time; or
b) if the vendor specific number of supported deferred error or asynchronous event log parameters has
been exceeded, then:
A) the log parameter with the oldest data shall be overwritten with the newest data (i.e., after the
highest supported parameter code is used, reporting wraps so that the next deferred error or
asynchronous event is reported in the log parameter with parameter code zero); and
B) if the RLEC bit is set to one in the Control mode page (see 7.5.8) and a LOG SELECT command
that transfers the Last n Deferred Errors or Asynchronous Events log page completes without
error, except for the parameter code being at its maximum value, then the device server shall
terminate the command with CHECK CONDITION status, with the sense key set to
RECOVERED ERROR, and the additional sense code set to LOG LIST CODES EXHAUSTED.

Working Draft SCSI Primary Commands - 4 (SPC-4) 565

T10/BSR INCITS 513 Revision 37 17 May 2014

7.3.10.2 Deferred Error or Asynchronous Event log parameters

Each Deferred Error or Asynchronous Event log parameter has the format shown in table 392.

Table 392 — Deferred Error or Asynchronous Event log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (see table 390)
1 (LSB)
Parameter control byte – binary format list log parameter (see 7.3.2.2.2.5)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (n-3)

4
•• • SENSE DATA (see 4.5)
n

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 390 for the Deferred
Error or Asynchronous Event log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a binary format list log parameter (see 7.3.2.2.2.5) for the Deferred Error or
Asynchronous Event log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1.

The SENSE DATA field contains the sense data (see 4.5) for a deferred error or asynchronous event that has
occurred.

7.3.11 Last n Error Events log page

7.3.11.1 Overview

Using the format shown in table 394, the Last n Error Events log page provides one or more Error Event log
parameters (see 7.3.11.2). The number of these Error Event log parameters supported (i.e., n) is vendor
specific. The parameter codes for the Last n Error Events log page are listed in table 393.

Table 393 — Last n Error Events log page parameter codes

Resettable or
Parameter code Description Changeable a Reference Support
0000h Mandatory
Error Event Reset Only 7.3.11.2
0001h to FFFFh Optional
a
The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.

566 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The Last n Error Events log page has the format shown in table 394.

Table 394 — Last n Error Events log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (07h)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Error event log parameters
4
•• • Error event log parameter (see 7.3.11.2) [first]

••
•

•• • Error event log parameter (see 7.3.11.2) [last]

n

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 394 for the Last n Error Events log
page.

The contents of each error event log parameter is described are 7.3.11.2. The device server shall assign
parameter codes to log parameters as follows:

a) if the vendor specific number of supported error event log parameters has not been exceeded, then
the parameter code in each log parameter shall indicate the relative time at which the error event
occurred. A higher parameter code indicates that the error event occurred later in time; or
b) if the vendor specific number of supported error event log parameters has been exceeded, then:
A) the log parameter with the oldest data shall be overwritten with the newest data (i.e., after the
highest supported parameter code is used, reporting wraps so that the next error event is
reported in the log parameter with parameter code zero); and
B) if the RLEC bit is set to one in the Control mode page (see 7.5.8) and a LOG SELECT command
that transfers the Last n Error Events log page completes without error, except for the parameter
code being at its maximum value, then the device server shall terminate the command with
CHECK CONDITION status, with the sense key set to RECOVERED ERROR, and the additional
sense code set to LOG LIST CODES EXHAUSTED.

Working Draft SCSI Primary Commands - 4 (SPC-4) 567

T10/BSR INCITS 513 Revision 37 17 May 2014

7.3.11.2 Error Event log parameters

Each Error Event log parameter has the format shown in table 395.

Table 395 — Error Event log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (see table 393)
1 (LSB)
Parameter control byte – ASCII format list log parameter (see 7.3.2.2.2.4)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (n-3)

4
•• • ERROR EVENT DATA
n

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 393 for the Error Event
log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a ASCII format list log parameter (see 7.3.2.2.2.4) for the Error Event log
parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1.

The ERROR EVENT DATA field contains ASCII data (see 4.3.1) that may describe the error event. The contents
of the ERROR EVENT DATA field are not defined by this standard.

7.3.12 Non-Medium Error log page

7.3.12.1 Overview

Using the format shown in table 397, the Non-Medium Error log page provides for counting the occurrences of
recoverable error events other than read (see 7.3.15), read reverse (see 7.3.16), verify (see 7.3.23), or write
(see 7.3.24) failures. No discrimination among the various types of events is provided. Vendor specific
discrimination may be provided through the vendor specific parameter codes. The parameter codes for the
Non-Medium Error log page are listed in table 396.

Table 396 — Non-Medium Error log page parameter codes

Resettable or
Parameter code Description Changeable a Reference Support
0000h Non-Medium Error Count Reset Only 7.3.12.2 Mandatory
8000h to FFFFh Vendor specific error counts
all others Reserved
a The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.

568 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The Non-Medium Error log page has the format shown in table 397.

Table 397 — Non-Medium Error log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (06h)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Non-medium error log parameters
4
Non-medium error log parameter (see table 396)
•• •
[first]

••
•

Non-medium error log parameter (see table 396)

•• •
[last]
n

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 397 for the Non-Medium Error log
page.

The contents of each non-medium error log parameter depends on the value in its PARAMETER CODE field (see
table 396).

7.3.12.2 Non-Medium Error Count log parameter

The Non-Medium Error Count log parameter has the format shown in table 398.

Table 398 — Non-Medium Error Count log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0000h)
1 (LSB)
Parameter control byte – bounded data counter log parameter (see 7.3.2.2.2.2)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (n-3)

4 (MSB)
•• • NON-MEDIUM ERROR COUNT
n (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 398 for the
Non-Medium Error Count log parameter.

Working Draft SCSI Primary Commands - 4 (SPC-4) 569

T10/BSR INCITS 513 Revision 37 17 May 2014

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a bounded data counter log parameter (see 7.3.2.2.2.2) for the Non-Medium
Error Count log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1.

The NON-MEDIUM ERROR COUNT field indicates the number of recoverable error events other than read, read
reverse, verify, or write failures.

7.3.13 Power Condition Transitions log page

7.3.13.1 Overview

Using the format shown in table 400, the Power Condition Transitions log page provides a count of the
occurrences of power condition transition events using the parameter codes listed in table 399.

Table 399 — Power Conditions Transitions log page parameter codes

Parameter Resettable or
code Description Changeable a Reference Support
0001h Accumulated Transitions to active Mandatory
0002h Accumulated Transitions to idle_a
0003h Accumulated Transitions to idle_b
Never 7.3.13.2
0004h Accumulated Transitions to idle_c At least one b
0008h Accumulated Transitions to standby_z
0009h Accumulated Transitions to standby_y
all others Reserved
a The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.
b
If the Power Conditions Transitions log page is supported, at least one of these parameter codes shall
be supported.

570 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The Power Conditions Transitions log page has the format shown in table 400.

Table 400 — Power Condition Transitions log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (1Ah)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Power condition transitions log parameters
4
Power condition transitions log parameter (see
•• •
table 399) [first]

••
•

Power condition transitions log parameter (see

•• •
table 399) [last]
n

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 400 for the Power Conditions
Transitions log page.

The contents of each power condition transitions log parameter depends on the value in its PARAMETER CODE
field (see table 399).

7.3.13.2 Accumulated Transitions log parameter

The Accumulated Transitions log parameter has the format shown in table 401.

Table 401 — Accumulated Transitions log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (see table 399)
1 (LSB)
Parameter control byte – binary format list log parameter (see 7.3.2.2.2.5)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (04h)

4 (MSB)
•• • ACCUMULATED TRANSITIONS TO
7 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 399 for the
Accumulated Transitions log parameter.

Working Draft SCSI Primary Commands - 4 (SPC-4) 571

T10/BSR INCITS 513 Revision 37 17 May 2014

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a binary format list log parameter (see 7.3.2.2.2.5) for the Accumulated
Transitions log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 401 for the
Accumulated Transitions log parameter.

The ACCUMULATED TRANSITIONS TO field contains a saturating counter that is incremented by one at a time
defined by the contents of the PARAMETER CODE field as described in table 402. The time in the transition at
which the count is incremented is vendor specific.

Table 402 — Accumulated Transitions parameter codes and saturating counters

Saturating counter incremented while the device server transitions

Parameter code from any other power condition to this power condition
0001h active power condition (see 5.11.4)
0002h idle_a power condition (see 5.11.5)
0003h idle_b power condition (see 5.11.5)
0004h idle_c power condition (see 5.11.5)
0008h standby_z power condition (see 5.11.6)
0009h standby_y power condition (see 5.11.6)

All values in the ACCUMULATED TRANSITIONS TO field are accumulated from the time the SCSI target device is
manufactured.

7.3.14 Protocol Specific Port log page

7.3.14.1 Overview

Using the format shown in table 403, the Protocol Specific Port log page provides SCSI transport protocol
specific parameters that are associated with the SCSI target ports in the SCSI target device. This log page
may be implemented in any logical unit, including the TARGET LOG PAGES well-known logical unit (see 8.4).

Protocol Specific Port log pages do not identify the information being logged using the PARAMETER CODE field
in each log parameter. Instead, the SUBPAGE CODE field in the log page header (see table 403) serves as the
indicator of what logged information is present. The PARAMETER CODE field identifies the SCSI Target Port to
which the logged information applies.

572 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The Protocol Specific Port log page has the format shown in table 403.

Table 403 — Protocol Specific Port log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF PAGE CODE (18h)
1 SUBPAGE CODE (00h to FEh)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Protocol specific port log parameters
4
•• • Protocol specific port log parameter [first]

••
•

•• • Protocol specific port log parameter [last]

n

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 403 for the Protocol Specific Port
log page.

The contents of each protocol specific port log parameter is defined by the corresponding SCSI transport
protocol standard.

7.3.14.2 Generic protocol specific port log parameter

The generic format of a protocol specific port log parameter is shown in table 404.

Table 404 — Generic protocol specific port log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE
1 (LSB)
Parameter control byte – binary format list log parameter (see 7.3.2.2.2.5)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (n-3)

4 Reserved PROTOCOL IDENTIFIER

5
•• • SCSI transport protocol specific
n

For the Generic protocol specific port log parameter, the PARAMETER CODE field is described in 7.3.2.2.1, and
contains the relative target port identifier of the target port for which the parameter data applies.

Working Draft SCSI Primary Commands - 4 (SPC-4) 573

T10/BSR INCITS 513 Revision 37 17 May 2014

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a binary format list log parameter (see 7.3.2.2.2.5) for the Generic protocol
specific port log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1.

The PROTOCOL IDENTIFIER field contains one of the values shown in table 479 (see 7.6.1) to identify the SCSI
transport protocol standard that defines the SCSI transport protocol specific data in this log parameter.

The SCSI transport protocol specific data is defined by the corresponding SCSI transport protocol standard.

7.3.15 Read Error Counters log page

7.3.15.1 Overview

The command standard that applies to the device type defines the operations that result in events that are
reported in this log page.

Using the format shown in table 406, the Read Error Counters log page contains log parameters that report
bounded data counters for detected events (e.g., total bytes processed) identified by the parameter codes
listed in table 405.

Table 405 — Read Error Counters log page parameter codes

Parameter Resettable or
code Description Changeable a Reference Support
Errors corrected without substantial
0000h
delay c
0001h Errors corrected with possible delays c
0002h Total (e.g., rewrites or rereads) c
0003h Total errors corrected c Reset Only 7.3.15.2 At least one b
Total times correction algorithm
0004h
processed c
0005h Total bytes processed c
0006h Total uncorrected errors c
8000h to
Vendor specific
FFFFh
all others Reserved
a
The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.
b If the Read Error Counters log page is supported, at least one of the parameter codes listed in this table
shall be supported.
c
The conditions that result in this error counter being modified are vendor specific. This counter should
not be used to compare products because the products may define errors differently.

574 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The Read Error Counters log page has the format shown in table 406.

Table 406 — Read Error Counters log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (03h)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Read Error Counter log parameters
4
Read Error Counter log parameter (see 7.3.15.2)
•• •
[first]

••
•

Read Error Counter log parameter (see 7.3.15.2)

•• •
[last]
n

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 406 for the Read Error Counters
log page.

Each Read Error Counter log parameter contains the information described in 7.3.15.2.

7.3.15.2 Read Error Counter log parameter

The Read Error Counter log parameter has the format shown in table 407.

Table 407 — Read Error Counter log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (see table 405)
1 (LSB)
Parameter control byte – bounded data counter log parameter (see 7.3.2.2.2.2)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (n-3)

4 (MSB)
•• • READ ERROR COUNTER
n (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 405 for the Read Error
Counter log parameter.

Working Draft SCSI Primary Commands - 4 (SPC-4) 575

T10/BSR INCITS 513 Revision 37 17 May 2014

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a bounded data counter log parameter (see 7.3.2.2.2.2) for the Read Error
Counter log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1.

The READ ERROR COUNTER field contains the value for the counter described by the contents of the PARAMETER
CODE field.

7.3.16 Read Reverse Error Counters log page

7.3.16.1 Overview

The command standard that applies to the device type defines the operations that result in events that are
reported in this log page.

Using the format shown in table 409, the Read Reverse Error Counters log page contains log parameters that
report bounded data counters for detected events (e.g., total bytes processed) identified by the parameter
codes listed in table 408.

Table 408 — Read Reverse Error Counters log page parameter codes

Parameter Resettable or
code Description Changeable a Reference Support
Errors corrected without substantial
0000h
delay c
0001h Errors corrected with possible delays c
0002h Total (e.g., rewrites or rereads) c
0003h Total errors corrected c Reset Only 7.3.16.2 At least one b
Total times correction algorithm
0004h
processed c
0005h Total bytes processed c
0006h Total uncorrected errors c
8000h to
Vendor specific
FFFFh
all others Reserved
a
The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.
b If the Read Reverse Error Counters log page is supported, at least one of the parameter codes listed in
this table shall be supported.
c
The conditions that result in this error counter being modified are vendor specific. This counter should
not be used to compare products because the products may define errors differently.

576 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The Read Reverse Error Counters log page has the format shown in table 409.

Table 409 — Read Reverse Error Counters log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (04h)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Read reverse error counter log parameters
4
Read Reverse Error Counter log parameter (see
•• •
7.3.16.2) [first]

••
•

Read Reverse Error Counter log parameter (see

•• •
7.3.16.2) [last]
n

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 409 for the Read Reverse Error
Counters log page.

Each Read Reverse Error Counter log parameter contains the information described in 7.3.16.2.

7.3.16.2 Read Reverse Error Counter log parameter

The Read Reverse Error Counter log parameter has the format shown in table 410.

Table 410 — Read Reverse Error Counter log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (see table 408)
1 (LSB)
Parameter control byte – bounded data counter log parameter (see 7.3.2.2.2.2)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (n-3)

4 (MSB)
•• • READ REVERSE ERROR COUNTER
n (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 408 for the Read
Reverse Error Counter log parameter.

Working Draft SCSI Primary Commands - 4 (SPC-4) 577

T10/BSR INCITS 513 Revision 37 17 May 2014

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a bounded data counter log parameter (see 7.3.2.2.2.2) for the Read Reverse
Error Counter log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1.

The READ REVERSE ERROR COUNTER field contains the value for the counter described by the contents of the
PARAMETER CODE field.

7.3.17 Self-Test Results log page

7.3.17.1 Overview

Using the format shown in table 412, the Self-Test Results log page reports the results from the 20 most
recent self-tests (see 5.14). The parameter codes for the Self-Test Results log page are listed in table 411.

Table 411 — Self-Test Results log page parameter codes

Resettable or
Parameter code Description Changeable a Reference Support
0001h to 0014h Self-Test Results Reset Only 7.3.17.2 Mandatory
all others Reserved
a
The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.

The Self-Test Results log page has the format shown in table 412.

Table 412 — Self-Test Results log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (10h)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (0190h)
3 (LSB)
Self-test results log parameters
4
•• • Self-test results log parameter [first]
23
•
••

384
•• • Self-test results log parameter [twentieth]
403

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field shall be set as shown in table 412 for the
Self-Test Results log page.

578 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The PARAMETER CODE field indicates the time at which the self-test has been performed with respect to other
self-tests (i.e., 0001h indicates the most recent self-test, 0002h indicates the second most recent self-test,
etc.). If fewer than 20 self-tests have been performed, then:

a) unused self-test log parameters shall have parameter code values higher than those of any used
self-test log parameter; and
b) each unused self-test log parameter entry shall have the format shown in table 413.

Table 413 — Unused Self-Test Results log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (see table 411)
1 (LSB)
Parameter control byte – binary format list log parameter (see 7.3.2.2.2.5)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (10h)

4
•• • ZERO
19

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 411 for each Unused
Self-Test Results log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a binary format list log parameter (see 7.3.2.2.2.5) for each Unused Self-Test
Results log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 413 for each Unused
Self-Test Results log parameter.

The ZERO field is set to zero.

Working Draft SCSI Primary Commands - 4 (SPC-4) 579

T10/BSR INCITS 513 Revision 37 17 May 2014

7.3.17.2 Self-Test Results log parameters

Each Self-Test Results log parameter has the format shown in table 414.

Table 414 — Self-Test Results log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (see table 411)
1 (LSB)
Parameter control byte – binary format list log parameter (see 7.3.2.2.2.5)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (10h)

4 SELF-TEST CODE Reserved SELF-TEST RESULTS

5 SELF-TEST NUMBER

6 (MSB)
ACCUMULATED POWER ON HOURS
7 (LSB)
8 (MSB)
•• • ADDRESS OF FIRST FAILURE
15 (LSB)
16 Reserved SENSE KEY

17 ADDITIONAL SENSE CODE

18 ADDITIONAL SENSE CODE QUALIFIER

19 Vendor specific

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 411 for the Self-Test
Results log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a binary format list log parameter (see 7.3.2.2.2.5) for the Self-Test Results log
parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 414 for the Self-Test
Results log parameter.

The SELF - TEST CODE field indicates the value in the SELF - TEST CODE field of the SEND DIAGNOSTIC
command (see 6.42) that initiated this self-test.

580 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 415 defines the content of the SELF-TEST RESULTS field.

Table 415 — SELF-TEST RESULTS field

Code Description
0h The self-test completed without error.
1h The background self-test was aborted by the application client using a SEND DIAGNOSTIC
command (see 6.42) with the SELF-TEST CODE field set to 100b (i.e., abort background
self-test).
2h The self-test routine was aborted by an application client using a method other than a SEND
DIAGNOSTIC command with the SELF-TEST CODE field set to 100b (e.g., by a task manage-
ment function, or by issuing an exception command as defined in 5.14.4).
3h An unknown error occurred while the device server was processing the self-test and the device
server was unable to complete the self-test.
4h The self-test completed with a failure in a test segment, and the test segment that failed is not
known.
5h The first segment of the self-test failed.
6h The second segment of the self-test failed.
7h Another segment of the self-test failed and which test is indicated by the contents of the
SELF-TEST NUMBER field.

8h to Eh Reserved
Fh The self-test is in progress.

The SELF-TEST NUMBER field identifies the self-test that failed and consists of either:

a) the number of the segment that failed during the self-test; or

b) the number of the test that failed and the number of the segment in which the test was run, using a
vendor specific method for placing the two values in one field.

If the specific segment in which the failure occurred is not able to be identified, the SELF-TEST NUMBER field
shall contain 00h.

The ACCUMULATED POWER ON HOURS field indicates the elapsed hours of powered on operation since
manufacture at the time the self-test was completed. If the self-test is still in progress, the ACCUMULATED
POWER ON HOURS field shall be set to zero. If the number of hours is greater than FFFFh, the ACCUMULATED
POWER ON HOURS field shall be set to FFFFh.

The ADDRESS OF FIRST FAILURE field indicates information that locates the failure on the media. If the logical
unit implements logical blocks, the content of the ADDRESS OF FIRST FAILURE field is the first logical block
address where a self-test error occurred. This has no implication about the quality of any other logical block on
the logical unit (e.g., the testing during which the error occurred may not have been performed in a sequential
manner). This value shall not change (e.g., as the result of block reassignment). The content of the ADDRESS
OF FIRST FAILURE field shall be FFFF FFFF FFFF FFFFh if no errors occurred during the self-test or if the error
that occurred is not related to an identifiable media address.

The SENSE KEY field, ADDITIONAL SENSE CODE field, and ADDITIONAL SENSE CODE QUALIFIER field may contain a
hierarchy of additional information relating to error or exception conditions that occurred during the self-test
represented in the same format used by the sense data (see 4.5).

Working Draft SCSI Primary Commands - 4 (SPC-4) 581

T10/BSR INCITS 513 Revision 37 17 May 2014

7.3.18 Start-Stop Cycle Counter log page

7.3.18.1 Overview

Using the format shown in table 417, the Start-Stop Cycle Counter log page provides information about
manufacturing dates and cycle counts since date of manufacture using the parameter codes listed in table
416.

Table 416 — Start-Stop Cycle Counter log page parameter codes

Parameter Resettable or
code Description Changeable a Reference Support
0001h Date of Manufacture Never 7.3.18.2
0002h Accounting Date Always 7.3.18.3
0003h Specified Cycle Count Over Device
Never 7.3.18.4
Lifetime
At least one b
0004h Accumulated Start-Stop Cycles Never 7.3.18.5
0005h Specified Load-Unload Count Over
Never 7.3.18.6
Device Lifetime
0006h Accumulated Load-Unload Cycles Never 7.3.18.7
all others Reserved
a The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.
b
If the Start-Stop Cycle Counter log page is supported, at least one of the parameter codes listed in this
table shall be supported.

The Start-Stop Cycle Counter log page has the format shown in table 417.

Table 417 — Start-Stop Cycle Counter log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (0Eh)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Start stop cycle log parameters
4
Start stop cycle log parameter (see table 416)
•• •
[first]

•
••

Start stop cycle log parameter (see table 416)

•• •
[last]
n

582 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 417 for the Start-Stop Cycle
Counter log page.

7.3.18.2 Date of Manufacture log parameter

The Date of Manufacture log parameter has the format shown in table 418.

Table 418 — Date of Manufacture log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0001h)
1 (LSB)
Parameter control byte – ASCII format list log parameter (see 7.3.2.2.2.4)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (06h)

4 (MSB)
•• • YEAR OF MANUFACTURE
7 (LSB)
8 (MSB)
WEEK OF MANUFACTURE
9 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 418 for the Date of
Manufacture log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a ASCII format list log parameter (see 7.3.2.2.2.4) for the Date of Manufacture
log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 418 for the Date of
Manufacture log parameter.

The YEAR OF MANUFACTURE field indicates the year in which the SCSI target device was manufactured and
contains four numeric ASCII characters (e.g., 30h for zero and 39h for nine).

The WEEK OF MANUFACTURE field indicates the week of the year in which the SCSI target device was
manufactured and contains two numeric ASCII characters.

Working Draft SCSI Primary Commands - 4 (SPC-4) 583

T10/BSR INCITS 513 Revision 37 17 May 2014

7.3.18.3 Accounting Date log parameter

The Accounting Date log parameter has the format shown in table 419.

Table 419 — Accounting Date log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0002h)
1 (LSB)
Parameter control byte – ASCII format list log parameter (see 7.3.2.2.2.4)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (06h)

4 (MSB)
•• • ACCOUNTING DATE YEAR
7 (LSB)
8 (MSB)
ACCOUNTING DATE WEEK
9 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 419 for the Accounting
Date log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a ASCII format list log parameter (see 7.3.2.2.2.4) for the Accounting Date log
parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 419 for the
Accounting Date log parameter.

The ACCOUNTING DATE YEAR field indicates the year in which the SCSI target device was placed in service and
contains four numeric ASCII characters (e.g., 30h for zero and 39h for nine).

The ACCOUNTING DATE WEEK field indicates the week of the year in which the SCSI target device was placed in
service and contains two numeric ASCII characters.

A LOG SELECT command may be used to change the value of the ACCOUNTING DATE YEAR field and
ACCOUNTING DATE WEEK field. If the Accounting Date log parameter is not yet set, then the value placed:

a) in the ACCOUNTING DATE YEAR field shall be four ASCII space characters (i.e., 20h); and
b) in the ACCOUNTING DATE WEEK field shall be two ASCII space characters (i.e., 20h).

The ACCOUNTING DATE YEAR field and ACCOUNTING DATE WEEK field shall not be checked for validity by the
device server.

584 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.3.18.4 Specified Cycle Count Over Device Lifetime log parameter

The Specified Cycle Count Over Device Lifetime log parameter has the format shown in table 420.

Table 420 — Specified Cycle Count Over Device Lifetime log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0003h)
1 (LSB)
Parameter control byte – binary format list log parameter (see 7.3.2.2.2.5)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (04h)

4 (MSB)
•• • SPECIFIED CYCLE COUNT OVER DEVICE LIFETIME
7 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 420 for the Specified
Cycle Count Over Device Lifetime log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a binary format list log parameter (see 7.3.2.2.2.5) for the Specified Cycle Count
Over Device Lifetime log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 420 for the Specified
Cycle Count Over Device Lifetime log parameter.

The contents of the SPECIFIED CYCLE COUNT OVER DEVICE LIFETIME field indicate the number of stop-start cycles
that may be performed over the lifetime of the SCSI target device without degrading the SCSI target device's
operation or reliability outside the limits specified by the manufacturer of the SCSI target device.

7.3.18.5 Accumulated Start-Stop Cycles log parameter

The Accumulated Start-Stop Cycles log parameter has the format shown in table 421.

Table 421 — Accumulated Start-Stop Cycles log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0004h)
1 (LSB)
Parameter control byte – binary format list log parameter (see 7.3.2.2.2.5)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (04h)

4 (MSB)
•• • ACCUMULATED START-STOP CYCLES
7 (LSB)

Working Draft SCSI Primary Commands - 4 (SPC-4) 585

T10/BSR INCITS 513 Revision 37 17 May 2014

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 421 for the
Accumulated Start-Stop Cycles log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a binary format list log parameter (see 7.3.2.2.2.5) for the Accumulated Start-Stop
Cycles log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 421 for the
Accumulated Start-Stop Cycles log parameter.

The contents of the ACCUMULATED START-STOP CYCLES field indicate the number of stop-start cycles the SCSI
target device has detected since its date of manufacture. This saturating counter is incremented by one for
each complete cycle. The time in the cycle at which the counter is incremented is vendor specific.

For rotating magnetic storage devices (see SBC-3), a single start-stop cycle is defined as an operational cycle
that:

a) begins with the disk spindle at rest;

b) continues while the disk accelerates to its normal operational rotational rate;
c) continues during the entire period the disk is rotating;
d) continues as the disk decelerates toward a resting state; and
e) ends when the disk is no longer rotating.

For devices without a spindle or with multiple spindles, the definition of a single start-stop cycle is vendor
specific.

7.3.18.6 Specified Load-Unload Count Over Device Lifetime log parameter

The Specified Load-Unload Count Over Device Lifetime log parameter has the format shown in table 422.

Table 422 — Specified Load-Unload Count Over Device Lifetime log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0005h)
1 (LSB)
Parameter control byte – binary format list log parameter (see 7.3.2.2.2.5)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (04h)

4 (MSB)
SPECIFIED LOAD-UNLOAD COUNT OVER DEVICE
•• •
LIFETIME
7 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 422 for the Specified
Load-Unload Count Over Device Lifetime log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a binary format list log parameter (see 7.3.2.2.2.5) for the Specified Load-Unload
Count Over Device Lifetime log parameter.

586 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 422 for the Specified
Load-Unload Count Over Device Lifetime log parameter.

The contents of the SPECIFIED LOAD - UNLOAD COUNT OVER DEVICE LIFETIME field indicate the number of
load-unload cycles that may be performed over the lifetime of the SCSI target device without degrading the
SCSI target device's operation or reliability outside the limits specified by the manufacturer of the SCSI target
device.

7.3.18.7 Accumulated Load-Unload Cycles log parameter

The Accumulated Load-Unload Cycles log parameter has the format shown in table 423.

Table 423 — Accumulated Load-Unload Cycles log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0006h)
1 (LSB)
Parameter control byte – binary format list log parameter (see 7.3.2.2.2.5)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (04h)

4 (MSB)
•• • ACCUMULATED LOAD-UNLOAD CYCLES
7 (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 423 for the
Accumulated Load-Unload Cycles log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a binary format list log parameter (see 7.3.2.2.2.5) for the Accumulated
Load-Unload Cycles log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 423 for the
Accumulated Load-Unload Cycles log parameter.

The contents of the ACCUMULATED LOAD-UNLOAD CYCLES field indicate the number of load-unload cycles the
SCSI target device has detected since its date of manufacture. This saturating counter is incremented by one
for each complete cycle. The time in the cycle at which the counter is incremented is vendor specific.

For rotating magnetic storage devices (see SBC-3), a single load-unload cycle is defined as an operational
cycle that:

a) begins with the heads unloaded from the medium;

b) continues while the heads are loaded onto the spinning medium; and
c) ends when the heads are unloaded from the medium.

The Accumulated Load-Unload Cycles log parameter is not applicable to rotating magnetic storage devices
without unloadable heads.

Working Draft SCSI Primary Commands - 4 (SPC-4) 587

T10/BSR INCITS 513 Revision 37 17 May 2014

7.3.19 Supported Log Pages log page

For the LOG SENSE command, the Supported Log Pages log page (see table 424) returns the list of log
pages implemented by the logical unit. Logical units that implement the LOG SENSE command shall
implement this log page. This log page is not defined for the LOG SELECT command.

Table 424 — Supported Log Pages log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS (0b) SPF (0b) PAGE CODE (00h)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Supported pages list
4 Supported page descriptor (see table 425) [first]
••
•
n Supported page descriptor (see table 425) [last]

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The DS
bit, SPF bit, SUBPAGE CODE field shall be set as shown in table 424 for the Supported Log Pages log page.

The supported page descriptors shall contain a list of all log page codes (see table 425) with a subpage code
of zero implemented by the logical unit in ascending order beginning with page code 00h.

Table 425 — Supported page descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 Reserved PAGE CODE

The PAGE CODE field indicates the number of a supported log page.

588 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.3.20 Supported Log Pages and Subpages log page

For the LOG SENSE command, the Supported Log Pages and Subpages log page (see table 426) returns the
list of log pages and subpages implemented by the logical unit. If log subpages are supported, this page shall
be supported. This log page is not defined for the LOG SELECT command.

Table 426 — Supported Log Pages and Subpages log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS (0b) SPF (1b) PAGE CODE (00h)
1 SUBPAGE CODE (FFh)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Supported page/subpage descriptors
4 Supported page/subpage descriptor (see table
5 427) [first]
•
••

n-1 Supported page/subpage descriptor (see table

n 427) [last]

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The DS
bit, SPF bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 426 for the Supported Log
Pages and Subpages log page.

The supported page/subpage descriptors (see table 427) shall be in ascending order sorted by page code
then subpage code.

Table 427 — Supported page/subpage descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 Reserved PAGE CODE

1 SUBPAGE CODE

The PAGE CODE field indicates the number of a supported log page.

The SUBPAGE CODE field indicates the supported subpage number of a supported log page.

Working Draft SCSI Primary Commands - 4 (SPC-4) 589

T10/BSR INCITS 513 Revision 37 17 May 2014

7.3.21 Supported Subpages log page

For the LOG SENSE command, the Supported Subpages log page (see table 428) returns the list of all
subpage codes (i.e., 00h to FFh) that are implemented by the logical unit for a specified page code. If log
subpages are supported, this page shall be supported. This log page is not defined for the LOG SELECT
command.

Table 428 — Supported Subpages log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS (0b) SPF (1b) PAGE CODE

1 SUBPAGE CODE (FFh)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Supported subpage descriptors
4 Supported subpage descriptor (see table 429)
5 [first]
•
••

n-1 Supported subpage descriptor (see table 429)

n [last]

The DS bit, SPF bit, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The DS bit, SPF bit,
SUBPAGE CODE field shall be set as shown in table 428 for the Supported Subpages log page.

The PAGE CODE field (see 7.3.2) indicates the log page for which log page and subpage codes are being
returned.

The supported subpage descriptors (see table 429) shall be in ascending order sorted by page code then
subpage code, and shall include a descriptor with subpage code 00h for any implemented log page in which
the SPF bit is set to zero.

Table 429 — Supported subpage descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 Reserved PAGE CODE

1 SUBPAGE CODE

The PAGE CODE field indicates the number of a supported log page.

The page code is the same in the page header (see table 428) and in each supported subpage descriptor (see
table 429).

The SUBPAGE CODE field indicates the supported subpage number of a supported log page.

590 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.3.22 Temperature log page

7.3.22.1 Overview

Using the format shown in table 431, the Temperature log page provides information about the current
operating temperature of the SCSI Target Device using the parameter codes listed in table 430.

Table 430 — Temperature log page parameter codes

Parameter Resettable or
code Description Changeable a Reference Support
0000h Temperature Never 7.3.22.2 Mandatory
0001h Reference Temperature Never 7.3.22.3 Optional
all others Reserved
a
The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.

The Temperature log page has the format shown in table 431.

Table 431 — Temperature log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (0Dh)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Temperature log parameters
4
•• • Temperature log parameter (see table 430) [first]

••
•

•• • Temperature log parameter (see table 430) [last]

n

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 431 for the Temperature log page.

The contents of each temperature log parameter depends on the value in its PARAMETER CODE field (see table
430).

Working Draft SCSI Primary Commands - 4 (SPC-4) 591

T10/BSR INCITS 513 Revision 37 17 May 2014

7.3.22.2 Temperature log parameter

The Temperature log parameter has the format shown in table 432.

Table 432 — Temperature log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0000h)
1 (LSB)
Parameter control byte – binary format list log parameter (see 7.3.2.2.2.5)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (02h)

4 Reserved
5 TEMPERATURE

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 432 for the
Temperature log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a binary format list log parameter (see 7.3.2.2.2.5) for the Temperature log
parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 432 for the
Temperature log parameter.

The TEMPERATURE field indicates the temperature of the SCSI target device in degrees Celsius at the time the
LOG SENSE command is performed. Temperatures equal to or less than zero degrees Celsius shall cause
the TEMPERATURE field to be set to zero. If the device server is unable to detect a valid temperature because of
a sensor failure or other condition, then the TEMPERATURE field shall be set to FFh. The temperature should be
reported with an accuracy of plus or minus three Celsius degrees while the SCSI target device is operating at
a steady state within its environmental limits.

7.3.22.3 Reference Temperature log parameter

The Reference Temperature log parameter has the format shown in table 433.

Table 433 — Reference Temperature log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (0001h)
1 (LSB)
Parameter control byte – binary format list log parameter (see 7.3.2.2.2.5)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (02h)

4 Reserved
5 REFERENCE TEMPERATURE

592 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 433 for the Reference
Temperature log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a binary format list log parameter (see 7.3.2.2.2.5) for the Reference
Temperature log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1, and shall be set as shown in table 433 for the
Reference Temperature log parameter.

The REFERENCE TEMPERATURE field indicates the maximum reported sensor temperature in degrees Celsius at
which the SCSI target device is capable of operating continuously without degrading the SCSI target device's
operation or reliability beyond manufacturer accepted limits. If the device server is unable to return a
reference temperature and the optional Reference Temperature log parameter is included in the Temperature
log page, then REFERENCE TEMPERATURE field is set to FFh.

The reference temperature may change for vendor specific reasons.

7.3.23 Verify Error Counters log page

7.3.23.1 Overview

The command standard that applies to the device type defines the operations that result in events that are
reported in this log page.

Using the format shown in table 435, the Verify Error Counters log page contains log parameters that report
bounded data counters for detected events (e.g., total bytes processed) identified by the parameter codes

Working Draft SCSI Primary Commands - 4 (SPC-4) 593

T10/BSR INCITS 513 Revision 37 17 May 2014

listed in table 434.

Table 434 — Verify Error Counters log page parameter codes

Parameter Resettable or
code Description Changeable a Reference Support
Errors corrected without substantial
0000h
delay c
0001h Errors corrected with possible delays c
0002h Total (e.g., rewrites or rereads) c
0003h Total errors corrected c Reset Only 7.3.23.2 At least one b
Total times correction algorithm
0004h
processed c
0005h Total bytes processed c
0006h Total uncorrected errors c
8000h to
Vendor specific
FFFFh
all others Reserved
a
The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.
b If the Verify Error Counters log page is supported, at least one of the parameter codes listed in this table
shall be supported.
c
The conditions that result in this error counter being modified are vendor specific. This counter should
not be used to compare products because the products may define errors differently.

The Verify Error Counters log page has the format shown in table 435.

Table 435 — Verify Error Counters log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (05h)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Verify error counter log parameters
4
Verify Error Counter log parameter (see 7.3.23.2)
•• •
[first]

••
•

Verify Error Counter log parameter (see 7.3.23.2)

•• •
[last]
n

594 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 435 for the Verify Error Counters
log page.

Each Verify Error Counter log parameter contains the information described in 7.3.23.2.

7.3.23.2 Verify Error Counter log parameter

The Verify Error Counter log parameter has the format shown in table 436.

Table 436 — Verify Error Counter log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (see table 434)
1 (LSB)
Parameter control byte – bounded data counter log parameter (see 7.3.2.2.2.2)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (n-3)

4 (MSB)
•• • VERIFY ERROR COUNTER
n (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 434 for the Verify Error
Counter log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a bounded data counter log parameter (see 7.3.2.2.2.2) for the Verify Error
Counter log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1.

The VERIFY ERROR COUNTER field contains the value for the counter described by the contents of the
PARAMETER CODE field.

7.3.24 Write Error Counters log page

7.3.24.1 Overview

The command standard that applies to the device type defines the operations that result in events that are
reported in this log page.

Using the format shown in table 438, the Write Error Counters log page contains log parameters that report
bounded data counters for detected events (e.g., total bytes processed) identified by the parameter codes

Working Draft SCSI Primary Commands - 4 (SPC-4) 595

T10/BSR INCITS 513 Revision 37 17 May 2014

listed in table 437.

Table 437 — Write Error Counters log page parameter codes

Parameter Resettable or
code Description Changeable a Reference Support
Errors corrected without substantial
0000h
delay c
0001h Errors corrected with possible delays c
0002h Total (e.g., rewrites or rereads) c
0003h Total errors corrected c Reset Only 7.3.24.2 At least one b
Total times correction algorithm
0004h
processed c
0005h Total bytes processed c
0006h Total uncorrected errors c
8000h to
Vendor specific
FFFFh
all others Reserved
a
The keywords in this column – Always, Reset Only, and Never – are defined in 7.3.3.
b If the Write Error Counters log page is supported, at least one of the parameter codes listed in this table
shall be supported.
c
The conditions that result in this error counter being modified are vendor specific. This counter should
not be used to compare products because the products may define errors differently.

The Write Error Counters log page has the format shown in table 438.

Table 438 — Write Error Counters log page

Bit
7 6 5 4 3 2 1 0
Byte
0 DS SPF (0b) PAGE CODE (02h)
1 SUBPAGE CODE (00h)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Write error counter log parameters
4
Write Error Counter log parameter (see 7.3.24.2)
•• •
[first]

••
•

Write Error Counter log parameter (see 7.3.24.2)

•• •
[last]
n

596 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The DS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.3.2. The SPF
bit, PAGE CODE field, and SUBPAGE CODE field shall be set as shown in table 438 for the Write Error Counters
log page.

Each Write Error Counter log parameter contains the information described in 7.3.24.2.

7.3.24.2 Write Error Counter log parameter

The Write Error Counter log parameter has the format shown in table 439.

Table 439 — Write Error Counter log parameter

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PARAMETER CODE (see table 437)
1 (LSB)
Parameter control byte – bounded data counter log parameter (see 7.3.2.2.2.2)
2
DU Obsolete TSD ETC TMC FORMAT AND LINKING

3 PARAMETER LENGTH (n-3)

4 (MSB)
•• • WRITE ERROR COUNTER
n (LSB)

The PARAMETER CODE field is described in 7.3.2.2.1, and shall be set as shown in table 437 for the Write Error
Counter log parameter.

The DU bit, TSD bit, ETC bit, TMC field, and FORMAT AND LINKING field are described in 7.3.2.2.2.1. These fields
shall be set as described for a bounded data counter log parameter (see 7.3.2.2.2.2) for the Write Error
Counter log parameter.

The PARAMETER LENGTH field is described in 7.3.2.2.1.

The WRITE ERROR COUNTER field contains the value for the counter described by the contents of the
PARAMETER CODEfield.

Working Draft SCSI Primary Commands - 4 (SPC-4) 597

T10/BSR INCITS 513 Revision 37 17 May 2014

7.4 Medium auxiliary memory attributes

7.4.1 Attribute format

Each medium auxiliary memory attribute shall be communicated between the application client and device
server in the format shown in table 440. This format shall be used in the parameter data for the WRITE
ATTRIBUTE command (see 6.48) and the READ ATTRIBUTE command (see 6.17). The attribute format in
this standard implies nothing about the physical representation of an attribute in the medium auxiliary memory.

Table 440 — MAM ATTRIBUTE format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
ATTRIBUTE IDENTIFIER
1 (LSB)
2 READ ONLY Reserved FORMAT

3 (MSB)
ATTRIBUTE LENGTH (n-4)
4 (LSB)
5
•• • ATTRIBUTE VALUE
n

The ATTRIBUTE IDENTIFIER field contains a code value identifying the attribute (see 7.4.2).

The READ ONLY bit indicates whether the attribute is in the read only state (see 5.7). If the READ ONLY bit is set
to one, the attribute is in the read only state. If the READ ONLY bit is set to zero, the attribute is not in the read
only state.

The FORMAT field (see table 441) specifies the format of the data in the ATTRIBUTE VALUE field.

Table 441 — MAM attribute FORMAT field

Format Name Description

00b BINARY The ATTRIBUTE VALUE field contains binary data.
01b ASCII The ATTRIBUTE VALUE field contains left-aligned ASCII data (see 4.3.1).
10b TEXT The attribute contains textual data. The character set is as described in
the TEXT LOCALIZATION IDENTIFIER attribute (see 7.4.2.4.6).
11b Reserved

The ATTRIBUTE LENGTH field specifies the length in bytes of the ATTRIBUTE VALUE field.

The ATTRIBUTE VALUE field contains the:

a) current value of the attribute for the READ ATTRIBUTE command (see 6.17); or
b) intended value of the attribute for the WRITE ATTRIBUTE command (see 6.48).

598 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.4.2 Attribute identifier values

7.4.2.1 Attribute identifier values overview

The values in the ATTRIBUTE IDENTIFIER field (see 7.4.1) are assigned according to the attribute type (see 5.7)
and whether the attribute is standard or vendor specific (see table 442).

Table 442 — MAM attribute identifier range assignments

Attribute Identifiers Attribute Type Standardized Reference

0000h to 03FFh Device Yes 7.4.2.2
0400h to 07FFh Medium Yes 7.4.2.3
0800h to 0BFFh Host Yes 7.4.2.4
0C00h to 0FFFh Device Vendor specific
1000h to 13FFh Medium Vendor specific
1400h to 17FFh Host Vendor specific
1800h to FFFFh Reserved

Device servers may process a WRITE ATTRIBUTE command containing standardized host type attribute
identifier values (i.e., 0800h-0BFFh) or vendor specific host type attribute identifier values (i.e., 1400h-17FFh).
Standardized host type attribute identifier values may be verified as described in 7.4.2.4.

7.4.2.2 Device type attributes

Device type attributes (see table 443) shall be maintained and updated by the device server while the medium
and associated medium auxiliary memory are present. All supported device type attributes shall have a status
of read only or unavailable (see 5.7).

Table 443 — Device type attributes (part 1 of 2)

Attribute
Attribute Length
Identifier Name (in bytes) Format a Reference
0000h REMAINING CAPACITY IN PARTITION 8 BINARY 7.4.2.2.1
0001h MAXIMUM CAPACITY IN PARTITION 8 BINARY 7.4.2.2.1
0002h Restricted (see SSC-4)
0003h LOAD COUNT 8 BINARY 7.4.2.2.2
0004h MAM SPACE REMAINING 8 BINARY 7.4.2.2.3
0005h to Restricted (see SSC-4)
0006h
0007h INITIALIZATION COUNT 2 BINARY 7.4.2.2.4
0008h VOLUME IDENTIFIER 32 ASCII 7.4.2.2.5
0009h Restricted (see SSC-4)
000Ah to Reserved
0209h
a See table 441 in 7.4.1.

Working Draft SCSI Primary Commands - 4 (SPC-4) 599

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 443 — Device type attributes (part 2 of 2)

Attribute
Attribute Length
Identifier Name (in bytes) Format a Reference
020Ah DEVICE VENDOR/SERIAL NUMBER AT LAST LOAD 40 ASCII 7.4.2.2.6
020Bh DEVICE VENDOR/SERIAL NUMBER AT LOAD-1 40 ASCII 7.4.2.2.6
020Ch DEVICE VENDOR/SERIAL NUMBER AT LOAD-2 40 ASCII 7.4.2.2.6
020Dh DEVICE VENDOR/SERIAL NUMBER AT LOAD-3 40 ASCII 7.4.2.2.6
020Eh to Reserved
021Fh
0220h TOTAL MEBIBYTES WRITTEN IN MEDIUM LIFE 8 BINARY 7.4.2.2.7
0221h TOTAL MEBIBYTES READ IN MEDIUM LIFE 8 BINARY 7.4.2.2.7
0222h TOTAL MEBIBYTES WRITTEN IN CURRENT/LAST 8 BINARY 7.4.2.2.8
LOAD
0223h TOTAL MEBIBYTES READ IN CURRENT/LAST 8 BINARY 7.4.2.2.8
LOAD
0224h LOGICAL POSITION OF FIRST ENCRYPTED BLOCK 8 BINARY 7.4.2.2.9
LOGICAL POSITION OF FIRST UNENCRYPTED
0225h 8 BINARY 7.4.2.2.10
BLOCK AFTER THE FIRST ENCRYPTED BLOCK
0226h to Reserved
033Fh
0340h MEDIUM USAGE HISTORY 90 BINARY 7.4.2.2.11
0341h PARTITION USAGE HISTORY 60 BINARY 7.4.2.2.12
0342h to Reserved
03FFh
a See table 441 in 7.4.1.

7.4.2.2.1 REMAINING CAPACITY IN PARTITION and MAXIMUM CAPACITY IN PARTITION

These attributes are native capacities (i.e., assuming no data compression for the specified medium partition)
expressed in units of mebibytes.

7.4.2.2.2 LOAD COUNT

This attribute is a saturating counter that indicates how many times this medium has been fully loaded. This
attribute should not be reset to zero by any action of the device server.

7.4.2.2.3 MAM SPACE REMAINING

This attribute indicates the space currently available in the medium auxiliary memory. The total medium
auxiliary memory capacity is reported in the MAM CAPACITY attribute (see 7.4.2.3.4).

NOTE 38 - It is not always possible to utilize all of the available space in a given medium auxiliary memory
implementation. Depending on the internal organization of the memory and the software that controls it,
fragmentation issues have the potential to result in conditions where cause certain attribute sizes to not be
fully accommodated as the medium auxiliary memory nears its maximum capacity.

600 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.4.2.2.4 INITIALIZATION COUNT

This attribute is a saturating counter that indicates the number of times that a device server has logically
formatted the medium. This value is cumulative over the life of the medium and shall not be reset to zero.

7.4.2.2.5 VOLUME IDENTIFIER

This attribute indicates the current volume identifier (see SMC-3) of the medium. If the device server supports
this attribute but does not have access to the volume identifier, the device server shall report this attribute with
an attribute length value of zero.

7.4.2.2.6 DEVICE VENDOR/SERIAL NUMBER AT LAST LOAD, DEVICE VENDOR/SERIAL

NUMBER AT LOAD –1, DEVICE VENDOR/SERIAL NUMBER AT LOAD –2 and DEVICE VENDOR/SERIAL
NUMBER AT LOAD –3

These attributes give a history of the last four device servers in which the medium has been loaded. The
format of these attributes is shown in table 444.

Table 444 — DEVICE VENDOR/SERIAL NUMBER attribute format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • T10 VENDOR IDENTIFICATION
7 (LSB)
8 (MSB)
•• • PRODUCT SERIAL NUMBER
39 (LSB)

The T10 VENDOR IDENTIFICATION field shall contain the T10 vendor identification bytes that the device server
loading the medium returns in the Standard INQUIRY data (see 6.6.2) parameter data for an INQUIRY
command (see 6.6).

The PRODUCT SERIAL NUMBER field contains ASCII data (see 4.3.1) that is a manufacturer assigned serial
number. If the product serial number is not available, the PRODUCT SERIAL NUMBER field shall contain ASCII
spaces (20h).

7.4.2.2.7 TOTAL MEBIBYTES WRITTEN IN MEDIUM LIFE and TOTAL MEBIBYTES READ IN
MEDIUM LIFE

These attributes indicate the total number of data mebibytes that are transferred to or from the medium, after
any data compression has been applied, over the entire medium life. These values are cumulative and shall
not be reset to zero.

7.4.2.2.8 TOTAL MEBIBYTES WRITTEN IN CURRENT/LAST LOAD and TOTAL MEBIBYTES

READ IN CURRENT/LAST LOAD

These attributes indicate the total number of data mebibytes that are transferred to or from the medium, after
any data compression has been applied, during:

a) the current load if the medium is currently loaded; or

b) the last load if the medium is currently unloaded.

Working Draft SCSI Primary Commands - 4 (SPC-4) 601

T10/BSR INCITS 513 Revision 37 17 May 2014

The device server should reset these attributes to zero when the medium is loaded.

7.4.2.2.9 LOGICAL POSITION OF FIRST ENCRYPTED BLOCK

This attribute indicates the first encrypted logical block, if any, in the partition specified by the PARTITION
NUMBER field in the CDB, and shall be set to:

a) FFFF FFFF FFFF FFFFh if there is no encrypted logical block in the partition specified by the
PARTITION NUMBER field in the CDB;
b) FFFF FFFF FFFF FFFEh if it is unknown whether there are any encrypted logical blocks in the
partition specified by the PARTITION NUMBER field in the CDB; or
c) the address of the first logical block in the partition specified by the PARTITION NUMBER field in the CDB
that contains encrypted data.

7.4.2.2.10 LOGICAL POSITION OF FIRST UNENCRYPTED BLOCK AFTER THE FIRST

ENCRYPTED BLOCK

If this attribute is supported, the LOGICAL POSITION OF FIRST ENCRYPTED BLOCK (see 7.4.2.2.9)
attribute shall be supported. This attribute indicates the first unencrypted logical block block, if any, in the
partition specified by the PARTITION NUMBER field in the CDB after one or more encrypted logical blocks, and
shall be set to:

a) FFFF FFFF FFFF FFFFh if there is:

A) no encrypted logical block in the partition specified by the PARTITION NUMBER field in the CDB (i.e.,
if the value for the LOGICAL POSITION OF FIRST ENCRYPTED BLOCK attribute (see 7.4.2.2.9)
is set to FFFF FFFF FFFF FFFFh); or
B) no unencrypted logical block in the partition specified by the PARTITION NUMBER field in the CDB
after the address specified in the LOGICAL POSITION OF FIRST ENCRYPTED BLOCK
attribute;
b) FFFF FFFF FFFF FFFEh if it is unknown whether:
A) there are any encrypted logical blocks in the partition specified by the PARTITION NUMBER field in
the CDB (i.e., the LOGICAL POSITION OF FIRST ENCRYPTED BLOCK attribute (see 7.4.2.2.9)
is set to FFFF FFFF FFFF FFFEh); or
B) any logical block in the partition specified by the PARTITION NUMBER field in the CDB after the first
encrypted logical block contains unencrypted data;
or
c) the address of the first logical block in the partition specified by the PARTITION NUMBER field in the CDB
that contains unencrypted data and is located after the address specified in the LOGICAL POSITION
OF FIRST ENCRYPTED BLOCK attribute.

602 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.4.2.2.11 MEDIUM USAGE HISTORY

This attribute provides saturating counters (see table 445) for the entire medium. The value in each field is the
sum for all partitions. If a field is not used, it should be set to zero.

Table 445 — MEDIUM USAGE HISTORY attribute format (part 1 of 2)

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • CURRENT AMOUNT OF DATA WRITTEN
5 (LSB)
6 (MSB)
•• • CURRENT WRITE RETRIES COUNT
11 (LSB)
12 (MSB)
•• • CURRENT AMOUNT OF DATA READ
17 (LSB)
18 (MSB)
•• • CURRENT READ RETRIES COUNT
23 (LSB)
24 (MSB)
•• • PREVIOUS AMOUNT OF DATA WRITTEN
29 (LSB)
30 (MSB)
•• • PREVIOUS WRITE RETRIES COUNT
35 (LSB)
36 (MSB)
•• • PREVIOUS AMOUNT OF DATA READ
41 (LSB)
42 (MSB)
•• • PREVIOUS READ RETRIES COUNT
47 (LSB)
48 (MSB)
•• • TOTAL AMOUNT OF DATA WRITTEN
53 (LSB)
54 (MSB)
•• • TOTAL WRITE RETRIES COUNT
59 (LSB)
60 (MSB)
•• • TOTAL AMOUNT OF DATA READ
65 (LSB)
66 (MSB)
•• • TOTAL READ RETRIES COUNT
71 (LSB)

Working Draft SCSI Primary Commands - 4 (SPC-4) 603

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 445 — MEDIUM USAGE HISTORY attribute format (part 2 of 2)

Bit
7 6 5 4 3 2 1 0
Byte
72 (MSB)
•• • LOAD COUNT
77 (LSB)
78 (MSB)
•• • TOTAL CHANGE PARTITION COUNT
83 (LSB)
84 (MSB)
•• • TOTAL PARTITION INITIALIZE COUNT
89 (LSB)

The CURRENT AMOUNT OF DATA WRITTEN field indicates the amount of data written to the medium during this
load of the medium. This value is expressed in mebibytes (see 3.5.2).

The CURRENT WRITE RETRIES COUNT field indicates the total number of times a write retry occurred during this
load of the medium.1)

The CURRENT AMOUNT OF DATA READ field indicates the amount of data read from the medium during this load
of the medium. This value is expressed in mebibytes (see 3.5.2).

The CURRENT READ RETRIES COUNT field indicates the number of times a read retry occurred during this load of
the medium.1)

The PREVIOUS AMOUNT OF DATA WRITTEN field indicates the amount of data written to the medium during the
previous load of the medium. This value is expressed in mebibytes (see 3.5.2).

The PREVIOUS WRITE RETRIES COUNT field indicates the total number of times a write retry occurred during the
previous load of the medium.1)

The PREVIOUS AMOUNT OF DATA READ field indicates the amount of data read from the medium during the
previous load of the medium. This value is expressed in mebibytes (see 3.5.2).

The PREVIOUS READ RETRIES COUNT field indicates the number of times a read retry occurred during the
previous load of the medium.1)

The TOTAL AMOUNT OF DATA WRITTEN field indicates the amount of data written to the medium since the last
time the medium was formatted. This value is expressed in mebibytes (see 3.5.2).

The TOTAL WRITE RETRIES COUNT field indicates the total number of times a write retry occurred since the last
time the medium was formatted.1)

The TOTAL AMOUNT OF DATA READ field indicates the amount of data read from the medium since the last time
the medium was formatted. This value is expressed in mebibytes (see 3.5.2).

1) The definition of a retry as counted by this attribute field is outside the scope of this standard. This
count should not be used to compare products because the products may define errors differently.

604 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The TOTAL READ RETRIES COUNT field indicates the number of times a read retry occurred since the last time
the medium was formatted.1)

The LOAD COUNT field indicates the number of loads since the last time the medium was formatted. This count
accumulates over the life of the medium but it is reset to zero after a medium format.

The TOTAL CHANGE PARTITION COUNT field indicates the number of times that switches between partitions have
been performed on the medium. This count accumulates over the life of the medium but it is reset to zero after
a medium format.

The TOTAL PARTITION INITIALIZE COUNT field indicates number of times that any of the partitions on the medium
have been erased. This count accumulates over the life of the medium but it is reset to zero after a medium
format.

7.4.2.2.12 PARTITION USAGE HISTORY

This attribute provides saturating counters (see table 446) for the partition specified by the PARTITION NUMBER
field in the CDB. If a field is not used, it should be set to zero.

Table 446 — PARTITION USAGE HISTORY attribute format (part 1 of 2)

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • CURRENT AMOUNT OF DATA WRITTEN
3 (LSB)
4 (MSB)
•• • CURRENT WRITE RETRIES COUNT
7 (LSB)
8 (MSB)
•• • CURRENT AMOUNT OF DATA READ
11 (LSB)
12 (MSB)
•• • CURRENT READ RETRIES COUNT
15 (LSB)
16 (MSB)
•• • PREVIOUS AMOUNT OF DATA WRITTEN
19 (LSB)
20 (MSB)
•• • PREVIOUS WRITE RETRIES COUNT
23 (LSB)
24 (MSB)
•• • PREVIOUS AMOUNT OF DATA READ
27 (LSB)
28 (MSB)
•• • PREVIOUS READ RETRIES COUNT
31 (LSB)

Working Draft SCSI Primary Commands - 4 (SPC-4) 605

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 446 — PARTITION USAGE HISTORY attribute format (part 2 of 2)

Bit
7 6 5 4 3 2 1 0
Byte
32 (MSB)
•• • TOTAL AMOUNT OF DATA WRITTEN
35 (LSB)
36 (MSB)
•• • TOTAL WRITE RETRIES COUNT
39 (LSB)
40 (MSB)
•• • TOTAL AMOUNT OF DATA READ
43 (LSB)
44 (MSB)
•• • TOTAL READ RETRIES COUNT
47 (LSB)
48 (MSB)
•• • LOAD COUNT
51 (LSB)
52 (MSB)
•• • CHANGE PARTITION COUNT
55 (LSB)
56 (MSB)
•• • PARTITION INITIALIZE COUNT
59 (LSB)

The CURRENT AMOUNT OF DATA WRITTEN field indicates the amount of data written to the medium in the partition
specified by the PARTITION NUMBER field in the CDB during this load of the medium. This value is expressed in
mebibytes (see 3.5.2).

The CURRENT WRITE RETRIES COUNT field indicates the total number of times a write retry occurred in the
partition specified by the PARTITION NUMBER field in the CDB during this load of the medium.1)

The CURRENT AMOUNT OF DATA READ field indicates the amount of data read from the medium in the partition
specified by the PARTITION NUMBER field in the CDB during this load of the medium. This value is expressed
mebibytes (see 3.5.2).

The CURRENT READ RETRIES COUNT field indicates the number of times a read retry occurred in the partition
specified by the PARTITION NUMBER field in the CDB during this load of the medium.1)

The PREVIOUS AMOUNT OF DATA WRITTEN field indicates the amount of data written to the medium in the
partition specified by the PARTITION NUMBER field in the CDB during the previous load of the medium. This
value is expressed in mebibytes (see 3.5.2).

The PREVIOUS WRITE RETRIES COUNT field indicates the total number of times a write retry occurred in the
partition specified by the PARTITION NUMBER field in the CDB during the previous load of the medium.1)

The PREVIOUS AMOUNT OF DATA READ field indicates the amount of data read from the medium in the partition
specified by the PARTITION NUMBER field in the CDB during the previous load of the medium. This value is

606 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

expressed in mebibytes (see 3.5.2).

The PREVIOUS READ RETRIES COUNT field indicates the number of times a read retry occurred in the partition
specified by the PARTITION NUMBER field in the CDB during the previous load of the medium.1)

The TOTAL AMOUNT OF DATA WRITTEN field indicates the amount of data written to the medium in the partition
specified by the PARTITION NUMBER field in the CDB since the last time the medium was formatted. This value
is expressed in mebibytes (see 3.5.2).

The TOTAL WRITE RETRIES COUNT field indicates the total number of times a write retry occurred in the partition
specified by the PARTITION NUMBER field in the CDB since the last time the medium was formatted.1)

The TOTAL AMOUNT OF DATA READ field indicates the amount of data read from the medium in the partition
specified by the PARTITION NUMBER field in the CDB since the last time the medium was formatted. This value
is expressed in mebibytes (see 3.5.2).

The TOTAL READ RETRIES COUNT field indicates the number of times a read retry occurred in the partition
specified by the PARTITION NUMBER field in the CDB since the last time the medium was formatted.1)

The LOAD COUNT field indicates the number of loads in the partition specified by the PARTITION NUMBER field in
the CDB since the last time the medium was formatted. This count accumulates over the life of the medium
but it is reset to zero after a medium format.

The TOTAL CHANGE PARTITION COUNT field indicates the number of times that switches to the partition specified
by the PARTITION NUMBER field in the CDB have been performed on the medium. This count accumulates over
the life of the medium but it is reset to zero after a medium format.

The TOTAL PARTITION INITIALIZE COUNT field indicates number of times that the partition specified by the
PARTITION NUMBER field in the CDB has been initialized. This count accumulates over the life of the medium
but it is reset to zero after a medium format.

7.4.2.3 Medium type attributes

Medium type attributes (see table 447) are stored in the medium auxiliary memory by the manufacturer. The
device server shall not alter medium type attributes. All supported medium type attributes shall have a status

Working Draft SCSI Primary Commands - 4 (SPC-4) 607

T10/BSR INCITS 513 Revision 37 17 May 2014

of read only or unavailable (see 5.7).

Table 447 — Medium type attributes

Attribute
Attribute Length
Identifier Name (in bytes) Format a Reference
0400h MEDIUM MANUFACTURER 8 ASCII 7.4.2.3.1
0401h MEDIUM SERIAL NUMBER 32 ASCII 7.4.2.3.2
0402h to 0405h Restricted (see SSC-4)
0406h MEDIUM MANUFACTURE DATE 8 ASCII 7.4.2.3.3
0407h MAM CAPACITY 8 BINARY 7.4.2.3.4
0408h MEDIUM TYPE 1 BINARY 7.4.2.3.5
0409h MEDIUM TYPE INFORMATION 2 BINARY 7.4.2.3.5
040Ah NUMERIC MEDIUM SERIAL NUMBER unspecified unspecified 7.4.2.3.6
040Bh to 07FFh Reserved
a
See table 441 in 7.4.1.

7.4.2.3.1 MEDIUM MANUFACTURER

This attribute contains eight bytes of left-aligned ASCII data (see 4.3.1) identifying the manufacturer of the
media. The medium manufacturer shall be a T10 vendor identification assigned by INCITS. A list of assigned
T10 vendor identifications is in Annex G and on the T10 web site (http://www.T10.org).

NOTE 39 - The T10 web site (http://www.t10.org) provides a convenient means to request an identification
code.

7.4.2.3.2 MEDIUM SERIAL NUMBER

This attribute contains the manufacturer’s serial number for the medium.

7.4.2.3.3 MEDIUM MANUFACTURE DATE

This attribute contains the date of manufacture of the medium. The format is YYYYMMDD (i.e., four numeric
ASCII characters for the year followed by two numeric ASCII characters for the month followed by two
numeric ASCII characters for the day with no intervening spaces).

7.4.2.3.4 MAM CAPACITY

This attribute is the total capacity of the medium auxiliary memory, in bytes.

7.4.2.3.5 MEDIUM TYPE and MEDIUM TYPE INFORMATION

These attributes contain information about non-data media and other types of media. The MEDIUM TYPE
INFORMATION attribute is interpreted according to the type of medium indicated by the MEDIUM TYPE (see

608 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

table 448).

Table 448 — MEDIUM TYPE and MEDIUM TYPE INFORMATION attributes

MEDIUM TYPE Description MEDIUM TYPE INFORMATION

00h Data medium Reserved
01h Cleaning medium Maximum number of cleaning cycles permitted
02h to 7Fh Reserved Reserved
80h Write-once medium Reserved
81h to FFh Reserved Reserved

7.4.2.3.6 NUMERIC MEDIUM SERIAL NUMBER

This attribute contains the manufacturer’s serial number for the medium in a vendor specific format.

7.4.2.4 Host type attributes

Application clients may use the WRITE ATTRIBUTE command (see 6.48) and READ ATTRIBUTE command
(see 6.17) to maintain the attributes shown in table 449. All supported host type attributes shall have a status
of nonexistent or read/write (see 5.7).

Table 449 — Host type attributes

Attribute
Attribute Length
Identifier Name (in bytes) Format a Reference
0800h APPLICATION VENDOR 8 ASCII 7.4.2.4.1
0801h APPLICATION NAME 32 ASCII 7.4.2.4.2
0802h APPLICATION VERSION 8 ASCII 7.4.2.4.3
0803h USER MEDIUM TEXT LABEL 160 TEXT 7.4.2.4.4
0804h DATE AND TIME LAST WRITTEN 12 ASCII 7.4.2.4.5
0805h TEXT LOCALIZATION IDENTIFIER 1 BINARY 7.4.2.4.6
0806h BARCODE 32 ASCII 7.4.2.4.7
0807h OWNING HOST TEXTUAL NAME 80 TEXT 7.4.2.4.8
0808h MEDIA POOL 160 TEXT 7.4.2.4.9
0809h PARTITION USER TEXT LABEL 16 ASCII 7.4.2.4.10
080Ah LOAD/UNLOAD AT PARTITION 1 BINARY 7.4.2.4.11
080Bh APPLICATION FORMAT VERSION 16 ASCII 7.4.2.4.12
080Ch Restricted (see SSC-4)
080Dh to BFFh Reserved
a
See table 441 in 7.4.1.

Working Draft SCSI Primary Commands - 4 (SPC-4) 609

T10/BSR INCITS 513 Revision 37 17 May 2014

7.4.2.4.1 APPLICATION VENDOR

This attribute identifies the manufacturer of the application client (e.g., class driver or backup program)
associated with use of the MAM. The attribute value should be a T10 vendor identification assigned by
INCITS. A list of assigned T10 vendor identifications is in Annex G and on the T10 web site
(http://www.T10.org). This attribute may provide inaccurate information if the application client does not
update it.

NOTE 40 - The T10 web site (http://www.t10.org) provides a convenient means to request an identification
code.

7.4.2.4.2 APPLICATION NAME

This attribute contains the name of the application client.

7.4.2.4.3 APPLICATION VERSION

This attribute contains the version of the application client.

7.4.2.4.4 USER MEDIUM TEXT LABEL

This attribute contains a user assigned label for the volume.

7.4.2.4.5 DATE & TIME LAST WRITTEN

This attribute contains the time at which the application client last wrote to the medium auxiliary memory. The
format is YYYYMMDDHHMM (i.e., four numeric ASCII characters for the year followed by two numeric ASCII
characters for the month followed by two numeric ASCII characters for the day followed by two numeric ASCII
characters between 00 and 24 for the hour followed by two numeric ASCII characters for the minute with no
intervening spaces).

610 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.4.2.4.6 TEXT LOCALIZATION IDENTIFIER

This attribute defines the character set (see table 450) used for attributes with a TEXT format (see 7.4.1).

Table 450 — TEXT LOCALIZATION IDENTIFIER attribute values

Value Meaning
00h No code specified (ASCII)
01h ISO/IEC 8859-1 (Europe, Latin America)
02h ISO/IEC 8859-2 (Eastern Europe)
03h ISO/IEC 8859-3 (SE Europe/miscellaneous)
04h ISO/IEC 8859-4 (Scandinavia/Baltic)
05h ISO/IEC 8859-5 (Cyrillic)
06h ISO/IEC 8859-6 (Arabic)
07h ISO/IEC 8859-7 (Greek)
08h ISO/IEC 8859-8 (Hebrew)
09h ISO/IEC 8859-9 (Latin 5)
0Ah ISO/IEC 8859-10 (Latin 6)
0Bh to 7Fh Reserved
80h ISO/IEC 10646-1 (UCS-2BE)
81h ISO/IEC 10646-1 (UTF-8)
82h to FFh Reserved

7.4.2.4.7 BARCODE

This attribute contains the barcode associated with the medium described by the MAM.

7.4.2.4.8 OWNING HOST TEXTUAL NAME

This attribute indicates the host from which that USER MEDIUM TEXT LABEL (see 7.4.2.4.4) originates.

7.4.2.4.9 MEDIA POOL

This attribute indicates the media pool to which this medium belongs.

7.4.2.4.10 PARTITION USER TEXT LABEL

This attribute is a user assigned identifier for the partition specified by the PARTITION NUMBER field in the CDB.

7.4.2.4.11 LOAD/UNLOAD AT PARTITION

This attribute indicates whether the media is capable of being loaded or unloaded at the partition specified by
the PARTITION NUMBER field in the CDB. If loads and unloads are enabled for the specified partition, the value
of this attribute shall be one. If loads and unloads are not enabled for the specified partition, the value of this
attribute shall be zero. All attribute values other than zero and one are reserved. If LOAD/UNLOAD AT
PARTITION is disabled, then loads and unloads are performed at the beginning of the media instead of at the
specified partition. If this attribute is in the nonexistent state (see 5.7), then the default action shall be to load
and unload at the beginning of media.

Working Draft SCSI Primary Commands - 4 (SPC-4) 611

T10/BSR INCITS 513 Revision 37 17 May 2014

7.4.2.4.12 APPLICATION FORMAT VERSION

This attribute indicates the version of the format being used by the application that set this attribute.

612 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.5 Mode parameters

7.5.1 Summary of mode page codes

The page code assignments for mode pages are summarized in table 451.

Table 451 — Summary of mode page codes

Mode page name Page code Subpage code Reference

Control 0Ah n/a a 7.5.8
Control Extension 0Ah 01h 7.5.9
Disconnect-Reconnect 02h n/a a 7.5.10
Extended 15h 01h to FEh 7.5.11
Extended Device-Type Specific 16h 01h to FEh 7.5.12
Power Condition 1Ah n/a a 7.5.13
Power Consumption 1Ah 01h 7.5.14
Protocol Specific Logical Unit 18h n/a a 7.5.15
Protocol Specific Port 19h n/a a 7.5.16
18h 01h to FEh
Restricted (see applicable protocol standard)
19h 01h to FEh
01h 00h to FEh
03h to 08h 00h to FEh
0Ah F0h to FEh
Restricted (see applicable command standard) 0Bh to 14h 00h to FEh
1Ah F0h to FEh
1Bh to 1Fh 00h to FEh
20h to 3Eh 00h to FEh
b
Return all pages 3Fh 00h b 6.13 and 6.14
Return all pages and subpages 3Fh b FFh b 6.13 and 6.14
b b
Return all subpages 00h to 3Eh FFh 6.13 and 6.14
c
Obsolete
Vendor specific d
Reserved All other codes
A numeric ordered listing of mode page and subpage codes is provided in F.6.
a
Applicable only in the MODE SENSE command (see table 201 in 6.13).
b The use of these page codes and subpage codes is described in table 201 (see 6.13).
c The following page codes are obsolete: 09h.
d
Page code 00h is vendor specific and does not require a page format or a subpage code.

Working Draft SCSI Primary Commands - 4 (SPC-4) 613

T10/BSR INCITS 513 Revision 37 17 May 2014

7.5.2 Mode page policies

Logical units shall share mode parameter header and block descriptor values across all I_T nexuses. I_T
nexus loss shall not affect mode parameter header, block descriptor, and mode page values.

Each logical unit shall maintain current values and saved values of each mode page based on any of the
policies listed in table 452. The mode page policy used for each mode page may be reported in the Mode
Page Policy VPD page (see 7.8.9).

Table 452 — Mode page policies

Mode page policy Number of mode page copies

Shared One copy of the mode page that is shared by all I_T nexuses.
Per target port A separate copy of the mode page for each target port with
each copy shared by all initiator ports.
Per I_T nexus A separate copy of the mode page for each I_T nexus

After a logical unit reset, each mode parameter header, block descriptor, and mode page shall revert to saved
values if supported or default values if saved values are not supported.

7.5.3 Mode parameters overview

This subclause describes the mode parameter headers, block descriptors, and mode pages used with MODE
SELECT command (see 6.11 and 6.12) and MODE SENSE command (see 6.13 and 6.14) that are applicable
to all SCSI devices. Subpages are identical to mode pages except that they include a SUBPAGE CODE field that
further differentiates the mode page contents. Mode pages specific to each device type are described in the
command standard that applies to that device type.

7.5.4 Mode parameter list format

The mode parameter list shown in table 453 contains a header, followed by zero or more block descriptors,
followed by zero or more variable length mode pages. Parameter lists are defined for each device type.

Table 453 — Mode parameter list

Bit
7 6 5 4 3 2 1 0
Byte
Mode parameter header
Block descriptor(s)
Mode page(s) or vendor specific (e.g., page code set to zero)

614 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.5.5 Mode parameter header formats

The mode parameter header that is used by the MODE SELECT(6) command (see 6.11) and the MODE
SENSE(6) command (see 6.13) is defined in table 454.

Table 454 — Mode parameter header(6)

Bit
7 6 5 4 3 2 1 0
Byte
0 MODE DATA LENGTH

1 MEDIUM TYPE

2 DEVICE-SPECIFIC PARAMETER

3 BLOCK DESCRIPTOR LENGTH

The mode parameter header that is used by the MODE SELECT(10) command (see 6.12) and the MODE
SENSE(10) command (see 6.14) is defined in table 455.

Table 455 — Mode parameter header(10)

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
MODE DATA LENGTH
1 (LSB)
2 MEDIUM TYPE

3 DEVICE-SPECIFIC PARAMETER

4 Reserved LONGLBA

5 Reserved
6 (MSB)
BLOCK DESCRIPTOR LENGTH
7 (LSB)

When using the MODE SENSE command, the MODE DATA LENGTH field indicates the number of bytes that
follow in the mode parameter list. When using the MODE SELECT command, the MODE DATA LENGTH field is
reserved.

NOTE 41 - Logical units that support more than 256 bytes of block descriptors and mode pages should
implement ten-byte mode commands. The MODE DATA LENGTH field in the six-byte CDB header limits the
transferred data to 256 bytes.

The contents of the MEDIUM TYPE field are unique for each device type. Refer to the mode parameters
subclause of the specific device type command standard for definition of these values. Some device types
reserve this field.

The DEVICE-SPECIFIC PARAMETER field is unique for each device type. Refer to the mode parameters subclause
of the specific device type command standard for definition of this field.

If the Long LBA (LONGLBA) bit is set to zero, the mode parameter block descriptor(s), if any, are each eight
bytes long and have the format described in 7.5.6.1. If the LONGLBA bit is set to one, the mode parameter block
descriptor(s), if any, are each 16 bytes long and have a format described in a command standard.

Working Draft SCSI Primary Commands - 4 (SPC-4) 615

T10/BSR INCITS 513 Revision 37 17 May 2014

The BLOCK DESCRIPTOR LENGTH field indicates the length in bytes of all the block descriptors. It is equal to the
number of block descriptors times eight if the LONGLBA bit is set to zero or times sixteen if the LONGLBA bit is
set to one, and does not include the length of mode pages or vendor specific parameters (e.g., page code set
to zero), if any, that may follow the last block descriptor. A block descriptor length of zero indicates that no
block descriptors are included in the mode parameter list. This condition shall not be considered an error.

7.5.6 Mode parameter block descriptor formats

7.5.6.1 General block descriptor format

If the LONGLBA bit is set to zero (see 7.5.5), the mode parameter block descriptor format for all device types
except direct access block devices (see SBC-3) is shown in table 456.

Table 456 — General mode parameter block descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 DENSITY CODE

1 (MSB)
•• • NUMBER OF BLOCKS
3 (LSB)
4 Reserved
5 (MSB)
•• • BLOCK LENGTH
7 (LSB)

Block descriptors specify some of the medium characteristics for all or part of a logical unit. Each block
descriptor, if any, contains a DENSITY CODE field, a NUMBER OF BLOCKS field, and a BLOCK LENGTH field. Block
descriptor values are always current (i.e., saving is not supported). Whenever any block descriptor values are
changed, the device server shall establish a unit attention condition (see SAM-5) for the initiator port
associated with every I_T nexus except the I_T nexus on which the MODE SELECT command (see 6.11) was
received, with the additional sense code set to MODE PARAMETERS CHANGED. Command standards may
place additional requirements on the general mode parameter block descriptor. Requirements in the
command standards that conflict with requirements defined in this subclause shall take precedence over the
requirements defined in this subclause.

The DENSITY CODE field is unique for each device type. Refer to the mode parameters subclause of the specific
device type command standard for definition of this field.

The NUMBER OF BLOCKS field specifies the number of logical blocks on the medium to which the DENSITY CODE
field and BLOCK LENGTH field apply. A value of zero indicates that all of the remaining logical blocks of the
logical unit shall have the medium characteristics specified.

If the number of logical blocks on the medium exceeds the maximum value that may be specified in the
NUMBER OF BLOCKS field, then a value of FF FFFFh indicates that all of the remaining logical blocks of the
logical unit shall have the medium characteristics specified.

NOTE 42 - There may be implicit association between parameters defined in the mode pages and block
descriptors. In this case, the device server may change parameters not explicitly sent with the MODE
SELECT command. A subsequent MODE SENSE command may be used to detect these changes.

616 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

NOTE 43 - The number of remaining logical blocks may be unknown for some device types.

The BLOCK LENGTH field specifies the length in bytes of each logical block described by the block descriptor.
For sequential-access devices, a block length of zero indicates that the logical block size written to the
medium is specified by the TRANSFER LENGTH field in the CDB (see SSC-4).

7.5.7 Mode page and subpage formats and page codes

The page_0 mode page format is defined in table 457.

Table 457 — Page_0 mode page format

Bit
7 6 5 4 3 2 1 0
Byte
0 PS SPF (0b) PAGE CODE

1 PAGE LENGTH (n-1)

2
•• • Mode parameters
n

The sub_page mode page format is defined in table 458.

Table 458 — Sub_page mode page format

Bit
7 6 5 4 3 2 1 0
Byte
0 PS SPF (1b) PAGE CODE

1 SUBPAGE CODE

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4
•• • Mode parameters
n

Each mode page contains a PS bit, an SPF bit, a PAGE CODE field, a PAGE LENGTH field, and a set of mode
parameters. The page codes are defined in this subclause and in the mode parameter subclauses in the
command standard for the specific device type. Each mode page with a SPF bit set to one contains a SUBPAGE
CODE field.

A SubPage Format (SPF) bit set to zero indicates that the page_0 mode page format is being used. A SPF bit
set to one indicates that the sub_page mode page format is being used.

When using the MODE SENSE command, a parameters saveable (PS) bit set to one indicates that the mode
page may be saved by the logical unit in a nonvolatile, vendor specific location. A PS bit set to zero indicates
that the device server is not able to save the supported parameters. When using the MODE SELECT
command, the PS bit is reserved.

The PAGE CODE field and SUBPAGE CODE field (see 7.5.1) identify the format and parameters defined for that
mode page. Page codes are defined as applying to all device types or as applying to a specific device type.

Working Draft SCSI Primary Commands - 4 (SPC-4) 617

T10/BSR INCITS 513 Revision 37 17 May 2014

The page codes that apply to a specific device type are defined in the command standard for that device type.
The applicability of each subpage code matches that of the page code with which the subpage code is
associated.

The device server shall use the page_0 mode page format only for mode pages associated with subpage
code 00h (i.e., mode pages for which table 201 (see 6.13.1) requires the use of page_0 mode page format).

When using the MODE SENSE command, if page code 00h (i.e., vendor specific mode page) is implemented,
the device server shall return that mode page last in response to a request to return all mode pages (e.g., a
MODE SENSE command (see 6.13 or 6.14) with the PAGE CODE field set to 3Fh). When using the MODE
SELECT command, this mode page should be sent last.

The PAGE LENGTH field specifies the length in bytes of the mode parameters that follow. If the parameter list in
a MODE SELECT command (see 6.11 or 6.12) does not set the PAGE LENGTH field to the value that is returned
for the mode page by a MODE SENSE command, then the device server shall terminate the MODE SELECT
command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID FIELD IN PARAMETER LIST. The logical unit may implement a mode page that is
less than the full mode page length defined, provided no field is truncated and the PAGE LENGTH field correctly
specifies the actual length implemented.

The mode parameters for each mode page are defined in the following subclauses or in the mode parameters
subclause in the command standard for the specific device type. Mode parameters not implemented by the
logical unit shall be set to zero.

7.5.8 Control mode page

The Control mode page (see table 459) provides controls over SCSI features that are applicable to all device
types (e.g., task set management and error logging). If a field in this mode page is changed while there is a
command already in the task set, then whether the old or new value of the field applies to that command is
outside the scope of this standard. The mode page policy (see 7.5.2) for this mode page shall be shared or
per I_T nexus.

Table 459 — Control mode page

Bit
7 6 5 4 3 2 1 0
Byte
0 PS SPF (0b) PAGE CODE (0Ah)
1 PAGE LENGTH (0Ah)
2 TST TMF_ONLY DPICZ D_SENSE GLTSD RLEC

3 QUEUE ALGORITHM MODIFIER NUAR QERR Obsolete

4 VS RAC UA_INTLCK_CTRL SWP Obsolete
5 ATO TAS ATMPE RWWP Reserved AUTOLOAD MODE

6
Obsolete
7
8 (MSB)
BUSY TIMEOUT PERIOD
9 (LSB)
10 (MSB)
EXTENDED SELF-TEST COMPLETION TIME
11 (LSB)

618 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The PS bit, SPF bit, PAGE CODE field, and PAGE LENGTH field are described in 7.5.7.

The SPF bit, PAGE CODE field, and PAGE LENGTH field shall be set as shown in table 459 for the Control mode
page.

A task set type (TST) field (see table 460) specifies the type of task set in the logical unit.

Table 460 — Task set type (TST) field

Code Description
000b The logical unit maintains one task set for all I_T nexuses
001b The logical unit maintains separate task sets for each I_T nexus
010b to 111b Reserved

Regardless of the mode page policy (see 7.5.2) for the Control mode page, the shared mode page policy shall
be applied to the TST field. If the most recent MODE SELECT changes the setting of this field, then the device
server shall establish a unit attention condition (see SAM-5) for the initiator port associated with every I_T
nexus except the I_T nexus on which the MODE SELECT command was received, with the additional sense
code set to MODE PARAMETERS CHANGED.

The allow task management functions only (TMF_ONLY) bit set to zero specifies that the device server shall
process commands with the ACA task attribute received on the faulted I_T nexus while an ACA condition is
established (see SAM-5). A TMF _ONLY bit set to one specifies that the device server shall complete all
commands received on the faulted I_T nexus with an ACA ACTIVE status while an ACA condition is
established.

A disable protection information check if protect field is zero (DPICZ) bit set to zero indicates that checking of
protection information bytes is enabled. A DPICZ bit set to one indicates that checking of protection information
is disabled on commands with:

a) the RDPROTECT field (see SBC-3) set to zero;

b) the VRPROTECT field (see SBC-3) set to zero; or
c) the ORPROTECT field (see SBC-3) set to zero.

A descriptor format sense data (D_SENSE) bit set to zero specifies that the device server shall use fixed format
sense data (see 4.5.3) when including sense data in the same I_T_L_Q nexus transaction as the status. A
D_SENSE bit set to one specifies that the device server shall use descriptor format sense data (see 4.5.2) when
including sense data in the same I_T_L_Q nexus transaction as the status, except as defined in 4.5.1. If an
application client enables reporting of referrals in sense data (see SBC-3), then the application client should
be able to handle up to 252 bytes of sense data.

A global logging target save disable (GLTSD) bit set to zero specifies that the logical unit implicitly saves, at
vendor specific intervals, each log parameter in which the TSD bit (see 7.3) is set to zero. A GLTSD bit set to
one specifies that the logical unit shall not implicitly save any log parameters.

A report log exception condition (RLEC) bit set to one specifies that the device server shall report log exception
conditions as described in 7.3. A RLEC bit set to zero specifies that the device server shall not report log
exception conditions.

Working Draft SCSI Primary Commands - 4 (SPC-4) 619

T10/BSR INCITS 513 Revision 37 17 May 2014

The QUEUE ALGORITHM MODIFIER field (see table 461) specifies restrictions on the algorithm used for reordering
commands having the SIMPLE task attribute (see SAM-5).

Table 461 — QUEUE ALGORITHM MODIFIER field

Code Description
0h Restricted reordering: The device server shall order the processing sequence of com-
mands having the SIMPLE task attribute such that data integrity is maintained for that I_T
nexus (i.e., if the transmission of new SCSI transport protocol requests is halted at any
time, the final value of all data observable on the medium shall be the same as if all the
commands had been processed with the ORDERED task attribute).
1h Unrestricted reordering allowed: The device server may reorder the processing
sequence of commands having the SIMPLE task attribute in any manner. Any data
integrity exposures related to command sequence order shall be explicitly handled by
the application client through the selection of appropriate commands and task attributes.
2h to 7h Reserved
8h to Fh Vendor specific

A no unit attention on release (NUAR) bit set to one specifies that the device server shall not establish a unit
attention condition as described in 5.12.11.2.2. A NUAR bit set to zero specifies that the device server shall
establish a unit attention condition as described in 5.12.11.2.2.

The queue error management (QERR) field (see table 462) specifies how the device server shall handle other
commands as the result of one command being terminated with CHECK CONDITION status (see SAM-5).
The task set type (see the TST field definition in this subclause) defines which other commands are affected. If
the TST field equals 000b, then all commands from all I_T nexuses are affected. If the TST field equals 001b,
then only commands from the same I_T nexus as the command that is terminated with CHECK CONDITION
status are affected.

Table 462 — Queue error management (QERR) field

Code Definition
00b If an ACA condition is established, the affected commands in the task set shall resume after
the ACA condition is cleared (see SAM-5). Otherwise, all commands other than the command
terminated with CHECK CONDITION status shall be processed as if no error occurred.
01b All the affected commands in the task set shall be aborted when the CHECK CONDITION
status is returned. If the TAS bit is set to zero, the device server shall establish a unit attention
condition (see SAM-5) for the initiator port associated with every I_T nexus that had
commands aborted except for the I_T nexus on which the command was terminated with
CHECK CONDITION status, with the additional sense code set to COMMANDS CLEARED BY
ANOTHER INITIATOR. If the TAS bit is set to one, all affected commands in the task set for I_T
nexuses other than the I_T nexus on which the command was terminated with CHECK
CONDITION status shall be completed with TASK ABORTED status and no unit attention shall
be established. For the I_T nexus on which the command was terminated with CHECK
CONDITION status, no status shall be returned for the commands that are aborted.
10b Reserved
11b Affected commands in the task set belonging to the I_T nexus on which a command was
terminated with CHECK CONDITION status shall be aborted as part of processing the
command termination.

620 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The report a check (RAC) bit provides control of reporting long busy conditions or CHECK CONDITION status.
A RAC bit set to one specifies that the device server should return CHECK CONDITION status rather than
returning BUSY status if the reason for returning BUSY status may persist for a longer time than that specified
by the BUSY TIMEOUT PERIOD field. A RAC bit set to zero specifies that the device server may return BUSY
status regardless of the length of time the reason for returning BUSY status may persist.

The unit attention interlocks control ( UA_ INTLCK_ CTRL) field (see table 463) controls the clearing of unit
attention conditions reported in the same I_T_L_Q nexus transaction as a CHECK CONDITION status and
whether returning a status of BUSY, TASK SET FULL or RESERVATION CONFLICT results in the estab-
lishment of a unit attention condition (see SAM-5).

Table 463 — Unit attention interlocks control (UA_INTLCK_CTRL) field

Code Definition
00b The logical unit shall clear any unit attention condition reported in the same I_T_L_Q nexus
transaction as a CHECK CONDITION status and shall not establish a unit attention condition for
a command that is completed with BUSY status, TASK SET FULL status, or RESERVATION
CONFLICT status.
01b Reserved
10b The logical unit shall not clear any unit attention condition reported in the same I_T_L_Q nexus
transaction as a CHECK CONDITION status and shall not establish a unit attention condition for
a command that is completed with BUSY status, TASK SET FULL status, or RESERVATION
CONFLICT status.
11b The logical unit shall not clear any unit attention condition reported in the same I_T_L_Q nexus
transaction as a CHECK CONDITION status and shall establish a unit attention condition for the
initiator port associated with the I_T nexus on which the BUSY status, TASK SET FULL status,
or RESERVATION CONFLICT status is being returned. Depending on the status, the additional
sense code shall be set to PREVIOUS BUSY STATUS, PREVIOUS TASK SET FULL STATUS,
or PREVIOUS RESERVATION CONFLICT STATUS. Until it is cleared by a REQUEST SENSE
command, a unit attention condition shall be established only once for a BUSY status, TASK
SET FULL status, or RESERVATION CONFLICT status regardless to the number of commands
completed with one of those status codes.
NOTE – The requirements for REQUEST SENSE processing of unit attention interlocks are defined
in SAM -5.

A software write protect (SWP) bit set to one specifies that the logical unit shall inhibit writing to the medium. If
the SWP bit is changed from zero to one, any cached or buffered write data shall be written to the medium
before enforcing the write protected condition. If the SWP bit is set to one, the device server shall terminate all
commands that require writes to the medium with CHECK CONDITION status, with the sense key set to DATA
PROTECT, and the additional sense code set to WRITE PROTECTED. If the SWP bit is set to zero, specifies
logical unit may allow writing to the medium depending on other write inhibit mechanisms implemented by the
logical unit.

If the device type's command standard defines a write protect (WP) bit in the DEVICE-SPECIFIC PARAMETER field
in the mode parameter header, then:

a) if the SWP bit is set to one, the WP bit shall be set to one for subsequent MODE SENSE commands;
and
b) if the SWP bit is set to zero, the value of the WP bit is device type specific.

For a list of commands affected by the SWP bit and details of the WP bit see the command standard for the
specific device type.

Working Draft SCSI Primary Commands - 4 (SPC-4) 621

T10/BSR INCITS 513 Revision 37 17 May 2014

An application tag owner (ATO) bit set to zero specifies that the device server may modify the contents of the
LOGICAL BLOCK APPLICATION TAG field and, depending on the protection type, may modify the contents of the
LOGICAL BLOCK REFERENCE TAG field (see SBC-3). If the ATO bit is set to one the device server shall not modify
the LOGICAL BLOCK APPLICATION TAG field and, depending on the protection type, shall not modify the contents
of the LOGICAL BLOCK REFERENCE TAG field.

A task aborted status (TAS) bit set to zero specifies that aborted commands shall be terminated by the device
server without any response to the application client. A TAS bit set to one specifies that commands aborted by
the actions of an I_T nexus other than the I_T nexus on which the command was received shall be completed
with TASK ABORTED status (see SAM-5).

An application tag mode page enabled (ATMPE) bit set to zero specifies that use of the Application Tag mode
page (see SBC-3) is disabled and the contents of logical block application tags are not defined by the
Application Tag mode page. An ATMPE bit set to one specifies that use of the Application Tag mode page is
enabled.

If:
a) the ATMPE bit is set to one;
b) the ATO bit is set to one;
c) the value in the DPICZ bit allows protection information checking for the specified command; and
d) the APP_CHK bit is set to one in the Extended INQUIRY VPD page (see 7.8.7),
then knowledge of the value of the Application Tag shall come from the values in the Application Tag mode
page as specified by the DPICZ bit.

A reject write without protection (RWWP) bit set to zero specifies that the device server shall process write
commands that are specified to include user data without protection information (e.g., a WRITE(10) command
with the WRPROTECT field set to 000b (see SBC-3)). A RWWP bit set to one specifies that the device server in a
logical unit that has been formatted with protection information shall terminate with CHECK CONDITION
status with the sense key set to ILLEGAL REQUEST and the additional sense code set to INVALID FIELD IN
CDB any write command that is specified to include user data without protection information.

The AUTOLOAD MODE field specifies the action to be taken by a removable medium device server at the time
when a medium is inserted. For devices other than removable medium devices, this field is reserved. Table
464 shows the usage of the AUTOLOAD MODE field.

Table 464 — AUTOLOAD MODE field

Code Definition
000b Medium shall be loaded for full access.
001b Medium shall be loaded for medium auxiliary memory access only.
010b Medium shall not be loaded.
011b to 111b Reserved

The BUSY TIMEOUT PERIOD field specifies the maximum time, in 100 milliseconds increments, that the
application client allows for the device server to return BUSY status for unanticipated conditions that are not a
routine part of commands from the application client. This value may be rounded down as defined in 5.8. A
0000h value in this field is undefined by this standard. An FFFFh value in this field is defined as an unlimited
time.

The EXTENDED SELF-TEST COMPLETION TIME field specifies advisory data that is the time in seconds that the
device server requires to complete an extended self-test provided the device server is not interrupted by
subsequent commands and no errors occur during processing of the self-test. The application client should

622 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

expect this time to increase significantly if other commands are sent to the logical unit while a self-test is in
progress or if errors occur during the processing of the self-test. Device servers supporting SELF-TEST CODE
field values other than 000b for the SEND DIAGNOSTIC command (see 6.42) shall support the EXTENDED
SELF-TEST COMPLETION TIME field. The EXTENDED SELF-TEST COMPLETION TIME field is not changeable. A value
of FFFFh indicates that the extended self-test takes 65 535 seconds or longer. If the value is FFFFh, then
refer to the EXTENDED SELF-TEST COMPLETION MINUTES field in the Extended INQUIRY Data VPD page (see
7.8.7).

7.5.9 Control Extension mode page

The Control Extension mode page (see table 465) provides controls over SCSI features that are applicable to
all device types. The mode page policy (see 7.5.2) for this mode page shall be shared. If a field in this mode
page is changed while there is a command already in the task set, then whether the old or new value of the
field applies to that command is outside the scope of this standard.

Table 465 — Control Extension mode page

Bit
7 6 5 4 3 2 1 0
Byte
0 PS SPF (1b) PAGE CODE (0Ah)
1 SUBPAGE CODE (01h)
2 (MSB)
PAGE LENGTH (001Ch)
3 (LSB)
4 Reserved TCMOS SCSIP IALUAE

5 Reserved INITIAL COMMAND PRIORITY

6 MAXIMUM SENSE DATA LENGTH

7
•• • Reserved
31

The PS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.5.7.

The SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field shall be set as shown in table 465 for
the Control Extension mode page.

A timestamp changeable by methods outside this standard (TCMOS) bit set to one specifies that a device clock
(see 5.2) may be initialized by methods outside the scope of this standard. A TCMOS bit set to zero specifies
that a device clock shall not be initialized by any method except the ones defined by this standard.

A SCSI precedence (SCSIP) bit set to one specifies that device clock initialization (see 5.2) specified by a SET
TIMESTAMP command (see 6.46) shall take precedence over methods outside the scope of this standard. A
SCSIP bit set to zero specifies that methods outside this standard may initialize a device clock and that the SET
TIMESTAMP command shall be terminated as described in 6.46.

An implicit asymmetric logical unit access enabled (IALUAE) bit set to one specifies that implicitly managed
transitions between primary target port asymmetric access states (see 5.15.2) are allowed. An IALUAE bit set
to zero specifies that implicitly managed transitions between primary target port asymmetric access states are
disallowed and indicates that implicitly managed transitions between primary target port asymmetric access
states are disallowed or not supported.

Working Draft SCSI Primary Commands - 4 (SPC-4) 623

T10/BSR INCITS 513 Revision 37 17 May 2014

The INITIAL COMMAND PRIORITY field specifies the priority that may be used as the command priority (see
SAM-5) for commands received by the logical unit on any I_T nexus (i.e., on any I_T_L nexus) where a priority
has not been modified by a SET PRIORITY command (see 6.44). If a MODE SELECT command specifies an
initial command priority value that is different than the current initial command priority, then the device server
shall set any priorities that have not be set with a SET PRIORITY command to a value different than the new
initial command priority value to the new priority. The device server shall establish a unit attention condition for
the initiator port associated with every I_T_L nexus that receives a new priority, with the additional sense code
set to PRIORITY CHANGED.

The MAXIMUM SENSE DATA LENGTH field specifies the maximum number of bytes of sense data the device
server shall include in the same I_T_L_Q nexus transaction as the status. A MAXIMUM SENSE DATA LENGTH field
set to zero specifies that there is no limit. The device server shall not include more sense data bytes in the
same I_T_L_Q nexus transaction as the status than the smaller of the length indicated by:

a) the MAXIMUM SENSE DATA LENGTH field; and

b) the MAXIMUM SUPPORTED SENSE DATA LENGTH field in the Extended INQUIRY VPD page (see 7.8.7).

7.5.10 Disconnect-Reconnect mode page

NOTE 44 - The name for this mode page, disconnect-reconnect, comes from the SCSI parallel interface.

The Disconnect-Reconnect mode page (see table 466) provides the application client the means to tune the
performance of a service delivery subsystem. The mode page policy (see 7.5.2) for this mode page shall be
shared or per target port. If the SCSI target device contains more than one target port, the mode page policy
should be per target port.

The Disconnect-Reconnect mode page controls parameters that affect one or more target ports. The
parameters that may be implemented are defined in the SCSI transport protocol standard for the target port.
The MLUS bit (see 7.8.9) shall be set to one in the mode page policy descriptor for this mode page.

The parameters for a target port affect its behavior regardless of which initiator port is forming an I_T nexus
with the target port. The parameters may be accessed by MODE SENSE (see 6.13) and MODE SELECT (see
6.11) commands directed to any logical unit accessible through the target port. If a parameter value is
changed, all the device servers for all logical units accessible through the target port shall establish a unit
attention condition for the initiator port associated with every I_T nexus that includes the target port except the
I_T nexus on which the MODE SELECT command was received, with the additional sense code set to MODE
PARAMETERS CHANGED.

If a parameter that is not appropriate for the specific SCSI transport protocol implemented by the target port is
non-zero, then the device server shall terminate the command with CHECK CONDITION status, with the
sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER
LIST.

624 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

An interconnect tenancy is a period of time during which a given pair of SCSI ports (i.e., an initiator port and a
target port) are accessing the interconnect layer to communicate with each other (e.g., on arbitrated intercon-
nects, a tenancy typically begins when a SCSI port successfully arbitrates for the interconnect and ends when
the SCSI port releases the interconnect for use by other devices). Data and other information transfers take
place during interconnect tenancies.

Table 466 — Disconnect-Reconnect mode page

Bit
7 6 5 4 3 2 1 0
Byte
0 PS SPF (0b) PAGE CODE (02h)
1 PAGE LENGTH (0Eh)
2 BUFFER FULL RATIO

3 BUFFER EMPTY RATIO

4 (MSB)
BUS INACTIVITY LIMIT
5 (LSB)
6 (MSB)
DISCONNECT TIME LIMIT
7 (LSB)
8 (MSB)
CONNECT TIME LIMIT
9 (LSB)
10 (MSB)
MAXIMUM BURST SIZE
11 (LSB)
12 EMDP FAIR ARBITRATION DIMM DTDC

13 Reserved
14 (MSB)
FIRST BURST SIZE
15 (LSB)

The PS bit, SPF bit, PAGE CODE field, and PAGE LENGTH field are described in 7.5.7.

The SPF bit, PAGE CODE field, and PAGE LENGTH field shall be set as shown in table 466 for the
Disconnect-Reconnect mode page.

The BUFFER FULL RATIO field specifies to the target port how full the buffer should be during read operations
prior to requesting an interconnect tenancy. Target ports that do not implement the requested ratio should
round down to the nearest implemented ratio as defined in 5.8.

The BUFFER EMPTY RATIO field specifies to the target port how empty the buffer should be during write
operations prior to requesting an interconnect tenancy. Target ports that do not implement the requested ratio
should round down to the nearest implemented ratio as defined in 5.8.

The buffer full and buffer empty ratios are numerators of a fractional multiplier that has 256 as its denominator.
A value of zero indicates that the target port determines when to request an interconnect tenancy consistent
with the disconnect time limit parameter. These parameters are advisory to the target port.

Working Draft SCSI Primary Commands - 4 (SPC-4) 625

T10/BSR INCITS 513 Revision 37 17 May 2014

EXAMPLE – Consider a target port with ten 512-byte buffers and a specified buffer full ratio of 3Fh. The formula is:
INTEGER((ratio256)number of buffers). Therefore in this example INTEGER((3Fh256)10) = 2. During the read
operations described in this example, the target port should request an interconnect tenancy whenever two or more
buffers are full.

The BUS INACTIVITY LIMIT field specifies the maximum time that the target port is permitted to maintain an
interconnect tenancy without data or information transfer. If the bus inactivity limit is exceeded, then the target
port shall conclude the interconnect tenancy, within the restrictions placed on it by the applicable SCSI
transport protocol. The contents of the DTDC field in this mode page also shall affect the duration of an
interconnect tenancy. This value may be rounded as defined in 5.8. A value of zero specifies that there is no
bus inactivity limit. Different SCSI transport protocols define different units of measure for the bus inactivity
limit.

The DISCONNECT TIME LIMIT field specifies the minimum time that the target port shall wait between
interconnect tenancies. This value may be rounded as defined in 5.8. A value of zero specifies that there is no
disconnect time limit. Different SCSI transport protocols define different units of measure for the disconnect
time limit.

The CONNECT TIME LIMIT field specifies the maximum duration of a single interconnect tenancy. If the connect
time limit is exceeded, then the target port shall conclude the interconnect tenancy, within the restrictions
placed on it by the applicable SCSI transport protocol. The contents of the DTDC field in this mode page also
shall affect the duration of an interconnect tenancy. This value may be rounded as defined in 5.8. A value of
zero specifies that there is no connect time limit. Different SCSI transport protocols define different units of
measure for the connect time limit.

The MAXIMUM BURST SIZE field specifies the maximum amount of data that the target port shall transfer during
a single data transfer operation. This value is expressed in increments of 512 bytes (i.e., a value of one means
512 bytes, two means 1 024 bytes, etc.). The relationship, if any, between data transfer operations and
interconnect tenancies is defined in the individual SCSI transport protocol standards. A value of zero specifies
there is no limit on the amount of data transferred per data transfer operation.

In terms of the SCSI transport protocol services (see SAM-5), the device server shall limit the Request Byte
Count argument to the Receive Data-Out protocol service and the Send Data-In protocol service to the
amount specified in the MAXIMUM BURST SIZE field.

The enable modify data pointers (EMDP) bit specifies whether or not the target port may transfer data out of
order. If the EMDP bit is set to zero, the target port shall not transfer data out of order. If the EMDP bit is set to
one, the target port is allowed to transfer data out of order.

The FAIR ARBITRATION field specifies whether the target port should use fair or unfair arbitration when
requesting an interconnect tenancy. The field may be used to specify different fairness methods as defined in
the individual SCSI transport protocol standards.

A disconnect immediate (DIMM) bit set to zero specifies that the target port may transfer data for a command
during the same interconnect tenancy in which the SCSI target device receives the command. Whether or not
the target port does so may depend upon the target port’s internal algorithms, the rules of the applicable SCSI
transport protocol, and settings of the other parameters in this mode page. A disconnect immediate (DIMM) bit
set to one specifies that the target port shall not transfer data for a command during the same interconnect
tenancy in which the SCSI target device receives the command.

626 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The data transfer disconnect control (DTDC) field (see table 467) defines other restrictions on when multiple
interconnect tenancies are permitted. A non-zero value in the DTDC field shall take precedence over other
interconnect tenancy controls represented by other fields in this mode page.

Table 467 — Data transfer disconnect control (DTDC) field

Code Description
000b Data transfer disconnect control is not used. Interconnect tenancies are
controlled by other fields in this mode page.
001b All data for a command shall be transferred within a single interconnect tenancy.
010b Reserved
011b All data and the response for a command shall be transferred within a single
interconnect tenancy.
100b to 111b Reserved

The FIRST BURST SIZE field specifies the maximum amount of data that may be transferred to the target port for
a command along with the command (i.e., the first burst). This value is expressed in increments of 512 bytes
(i.e., a value of one means 512 bytes, two means 1 024 bytes, etc.). The meaning of a value of zero is SCSI
transport protocol specific. SCSI transport protocols supporting this field shall provide an additional
mechanism to enable and disable the first burst function.

In terms of the SCSI transport protocol services (see SAM-5), the Receive Data-Out protocol service shall
transfer the first FIRST BURST SIZE amount of data during the first burst.

7.5.11 Extended mode page

The Extended mode page (see table 468) provides a means to specify subpages that are defined for all
device types. Subpage code 00h is reserved. All Extended mode pages use the sub_page mode page format.

Table 468 — Extended mode page

Bit
7 6 5 4 3 2 1 0
Byte
0 PS SPF (1b) PAGE CODE (15h)
1 SUBPAGE CODE

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4
•• • Subpage specific mode parameters
n

The PS bit, SPF bit, PAGE CODE field, and PAGE LENGTH field are described in 7.5.7.

The SPF bit and PAGE CODE field shall be set as shown in table 468 for the Extended mode page.

Working Draft SCSI Primary Commands - 4 (SPC-4) 627

T10/BSR INCITS 513 Revision 37 17 May 2014

7.5.12 Extended Device-Type Specific mode page

The Extended Device-Type Specific mode page (see table 469) provides a means to specify subpages that
are defined differently for each device type. Subpage code 00h is reserved in the MODE SENSE command
(see 6.13.1). All Extended Device-Type Specific mode pages use the sub_page mode page format.

Table 469 — Extended Device-Type Specific mode page

Bit
7 6 5 4 3 2 1 0
Byte
0 PS SPF (1b) PAGE CODE (16h)
1 SUBPAGE CODE

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4
•• • Subpage specific mode parameters
n

The PS bit, SPF bit, PAGE CODE field, and PAGE LENGTH field are described in 7.5.7.

The SPF bit and PAGE CODE field shall be set as shown in table 469 for the Extended Device-Type Specific
mode page.

7.5.13 Power Condition mode page

The Power Condition mode page provides an application client with a method to control the power condition of
a logical unit (see 5.11).

The mode page policy (see 7.5.2) for this mode page shall be shared.

The logical unit shall use the values in the Power Condition mode page to control its power condition after a
power on or a hard reset until a START STOP UNIT command (see SBC-3) setting a power condition is
received.

628 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 470 defines the Power Condition mode page.

Table 470 — Power Condition mode page

Bit
7 6 5 4 3 2 1 0
Byte
0 PS SPF (0b) PAGE CODE (1Ah)
1 PAGE LENGTH (26h)
2 PM_BG_PRECEDENCE Reserved STANDBY_Y

3 Reserved IDLE_C IDLE_B IDLE_A STANDBY_Z

4 (MSB)
•• • IDLE_A CONDITION TIMER
7 (LSB)
8 (MSB)
•• • STANDBY_Z CONDITION TIMER
11 (LSB)
12 (MSB)
•• • IDLE_B CONDITION TIMER
15 (LSB)
16 (MSB)
•• • IDLE_C CONDITION TIMER
19 (LSB)
20 (MSB)
•• • STANDBY_Y CONDITION TIMER
23 (LSB)
24
•• • Reserved
38
39 CCF IDLE CCF STANDBY CCF STOPPED Reserved

The PS bit, SPF bit, PAGE CODE field, and PAGE LENGTH field are described in 7.5.7.

The SPF bit, PAGE CODE field, and PAGE LENGTH field shall be set as shown in table 470 for the Power Condition
mode page.

The PM_BG_PRECEDENCE field (see table 471) specifies the interactions between background functions and
power management.

Working Draft SCSI Primary Commands - 4 (SPC-4) 629

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 471 — PM_BG_PRECEDENCE field

Cod Description
e
00b Vendor specific
01b Performing background functions take precedence over maintaining low power conditions as
follows:
a) if the logical unit is in a low power condition as the result of a power condition timer
associated with that condition expiring, then:
1) the logical unit shall change from that power condition, if necessary, to the power
condition required to perform the background function, if:
a) a timer associated with a background scan operation expires, and that function is
enabled (see SBC-3); or
b) an event occurs to initiate a device specific background function, and that function
is enabled (see 5.3);
2) the logical unit shall perform the background function(s) based on the definitions in
this standard and other command standards (e.g., if the device server receives a
command while performing a background function, then the logical unit shall suspend
the function to process the command);
3) if more than one condition is met to initiate a background function, then:
a) all initiated background functions shall be performed; and
b) the order of performing the functions is vendor specific;
and
4) after all initiated background functions have been completed, the device server shall
check to see if any power condition timers have expired. If any power condition timer
has expired, then the logical unit shall change to the power condition associated with
the highest priority timer that has expired;
or
b) if the logical unit is performing a background function, and a power condition timer expires,
then the logical unit shall perform all initiated background functions before the logical unit
changes to a power condition associated with a timer that has expired.
10b Maintaining low power conditions take precedence over performing background functions as
follows:
a) if the logical unit is in a low power condition, then the logical unit shall not change from that
power condition to perform a background function;
b) the device server may perform any initiated and enabled background function based on
the definitions in this standard or other command standards, if all of the following are true:
A) a condition is met to initiate a background function;
B) that background function is enabled;
C) the logical unit changes to a power condition in which the background function may be
performed (e.g., the device server processes a medium access command causing the
logical unit to change its power condition to continue processing that command); and
D) all outstanding application client requests have been completed;
or
c) if the logical unit is performing a background function, and a power condition timer expires
that causes a change to a power condition in which the logical unit is unable to continue
performing the background function, then the logical unit shall:
A) suspend the background function; and
B) change to the power condition associated with the timer that expired.
11b Reserved

630 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The behavior of the idle condition timer and standby condition timer controlled by this mode page is defined in
the power condition overview (see 5.11.1) and the power condition state machine (see 5.11.8).

If the STANDBY_Y bit is set to one, the standby_y condition timer is enabled. If the STANDBY_Y bit is set to zero,
the device server shall ignore the standby_y condition timer.

If the IDLE_C bit is set to one, the idle_c condition timer is enabled. If the IDLE_C bit is set to zero, the device
server shall ignore the idle_c condition timer.

If the IDLE_B bit is set to one, the idle_b condition timer is enabled. If the IDLE_B bit is set to zero, the device
server shall ignore the idle_b condition timer.

If the IDLE_A bit is set to one, the idle_a condition timer is enabled. If the IDLE_A bit is set to zero, the device
server shall ignore the idle_a condition timer.

If the STANDBY_Z bit is set to one, the standby_z condition timer is enabled. If the STANDBY_Z bit is set to zero,
the device server shall ignore the standby_z condition timer.

If any of the power condition enable bits (e.g., the IDLE_C bit or the STANDBY_Y bit) are set to zero and are not
changeable (see 6.13.3), then the device server does not implement the power condition timer associated
with that enable bit (see table 65 in 5.11.8.1).

The IDLE_A CONDITION TIMER field specifies the initial value, in 100 millisecond increments, for the idle_a power
condition timer (see 5.11.8.1). This value may be rounded up or down to the nearest implemented time as
described in 5.8.

The STANDBY _ Z CONDITION TIMER field specifies the initial value, in 100 millisecond increments, for the
standby_z power condition timer (see 5.11.8.1). This value may be rounded up or down to the nearest
implemented time as described in 5.8.

The IDLE_B CONDITION TIMER field specifies the initial value, in 100 millisecond increments, for the idle_b power
condition timer (see 5.11.8.1). This value may be rounded up or down to the nearest implemented time as
described in 5.8.

The IDLE_C CONDITION TIMER field specifies the initial value, in 100 millisecond increments, for the idle_c power
condition timer (see 5.11.8.1). This value may be rounded up or down to the nearest implemented time as
described in 5.8.

The STANDBY _ Y CONDITION TIMER field specifies the initial value, in 100 millisecond increments, for the
standby_y power condition timer (see 5.11.8.1). This value may be rounded up or down to the nearest
implemented time as described in 5.8.

Working Draft SCSI Primary Commands - 4 (SPC-4) 631

T10/BSR INCITS 513 Revision 37 17 May 2014

The CHECK CONDITION if from idle_c (CCF IDLE) field is defined in table 472.

Table 472 — CCF IDLE field

Code Description
00b Restricted a
01b If the transition was from an idle_c power condition, returning CHECK CONDITION status is
disabled. b
10b If the transition was from an idle_c power condition, returning CHECK CONDITION status is
enabled. b
11b Reserved
a
See SAS-2 for command processing in the Active_Wait state and Idle_Wait state.
b
For direct-access block devices see the Active_Wait state in SBC-3 for the definition of command
processing in that state. For devices that are not direct-access block devices, see the Active_Wait
state in this standard (i.e., see 5.11.8.6) for the definition of command processing in that state.

The CHECK CONDITION if from standby (CCF STANDBY) field is defined in table 473.

Table 473 — CCF STANDBY field

Code Description
00b Restricted a
01b If the transition was from a standby power condition, returning CHECK CONDITION status is
disabled. b
10b If the transition was from a standby power condition, returning CHECK CONDITION status is
enabled. b
11b Reserved
a
See SAS-2 for command processing in the Active_Wait state and Idle_Wait state.
b
For direct-access block devices see the Active_Wait state and the Idle_Wait state in SBC-3 for the
definition of command processing in those states. For devices that are not direct-access block devices,
see the Active_Wait state in this standard (i.e., see 5.11.8.6) for the definition of command processing
in that state.

632 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The CHECK CONDITION if from stopped (CCF STOPPED) field is defined in table 474.

Table 474 — CCF STOPPED field

Code Description
00b Restricted a
01b If the transition was from a stopped power condition, returning CHECK CONDITION status is
disabled. b
10b If the transition was from a stopped power condition, returning CHECK CONDITION status is
enabled. b
11b Reserved
a
See SAS-2 for command processing in the Active_Wait state and Idle_Wait state.
b
For direct-access block devices see the Active_Wait state, the Idle_Wait state description and the
Standby_Wait state in SBC-3 for the definition of command processing in those states.

7.5.14 Power Consumption mode page

The Power Consumption mode page (see table 475) provides a method to select a maximum power
consumption level while in the active power condition (see 5.11.4) based on the contents of the power
consumption descriptors in the Power Consumption VPD page (see 7.8.11) as described in 5.11.2. The mode
page policy (see 7.5.2) for this mode page shall be shared.

Table 475 — Power Consumption mode page

Bit
7 6 5 4 3 2 1 0
Byte
0 PS SPF (1b) PAGE CODE (1Ah)
1 SUBPAGE CODE (01h)
2 (MSB)
PAGE LENGTH (000Ch)
3 (LSB)
4
•• • Reserved
6
7 POWER CONSUMPTION IDENTIFIER

8
•• • Reserved
15

The PS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.5.7.

The SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field shall be set as shown in table 475 for
the Power Consumption mode page.

The POWER CONSUMPTION IDENTIFIER field specifies the power consumption identifier from one of the power
consumption descriptors in the Power Consumption VPD page (see 7.8.11) that the device server is to use as
described in 5.11.2. If none of the power consumption descriptors in the Power Consumption VPD page
contain the value in the POWER CONSUMPTION IDENTIFIER field, then the device server shall terminate the

Working Draft SCSI Primary Commands - 4 (SPC-4) 633

T10/BSR INCITS 513 Revision 37 17 May 2014

MODE SELECT command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST,
and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

7.5.15 Protocol Specific Logical Unit mode page

The Protocol Specific Logical Unit mode page (see table 476) provides protocol specific controls that are
associated with a logical unit.

During an I_T_L nexus, the Protocol Specific Logical Unit mode page controls parameters that affect both:

a) one or more target ports; and

b) the logical unit.

The parameters that may be implemented are defined in the SCSI transport protocol standard for the target
port. The mode page policy (see 7.5.2) for this mode page shall be shared or per target port and should be per
target port.

The parameters for a target port and logical unit affect their behavior regardless of which initiator port is
forming an I_T_L nexus with the target port and logical unit. If a parameter value is changed, the device server
shall establish a unit attention condition for the initiator port associated with every I_T nexus except the I_T
nexus on which the MODE SELECT command was received, with the additional sense code set to MODE
PARAMETERS CHANGED.

Table 476 — Protocol Specific Logical Unit mode page

Bit
7 6 5 4 3 2 1 0
Byte
0 PS SPF (0b) PAGE CODE (18h)
1 PAGE LENGTH (n-1)
2 Protocol specific mode parameters PROTOCOL IDENTIFIER

3
•• • Protocol specific mode parameters
n

The PS bit, SPF bit, PAGE CODE field, and PAGE LENGTH field are described in 7.5.7.

The SPF bit and PAGE CODE field shall be set as shown in table 476 for the Protocol Specific Logical Unit mode
page.

The value in the PROTOCOL IDENTIFIER field (see 7.6.1) defines the SCSI transport protocol to which the mode
page applies. For a MODE SENSE command (see 6.13), the device server shall set the PROTOCOL IDENTIFIER
field to one of the values shown in table 479 (see 7.6.1) to indicate the SCSI transport protocol used by the
target port through which the MODE SENSE command is being processed. For a MODE SELECT command
(see 6.11), the application client should set the PROTOCOL IDENTIFIER field to the same value that is returned in
a MODE SENSE command for that SCSI target port. If a device server receives a mode page containing a
transport protocol identifier value other than the one used by the target port on which the MODE SELECT
command was received, then the device server shall terminate the command with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN
PARAMETER LIST.

634 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.5.16 Protocol Specific Port mode page

The Protocol Specific Port mode page provides protocol specific controls that are associated with a SCSI port.
The page_0 mode page format (see table 477) is used if a MODE SENSE command (see 6.13.1) contains
zero in the SUBPAGE CODE field, and sub_page mode page format (see table 478) is used for subpages 01h
through FEh. See the SCSI transport protocol standard for definition of the protocol specific mode parameters.

The Protocol Specific Port mode page controls parameters that affect one or more target ports. The
parameters that may be implemented are defined in the SCSI transport protocol standard for the target port.
The mode page policy (see 7.5.2) for this mode page shall be shared or per target port. If the SCSI target
device contains more than one target port, the mode page policy should be per target port.

The parameters for a target port affect its behavior regardless of which initiator port is forming an I_T nexus
with the target port. The MLUS bit (see 7.8.9) shall be set to one in the mode page policy descriptor for this
mode page.

The parameters may be accessed by MODE SENSE (see 6.13) and MODE SELECT (see 6.11) commands
directed to any logical unit accessible through the target port. If a parameter value is changed, the device
servers for all logical units accessible through the target port shall establish a unit attention condition for the
initiator port associated with every I_T nexus except the I_T nexus on which the MODE SELECT command
was received, with the additional sense code set to MODE PARAMETERS CHANGED.

Table 477 — Page_0 mode page format Protocol Specific Port mode page

Bit
7 6 5 4 3 2 1 0
Byte
0 PS SPF (0b) PAGE CODE (19h)
1 PAGE LENGTH (n-1)
2 Protocol specific mode parameters PROTOCOL IDENTIFIER

3
•• • Protocol specific mode parameters
n

Table 478 — Sub_page mode page format Protocol Specific Port mode page

Bit
7 6 5 4 3 2 1 0
Byte
0 PS SPF (1b) PAGE CODE (19h)
1 SUBPAGE CODE

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4 Reserved
5 Protocol specific mode parameters PROTOCOL IDENTIFIER

6
•• • Protocol specific mode parameters
n

The PS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 7.5.7.

Working Draft SCSI Primary Commands - 4 (SPC-4) 635

T10/BSR INCITS 513 Revision 37 17 May 2014

The SPF bit and PAGE CODE field shall be set as shown in table 477 or table 478 for the Protocol Specific Port
mode page.

The value in the PROTOCOL IDENTIFIER field (see 7.6.1) defines the SCSI transport protocol to which the mode
page applies. For a MODE SENSE command, the device server shall set the PROTOCOL IDENTIFIER field to one
of the values shown in table 479 (see 7.6.1) to indicate the SCSI transport protocol used by the target port
through which the MODE SENSE command is being processed. For a MODE SELECT command, the
application client should set the PROTOCOL IDENTIFIER field to the same value that is returned in a MODE
SENSE command for that SCSI target port. If a device server receives a mode page containing a transport
protocol identifier value other than the one used by the target port on which the MODE SELECT command
was received, then the device server shall terminate the command with CHECK CONDITION status, with the
sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER
LIST.

636 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.6 Protocol specific parameters

7.6.1 Protocol specific parameters introduction

Some commands include protocol specific information in their command definitions. This subclause describes
those protocol specific parameters.

Protocol specific parameters may include a PROTOCOL IDENTIFIER field (see table 479) as a reference for the
SCSI transport protocol to which the protocol specific parameter applies.

Table 479 — PROTOCOL IDENTIFIER field values

Protocol Protocol
Identifier Description Standard
0h Fibre Channel Protocol for SCSI FCP-4
1h SCSI Parallel Interface SPI-5
2h Serial Storage Architecture SCSI-3 Protocol SSA-S3P
3h Serial Bus Protocol for IEEE 1394 SBP-3
4h SCSI RDMA Protocol SRP
5h Internet SCSI (iSCSI) iSCSI
6h SAS Serial SCSI Protocol SPL-3
7h Automation/Drive Interface Transport Protocol ADT-2
8h AT Attachment Interface ACS-2
9h USB Attached SCSI UAS-2
Ah SCSI over PCI Express SOP
Bh to Eh Reserved
Fh No specific protocol

7.6.2 Alias entry protocol specific designations

7.6.2.1 Introduction to alias entry protocol specific designations

The alias entry formats (see 6.2.2) used by specific SCSI transport protocols in the CHANGE ALIASES
command (see 6.2) and REPORT ALIASES command (see 6.30) are based on the SCSI transport protocol
specified in the PROTOCOL IDENTIFIER field (see 7.6.1). These alias entry formats are defined in 7.6.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 637

T10/BSR INCITS 513 Revision 37 17 May 2014

7.6.2.2 Fibre Channel specific alias entry formats

7.6.2.2.1 Summary of Fibre Channel specific alias entry formats

The alias entry formats for the Fibre Channel protocol are summarized in table 480.

Table 480 — Fibre Channel alias entry format codes

Designation
Format Length
Code Description (bytes) Reference
00h World Wide Port Name 8 7.6.2.2.2
01h World Wide Port Name 12 7.6.2.2.3
with N_Port checking
02h to FFh Reserved

7.6.2.2.2 Fibre Channel world wide port name alias entry format

The format of a Fibre Channel world wide port name alias entry is shown in table 481.

Table 481 — Fibre Channel world wide port name alias entry format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • ALIAS VALUE
7 (LSB)
8 PROTOCOL IDENTIFIER (00h)
9
Reserved
10
11 FORMAT CODE (00h)
12
Reserved
13
14 (MSB)
DESIGNATION LENGTH (0008h)
15 (LSB)
16
•• • FIBRE CHANNEL WORLD WIDE PORT NAME
23

The ALIAS VALUE field is defined in 6.2.2.

The PROTOCOL IDENTIFIER field is defined in 6.2.2 and shall be set as shown in table 481 for the Fibre Channel
world wide port name alias entry format.

The FORMAT CODE field is defined in 6.2.2 and shall be set as shown in table 481 for the Fibre Channel world
wide port name alias entry format.

638 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The DESIGNATION LENGTH field is defined in 6.2.2 and shall be set as shown in table 481 for the Fibre Channel
world wide port name alias entry format.

The FIBRE CHANNEL WORLD WIDE PORT NAME field shall contain the port world wide name defined by the port
login (PLOGI) extended link service (see FC-FS-3).

A Fibre Channel world wide port name designation is valid (see 6.2.3) if the device server has access to a
SCSI domain formed by a Fibre Channel fabric and the fabric contains a port with the specified port world
wide name.

7.6.2.2.3 Fibre Channel world wide port name with N_Port checking alias entry format

The format of a Fibre Channel world wide port name with N_Port checking alias entry IS shown in table 482.

Table 482 — Fibre Channel world wide port name with N_Port checking alias entry format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • ALIAS VALUE
7 (LSB)
8 PROTOCOL IDENTIFIER (00h)
9
Reserved
10
11 FORMAT CODE (01h)
12
Reserved
13
14 (MSB)
DESIGNATION LENGTH (000Ch)
15 (LSB)
16
•• • FIBRE CHANNEL WORLD WIDE PORT NAME
23
24 Reserved
25 (MSB)
26 N_PORT

27 (LSB)

The ALIAS VALUE field is defined in 6.2.2.

The PROTOCOL IDENTIFIER field is defined in 6.2.2 and shall be set as shown in table 482 for the Fibre Channel
world wide port name with N_Port checking alias entry format.

The FORMAT CODE field is defined in 6.2.2 and shall be set as shown in table 482 for the Fibre Channel world
wide port name with N_Port checking alias entry format.

The DESIGNATION LENGTH field is defined in 6.2.2 and shall be set as shown in table 482 for the Fibre Channel
world wide port name with N_Port checking alias entry format.

Working Draft SCSI Primary Commands - 4 (SPC-4) 639

T10/BSR INCITS 513 Revision 37 17 May 2014

The FIBRE CHANNEL WORLD WIDE PORT NAME field shall contain the port world wide name defined by the port
login (PLOGI) extended link service (see FC-FS-3).

The N_PORT field shall contain the FC-FS-3 port D_ID to be used to transport frames including PLOGI and
FCP-4 related frames.

A Fibre Channel world wide port name with N_Port checking designation is valid (see 6.2.3) if all of the
following conditions are true:

a) the device server has access to a SCSI domain formed by a Fibre Channel fabric;
b) the fabric contains a port with the specified port World Wide Name; and
c) the value in the N_PORT field is the N_Port identifier of a Fibre Channel port whose port world wide
name matches that in the FIBRE CHANNEL WORLD WIDE PORT NAME field.

7.6.2.3 RDMA specific alias entry formats

7.6.2.3.1 Summary of RDMA specific alias entry formats

The alias entry formats for the SCSI RDMA protocol are summarized in table 483.

Table 483 — RDMA alias entry format codes

Designation
Format Length
Code Description (bytes) Reference
00h Target Port Identifier 16 7.6.2.3.2
01h InfiniBand™ Global Identifier with 32 7.6.2.3.3
Target Port Identifier checking
02h to FFh Reserved

640 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.6.2.3.2 RDMA target port identifier alias entry format

The format of a SCSI RDMA target port identifier alias entry IS shown in table 484.

Table 484 — RDMA target port identifier alias entry format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • ALIAS VALUE
7 (LSB)
8 PROTOCOL IDENTIFIER (04h)
9
Reserved
10
11 FORMAT CODE (00h)
12
Reserved
13
14 (MSB)
DESIGNATION LENGTH (0010h)
15 (LSB)
16
•• • TARGET PORT IDENTIFIER
31

The ALIAS VALUE field is defined in 6.2.2.

The PROTOCOL IDENTIFIER field is defined in 6.2.2 and shall be set as shown in table 484 for the RDMA target
port identifier alias entry format.

The FORMAT CODE field is defined in 6.2.2 and shall be set as shown in table 484 for the RDMA target port
identifier alias entry format.

The DESIGNATION LENGTH field is defined in 6.2.2 and shall be set as shown in table 484 for the RDMA target
port identifier alias entry format.

The TARGET PORT IDENTIFIER field shall contain an SRP target port identifier.

A SCSI RDMA target port identifier designation is valid (see 6.2.3) if the device server has access to an SRP
SCSI domain containing the specified SRP target port identifier.

Working Draft SCSI Primary Commands - 4 (SPC-4) 641

T10/BSR INCITS 513 Revision 37 17 May 2014

7.6.2.3.3 InfiniBand global identifier with target port identifier checking alias entry format

The format of an InfiniBand global identifier with target port identifier checking alias entry is shown in table
485.

Table 485 — InfiniBand global identifier with target port identifier checking alias entry format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • ALIAS VALUE
7 (LSB)
8 PROTOCOL IDENTIFIER (04h)
9
Reserved
10
11 FORMAT CODE (01h)
12
Reserved
13
14 (MSB)
DESIGNATION LENGTH (0020h)
15 (LSB)
16
•• • INFINIBAND GLOBAL IDENTIFIER
31
32
•• • TARGET PORT IDENTIFIER
47

The ALIAS VALUE field is defined in 6.2.2.

The PROTOCOL IDENTIFIER field is defined in 6.2.2 and shall be set as shown in table 485 for the InfiniBand
global identifier with target port identifier checking alias entry format.

The FORMAT CODE field is defined in 6.2.2 and shall be set as shown in table 485 for the InfiniBand global
identifier with target port identifier checking alias entry format.

The DESIGNATION LENGTH field is defined in 6.2.2 and shall be set as shown in table 485 for the InfiniBand
global identifier with target port identifier checking alias entry format.

The INFINIBAND GLOBAL IDENTIFIER field specifies an InfiniBand global identifier (GID) of an InfiniBand port
connected to an SRP target port.

The TARGET PORT IDENTIFIER field specify an SRP target port identifier.

An InfiniBand global identifier with target port identifier checking designation is valid (see 6.2.3) if all of the
following conditions are true:

a) the device server has access to an SRP SCSI domain layered on InfiniBand;

642 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

b) the device server has access to an SRP target port based on the InfiniBand global identifier specified
in the INFINIBAND GLOBAL IDENTIFIER field; and
c) the value in the TARGET PORT IDENTIFIER field is the SRP target port identifier for the SRP target port
that is accessible via the InfiniBand global identifier contained in the INFINIBAND GLOBAL IDENTIFIER
field.

7.6.2.4 Internet SCSI specific alias entry formats

7.6.2.4.1 Summary of Internet SCSI specific alias entry formats

The alias entry formats for the iSCSI protocol are summarized in table 486.

Table 486 — iSCSI alias entry format codes

Designation
Length
Format (bytes,
Code Description maximum) Reference
00h iSCSI Name 224 7.6.2.4.2
01h iSCSI Name with binary IPv4 address 236 7.6.2.4.3
02h iSCSI Name with IPName 488 7.6.2.4.4
03h iSCSI Name with binary IPv6 address 248 7.6.2.4.5
04h to FFh Reserved

NOTE 45 - A designation that contains no IP addressing information or contains IP addressing information

that does not address the named SCSI target device may require a device server to have access to a name
server or to other discovery protocols to resolve the given iSCSI Name to an IP address through which the
device server may establish iSCSI Login. Access to such a service is protocol specific and vendor specific.

Working Draft SCSI Primary Commands - 4 (SPC-4) 643

T10/BSR INCITS 513 Revision 37 17 May 2014

7.6.2.4.2 iSCSI name alias entry format

The format of an iSCSI name alias entry IS shown in table 487.

Table 487 — iSCSI name alias entry format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • ALIAS VALUE
7 (LSB)
8 PROTOCOL IDENTIFIER (05h)
9
Reserved
10
11 FORMAT CODE (00h)
12
Reserved
13
14 (MSB)
DESIGNATION LENGTH (4m-16)
15 (LSB)
16 (MSB)
•• • ISCSI NAME
4m-1 (LSB)

The ALIAS VALUE field is defined in 6.2.2.

The PROTOCOL IDENTIFIER field is defined in 6.2.2 and shall be set as shown in table 487 for the iSCSI name
alias entry format.

The FORMAT CODE field is defined in 6.2.2 and shall be set as shown in table 487 for the iSCSI name alias
entry format.

The DESIGNATION LENGTH field is defined in 6.2.2.

The null-terminated, null-padded (see 4.3.2) ISCSI NAME field shall contain the iSCSI name of an iSCSI node
(see RFC 7143). The number of bytes in the ISCSI NAME field shall be a multiple of four.

An iSCSI name designation is valid if the device server has access to a SCSI domain containing an Internet
protocol network and that network contains an iSCSI node with the specified iSCSI name.

644 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.6.2.4.3 iSCSI name with binary IPv4 address alias entry format

The format of an iSCSI name with binary IPv4 address alias entry is shown in table 488.

Table 488 — iSCSI name with binary IPv4 address alias entry format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • ALIAS VALUE
7 (LSB)
8 PROTOCOL IDENTIFIER (05h)
9
Reserved
10
11 FORMAT CODE (01h)
12
Reserved
13
14 (MSB)
DESIGNATION LENGTH (4m+12)
15 (LSB)
16 (MSB)
•• • ISCSI NAME
4m-1 (LSB)
4m (MSB)
•• • IPV4 ADDRESS
4m+3 (LSB)
4m+4
Reserved
4m+5
4m+6 (MSB)
PORT NUMBER
4m+7 (LSB)
4m+8
Reserved
4m+9
4m+10 (MSB)
INTERNET PROTOCOL NUMBER
4m+11 (LSB)

The ALIAS VALUE field is defined in 6.2.2.

The PROTOCOL IDENTIFIER field is defined in 6.2.2 and shall be set as shown in table 488 for the iSCSI name
with binary IPv4 address alias entry format.

The FORMAT CODE field is defined in 6.2.2 and shall be set as shown in table 488 for the iSCSI name with
binary IPv4 address alias entry format.

The DESIGNATION LENGTH field is defined in 6.2.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 645

T10/BSR INCITS 513 Revision 37 17 May 2014

The null-terminated, null-padded (see 4.3.2) ISCSI NAME field shall contain the iSCSI name of an iSCSI node
(see RFC 7143). The number of bytes in the ISCSI NAME field shall be a multiple of four.

The IPV4 ADDRESS field shall contain an IPv4 address (see RFC 791).

The PORT NUMBER field shall contain a TCP port number. The TCP port number shall conform to the
requirements defined by iSCSI (see RFC 7143).

The INTERNET PROTOCOL NUMBER field shall contain an Internet protocol number. The Internet protocol number
shall conform to the requirements defined by iSCSI (see RFC 7143).

An iSCSI name designation is valid if the device server has access to a SCSI domain containing an Internet
protocol network and that network contains an iSCSI node with the specified iSCSI name.

The IPv4 address, port number, and Internet protocol number provided in the designation may be used by a
device server for addressing to discover and establish communication with the named iSCSI node.
Alternatively, the device server may use other protocol specific or vendor specific methods to discover and
establish communication with the named iSCSI node.

646 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.6.2.4.4 iSCSI name with IPname alias entry format

The format of an iSCSI name with IPname alias entry IS shown in table 489.

Table 489 — iSCSI name with IPname alias entry format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • ALIAS VALUE
7 (LSB)
8 PROTOCOL IDENTIFIER (05h)
9
Reserved
10
11 FORMAT CODE (03h)
12
Reserved
13
14 (MSB)
DESIGNATION LENGTH (4m+8)
15 (LSB)
16 (MSB)
•• • ISCSI NAME
k (LSB)
k+1 (MSB)
•• • IPNAME
n (LSB)
n+1
PAD (if any)
4m-1
4m
Reserved
4m+1
4m+2 (MSB)
PORT NUMBER
4m+3 (LSB)
4m+4
Reserved
4m+5
4m+6 (MSB)
INTERNET PROTOCOL NUMBER
4m+7 (LSB)

The ALIAS VALUE field is defined in 6.2.2.

The PROTOCOL IDENTIFIER field is defined in 6.2.2 and shall be set as shown in table 489 for the iSCSI name
with IPname alias entry format.

The FORMAT CODE field is defined in 6.2.2 and shall be set as shown in table 489 for the iSCSI name with
IPname alias entry format.

Working Draft SCSI Primary Commands - 4 (SPC-4) 647

T10/BSR INCITS 513 Revision 37 17 May 2014

The DESIGNATION LENGTH field is defined in 6.2.2.

The null-terminated (see 4.3.2) ISCSI NAME field shall contain the iSCSI name of an iSCSI node (see RFC
7143).

The null-terminated (see 4.3.2) IPNAME field shall contain a Internet protocol domain name.

The PAD field shall contain zero to three bytes set to zero such that the total length of the ISCSI NAME field,
IPNAMEfield, and PAD field is a multiple of four. Device servers shall ignore the PAD field.

The PORT NUMBER field shall contain a TCP port number. The TCP port number shall conform to the
requirements defined by iSCSI (see RFC 7143).

The INTERNET PROTOCOL NUMBER field shall contain an Internet protocol number. The Internet protocol number
shall conform to the requirements defined by iSCSI (see RFC 7143).

An iSCSI name designation is valid if the device server has access to a SCSI domain containing an Internet
protocol network and that network contains an iSCSI node with the specified iSCSI name.

The Internet protocol domain name, port number, and Internet protocol number provided in the designation
may be used by a device server for addressing to discover and establish communication with the named
iSCSI node. Alternatively, the device server may use other protocol specific or vendor specific methods to
discover and establish communication with the named iSCSI node.

648 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.6.2.4.5 iSCSI name with binary IPv6 address alias entry format

The format of an iSCSI name with binary IPv6 address alias entry IS shown in table 490.

Table 490 — iSCSI name with binary IPv6 address alias entry format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • ALIAS VALUE
7 (LSB)
8 PROTOCOL IDENTIFIER (05h)
9
Reserved
10
11 FORMAT CODE (03h)
12
Reserved
13
14 (MSB)
DESIGNATION LENGTH (4m+24)
15 (LSB)
16 (MSB)
•• • ISCSI NAME
n (LSB)
4m (MSB)
•• • IPV6 ADDRESS
4m+15 (LSB)
4m+16
Reserved
4m+17
4m+18 (MSB)
PORT NUMBER
4m+19 (LSB)
4m+20
Reserved
4m+21
4m+22 (MSB)
INTERNET PROTOCOL NUMBER
4m+23 (LSB)

The ALIAS VALUE field is defined in 6.2.2.

The PROTOCOL IDENTIFIER field is defined in 6.2.2 and shall be set as shown in table 490 for the iSCSI name
with binary IPv6 address alias entry format.

The FORMAT CODE field is defined in 6.2.2 and shall be set as shown in table 490 for the iSCSI name with
binary IPv6 address alias entry format.

The DESIGNATION LENGTH field is defined in 6.2.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 649

T10/BSR INCITS 513 Revision 37 17 May 2014

The null-terminated, null-padded (see 4.3.2) ISCSI NAME field shall contain the iSCSI name of an iSCSI node
(see RFC 7143).

The IPV6 ADDRESS field shall contain an IPv6 address (see RFC 4291).

The PORT NUMBER field shall contain a TCP port number. The TCP port number shall conform to the
requirements defined by iSCSI (see RFC 7143).

The INTERNET PROTOCOL NUMBER field shall contain an Internet protocol number. The Internet protocol number
shall conform to the requirements defined by iSCSI (see RFC 7143).

An iSCSI name designation is valid if the device server has access to a SCSI domain containing an Internet
protocol network and that network contains an iSCSI node with the specified iSCSI name.

The IPv6 address, port number and Internet protocol number provided in the designation may be used by a
device server for addressing to discover and establish communication with the named iSCSI node.
Alternatively, the device server may use other protocol specific or vendor specific methods to discover and
establish communication with the named iSCSI node.

650 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.6.3 EXTENDED COPY protocol specific CSCD descriptors

7.6.3.1 Introduction to EXTENDED COPY protocol specific CSCD descriptors

The protocol-specific CSCD descriptors (see 6.4.5.1) in the parameter list (see 5.16.7.1) of the EXTENDED
COPY(LID4) command (see 6.4) and the EXTENDED COPY(LID1) command (see 6.5) are described in
7.6.3.

7.6.3.2 Fibre Channel N_Port_Name CSCD descriptor format

The CSCD descriptor format shown in table 491 is used by an EXTENDED COPY command to specify an
FCP CSCD using its Fibre Channel N_Port_Name.

Table 491 — Fibre Channel N_Port_Name CSCD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (E0h)
1 LU ID TYPE Obsolete PERIPHERAL DEVICE TYPE

2 (MSB)
RELATIVE INITIATOR PORT IDENTIFIER
3 (LSB)
4
•• • LU IDENTIFIER
11
12
•• • N_PORT_NAME
19
20
•• • Reserved
27
28
•• • Device type specific parameters
31

The DESCRIPTOR TYPE CODE field, LU ID TYPE field, PERIPHERAL DEVICE TYPE field, RELATIVE INITIATOR PORT
IDENTIFIER field, LU IDENTIFIER field, and the device type specific parameters are described in 6.4.5.1. The
DESCRIPTOR TYPE CODE field shall be set as shown in table 491 for the Fibre Channel N_Port_Name CSCD
descriptor.

The N_PORT_NAME field shall contain the N_Port_Name defined by the port login (PLOGI) extended link
service (see FC-LS-2).

NOTE 46 - The Fibre Channel N_Port_Name CSCD descriptor format requests that the copy manager
translate the N_Port_Name to an N_Port_ID (see FC-FS-3, FC-LS-2, and 7.6.3.3).

Working Draft SCSI Primary Commands - 4 (SPC-4) 651

T10/BSR INCITS 513 Revision 37 17 May 2014

7.6.3.3 Fibre Channel N_Port_ID CSCD descriptor format

The CSCD descriptor format shown in table 492 is used by an EXTENDED COPY command to specify an
FCP CSCD using its Fibre Channel N_Port_ID.

Table 492 — Fibre Channel N_Port_ID CSCD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (E1h)
1 LU ID TYPE Obsolete PERIPHERAL DEVICE TYPE

2 (MSB)
RELATIVE INITIATOR PORT IDENTIFIER
3 (LSB)
4
•• • LU IDENTIFIER
11
12
•• • Reserved
20
21 (MSB)
•• • N_PORT_ID
23 (LSB)
24
•• • Reserved
27
28
•• • Device type specific parameters
31

The DESCRIPTOR TYPE CODE field, LU ID TYPE field, PERIPHERAL DEVICE TYPE field, RELATIVE INITIATOR PORT
IDENTIFIER field, LU IDENTIFIER field, and the device type specific parameters are described in 6.4.5.1. The
DESCRIPTOR TYPE CODE field shall be set as shown in table 492 for the Fibre Channel N_Port_ID CSCD
descriptor.

The N_PORT_ID field shall contain the port D_ID (see FC-FS-3) to be used to transport frames including PLOGI
(see FC-LS-2) and FCP-4 related frames.

NOTE 47 - Use of N_Port_ID addressing restricts this CSCD descriptor format to a single Fibre Channel
fabric.

652 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.6.3.4 Fibre Channel N_Port_ID With N_Port_Name Checking CSCD descriptor format

The CSCD descriptor format shown in table 493 is used by an EXTENDED COPY command to specify an
FCP CSCD using its Fibre Channel N_Port_ID and to require the copy manager to verify that the
N_Port_Name of the specified N_Port matches the value in the CSCD descriptor.

Table 493 — Fibre Channel N_Port_ID With N_Port_Name Checking CSCD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (E2h)
1 LU ID TYPE Obsolete PERIPHERAL DEVICE TYPE

2 (MSB)
RELATIVE INITIATOR PORT IDENTIFIER
3 (LSB)
4
•• • LU IDENTIFIER
11
12
•• • N_PORT_NAME
19
20 Reserved
21 (MSB)
•• • N_PORT_ID
23 (LSB)
24
•• • Reserved
27
28
•• • Device type specific parameters
31

The DESCRIPTOR TYPE CODE field, LU ID TYPE field, PERIPHERAL DEVICE TYPE field, RELATIVE INITIATOR PORT
field, LU IDENTIFIER field, and the device type specific parameters are described in 6.4.5.1. The
IDENTIFIER
DESCRIPTOR TYPE CODE field shall be set as shown in table 493 for the Fibre Channel N_Port_ID With
N_Port_Name Checking CSCD descriptor.

The N_PORT_NAME field shall contain the N_Port_Name defined by the port login (PLOGI) extended link
service (see FC-FS-3 and FC-LS-2).

The N_PORT_ID field shall contain the port D_ID (see FC-FS-3) to be used to transport frames including PLOGI
(see FC-LS-2) and FCP-4 related frames.

NOTE 48 - Use of N_Port addressing restricts this CSCD descriptor format to a single fabric.

If the copy manager first processes a segment descriptor that references this type of CSCD descriptor, the
copy manager shall confirm that the D_ID in the N_PORT_ID field is associated with the N_Port_Name in the
N _ PORT _ NAME field. If the confirmation fails, the copy manager shall terminate the copy operation (see
5.16.4.3) because the CSCD is unreachable (see 5.16.7.4). The copy manager processing this CSCD

Working Draft SCSI Primary Commands - 4 (SPC-4) 653

T10/BSR INCITS 513 Revision 37 17 May 2014

descriptor shall track configuration changes that affect the D_ID value for the duration of the copy operation
(see 5.16.4.3). An application client is responsible for tracking configuration changes between commands.

7.6.3.5 SCSI Parallel T_L CSCD descriptor format

The CSCD descriptor format shown in table 494 is used by an EXTENDED COPY command to specify a SPI
CSCD using one of its target port identifiers (see SAM-5).

Table 494 — SCSI Parallel T_L CSCD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (E3h)
1 LU ID TYPE Obsolete PERIPHERAL DEVICE TYPE

2 (MSB)
RELATIVE INITIATOR PORT IDENTIFIER
3 (LSB)
4
•• • LU IDENTIFIER
11
12 Vendor specific
13 TARGET IDENTIFIER

14
•• • Reserved
27
28
•• • Device type specific parameters
31

The DESCRIPTOR TYPE CODE field, LU ID TYPE field, PERIPHERAL DEVICE TYPE field, RELATIVE INITIATOR PORT
field, LU IDENTIFIER field, and the device type specific parameters are described in 6.4.5.1. The
IDENTIFIER
DESCRIPTOR TYPE CODE field shall be set as shown in table 494 for the SCSI Parallel T_L CSCD descriptor.

The TARGET IDENTIFIER field specifies the SCSI target identifier (see SPI-5).

654 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.6.3.6 IEEE 1394 EUI-64 CSCD descriptor format

The CSCD descriptor format shown in table 495 is used by an EXTENDED COPY command to specify an
SBP-3 CSCD using its IEEE 1394 Extended Unique Identifier, 64-bits (EUI-64) and configuration ROM
directory identifier.

Table 495 — IEEE 1394 EUI-64 CSCD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (E8h)
1 LU ID TYPE Obsolete PERIPHERAL DEVICE TYPE

2 (MSB)
RELATIVE INITIATOR PORT IDENTIFIER
3 (LSB)
4
•• • LU IDENTIFIER
11
12
•• • EUI-64
19
20
•• • DIRECTORY ID
22
23
•• • Reserved
27
28
•• • Device type specific parameters
31

The DESCRIPTOR TYPE CODE field, LU ID TYPE field, PERIPHERAL DEVICE TYPE field, RELATIVE INITIATOR PORT
field, LU IDENTIFIER field, and the device type specific parameters are described in 6.4.5.1. The
IDENTIFIER
DESCRIPTOR TYPE CODE field shall be set as shown in table 495 for the IEEE 1394 EUI-64 CSCD descriptor.

The EUI-64 field shall contain the SBP-3 node’s unique identifier (EUI-64) obtained from the configuration
ROM bus information block, as specified by ANSI IEEE 1394a:2000.

NOTE 49 - ANSI IEEE 1394a-2000 separately labels the components of the EUI-64 as NODE_VENDOR_ID,
CHIP_ID_HI and CHIP_ID_LO. Collectively these form the node’s EUI-64.

The DIRECTORY ID field shall contain the CSCD’s directory identifier, as specified by ISO/IEC 13213:1994.

Working Draft SCSI Primary Commands - 4 (SPC-4) 655

T10/BSR INCITS 513 Revision 37 17 May 2014

7.6.3.7 RDMA CSCD descriptor format

The CSCD descriptor format shown in table 496 is used by an EXTENDED COPY command to specify an
SRP CSCD using its RDMA SRP target port identifier.

Table 496 — RDMA CSCD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (E7h)
1 LU ID TYPE Obsolete PERIPHERAL DEVICE TYPE

2 (MSB)
RELATIVE INITIATOR PORT IDENTIFIER
3 (LSB)
4
•• • LU IDENTIFIER
11
12
•• • TARGET PORT IDENTIFIER
27
28
•• • Device type specific parameters
31

The DESCRIPTOR TYPE CODE field, LU ID TYPE field, PERIPHERAL DEVICE TYPE field, RELATIVE INITIATOR PORT
field, LU IDENTIFIER field, and the device type specific parameters are described in 6.4.5.1. The
IDENTIFIER
DESCRIPTOR TYPE CODE field shall be set as shown in table 496 for the RDMA CSCD descriptor.

The TARGET PORT IDENTIFIER field specifies the SRP target port identifier (see SRP).

656 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.6.3.8 iSCSI IPv4 CSCD descriptor format

The CSCD descriptor format shown in table 497 is used by an EXTENDED COPY command to specify an
iSCSI CSCD using its binary IPv4 address.

Table 497 — iSCSI IPv4 CSCD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (E5h)
1 LU ID TYPE Obsolete PERIPHERAL DEVICE TYPE

2 (MSB)
RELATIVE INITIATOR PORT IDENTIFIER
3 (LSB)
4
•• • LU IDENTIFIER
11
12 (MSB)
•• • IPV4 ADDRESS
15 (LSB)
16
•• • Reserved
21
22 (MSB)
PORT NUMBER
23 (LSB)
24
Reserved
25
26 (MSB)
INTERNET PROTOCOL NUMBER
27 (LSB)
28
•• • Device type specific parameters
31

The DESCRIPTOR TYPE CODE field, LU ID TYPE field, PERIPHERAL DEVICE TYPE field, RELATIVE INITIATOR PORT
field, LU IDENTIFIER field, and the device type specific parameters are described in 6.4.5.1. The
IDENTIFIER
DESCRIPTOR TYPE CODE field shall be set as shown in table 497 for the iSCSI IPv4 CSCD descriptor.

The IPV4 ADDRESS field shall contain an IPv4 address (see RFC 791).

The PORT NUMBER field shall contain the TCP port number. The TCP port number shall conform to the
requirements defined by iSCSI (see RFC 7143).

The INTERNET PROTOCOL NUMBER field shall contain an Internet protocol number. The Internet protocol number
shall conform to the requirements defined by iSCSI (see RFC 7143).

NOTE 50 - The internet protocol number for TCP is 0006h.

Working Draft SCSI Primary Commands - 4 (SPC-4) 657

T10/BSR INCITS 513 Revision 37 17 May 2014

7.6.3.9 iSCSI IPv6 CSCD descriptor format

The CSCD descriptor format shown in table 498 is used by an EXTENDED COPY command to specify an
iSCSI CSCD using its binary IPv6 address.

Table 498 — iSCSI IPv6 CSCD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (EAh)
1 LU ID TYPE Obsolete PERIPHERAL DEVICE TYPE

2 (MSB)
RELATIVE INITIATOR PORT IDENTIFIER
3 (LSB)
4
•• • LU IDENTIFIER
11
12 (MSB)
•• • IPV6 ADDRESS
27 (LSB)
28
•• • Device type specific parameters
31
32 EXTENSION DESCRIPTOR TYPE CODE (FFh)
33
34 Reserved
35
36 (MSB)
PORT NUMBER
37 (LSB)
38 (MSB)
INTERNET PROTOCOL NUMBER
39 (LSB)
40
•• • Reserved
63

The DESCRIPTOR TYPE CODE field, LU ID TYPE field, PERIPHERAL DEVICE TYPE field, RELATIVE INITIATOR PORT
field, LU IDENTIFIER field, and the device type specific parameters are described in 6.4.5.1. The
IDENTIFIER
DESCRIPTOR TYPE CODE field shall be set as shown in table 498 for the iSCSI IPv6 CSCD descriptor.

The IPV6 ADDRESS field shall contain a unicast IPv6 address (see RFC 4291).

The EXTENSION DESCRIPTOR TYPE CODE field is described in 6.4.5.2. If the EXTENSION DESCRIPTOR TYPE CODE
field does not contain the value shown in table 498, then the copy manager shall terminate the copy operation
(see 5.16.4.3) with CHECK CONDITION status, with the sense key set to COPY ABORTED, and the
additional sense code set to INVALID FIELD IN PARAMETER LIST.

658 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The PORT NUMBER field shall contain the TCP port number. The TCP port number shall conform to the
requirements defined by iSCSI (see RFC 7143).

The INTERNET PROTOCOL NUMBER field shall contain an Internet protocol number. The Internet protocol number
shall conform to the requirements defined by iSCSI (see RFC 7143).

NOTE 51 - The internet protocol number for TCP is 0006h.

7.6.3.10 SAS Serial SCSI Protocol CSCD descriptor format

The CSCD descriptor format shown in table 499 is used by an EXTENDED COPY command to specify a SAS
CSCD using its SAS address.

Table 499 — SAS Serial SCSI Protocol CSCD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR TYPE CODE (E9h)
1 LU ID TYPE Obsolete PERIPHERAL DEVICE TYPE

2 (MSB)
RELATIVE INITIATOR PORT IDENTIFIER
3 (LSB)
4
•• • LU IDENTIFIER
11
12
•• • SAS ADDRESS
19
20
•• • Reserved
27
28
•• • Device type specific parameters
31

The DESCRIPTOR TYPE CODE field, LU ID TYPE field, PERIPHERAL DEVICE TYPE field, RELATIVE INITIATOR PORT
IDENTIFIER field, LU IDENTIFIER field, and the device type specific parameters are described in 6.4.5.1. The
DESCRIPTOR TYPE CODE field shall be set as shown in table 499 for the SAS Serial SCSI Protocol CSCD
descriptor.

The SAS ADDRESS field specifies the SAS address (see SPL-3).

7.6.4 TransportID identifiers

7.6.4.1 Overview of TransportID identifiers

An application client may use a TransportID to specify an initiator port other than the initiator port that is
transporting the command and parameter data (e.g., as an Access identifiers (see 8.3.1.3.2) in ACL ACEs, as
the initiator port in the I_T nexus to which PERSISTENT RESERVE OUT command with REGISTER AND

Working Draft SCSI Primary Commands - 4 (SPC-4) 659

T10/BSR INCITS 513 Revision 37 17 May 2014

MOVE service action (see 5.12.8) is moving a persistent reservation).

TransportIDs (see table 500) shall be at least 24 bytes long and shall be a multiple of four bytes in length.

Table 500 — TransportID format

Bit
7 6 5 4 3 2 1 0
Byte
0 TPID FORMAT Reserved PROTOCOL IDENTIFIER

1
•• • SCSI transport protocol specific data
n

The TransportID format (TPID FORMAT) field specifies the format of the TransportID. All TransportID format
codes not defined in this standard (i.e., in 7.6.4) are reserved.

The PROTOCOL IDENTIFIER field (see table 479 in 7.6.1) specifies the SCSI transport protocol to which the
TransportID applies.

The format of the SCSI transport protocol specific data depends on the value in the PROTOCOL IDENTIFIER field.
The SCSI transport protocol specific data in a TransportID shall only include initiator port identifiers, initiator
port names, or SCSI device names (see SAM-5) that persist across hard resets and I_T nexus losses.
TransportID formats specific to SCSI transport protocols are listed in table 501.

Table 501 — TransportID formats for specific SCSI transport protocols

Protocol
SCSI transport protocol standard Reference
Fibre Channel Protocol (FCP) FCP-4 7.6.4.2
SCSI Parallel Interface (SPI) SPI-5 7.6.4.3
Serial Bus Protocol (SBP) (i.e., IEEE 1394) SBP-3 7.6.4.4
Remote Direct Memory Access (RDMA) (e.g., InfiniBand™) SRP 7.6.4.5
Internet SCSI (iSCSI) iSCSI 7.6.4.6
Serial Attached SCSI (SAS) Serial SCSI Protocol (SSP) SPL-3 7.6.4.7
SCSI over PCI Express (SOP) SOP 7.6.4.8

660 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.6.4.2 TransportID for initiator ports using SCSI over Fibre Channel

A Fibre Channel TransportID (see table 502) specifies an FCP-4 initiator port based on the N_Port_Name
belonging to that initiator port.

Table 502 — Fibre Channel TransportID format

Bit
7 6 5 4 3 2 1 0
Byte
0 TPID FORMAT (00b) Reserved PROTOCOL IDENTIFIER (0h)
1
•• • Reserved
7
8
•• • N_PORT_NAME
15
16
•• • Reserved
23

The TPID FORMAT field and PROTOCOL IDENTIFIER field are defined in 7.6.4.1, and shall be set as shown in table
502 for the Fibre Channel TransportID format.

The N_PORT_NAME field shall contain the N_Port_Name defined by the N_Port login (PLOGI) extended link
service (see FC-FS-3).

Working Draft SCSI Primary Commands - 4 (SPC-4) 661

T10/BSR INCITS 513 Revision 37 17 May 2014

7.6.4.3 TransportID for initiator ports using a parallel SCSI bus

A parallel SCSI bus TransportID (see table 503) specifies a SPI-5 initiator port based on the SCSI address of
an initiator port and the relative port identifier of the target port through which the application client accesses
the SCSI target device.

Table 503 — Parallel SCSI bus TransportID format

Bit
7 6 5 4 3 2 1 0
Byte
0 TPID FORMAT (00b) Reserved PROTOCOL IDENTIFIER (1h)
1 Reserved
2 (MSB)
SCSI ADDRESS
3 (LSB)
4
Obsolete
5
6 (MSB)
RELATIVE TARGET PORT IDENTIFIER
7 (LSB)
8
•• • Reserved
23

The TPID FORMAT field and PROTOCOL IDENTIFIER field are defined in 7.6.4.1, and shall be set as shown in table
503 for the Parallel SCSI bus TransportID format.

The SCSI ADDRESS field specifies the SCSI address (see SPI-5) of the initiator port.

The RELATIVE TARGET PORT IDENTIFIER field (see 4.3.4) specifies the relative port identifier of the target port for
which the initiator port SCSI address applies. If the RELATIVE TARGET PORT IDENTIFIER does not reference a
target port in the SCSI target device, the TransportID is invalid.

662 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.6.4.4 TransportID for initiator ports using SCSI over IEEE 1394

An IEEE 1394 TransportID (see table 504) specifies an SBP-3 initiator port based on the EUI-64 initiator port
name belonging to that initiator port.

Table 504 — IEEE 1394 TransportID format

Bit
7 6 5 4 3 2 1 0
Byte
0 TPID FORMAT (00b) Reserved PROTOCOL IDENTIFIER (3h)
1
•• • Reserved
7
8
•• • EUI-64 NAME
15
16
•• • Reserved
23

The TPID FORMAT field and PROTOCOL IDENTIFIER field are defined in 7.6.4.1, and shall be set as shown in table
504 for the IEEE 1394 TransportID format.

The EUI-64 NAME field shall contain the EUI-64 IEEE 1394 node unique identifier (see SBP-3) for an initiator
port.

7.6.4.5 TransportID for initiator ports using SCSI over an RDMA interface

A RDMA TransportID (see table 505) specifies an SRP initiator port based on the world wide unique initiator
port name belonging to that initiator port.

Table 505 — RDMA TransportID format

Bit
7 6 5 4 3 2 1 0
Byte
0 TPID FORMAT (00b) Reserved PROTOCOL IDENTIFIER (4h)
1
•• • Reserved
7
8
•• • INITIATOR PORT IDENTIFIER
23

The TPID FORMAT field and PROTOCOL IDENTIFIER field are defined in 7.6.4.1, and shall be set as shown in table
505 for the RDMA TransportID format.

The INITIATOR PORT IDENTIFIER field shall contain an SRP initiator port identifier (see SRP).

Working Draft SCSI Primary Commands - 4 (SPC-4) 663

T10/BSR INCITS 513 Revision 37 17 May 2014

7.6.4.6 TransportID for initiator ports using SCSI over iSCSI

An iSCSI TransportID specifies an iSCSI initiator port using one of the TransportID formats listed in table 506.

Table 506 — iSCSI TPID FORMAT field codes

Code Description Reference

00b Initiator port is identified using the world wide unique SCSI device name of table 507
the iSCSI initiator device containing the initiator port.
01b Initiator port is identified using the world wide unique initiator port identifier. table 508
10b to 11b Reserved

iSCSI TransportIDs with the TPID FORMAT field set to 01b should be processed. iSCSI TransportIDs with the
TPID FORMAT field set to 00b may result in the command being terminated.

A iSCSI TransportID with the TPID FORMAT field set to 00b (see table 507) specifies an iSCSI initiator port
based on the world wide unique SCSI device name of the iSCSI initiator device containing the initiator port.

Table 507 — iSCSI initiator device TransportID format

Bit
7 6 5 4 3 2 1 0
Byte
0 TPID FORMAT (00b) Reserved PROTOCOL IDENTIFIER (5h)
1 Reserved
2 (MSB)
ADDITIONAL LENGTH (m-3)
3 (LSB)
4 (MSB)
•• • ISCSI NAME
m (LSB)

The TPID FORMAT field and PROTOCOL IDENTIFIER field are defined in 7.6.4.1, and shall be set as shown in table
507 for the iSCSI initiator device TransportID format.

The ADDITIONAL LENGTH field specifies the number of bytes that follow in the TransportID. The additional length
shall be at least 20 and shall be a multiple of four.

The null-terminated, null-padded (see 4.3.2) ISCSI NAME field shall contain the iSCSI name of an iSCSI initiator
node (see RFC 7143). The first ISCSI NAME field byte containing an ASCII null character terminates the ISCSI
NAME field without regard for the specified length of the iSCSI TransportID or the contents of the ADDITIONAL
LENGTH field.

The iSCSI name length does not exceed 223 bytes. The maximum length of the iSCSI TransportID is 228
bytes.

If a iSCSI TransportID with the TPID FORMAT field set to 00b appears in a PERSISTENT RESERVE OUT
parameter list (see 6.16.3), then all initiator ports known to the device server with an iSCSI node name
matching the one in the TransportID shall be registered.

If a iSCSI TransportID with the TPID FORMAT field set to 00b appears in an ACE access identifier (see
8.3.1.3.2), the logical units listed in the ACE shall be accessible to any initiator port with an iSCSI node name

664 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

matching the value in the TransportID. The access controls coordinator shall reject any command that
attempts to define more than one ACE with an iSCSI TransportID access identifier containing the same iSCSI
name. The access controls coordinator shall terminate the command with CHECK CONDITION status, with
the sense key ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER
LIST.

A iSCSI TransportID with the TPID FORMAT field set to 01b (see table 508) specifies an iSCSI initiator port
based on its world wide unique initiator port identifier.

Table 508 — iSCSI initiator port TransportID format

Bit
7 6 5 4 3 2 1 0
Byte
0 TPID FORMAT (01b) Reserved PROTOCOL IDENTIFIER (5h)
1 Reserved
2 (MSB)
ADDITIONAL LENGTH (m-3)
3 (LSB)
4 (MSB)
•• • ISCSI NAME
n-1 (LSB)
n (MSB)
•• • SEPARATOR (2C 692C 3078h)
n+4 (LSB)
n+5 (MSB)
•• • ISCSI INITIATOR SESSION ID
m (LSB)

The TPID FORMAT field and PROTOCOL IDENTIFIER field are defined in 7.6.4.1, and shall be set as shown in table
508 for the iSCSI initiator port TransportID format.

The ADDITIONAL LENGTH field specifies the number of bytes that follow in the TransportID encompassing the
ISCSI NAME, SEPARATOR, and ISCSI INITIATOR SESSION ID fields. The additional length shall be at least 20 and
shall be a multiple of four.

The ISCSI NAME field shall contain the iSCSI name of an iSCSI initiator node (see RFC 7143). The ISCSI NAME
field shall not be null-terminated (see 4.3.2) and shall not be padded.

The SEPARATOR field shall be set as shown in table 508 (i.e., the five ASCII characters ‘,i,0x’).

The null-terminated, null-padded ISCSI INITIATOR SESSION ID field shall contain the iSCSI initiator session
identifier (see RFC 7143) in the form of ASCII characters that are the hexadecimal digits converted from the
binary iSCSI initiator session identifier value. The first ISCSI INITIATOR SESSION ID field byte containing an ASCII
null character terminates the ISCSI INITIATOR SESSION ID field without regard for the specified length of the
iSCSI TransportID or the contents of the ADDITIONAL LENGTH field.

Working Draft SCSI Primary Commands - 4 (SPC-4) 665

T10/BSR INCITS 513 Revision 37 17 May 2014

7.6.4.7 TransportID for initiator ports using SCSI over SAS Serial SCSI Protocol

A SAS Serial SCSI Protocol (SSP) TransportID (see table 509) specifies a SAS initiator port that is
communicating via SSP using the SAS address belonging to that initiator port.

Table 509 — SAS Serial SCSI Protocol TransportID format

Bit
7 6 5 4 3 2 1 0
Byte
0 TPID FORMAT (00b) Reserved PROTOCOL IDENTIFIER (6h)
1
•• • Reserved
3
4
•• • SAS ADDRESS
11
12
•• • Reserved
23

The TPID FORMAT field and PROTOCOL IDENTIFIER field are defined in 7.6.4.1, and shall be set as shown in table
509 for the SAS Serial SCSI Protocol TransportID format.

The SAS ADDRESS field specifies the SAS address of the SCSI initiator port (see SPL-3).

7.6.4.8 TransportID for initiator ports using SCSI over PCI Express

A SCSI over PCI Express (SOP) TransportID (see table 510) specifies a SOP initiator port.

Table 510 — SOP TransportID format

Bit
7 6 5 4 3 2 1 0
Byte
0 TPID FORMAT (00b) Reserved PROTOCOL IDENTIFIER (Ah)
1 Reserved
2
ROUTING ID
3
4
•• • Reserved
23

The TPID FORMAT field and PROTOCOL IDENTIFIER field are defined in 7.6.4.1, and shall be set as shown in table
510 for the SOP TransportID format.

The ROUTING ID field shall contain a PCI Express routing ID (see SOP).

666 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7 Security protocol parameters

7.7.1 Security protocol information description

7.7.1.1 Overview

The security protocol information security protocol (i.e., the SECURITY PROTOCOL field set to 00h in a
SECURITY PROTOCOL IN command) returns security protocol related information. A SECURITY
PROTOCOL IN command in which the SECURITY PROTOCOL field is set to 00h is not associated with an
previous SECURITY PROTOCOL OUT command and shall be processed without regard for whether a
SECURITY PROTOCOL OUT command has been processed.

If the SECURITY PROTOCOL IN command is supported, the SECURITY PROTOCOL field set to 00h shall be
supported as defined in this standard.

7.7.1.2 CDB description

If the SECURITY PROTOCOL field is set to 00h in a SECURITY PROTOCOL IN command, the contents of the
SECURITY PROTOCOL SPECIFIC field are defined in table 511.

Table 511 — SECURITY PROTOCOL SPECIFIC field for SECURITY PROTOCOL IN protocol 00h

Code Description Support Reference

0000h Supported security protocol list Mandatory 7.7.1.3
0001h Certificate data Mandatory 7.7.1.4
0002h Security compliance information Optional 7.7.1.5
all others Reserved

All other CDB fields for SECURITY PROTOCOL IN command shall meet the requirements stated in 6.40.

Each time a SECURITY PROTOCOL IN command with the SECURITY PROTOCOL field set to 00h is received,
the device server shall transfer the data defined in 7.7.1 starting with byte 0.

Working Draft SCSI Primary Commands - 4 (SPC-4) 667

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.1.3 Supported security protocols list description

If the SECURITY PROTOCOL field is set to 00h and the SECURITY PROTOCOL SPECIFIC field is set to 0000h in a
SECURITY PROTOCOL IN command, then the parameter data shall have the format shown in table 512.

Table 512 — Supported security protocols SECURITY PROTOCOL IN parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • Reserved
5
6 (MSB) SUPPORTED SECURITY PROTOCOL LIST LENGTH
7 (m-7) (LSB)
Supported security protocol list
8 SUPPORTED SECURITY PROTOCOL (00h) [first]
•
••

m SUPPORTED SECURITY PROTOCOL [last]

m+1
•• • Pad bytes (if any)
n

The SUPPORTED SECURITY PROTOCOL LIST LENGTH field indicates the total length, in bytes, of the supported
security protocol list that follows.

Each SUPPORTED SECURITY PROTOCOL field in the supported security protocols list shall contain one of the
security protocol values (see table 317 in 6.40 and table 319 in 6.41) supported by the logical unit. The values
shall be listed in ascending order starting with 00h.

The total data length shall conform to the ALLOCATION LENGTH field requirements (see 6.40). Pad bytes may be
appended to meet this length. Pad bytes shall have a value of 00h.

668 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7.1.4 Certificate data description

7.7.1.4.1 Certificate overview

A certificate is either an X.509 Public Key Certificate (see 7.7.1.4.2) or an X.509 Attribute Certificate (see
7.7.1.4.3) depending on the capabilities of the logical unit.

If the SECURITY PROTOCOL field is set to 00h and the SECURITY PROTOCOL SPECIFIC field is set to 0001h in a
SECURITY PROTOCOL IN command, then the parameter data shall have the format shown in table 513.

Table 513 — Certificate data SECURITY PROTOCOL IN parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0
Reserved
1
2 (MSB)
CERTIFICATE LENGTH (m-3)
3 (LSB)
4
•• • CERTIFICATE
m
m+1
•• • Pad bytes (if any)
n

The CERTIFICATE LENGTH field indicates the total length, in bytes, of the certificate or certificates that follow.
The length may include more than one certificate. If the device server doesn’t have a certificate to transfer, the
CERTIFICATE LENGTH field shall be set to 0000h.

The contents of the CERTIFICATE field are defined in 7.7.1.4.2 and 7.7.1.4.3.

The total data length shall conform to the ALLOCATION LENGTH field requirements (see 6.40). Pad bytes may be
appended to meet this length. Pad bytes shall have a value of 00h.

7.7.1.4.2 Public Key certificate description

RFC 5280 defines the certificate syntax for certificates consistent with X.509v3 Public Key Certificate
Specification.

7.7.1.4.3 Attribute certificate description

RFC 3281 defines the certificate syntax for certificates consistent with X.509v2 Attribute Certificate
Specification.

Working Draft SCSI Primary Commands - 4 (SPC-4) 669

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.1.5 Security compliance information description

7.7.1.5.1 Security compliance information overview

The security compliance information parameter data contains information about security standards that apply
to this SCSI target device.

If the SECURITY PROTOCOL field is set to 00h and the SECURITY PROTOCOL SPECIFIC field is set to 0002h in a
SECURITY PROTOCOL IN command, then the parameter data shall have the format shown in table 514.

Table 514 — Security compliance information SECURITY PROTOCOL IN parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • SECURITY COMPLIANCE INFORMATION LENGTH (m-3)
3 (LSB)
Compliance descriptors
4
•• • Compliance descriptor [first]

•
••

•• • Compliance descriptor [last]

n
m+1
•• • Pad bytes (if any)
n

The SECURITY COMPLIANCE INFORMATION LENGTH field indicates the total length, in bytes, of the compliance
descriptors that follow.

Each compliance descriptor (see 7.7.1.5.2) contains information about a security standard that applies to this
SCSI target device. Compliance descriptors may be returned in any order.

The total data length shall conform to the ALLOCATION LENGTH field requirements (see 6.40). Pad bytes may be
appended to meet this length. Pad bytes shall have a value of 00h.

670 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7.1.5.2 Compliance descriptor overview

The format of a compliance descriptor in the security compliance information SECURITY PROTOCOL IN
parameter data is shown in table 515.

Table 515 — Compliance descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
COMPLIANCE DESCRIPTOR TYPE
1 (LSB)
2
Reserved
3
4 (MSB)
•• • COMPLIANCE DESCRIPTOR LENGTH (n-3)
7 (LSB)
8
•• • Descriptor specific information
n

The COMPLIANCE DESCRIPTOR TYPE field (see table 516) indicates the format of the descriptor specific
information. The security compliance information SECURITY PROTOCOL IN parameter data may contain
more than one compliance descriptor with the same value in the COMPLIANCE DESCRIPTOR TYPE field.

Table 516 — COMPLIANCE DESCRIPTOR TYPE field

Related
Code Description standards Reference
0001h Security requirements for cryptographic modules FIPS 140-2 7.7.1.5.3
FIPS 140-3
all others Reserved

The COMPLIANCE DESCRIPTOR LENGTH field indicates the number of bytes that follow in the compliance
descriptor.

The contents of the descriptor specific information depend on the value in the COMPLIANCE DESCRIPTOR TYPE
field.

Working Draft SCSI Primary Commands - 4 (SPC-4) 671

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.1.5.3 FIPS 140 compliance descriptor

The FIPS 140 compliance descriptor (see table 517) contains information that may be used to locate
information about a FIPS 140 certificate associated with the SCSI target device. The SCSI target device may
or may not be operating in the mode specified by that certificate.

Table 517 — FIPS 140 compliance descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
COMPLIANCE DESCRIPTOR TYPE (0001h)
1 (LSB)
2
Reserved
3
4 (MSB)
•• • COMPLIANCE DESCRIPTOR LENGTH (0000 0208h)
7 (LSB)
8 RELATED STANDARD

9 OVERALL SECURITY LEVEL

10
•• • Reserved
15
16 (MSB)
•• • COMPLIANCE DESCRIPTOR HARDWARE VERSION
143 (LSB)
144 (MSB)
•• • COMPLIANCE DESCRIPTOR VERSION
271 (LSB)
272 (MSB)
•• • COMPLIANCE DESCRIPTOR MODULE NAME
527 (LSB)

The COMPLIANCE DESCRIPTOR TYPE field and COMPLIANCE DESCRIPTOR LENGTH field are defined in 7.7.1.5.2 and
shall be set as shown in table 517 for the FIPS 140 compliance descriptor.

The RELATED STANDARD field (see table 518) is an ASCII data field (see 4.3.1) that indicates the related
standard described by this compliance descriptor.

Table 518 — RELATED STANDARD field

Code Related standard

32h FIPS 140-2
33h FIPS 140-3
all others Reserved

The OVERALL SECURITY LEVEL field is an ASCII data field (see 4.3.1) that indicates the FIPS 140 overall
security level that is reported by NIST or CSEC.

672 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The COMPLIANCE DESCRIPTOR HARDWARE VERSION field is null terminated, null padded data (see 4.3.2) that
indicates the version number of the hardware in the module, as reported by NIST or CSEC.

The COMPLIANCE DESCRIPTOR VERSION field is null terminated, null padded data (see 4.3.2) that indicates the
version number of the firmware or software in the module, as reported by NIST or CSEC. The value in the
COMPLIANCE DESCRIPTOR VERSION field is not related to the PRODUCT REVISION LEVEL field of standard INQUIRY
data (see 6.6.2).

The COMPLIANCE DESCRIPTOR MODULE NAME field is null terminated, null padded data (see 4.3.2) that indicates
the name or identifier of the cryptographic module, as reported by NIST or CSEC.

7.7.2 SA creation capabilities

7.7.2.1 Overview

If the SECURITY PROTOCOL field in a SECURITY PROTOCOL IN command (see 6.40) is set to 40h, then the
command returns information related to the SA creation (see 5.13.2.3) capabilities provided by the device
server.

The SA creation capabilities protocol is independent of any other SA creation protocols. If any SA creation
protocols are supported (e.g., IKEv2-SCSI (see 5.13.4)), then the device server shall not refuse to process an
SA creation capabilities SECURITY PROTOCOL IN command, and this processing shall not affect the state
maintained for any SA creation CCS (e.g., an IKEv2-SCSI CCS) on any I_T_L nexus. Except for those cases
where an SA creation capabilities SECURITY PROTOCOL IN command reports changed SA creation
capabilities, processing of the command shall not affect the concurrent processing of any commands that are
part of an SA creation CCS.

If any SA creation protocols are supported, the SA creation capabilities protocol shall be supported as
described in 7.7.2.

The SA creation capabilities SECURITY PROTOCOL IN CDB requirements are described in 7.7.2.2.

As shown in table 519 (see 7.7.2.2), the format of the parameter data for a SA creation capabilities
SECURITY PROTOCOL IN command depends on the value in the SECURITY PROTOCOL SPECIFIC field in the
CDB.

7.7.2.2 SA creation capabilities CDB description

The SA creation capabilities SECURITY PROTOCOL IN CDB has the format defined in 6.40 with the
additional requirements described in this subclause.

Working Draft SCSI Primary Commands - 4 (SPC-4) 673

T10/BSR INCITS 513 Revision 37 17 May 2014

If the SECURITY PROTOCOL field is set to SA creation capabilities (i.e., 40h) in a SECURITY PROTOCOL IN
command, the SECURITY PROTOCOL SPECIFIC field (see table 519) identifies the SA creation protocol (see
5.13.2.3) for which the device server shall return capability information.

Table 519 — SECURITY PROTOCOL SPECIFIC field for the SA creation capabilities

Parameter
Code Description data format
0000h Supported device server capabilities formats 7.7.2.3.1
0001h to 0100h Reserved
0101h IKEv2-SCSI device server capabilities 7.7.2.3.2
0102h to EFFFh Reserved
F000h to FFFFh Vendor Specific

If an SA creation capabilities SECURITY PROTOCOL IN command is received with the INC_512 bit set to one,
then the device server shall terminate the SECURITY PROTOCOL IN command with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN
CDB.

7.7.2.3 SA creation capabilities parameter data formats

7.7.2.3.1 Supported device server capabilities formats parameter data format

The supported device server capabilities formats parameter data (see table 520) indicates which device
server capabilities parameter data formats are supported by the device server.

Table 520 — Supported device server capabilities formats parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • PARAMETER DATA LENGTH (n-3)
3 (LSB)
Supported capabilities parameter data formats
4 (MSB) CAPABILITIES PARAMETER DATA FORMAT (0000h)
5 [first] (LSB)
••
•
n-1 (MSB)
CAPABILITIES PARAMETER DATA FORMAT [last]
n (LSB)

The PARAMETER DATA LENGTH field indicates the number of bytes that follow in the parameter data.

Each CAPABILITIES PARAMETER DATA FORMAT field in the supported capabilities parameter data formats list shall
contain one of the SECURITY PROTOCOL SPECIFIC field values (see table 519) supported by the device server.
The values shall be listed in ascending order starting with 0000h.

674 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7.2.3.2 IKEv2-SCSI device server capabilities parameter data format

The IKEv2-SCSI device server capabilities parameter data (see table 521) indicates the IKEv2 transforms
(i.e., key exchange protocols and authentication protocols) supported by the device server for IKEv2-SCSI.

Table 521 — IKEv2-SCSI device server capabilities parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • PARAMETER DATA LENGTH (n-3)
3 (LSB)
4
IKEv2-SCSI SA Creation Capabilities payload
•• •
(see 7.7.3.5.12)
n

The PARAMETER DATA LENGTH field indicates the number of bytes that follow in the parameter data.

The IKEv2-SCSI SA Creation Capabilities payload (see 7.7.3.5.12) indicates the algorithms supported by
IKEv2-SCSI in the Key Exchange step (see 5.13.4.6) and Authentication step (see 5.13.4.7).

The primary content of the IKEv2-SCSI device server capabilities SA creation capabilities parameter data is
an IKEv2-SCSI payload (see 7.7.3.5) that is used by the device server and application client in the
construction of other IKEv2-SCSI payloads (see 5.13.4).

7.7.3 IKEv2-SCSI

7.7.3.1 Overview

If the SECURITY PROTOCOL field in a SECURITY PROTOCOL OUT command (see 6.41) or a SECURITY
PROTOCOL IN command (see 6.40) is set to 41h, then the command is part of an IKEv2-SCSI CCS (see
5.13.4) and is used to transfer IKEv2-SCSI protocol information to or from the device server.

In an IKEv2-SCSI CCS, a defined sequence of SECURITY PROTOCOL OUT commands and SECURITY
PROTOCOL IN commands are sent by the application client and processed by the device server as
summarized in 5.13.4.1.

The IKEv2-SCSI SECURITY PROTOCOL OUT CDB format is described in 7.7.3.3.

The IKEv2-SCSI SECURITY PROTOCOL IN CDB format is described in 7.7.3.2.

The IKEv2-SCSI SECURITY PROTOCOL OUT command and the IKEv2-SCSI SECURITY PROTOCOL IN
command use the same parameter data format (see 7.7.3.4). The primary content of the IKEv2-SCSI
parameter data is one or more IKE payloads (see 7.7.3.5).

If the IKEv2-SCSI SA creation protocol is supported (see 7.7.1), the SA creation capabilities protocol (see
7.7.2) shall also be supported.

Working Draft SCSI Primary Commands - 4 (SPC-4) 675

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.3.2 IKEv2-SCSI SECURITY PROTOCOL IN CDB description

The IKEv2-SCSI SECURITY PROTOCOL IN CDB has the format defined in 6.40 with the additional
requirements described in this subclause.

If the SECURITY PROTOCOL field is set to IKEv2-SCSI (i.e., 41h) in a SECURITY PROTOCOL IN command, the
SECURITY PROTOCOL SPECIFIC field (see table 522) identifies the IKEv2-SCSI step (see 5.13.4.1) that the
device server is to process. If the IKEv2-SCSI SA creation protocol is supported (see 7.7.1), the SECURITY
PROTOCOL IN command support requirements are shown in table 522.

Table 522 — SECURITY PROTOCOL SPECIFIC field as defined by the IKEv2-SCSI SECURITY PROTOCOL
IN command

References

Code Description Support Usage Data format

0000h to 00FFh Restricted RFC 4306 RFC 4306
0100h to 0101h Reserved
0102h Key Exchange step Mandatory 5.13.4.6.3 7.7.3.4
0103h Authentication step Mandatory 5.13.4.7.3 7.7.3.4
0104h to EFFFh Reserved
F000h to FFFFh Vendor Specific

If an IKEv2-SCSI SECURITY PROTOCOL IN command is received with the INC_512 bit set to one while the
device server is maintaining state for an IKEv2-SCSI CCS on the I_T_L nexus on which the command was
received (see 5.13.4.1), then:

a) the device server shall terminate the SECURITY PROTOCOL IN command with CHECK CONDITION
status, with the sense key set to NOT READY, and the additional sense code set to LOGICAL UNIT
NOT READY, SA CREATION IN PROGRESS; and
b) the device server shall continue the IKEv2-SCSI CCS by preparing to receive another SECURITY
PROTOCOL IN command or SECURITY PROTOCOL OUT command.

If an IKEv2-SCSI SECURITY PROTOCOL IN command is received with the INC_512 bit set to one while the
device server is not maintaining state for an IKEv2-SCSI CCS (see 5.13.4.1), then the device server shall
terminate the SECURITY PROTOCOL IN command with CHECK CONDITION status, with the sense key set
to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

676 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7.3.3 IKEv2-SCSI SECURITY PROTOCOL OUT CDB description

The IKEv2-SCSI SECURITY PROTOCOL OUT CDB has the format defined in 6.41 with the additional
requirements described in this subclause.

If the SECURITY PROTOCOL field is set to IKEv2-SCSI (i.e., 41h) in a SECURITY PROTOCOL OUT command,
the SECURITY PROTOCOL SPECIFIC field (see table 523) identifies the IKEv2-SCSI step (see 5.13.4.1) that the
device server is to process. If the IKEv2-SCSI SA creation protocol is supported (see 7.7.1), the SECURITY
PROTOCOL OUT command support requirements are shown in table 523.

Table 523 — SECURITY PROTOCOL SPECIFIC field as defined by the IKEv2-SCSI SECURITY PROTOCOL
OUT command

References

Code Description Support Usage Data format

0000h to 00FFh Restricted RFC 4306 RFC 4306
0100h to 0101h Reserved
0102h Key Exchange step Mandatory 5.13.4.6.3 7.7.3.4
0103h Authentication step Mandatory 5.13.4.7.3 7.7.3.4
0104h Delete operation Mandatory 5.13.4.11 7.7.3.4
0105h to EFFFh Reserved
F000h to FFFFh Vendor Specific

If an IKEv2-SCSI SECURITY PROTOCOL OUT command is received with the INC_512 bit set to one while the
device server is maintaining state for an IKEv2-SCSI CCS on the I_T_L nexus on which the command was
received (see 5.13.4.1), then:

a) the device server shall terminate the SECURITY PROTOCOL OUT command with CHECK
CONDITION status, with the sense key set to NOT READY, and the additional sense code set to
LOGICAL UNIT NOT READY, SA CREATION IN PROGRESS; and
b) the device server shall continue the IKEv2-SCSI CCS by preparing to receive another SECURITY
PROTOCOL OUT command or SECURITY PROTOCOL IN command.

If an IKEv2-SCSI SECURITY PROTOCOL OUT command is received with the INC_512 bit set to one while the
device server is not maintaining state for an IKEv2-SCSI CCS (see 5.13.4.1), then the device server shall
terminate the SECURITY PROTOCOL OUT command with CHECK CONDITION status, with the sense key
set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

Any IKEv2-SCSI SECURITY PROTOCOL OUT command with a transfer length of up to 16 384 bytes shall
not be terminated with an error due to the number of bytes to be transferred and processed.

Working Draft SCSI Primary Commands - 4 (SPC-4) 677

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.3.4 IKEv2-SCSI parameter data format

Table 524 shows the parameter list format used by a SECURITY PROTOCOL OUT command and the
parameter data format used by a SECURITY PROTOCOL IN command if the SECURITY PROTOCOL field is set
to IKEv2-SCSI (i.e., 41h).

Table 524 — IKEv2-SCSI SECURITY PROTOCOL OUT command and SECURITY PROTOCOL IN
command parameter data

Bit
7 6 5 4 3 2 1 0
Byte
IKEv2-SCSI header
0
•• • Restricted (see RFC 4306)
3
4 (MSB)
•• • IKE_SA APPLICATION CLIENT SAI
7 (LSB)
8
•• • Restricted (see RFC 4306)
11
12 (MSB)
•• • IKE_SA DEVICE SERVER SAI
15 (LSB)
16 NEXT PAYLOAD

17 MAJOR VERSION (2h) MINOR VERSION

18 EXCHANGE TYPE

19 Reserved INTTR VERSION RSPNS Reserved

20 (MSB)
•• • MESSAGE ID
23 (LSB)
24 (MSB)
•• • IKE LENGTH (n+1)
27 (LSB)
IKEv2-SCSI payloads
28
•• • IKEv2-SCSI payload (see 7.7.3.5) [first]

•
••

•• • IKEv2-SCSI payload (see 7.7.3.5) [last]

n

678 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The IKE_SA APPLICATION CLIENT SAI field specifies the value that is or is destined to become the AC_SAI SA
parameter (see 5.13.2.2) in the generated SA (see 5.13.4.9). The AC_SAI is chosen by the application client
to uniquely identify its representation of the SA that is being negotiated or managed (e.g., deleted).

If the device server receives an IKEv2-SCSI header with the IKE_SA APPLICATION CLIENT SAI field set to zero,
then the error shall be processed as described in 7.7.3.8.

The application client should compare the IKE_SA APPLICATION CLIENT SAI field contents in any SECURITY
PROTOCOL IN parameter data to the value that the application client is maintaining for the IKEv2-SCSI CCS
or SA management. If the two values are not identical, the application client should abandon the IKEv2-SCSI
CCS, if any, and notify the device server that the IKEv2-SCSI CCS, if any, is being abandoned as described in
5.13.4.10.

Except in the Key Exchange step SECURITY PROTOCOL OUT command (see 5.13.4.6.2), the IKE_SA DEVICE
SERVER SAI field specifies the value that is or is destined to become the DS_SAI SA parameter in the
generated SA. The DS_SAI is chosen by the device server in accordance with the requirements in 5.13.2.1 to
uniquely identify its representation of the SA that is being negotiated. In the Key Exchange step SECURITY
PROTOCOL OUT command the IKE_SA DEVICE SERVER SAI field is reserved.

The application client should compare the IKE_SA DEVICE SERVER SAI field contents in the Authentication step
SECURITY PROTOCOL IN parameter data to the value that the application client is maintaining for the
IKEv2-SCSI CCS. If the two values are not identical, the application client should abandon the IKEv2-SCSI
CCS and notify the device server that the IKEv2-SCSI CCS is being abandoned as described in 5.13.4.10.

Working Draft SCSI Primary Commands - 4 (SPC-4) 679

T10/BSR INCITS 513 Revision 37 17 May 2014

The device server shall validate the contents of the IKE_SA APPLICATION CLIENT SAI field and the IKE_SA DEVICE
SERVER SAI field as shown in table 525.

Table 525 — IKEv2-SCSI header checking of SAIs

Expected contents for …

Contents of SECURITY IKE_SA IKE_SA

PROTOCOL SPECIFIC field APPLICATION DEVICE
in SECURITY CLIENT SERVER Device server action if expected field
PROTOCOL OUT CDB SAI field SAI field contents not received
0102h any value reserved No actions taken based on expected field
(i.e., Key Exchange step) contents.
0103h A match with the SAI The device server shall:
(i.e., Authentication step) values maintained for an a) terminate the SECURITY PROTOCOL
IKEv2-SCSI CCS on the OUT command with CHECK CONDITION
I_T_L nexus on which the status, with the sense key set to ILLEGAL
command was received REQUEST, and the additional sense code
set to SA CREATION PARAMETER
VALUE REJECTED; and
b) continue the IKEv2-SCSI CCS by
preparing to receive another Authenti-
cation step SECURITY PROTOCOL
OUT command.
0104h If at least one IKEv2-SCSI The device server shall:
(i.e., Delete operation) CCS is being maintained a) terminate the SECURITY PROTOCOL
for the I_T_L nexus on OUT command with CHECK CONDITION
which the command was status, with the sense key set to ILLEGAL
received, then: REQUEST, and the additional sense code
a) a match with the SAI set to SA CREATION PARAMETER
values maintained VALUE REJECTED; and
for an IKEv2-SCSI b) continue the IKEv2-SCSI CCS by
CCS; or preparing to receive another Authenti-
b) a match with the SAI cation step SECURITY PROTOCOL
values maintained OUT command.
for any active SA
If no IKEv2-SCSI CCS is The device server shall terminate the SECU-
being maintained for the RITY PROTOCOL OUT command with CHECK
I_T_L nexus on which the CONDITION status, with the sense key set to
command was received, ILLEGAL REQUEST, and the additional sense
then a match with the SAI code set to INVALID FIELD IN PARAMETER
values maintained for any LIST.
active SA

680 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The NEXT PAYLOAD field (see table 526) identifies the first IKEv2-SCSI payload that follows the IKEv2-SCSI
header.

Table 526 — NEXT PAYLOAD field

Support requirements in
SECURITY PROTOCOL …

Code IKE Payload Name IN OUT Reference

00h No Next Payload Mandatory 7.7.3.5.2
01h to 20h Reserved
21h Security Association Prohibited a RFC 4306
22h Key Exchange Mandatory 7.7.3.5.3
23h Identification – Application Client Prohibited Mandatory 7.7.3.5.4
24h Identification – Device Server Mandatory Prohibited 7.7.3.5.4
25h Certificate Optional 7.7.3.5.5
26h Certificate Request Optional 7.7.3.5.6
27h Authentication Mandatory 7.7.3.5.7
28h Nonce Mandatory 7.7.3.5.8
29h Notify Prohibited Mandatory 7.7.3.5.9
2Ah Delete Prohibited Mandatory 7.7.3.5.10
2Bh Vendor ID Prohibited RFC 4306
2Ch Traffic Selector – Application Client Prohibited RFC 4306
2Dh Traffic Selector – Device Server Prohibited RFC 4306
2Eh Encrypted Mandatory 7.7.3.5.11
2Fh Configuration Prohibited RFC 4306
30h Extensible Authentication Prohibited RFC 4306
31h to 7Fh Restricted RFC 4306
80h IKEv2-SCSI SA Creation Capabilities Mandatory 7.7.3.5.12
81h IKEv2-SCSI SA Cryptographic Algorithms Mandatory 7.7.3.5.13
82h IKEv2-SCSI SAUT Cryptographic Algorithms Mandatory 7.7.3.5.14
83h IKEv2-SCSI Timeout Values Mandatory 7.7.3.5.15
84h to BFh Reserved
C0h to FFh Vendor Specific
a The Security Association payload type value is not used in IKEv2-SCSI. The IKEv2-SCSI SA
Cryptographic Algorithms payload (i.e., 81h) and IKEv2-SCSI SAUT Cryptographic Algorithms payload
(i.e., 82h) are used instead.

The MAJOR VERSION field shall contain the value 2h. If a device server receives an IKEv2-SCSI header with a
MAJOR VERSION field containing a value other than 2h, then the error shall be processed as described in
7.7.3.8.

The MINOR VERSION field is reserved.

Working Draft SCSI Primary Commands - 4 (SPC-4) 681

T10/BSR INCITS 513 Revision 37 17 May 2014

The EXCHANGE TYPE field is reserved.

The initiator (INTTR) bit shall be set to:

a) one for SECURITY PROTOCOL OUT commands; and

b) zero for SECURITY PROTOCOL IN commands.

If a device server receives an IKEv2-SCSI header with the INTTR bit set to zero, the error shall be processed
as described in 7.7.3.8.

If an application client receives an IKEv2-SCSI header with the INTTR bit set to one, it should abandon the
IKEv2-SCSI CCS and notify the device server that the IKEv2-SCSI CCS is being abandoned as described in
5.13.4.10.

The VERSION bit is reserved.

The response (RSPNS) bit shall be set to:

a) zero for SECURITY PROTOCOL OUT commands; and

b) one for SECURITY PROTOCOL IN commands.

If a device server receives an IKEv2-SCSI header with the RSPNS bit set to one, the error shall be processed
as described in 7.7.3.8.

If an application client receives an IKEv2-SCSI header with the RSPNS bit set to zero, it should abandon the
IKEv2-SCSI CCS and notify the device server that the IKEv2-SCSI CCS is being abandoned as described in
5.13.4.10.

The MESSAGE ID field (see table 527) identifies the function of the parameter data.

Table 527 — MESSAGE ID field

Code Description
0000 0000h Key Exchange step SECURITY PROTOCOL OUT command (see
5.13.4.6.2) or SECURITY PROTOCOL IN command (see 5.13.4.6.3)
0000 0001h Authentication step SECURITY PROTOCOL OUT command (see
5.13.4.7.2) or SECURITY PROTOCOL IN command (see 5.13.4.7.3)
0000 0002h Delete operation in a SECURITY PROTOCOL OUT command
all others Reserved

If the device server receives a SECURITY PROTOCOL OUT command with an invalid MESSAGE ID field in its
IKEv2-SCSI header, then the error shall be processed as described in 7.7.3.8.

If the application client receives an invalid MESSAGE ID field in the parameter data for a SECURITY
PROTOCOL IN command, then the application client should abandon the IKEv2-SCSI CCS and notify the
device server that the IKEv2-SCSI CCS is being abandoned as described in 5.13.4.10.

The IKE LENGTH field specifies the total number of bytes in the parameter data, including the IKEv2-SCSI
header and all the IKEv2-SCSI payloads.

NOTE 52 - The contents of the IKE LENGTH field differ from those found in most SCSI length fields. However,
they are consistent with the IKEv2 usage (see RFC 4306).

682 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Each IKEv2-SCSI payload (see 7.7.3.5) contains specific data related to the operation being performed. A
specific combination of IKEv2-SCSI payloads is specified for each operation (e.g., Key Exchange) as
summarized in 5.13.4.2. The Encryption payload (see 7.7.3.6.2) nests one set of IKEv2-SCSI payloads inside
another.

Based on the contents of the SECURITY PROTOCOL SPECIFIC field in the SECURITY PROTOCOL OUT CDB, the
device server shall:

a) validate the contents of the NEXT PAYLOAD field in the IKEv2-SCSI header as shown in table 528,
before performing any decryption or integrity checking; and
b) validate that the number of instances of each next payload value shown in table 528 occur in the
parameter data after the encrypted data, if any, is decrypted and integrity checked (i.e., if the NEXT
PAYLOAD field in the IKEv2-SCSI header contains 2Eh, after the Encrypted payload is decrypted and
integrity checked).

If in the parameter data for a SECURITY PROTOCOL OUT command the next payload values in the
IKEv2-SCSI header and in the unencrypted payloads in the IKEv2-SCSI payloads (see table 524) do not meet
the requirements shown in table 528 for the listed SECURITY PROTOCOL SPECIFIC field contents, then the error
shall be processed as described in 7.7.3.8.

Based on the contents of the SECURITY PROTOCOL SPECIFIC field in the SECURITY PROTOCOL IN command,
the device server shall:

a) place one of the next payload values allowed by table 528 in the NEXT PAYLOAD field in the
IKEv2-SCSI header; and
b) include the number of instances of each next payload value shown in table 528 in the parameter data
either before or after encryption, if applicable (i.e., if the NEXT PAYLOAD field in the IKEv2-SCSI header
contains 2Eh, before the contents of the Encrypted payload are encrypted and integrity check value is
computed).

Table 528 — Next payload values in SECURITY PROTOCOL OUT/IN parameter data (part 1 of 3)

Next payload
value allowed Number of times
in IKEv2-SCSI a next payload
Next payload value header value is allowed
Authentication step
SECURITY PROTOCOL OUT command with not skipped
SECURITY PROTOCOL SPECIFIC field set to 0102h (i.e., Key Exchange step) (see 5.13.4.1)
83h (i.e., IKEv2-SCSI Timeout Values) Yes 1
81h (i.e., IKEv2-SCSI SA Cryptographic Algorithms) Yes 1
82h (i.e., IKEv2-SCSI SAUT Cryptographic Algorithms) No 0
22h (i.e., Key Exchange) Yes 1
28h (i.e., Nonce) Yes 1
00h (i.e., No Next Payload) No 1
All other next payload codes No 0

Working Draft SCSI Primary Commands - 4 (SPC-4) 683

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 528 — Next payload values in SECURITY PROTOCOL OUT/IN parameter data (part 2 of 3)

Next payload
value allowed Number of times
in IKEv2-SCSI a next payload
Next payload value header value is allowed
Authentication step
SECURITY PROTOCOL OUT command with skipped
SECURITY PROTOCOL SPECIFIC field set to 0102h (i.e., Key Exchange step) (see 5.13.4.1)
83h (i.e., IKEv2-SCSI Timeout Values) Yes 1
81h (i.e., IKEv2-SCSI SA Cryptographic Algorithms) Yes 1
82h (i.e., IKEv2-SCSI SAUT Cryptographic Algorithms) Yes 1
22h (i.e., Key Exchange) Yes 1
28h (i.e., Nonce) Yes 1
00h (i.e., No Next Payload) No 1
All other next payload codes No 0
Authentication step
SECURITY PROTOCOL IN command with not skipped
SECURITY PROTOCOL SPECIFIC field set to 0102h (i.e., Key Exchange step) (see 5.13.4.1)
81h (i.e., IKEv2-SCSI SA Cryptographic Algorithms) Yes 1
82h (i.e., IKEv2-SCSI SAUT Cryptographic Algorithms) No 0
22h (i.e., Key Exchange) Yes 1
28h (i.e., Nonce) Yes 1
26h (i.e., Certificate Request) Yes 0 or more
00h (i.e., No Next Payload) No 1
All other next payload codes No 0
Authentication step
SECURITY PROTOCOL IN command with skipped
SECURITY PROTOCOL SPECIFIC field set to 0102h (i.e., Key Exchange step) (see 5.13.4.1)
81h (i.e., IKEv2-SCSI SA Cryptographic Algorithms) Yes 1
82h (i.e., IKEv2-SCSI SAUT Cryptographic Algorithms) Yes 1
22h (i.e., Key Exchange) Yes 1
28h (i.e., Nonce) Yes 1
26h (i.e., Certificate Request) Yes 0 or more
00h (i.e., No Next Payload) No 1
All other next payload codes No 0

684 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 528 — Next payload values in SECURITY PROTOCOL OUT/IN parameter data (part 3 of 3)

Next payload
value allowed Number of times
in IKEv2-SCSI a next payload
Next payload value header value is allowed
SECURITY PROTOCOL OUT command with
SECURITY PROTOCOL SPECIFIC field set to 0103h (i.e., Authentication step)

2Eh (i.e., Encrypted) Yes 1

23h (i.e., Identification – Application Client) No 1
82h (i.e., IKEv2-SCSI SAUT Cryptographic Algorithms) No 1
25h (i.e., Certificate) No 0 or more
26h (i.e., Certificate Request) No 0 or more
29h (i.e., Notify) No 0 or 1
27h (i.e., Authentication) No 1
00h (i.e., No Next Payload) No 1
All other next payload codes No 0
SECURITY PROTOCOL IN command with
SECURITY PROTOCOL SPECIFIC field set to 0103h (i.e., Authentication step)

2Eh (i.e., Encrypted) Yes 1

24h (i.e., Identification – Device Server) No 1
82h (i.e., IKEv2-SCSI SAUT Cryptographic Algorithms) No 1
25h (i.e., Certificate) No 0 or more
27h (i.e., Authentication) No 1
00h (i.e., No Next Payload) No 1
All other next payload codes No 0
SECURITY PROTOCOL OUT command with
SECURITY PROTOCOL SPECIFIC field set to 0104h (i.e., Delete operation)

2Eh (i.e., Encrypted) Yes 1

2Ah (i.e., Delete) No 1
00h (i.e., No Next Payload) No 1
All other next payload codes No 0

Working Draft SCSI Primary Commands - 4 (SPC-4) 685

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.3.5 IKEv2-SCSI payloads

7.7.3.5.1 IKEv2-SCSI payload format

Each IKEv2-SCSI payload (see table 529) is composed of a header and data that is specific to the payload
type.

Table 529 — IKEv2-SCSI payload format

Bit
7 6 5 4 3 2 1 0
Byte
IKEv2-SCSI payload header
0 NEXT PAYLOAD

1 CRIT Reserved
2 (MSB)
IKE PAYLOAD LENGTH (n+1)
3 (LSB)
IKEv2-SCSI payload-specific data
4
•• • Payload-specific data
n

The NEXT PAYLOAD field identifies the IKEv2-SCSI payload that follows this IKEv2-SCSI payload using one of
the code values shown in table 526 (see 7.7.3.4).

The device server shall set the critical (CRIT) bit to one in all IKEv2-SCSI payloads returned to the application
client. The application client should set the CRIT bit to one in all IKEv2-SCSI payloads sent to the device
server.

If a device server receives an IKEv2-SCSI payload that it does not recognize (e.g., an IKEv2-SCSI payload
identified by a next payload value of 01h) with the CRIT bit set to one, then the error shall be processed
as described in 7.7.3.8.

If an application client receives an IKEv2-SCSI payload that it does not recognize with the CRIT bit set to one,
then the application client should abandon the IKEv2-SCSI CCS and notify the device server that it is
abandoning the IKEv2-SCSI CCS as described in 5.13.4.10.

If an application client or device server receives an IKEv2-SCSI payload that it does not recognize with the
CRIT bit set to zero, then it should use the NEXT PAYLOAD field and the IKE PAYLOAD LENGTH field to skip
processing of the unrecognized IKEv2-SCSI payload and continue processing at the next IKEv2-SCSI
payload.

The IKE PAYLOAD LENGTH field specifies the total number of bytes in the payload, including the IKEv2-SCSI
payload header. The value in the IKE PAYLOAD LENGTH field is not required to be a multiple of two or four (i.e.,
no byte alignment is maintained among IKEv2-SCSI payloads).

NOTE 53 - The contents of the IKE PAYLOAD LENGTH field differ from those found in most SCSI length fields.
However, they are consistent with the IKEv2 usage (see RFC 4306).

686 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The format and contents of the IKEv2-SCSI payload-specific data depends on the value in the NEXT PAYLOAD
field of:

a) the IKEv2-SCSI header (see 7.7.3.4), if this is the first IKEv2-SCSI payload in the parameter data; or
b) the previous IKEv2-SCSI payload, in all other cases.

7.7.3.5.2 No Next payload

A NEXT PAYLOAD field that is set to 00h (i.e., No Next payload) specifies that no more IKEv2-SCSI payloads
follow the current payload. The IKEv2-SCSI No Next payload contains no bytes.

7.7.3.5.3 Key Exchange payload

The Key Exchange payload (see table 530) transfers Diffie-Hellman shared key exchange data between an
application client and a device server or vice versa.

Table 530 — Key Exchange payload format

Bit
7 6 5 4 3 2 1 0
Byte
0 NEXT PAYLOAD

1 CRIT Reserved
2 (MSB)
IKE PAYLOAD LENGTH (n+1)
3 (LSB)
4 (MSB)
DIFFIE-HELLMAN GROUP NUMBER
5 (LSB)
6
Reserved
7
8
•• • KEY EXCHANGE DATA
n

The NEXT PAYLOAD field, CRIT bit, and IKE PAYLOAD LENGTH field are described in 7.7.3.5.1.

The DIFFIE-HELLMAN GROUP NUMBER field specifies the least significant 16 bits from ALGORITHM IDENTIFIER field
in the D-H IKEv2-SCSI algorithm descriptor (see 7.7.3.6.5) in the IKEv2-SCSI SA Cryptographic Algorithms
payload (see 7.7.3.5.13).

The KEY EXCHANGE DATA field specifies the sender's Diffie-Hellman public value for this key exchange. The
binary representation of key exchange data is defined in the reference cited for the Diffie-Hellman group that
is used (see table 555).

When a prime modulus (i.e., mod p) Diffie-Hellman group is used, the length of the Diffie-Hellman public value
shall be equal to the length of the prime modulus over which the exponentiation was performed as shown in
table 555 (see 7.7.3.6.5). Bits that are set to zero shall be prepended to the KEY EXCHANGE DATA field if
necessary.

Working Draft SCSI Primary Commands - 4 (SPC-4) 687

T10/BSR INCITS 513 Revision 37 17 May 2014

Diffie-Hellman exponential reuse and reuse of analogous Diffie-Hellman public values for Diffie-Hellman
mechanisms not based on exponentiation:

a) should not be performed; and

b) if performed, shall be constrained (e.g., requirements for discarding Diffie-Hellman information) as
defined in RFC 4306.

If Diffie-Hellman exponentials and public values are reused in IKEv2-SCSI, the associated random nonces
shall not be reused and the new random nonces should have a large number of bits of entropy (see RFC
4306).

7.7.3.5.4 Identification – Application Client payload and Identification – Device Server payload

The Identification – Application Client payload (see table 531) transfers identification information from the
application client to the device server. The Identification – Device Server payload (see table 531) transfers
identification information from the device server to the application client.

Table 531 — Identification payload format

Bit
7 6 5 4 3 2 1 0
Byte
0 NEXT PAYLOAD

1 CRIT Reserved
2 (MSB)
IKE PAYLOAD LENGTH (n+1)
3 (LSB)
4 ID TYPE

5
Reserved
7
8
•• • IDENTIFICATION DATA
n

The NEXT PAYLOAD field, CRIT bit, and IKE PAYLOAD LENGTH field are described in 7.7.3.5.1.

688 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The ID TYPE field describes the contents of the IDENTIFICATION DATA field and shall contain one of the named
values shown in table 532.

Table 532 — ID TYPE field

Code Name a Contents of the IDENTIFICATION DATA field

09h ID_DER_ASN1_DN The value of a certificate subject field (see RFC 5280)
The value of a name contained in a Subject Alternative
0Ah ID_DER_ASN1_GN Name (i.e., SubjectAltName) certificate extension (see
RFC 5280)
Arbitrary identity data (e.g., initiator port names, target
0Bh ID_KEY_ID
port names, and SCSI device names)
FC-SP-2 certificates that certify a Fibre Channel name
0Ch ID_FC_NAME
as an identity to be used (see RFC 4595 and FC-SP-2)
all other values Prohibited
a See RFC 4306 and RFC 4595 for additional information about the associated identification
data for these names.

The contents of the IDENTIFICATION DATA field depend on the value in the ID TYPE field.

If the Certificate payload is included in the parameter data, the identity in the Identification – Application Client
payload or Identification – Device Server payload is not required to match anything in the Certificate payload
(see RFC 4306). Based on information provided by a configuration method that is outside the scope of this
standard, device servers and application clients are required to verify a match between:

a) the identity in an Identification payload; and

b) the subject name or subject alternative name in a Certificate payload that contains an X.509
Certificate (see 7.7.3.5.5).

If a device server receives an Identification – Application Client payload that does not conform to the
requirements in RFC 4306 or the requirements in this subclause, then the IKEv2-SCSI CCS state maintained
for the I_T_L nexus shall be abandoned as described in 7.7.3.8.3.

If an application client receives an Identification – Device Server payload that does not conform to the
requirements in RFC 4306 or the requirements in this subclause, then the application client should abandon
the IKEv2-SCSI CCS and notify the device server that it is abandoning the IKEv2-SCSI CCS as described in
5.13.4.10.

Working Draft SCSI Primary Commands - 4 (SPC-4) 689

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.3.5.5 Certificate payload

The Certificate payload (see table 533) delivers a requested identity authentication certificate. The protocol for
using Certificate payloads is described in 5.13.4.3.3.4.

Table 533 — Certificate payload format

Bit
7 6 5 4 3 2 1 0
Byte
0 NEXT PAYLOAD

1 CRIT Reserved
2 (MSB)
IKE PAYLOAD LENGTH (n+1)
3 (LSB)
4 CERTIFICATE ENCODING

5
•• • CERTIFICATE DATA
n

The NEXT PAYLOAD field, CRIT bit, and IKE PAYLOAD LENGTH field are described in 7.7.3.5.1.

The CERTIFICATE ENCODING field describes the contents of the CERTIFICATE DATA field and shall contain one of
the values shown in table 534.

Table 534 — CERTIFICATE ENCODING field

Code Description Reference

00h Reserved
01h to 03h Prohibited Annex E
04h X.509 Certificate - Signature RFC 4306
05h to 0Ah Prohibited Annex E
0Bh Raw RSA Key RFC 4306 and RFC 4718
0Ch to 0Dh Prohibited Annex E
0Eh to C8h Restricted IANA
C9h to FFh Reserved

The contents of the CERTIFICATE DATA field depend on the value in the CERTIFICATE ENCODING field.

The relationship between the Certificate payload and the Identification payload is described in 7.7.3.5.4.

Device servers that support certificates should support a mechanism outside the scope of this standard for
replacing certificates and have the ability to store more than one certificate to facilitate such replacements.

690 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7.3.5.6 Certificate Request payload

The Certificate Request payload (see table 535) allows an application client or device server to request the
use of certificates as part of identity authentication and to name one or more trust anchors (see RFC 4306) for
the certificate verification process. The Certificate payload (see table 533) delivers a requested identity
authentication certificate. The protocol for using Certificate Request payloads is described in 5.13.4.3.3.4.

Table 535 — Certificate Request payload format

Bit
7 6 5 4 3 2 1 0
Byte
0 NEXT PAYLOAD

1 CRIT Reserved
2 (MSB)
IKE PAYLOAD LENGTH (n+1)
3 (LSB)
4 CERTIFICATE ENCODING

Certification authority list

5 (MSB)
•• • CERTIFICATION AUTHORITY [first]
24 (LSB)
••
•
n-19 (MSB)
•• • CERTIFICATION AUTHORITY [last]
n (LSB)

The NEXT PAYLOAD field, CRIT bit, and IKE PAYLOAD LENGTH field are described in 7.7.3.5.1.

The value in the CERTIFICATE ENCODING field (see table 534 in 7.7.3.5.5) indicates the type or format of
certificate being requested. Multiple Certificate Request payloads may be included in the parameter data
transferred by a single command. If the parameter data contains more than one Certificate Request payload,
each Certificate Request payload should have a different value in the CERTIFICATE ENCODING field.

Each CERTIFICATION AUTHORITY field contains an indicator of a trusted authority for the certificate type indicated
by the CERTIFICATE ENCODING field in this Certificate Request payload. The indicator is a SHA-1 hash of the
public key of a trusted certification authority. The indicator is encoded as the SHA-1 hash of the Subject Public
Key Info element from the trust anchor certificate (see RFC 5280).

Device servers that support certificates should support a mechanism outside the scope of this standard for
replacing certification authority values, and shall have the ability to store one or more certification authority
values to facilitate such replacements.

Working Draft SCSI Primary Commands - 4 (SPC-4) 691

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.3.5.7 Authentication payload

The Authentication payload (see table 536) allows the application client and a device server to verify that the
data transfers in their IKEv2-SCSI CCS have not be compromised by a man-in-the-middle attack (see
5.13.1.4).

Table 536 — Authentication payload format

Bit
7 6 5 4 3 2 1 0
Byte
0 NEXT PAYLOAD

1 CRIT Reserved
2 (MSB)
IKE PAYLOAD LENGTH (n+1)
3 (LSB)
4 AUTH METHOD

5
Reserved
7
8
•• • AUTHENTICATION DATA
n

The NEXT PAYLOAD field, CRIT bit, and IKE PAYLOAD LENGTH field are described in 7.7.3.5.1.

The AUTH METHOD field indicates the authentication algorithm to be applied to this Authentication payload. The
AUTH METHOD field contains the least significant eight bits of the ALGORITHM IDENTIFIER field in an
SA_AUTH_OUT algorithm descriptor or an SA_AUTH_IN algorithm descriptor (see 7.7.3.6.6) from the Key
Exchange step (see 5.13.4.6).

If the contents of the AUTH METHOD field in the parameter data for the Authentication step SECURITY
PROTOCOL OUT command (see 5.13.4.7.2) do not match the least significant eight bits in the ALGORITHM
IDENTIFIER field in the SA_AUTH_OUT algorithm descriptor in the IKEv2-SCSI SA Cryptographic Algorithms
payload (see 7.7.3.5.13) in the Key Exchange step, then the device server shall:

a) terminate the SECURITY PROTOCOL OUT command CHECK CONDITION status, with the sense
key set to ABORTED COMMAND and the additional sense code set to AUTHENTICATION FAILED;
and
b) abandon the IKEv2-SCSI CCS (see 5.13.4.10).

If the contents of the AUTH METHOD field in the parameter data for the Authentication step SECURITY
PROTOCOL IN command (see 5.13.4.7.3) do not match the least significant eight bits in the ALGORITHM
IDENTIFIER field in the SA_AUTH_IN algorithm descriptor in the IKEv2-SCSI SA Cryptographic Algorithms
payload in the Key Exchange step, then application client should abandon the IKEv2-SCSI CCS and notify the
device server that it is abandoning the IKEv2-SCSI CCS as described in 5.13.4.10.

In the Authentication step SECURITY PROTOCOL OUT command (see 5.13.4.7.2) parameter list, the
AUTHENTICATION DATA field contains the result of applying the algorithm specified by the ALGORITHM IDENTIFIER
field in the SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor in the IKEv2-SCSI SA
Cryptographic Algorithms payload (see 7.7.3.5.13) in the Key Exchange step (see 5.13.4.6) as described in

692 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

table 557 (see 7.7.3.6.6) and this subclause to generate the following concatenation of bytes:

1) all the bytes in the Data-In Buffer returned by the Device Server Capabilities step (see 5.13.4.5)
SECURITY PROTOCOL IN command;
2) all the bytes in the Data-Out Buffer sent by the Key Exchange step SECURITY PROTOCOL OUT
command (see 5.13.4.6.2) in the same IKEv2-SCSI CCS for which GOOD status was returned;
3) all the bytes in the IKEv2-SCSI payload-specific data part (see 7.7.3.5.1) of the Nonce payload (see
7.7.3.5.8) that was received in the Key Exchange step SECURITY PROTOCOL IN command in the
same IKEv2-SCSI CCS; and
4) all the bytes produced by applying the PRF selected by the PRF IKEv2-SCSI cryptographic algorithm
descriptor (see 7.7.3.6.3) in the IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13) to
the following inputs:
1) the SK_pi shared key (see 5.13.4.4); and
2) all the bytes in the IKEv2-SCSI payload-specific data part (see 7.7.3.5.1) of the Identification –
Application Client payload (see 7.7.3.5.4).

While processing the Authentication step SECURITY PROTOCOL OUT command, the device server shall
verify the contents of the AUTHENTICATION DATA field by applying the algorithm specified by the ALGORITHM
IDENTIFIER field in the SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor in the IKEv2-SCSI SA
Cryptographic Algorithms payload (see 7.7.3.5.13) in the Key Exchange step (see 5.13.4.6) as described in
table 557 (see 7.7.3.6.6) and this subclause to generate the following concatenation of bytes:

1) all the bytes in the Data-In Buffer that the device server returned to any application client in response
to the last received Device Server Capabilities step SECURITY PROTOCOL IN command;
2) all the bytes in the Data-Out Buffer received in the Key Exchange step SECURITY PROTOCOL OUT
command (see 5.13.4.6.2) in the same IKEv2-SCSI CCS for which GOOD status was returned;
3) all the bytes in the IKEv2-SCSI payload-specific data part (see 7.7.3.5.1) of the Nonce payload (see
7.7.3.5.8) sent in the Key Exchange step SECURITY PROTOCOL IN command in the same
IKEv2-SCSI CCS; and
4) all the bytes produced by applying the PRF selected by the PRF IKEv2-SCSI cryptographic algorithm
descriptor (see 7.7.3.6.3) in the IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13) to
the following inputs:
1) the SK_pi shared key (see 5.13.4.4); and
2) all the bytes received in the IKEv2-SCSI payload-specific data part (see 7.7.3.5.1) of the
Identification – Application Client payload (see 7.7.3.5.4) of the parameter list being processed.

If the verification of the contents of the AUTHENTICATION DATA field is not successful, then the device server
shall:

a) terminate the SECURITY PROTOCOL OUT command with CHECK CONDITION status, with the
sense key set to ABORTED COMMAND and the additional sense code set to AUTHENTICATION
FAILED; and
b) abandon the IKEv2-SCSI CCS (see 5.13.4.10).

For the Authentication step SECURITY PROTOCOL IN command (see 5.13.4.7.3) parameter list, the device
server shall compute the AUTHENTICATION DATA field contents by applying the algorithm specified by the
ALGORITHM IDENTIFIER field in the SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptor in the
IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13) in the Key Exchange step (see 5.13.4.6)
as described in table 557 (see 7.7.3.6.6) and this subclause to generate the following concatenation of bytes:

1) all the bytes in the Data-In Buffer that the device server returned to any application client in response
to the last received Device Server Capabilities step SECURITY PROTOCOL IN command;

Working Draft SCSI Primary Commands - 4 (SPC-4) 693

T10/BSR INCITS 513 Revision 37 17 May 2014

2) all the bytes in the Data-In Buffer sent by the most recent Key Exchange step SECURITY
PROTOCOL IN command (see 5.13.4.6.3) in the same IKEv2-SCSI CCS for which GOOD status was
returned;
3) all the bytes in the IKEv2-SCSI payload-specific data part (see 7.7.3.5.1) of the Nonce payload (see
7.7.3.5.8) received in the Key Exchange step SECURITY PROTOCOL OUT command in the same
IKEv2-SCSI CCS; and
4) all the bytes produced by applying the PRF selected by the PRF IKEv2-SCSI cryptographic algorithm
descriptor (see 7.7.3.6.3) in the IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13) to
the following inputs:
1) the SK_pr shared key (see 5.13.4.4); and
2) all the bytes in the IKEv2-SCSI payload-specific data part (see 7.7.3.5.1) of the Identification –
Device Server payload (see 7.7.3.5.4).

After the Authentication step SECURITY PROTOCOL IN command completes with GOOD status, the
application client should verify the contents of the AUTHENTICATION DATA field by applying the algorithm
specified by the ALGORITHM IDENTIFIER field in the SA_AUTH_IN IKEv2-SCSI cryptographic algorithm
descriptor in the IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13) in the Key Exchange step
(see 5.13.4.6) as described in table 557 (see 7.7.3.6.6) and this subclause to generate the following
concatenation of bytes:

1) all the bytes in the Data-In Buffer returned by the Device Server Capabilities step (see 5.13.4.5)
SECURITY PROTOCOL IN command;
2) all the bytes in the Data-In Buffer returned by the most recent Key Exchange step SECURITY
PROTOCOL IN command (see 5.13.4.6.3) in the same IKEv2-SCSI CCS for which GOOD status was
returned;
3) all the bytes in the IKEv2-SCSI payload-specific data part (see 7.7.3.5.1) of the Nonce payload (see
7.7.3.5.8) sent in the Key Exchange step SECURITY PROTOCOL OUT command in the same
IKEv2-SCSI CCS; and
4) all the bytes produced by applying the PRF selected by the PRF IKEv2-SCSI cryptographic algorithm
descriptor (see 7.7.3.6.3) in the IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13) to
the following inputs:
1) the SK_pr shared key (see 5.13.4.4); and
2) all the bytes in the IKEv2-SCSI payload-specific data part (see 7.7.3.5.1) of the Identification –
Device Server payload (see 7.7.3.5.4) received in the SECURITY PROTOCOL IN parameter
data.

If the verification of the contents of the AUTHENTICATION DATA field is not successful, then the application client
should abandon the IKEv2-SCSI CCS and notify the device server that it is abandoning the IKEv2-SCSI CCS
as described in 5.13.4.10.

If the AUTH METHOD field is set to 01h (i.e., RSA Digital Signature), the RSA digital signature shall be encoded
with the EMSA-PKCS1-v1_5 signature encoding method as defined in RFC 2437 (see RFC 4718).

694 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7.3.5.8 Nonce payload

The Nonce payload (see table 537) transfers one random nonce from the application client to the device
server or from the device server to the application client.

Table 537 — Nonce payload format

Bit
7 6 5 4 3 2 1 0
Byte
0 NEXT PAYLOAD

1 CRIT Reserved
2 (MSB)
IKE PAYLOAD LENGTH (n+1)
3 (LSB)
4
•• • NONCE DATA
n

The NEXT PAYLOAD field, CRIT bit, and IKE PAYLOAD LENGTH field are described in 7.7.3.5.1.

In the Key Exchange step SECURITY PROTOCOL OUT command (see 5.13.4.6.2) the NONCE DATA field
specifies the application client’s random nonce.

In the Key Exchange step SECURITY PROTOCOL IN command (see 5.13.4.6.3) the NONCE DATA field
indicates the device server’s random nonce.

The requirements that RFC 4306 places on the nonce data shall apply to this standard.

Working Draft SCSI Primary Commands - 4 (SPC-4) 695

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.3.5.9 Notify payload

This standard uses the Notify payload (see table 538) to provide initial contact notification from the application
client to the device server. See Annex E for information about differences between this standard and IKEv2.

Table 538 — Notify payload format

Bit
7 6 5 4 3 2 1 0
Byte
0 NEXT PAYLOAD

1 CRIT Reserved
2 (MSB)
IKE PAYLOAD LENGTH (0010h)
3 (LSB)
4 PROTOCOL ID (01h)
5 SAI SIZE (08h)
6 (MSB)
NOTIFY MESSAGE TYPE (4000h)
7 (LSB)
8
•• • Restricted (see RFC 4306)
11
12 (MSB)
•• • SAI
15 (LSB)

The NEXT PAYLOAD field, CRIT bit, and IKE PAYLOAD LENGTH field are described in 7.7.3.5.1.

The PROTOCOL ID field is set as shown in table 538 for the IKEv2-SCSI Notify payload. If the device server
receives a PROTOCOL ID field that is not set as shown in table 538, the IKEv2-SCSI CCS state maintained for
the I_T_L nexus shall be abandoned as described in 7.7.3.8.3.

The SAI SIZE field is set as shown in table 538 for the IKEv2-SCSI Notify payload. If the device server receives
an SAI SIZE field that is not set as shown in table 538, the IKEv2-SCSI CCS state maintained for the I_T_L
nexus shall be abandoned as described in 7.7.3.8.3.

The NOTIFY MESSAGE TYPE field is set as shown in table 538 (i.e., INITIAL_CONTACT) for the IKEv2-SCSI
Notify payload. If the device server receives a NOTIFY MESSAGE TYPE field that is not set as shown in table 538,
the IKEv2-SCSI CCS state maintained for the I_T_L nexus shall be abandoned as described in 7.7.3.8.3.

The SAI field specifies the device server’s SAI. If the contents of the SAI field are not identical to the contents of
the IKE_SA DEVICE SERVER SAI field in the IKEv2-SCSI header (see 7.7.3.4), then the IKEv2-SCSI CCS state
maintained for the I_T_L nexus shall be abandoned as described in 7.7.3.8.3.

Unless an error is detected, the device server shall process the Notify payload as described in 5.13.4.7.2.

696 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7.3.5.10 Delete payload

The Delete payload (see table 539) requests the deletion of an existing SA or the abandonment of an
IKEv2-SCSI CCS that is in progress.

Table 539 — Delete payload format

Bit
7 6 5 4 3 2 1 0
Byte
0 NEXT PAYLOAD

1 CRIT Reserved
2 (MSB)
IKE PAYLOAD LENGTH (0018h)
3 (LSB)
4 PROTOCOL ID (01h)
5 SAI SIZE (08h)
6 (MSB)
NUMBER OF SAIS (0002h)
7 (LSB)
8
•• • Restricted (see RFC 4306)
11
12 (MSB)
•• • AC_SAI
15 (LSB)
16
•• • Restricted (see RFC 4306)
19
20 (MSB)
•• • DS_SAI
23 (LSB)

The NEXT PAYLOAD field, CRIT bit, and IKE PAYLOAD LENGTH field are described in 7.7.3.5.1.

The PROTOCOL ID field is set as shown in table 539 for the IKEv2-SCSI Delete payload. If the device server
receives a PROTOCOL ID field that is not set as shown in table 539, the error shall be processed as described in
7.7.3.8.3.

The SAI SIZE field is set as shown in table 539 for the IKEv2-SCSI Delete payload. If the device server receives
an SAI SIZE field that is not set as shown in table 539, the error shall be processed as described in 7.7.3.8.3.

The NUMBER OF SAIS field is set as shown in table 539 for the IKEv2-SCSI Delete payload. If the device server
receives a NUMBER OF SAIS field that is not set as shown in table 539, the error shall be processed as
described in 7.7.3.8.3.

The AC_SAI field specifies the AC_SAI SA parameter value for the SA to be deleted. If the contents of the
AC_SAI field do not match the contents of the IKE_SA APPLICATION CLIENT SAI field in the IKEv2-SCSI header
(see 7.7.3.4), then the error shall be processed as described in 7.7.3.8.3.

Working Draft SCSI Primary Commands - 4 (SPC-4) 697

T10/BSR INCITS 513 Revision 37 17 May 2014

The DS_SAI field specifies the DS_SAI SA parameter value for the SA to be deleted. If the contents of the
DS_SAI field do not match the contents of the IKE_SA DEVICE SERVER SAI field in the IKEv2-SCSI header (see
7.7.3.4), then the error shall be processed as described in 7.7.3.8.3.

If the device server is maintaining SA parameters for which the AC_SAI matches the contents of the AC_SAI
field and the DS_SAI matches the contents of the DS _SAI field, then that set of SA parameters shall be
deleted.

If the device server is maintaining state for an IKEv2-SCSI CCS on the I_T_L nexus on which the command
was received, then the IKEv2-SCSI CCS shall be abandoned (see 5.13.4.10) if:

a) the contents of the AC_SAI field match the application client’s SAI in the maintained state; and
b) the contents of the DS_SAI field match the device server’s SAI in the maintained state.

7.7.3.5.11 Encrypted payload

7.7.3.5.11.1 Combined mode encryption

The following types of encryption algorithms are used in the Encrypted payload:

a) non-combined modes that use separate algorithms to encrypt/decrypt and integrity check the
Encrypted payload; and
b) combined modes in which a single encryption algorithm does both encryption/decryption and integrity
checking.

The ALGORITHM IDENTIFIER field in the INTEG IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.4) in
the IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13) in the Key Exchange step (see
5.13.4.6) indicates the type of encryption algorithm to be applied to the Encrypted payload for IKEv2-SCSI
functions as follows:

a) if the ALGORITHM IDENTIFIER field is not set to AUTH_COMBINED, a non-combined mode encryption
algorithm is being used; or
b) if the ALGORITHM IDENTIFIER field is set to AUTH_COMBINED, a combined mode encryption algorithm
is being used.

If the Encrypted payload is in parameter data that is not associated with an active IKEv2-SCSI CCS, then the
integrity checking algorithm identifier that selects between combined and non-combined mode encryption is
found in the MGMT_DATA SA parameter (see 5.13.4.9).

698 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7.3.5.11.2 Encrypted payload introduction

The Encrypted payload transfers (see table 540) one or more other IKEv2-SCSI payloads that are encrypted
and integrity checked from the application client to the device server and vice versa.

If IKEv2-SCSI parameter data contains the Encrypted payload, then the Encrypted payload is the first payload
in the parameter data (i.e., the NEXT PAYLOAD field in the IKEv2-SCSI header (see 7.7.3.5.1) contains 2Eh).
Since the NEXT PAYLOAD field in an Encrypted payload identifies the first payload in the CIPHERTEXT field, there
is no way to identify a payload following the Encrypted payload. As a result, the Encrypted payload is required
to be the last payload in the IKEv2-SCSI payloads part of the parameter data (see 7.7.3.4).

Table 540 — Encrypted payload format

Bit
7 6 5 4 3 2 1 0
Byte
0 NEXT PAYLOAD

1 CRIT Reserved
2 (MSB)
IKE PAYLOAD LENGTH (n+1)
3 (LSB)
4
•• • INITIALIZATION VECTOR
i-1
i
•• • CIPHERTEXT
k-1
k
•• • INTEGRITY CHECK VALUE
n

The NEXT PAYLOAD field identifies the first IKEv2-SCSI payload in the CIPHERTEXT field using the coded values
shown in table 526 (see 7.7.3.5.1).

The CRIT bit and IKE PAYLOAD LENGTH field are described in 7.7.3.5.1.

The IKE PAYLOAD LENGTH field specifies the number of bytes that follow in the Encrypted payload. The number
of bytes in the CIPHERTEXT field is equal to the number of bytes in the plaintext (see table 541).

The INITIALIZATION VECTOR field specifies the initialization vector encryption algorithm input value. The size of
the initialization vector is defined by the encryption algorithm as shown in table 549 (see 7.7.3.6.2).

The CIPHERTEXT field contains an output of the encryption algorithm specified by the ALGORITHM IDENTIFIER
field in the ENCR IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.2) in the IKEv2-SCSI SA
Cryptographic Algorithms payload (see 7.7.3.5.13) in the Key Exchange step (see 5.13.4.6) using the inputs:

a) IKEv2-SCSI AAD is an encryption algorithm input as follows:

A) if a non-combined mode encryption algorithm is being used (see 7.7.3.5.11.1), then there is no
AAD input; or
B) if a combined mode encryption algorithm is being used (see 7.7.3.5.11.1), then the AAD
described in 7.7.3.5.11.3 is an input;
b) the contents of the INITIALIZATION VECTOR field (see table 549);

Working Draft SCSI Primary Commands - 4 (SPC-4) 699

T10/BSR INCITS 513 Revision 37 17 May 2014

c) the plaintext data shown in table 541; and

d) the shared key value, key length, and salt bytes (see table 549 in 7.7.3.6.2) if any, for one of the
following shared keys:
A) if the Encrypted payload appears in the parameter data for an Authentication step SECURITY
PROTOCOL OUT command (see 5.13.4.7.2) or the parameter data for a Delete operation
SECURITY PROTOCOL OUT command (see 5.13.4.11) that affects an active IKEv2-SCSI CCS,
then the SK_ei shared key (see 5.13.4.4) for the IKEv2-SCSI CCS;
B) if the Encrypted payload appears in the parameter data for an Authentication step SECURITY
PROTOCOL IN command (see 5.13.4.7.3), then the SK_er shared key (see 5.13.4.4) for the
IKEv2-SCSI CCS; or
C) if the Encrypted payload appears in the parameter data for a Delete operation SECURITY
PROTOCOL OUT command (see 5.13.4.11) that does not affect an active IKEv2-SCSI CCS, then
the SK_ei shared key (see 5.13.4.4) from the MGMT_DATA SA parameter (see 5.13.4.9).

NOTE 54 - Salt bytes (see table 549 in 7.7.3.6.2) are used only by combined mode encryption algorithms
(see 7.7.3.5.11.1).

If the Encrypted payload appears in the parameter data for a Delete operation SECURITY PROTOCOL OUT
command that does not affect an active IKEv2-SCSI CCS, then the encryption algorithm identifier stored in
the MGMT_DATA SA parameter indicates the encryption algorithm to use.

The INTEGRITY CHECK VALUE field contains the integrity check value that is computed as described in
7.7.3.5.11.1 (e.g., if the integrity algorithm is AUTH_COMBINED, then the integrity check value is an output of
the encryption algorithm). The size of the integrity check value is defined by the integrity algorithm or
encryption algorithm, depending on which algorithm computes the value.

If the integrity algorithm specified by the ALGORITHM IDENTIFIER field in the INTEG IKEv2-SCSI cryptographic
algorithm descriptor in the IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13) in the Key
Exchange step is not AUTH_COMBINED, then the contents of the INTEGRITY CHECK VALUE field are computed
by processing the integrity check algorithm specified by the ALGORITHM IDENTIFIER field in the INTEG
IKEv2-SCSI cryptographic algorithm descriptor using the following inputs:

a) a byte string composed of:

1) the AAD described in 7.7.3.5.11.3;
2) the contents of the INITIALIZATION VECTOR field (see table 540); and
3) the ciphertext that is the result of encrypting the plaintext data;
and
b) the shared key value from one of the following shared keys:
A) if the Encrypted payload appears in the parameter data for an Authentication step SECURITY
PROTOCOL OUT command (see 5.13.4.7.2) or the parameter data for a Delete operation
SECURITY PROTOCOL OUT command (see 5.13.4.11) that affects an active IKEv2-SCSI CCS,
then the SK_ai shared key (see 5.13.4.4) for the IKEv2-SCSI CCS;
B) if the Encrypted payload appears in the parameter data for an Authentication step SECURITY
PROTOCOL IN command (see 5.13.4.7.3), then the SK_ar shared key (see 5.13.4.4) for the
IKEv2-SCSI CCS; or
C) if the Encrypted payload appears in the parameter data for a Delete operation SECURITY
PROTOCOL OUT command (see 5.13.4.11) that does not affect an active IKEv2-SCSI CCS, then
the SK_ai shared key (see 5.13.4.4) from the MGMT_DATA SA parameter (see 5.13.4.9).

If the Encrypted payload appears in the parameter data for a Delete operation SECURITY PROTOCOL OUT
command that does not affect an active IKEv2-SCSI CCS, then the integrity checking algorithm identifier
stored in the MGMT_DATA SA parameter indicates the integrity checking algorithm to use.

700 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

While computing the encrypted CIPHERTEXT field contents for an Encrypted payload, the plaintext format
shown in table 541 is used.

Table 541 — Plaintext format for Encrypted payload CIPHERTEXT field

Bit
7 6 5 4 3 2 1 0
Byte
IKEv2-SCSI payloads
0
•• • IKEv2-SCSI payload (see 7.7.3.5) [first]

•
•
•

•• • IKEv2-SCSI payload (see 7.7.3.5) [last]

n
p
•• • PADDING BYTES (if any)
k-1
k PAD LENGTH (k-p)

Each IKEv2-SCSI payload (see 7.7.3.5) contains specific data related to the operation being performed. A
specific combination of IKEv2-SCSI payloads is required for each operation (e.g., Authentication) as
summarized in 5.13.4.2.

The PADDING BYTES field contains zero to 255 bytes. The number of padding bytes is:

a) defined by the encryption algorithm; or

b) any number of bytes that causes the length of all plaintext bytes (i.e., k+1) to be a whole multiple of
the alignment (see table 549 in 7.7.3.6.2) for the encryption algorithm being used.

The contents of the padding bytes are:

a) defined by the encryption algorithm; or

b) if the encryption algorithm does not define the padding bytes contents, a series of one byte binary
values starting at one and incrementing by one in each successive byte (i.e., 01h in the first padding
byte, 02h in the second padding byte, etc.).

If the encryption algorithm does not place requirements on the contents of the padding bytes (i.e., option b) is
in effect), then after decryption the contents of the padding bytes shall be verified to match the series of one
byte binary values described in this subclause. If this verification is not successful in a device server, the error
shall be processed as described in 7.7.3.8.2. If this verification is not successful in an application client, the
decrypted data should be ignored.

The PAD LENGTH field specifies the number of bytes in the PADDING BYTES field.

7.7.3.5.11.3 IKEv2-SCSI AAD

The AAD defined by this standard for IKEv2-SCSI use is as follows:

1) all the bytes in the IKEv2-SCSI Header (see 7.7.3.4); and

Working Draft SCSI Primary Commands - 4 (SPC-4) 701

T10/BSR INCITS 513 Revision 37 17 May 2014

2) all the bytes in the IKEv2-SCSI Payload Header (see 7.7.3.5.1) of the Encrypted payload (see
7.7.3.5.11).

7.7.3.5.11.4 Processing a received Encrypted payload

Before performing any checks of data contained in the CIPHERTEXT field, the contents of the INTEGRITY CHECK
VALUE field and CIPHERTEXT field shall be integrity checked and decrypted based on the contents of the IKE_SA
APPLICATION CLIENT SAI field and the IKE_SA DEVICE SERVER SAI field in the IKEv2-SCSI header (see 7.7.3.4) as
described in this subclause.

Computation of the comparison integrity check value and decryption of an Encrypted payload is performed as
follows:

1) if a non-combined mode encryption algorithm is being used (see 7.7.3.5.11.1), then the comparison
integrity check value is computed by performing the integrity check algorithm specified by the
ALGORITHM IDENTIFIER field in the INTEG IKEv2-SCSI cryptographic algorithm descriptor using the
following inputs:
A) a byte string composed of:
1) the AAD described in 7.7.3.5.11.3;
2) the contents of the INITIALIZATION VECTOR field (see table 540) in the Encrypted payload; and
3) the contents of the CIPHERTEXT field (see table 540) in the Encrypted payload;
and
B) the shared key value from one of the following shared keys:
a) if the Encrypted payload appears in the parameter data for an Authentication step SECURITY
PROTOCOL OUT command (see 5.13.4.7.2) or the parameter data for a Delete operation
SECURITY PROTOCOL OUT command (see 5.13.4.11) that affects an active IKEv2-SCSI
CCS, then the SK_ai shared key (see 5.13.4.4) for the IKEv2-SCSI CCS;
b) if the Encrypted payload appears in the parameter data for an Authentication step SECURITY
PROTOCOL IN command (see 5.13.4.7.3), then the SK_ar shared key (see 5.13.4.4) for the
IKEv2-SCSI CCS; or
c) if the Encrypted payload appears in the parameter data for a Delete operation SECURITY
PROTOCOL OUT command (see 5.13.4.11) that does not affect an active IKEv2-SCSI CCS,
then the SK_ai shared key (see 5.13.4.4) from the MGMT_DATA SA parameter (see
5.13.4.9);
and
2) process the CIPHERTEXT field using the encryption algorithm specified by the ALGORITHM IDENTIFIER
field in the ENCR IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.2) in the IKEv2-SCSI
SA Cryptographic Algorithms payload (see 7.7.3.5.13) in the Key Exchange step (see 5.13.4.6) using
the inputs:
A) IKEv2-SCSI AAD is an input to the encryption algorithm as follows:
a) if a non-combined mode encryption algorithm is being used (see 7.7.3.5.11.1), then there is
no AAD input; or
b) if a combined mode encryption algorithm is being used (see 7.7.3.5.11.1), then the AAD
described in 7.7.3.5.11.3 is an input;
B) the contents of the INITIALIZATION VECTOR field (see table 540) in the Encrypted payload;
C) the contents of the CIPHERTEXT field (see table 540) in the Encrypted payload; and
D) the shared key value, key length, and salt bytes (see table 549 in 7.7.3.6.2) if any, for one of the
following shared keys:
a) if the Encrypted payload appears in the parameter data for an Authentication step SECURITY
PROTOCOL OUT command (see 5.13.4.7.2), or the parameter data for a Delete operation
SECURITY PROTOCOL OUT command (see 5.13.4.11) that affects an active IKEv2-SCSI
CCS, then the SK_ei shared key (see 5.13.4.4) for the IKEv2-SCSI CCS;

702 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

b) if the Encrypted payload appears in the parameter data for an Authentication step SECURITY
PROTOCOL IN command (see 5.13.4.7.3), then the SK_er shared key (see 5.13.4.4) for the
IKEv2-SCSI CCS; or
c) if the Encrypted payload appears in the parameter data for a Delete operation SECURITY
PROTOCOL OUT command (see 5.13.4.11) that does not affect an active IKEv2-SCSI CCS,
then the SK_ei shared key (see 5.13.4.4) from the MGMT_DATA SA parameter (see
5.13.4.9).

The results of step 2) are:

a) the decrypted plaintext, if a non-combined mode encryption algorithm is being used (see
7.7.3.5.11.1); or
b) the decrypted plaintext and the comparison integrity check value, if a combined mode encryption
algorithm is being used.

If the Encrypted payload appears in the parameter data for a Delete operation SECURITY PROTOCOL OUT
command that does not affect an active IKEv2-SCSI CCS, then the integrity checking algorithm identifier
value and encryption algorithm identifier value that are stored in the MGMT_DATA SA parameter indicate the
integrity checking algorithm to use.

If the comparison integrity check value differs from the value in the INTEGRITY CHECK VALUE field of the
Encrypted payload, then:

a) the application client should abandon the IKEv2-SCSI CCS and notify the device server that it is
abandoning the IKEv2-SCSI CCS as described in 5.13.4.10; and
b) the device server shall respond to the mismatch as follows:
A) if the IKEv2-SCSI header (see 7.7.3.4) specifies an attempt to provide authentication data for or
the deletion of an IKE-v2-SCSI CCS on the I_T_L nexus on which the command was received,
then the device server shall:
a) terminate the SECURITY PROTOCOL OUT command with CHECK CONDITION status, with
the sense key set to ILLEGAL REQUEST, and the additional sense code set to SA
CREATION PARAMETER VALUE REJECTED; and
b) continue the IKEv2-SCSI CCS by preparing to receive another Authentication step
SECURITY PROTOCOL OUT command;
or
B) if the IKEv2-SCSI header (see 7.7.3.4) specifies the deletion of an active SA, then the device
server shall terminate the SECURITY PROTOCOL OUT command with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
INVALID FIELD IN PARAMETER LIST.

Working Draft SCSI Primary Commands - 4 (SPC-4) 703

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.3.5.12 IKEv2-SCSI SA Creation Capabilities payload

The IKEv2-SCSI SA Creation Capabilities payload (see table 542) lists all the security algorithms that the
device server allows to be used in an IKEv2-SCSI CCS. Events that are outside the scope of this standard
may change the contents of the IKEv2-SCSI SA Creation Capabilities payload at any time.

Table 542 — IKEv2-SCSI SA Creation Capabilities payload format

Bit
7 6 5 4 3 2 1 0
Byte
0 NEXT PAYLOAD (00h)
1 CRIT Reserved
2 (MSB)
IKE PAYLOAD LENGTH (n+1)
3 (LSB)
4
5 Reserved
6
7 NUMBER OF ALGORITHM DESCRIPTORS

IKEv2-SCSI cryptographic algorithm descriptors

8
IKEv2-SCSI cryptographic algorithm descriptor
•• •
(see 7.7.3.6) [first]

••
•

IKEv2-SCSI cryptographic algorithm descriptor

•• •
(see 7.7.3.6) [last]
n

The NEXT PAYLOAD field, CRIT bit, and IKE PAYLOAD LENGTH field are described in 7.7.3.5.1.

The NEXT PAYLOAD field is set as shown in table 542 (i.e., No Next Payload) in the IKEv2-SCSI SA Creation
Capabilities payload.

The NUMBER OF ALGORITHM DESCRIPTORS field specifies the number of IKEv2-SCSI cryptographic algorithm
descriptors that follow in the IKEv2-SCSI SA Creation Capabilities payload.

Each IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6) describes one combination of security
algorithm and algorithm attributes that the device server allows to be used in an IKEv2-SCSI CCS. If more
than one set of algorithm attributes (e.g., key length) is allowed for any allowed security algorithm, then a
different SCSI cryptographic algorithms descriptor shall be included for each set of algorithm attributes.

The SCSI cryptographic algorithms descriptors shall be ordered by:

1) increasing algorithm type;

2) increasing algorithm identifier within the same algorithm type; and
3) increasing key length, if any, within the same algorithm identifier.

The algorithms allowed may be a subset of the algorithms supported by the device server.

704 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The method for changing which of the device server supported algorithms are allowed is outside the scope of
this standard. Any changes in allowed algorithms do not take effect until the new list is returned to any
application client in an IKEv2-SCSI SA Creation Capabilities payload.

7.7.3.5.13 IKEv2-SCSI SA Cryptographic Algorithms payload

The IKEv2-SCSI SA Cryptographic Algorithms payload (see table 543) lists the security algorithms that are
being used in the creation and management (e.g., deletion) of an SA using an IKEv2-SCSI CCS.

Table 543 — IKEv2-SCSI SA Cryptographic Algorithms payload format

Bit
7 6 5 4 3 2 1 0
Byte
0 NEXT PAYLOAD

1 CRIT Reserved
2 (MSB)
IKE PAYLOAD LENGTH (n+1)
3 (LSB)
4
•• • Reserved
13
14 (MSB)
USAGE DATA LENGTH (0000h)
15 (LSB)
16
•• • Reserved
19
20 NUMBER OF ALGORITHM DESCRIPTORS

IKEv2-SCSI cryptographic algorithm descriptors

21
IKEv2-SCSI cryptographic algorithm descriptor
•• •
(see 7.7.3.6) [first]

••
•

IKEv2-SCSI cryptographic algorithm descriptor

•• •
(see 7.7.3.6) [last]
n

The NEXT PAYLOAD field, CRIT bit, and IKE PAYLOAD LENGTH field are described in 7.7.3.5.1.

The USAGE DATA LENGTH field is set as shown in table 543 in the IKEv2-SCSI SA Cryptographic Algorithms
payload.

The NUMBER OF ALGORITHM DESCRIPTORS field specifies the number of IKEv2-SCSI cryptographic algorithm
descriptors that follow in the IKEv2-SCSI SA Cryptographic Algorithms payload. If a device server receives a
NUMBER OF ALGORITHM DESCRIPTORS field that is not set to six, then the error shall be processed as described
in 7.7.3.8.3.

Each IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6) describes one combination of security
algorithm and algorithm attributes to be used during the IKEv2-SCSI CCS.

Working Draft SCSI Primary Commands - 4 (SPC-4) 705

T10/BSR INCITS 513 Revision 37 17 May 2014

The IKEv2-SCSI cryptographic algorithm descriptors are ordered as follows:

1) one ENCR IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.2);

2) one PRF IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.3);
3) one INTEG IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.4);
4) one D-H IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.5);
5) one SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.6).
6) one SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.6).

If a device server receives an IKEv2-SCSI SA Cryptographic Algorithms payload that does not contain the
IKEv2-SCSI cryptographic algorithm descriptors described in this subclause in the order described in this
subclause, then the error shall be processed as described in 7.7.3.8.3.

If the device server receives an IKEv2-SCSI SA Cryptographic Algorithms payload that contains an ENCR
IKEv2-SCSI cryptographic algorithm descriptor with the ALGORITHM IDENTIFIER field set to ENCR_NULL, then
the error shall be processed as described in 7.7.3.8.3.

In the Key Exchange step SECURITY PROTOCOL IN parameter data (see 5.13.4.6.3), the device server
returns the IKEv2-SCSI SA Cryptographic Algorithms payload received during the Key Exchange step
SECURITY PROTOCOL OUT command (see 5.13.4.6.2) to confirm acceptance of the algorithms.

706 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7.3.5.14 IKEv2-SCSI SAUT Cryptographic Algorithms payload

The IKEv2-SCSI SAUT Cryptographic Algorithms payload (see table 544) lists the usage type of and security
algorithms to be used by the SA that is created as a result of an IKEv2-SCSI CCS.

Table 544 — IKEv2-SCSI SAUT Cryptographic Algorithms payload format

Bit
7 6 5 4 3 2 1 0
Byte
0 NEXT PAYLOAD

1 CRIT Reserved
2 (MSB)
IKE PAYLOAD LENGTH (n+1)
3 (LSB)
4
Reserved
11
12 (MSB)
SA TYPE
13 (LSB)
14 (MSB)
USAGE DATA LENGTH (j)
15 (LSB)
16
•• • USAGE DATA
16+j-1
16+j
16+j+1 Reserved
16+j+2
16+j+3 NUMBER OF ALGORITHM DESCRIPTORS

IKEv2-SCSI cryptographic algorithm descriptors

16+j+4
IKEv2-SCSI cryptographic algorithm descriptor
•• •
(see 7.7.3.6) [first]

•
••

IKEv2-SCSI cryptographic algorithm descriptor

•• •
(see 7.7.3.6) [last]
n

The NEXT PAYLOAD field, CRIT bit, and IKE PAYLOAD LENGTH field are described in 7.7.3.5.1.

The SA TYPE field specifies the usage type for the SA and is selected from among those listed in table 75 (see
5.13.2.2). An error shall be processed as described in 7.7.3.8.3 if any of the following conditions occur:

a) the device server receives an SA usage type that is not allowed by the device server;
b) an SA usage type between 8000h and BFFFh inclusive is received in a Key Exchange step
SECURITY PROTOCOL OUT command (see 5.13.4.6.2); or
c) an SA usage type between A000h and CFFFh inclusive is received for which the device server is
unable to verify the applicable usage type constraints.

Working Draft SCSI Primary Commands - 4 (SPC-4) 707

T10/BSR INCITS 513 Revision 37 17 May 2014

The method for changing which of the device server supported SA usage types are allowed is outside the
scope of this standard.

The USAGE DATA LENGTH field specifies number of bytes of usage data that follow.

The size and format of the usage data depends on the SA type (see table 75 in 5.13.2.2). If the device server
receives a USAGE DATA LENGTH field that contains a value that is inconsistent with the SA type, then the
error shall be processed as described in 7.7.3.8.3.

The USAGE DATA field contains information to be stored in the USAGE_DATA SA parameter if the SA is
generated (see 5.13.4.9).

The NUMBER OF ALGORITHM DESCRIPTORS field specifies the number of IKEv2-SCSI cryptographic algorithm
descriptors that follow in the IKEv2-SCSI SAUT Cryptographic Algorithms payload. If a device server receives
a NUMBER OF ALGORITHM DESCRIPTORS field that is not set to two, the error shall be processed as described
in 7.7.3.8.3.

Each IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6) describes one combination of security
algorithm and algorithm attributes to be used by the SA created as a result of the IKEv2-SCSI CCS. The
IKEv2-SCSI cryptographic algorithm descriptors are ordered as follows:

1) one ENCR IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.2); and

2) one INTEG IKEv2-SCSI cryptographic algorithm descriptor (see 7.7.3.6.4).

If a device server receives an IKEv2-SCSI SAUT Cryptographic Algorithms payload that does not contain the
IKEv2-SCSI cryptographic algorithm descriptors described in this subclause in the order described in this
subclause, then the error shall be processed as described in 7.7.3.8.3.

708 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7.3.5.15 IKEv2-SCSI Timeout Values payload

The IKEv2-SCSI Timeout Values payload (see table 545) specifies the timeout intervals associated with an
IKEv2-SCSI CCS

Table 545 — IKEv2-SCSI Timeout Values payload format

Bit
7 6 5 4 3 2 1 0
Byte
0 NEXT PAYLOAD

1 CRIT Reserved
2 (MSB)
IKE PAYLOAD LENGTH (0010h)
3 (LSB)
4
•• • Reserved
6
7 NUMBER OF TIMEOUT VALUES (02h)
8 (MSB)
•• • IKEV2-SCSI PROTOCOL TIMEOUT
11 (LSB)
12 (MSB)
•• • IKEV2-SCSI SA INACTIVITY TIMEOUT
15 (LSB)

The NEXT PAYLOAD field, CRIT bit, and IKE PAYLOAD LENGTH field are described in 7.7.3.5.1.

The NUMBER OF TIMEOUT VALUES field specifies the number of four-byte timeout values that follow. If the
number of timeout values is less than two, the IKEv2-SCSI CCS state maintained for the I_T_L nexus shall be
abandoned as described in 7.7.3.8.3.

The IKEV2-SCSI PROTOCOL TIMEOUT field specifies the number of seconds that the device server shall wait for
the next command in the IKEv2-SCSI CCS. If the timeout expires before the device server receives an
IKEv2-SCSI CCS command, the device server shall abandon the IKEv2-SCSI CCS as described in 5.13.4.10.

The IKEV2-SCSI SA INACTIVITY TIMEOUT field specifies the number of seconds that the device server shall wait for
the next command that uses an SA. This value is copied to the TIMEOUT SA parameter when the SA is
generated (see 5.13.4.9).

The device server shall replace any timeout value that is set to zero with a value of ten (i.e., ten seconds).

The maximum value for the protocol timeout should be long enough to allow the application client to continue
the IKEv2-SCSI CCS, but short enough that, if an incomplete IKEv2-SCSI CCS is abandoned, the device
server discards the state for that IKEv2-SCSI CCS and becomes available to for another IKEv2-SCSI CCS
without delays that have adverse effects.

Working Draft SCSI Primary Commands - 4 (SPC-4) 709

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.3.6 IKEv2-SCSI cryptographic algorithm descriptors

7.7.3.6.1 Overview

Each IKEv2-SCSI cryptographic algorithm descriptor (see table 546) specifies a cryptographic algorithm for
IKEv2-SCSI (e.g., an encryption algorithm, an integrity checking algorithm, a key generation algorithm, or an
authentication algorithm).

Table 546 — IKEv2-SCSI cryptographic algorithm descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 ALGORITHM TYPE

1 Reserved
2 (MSB)
IKE DESCRIPTOR LENGTH (000Ch)
3 (LSB)
4 (MSB)
•• • ALGORITHM IDENTIFIER
7 (LSB)
8
•• • ALGORITHM ATTRIBUTES
11

The ALGORITHM TYPE field (see table 547) specifies the type of cryptographic algorithm to which the
IKEv2-SCSI cryptographic algorithm descriptor applies.

Table 547 — ALGORITHM TYPE field

Code Name Description Reference

01h ENCR Encryption algorithm 7.7.3.6.2
02h PRF Pseudo-random function 7.7.3.6.3
03h INTEG Integrity algorithm 7.7.3.6.4
04h D-H Diffie-Hellman group 7.7.3.6.5
05h to F0h Restricted RFC 4306
IKEv2-SCSI authentication algorithm
F9h SA_AUTH_OUT 7.7.3.6.6
for SECURITY PROTOCOL OUT data
IKEv2-SCSI authentication algorithm
FAh SA_AUTH_IN 7.7.3.6.6
for SECURITY PROTOCOL IN data
All others Reserved

The IKE DESCRIPTOR LENGTH field specifies the total number of bytes in the IKEv2-SCSI SA Cryptographic
Algorithms descriptor and shall be set as shown in table 546 in all the IKEv2-SCSI SA Cryptographic
Algorithms descriptors summarized in table 547.

NOTE 55 - The contents of the IKE DESCRIPTOR LENGTH field differ from those found in most SCSI length
fields, However, they are consistent with the IKEv2 usage (see RFC 4306).

710 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The contents of the ALGORITHM IDENTIFIER field and ALGORITHM ATTRIBUTES field depend on the contents of the
ALGORITHM TYPE field (see table 547). The ALGORITHM ATTRIBUTES field is reserved in some IKEv2-SCSI SA
Cryptographic Algorithms descriptor formats.

7.7.3.6.2 ENCR IKEv2-SCSI cryptographic algorithm descriptor

If the ALGORITHM TYPE field is set to ENCR (i.e., 01h) in an IKEv2-SCSI cryptographic algorithm descriptor (see
table 548), then the descriptor specifies an encryption algorithm to be applied during the IKEv2-SCSI
Authentication step (see 5.13.4.7), SA deletion operation (see 5.13.4.11), and when the SA created by the
IKEv2-SCSI is applied to user data.

Table 548 — ENCR IKEv2-SCSI cryptographic algorithm descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 ALGORITHM TYPE (01h)
1 Reserved
2 (MSB)
IKE DESCRIPTOR LENGTH (000Ch)
3 (LSB)
4 (MSB)
•• • ALGORITHM IDENTIFIER
7 (LSB)
8
Reserved
9
10 (MSB)
KEY LENGTH
11 (LSB)

The ALGORITHM TYPE field and IKE DESCRIPTOR LENGTH field are described in 7.7.3.6.1, and shall be set as
shown in table 548 for the ENCR IKEv2-SCSI cryptographic algorithm descriptor.

Working Draft SCSI Primary Commands - 4 (SPC-4) 711

T10/BSR INCITS 513 Revision 37 17 May 2014

The ALGORITHM IDENTIFIER field (see table 549) specifies the encryption algorithm to which the ENCR
IKEv2-SCSI cryptographic algorithm descriptor applies.

Table 549 — ENCR ALGORITHM IDENTIFIER field

Salt
bytes IV a Align- Key
length length ment b length
Code Description (bytes) (bytes) (bytes) (bytes) Support Reference
8001 000Bh ENCR_NULL n/a 0 4 0 Mandatory RFC 2410
16 Optional
8001 000Ch AES-CBC n/a 16 16 24 Prohibited RFC 3602
32 Optional
16 Optional
AES-CCM RFC 4309
8001 0010h with a 16-byte 3 8 4 24 Prohibited and
MAC RFC 5282
32 Optional
16 Optional
AES-GCM RFC 4106
8001 0014h with a 16-byte 4 8 4 24 Prohibited and
MAC 32 Optional RFC 5282

8001 0400h to
Vendor Specific
8001 FFFFh
0000 0000h to
Restricted IANA
0000 FFFFh
All other values Reserved
a Initialization Vector.
b
The alignment required in the plaintext prior to encryption..

ENCR_NULL indicates that encryption shall not be applied when the SA created by the IKEv2-SCSI is applied
to user data.

The IKEv2-SCSI CCS state maintained for the I_T_L nexus shall be abandoned and an error shall be
processed as described in 7.7.3.8.3 if the parameter list contains an IKEv2-SCSI SA Cryptographic
Algorithms payload (see 7.7.3.5.13) that contains:

a) an ENCR IKEv2-SCSI cryptographic algorithm descriptor with the ALGORITHM IDENTIFIER field set to
ENCR_NULL;
b) the following combination of IKEv2-SCSI cryptographic algorithm descriptors (see 7.7.3.6.4):
A) an INTEG IKEv2-SCSI cryptographic algorithm descriptor with the ALGORITHM IDENTIFIER field set
to a value other than AUTH_COMBINED; and
B) an ENCR IKEv2-SCSI cryptographic algorithm descriptor with the ALGORITHM IDENTIFIER field set
to a value that table 549 describes as requiring AUTH_COMBINED as the integrity check
algorithm;
or
c) the following combination of IKEv2-SCSI cryptographic algorithm descriptors:
A) an INTEG IKEv2-SCSI cryptographic algorithm descriptor with the ALGORITHM IDENTIFIER field set
to AUTH_COMBINED; and

712 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

B) an ENCR IKEv2-SCSI cryptographic algorithm descriptor with the ALGORITHM IDENTIFIER field set
to a value that table 549 does not describe as requiring AUTH_COMBINED as the integrity check
algorithm.

The KEY LENGTH field specifies the number of bytes in the shared key for the encryption algorithm to which the
ENCR IKEv2-SCSI cryptographic algorithm descriptor applies.

The IKEv2-SCSI CCS state maintained for the I_T_L nexus shall be abandoned as described in 7.7.3.8.3 if
the parameter list contains:

a) no ENCR IKEv2-SCSI cryptographic algorithm descriptors;

b) more than one ENCR IKEv2-SCSI cryptographic algorithm descriptor;
c) an ENCR IKEv2-SCSI cryptographic algorithm descriptor that does not appear in the SA Creations
Capabilities payload (see 7.7.3.5.12) last returned by the device server to any application client (i.e.,
an ENCR IKEv2-SCSI cryptographic algorithm descriptor for a combination of algorithm identifier and
key length that the device server has not reported as one of its SA creation capabilities); or
d) an ENCR IKEv2-SCSI cryptographic algorithm descriptor that contains:
A) an algorithm identifier that is not shown in table 549; or
B) a key length that:
a) does not match one of the values shown in table 549; or
b) is not supported by the device server.

7.7.3.6.3 PRF IKEv2-SCSI cryptographic algorithm descriptor

If the ALGORITHM TYPE field is set to PRF (i.e., 02h) in an IKEv2-SCSI cryptographic algorithm descriptor (see
table 550), then the descriptor specifies the pseudo-random function and KDF to be used during the Key
Exchange step completion (see 5.13.4.6.4).

Table 550 — PRF IKEv2-SCSI cryptographic algorithm descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 ALGORITHM TYPE (02h)
1 Reserved
2 (MSB)
IKE DESCRIPTOR LENGTH (000Ch)
3 (LSB)
4 (MSB)
•• • ALGORITHM IDENTIFIER
7 (LSB)
8
•• • Reserved
11

The ALGORITHM TYPE field and IKE DESCRIPTOR LENGTH field are described in 7.7.3.6.1, and shall be set as
shown in table 550 for the PRF IKEv2-SCSI cryptographic algorithm descriptor.

Working Draft SCSI Primary Commands - 4 (SPC-4) 713

T10/BSR INCITS 513 Revision 37 17 May 2014

The ALGORITHM IDENTIFIER field (see table 551) specifies PRF and KDF to which the PRF IKEv2-SCSI
cryptographic algorithm descriptor applies.

Table 551 — PRF ALGORITHM IDENTIFIER field

Output Reference
length
Code Description Support (bytes) PRF a KDF b
8002 0002h IKEv2-use based on SHA-1 Optional 20 RFC 2104 5.13.3.3
8002 0004h IKEv2-use based on AES-128 Optional 16 RFC 4434 5.13.3.4
in CBC mode
8002 0005h IKEv2-use based on SHA-256 Optional 32 RFC 4868 5.13.3.3
8002 0007h IKEv2-use based on SHA-512 Optional 64 RFC 4868 5.13.3.3
8002 0400h to
Vendor Specific
8002 FFFFh
0000 0000h to
Restricted IANA
0000 FFFFh
All others Reserved
a PRFs are equivalent to the prf() functions defined in RFC 4306.
b
KDFs are equivalent to the prf+() functions defined in RFC 4306.

The IKEv2-SCSI CCS state maintained for the I_T_L nexus shall be abandoned as described in 7.7.3.8.3 if
the parameter list contains:

a) no PRF IKEv2-SCSI cryptographic algorithm descriptors;

b) more than one PRF IKEv2-SCSI cryptographic algorithm descriptor;
c) a PRF IKEv2-SCSI cryptographic algorithm descriptor that contains an algorithm identifier that does
not appear in the SA Creations Capabilities payload (see 7.7.3.5.12) last returned by the device
server to any application client; or
d) an PRF IKEv2-SCSI cryptographic algorithm descriptor that contains an algorithm identifier that is not
shown in table 551.

714 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7.3.6.4 INTEG IKEv2-SCSI cryptographic algorithm descriptor

If the ALGORITHM TYPE field is set to INTEG (i.e., 03h) in an IKEv2-SCSI cryptographic algorithm descriptor
(see table 552), then the descriptor specifies an integrity checking (i.e., data authentication) algorithm to be
applied during the IKEv2-SCSI Authentication step (see 5.13.4.7) and when the SA created by the
IKEv2-SCSI is applied to user data.

Table 552 — INTEG IKEv2-SCSI cryptographic algorithm descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 ALGORITHM TYPE (03h)
1 Reserved
2 (MSB)
IKE DESCRIPTOR LENGTH (000Ch)
3 (LSB)
4 (MSB)
•• • ALGORITHM IDENTIFIER
7 (LSB)
8
•• • Reserved
11

The ALGORITHM TYPE field and IKE DESCRIPTOR LENGTH field are described in 7.7.3.6.1, and shall be set as
shown in table 552 for the INTEG IKEv2-SCSI cryptographic algorithm descriptor.

The ALGORITHM IDENTIFIER field (see table 553) specifies integrity checking algorithm and shared key length to
which the INTEG IKEv2-SCSI cryptographic algorithm descriptor applies.

Table 553 — INTEG ALGORITHM IDENTIFIER field

ICV a Key
length length
Code IKEv2 Name (bytes) (bytes) Support Reference
8003 0002h AUTH_HMAC_SHA1_96 12 20 Optional RFC 2404
8003 000Ch AUTH_HMAC_SHA2_256_128 16 32 Optional RFC 4868
8003 000Eh AUTH_HMAC_SHA2_512_256 32 64 Optional RFC 4868
F003 0001h AUTH_COMBINED n/a 0 Optional this
subclause
8003 0400h to
Vendor Specific
8003 FFFFh
0000 0000h to
Restricted IANA
0000 FFFFh
All others Reserved
a Integrity Check Value.

Working Draft SCSI Primary Commands - 4 (SPC-4) 715

T10/BSR INCITS 513 Revision 37 17 May 2014

The AUTH_COMBINED integrity checking algorithm is used with encryption algorithms that include integrity
checking as described in 7.7.3.6.2. The AUTH_COMBINED algorithm identifier specifies that no additional
integrity check is performed, as indicated by the zero-length key.

The key length used with an integrity checking algorithm is determined by the algorithm identifier as shown in
table 553.

The IKEv2-SCSI CCS state maintained for the I_T_L nexus shall be abandoned as described in 7.7.3.8.3 if
the parameter list contains:

a) no INTEG IKEv2-SCSI cryptographic algorithm descriptors;

b) more than one INTEG IKEv2-SCSI cryptographic algorithm descriptor;
c) an INTEG IKEv2-SCSI cryptographic algorithm descriptor that contains an algorithm identifier that
does not appear in the SA Creations Capabilities payload (see 7.7.3.5.12) last returned by the device
server to any application client; or
d) an INTEG IKEv2-SCSI cryptographic algorithm descriptor that contains an algorithm identifier that is
not shown in table 553.

7.7.3.6.5 D-H IKEv2-SCSI cryptographic algorithm descriptor

If the ALGORITHM TYPE field is set to D-H (i.e., 04h) in an IKEv2-SCSI cryptographic algorithm descriptor (see
table 554), then the descriptor specifies Diffie-Hellman group and Diffie-Hellman algorithm used during the
IKEv2-SCSI Key Exchange step (see 5.13.4.6) to derive a shared key that is known only to the application
client and device server.

Table 554 — D-H IKEv2-SCSI cryptographic algorithm descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 ALGORITHM TYPE (04h)
1 Reserved
2 (MSB)
IKE DESCRIPTOR LENGTH (000Ch)
3 (LSB)
4 (MSB)
•• • ALGORITHM IDENTIFIER
7 (LSB)
8
•• • Reserved
11

The ALGORITHM TYPE field and IKE DESCRIPTOR LENGTH field are described in 7.7.3.6.1, and shall be set as
shown in table 554 for the D-H IKEv2-SCSI cryptographic algorithm descriptor.

716 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The ALGORITHM IDENTIFIER field (see table 555) specifies Diffie-Hellman algorithm, group, and shared key
length to which the D-H IKEv2-SCSI cryptographic algorithm descriptor applies.

Table 555 — D-H ALGORITHM IDENTIFIER field

Key
length
Code Description (bytes) Support Reference
8004 000Eh 2 048-bit MODP group (finite field D-H) 256 Optional RFC 3526
8004 000Fh 3 072-bit MODP group (finite field D-H) 384 Optional RFC 3526
8004 0010h 4 096-bit MODP group (finite field D-H) 512 Optional RFC 3526
8004 0013h 256-bit random ECP group 64 Optional RFC 4753 a
8004 0015h 521-bit random ECP group 132 Optional RFC 4753 a
8004 0400h to
Vendor Specific
8004 FFFFh
0000 0000h to
Restricted IANA
0000 FFFFh
All others Reserved
a
The RFC Errata for RFC 4753 modify the binary representation of ECP key exchange data. The
modified binary representation shall be used, see http://rfc-editor.org/errata_search.php?rfc=4753.

The key length of the public value transferred in the KEY EXCHANGE DATA field (see 7.7.3.5.3) is determined by
the algorithm identifier as shown in table 555.

The IKEv2-SCSI CCS state maintained for the I_T_L nexus shall be abandoned as described in 7.7.3.8.3 if
the parameter list contains:

a) no D-H IKEv2-SCSI cryptographic algorithm descriptors;

b) more than one D-H IKEv2-SCSI cryptographic algorithm descriptor;
c) a D-H IKEv2-SCSI cryptographic algorithm descriptor that contains an algorithm identifier that does
not appear in the SA Creations Capabilities payload (see 7.7.3.5.12) last returned by the device
server to any application client; or
d) an D-H IKEv2-SCSI cryptographic algorithm descriptor that contains an algorithm identifier that is not
shown in table 555.

Working Draft SCSI Primary Commands - 4 (SPC-4) 717

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.3.6.6 IKEv2-SCSI authentication algorithm IKEv2-SCSI cryptographic algorithm descriptor

If the ALGORITHM TYPE field is set to SA_AUTH_OUT (i.e., F9h) in an IKEv2-SCSI cryptographic algorithm
descriptor (see table 556), then the descriptor specifies Authentication payload authentication algorithm used
by the IKEv2-SCSI Authentication step SECURITY PROTOCOL OUT command (see 5.13.4.7.2).

If the ALGORITHM TYPE field is set to SA_AUTH_IN (i.e., FAh) in an IKEv2-SCSI cryptographic algorithm
descriptor (see table 556), then the descriptor specifies Authentication payload authentication algorithm used
by the IKEv2-SCSI Authentication step SECURITY PROTOCOL IN command (see 5.13.4.7.3).

Table 556 — SA_AUTH_OUT and SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 ALGORITHM TYPE (F9h or FAh)
1 Reserved
2 (MSB)
IKE DESCRIPTOR LENGTH (000Ch)
3 (LSB)
4 (MSB)
•• • ALGORITHM IDENTIFIER
7 (LSB)
8
•• • Reserved
11

The ALGORITHM TYPE field and IKE DESCRIPTOR LENGTH field are described in 7.7.3.6.1. The IKE DESCRIPTOR
LENGTH field shall be set as shown in table 556 for the SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm
descriptor and the SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptor.

718 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The ALGORITHM IDENTIFIER field (see table 557) specifies Authentication payload authentication algorithm to
which the SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor or SA_AUTH_IN IKEv2-SCSI
cryptographic algorithm descriptor applies.

Table 557 — SA_AUTH_OUT and SA_AUTH_IN ALGORITHM IDENTIFIER field

Authentication
Code Description Support Reference Reference a
00F9 0000h SA_AUTH_NONE Optional this subclause n/a
00F9 0001h RSA Digital Signature with SHA-1 b
Optional RFC 4306 5.13.4.3.3
00F9 0002h Shared Key Message Integrity Code Optional RFC 4306 c, d 5.13.4.3.2
00F9 0009h ECDSA with SHA-256 on the P-256 RFC 4754 5.13.4.3.3
Optional
curve b
00F9 000Bh ECDSA with SHA-512 on the P-521 RFC 4754 5.13.4.3.3
Optional
curve b
00F9 00C9h to
Vendor Specific Optional
00F9 00FFh
0000 0000h to Restricted Prohibited IANA
0000 FFFFh
All others Reserved
a
Description of how the algorithm shall be used to generate and verify the contents of the
AUTHENTICATION DATA field of the Authentication Payload.
b
Support for an RSA Digital Signature authentication algorithm does not mandate support for digital
certificates.
c The 17 ASCII character non-terminated pre-shared key pad string 'Key Pad for IKEv2' specified by RFC

4306 is replaced by the 22 ASCII character non-terminated pre-shared key pad string 'Key Pad for
IKEv2-SCSI'.
d The pre-shared key requirements used by this standard (see 5.13.4.3.2) apply in addition to those found

in RFC 4306.

SA_AUTH_NONE specifies the omission of the IKEv2-SCSI Authentication step (see 5.13.4.7) as follows:

a) the presence of an SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor and an

SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptor with the ALGORITHM IDENTIFIER field set
to SA_AUTH_NONE is an SA Creation Capabilities payload (see 7.7.3.5.12) indicates that the device
server is allowed to negotiate the omission of the IKEv2-SCSI Authentication step; and
b) the presence of an SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor and an
SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptor with the ALGORITHM IDENTIFIER field set
to SA_AUTH_NONE is an IKEv2-SCSI SA Cryptographic Algorithms payload (see 7.7.3.5.13)
indicates the following based upon the command whose parameter data carries the payload:
A) in the parameter list for a Key Exchange SECURITY PROTOCOL OUT command (see
5.13.4.6.2), SA_AUTH_NONE specifies that the application client is requesting that the
IKEv2-SCSI Authentication step be skipped; and
B) in the parameter data for a Key Exchange SECURITY PROTOCOL IN command (see 5.13.4.6.3),
SA_AUTH_NONE indicates that the device server has agreed to skip the IKEv2-SCSI
Authentication step.

Working Draft SCSI Primary Commands - 4 (SPC-4) 719

T10/BSR INCITS 513 Revision 37 17 May 2014

If the device server indicates that skipping the Authentication step is allowed in its capabilities and the
application client specifies that the Authentication step be skipped (see 5.13.4.3.4), then the IKEv2-SCSI
Authentication step is skipped and the resulting SAs are not authenticated.

An SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor with the ALGORITHM IDENTIFIER field set to
SA_AUTH_NONE shall not appear in an IKEv2-SCSI SA Cryptographic Algorithms payload except as
described in 5.13.4.3.4.

The Shared Key Message Integrity Code is based on a pre-shared key (see 5.13.4.3.2) that is associated with
the identity in the Identification payload (see 7.7.3.5.4).

The IKEv2-SCSI CCS state maintained for the I_T_L nexus shall be abandoned as described in 7.7.3.8.3 if
the parameter list contains:

a) no SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptors;

b) no SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptors;
c) more than one SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor;
d) more than one SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptor;
e) an SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor that contains an algorithm
identifier that does not appear in the SA Creations Capabilities payload (see 7.7.3.5.12) last returned
by the device server to any application client;
f) an SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptor that contains an algorithm identifier
that does not appear in the SA Creations Capabilities payload last returned by the device server to
any application client;
g) an SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor that contains an algorithm
identifier that is not shown in table 557;
h) an SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptor that contains an algorithm identifier
that is not shown in table 557;
i) an SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor with the ALGORITHM IDENTIFIER
field set to SA_AUTH_NONE, and an SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptor
with the ALGORITHM IDENTIFIER field set to a value other than SA_AUTH_NONE; or
j) an SA_AUTH_IN IKEv2-SCSI cryptographic algorithm descriptor with the ALGORITHM IDENTIFIER field
set to SA_AUTH_NONE, and an SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor
with the ALGORITHM IDENTIFIER field set to a value other than SA_AUTH_NONE.

720 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7.3.7 Errors in IKEv2-SCSI security protocol commands

For a single I_T_L nexus, the device server shall ensure that two or four IKEv2-SCSI CCS commands are
processed in the order described in 5.13.4.1 as shown in table 558. For each SECURITY PROTOCOL OUT
command shown in table 558, the parameter data shall not be processed unless table 558 specifies that the
command is processed.

Table 558 — IKEv2-SCSI command ordering processing requirements on a single I_T_L nexus (part 1
of 2)

Time

Before Key After a Key After a Key After an After an

Exchange Exchange Exchange Authentica- Authentica-
step step step tion step tion step
IKEv2-SCSI SECURITY SECURITY SECURITY SECURITY SECURITY
SECURITY PROTOCOL PROTOCOL PROTOCOL PROTOCOL PROTOCOL
PROTOCOL OUT OUT OUT IN command OUT IN command
command or command command completes command completes
SECURITY completes completes with GOOD completes with GOOD
PROTOCOL IN with GOOD with GOOD status with GOOD status
command received status status status
Same as
before Key
Key Exchange step Process the Exchange
Do not Do not Do not
SECURITY command as step
process the process the process the
PROTOCOL OUT described in SECURITY
command a command a command a
command this standard PROTOCOL
OUT
command
Key Exchange step Process the Repeat
No Do not Do not
SECURITY command as processing
IKEv2-SCSI process the process the
PROTOCOL IN described in of the
CCS exists b command a command a
command this standard command c
a The command shall be terminated and the IKEv2-SCSI CCS shall be continued as follows:
a) the device server shall terminate the command with CHECK CONDITION status, with the sense
key set to NOT READY, and the additional sense code set to LOGICAL UNIT NOT READY, SA
CREATION IN PROGRESS; and
b) the device server shall continue the IKEv2-SCSI CCS by preparing to receive another
IKEv2-SCSI CCS SECURITY PROTOCOL OUT command.
b
The device server shall terminate the command with CHECK CONDITION status, with the sense key
set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.
c
Processing of the SECURITY PROTOCOL IN commands in an IKEv2-SCSI CCS may be repeated.
The device server should save the information necessary to repeat processing of these commands
until the number of seconds specified in the IKEV2-SCSI PROTOCOL TIMEOUT field of the IKEv2-SCSI
Timeout Values payload (see 7.7.3.5.15) have elapsed since the processing of the Authentication step
SECURITY PROTOCOL OUT command that completed with GOOD status.

Working Draft SCSI Primary Commands - 4 (SPC-4) 721

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 558 — IKEv2-SCSI command ordering processing requirements on a single I_T_L nexus (part 2
of 2)

Time

Before Key After a Key After a Key After an After an

Exchange Exchange Exchange Authentica- Authentica-
step step step tion step tion step
IKEv2-SCSI SECURITY SECURITY SECURITY SECURITY SECURITY
SECURITY PROTOCOL PROTOCOL PROTOCOL PROTOCOL PROTOCOL
PROTOCOL OUT OUT OUT IN command OUT IN command
command or command command completes command completes
SECURITY completes completes with GOOD completes with GOOD
PROTOCOL IN with GOOD with GOOD status with GOOD status
command received status status status

Authentication step Process the

Do not Do not Do not
SECURITY command as
process the process the process the
PROTOCOL OUT described in
No command a command a command a
command this standard
IKEv2-SCSI
Authentication step CCS exists b Do not Do not
Process the Repeat
SECURITY command as processing
process the process the
PROTOCOL IN described in of the
command a command a
command this standard command c

Command with an No Do not Do not Do not No

invalid field in the IKEv2-SCSI process the process the process the IKEv2-SCSI
CDB CCS exists b command a command a command a CCS exists b
a The command shall be terminated and the IKEv2-SCSI CCS shall be continued as follows:
a) the device server shall terminate the command with CHECK CONDITION status, with the sense
key set to NOT READY, and the additional sense code set to LOGICAL UNIT NOT READY, SA
CREATION IN PROGRESS; and
b) the device server shall continue the IKEv2-SCSI CCS by preparing to receive another
IKEv2-SCSI CCS SECURITY PROTOCOL OUT command.
b
The device server shall terminate the command with CHECK CONDITION status, with the sense key
set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.
c
Processing of the SECURITY PROTOCOL IN commands in an IKEv2-SCSI CCS may be repeated.
The device server should save the information necessary to repeat processing of these commands
until the number of seconds specified in the IKEV2-SCSI PROTOCOL TIMEOUT field of the IKEv2-SCSI
Timeout Values payload (see 7.7.3.5.15) have elapsed since the processing of the Authentication step
SECURITY PROTOCOL OUT command that completed with GOOD status.

The processing shown in table 558 shall be performed before parameter data error handling described in
7.7.3.8.

722 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7.3.8 Errors in IKEv2-SCSI security protocol parameter data

7.7.3.8.1 Overview

Errors in the parameter data transferred to the device server by an IKEv2-SCSI SECURITY PROTOCOL OUT
command are classified (see table 559) based on the ease with which they may be used to mount denial of
service attacks against IKEv2-SCSI SA creation operations by an attacker that has not participated
as the application client or device server in the Key Exchange step SECURITY PROTOCOL OUT command
(see 5.13.4.6.2) that started the IKEv2-SCSI CCS.

Table 559 — IKEv2-SCSI parameter error categories

Denial of service Applicable SECURITY

attack potential PROTOCOL OUT
commands Error handling description Reference

High a Authentication step, and If the device sever is able to, 7.7.3.8.2
Delete operation the IKEv2-SCSI CCS state
maintained for an I_T_L nexus
is not changed
Low b Key Exchange step, The IKEv2-SCSI CCS state 7.7.3.8.3
Authentication step, and maintained for an I_T_L nexus
Delete operation is abandoned
a
Attacks capable of causing significant harm by sending a malformed IKEv2-SCSI SECURITY
PROTOCOL OUT command to the device server.
b Attacks that produce no significant harm, or collusive attacks (i.e., attacks that require knowledge

of the IKEv2-SCSI CCS shared keys and participation in the IKEv2-SCSI CCS). Collusive attacks
depend on collusion between the attacker and the application client (i.e., require the application
client to act against its own best interests). The device server may abandon the IKEv2-SCSI CCS
in response to such attacks.

7.7.3.8.2 Errors with high denial of service attack potential

Errors detected before or during the decryption and integrity checking of an Encrypted payload in an
Authentication step SECURITY PROTOCOL OUT command or a Delete operation SECURITY PROTOCOL
OUT command have a high potential for being a denial of service attack against one or more application
clients (see table 559 in 7.7.3.8.1).

The device server shall respond to these SECURITY PROTOCOL OUT command errors as follows:

a) the device server shall terminate the command with CHECK CONDITION status, with the sense key
set to ILLEGAL REQUEST, and the additional sense code set to SA CREATION PARAMETER
VALUE REJECTED; and
b) the device server shall continue the IKEv2-SCSI CCS, if any, by preparing to receive an
Authentication step SECURITY PROTOCOL OUT command.

If a specific field is the cause for returning the SA CREATION PARAMETER VALUE REJECTED additional
sense code, then the SKSV bit may be set to one. If the SKSV bit is set to one, then the SENSE KEY SPECIFIC field
shall be set as defined in 4.5.2.4.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 723

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.3.8.3 Errors with low denial of service attack potential

The errors that have low denial of service attack potential for IKEv2-SCSI SA creation (see table 559 in
7.7.3.8.1) are:

a) all errors detected for a Key Exchange step SECURITY PROTOCOL OUT command or its associated
parameter data (e.g., errors detected in the IKEv2-SCSI header) that is attempting to establish a new
IKEv2-SCSI CCS on an I_T_L nexus; and
b) all errors that are detected after the Encrypted payload has been successfully decrypted and integrity
checked in an Authentication step SECURITY PROTOCOL OUT command (see 5.13.4.7.2) or a
Delete operation SECURITY PROTOCOL OUT command (see 5.13.4.11).

The device server shall respond to these SECURITY PROTOCOL OUT command errors by terminating the
command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to SA CREATION PARAMETER VALUE INVALID. The state being maintained for an
IKEv2-SCSI CCS on the I_T_L nexus on which the command was received, if any, shall be abandoned (see
5.13.4.10).

If a specific field is the cause for returning the SA CREATION PARAMETER VALUE INVALID additional sense
code, then the SKSV bit shall be set to one and SENSE KEY SPECIFIC field shall be set as defined in 4.5.2.4.2.

7.7.3.9 Translating IKEv2 errors

IKEv2 (see RFC 4306) defines an error reporting mechanism based on the Notify payload. This standard
translates such error reports into the device server and application actions defined in this subclause.

If a device server is required by IKEv2 to report an error using a Notify payload, the device server shall
translate the error into CHECK CONDITION status with the sense key and additional sense code as shown in
table 560. The device server shall terminate the SECURITY PROTOCOL OUT command (see 6.41) that
transferred the parameter list in which the IKE requirements for one or more payloads (see 7.7.3.5) require

724 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

use of the Notify payload to report an error. The device server shall terminate the SECURITY PROTOCOL
OUT command as described in this subclause. The device server shall not report the IKE errors described in
this subclause by terminating a SECURITY PROTOCOL IN command (see 6.40) with CHECK CONDITION
status.

Table 560 — IKEv2 Notify payload error translations for IKEv2-SCSI

IKEv2 (see RFC 4306) IKEv2-SCSI

Error Type Description Additional sense code Sense key

0000h Reserved
0001h UNSUPPORTED_CRITICAL_ SA CREATION PARAMETER
PAYLOAD NOT SUPPORTED
0004h INVALID_IKE_SPI SA CREATION PARAMETER
0005h INVALID_MAJOR_VERSION VALUE INVALID
or
0007h INVALID_SYNTAX a SA CREATION PARAMETER ILLEGAL REQUEST
0009h INVALID_MESSAGE_ID VALUE REJECTED
000Bh INVALID_SPI SA CREATION PARAMETER
VALUE INVALID b
000Eh NO_PROPOSAL_CHOSEN c SA CREATION PARAMETER
0011h INVALID_KE_PAYLOAD c VALUE INVALID
0018h AUTHENTICATION_FAILED AUTHENTICATION FAILED ABORTED COMMAND
d
0022h to See RFC 4306 n/a n/a
0027h
2000h to Vendor Specific
3FFFh
All others Restricted (see RFC 4306)
a This sense key and one of the additional sense codes shown shall be returned for a syntax error within
an Encrypted payload (see 7.7.3.5.11) regardless of conflicting IKEv2 requirements.
b
SA CREATION PARAMETER VALUE INVALID shall be used for an invalid SAI in an IKEv2-SCSI
SECURITY PROTOCOL IN or SECURITY PROTOCOL OUT. The additional sense code for an invalid
SAI in all other commands is specified by the applicable usage type definition (see table 75 in 5.13.2.2).
c
An application client recovers by restarting processing with the Device Capabilities step (see 5.13.4.5)
to rediscover the device server's capabilities.
d
These IKEv2 Error Types are used for features that are not supported by IKEv2-SCSI SA creation.

If an application client detects an IKEv2 error that RFC 4306 requires to be reported with a Notify payload, the
application client should abandon the IKEv2-SCSI CCS and notify the device server that it is abandoning the
IKEv2-SCSI CCS as described in 5.13.4.10.

Working Draft SCSI Primary Commands - 4 (SPC-4) 725

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.4 CbCS security protocol

7.7.4.1 Overview

If the SECURITY PROTOCOL field in a SECURITY PROTOCOL IN command (see 6.40) is set to 07h, the
command specifies one of the CbCS pages (see 7.7.4.2) to be returned by the device server. The information
returned by a CbCS SECURITY PROTOCOL IN command indicates the CbCS operating parameters of:

a) the logical unit to which the CbCS SECURITY PROTOCOL IN command is addressed; or
b) the SCSI target device that contains the well-known logical unit to which the CbCS SECURITY
PROTOCOL IN command is addressed.

If the SECURITY PROTOCOL field in a SECURITY PROTOCOL OUT command (see 6.41) is set to 07h, the
command specifies one of the CbCS pages (see 7.7.4.4) to be sent to the device server. The information sent
in a CbCS SECURITY PROTOCOL OUT command specifies the CbCS operating parameters of:

a) the logical unit to which the CbCS SECURITY PROTOCOL OUT command is addressed; or
b) the SCSI target device that contains the well-known logical unit to which the CbCS SECURITY
PROTOCOL OUT command is addressed.

7.7.4.2 CbCS SECURITY PROTOCOL IN CDB description

The CbCS SECURITY PROTOCOL IN CDB has the format defined in 6.40 with the additional requirements
described in this subclause.

If the SECURITY PROTOCOL field is set to CbCS (i.e., 07h) in a SECURITY PROTOCOL IN command, the
SECURITY PROTOCOL SPECIFIC field (see table 561) specifies the CbCS page to be returned in the parameter
data (see 7.7.4.3). If the CBCS bit is set to one in the Extended INQUIRY Data VPD page (see 7.8.7), the
CbCS SECURITY PROTOCOL IN command support requirements are shown in table 561.

Table 561 — SECURITY PROTOCOL SPECIFIC field for the CbCS SECURITY PROTOCOL IN command

Code a CbCS page returned Support Reference

0000h Supported CbCS SECURITY PROTOCOL IN Pages Mandatory 7.7.4.3.1
0001h Supported CbCS SECURITY PROTOCOL OUT Pages Mandatory 7.7.4.3.2
0002h Unchangeable CbCS Parameters Mandatory 7.7.4.3.3
0003h to 003Eh Reserved
003Fh Security Token See b 7.7.4.3.4
0040h Current CbCS Parameters Mandatory 7.7.4.3.5
0041h to D00Fh Reserved
D010h Set Master Key – Seed Exchange See b 7.7.4.3.6
D011h to FFFFh Reserved
a
If the SECURITY PROTOCOL SPECIFIC field is set to a value that is less than D000h, the working key
specified by the KEY VERSION field in the CbCS capability descriptor (see 6.26.2.3) shall be used to
compute the capability key (see 5.13.6.7.12). If the SECURITY PROTOCOL SPECIFIC field is set to a value
that is greater than or equal to D000h, the authentication key component of the master key (see
5.13.6.7.11) shall be used to compute the capability key.
b
Mandatory if the CAPKEY CbCS method (see 5.13.6.7.8.3) is supported.

726 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If a CbCS SECURITY PROTOCOL IN command is received with the INC_512 bit set to one, the device server
shall terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST,
and the additional sense code set to INVALID FIELD IN CDB.

7.7.4.3 CbCS SECURITY PROTOCOL IN parameter data

7.7.4.3.1 Supported CbCS SECURITY PROTOCOL IN Pages CbCS page

The Supported CbCS SECURITY PROTOCOL IN Pages CbCS page (see table 562) lists the CbCS pages
that are supported (i.e., the values that are allowed in the SECURITY PROTOCOL SPECIFIC field) for the
SECURITY PROTOCOL IN command (see 6.40).

Table 562 — Supported CbCS SECURITY PROTOCOL IN Pages CbCS page format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PAGE CODE (0000h)
1 (LSB)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Supported CbCS SECURITY PROTOCOL IN page list
4 (MSB) SUPPORTED CBCS SECURITY PROTOCOL IN PAGE
5 (0000h) [first] (LSB)
•
••

n-1 (MSB) SUPPORTED CBCS SECURITY PROTOCOL IN PAGE

n [last] (LSB)

The PAGE CODE field shall be set as shown in table 562 to indicate that the Supported CbCS SECURITY
PROTOCOL IN Pages CbCS page is being returned.

The PAGE LENGTH field indicates the number of bytes that follow in the Supported CbCS SECURITY
PROTOCOL IN Pages CbCS page.

Each SUPPORTED CBCS SECURITY PROTOCOL IN PAGE field indicates the page code (see table 561 in 7.7.4.2) of
one CbCS page that is supported by the SECURITY PROTOCOL IN command if the SECURITY PROTOCOL field
(see 6.40) is set to 07h (i.e., CbCS). The values in the SUPPORTED CBCS SECURITY PROTOCOL IN PAGE fields
shall be returned in ascending order beginning with 0000h (i.e., this CbCS page).

7.7.4.3.2 Supported CbCS SECURITY PROTOCOL OUT pages CbCS page

The Supported CbCS SECURITY PROTOCOL OUT Pages CbCS page (see table 563) lists the CbCS pages
that are supported (i.e., the values that are allowed in the SECURITY PROTOCOL SPECIFIC field) for the

Working Draft SCSI Primary Commands - 4 (SPC-4) 727

T10/BSR INCITS 513 Revision 37 17 May 2014

SECURITY PROTOCOL OUT command (see 6.41).

Table 563 — Supported CbCS SECURITY PROTOCOL OUT Pages CbCS page format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PAGE CODE (0001h)
1 (LSB)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Supported CbCS SECURITY PROTOCOL OUT page list
4 (MSB) SUPPORTED CBCS SECURITY PROTOCOL OUT PAGE
5 [first] (LSB)
•
••

n-1 (MSB) SUPPORTED CBCS SECURITY PROTOCOL OUT PAGE

n [last] (LSB)

The PAGE CODE field shall be set as shown in table 563 to indicate that the Supported CbCS SECURITY
PROTOCOL OUT Pages CbCS page is being returned.

The PAGE LENGTH field indicates the number of bytes that follow in the Supported CbCS SECURITY
PROTOCOL OUT Pages CbCS page.

Each SUPPORTED CBCS SECURITY PROTOCOL OUT PAGE field indicates the page code (see table 570 in 7.7.4.4)
of one CbCS page that is supported by the SECURITY PROTOCOL OUT command if the SECURITY PROTOCOL
field (see 6.41) is set to 07h (i.e., CbCS). The values in the SUPPORTED CBCS SECURITY PROTOCOL IN PAGE
fields shall be returned in ascending order.

7.7.4.3.3 Unchangeable CbCS Parameters CbCS page

The Unchangeable CbCS Parameters CbCS page (see table 564) indicates the supported CbCS features and
algorithms.

Table 564 — Unchangeable CbCS Parameters CbCS page format (part 1 of 2)

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PAGE CODE (0002h)
1 (LSB)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4 KEYS SUPPORT MIN CBCS METHOD SUP Reserved
5 Reserved
6 (MSB) SUPPORTED INTEGRITY CHECK VALUE ALGORITHM
7 LIST LENGTH (c-7) (LSB)

728 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table 564 — Unchangeable CbCS Parameters CbCS page format (part 2 of 2)

Bit
7 6 5 4 3 2 1 0
Byte
Supported integrity check value algorithms list
8 (MSB)
SUPPORTED INTEGRITY CHECK VALUE ALGORITHM
•• •
[first]
11 (LSB)
•
••

c-3 (MSB)
SUPPORTED INTEGRITY CHECK VALUE ALGORITHM
•• •
[last]
c (LSB)
c+1
Reserved
c+2
c+3 (MSB)
SUPPORTED D-H ALGORITHM LIST LENGTH (d-c-4)
c+4 (LSB)
Supported Diffie-Hellman (D-H) algorithms list
c+5 (MSB)
•• • SUPPORTED D-H ALGORITHM [first]
c+8 (LSB)
••
•
d-3 (MSB)
•• • SUPPORTED D-H ALGORITHM [last]
d (LSB)
d+1 (MSB)
SUPPORTED CBCS METHODS LIST LENGTH (n-d-2)
d+2 (LSB)
Supported CbCS methods list
d+3 SUPPORTED CBCS METHOD [first]
••
•
n SUPPORTED CBCS METHOD [last]

The PAGE CODE field shall be set as shown in table 564 to indicate that the Unchangeable CbCS Parameters
CbCS page is being returned.

The PAGE LENGTH field indicates the number of bytes that follow in the Unchangeable CbCS Parameters
CbCS page.

Working Draft SCSI Primary Commands - 4 (SPC-4) 729

T10/BSR INCITS 513 Revision 37 17 May 2014

The KEYS SUPPORT field (see table 565) indicates the type of CbCS master keys and working keys supported.

Table 565 — KEYS SUPPORT field

Code Description
00b Reserved
01b The SCSI target device supports single CbCS master key and a set of CbCS working
keys (see 5.13.6.7.11) for the SCSI target device, but the logical units in the SCSI target
device do not support CbCS master keys or working keys.
10b The SCSI target device does not support CbCS master keys or working keys for the
SCSI target device, but each logical unit in the SCSI target device supports a single
CbCS master key and a set of CbCS working keys for that logical unit.
11b The SCSI target device supports single CbCS master key and a set of CbCS working
keys for the SCSI target device, and each logical unit in the SCSI target device supports
a single CbCS master key and a set of CbCS working keys for that logical unit. Keys
stored in the logical unit take precedence over keys stored in the SCSI target device
(see 5.13.6.7.6).

The MIN CBCS METHOD SUP field (see table 566) indicates how the assignment of the minimum allowable CbCS
method is supported.

Table 566 — MIN CBCS METHOD SUP field

Code Description
00b Reserved
01b A single minimum allowed CbCS method (see 5.13.6.7.8) is assigned to all logical units in the
SCSI target device, and the SECURITY PROTOCOL well known logical unit is implemented to
control its value.
10b Each logical unit in the SCSI target device is assigned its own minimum allowed CbCS method.
11b Reserved

The SUPPORTED INTEGRITY CHECK VALUE ALGORITHM LIST LENGTH field indicates the number of bytes that follow
in the supported integrity check value algorithms list.

Each SUPPORTED INTEGRITY CHECK VALUE ALGORITHM field indicates one supported algorithm for computing
CbCS integrity check values. The values in the SUPPORTED INTEGRITY CHECK VALUE ALGORITHM fields are
selected from the codes that table 105 (see 5.13.8) lists as integrity checking (i.e., AUTH) algorithms, except
for AUTH_COMBINED.

The SUPPORTED D-H ALGORITHM LIST LENGTH field indicates the number of bytes that follow in the supported
Diffie-Hellman (D-H) algorithms list.

Each SUPPORTED D-H ALGORITHM field indicates one supported algorithm for constructing CbCS shared keys.
The values in the SUPPORTED D-H ALGORITHM fields are selected from the codes that table 105 (see 5.13.8)
lists as Diffie-Hellman algorithms with finite field D-H computations.

The SUPPORTED CBCS METHODS LIST LENGTH field indicates the number of bytes that follow in the supported
CbCS methods list.

730 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Each SUPPORTED CBCS METHODS field indicates one supported CbCS method (see 6.26.2.3). The values in the
SUPPORTED CBCS METHODS fields are selected from the codes listed in table 267 (see 6.26.2.3).

7.7.4.3.4 Security Token CbCS page

The Security Token CbCS page (see table 567) indicates the value of the security token (see 5.13.6.7.10) for
the I_T nexus on which the SECURITY PROTOCOL IN command was received.

Table 567 — Security Token CbCS page format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PAGE CODE (003Fh)
1 (LSB)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4 (MSB)
•• • SECURITY TOKEN
n (LSB)

The PAGE CODE field shall be set as shown in table 567 to indicate that the Security Token CbCS page is being
returned.

The PAGE LENGTH field indicates the number of bytes that follow in the Security Token CbCS page.

The SECURITY TOKEN field shall contain the security token (see 5.13.6.7.10) for the I_T nexus on which the
command was received.

7.7.4.3.5 Current CbCS Parameters CbCS page

The Current CbCS Parameters CbCS page (see table 568) indicates the current values for the CbCS
parameters (see 5.13.6.7.15) used by the SCSI target device or logical unit as follows:

a) if the logical unit to which the SECURITY PROTOCOL IN command is addressed is the SECURITY
PROTOCOL well known logical unit (see 8.5), then the contents of the Current CbCS Parameters
CbCS page apply to the SCSI target device; or

Working Draft SCSI Primary Commands - 4 (SPC-4) 731

T10/BSR INCITS 513 Revision 37 17 May 2014

b) if the logical unit to which the SECURITY PROTOCOL IN command is addressed is not the
SECURITY PROTOCOL well known logical unit, then the contents of the Current CbCS Parameters
CbCS page apply to the addressed logical unit.

Table 568 — Current CbCS Parameters CbCS page format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PAGE CODE (0040h)
1 (LSB)
2 (MSB)
PAGE LENGTH (009Ah)
3 (LSB)
4
5 Reserved
6
7 MINIMUM ALLOWED CBCS METHOD

8 (MSB)
•• • POLICY ACCESS TAG
11 (LSB)
12
•• • Reserved
15
16 (MSB)
•• • MASTER KEY IDENTIFIER
23 (LSB)
24 (MSB)
•• • WORKING KEY 0 IDENTIFIER
31 (LSB)
32 (MSB)
•• • WORKING KEY 1 IDENTIFIER
39 (LSB)
••
•
144 (MSB)
•• • WORKING KEY 15 IDENTIFIER
151 (LSB)
152 (MSB)
•• • CLOCK
157 (LSB)

The PAGE CODE field shall be set as shown in table 568 to indicate that the Current CbCS Parameters CbCS
page is being returned.

The PAGE LENGTH field indicates the number of bytes that follow in the Current CbCS Parameters CbCS page.

732 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The contents of the MINIMUM ALLOWED CBCS METHOD field depend on the logical unit that returned the Current
CbCS Parameters CbCS page as follows:

a) if the logical unit is not the SECURITY PROTOCOL well known logical unit, then the MINIMUM
ALLOWED CBCS METHOD field indicates the smallest value allowed in the CBCS METHOD field (see
6.26.2.3) of a capability descriptor processed by the enforcement manager (see 5.13.6.7.7) as
described in 5.13.6.7.13.2 (i.e., the value of the minimum CbCS method CbCS parameter for the
logical unit (see 5.13.6.7.15); or
b) if the SECURITY PROTOCOL well known logical unit is returning the Current CbCS Parameters
CbCS page, then the MINIMUM ALLOWED CBCS METHOD field indicates the value that shall be copied to
the minimum CbCS method CbCS parameter of any dynamically created logical units (i.e., the initial
minimum CbCS method CbCS parameter summarized in 5.13.6.7.15).

The value in the MINIMUM ALLOWED CBCS METHOD field is selected from those listed in table 267 (see 6.26.2.3).

The contents of the POLICY ACCESS TAG field depend on the logical unit that returned the Current CbCS
Parameters CbCS page as follows:

a) if the logical unit is not the SECURITY PROTOCOL well known logical unit, then the POLICY ACCESS
TAG field indicates the value required in the POLICY ACCESS TAG field (see 6.26.2.3) of a capability
descriptor processed by the enforcement manager (see 5.13.6.7.7) as described in 5.13.6.7.13.2 (i.e.,
the value of the policy access tag CbCS parameter for the logical unit (see 5.13.6.7.15)); or
b) if the SECURITY PROTOCOL well known logical unit is returning the Current CbCS Parameters
CbCS page, then the POLICY ACCESS TAG field indicates the value that shall be copied to the policy
access tag CbCS parameter of any dynamically created logical units (i.e., the initial policy access tag
CbCS parameter summarized in 5.13.6.7.15).

The MASTER KEY IDENTIFIER field specifies the current CbCS shared key identifier (see 5.13.6.7.11.2) for the
master key (see 5.13.6.7.11).

The WORKING KEY 0 IDENTIFIER field, the WORKING KEY 1 IDENTIFIER field, the WORKING KEY 2 IDENTIFIER field,
through the WORKING KEY 15 IDENTIFIER field contain the current CbCS shared key identifier (see 5.13.6.7.11.2)
for the working keys (see 5.13.6.7.11).

The CLOCK field shall be set to the current value of the device clock using the device clock value format
defined in 5.2.

Working Draft SCSI Primary Commands - 4 (SPC-4) 733

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.4.3.6 Set Master Key – Seed Exchange CbCS page

The Set Master Key – Seed Exchange CbCS page (see table 569) in a SECURITY PROTOCOL IN command
continues a CbCS master key update CCS (see 5.13.6.7.11.4) that was initiated by processing of a Set
Master Key – Seed Exchange CbCS page in a SECURITY PROTOCOL OUT command (see 7.7.4.5.5), and
completes a Diffie-Hellman key exchange protocol as part of that CCS.

The Diffie-Hellman (D-H) algorithm being used in the CbCS master key update CCS is determined by the
contents of the D-H ALGORITHM field in the Set Master Key – Seed Exchange CbCS page in the SECURITY
PROTOCOL OUT command (see 7.7.4.5.5) that initiated the CCS. This Diffie-Hellman algorithm specifies the
DH_generator value and DH_prime value to be used in the computation of the D-H DATA field as described in
this subclause.

Table 569 — Set Master Key – Seed Exchange CbCS page format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PAGE CODE (D010h)
1 (LSB)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4 (MSB)
•• • D-H DATA
n (LSB)

The PAGE CODE field shall be set as shown in table 569 to indicate that the Set Master Key – Seed Exchange
CbCS page is being returned.

The PAGE LENGTH field indicates the number of bytes that follow in the Set Master Key – Seed Exchange
CbCS page.

The contents of the D-H DATA field are computed as follows:

1) a random number, y, is generated having a value between 0 and DH_prime minus one as defined in
RFC 4086; and
2) the D-H DATA field is set to DH_generatory modulo DH_prime, where the DH_generator and DH_prime
values are identified by the value in the D-H ALGORITHM field.

As part of the successful completion of processing for the SECURITY PROTOCOL IN command transfer of
the Set Master Key – Seed Exchange CbCS page the device server and application client store as part of the
state maintained for CbCS master key update CCS (see 5.13.6.7.11.4):

a) the authentication key component of the next master key; and

b) the generation key component of the next master key.

734 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The new master key is computed as follows:

1) an initial_seed value that is the value DH_generatorxy modulo DH_prime is computed as follows:
A) the device server computes (DH_generatorx modulo DH_prime)y, where DH_generatorx is the
contents of the D-H DATA field in the SECURITY PROTOCOL OUT command and y is the random
number generated by the device server; and
B) the application client computes (DH_generatory modulo DH_prime)x, where DH_generatory is the
contents of the D-H DATA field in the SECURITY PROTOCOL IN command and x is the random
number generated by the application client (see 7.7.4.5.5);
2) the generation key component of the new master key is computed using the integrity check value
algorithm specified by the integrity check value algorithm field in the capability (see 6.26.2.3) in the
CbCS extension descriptor (see 5.13.6.7.16) associated with the SECURITY PROTOCOL IN
command that transferred the Set Master Key – Seed Exchange CbCS page. The following inputs are
used with the specified integrity check value algorithm:
A) the concatenation of the initial_seed value computed in step 1) and all of the bytes in the Device
Identification VPD page (see 7.8.6) for the logical unit that is processing the CbCS master key
update CCS (see 5.13.6.7.11.4) as the string for which the integrity check value is to be
computed; and
B) the generation key component of the current master key (see 5.13.6.7.11) for the logical unit that
is processing the CbCS master key update CCS as the cryptographic key;
3) a modified_seed value is computed as follows:
A) if the least significant bit of the initial_seed value is zero, then the modified_seed value is equal to
the initial_seed value with the least significant bit set to one; and
B) if the least significant bit of the initial_seed value is one, then the modified_seed value is equal to
the initial_seed value with the least significant bit set to zero;
and
4) the authentication key component of the new master key is computed using the integrity check value
algorithm specified by the integrity check value algorithm field in the capability (see 6.26.2.3) in the
CbCS extension descriptor (see 5.13.6.7.16) associated with the SECURITY PROTOCOL IN
command that transferred the Set Master Key – Seed Exchange CbCS page. The following inputs are
used with the specified integrity check value algorithm:
A) the concatenation of the modified_seed value computed in step 3) and all of the bytes in the
Device Identification VPD page for the logical unit that is processing the CbCS master key update
CCS as the string for which the integrity check value is to be computed; and
B) the generation key component of the current master key for the logical unit that is processing the
CbCS master key update CCS as the cryptographic key.

Working Draft SCSI Primary Commands - 4 (SPC-4) 735

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.4.4 CbCS SECURITY PROTOCOL OUT CDB description

The CbCS SECURITY PROTOCOL OUT CDB has the format defined in 6.41 with the additional requirements
described in this subclause.

If the SECURITY PROTOCOL field is set to CbCS (i.e., 07h) in a SECURITY PROTOCOL OUT command, the
SECURITY PROTOCOL SPECIFIC field (see table 570) specifies the CbCS page to being sent in the parameter list
(see 7.7.4.5). If the CBCS bit is set to one in the Extended INQUIRY Data VPD page (see 7.8.7), the CbCS
SECURITY PROTOCOL OUT command support requirements are shown in table 570.

Table 570 — SECURITY PROTOCOL SPECIFIC field for the CbCS SECURITY PROTOCOL OUT command

Code a CbCS page sent Support Reference

0000h to 0040h Reserved
0041h Set Policy Access Tag Optional 7.7.4.5.1
0042h Set Minimum CbCS Method Optional 7.7.4.5.2
0043h to CFFFh Reserved
D000h Invalidate Key See b 7.7.4.5.3
D001h Set Key See b 7.7.4.5.4
D003h to D00Fh Reserved
D010h Set Master Key – Seed Exchange See b 7.7.4.5.5
b
D011h Set Master Key – Change Master Key See 7.7.4.5.6
D012h to FFFFh Reserved
a If the SECURITY PROTOCOL SPECIFIC field is set to a value that is less than D000h, then
the working key specified by the KEY VERSION field in the CbCS capability descriptor
(see 6.26.2.3) shall be used to compute the capability key (see 5.13.6.7.12). If the
SECURITY PROTOCOL SPECIFIC field is set to a value that is greater than or equal to
D000h, then the authentication key component of the master key (see 5.13.6.7.11)
shall be used to compute the capability key.
b
Mandatory if the CAPKEY CbCS method (see 5.13.6.7.8.3) is supported.

If a CbCS SECURITY PROTOCOL OUT command is received with the INC_512 bit set to one, the device
server shall terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

736 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.7.4.5 CbCS SECURITY PROTOCOL OUT parameter list

7.7.4.5.1 Set Policy Access Tag CbCS page

The Set Policy Access Tag CbCS page (see table 571) specifies a new policy access tag CbCS parameter
value or a new initial policy access tag CbCS parameter value.

Table 571 — Set Policy Access Tag CbCS page format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PAGE CODE (0041h)
1 (LSB)
2 (MSB)
PAGE LENGTH (0004h)
3 (LSB)
4 (MSB)
•• • POLICY ACCESS TAG
7 (LSB)

The PAGE CODE field set as shown in table 571 specifies that the Set Policy Access Tag CbCS page is being
sent.

The PAGE LENGTH field specifies the number of bytes that follow and is set as shown in table 571 for the Set
Policy Access Tag CbCS page. If the PAGE LENGTH field is not set as shown in table 571 or to a larger value,
the device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

The CbCS parameter (see 5.13.6.7.15) that is set to the contents of the POLICY ACCESS TAG field depends on
the logical unit that is processing the Set Policy Access Tag CbCS page as follows:

a) if the logical unit is not the SECURITY PROTOCOL well known logical unit, then the contents of the
POLICY ACCESS TAG field shall be placed in the policy access tag CbCS parameter for the logical unit;
or
b) if the SECURITY PROTOCOL well known logical unit is processing the Set Policy Access Tag CbCS
page, then the contents of the POLICY ACCESS TAG field shall be placed in the initial policy access tag
CbCS parameter.

Working Draft SCSI Primary Commands - 4 (SPC-4) 737

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.4.5.2 Set Minimum CbCS Method CbCS page

The Set Minimum CbCS Method CbCS page (see table 572) specifies a new minimum CbCS method CbCS
parameter value or a new initial minimum CbCS method CbCS parameter value.

Table 572 — Set Minimum CbCS Method CbCS page format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PAGE CODE (0042h)
1 (LSB)
2 (MSB)
PAGE LENGTH (0002h)
3 (LSB)
4 Reserved
5 MINIMUM ALLOWED CBCS METHOD

The PAGE CODE field set as shown in table 572 specifies that the Set Minimum CbCS Method CbCS page is
being sent.

The PAGE LENGTH field specifies the number of bytes that follow and is set as shown in table 572 for the Set
Minimum CbCS Method CbCS page. If the PAGE LENGTH field is not set as shown in table 572 or to a larger
value, the device server shall terminate the command with CHECK CONDITION status, with the sense key
set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

The CbCS parameter or CbCS parameters (see 5.13.6.7.15) that are set to the contents of the MINIMUM
ALLOWED CBCS METHOD field depends on the logical unit that is processing the Set Minimum CbCS Method
CbCS page and the contents of the MIN CBCS METHOD SUP field in the Unchangeable CbCS Parameters CbCS
page (see 7.7.4.3.3) as shown in table 573.

Table 573 — Minimum CbCS Method CbCS Parameter set

CbCS Parameter set based on the logical unit that processes the Set Minimum CbCS
Method CbCS page
MIN CBCS
METHOD Not the SECURITY PROTOCOL SECURITY PROTOCOL
SUP field well known logical unit well known logical unit
00b Reserved
01b The device server terminates the command All minimum CbCS method CbCS parame-
with CHECK CONDITION status with the ters for all logical units in the SCSI target
sense key set to ILLEGAL REQUEST, and device, and the initial minimum CbCS
the additional sense code set to INVALID method, if any
FIELD IN PARAMETER LIST
10b The minimum CbCS method CbCS parame- The initial minimum CbCS method CbCS
ter for the logical unit that processes the Set parameter
Minimum CbCS Method CbCS page
11b Reserved

If the MINIMUM ALLOWED CBCS METHOD field specifies a value that does not appear in the supported CbCS
methods list in the Unchangeable CbCS Parameters CbCS page (see 7.7.4.3.3), then the device server shall

738 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and
the additional sense code set to INVALID FIELD IN PARAMETER LIST.

7.7.4.5.3 Invalidate Key CbCS page

The Invalidate Key CbCS page (see table 574) causes a working key (see 5.13.6.7.11) to be invalidated. After
the successful processing of an Invalidate Key CbCS page, the working key with the specified key version
shall not be valid for the purposes of enforcement manager (see 5.13.6.7.7) CbCS extension descriptor
validation (see 5.13.6.7.13.2).

Table 574 — Invalidate Key CbCS page format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PAGE CODE (D000h)
1 (LSB)
2 (MSB)
PAGE LENGTH (0004h)
3 (LSB)
4
5 Reserved
6
7 Reserved KEY VERSION

The PAGE CODE field set as shown in table 574 specifies that the Invalidate Key CbCS page is being sent.

The PAGE LENGTH field specifies the number of bytes that follow and is set as shown in table 574 for the
Invalidate Key CbCS page. If the PAGE LENGTH field is is not set as shown in table 574 or to a larger value, the
device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

The KEY VERSION field specifies which working key (e.g., a KEY VERSION field set to four specifies that the
working key whose Current CbCS Parameters CbCS page (see 7.7.4.3.5) key identifier is returned in the
WORKING KEY 4 IDENTIFIER field) is to be invalidated as follows:

a) if the Invalidate Key CbCS page is processed by a logical unit that is not the SECURITY PROTOCOL
well known logical unit, then the specified working key for that logical unit shall be invalidated; or
b) if the Invalidate Key CbCS page is processed by the SECURITY PROTOCOL well known logical unit,
then the specified target-wide working key (see 5.13.6.7.11) shall be invalidated.

The CbCS shared key identifier (see 5.13.6.7.11.2) for the invalidated working key shall be set to
FFFF FFFF FFFF FFFEh.

It shall not be an error to invalidate a working key that is already invalid.

Working Draft SCSI Primary Commands - 4 (SPC-4) 739

T10/BSR INCITS 513 Revision 37 17 May 2014

7.7.4.5.4 Set Key CbCS page

The Set Key CbCS page (see table 575) causes a working key (see 5.13.6.7.11) to be set to a new value.
After the successful processing of a Set Key CbCS page, the working key with the specified key version shall
be valid for the purposes of enforcement manager (see 5.13.6.7.7) CbCS extension descriptor validation (see
5.13.6.7.13.2).

Table 575 — Set Key CbCS page format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PAGE CODE (D001h)
1 (LSB)
2 (MSB)
PAGE LENGTH (0020h)
3 (LSB)
4
5 Reserved
6
7 Reserved KEY VERSION

8 (MSB)
•• • KEY IDENTIFIER
15 (LSB)
16 (MSB)
•• • SEED
35 (LSB)

The PAGE CODE field set as shown in table 575 specifies that the Set Key CbCS page is being sent.

The PAGE LENGTH field specifies the number of bytes that follow and is set as shown in table 575 for the Set
Key CbCS page. If the PAGE LENGTH field is is not set as shown in table 575 or to a larger value, the device
server shall terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

The KEY VERSION field specifies which working key (e.g., a KEY VERSION field set to six specifies that the
working key whose Current CbCS Parameters CbCS page (see 7.7.4.3.5) key identifier is returned in the
WORKING KEY 6 IDENTIFIER field) is to be set as follows:

a) if the Set Key CbCS page is processed by a logical unit that is not the SECURITY PROTOCOL well
known logical unit, then the specified working key for that logical unit shall be set; or
b) if the Set Key CbCS page is processed by the SECURITY PROTOCOL well known logical unit, then
the specified target-wide working key (see 5.13.6.7.11) shall be set.

The KEY IDENTIFIER field specifies the value to which the CbCS shared key identifier (see 5.13.6.7.11.2) shall
be set for the working key affected by the Set Key CbCS page. If the KEY IDENTIFIER field is set to a value that
table 89 (see 5.13.6.7.11.2) describes as reserved in the CbCS pages that change CbCS shared key values,
then the device server shall terminate the command with CHECK CONDITION status, with the sense key set
to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

The SEED field specifies a random number that is an input to the computation of the new working key value.

740 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The value to which the specified working key is set shall be computed using the integrity check value
algorithm specified by the INTEGRITY CHECK VALUE ALGORITHM field in the capability (see 6.26.2.3) in the CbCS
extension descriptor (see 5.13.6.7.16) associated with the SECURITY PROTOCOL OUT command that sent
the Set Key CbCS page. The following inputs shall be used with the specified integrity check value algorithm:

a) the contents of the SEED field in the Set Key CbCS page as the string for which the integrity check
value is to be computed; and
b) the generation key component of the master key (see 5.13.6.7.11) for the logical unit that is
processing the Set Key CbCS page as the cryptographic key.

7.7.4.5.5 Set Master Key – Seed Exchange CbCS page

The Set Master Key – Seed Exchange CbCS page (see table 576) in a SECURITY PROTOCOL OUT
command initiates a CbCS master key update CCS (see 5.13.6.7.11.4) and begins a Diffie-Hellman key
exchange protocol as part of that CCS.

Table 576 — Set Master Key – Seed Exchange CbCS page format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PAGE CODE (D010h)
1 (LSB)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4 (MSB)
•• • D-H ALGORITHM
7 (LSB)
8 (MSB)
•• • D-H DATA LENGTH (n-11)
11 (LSB)
12 (MSB)
•• • D-H DATA
n (LSB)

The PAGE CODE field set as shown in table 576 specifies that the Set Master Key – Seed Exchange CbCS
page is being sent.

The PAGE LENGTH field specifies the number of bytes that follow in the Set Master Key – Seed Exchange
CbCS page. If the PAGE LENGTH field is set to a value that is smaller than ten, then the device server shall
terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and
the additional sense code set to INVALID FIELD IN PARAMETER LIST.

The D- H ALGORITHM field specifies the Diffie-Hellman (D-H) algorithm to be used in the seed exchange
protocol. The value in the D-H ALGORITHM field is selected from the codes that table 105 (see 5.13.8) lists as
Diffie-Hellman algorithms with finite field D-H computations. The Diffie-Hellman algorithm selected specifies
the DH_generator value and DH_prime value to be used in the computation of the D-H DATA field as described
in this subclause.

If the value in the D-H ALGORITHM field does not appear in the Supported Diffie-Hellman algorithms list in the
Unchangeable CbCS Parameters CbCS page (see 7.7.4.3.3), then the device server shall terminate the

Working Draft SCSI Primary Commands - 4 (SPC-4) 741

T10/BSR INCITS 513 Revision 37 17 May 2014

command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID FIELD IN PARAMETER LIST.

The D-H DATA LENGTH field specifies the number of bytes that follow in D-H DATA field. If the D-H DATA LENGTH
field is set to a value that is inconsistent with the Diffie-Hellman algorithm specified by the D-H ALGORITHM field,
then the device server shall terminate the command with CHECK CONDITION status, with the sense key set
to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

The contents of the D-H DATA field are computed as follows:

1) a random number, x, is generated having a value between 0 and DH_prime minus one observing the
requirements in RFC 4086; and
2) the D-H DATA field is set to DH_generatorx modulo DH_prime, where the DH_generator and DH_prime
values are identified by the value in the D-H ALGORITHM field.

7.7.4.5.6 Set Master Key – Change Master Key CbCS page

The Set Master Key – Change Master Key CbCS page (see table 577) concludes a CbCS master key update
CCS (see 5.13.6.7.11.4) and changes the master key components to the values computed as part of
processing completion (see 7.7.4.3.6) for the SECURITY PROTOCOL IN command that transferred the Set
Master Key – Seed Exchange CbCS page.

Table 577 — Set Master Key – Change Master Key CbCS page format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
PAGE CODE (D011h)
1 (LSB)
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4
•• • Reserved
7
8 (MSB)
•• • KEY IDENTIFIER
15 (LSB)
16 (MSB)
•• • APPLICATION CLIENT D-H DATA LENGTH (k-19)
19 (LSB)
20 (MSB)
•• • APPLICATION CLIENT D-H DATA
k (LSB)
k+1 (MSB)
•• • DEVICE SERVER D-H DATA LENGTH (n-(k-4))
k+4 (LSB)
k+5 (MSB)
•• • DEVICE SERVER D-H DATA
n (LSB)

742 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The PAGE CODE field set as shown in table 577 specifies that the Set Master Key – Change Master Key CbCS
page is being sent.

The PAGE LENGTH field specifies the number of bytes that follow in the Set Master Key – Change Master Key
CbCS page. If the PAGE LENGTH field is set to a value that is smaller than 24, then the device server shall
terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and
the additional sense code set to INVALID FIELD IN PARAMETER LIST.

The KEY IDENTIFIER field specifies the value to which the master key CbCS shared key identifier (see
5.13.6.7.11.2) shall be set. If the KEY IDENTIFIER field is set to a value that table 89 (see 5.13.6.7.11.2)
describes as reserved in the CbCS pages that change CbCS shared key values, then the device server shall
terminate the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST,
and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

The APPLICATION CLIENT D-H DATA LENGTH field specifies the number of bytes that follow in the APPLICATION
CLIENT D-H DATA field. If the contents of the APPLICATION CLIENT D-H DATA LENGTH field do not match the number
of Diffie-Hellman (D-H) data bytes that the device server received in the SECURITY PROTOCOL OUT
command that sent the Set Master Key – Seed Exchange CbCS page (see 7.7.4.5.5) and initiated the current
CbCS master key update CCS (see 5.13.6.7.11.4), then the master key shall not be modified and the
command shall be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

The APPLICATION CLIENT D-H DATA field contains Diffie-Hellman data field that was sent in the Set Master Key –
Seed Exchange CbCS page that initiated the current CbCS master key update CCS. If the contents of the
APPLICATION CLIENT D-H DATA field do not match Diffie-Hellman data that the device server received in the
SECURITY PROTOCOL OUT command that sent the Set Master Key – Seed Exchange CbCS page that
initiated the current CbCS master key update CCS (see 5.13.6.7.11.4), then the master key shall not be
modified and the command shall be terminated with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

The DEVICE SERVER D-H DATA LENGTH field specifies the number of bytes that follow in the DEVICE SERVER D-H
DATA field. If the contents of the DEVICE SERVER D - H DATA LENGTH field do not match the number of
Diffie-Hellman data bytes that the device server returned in the SECURITY PROTOCOL IN command that
returned the Set Master Key – Seed Exchange CbCS page (see 7.7.4.3.6) in the current CbCS master key
update CCS, then the master key shall not be modified and the command shall be terminated with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
INVALID FIELD IN PARAMETER LIST.

The DEVICE SERVER D-H DATA field contains Diffie-Hellman data field that was returned in the Set Master Key –
Seed Exchange CbCS page that the device server returned in response to a SECURITY PROTOCOL IN
command as part of the current CbCS master key update CCS. If the contents of the DEVICE SERVER D-H DATA
field do not match Diffie-Hellman data that the device server returned in the SECURITY PROTOCOL IN
command that send the Set Master Key – Seed Exchange CbCS page, then the master key shall not be
modified and the command shall be terminated with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

Working Draft SCSI Primary Commands - 4 (SPC-4) 743

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8 Vital product data parameters

7.8.1 Vital product data parameters overview and page codes

This subclause describes the vital product data (VPD) page structure and the VPD pages (see table 578) that
are applicable to all SCSI devices. These VPD pages are returned by an INQUIRY command with the EVPD bit
set to one (see 6.6) and contain product information about a logical unit and SCSI target device.

Table 578 — Vital product data page codes

VPD Page Name Page code Reference Support

ASCII Information 01h to 7Fh 7.8.3 Optional
ATA Information 89h SAT-3 See SAT-3
CFA Profile Information 8Ch 7.8.4 Optional
Device Constituents 8Bh 7.8.5 Optional
Device Identification 83h 7.8.6 Mandatory
Extended INQUIRY Data 86h 7.8.7 Optional
Management Network Addresses 85h 7.8.8 Optional
Mode Page Policy 87h 7.8.9 Optional
Power Condition 8Ah 7.8.10 Optional
Power Consumption 8Dh 7.8.11 Optional
Protocol Specific Logical Unit Information 90h 7.8.12 Protocol specific a
Protocol Specific Port Information 91h 7.8.13 Protocol specific a
SCSI Ports 88h 7.8.14 Optional
Software Interface Identification 84h 7.8.15 Optional
Supported VPD Pages 00h 7.8.16 Mandatory
Third-party Copy 8Fh 7.8.17 Optional
Unit Serial Number 80h 7.8.18 Optional
Restricted (see applicable command standard) B0h to BFh
b
Obsolete
Vendor specific c
Reserved All other codes
A numeric ordered listing of VPD page codes is provided in F.7.
a
See applicable SCSI transport protocol standard for support requirements.
b The following page codes are obsolete: 81h and 82h.
c The following page codes are vendor specific: C0h to FFh.

This standard does not define the location or method of storing the vital product data. The return of the vital
product data may require completion of initialization operations within the device, that may result in delays
before the vital product data is available to the application client. Time-critical requirements are an
implementation consideration and are not defined in this standard.

744 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.8.2 VPD page format for all device types

This subclause describes the VPD page structure that is applicable to all SCSI devices. VPD pages specific to
each device type are described in the command standard that applies to that device type.

An INQUIRY command with the EVPD bit set to one (see 6.6) specifies that the device server return a VPD
page using the format defined in table 579.

Table 579 — VPD page format

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4
•• • VPD parameters
n

The PERIPHERAL QUALIFIER field and the PERIPHERAL DEVICE TYPE field are the same as defined for standard
INQUIRY data (see 6.6.2).

The PAGE CODE field (see 7.8.1) identifies the VPD page and contains the same value as in the PAGE CODE
field in the INQUIRY CDB (see 6.6).

The PAGE LENGTH field indicates the length in bytes of the VPD parameters that follow this field. The contents
of the PAGE LENGTH field are not altered based on the allocation length (see 4.2.5.6).

The VPD parameters are defined for each VPD page code. If the PERIPHERAL QUALIFIER field is not set to 000b,
the contents of the PAGE LENGTH field and the VPD parameters are outside the scope of this standard.

Working Draft SCSI Primary Commands - 4 (SPC-4) 745

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.3 ASCII Information VPD page

The ASCII Information VPD page (see table 580) contains information for the field replaceable unit code
returned in the sense data (see 4.5).

Table 580 — ASCII Information VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (01h to 7Fh)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4 ASCII LENGTH (m-4)
5 (MSB)
•• • ASCII INFORMATION
m (LSB)
m+1
•• • Vendor specific information
n

The PERIPHERAL QUALIFIER field, PERIPHERAL DEVICE TYPE field, PAGE CODE field, and PAGE LENGTH field are
defined in 7.8.2.

The value in the PAGE CODE field is associated with the FIELD REPLACEABLE UNIT CODE field returned in the
sense data.

NOTE 56 - The FIELD REPLACEABLE UNIT CODE field in the sense data provides for 255 possible codes, while
the PAGE CODE field provides for only 127 possible codes. For that reason it is not possible to return ASCII
Information VPD pages for the upper code values.

The ASCII LENGTH field indicates the length in bytes of the ASCII INFORMATION field. A value of zero in this field
indicates that no ASCII information is available for the indicated page code. The contents of the ASCII LENGTH
field are not altered based on the allocation length (see 4.2.5.6).

The ASCII INFORMATION field contains ASCII information concerning the field replaceable unit identified by the
page code. The data in this field shall be formatted in one or more character string lines. Each line shall
contain only ASCII printable characters (i.e., code values 20h through 7Eh) and shall be terminated with a
NULL (00h) character.

The contents of the vendor specific information are not defined in this standard.

746 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.8.4 CFA Profile Information VPD page

The CFA Profile Information VPD page (see table 581) provides information on the CFA profiles, if any, that
are supported by the device server.

Table 581 — CFA Profile Information VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (8Ch)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
CFA profile descriptor list
4
•• • CFA profile descriptor (see table 582) [first]
7
••
•
n-3
•• • CFA profile descriptor (see table 582) [last]
n

The PERIPHERAL QUALIFIER field, PERIPHERAL DEVICE TYPE field, and PAGE LENGTH field are defined in 7.8.2.

The PAGE CODE field is defined in 7.8.2 and shall be set as shown in table 581 for the CFA Profile Information
VPD page.

Each CFA profile descriptor (see table 582) contains identifying information for one CFA profile supported by
the device server described in the standard INQUIRY data (see 6.6.2).

Table 582 — CFA profile descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 CFA PROFILE SUPPORTED

1 Reserved
2 (MSB)
SEQUENTIAL WRITE DATA SIZE
3 (LSB)

The CFA PROFILE SUPPORTED field indicates a CFA profile number (see VPG1) that the device server supports.

The SEQUENTIAL WRITE DATA SIZE field indicates the preferred number of logical blocks in a stream field write
operation (see VPG1) for the CFA profile indicated by the CFA PROFILE SUPPORTED field. If the SEQUENTIAL
WRITE DATA SIZE field is set to zero, then no preferred number of logical blocks is indicated for stream field
write operations by this CFA profile descriptor.

Working Draft SCSI Primary Commands - 4 (SPC-4) 747

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.5 Device Constituents VPD page

The Device Constituents VPD page (see table 583) provides identifying information for the constituents (e.g.,
logical units in other SCSI devices, microcode, storage medium, or vendor specific information technology
components) of the logical unit described in the standard INQUIRY data (see 6.6.2).

Table 583 — Device Constituents VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (8Bh)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Constituent descriptor list
4
•• • Constituent descriptor (see table 584) [first]

••
•

•• • Constituent descriptor (see table 584) [last]

n

The PERIPHERAL QUALIFIER field, PERIPHERAL DEVICE TYPE field, and PAGE LENGTH field are defined in 7.8.2.

The PAGE CODE field is defined in 7.8.2 and shall be set as shown in table 583 for the Device Constituents VPD
page.

748 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Each constituent descriptor (see table 584) contains identifying information for one constituent of the logical
unit described in the standard INQUIRY data (see 6.6.2).

Table 584 — Constituent descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
CONSTITUENT TYPE
1 (LSB)
2 CONSTITUENT DEVICE TYPE

3 Reserved
4 (MSB)
•• • T10 VENDOR IDENTIFICATION
11 (LSB)
12 (MSB)
•• • PRODUCT IDENTIFICATION
27 (LSB)
28 (MSB)
•• • PRODUCT REVISION LEVEL
31 (LSB)
32
Reserved
33
34 (MSB)
CONSTITUENT DESCRIPTOR LENGTH (n-35)
35 (LSB)
Constituent specific descriptor list
36
•• • Constituent specific descriptor [first]

•
••

•• • Constituent specific descriptor [last]

n

The CONSTITUENT TYPE field (see table 585) indicates the constituent descriptor type.

Table 585 — CONSTITUENT TYPE field

Code Description
0000h Reserved
0001h Virtual tape library
0002h Virtual tape drive
0003h Direct access block device
0004h to FFFFh Reserved

Working Draft SCSI Primary Commands - 4 (SPC-4) 749

T10/BSR INCITS 513 Revision 37 17 May 2014

The CONSTITUENT DEVICE TYPE field (see table 586) indicates the constituent descriptor type.

Table 586 — CONSTITUENT DEVICE TYPE field

Code Description Reference

00h to 1Fh One of the values defined for the PERIPHERAL DEVICE TYPE field 6.6.2
in the standard INQUIRY data
20h to FEh Reserved
FFh Unknown

The T10 VENDOR IDENTIFICATION field, PRODUCT IDENTIFICATION field, and the PRODUCT REVISION LEVEL field are
identifying information for one constituent of the logical unit described in the standard INQUIRY data, and are
as defined in 6.6.2.

The CONSTITUENT DESCRIPTOR LENGTH field indicates the length of the constituent specific descriptor list.

Each constituent specific descriptor (see table 587) contains information that is specific to the constituent.

Table 587 — Constituent specific descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 CONSTITUENT SPECIFIC TYPE

1 Reserved
2 (MSB)
ADDITIONAL LENGTH (n-3)
3 (LSB)
4
•• • Constituent specific data
n

The CONSTITUENT SPECIFIC TYPE field (see table 588) indicates the type of constituent specific data in this
descriptor.

Table 588 — CONSTITUENT SPECIFIC TYPE field

Code Description
01h VPD page
FFh Vendor specific
all others Reserved

The ADDITIONAL LENGTH field indicates the number of bytes that follow in this descriptor.

The contents of the constituent specific data depend on the value in the CONSTITUENT SPECIFIC TYPE field.

If the CONSTITUENT SPECIFIC TYPE field is set to 01h, then:

a) the constituent specific data contains a VPD page (see 7.8.1); and
b) the device server shall not set the PAGE CODE field in that VPD page to 8Bh (i.e., the VPD page in the
constituent specific data shall not be a Device Constituents VPD page).

750 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If SCSI port specific information or protocol specific information is reported in the Device Constituents VPD
page, then that information shall be associated with the device constituent, not the addressed logical unit.

7.8.6 Device Identification VPD page

7.8.6.1 Device Identification VPD page overview

The Device Identification VPD page (see table 589) provides the means to retrieve designation descriptors
applying to the logical unit. Logical units may have more than one designation descriptor (e.g., if several types
or associations of designator are supported). Designators consist of one or more of the following:

a) logical unit names;

b) SCSI target port identifiers;
c) SCSI target port names;
d) SCSI device names;
e) relative target port identifiers;
f) primary target port group number; or
g) logical unit group number.

Designation descriptors shall be assigned to the peripheral device (e.g., a disk drive) and not to the currently
mounted media, in the case of removable media devices. Application clients should use the designation
descriptors during system configuration activities to determine whether alternate paths exist for the same
peripheral device.

Table 589 — Device Identification VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (83h)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Designation descriptor list
4
•• • Designation descriptor [first]

••
•

•• • Designation descriptor [last]

n

The PERIPHERAL QUALIFIER field, PERIPHERAL DEVICE TYPE field, and PAGE LENGTH field are defined in 7.8.2.

The PAGE CODE field is defined in 7.8.2 and shall be set as shown in table 589 for the Device Identification
VPD page.

Working Draft SCSI Primary Commands - 4 (SPC-4) 751

T10/BSR INCITS 513 Revision 37 17 May 2014

Each designation descriptor (see table 590) contains information identifying the logical unit, SCSI target
device containing the logical unit, or access path (i.e., target port) used by the command and returned
parameter data. The Device Identification VPD page shall contain the designation descriptors enumerated in
7.8.6.2.

Table 590 — Designation descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 PROTOCOL IDENTIFIER CODE SET

1 PIV Reserved ASSOCIATION DESIGNATOR TYPE

2 Reserved
3 DESIGNATOR LENGTH (n-3)
4
•• • DESIGNATOR
n

The PROTOCOL IDENTIFIER field may indicate the SCSI transport protocol to which the designation descriptor
applies. If the ASSOCIATION field is set to a value other than 01b (i.e., target port) or 10b (i.e., SCSI target
device) or the PIV bit is set to zero, then the PROTOCOL IDENTIFIER field contents are reserved. If the
ASSOCIATION field is set to a value of 01b or 10b and the PIV bit is set to one, then the PROTOCOL IDENTIFIER
field shall contain one of the values shown in table 479 (see 7.6.1) to indicate the SCSI transport protocol to
which the designation descriptor applies.

The CODE SET field contains a code set enumeration (see 4.3.3) that indicates the format of the DESIGNATOR
field.

A protocol identifier valid (PIV) bit set to zero indicates the PROTOCOL IDENTIFIER field contents are reserved. If
the ASSOCIATION field is set to a value of 01b or 10b, then a PIV bit set to one indicates the PROTOCOL
IDENTIFIER field contains a valid protocol identifier selected from the values shown in table 479 (see 7.6.1). If
the ASSOCIATION field is set to a value other than 01b or 10b, then the PIV bit contents are reserved.

The ASSOCIATION field indicates the entity with which the DESIGNATOR field is associated, as described in table
591. If a logical unit returns a designation descriptor with the ASSOCIATION field set to 00b or 10b, the logical
unit shall return the same descriptor when it is accessed through any other I_T nexus.

Table 591 — ASSOCIATION field

Code Description
00b The DESIGNATOR field is associated with the addressed logical unit.
01b The DESIGNATOR field is associated with the target port that received the command.
10b The DESIGNATOR field is associated with the SCSI target device that contains the
addressed logical unit.
11b Reserved

752 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The DESIGNATOR TYPE field (see table 592) indicates the format and assignment authority for the designator.

Table 592 — DESIGNATOR TYPE field

Code Description Reference

0h Vendor specific 7.8.6.3
1h T10 vendor ID based 7.8.6.4
2h EUI-64 based 7.8.6.5
3h NAA 7.8.6.6
4h Relative target port identifier 7.8.6.7
5h Target port group 7.8.6.8
6h Logical unit group 7.8.6.9
7h MD5 logical unit identifier 7.8.6.10
8h SCSI name string 7.8.6.11
9h Protocol specific port identifier 7.8.6.12
Ah to Fh Reserved

The DESIGNATOR LENGTH field indicates the length in bytes of the DESIGNATOR field. The contents of the
DESIGNATOR LENGTH field are not altered based on the allocation length (see 4.2.5.6).

The DESIGNATOR field contains the designator as described by the ASSOCIATION field, DESIGNATOR TYPE field,
CODE SET field, and DESIGNATOR LENGTH field.

7.8.6.2 Device designation descriptor requirements

7.8.6.2.1 Designation descriptors for logical units other than well known logical units

For each logical unit that is not a well known logical unit, the Device Identification VPD page shall include at
least one designation descriptor in which a logical unit name (see SAM-5) is indicated. The designation
descriptor shall have the ASSOCIATION field set to 00b (i.e., logical unit) and the DESIGNATOR TYPE field set to:

a) 1h (i.e., T10 vendor ID based);

b) 2h (i.e., EUI-64-based);
c) 3h (i.e., NAA); or
d) 8h (i.e., SCSI name string).

At least one designation descriptor should have the DESIGNATOR TYPE field set to:

a) 2h (i.e., EUI-64-based);
b) 3h (i.e., NAA); or
c) 8h (i.e., SCSI name string).

In the case of virtual logical units (e.g., volume sets as defined by SCC-2), designation descriptors should
contain a DESIGNATOR TYPE field set to:

a) 2h (i.e., EUI-64-based);
b) 3h (i.e., NAA); or
c) 8h (i.e., SCSI name string).

Working Draft SCSI Primary Commands - 4 (SPC-4) 753

T10/BSR INCITS 513 Revision 37 17 May 2014

In the case of virtual logical units that have an EUI-64 based designation descriptor (see 7.8.6.5) the
DESIGNATOR LENGTH field should be set to:

a) 0Ch (i.e., EUI-64-based 12-byte); or

b) 10h (i.e., EUI-64-based 16-byte).

In the case of virtual logical units that have an NAA designation descriptor (see 7.8.6.6) the NAA field should
be set to 6h (i.e., IEEE Registered Extended).

The Device Identification VPD page shall contain the same set of designation descriptors with the
ASSOCIATION field set to 00b (i.e., logical unit) regardless of the I_T nexus being used to retrieve the
designation descriptors.

For logical units that are not well known logical units, the requirements for SCSI target device designation
descriptors are defined in 7.8.6.2.4 and the requirements for SCSI target port designation descriptors are
defined in 7.8.6.2.3.

7.8.6.2.2 Designation descriptors for well known logical units

Well known logical units shall not return any designation descriptors with the ASSOCIATION field set to 00b (i.e.,
logical unit).

The Device Identification VPD page shall contain the same set of designation descriptors with the
ASSOCIATION field set to 10b (i.e., SCSI target device) regardless of the I_T nexus being used to retrieve the
designation descriptors.

7.8.6.2.3 Designation descriptors for SCSI target ports

7.8.6.2.3.1 Relative target port identifiers

For the target port through which the Device Identification VPD page is accessed, the Device Identification
VPD page should include one designation descriptor with the ASSOCIATION field set to 01b (i.e., target port)
and the DESIGNATOR TYPE field set to 4h (i.e., relative target port identifier) identifying the target port being
used to retrieve the designation descriptors.

7.8.6.2.3.2 Target port names or identifiers

For the SCSI target port through which the Device Identification VPD page is accessed, the Device
Identification VPD page should include one designation descriptor in which the target port name or identifier
(see SAM-5) is indicated. The designation descriptor, if any, shall have the ASSOCIATION field set to 01b (i.e.,
target port) and the DESIGNATOR TYPE field set to:

a) 2h (i.e., EUI-64-based);
b) 3h (i.e., NAA); or
c) 8h (i.e., SCSI name string).

If the SCSI transport protocol standard for the target port defines target port names, the designation
descriptor, if any, shall contain the target port name. If the SCSI transport protocol for the target port does not
define target port names, the designation descriptor, if any, shall contain the target port identifier.

7.8.6.2.4 Designation descriptors for SCSI target devices

If the SCSI target device contains a well known logical unit, the Device Identification VPD page shall have one
or more designation descriptors for the SCSI target device. If the SCSI target device does not contain a well

754 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

known logical unit, the Device Identification VPD page should have one or more designation descriptors for
the SCSI target device.

Each SCSI target device designation descriptor, if any, shall have the ASSOCIATION field set to 10b (i.e., SCSI
target device) and the DESIGNATOR TYPE field set to:

a) 2h (i.e., EUI-64-based);
b) 3h (i.e., NAA); or
c) 8h (i.e., SCSI name string).

The Device Identification VPD page shall contain designation descriptors, if any, for all the SCSI device
names for all the SCSI transport protocols supported by the SCSI target device.

7.8.6.3 Vendor specific designator format

If the designator type is 0h (i.e., vendor specific), no assignment authority was used and there is no guarantee
that the designator is globally unique (i.e., the identifier is vendor specific). Table 593 defines the DESIGNATOR
field format.

Table 593 — Vendor specific DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • VENDOR SPECIFIC IDENTIFIER
n

7.8.6.4 T10 vendor ID based designator format

If the designator type is 1h (i.e., T10 vendor ID based), the DESIGNATOR field has the format shown in table
594.

Table 594 — T10 vendor ID based DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • T10 VENDOR IDENTIFICATION
7 (LSB)
8
•• • VENDOR SPECIFIC IDENTIFIER
n

The T10 VENDOR IDENTIFICATION field contains eight bytes of left-aligned ASCII data (see 4.3.1) identifying the
manufacturer of the product. The data shall be left aligned within this field.The T10 vendor identification shall
be one assigned by INCITS. A list of assigned T10 vendor identifications is in Annex G and on the T10 web
site (http://www.T10.org).

NOTE 57 - The T10 web site (http://www.t10.org) provides a convenient means to request an identification
code.

Working Draft SCSI Primary Commands - 4 (SPC-4) 755

T10/BSR INCITS 513 Revision 37 17 May 2014

The organization associated with the T10 vendor identification is responsible for ensuring that the VENDOR
SPECIFIC DESIGNATOR field is unique in a way that makes the entire DESIGNATOR field unique. A recommended
method of constructing a unique DESIGNATOR field is to concatenate the PRODUCT IDENTIFICATION field from the
standard INQUIRY data (see 6.6.2) and the PRODUCT SERIAL NUMBER field from the Unit Serial Number VPD
page (see 7.8.18).

7.8.6.5 EUI-64 based designator format

7.8.6.5.1 EUI-64 based designator format overview

If the designator type is 2h (i.e., EUI-64 based identifier), the DESIGNATOR LENGTH field (see table 595)
indicates the format of the designation descriptor.

Table 595 — EUI-64 based designator lengths

Designator Length Description Reference

08h EUI-64 identifier 7.8.6.5.2
0Ch EUI-64 based 12-byte identifier 7.8.6.5.3
10h EUI-64 based 16-byte identifier 7.8.6.5.4
All other values Reserved

7.8.6.5.2 EUI-64 designator format

If the designator type is 2h (i.e., EUI-64 based identifier) and the DESIGNATOR LENGTH field is set to 08h, the
DESIGNATOR field has the format shown in table 596. The CODE SET field shall be set to 1h (i.e., binary).

Table 596 — EUI-64 DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
1 IEEE COMPANY_ID

2 (LSB)
3 (MSB)
•• • VENDOR SPECIFIC EXTENSION IDENTIFIER
7 (LSB)

The IEEE COMPANY_ID field contains a 24-bit canonical form OUI assigned by the IEEE.

The VENDOR SPECIFIC EXTENSION IDENTIFIER field contains a 40-bit numeric value that is assigned by the
organization associated with the IEEE company_id as required by the IEEE definition of EUI-64 in a way that
makes the entire DESIGNATOR field (see table 596) unique.

756 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.8.6.5.3 EUI-64 based 12-byte designator format

If the designator type is 2h (i.e., EUI-64 based identifier) and the DESIGNATOR LENGTH field is set to 0Ch, the
DESIGNATOR field has the format shown in table 597. The CODE SET field shall be set to 1h (i.e., binary).

Table 597 — EUI-64 based 12-byte DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
1 IEEE COMPANY_ID

2 (LSB)
3 (MSB)
•• • VENDOR SPECIFIC EXTENSION IDENTIFIER
7 (LSB)
8 (MSB)
•• • DIRECTORY ID
11 (LSB)

The IEEE COMPANY_ID field and VENDOR SPECIFIC EXTENSION IDENTIFIER field are defined in 7.8.6.5.2.

The DIRECTORY ID field contains a directory identifier, as specified by ISO/IEC 13213:1994.

NOTE 58 - The EUI-64 based 12-byte format is used to return IEEE 1394 target port identifiers (see SBP-3).

7.8.6.5.4 EUI-64 based 16-byte designator format

If the designator type is 2h (i.e., EUI-64 based identifier) and the DESIGNATOR LENGTH field is set to 10h, the
DESIGNATOR field has the format shown in table 598. The CODE SET field shall be set to 1h (i.e., binary).

Table 598 — EUI-64 based 16-byte DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • IDENTIFIER EXTENSION
7 (LSB)
8 (MSB)
•• • IEEE COMPANY_ID
10 (LSB)
11 (MSB)
•• • VENDOR SPECIFIC EXTENSION IDENTIFIER
15 (LSB)

The IDENTIFIER EXTENSION field contains a 64-bit numeric value.

The IEEE COMPANY_ID field and VENDOR SPECIFIC EXTENSION IDENTIFIER field are defined in 7.8.6.5.2.

NOTE 59 - The EUI-64 based 16-byte format is used to return SCSI over RDMA target port identifiers (see SRP).

Working Draft SCSI Primary Commands - 4 (SPC-4) 757

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.6.6 NAA designator format

7.8.6.6.1 NAA identifier basic format

If the designator type is 3h (i.e., NAA identifier), the DESIGNATOR field has the format shown in table 599. This
format is compatible with the Name_Identifier format defined in FC-FS-3.

Table 599 — NAA DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0 NAA

1
•• • NAA specific data
n

The Network Address Authority (NAA) field (see table 600) defines the format of the NAA specific data in the
designator.

Table 600 — Network Address Authority (NAA) field

Code Description Reference

2h IEEE Extended 7.8.6.6.2
3h Locally Assigned 7.8.6.6.3
5h IEEE Registered 7.8.6.6.4
6h IEEE Registered Extended 7.8.6.6.5
All others Reserved

7.8.6.6.2 NAA IEEE Extended designator format

If NAA is 2h (i.e., IEEE Extended), the eight-byte fixed length DESIGNATOR field shall have the format shown in
table 601. The CODE SET field shall be set to 1h (i.e., binary) and the DESIGNATOR LENGTH field shall be set to
08h.

Table 601 — NAA IEEE Extended DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0 NAA (2h) (MSB)
1 VENDOR SPECIFIC IDENTIFIER A (LSB)
2 (MSB)
3 IEEE COMPANY_ID

4 (LSB)
5 (MSB)
6 VENDOR SPECIFIC IDENTIFIER B

7 (LSB)

The IEEE COMPANY_ID field contains a 24-bit canonical form OUI assigned by the IEEE.

758 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The VENDOR SPECIFIC IDENTIFIER A field contains a 12-bit numeric value that is assigned by the organization
associated with the IEEE company_id in a way that combines with the VENDOR SPECIFIC IDENTIFIER B field to
make the entire DESIGNATOR field (see table 601) unique.

The VENDOR SPECIFIC IDENTIFIER B field contains a 24-bit numeric value that is assigned by the organization
associated with the IEEE company_id in a way that combines with the VENDOR SPECIFIC IDENTIFIER A field to
make the entire DESIGNATOR field (see table 601) unique.

NOTE 60 - The EUI-64 format includes a 40-bit vendor specific identifier. The IEEE Extended format includes
36 bits of vendor specific identifier in two fields.

7.8.6.6.3 NAA Locally Assigned designator format

If NAA is 3h (i.e., Locally Assigned), the eight-byte fixed length DESIGNATOR field shall have the format shown
in table 602. The CODE SET field shall be set to 1h (i.e., binary) and the DESIGNATOR LENGTH field shall be set to
08h.

Table 602 — NAA Locally Assigned DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0 NAA (3h)
1
•• • LOCALLY ADMINISTERED VALUE
7

The LOCALLY ADMINISTERED VALUE field contains a 60-bit value that is assigned by an administrator to be
unique within the set of SCSI domains that are accessible by a common instance of an administrative tool or
tools.

7.8.6.6.4 NAA IEEE Registered designator format

If NAA is 5h (i.e., IEEE Registered), the eight-byte fixed length DESIGNATOR field shall have the format shown
in table 603. The CODE SET field shall be set to 1h (i.e., binary) and the DESIGNATOR LENGTH field shall be set to
08h.

Table 603 — NAA IEEE Registered DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0 NAA (5h) (MSB)
1
IEEE COMPANY_ID
2
3 (LSB) (MSB)
4
•• • VENDOR SPECIFIC IDENTIFIER
7 (LSB)

The IEEE COMPANY_ID field contains a 24-bit canonical form OUI assigned by the IEEE.

Working Draft SCSI Primary Commands - 4 (SPC-4) 759

T10/BSR INCITS 513 Revision 37 17 May 2014

The VENDOR SPECIFIC IDENTIFIER field contains a 36-bit numeric value that is assigned by the organization
associated with the IEEE company_id in a way that makes the entire DESIGNATOR field (see table 603) unique.

NOTE 61 - The EUI-64 identifier includes a 40-bit vendor specific identifier. The IEEE Registered format
includes a 36-bit vendor specific identifier.

7.8.6.6.5 NAA IEEE Registered Extended designator format

If NAA is 6h (i.e., IEEE Registered Extended), the 16-byte fixed length DESIGNATOR field shall have the format
shown in table 604. The CODE SET field shall be set to 1h (i.e., binary) and the DESIGNATOR LENGTH field shall
be set to 10h.

Table 604 — NAA IEEE Registered Extended DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0 NAA (6h) (MSB)
1
IEEE COMPANY_ID
2
3 (LSB) (MSB)
4
•• • VENDOR SPECIFIC IDENTIFIER
7 (LSB)
8 (MSB)
•• • VENDOR SPECIFIC IDENTIFIER EXTENSION
15 (LSB)

The IEEE COMPANY_ID field contains a 24-bit canonical form OUI assigned by the IEEE.

The VENDOR SPECIFIC IDENTIFIER field contains a 36-bit numeric value that is assigned by the organization
associated with the IEEE company_id in a way that combines with the VENDOR SPECIFIC IDENTIFIER EXTENSION
field to make the entire DESIGNATOR field (see table 604) unique.

NOTE 62 - The EUI-64 format includes a 40-bit vendor specific identifier. The IEEE Registered Extended
format includes a 36-bit vendor specific identifier.

The VENDOR SPECIFIC IDENTIFIER EXTENSION field contains a 64-bit numeric value that is assigned by the
organization associated with the IEEE company_id in a way that combines with the VENDOR SPECIFIC
IDENTIFIER field to make the entire DESIGNATOR field (see table 604) unique.

760 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.8.6.7 Relative target port designator format

If the designator type is 4h (i.e., relative target port identifier) and the ASSOCIATION field is set to 01b (i.e.,
target port), then the DESIGNATOR field shall have the format shown in table 605. The CODE SET field shall be
set to 1h (i.e., binary) and the DESIGNATOR LENGTH field shall be set to 04h. If the ASSOCIATION field does not
contain 01b, use of this designator type is reserved.

Table 605 — Relative target port DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0
Reserved
1
2 (MSB)
RELATIVE TARGET PORT IDENTIFIER
3 (LSB)

The RELATIVE TARGET PORT IDENTIFIER field (see 4.3.4) contains the relative port identifier of the target port on
which the INQUIRY command was received.

7.8.6.8 Target port group designator format

If the designator type is 5h (i.e., target port group) and the ASSOCIATION value is 01b (i.e., target port), the
four-byte fixed length DESIGNATOR field shall have the format shown in table 606. The CODE SET field shall be
set to 1h (i.e., binary) and the DESIGNATOR LENGTH field shall be set to 04h. If the ASSOCIATION field does not
contain 01b, use of this designator type is reserved.

Table 606 — Target port group DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0
Reserved
1
2 (MSB)
TARGET PORT GROUP
3 (LSB)

The TARGET PORT GROUP field indicates the primary target port group to which the target port is a member (see
5.15).

7.8.6.9 Logical unit group designator format

A logical unit group is a group of logical units that share the same primary target port group (see 5.15)
definitions. The primary target port groups maintain the same primary target port group asymmetric access

Working Draft SCSI Primary Commands - 4 (SPC-4) 761

T10/BSR INCITS 513 Revision 37 17 May 2014

states for all logical units in the same logical unit group. A logical unit shall be in no more than one logical unit
group.

If the designator type is 6h (i.e., logical unit group) and the ASSOCIATION value is 00b (i.e., logical unit), the
four-byte fixed length DESIGNATOR field shall have the format shown in table 607. The CODE SET field shall be
set to 1h (i.e., binary) and the DESIGNATOR LENGTH field shall be set to 04h. If the ASSOCIATION field does not
contain 00b, use of this designator type is reserved.

Table 607 — Logical unit group DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0
Reserved
1
2 (MSB)
LOGICAL UNIT GROUP
3 (LSB)

The LOGICAL UNIT GROUP field indicates the logical unit group to which the logical unit is a member.

7.8.6.10 MD5 logical unit designator format

If the designator type is 7h (i.e., MD5 logical unit identifier) and the ASSOCIATION value is 00b (i.e., logical unit),
the DESIGNATOR field has the format shown in table 608. The CODE SET field shall be set to 1h (i.e., binary). The
MD5 logical unit designator shall not be used if a logical unit provides unique identification using designator
types 2h (i.e., EUI-64 based identifier), 3h (i.e., NAA identifier), or 8h (i.e., SCSI name string). A bridge device
may return a MD5 logical unit designator type for that logical unit that does not support the Device
Identification VPD page (see 7.8.6).

If the ASSOCIATION field does not contain 00b, use of this designator type is reserved.

Table 608 — MD5 logical unit DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • MD5 LOGICAL UNIT IDENTIFIER
15 (LSB)

The MD5 LOGICAL UNIT IDENTIFIER field contains the message digest of the supplied message input. The
message digest shall be generated using the MD5 message-digest algorithm as defined in RFC 1321 (see
2.5) with the following information as message input:

1) the contents of the T10 VENDOR IDENTIFICATION field in the standard INQUIRY data (see 6.6.2);
2) the contents of the PRODUCT IDENTIFICATION field in the standard INQUIRY data;
3) the contents of the PRODUCT SERIAL NUMBER field in the Unit Serial Number VPD page (see 7.8.18);
4) the contents of a vendor specific DESIGNATOR field (designator type 0h) from the Device Identification
VPD page; and
5) the contents of a T10 vendor ID based DESIGNATOR field (designator type 1h) from the Device
Identification VPD page.

762 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If a field or page is not available, the message input for that field or page shall be 8 bytes of ASCII space
characters (i.e., 20h).

The uniqueness of the MD5 logical unit identifier is dependent upon the relative degree of randomness (i.e.,
the entropy) of the message input. If two or more logical units have the same MD5 logical unit identifier, the
application client should determine in a vendor specific manner whether the logical units are the same entities.

EXAMPLE – In this practical MD5 example, the data available for input to the MD5 algorithm is shown in table 609.

Table 609 — MD5 logical unit identifier example available data

MD5 message input Available Contents

T10 VENDOR IDENTIFICATION field Yes ‘T10’
PRODUCT IDENTIFICATION field Yes ‘MD5 Logical Unit’
PRODUCT SERIAL NUMBER field Yes ‘01234567’
vendor specific DESIGNATOR field No
T10 vendor ID based DESIGNATOR field No

In this example, the concatenation of the fields in table 609 to form input to the MD5 algorithm is shown in table 610.

Table 610 — Example MD5 input for computation of a logical unit identifier

Bytes Hexadecimal values ASCII values

00 to 15 54 31 30 20 20 20 20 20 4D 44 35 20 4C 6F 67 69 T10 MD5 Logi
16 to 31 63 61 6C 20 55 6E 69 74 30 31 32 33 34 35 36 37 cal Unit01234567
32 to 47 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20

Based on the example inputs shown in table 609 and the concatenation of the inputs shown in table 610, the MD5 base 16
algorithm described in RFC 1321 produces the value 8FAC A22A 0AC0 3839 255 25F2 0EFE 2E7Eh.

7.8.6.11 SCSI name string designator format

If the designator type is 8h (i.e., SCSI name string), the DESIGNATOR field has the format shown in table 611.
The CODE SET field shall be set to 3h (i.e., UTF-8).

Table 611 — SCSI name string DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • SCSI NAME STRING
n

The null-terminated, null-padded (see 4.3.2) SCSI NAME STRING field contains a UTF-8 format string. The
number of bytes in the SCSI NAME STRING field (i.e., the value in the DESIGNATOR LENGTH field) shall be:

a) less than 256; and

b) a multiple of four.

Working Draft SCSI Primary Commands - 4 (SPC-4) 763

T10/BSR INCITS 513 Revision 37 17 May 2014

The SCSI NAME STRING field starts with either:

a) the four UTF-8 characters 'eui.' concatenated with 16, 24, or 32 hexadecimal digits (i.e., the UTF-8
characters 0 through 9 and A through F) for an EUI-64 based identifier (see 7.8.6.5). The first
hexadecimal digit shall be the most significant four bits of the first byte (i.e., most significant byte) of
the EUI-64 based identifier;
b) the four UTF-8 characters 'naa.' concatenated with 16 or 32 hexadecimal digits for an NAA identifier
(see 7.8.6.6). The first hexadecimal digit shall be the most significant four bits of the first byte (i.e.,
most significant byte) of the NAA identifier; or
c) the four UTF-8 characters 'iqn.' concatenated with an iSCSI Name for an iSCSI-name based identifier
(see iSCSI).

If the ASSOCIATION field is set to 00b (i.e., logical unit) and the SCSI NAME STRING field starts with the four UTF-8
characters 'iqn.', then the SCSI NAME STRING field ends with the five UTF-8 characters ',L,0x' concatenated with
16 hexadecimal digits for the logical unit name extension. The logical unit name extension is a UTF-8 string
containing no more than 16 hexadecimal digits. The logical unit name extension is assigned by the SCSI
target device vendor and shall be assigned so the logical unit name is world wide unique.

If the ASSOCIATION field is set to 01b (i.e., target port), the SCSI NAME STRING field ends with the five UTF-8
characters ',t,0x' concatenated with two or more hexadecimal digits as defined in the applicable SCSI
transport protocol standard.

If the ASSOCIATION field is set to 10b (i.e., SCSI target device), the SCSI NAME STRING field has no additional
characters.

7.8.6.12 Protocol specific port identifier designator format

7.8.6.12.1 Protocol specific port identifier designator format overview

If the designator type is 9h (i.e., protocol specific port identifier), then:

a) the ASSOCIATION field shall be set to 01b (i.e., target port);

b) the PIV bit shall set to one; and
c) the contents of the PROTOCOL IDENTIFIER field (see table 612) indicate the format of the DESIGNATOR
field.

Table 612 — Protocol specific port designator formats

PROTOCOL
IDENTIFIER
field Description Reference
9h USB target port identifier 7.8.6.12.2
Ah PCI Express routing ID 7.8.6.12.3
all others Reserved

764 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.8.6.12.2 USB target port identifier designator format

If the DESIGNATOR TYPE field is set to 9h (i.e., protocol specific port identifier) and the PROTOCOL IDENTIFIER field
is set to 9h (i.e., USB Attached SCSI), then:

a) the DESCRIPTOR LENGTH field shall be set to four; and

b) the DESIGNATOR field has the format is shown in table 613.

Table 613 — USB target port identifier DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0 Reserved DEVICE ADDRESS

1 Reserved
2 INTERFACE NUMBER

3 Reserved

The DEVICE ADDRESS field contains a USB device address (see USB-3).

The INTERFACE NUMBER field contains a USB interface number within a USB configuration (see USB-3).

7.8.6.12.3 PCI Express routing ID designator format

If the DESIGNATOR TYPE field is set to 9h (i.e., protocol specific port identifier) and the PROTOCOL IDENTIFIER field
is set to Ah (i.e., SCSI over PCI Express architecture), then:

a) the DESCRIPTOR LENGTH field shall be set to eight; and

b) the DESIGNATOR field has the format shown in table 614.

Table 614 — PCI Express routing ID DESIGNATOR field format

Bit
7 6 5 4 3 2 1 0
Byte
0
ROUTING ID
1
2
•• • Reserved
7

The ROUTING ID field contains a PCI Express routing ID (see SOP).

Working Draft SCSI Primary Commands - 4 (SPC-4) 765

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.7 Extended INQUIRY Data VPD page

The Extended INQUIRY Data VPD page (see table 615) provides the application client with a means to obtain
information about the logical unit.

Table 615 — Extended INQUIRY Data VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (86h)

2 (MSB)
PAGE LENGTH (003Ch)
3 (LSB)
4 ACTIVATE MICROCODE SPT GRD_CHK APP_CHK REF_CHK

5 Reserved UASK_SUP GROUP_SUP PRIOR_SUP HEADSUP ORDSUP SIMPSUP

6 Reserved WU_SUP CRD_SUP NV_SUP V_SUP

7 Reserved P_I_I_SUP Reserved LUICLR

8 Reserved R_SUP Reserved CBCS

9 Reserved MULTI I_T NEXUS MICROCODE DOWNLOAD

10 (MSB)
EXTENDED SELF-TEST COMPLETION MINUTES
11 (LSB)
12 POA_SUP HRA_SUP VSA_SUP Reserved
13 MAXIMUM SUPPORTED SENSE DATA LENGTH

14
•• • Reserved
63

The PERIPHERAL QUALIFIER field and PERIPHERAL DEVICE TYPE field are defined in 7.8.2.

The PAGE CODE field and PAGE LENGTH field are defined in 7.8.2, and shall be set to the value shown in table
615 for the Extended INQUIRY Data VPD page.

The ACTIVATE MICROCODE field (see table 616) indicates how a device server activates microcode and
establishes a unit attention condition during the processing of a WRITE BUFFER command (see 6.49) with

766 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

the download microcode mode set to 05h or 07h (see 5.4).

Table 616 — ACTIVATE MICROCODE field

Value Meaning
00b The actions of the device server server are not indicated.
01b The device server:
1) activates the microcode before completion of the final command in the WRITE BUFFER
sequence; and
2) establishes zero or more unit attention conditions as described in 5.4.2.
10b The device server:
1) activates the microcode after:
A) a vendor specific event;
B) a power on event; or
C) a hard reset event;
and
2) establishes a unit attention condition for the initiator port associated with every I_T nexus
with the additional sense code set to MICROCODE HAS BEEN CHANGED.
11b Reserved

The supported protection type (SPT) field indicates the type of protection the logical unit supports based on the
contents of the PERIPHERAL DEVICE TYPE field. If the PROTECT bit (see 6.6.2) is set to zero, the SPT field is
reserved.

If the PERIPHERAL DEVICE TYPE field is set to 00h (i.e., direct access block device) and the PROTECT bit is set to
one, then table 617 defines the contents of the SPT field.

Table 617 — SPT field for peripheral device type 00h

Protection type supported

Code Type 1 Type 2 Type 3

000b yes no no
001b yes yes no
010b no yes no
011b yes no yes
100b no no yes
101b no yes yes
110b Reserved
111b yes yes yes

Working Draft SCSI Primary Commands - 4 (SPC-4) 767

T10/BSR INCITS 513 Revision 37 17 May 2014

If the PERIPHERAL DEVICE TYPE field is set to 01h (i.e., sequential-access device) and the PROTECT bit is set to
one, then table 618 defines the contents of the SPT field.

Table 618 — SPT field for peripheral device type 01h

Code Protection type supported

001b Logical block protection
all others Reserved

If the PROTECT bit is set to one and the PERIPHERAL DEVICE TYPE field is set to a value other than 00h or 01h,
the SPT field is reserved.

A guard check (GRD_CHK) bit set to zero indicates that the device server does not check the LOGICAL BLOCK
GUARD field in the protection information (see SBC-3), if any. A GRD_CHK bit set to one indicates that the
device server checks the LOGICAL BLOCK GUARD field in the protection information, if any.

An application tag check (APP_CHK) bit set to zero indicates that the device server does not check the LOGICAL
BLOCK APPLICATION TAG field in the protection information (see SBC-3), if any. An APP_ CHK bit set to one
indicates that the device server checks the LOGICAL BLOCK APPLICATION TAG field in the protection information,
if any.

A reference tag check (REF_CHK) bit set to zero indicates that the device server does not check the LOGICAL
BLOCK REFERENCE TAG field in the protection information (see SBC-3), if any. A REF _ CHK bit set to one
indicates that the device server checks the LOGICAL BLOCK REFERENCE TAG field in the protection information, if
any.

A unit attention condition sense key specific data supported (UASK_SUP) bit set to one indicates that the device
server returns sense-key specific data for the UNIT ATTENTION sense key (see 4.5.2.4.6). A UASK_SUP bit
set to zero indicates that the device server does not return sense-key specific data for the UNIT ATTENTION
sense key.

A grouping function supported (GROUP_SUP) bit set to one indicates that the grouping function (see SBC-3) is
supported by the device server. A GROUP_ SUP bit set to zero indicates that the grouping function is not
supported.

A priority supported (PRIOR_SUP) bit set to one indicates that command priority (see SAM-5) is supported by
the logical unit. A PRIOR_SUP bit set to zero indicates that command priority is not supported.

A head of queue supported (HEADSUP) bit set to one indicates that the HEAD OF QUEUE task attribute (see
SAM-5) is supported by the logical unit. A HEADSUP bit set to zero indicates that the HEAD OF QUEUE task
attribute is not supported. If the HEADSUP bit is set to zero, application clients should not specify the HEAD OF
QUEUE task attribute as an Execute Command (see SAM-5) procedure call argument.

An ordered supported ( ORDSUP ) bit set to one indicates that the ORDERED task attribute (see SAM-5) is
supported by the logical unit. An ORDSUP bit set to zero indicates that the ORDERED task attribute is not
supported. If the ORDSUP bit is set to zero, application clients should not specify the ORDERED task attribute as
an Execute Command procedure call argument.

The simple supported (SIMPSUP) bit shall be set to one indicating that the SIMPLE task attribute (see SAM-5) is
supported by the logical unit.

SAM-5 defines how unsupported task attributes are processed.

768 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

A write uncorrectable supported (WU_SUP) bit set to zero indicates that the device server does not support
application clients setting the WR_UNCOR bit to one in the WRITE LONG command (see SBC-3). A WU_SUP bit
set to one indicates that the device server supports application clients setting the WR_UNCOR bit to one in the
WRITE LONG command.

A correction disable supported (CRD_SUP) bit set to zero indicates that the device server does not support
application clients setting the COR_DIS bit to one in the WRITE LONG command (see SBC-3). A CRD_SUP bit
set to one indicates that the device server supports application clients setting the COR_DIS bit to one in the
WRITE LONG command.

A non-volatile cache supported (NV_SUP) bit set to one indicates that the device server supports a non-volatile
cache and that the applicable command standard defines features using this cache (e.g., the FUA_NV bit in
SBC-2). An NV_SUP bit set to zero indicates that the device server may or may not support a non-volatile
cache.

A volatile cache supported (V_SUP) bit set to one indicates that the device server supports a volatile cache and
that the applicable command standard defines features using this cache (e.g., the FUA bit in SBC-3). An V_SUP
bit set to zero indicates that the device server may or may not support a volatile cache.

A protection information interval supported (P_I_I_SUP) bit set to one indicates that the logical unit supports
protection information intervals (see SBC-3). A P_I_I_SUP bit set to zero indicates that the logical unit does not
support protection information intervals.

A logical unit I_T nexus clear (LUICLR) bit set to one indicates the SCSI target device clears any unit attention
condition with an additional sense code of REPORTED LUNS DATA HAS CHANGED in each logical unit
accessible to an I_T nexus after reporting the unit attention condition for any logical unit over that I_T nexus
(see SAM-5). An LUICLR bit set to zero indicates the SCSI target device clears unit attention conditions as
defined in SPC-3. The LUICLR bit shall be set to one.

A referrals supported (R_SUP) bit set to zero indicates that the device server does not support referrals (see
SBC-3). An R_SUP bit set to one indicates that the device server supports referrals.

A capability-based command security ( CBCS ) bit set to one indicates that the logical unit supports the
capability-based command security technique (see 5.13.6.7). A CBCS bit set to zero indicates that the logical
unit does not support the capability-based command security technique.

The MULTI I_T NEXUS MICROCODE DOWNLOAD field (see table 60 in 5.4) indicates how the device server handles
concurrent attempts to download microcode using the WRITE BUFFER command (see 5.4) from multiple I_T
nexuses.

The EXTENDED SELF-TEST COMPLETION MINUTES field contains advisory data that is the time in minutes that the
device server requires to complete an extended self-test provided the device server is not interrupted by
subsequent commands and no errors occur during processing of the self-test. The application client should
expect the self-test completion time to exceed the value in this field if other commands are sent to the logical
unit while a self-test is in progress or if errors occur during the processing of the self-test. If a device server
supports SELF-TEST CODE field values other than 000b for the SEND DIAGNOSTIC command (see 6.42) and
the self-test completion time is greater than 18 hours, then the device server shall support the EXTENDED
SELF-TEST COMPLETION MINUTES field. A value of 0000h indicates that the EXTENDED SELF-TEST COMPLETION
MINUTES field is not supported. A value of FFFFh indicates that the extended self-test takes 65 535 minutes
(i.e., 45 days, 12 hours, and 15 minutes) or longer.

Working Draft SCSI Primary Commands - 4 (SPC-4) 769

T10/BSR INCITS 513 Revision 37 17 May 2014

A power on activation supported (POA_SUP) bit set to one indicates that the device server supports a WRITE
BUFFER command with the MODE field set to 0Dh (see 6.49.9) and the PO_ACT bit set to one. A POA_SUP bit
set to zero indicates that the device server does not support a WRITE BUFFER command with the MODE field
set to 0Dh and the PO_ACT bit set to one.

A hard reset activation supported (HRA_SUP) bit set to one indicates that the device server supports a WRITE
BUFFER command with the MODE field set to 0Dh (see 6.49.9) and the HR_ACT bit set to one. A HRA_SUP bit
set to zero indicates that the device server does not support a WRITE BUFFER command with the MODE field
set to 0Dh and the HR_ACT bit set to one.

A vendor specific activation supported (VSA_SUP) bit set to one indicates that the device server supports a
WRITE BUFFER command with the MODE field set to 0Dh (see 6.49.9) and the VSE_ACT bit set to one. A
VSA_SUP bit set to zero indicates that the device server does not support a WRITE BUFFER command with
the MODE field set to 0Dh and the VSE_ACT bit set to one.

The MAXIMUM SUPPORTED SENSE DATA LENGTH field indicates the maximum length in bytes of sense data (see
4.5) that the device server is capable of including in the same I_T_L_Q nexus transaction as the status. A
MAXIMUM SUPPORTED SENSE DATA LENGTH field set to zero indicates that the device server does not report a
maximum length. This value shall be less than or equal to 252.

7.8.8 Management Network Addresses VPD page

The Management Network Addresses VPD page (see table 619) provides a list of network addresses of
management services associated with a SCSI target device, target port, or logical unit.

Table 619 — Management Network Addresses VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (85h)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Network services descriptor list
4
•• • Network services descriptor [first]

••
•

•• • Network services descriptor [last]

n

The PERIPHERAL QUALIFIER field, PERIPHERAL DEVICE TYPE field, and PAGE LENGTH field are defined in 7.8.2.

The PAGE CODE field is defined in 7.8.2 and shall be set as shown in table 619 for the Management Network
Address VPD page.

770 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Each network service descriptor (see table 620) contains information about one management service.

Table 620 — Network service descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 Reserved ASSOCIATION SERVICE TYPE

1 Reserved
2 (MSB)
NETWORK ADDRESS LENGTH (n-3)
3 (LSB)
4
•• • NETWORK ADDRESS
n

The ASSOCIATION field (see table 591 in 7.8.6.1) indicates the entity (i.e., SCSI target device, target port, or
logical unit) with which the service is associated.

The SERVICE TYPE field (see table 621) allows differentiation of multiple services with the same protocol
running at different port numbers or paths.

NOTE 63 - A SCSI target device is allowed to provide separate HTTP services for configuration and
diagnostics. One of these services uses the standard HTTP port 80 and the other service uses a different port
(e.g., 8080).

Table 621 — SERVICE TYPE field

Code Description
00h Unspecified
01h Storage Configuration Service
02h Diagnostics
03h Status
04h Logging
05h Code Download
06h Copy Service
07h Administrative Configuration Service
08h to 1Fh Reserved

The NETWORK ADDRESS LENGTH field indicates the length in bytes of the NETWORK ADDRESS field. The network
address length shall be a multiple of four.

The null-terminated, null-padded NETWORK ADDRESS field contains the URL form of a URI as defined in RFC
3986.

Working Draft SCSI Primary Commands - 4 (SPC-4) 771

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.9 Mode Page Policy VPD page

The Mode Page Policy VPD page (see table 622) indicates which mode page policy (see 7.5.2) is in effect for
each mode page supported by the logical unit.

Table 622 — Mode Page Policy VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (87h)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Mode page policy descriptor list
4
•• • Mode page policy descriptor [first]
7
••
•
n-3
•• • Mode page policy descriptor [last]
n

The PERIPHERAL QUALIFIER field, PERIPHERAL DEVICE TYPE field, and PAGE LENGTH field are defined in 7.8.2.

The PAGE CODE field is defined in 7.8.2 and shall be set as shown in table 622 for the Mode Page Policy VPD
page.

Each mode page policy descriptor (see table 623) contains information describing the mode page policy for
one or more mode pages or subpages (see 7.5.7). The information in the mode page policy descriptors in this
VPD page shall describe the mode page policy for every mode page and subpage supported by the logical
unit.

Table 623 — Mode page policy descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 Reserved POLICY PAGE CODE

1 POLICY SUBPAGE CODE

2 MLUS Reserved MODE PAGE POLICY

3 Reserved

The POLICY PAGE CODE field and POLICY SUBPAGE CODE field indicate the mode page and subpage to which the
descriptor applies. The POLICY PAGE CODE field contains the value that is used in a MODE SENSE command
(see table 201 in 6.13.1) to retrieve the mode page being described.

772 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If the first mode page policy descriptor in the list contains a POLICY PAGE CODE field set to 3Fh and a POLICY
SUBPAGE CODE field set to FFh, then the descriptor applies to all mode pages and subpages not described by
other mode page policy descriptors. The POLICY PAGE CODE field shall be set to 3Fh and the POLICY SUBPAGE
CODE field shall be set to FFh only in the first mode page policy descriptor in the list.

If the POLICY PAGE CODE field is set to a value other than 3Fh and a POLICY SUBPAGE CODE field is set to a value
other than FFh, then the POLICY PAGE CODE field and the POLICY SUBPAGE CODE field indicate a single mode
page and subpage to which the descriptor applies.

If the POLICY PAGE CODE field is set to a value other than 3Fh, the POLICY SUBPAGE CODE field shall contain a
value other than FFh. If the POLICY SUBPAGE CODE field is set to a value other than FFh, then POLICY PAGE
CODE field shall contain a value other than 3Fh.

If the SCSI target device has more than one logical unit, a multiple logical units share (MLUS) bit set to one
indicates the mode page and subpage identified by the POLICY PAGE CODE field and POLICY SUBPAGE CODE field
is shared by more than one logical unit. A MLUS bit set to zero indicates the logical unit maintains its own copy
of the mode page and subpage identified by the POLICY PAGE CODE field and POLICY SUBPAGE CODE field.

The MLUS bit is set to one in the mode page policy descriptors or descriptor that indicates the mode page
policy for:

a) the Disconnect-Reconnect mode page (see 7.5.10); and

b) the Protocol Specific Port mode page (see 7.5.16).

The MODE PAGE POLICY field (see table 624) indicates the mode page policy for the mode page and subpage
identified by the POLICY PAGE CODE field and POLICY SUBPAGE CODE field. The mode page policies are
described in table 452 (see 7.5.2).

Table 624 — MODE PAGE POLICY field

Code Description
00b Shared
01b Per target port
10b Obsolete
11b Per I_T nexus

Working Draft SCSI Primary Commands - 4 (SPC-4) 773

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.10 Power Condition VPD page

The Power Condition VPD page (see table 625) indicates which power conditions (see 5.11) are supported by
the logical unit and provides information about how those power conditions operate.

Table 625 — Power Condition VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (8Ah)

2 (MSB)
PAGE LENGTH (000Eh)
3 (LSB)
4 Reserved STANDBY_Y STANDBY_Z

5 Reserved IDLE_C IDLE_B IDLE_A

6 (MSB)
STOPPED CONDITION RECOVERY TIME
7 (LSB)
8 (MSB)
STANDBY_Z CONDITION RECOVERY TIME
9 (LSB)
10 (MSB)
STANDBY_Y CONDITION RECOVERY TIME
11 (LSB)
12 (MSB)
IDLE_A CONDITION RECOVERY TIME
13 (LSB)
14 (MSB)
IDLE_B CONDITION RECOVERY TIME
15 (LSB)
16 (MSB)
IDLE_C CONDITION RECOVERY TIME
17 (LSB)

The PERIPHERAL QUALIFIER field and PERIPHERAL DEVICE TYPE field are defined in 7.8.2.

The PAGE CODE field and PAGE LENGTH field are defined in 7.8.2, and shall be set to the value shown in table
625 for the Power Condition VPD page.

If set to one, a power condition support bit (i.e., the STANDBY_Y bit, the STANDBY_Z bit, the IDLE_C bit, the
IDLE_B bit, and the IDLE_A bit) indicates that:

a) the associated power condition may be entered with the START STOP UNIT command (see SBC-3) if
that command is implemented; and
b) the associated power condition may be entered with a power condition timer if the associated timer is
supported and enabled (see 7.5.13).

A STANDBY_Y power conditions support bit set to one indicates that the logical unit supports the standby_y
power condition as described in 5.11. A STANDBY_Y bit set to zero indicates that the logical unit does not
support the standby_y power condition.

774 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

A STANDBY_Z power conditions support bit set to one indicates that the logical unit supports the standby_z
power condition as described in 5.11. A STANDBY_Z bit set to zero indicates that the logical unit does not
support the standby_z power condition.

A IDLE_C power conditions support bit set to one indicates that the logical unit supports the idle_c power
condition as described in 5.11. A IDLE_C bit set to zero indicates that the logical unit does not support the
idle_c power condition.

A IDLE_B power conditions support bit set to one indicates that the logical unit supports the idle_b power
condition as described in 5.11. A IDLE_B bit set to zero indicates that the logical unit does not support the
idle_b power condition.

A IDLE_A power conditions support bit set to one indicates that the logical unit supports the idle_a power
condition as described in 5.11. A IDLE_A bit set to zero indicates that the logical unit does not support the
idle_a power condition.

The STOPPED CONDITION RECOVERY TIME field indicates the time, in one millisecond increments, that the logical
unit takes to transition from the stopped power condition to the active power condition. This field is only
applicable to SCSI target devices that implement the START STOP UNIT command (see SBC-3). This time
does not include the processing time for the command that caused this transition to occur or any SCSI
transport protocol specific waiting time (e.g., the NOTIFY (ENABLE SPINUP) requirement described in
SPL-3). A value of zero indicates that the recovery time is not specified. A value of FFFFh indicates that the
recovery time is more than 65.534 seconds.

The STANDBY_Z CONDITION RECOVERY TIME field indicates the time, in one millisecond increments, that the
logical unit takes to transition from the standby_z power condition to the active power condition. This time
does not include the processing time for the command that caused this transition to occur or any SCSI
transport protocol specific waiting time (e.g., the NOTIFY (ENABLE SPINUP) requirement described in
SPL-3). A value of zero indicates that the recovery time is not specified. A value of FFFFh indicates that the
recovery time is more than 65.534 seconds.

The STANDBY_Y CONDITION RECOVERY TIME field indicates the time, in one millisecond increments, that the
logical unit takes to transition from the standby_y power condition to the active power condition. This time
does not include the processing time for the command that caused this transition to occur or any SCSI
transport protocol specific waiting time (e.g., the NOTIFY (ENABLE SPINUP) requirement described in
SPL-3). A value of zero indicates that the recovery time is not specified. A value of FFFFh indicates that the
recovery time is more than 65.534 seconds.

The IDLE_A CONDITION RECOVERY TIME field indicates the time, in one millisecond increments, that the logical
unit takes to transition from the idle_a power condition to the active power condition. This time does not
include the processing time for the command that caused this transition to occur. A value of zero indicates that
the recovery time is not specified. A value of FFFFh indicates that the recovery time is more than 65.534
seconds.

The IDLE_B CONDITION RECOVERY TIME field indicates the time, in one millisecond increments, that the logical
unit takes to transition from the idle_b power condition to the active power condition. This time does not
include the processing time for the command that caused this transition to occur. A value of zero indicates that
the recovery time is not specified. A value of FFFFh indicates that the recovery time is more than 65.534
seconds.

The IDLE_C CONDITION RECOVERY TIME field indicates the time, in one millisecond increments, that the logical
unit takes to transition from the idle_c power condition to the active power condition. This time does not
include the processing time for the command that caused this transition to occur. A value of zero indicates that

Working Draft SCSI Primary Commands - 4 (SPC-4) 775

T10/BSR INCITS 513 Revision 37 17 May 2014

the recovery time is not specified. A value of FFFFh indicates that the recovery time is more than 65.534
seconds.

7.8.11 Power Consumption VPD page

The Power Consumption VPD page (see table 626) provides an application client with a list of the available
settings to limit the maximum power consumption (e.g., see USB-3) of the logical unit while in the active
power condition (see 5.11.4) as described in 5.11.2.

Table 626 — Power Consumption VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (8Dh)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Power consumption descriptor list
4
•• • Power consumption descriptor [first]
7
••
•
n-3
•• • Power consumption descriptor [last]
n

The PERIPHERAL QUALIFIER field and PERIPHERAL DEVICE TYPE field are defined in 7.8.2.

The PAGE CODE field and PAGE LENGTH field are defined in 7.8.2, and shall be set to the value shown in table
626 for the Power Consumption VPD page.

Each power consumption descriptor (see table 627) describes one maximum power consumption level that
the application client may establish for use by the active power condition (see 5.11.4) using the Power
Consumption mode page (see 7.5.14) as described in 5.11.2.

Table 627 — Power consumption descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 POWER CONSUMPTION IDENTIFIER

1 Reserved POWER CONSUMPTION UNITS

2 (MSB)
POWER CONSUMPTION VALUE
3 (LSB)

The POWER CONSUMPTION IDENTIFIER field contains a value that the application client or device server may use
in the Power Consumption mode page (see 7.5.14) to specify which descriptor is being used to effect the
maximum power consumption level.

776 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The POWER CONSUMPTION UNITS field (see table 628) indicates the units used for the POWER CONSUMPTION
VALUEfield.

Table 628 — POWER CONSUMPTION UNITS field

Code Units
000b Gigawatts
001b Megawatts
010b Kilowatts
011b Watts
100b Milliwatts
101b Microwatts
all others Reserved

The POWER CONSUMPTION VALUE field indicates the maximum power consumption associated with the identifier
in the POWER CONSUMPTION IDENTIFIER field using the units specified by the POWER CONSUMPTION UNITS field.

7.8.12 Protocol Specific Logical Unit Information VPD page

The Protocol Specific Logical Unit Information VPD page (see table 629) contains protocol specific
parameters associated with a SCSI port that may be different for each logical unit in the SCSI target device.

Table 629 — Protocol Specific Logical Unit Information VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (90h)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Logical unit information descriptor list
4
Logical unit information descriptor
•• •
(see table 630) [first]

•
•
•

Logical unit information descriptor

•• •
(see table 630) [last]
n

The PERIPHERAL QUALIFIER field, PERIPHERAL DEVICE TYPE field, and PAGE LENGTH field are defined in 7.8.2.

The PAGE CODE field is defined in 7.8.2 and shall be set as shown in table 629 for the Protocol Specific Logical
Unit Information VPD page.

Working Draft SCSI Primary Commands - 4 (SPC-4) 777

T10/BSR INCITS 513 Revision 37 17 May 2014

The logical unit information descriptor list contains descriptors for SCSI ports known to the device server that
is processing the INQUIRY command. The logical unit information descriptors (see table 630) may be
returned in any order.

Table 630 — Logical unit information descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
RELATIVE PORT IDENTIFIER
1 (LSB)
2 Reserved PROTOCOL IDENTIFIER

3
4 Reserved
5
6 (MSB)
PROTOCOL SPECIFIC DATA LENGTH (n-7)
7 (LSB)
8 Per logical unit SCSI transport protocol specific
n data

The RELATIVE PORT IDENTIFIER field (see 4.3.4) indicates the relative port identifier of the SCSI port to which the
logical unit information descriptor applies.

The PROTOCOL IDENTIFIER field indicates the SCSI transport protocol to which the logical unit information
descriptor applies as described in 7.6.1.

The PROTOCOL SPECIFIC DATA LENGTH field indicates the length in bytes of the per logical unit SCSI transport
protocol specific data.

The per logical unit SCSI transport protocol specific data is defined by the SCSI transport protocol standard
that corresponds to the SCSI port.

778 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.8.13 Protocol Specific Port Information VPD page

The Protocol Specific Port Information VPD page (see table 631) contains protocol specific parameters
associated with a SCSI port that are the same for all logical units in the SCSI target device.

Table 631 — Protocol Specific Port Information VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (91h)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Port information descriptor list
4
•• • Port information descriptor (see table 630) [first]

••
•

•• • Port information descriptor (see table 630) [last]

n

The PERIPHERAL QUALIFIER field, PERIPHERAL DEVICE TYPE field, and PAGE LENGTH field are defined in 7.8.2.

The PAGE CODE field is defined in 7.8.2 and shall be set as shown in table 631 for the Protocol Specific Port
Information VPD page.

Working Draft SCSI Primary Commands - 4 (SPC-4) 779

T10/BSR INCITS 513 Revision 37 17 May 2014

The port information descriptor list contains descriptors for SCSI ports known to the device server that is
processing the INQUIRY command. The port information descriptors (see table 632) may be returned in any
order.

Table 632 — Port information descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
RELATIVE PORT IDENTIFIER
1 (LSB)
2 Reserved PROTOCOL IDENTIFIER

3
4 Reserved
5
6 (MSB)
PROTOCOL SPECIFIC DATA LENGTH (n-7)
7 (LSB)
8
•• • Shared SCSI transport protocol specific data
n

The RELATIVE PORT IDENTIFIER field (see 4.3.4) indicates the relative port identifier of the SCSI port to which the
port information descriptor applies.

The PROTOCOL IDENTIFIER field indicates the SCSI transport protocol to which the port information descriptor
applies as described in 7.6.1.

The PROTOCOL SPECIFIC DATA LENGTH field indicates the length in bytes of the shared SCSI transport protocol
specific data.

The shared SCSI transport protocol specific data is defined by the SCSI transport protocol standard that
corresponds to the SCSI target port.

780 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.8.14 SCSI Ports VPD page

The SCSI Ports VPD page (see table 633) contains designation descriptors for all the SCSI ports in a SCSI
target device.

The SCSI Ports VPD page only reports information on SCSI ports known to the device server processing the
INQUIRY command. The REPORT LUNS well-known logical unit (see 8.2) may be used to return information
on all SCSI ports in the SCSI device (i.e., all target ports and all initiator ports).

If the device server detects that a SCSI port is added or removed from the SCSI device and the SCSI port
designation descriptor list changes, then the device server shall establish a unit attention condition (see
SAM-5) for the initiator port associated with every I_T nexus, with the additional sense code set to INQUIRY
DATA HAS CHANGED.

Table 633 — SCSI Ports VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (88h)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Designation descriptor list
4
SCSI port designation descriptor
•• •
(see table 634) [first]

••
•

SCSI port designation descriptor

•• •
(see table 634) [last]
n

The PERIPHERAL QUALIFIER field, PERIPHERAL DEVICE TYPE field, and PAGE LENGTH field are defined in 7.8.2.

The PAGE CODE field is defined in 7.8.2 and shall be set as shown in table 633 for the SCSI Ports VPD page.

Working Draft SCSI Primary Commands - 4 (SPC-4) 781

T10/BSR INCITS 513 Revision 37 17 May 2014

Each SCSI port designation descriptor (see table 634) identifies a SCSI port. The SCSI port designation
descriptors may be returned in any order.

Table 634 — SCSI port designation descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0
Reserved
1
2 (MSB)
RELATIVE PORT IDENTIFIER
3 (LSB)
4
Reserved
5
6 (MSB)
INITIATOR PORT TRANSPORTID LENGTH (k-7)
7 (LSB)
8
•• • INITIATOR PORT TRANSPORTID, if any
k
k+1
Reserved
k+2
k+3 (MSB)
TARGET PORT DESCRIPTORS LENGTH (n-(k+4))
k+4 (LSB)
Target port descriptor list
k+5
•• • Target port descriptor (see table 635) [first]

•
••

•• • Target port descriptor (see table 635) [last]

n

The RELATIVE PORT IDENTIFIER field (see 4.3.4) contains the relative port identifier of the SCSI port to which the
SCSI port designation descriptor applies.

The INITIATOR PORT TRANSPORTID LENGTH field indicates the length of the INITIATOR PORT TRANSPORTID field. An
INITIATOR PORT TRANSPORTID LENGTH field set to zero indicates no INITIATOR PORT TRANSPORTID field is present
(i.e., the SCSI port is not an initiator port).

If the INITIATOR PORT TRANSPORTID LENGTH field is set to a non-zero value, the INITIATOR PORT TRANSPORTID
field indicates a TransportID identifying the initiator port as defined in 7.6.4.

The TARGET PORT DESCRIPTORS LENGTH field indicates the length of the target port descriptors, if any. A TARGET
PORT DESCRIPTORS LENGTH field set to zero indicates no target port descriptors are present (i.e., the SCSI port
is not a target port).

782 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Each target port descriptor (see table 635) contains an identifier for the target port. The target port descriptors
may be returned in any order.

Table 635 — Target port descriptor

Bit
7 6 5 4 3 2 1 0
Byte
0 PROTOCOL IDENTIFIER CODE SET

1 PIV (1b) Reserved ASSOCIATION (01b) DESIGNATOR TYPE

2 Reserved
3 DESIGNATOR LENGTH (n-3)
4
•• • DESIGNATOR
n

The PROTOCOL IDENTIFIER field indicates the SCSI transport protocol to which the designation descriptor
applies as described in 7.6.1.

The CODE SET field, PIV field, ASSOCIATION field, DESIGNATOR TYPE field, DESIGNATOR LENGTH field, and
DESIGNATOR field are as defined in the Device Identification VPD page designation descriptor (see 7.8.6.1),
with the following additional requirements:

a) the PIV bit shall be set to one (i.e., the PROTOCOL IDENTIFIER field always contains a SCSI transport
protocol identifier); and
b) the ASSOCIATION field shall be set to 01b (i.e., the descriptor always identifies a target port).

Working Draft SCSI Primary Commands - 4 (SPC-4) 783

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.15 Software Interface Identification VPD page

The Software Interface Identification VPD page (see table 636) provides identification of software interfaces
applicable to the logical unit. Logical units may have more than one associated software interface identifier.

NOTE 64 - Application clients are allowed to use the software IDs to differentiate peripheral device functions
in cases where the command set (e.g., processor devices) is too generic to distinguish different software
interfaces implemented.

Table 636 — Software Interface Identification VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (84h)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Software interface identifier list
4
•• • Software interface identifier [first]
10
••
•
n-9
•• • Software interface identifier [last]
n

The PERIPHERAL QUALIFIER field, PERIPHERAL DEVICE TYPE field, and PAGE LENGTH field are defined in 7.8.2.

The PAGE CODE field is defined in 7.8.2 and shall be set as shown in table 636 for the Software Interface
Identification VPD page.

Each software interface identifier (see table 637) information that identifies a software interface implemented
by the logical unit. The contents of software interface identifier are in EUI-48 format.

Table 637 — Software interface identifier format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
1 IEEE COMPANY_ID

2 (LSB)
3 (MSB)
4 VENDOR SPECIFIC EXTENSION IDENTIFIER

5 (LSB)

The IEEE COMPANY_ID field contains a 24-bit canonical format OUI assigned by the IEEE.

784 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The VENDOR SPECIFIC EXTENSION IDENTIFIER a 24-bit numeric value that is uniquely assigned by the
organization associated with the OUI as required by the IEEE definition of EUI-48. The combination of OUI
and vendor specific extension identifier shall uniquely identify the software interface.

7.8.16 Supported VPD Pages VPD page

The Supported VDP Pages VPD page contains a list of the VPD page codes supported by the logical unit (see
table 638). If a device server supports any VPD pages, the device server shall support this VPD page.

Table 638 — Supported VPD Pages VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (00h)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4
•• • Supported VPD page list
n

The PERIPHERAL QUALIFIER field, PERIPHERAL DEVICE TYPE field, and PAGE LENGTH field are defined in 7.8.2.

The PAGE CODE field is defined in 7.8.2 and shall be set as shown in table 638 for the Supported VDP Pages
VPD page.

The supported VPD page list shall contain a list of all VPD page codes (see 7.8) implemented by the logical
unit in ascending order beginning with page code 00h.

Working Draft SCSI Primary Commands - 4 (SPC-4) 785

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.17 Third-party Copy VPD page

7.8.17.1 Third-party Copy VPD page overview

The Third-party Copy VPD page (see table 639) provides a means to retrieve descriptors that indicate the
capabilities supported by the copy manager (see 5.16.2).

Table 639 — Third-party Copy VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (8Fh)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Third-party copy descriptors
4
•• • Third-party copy descriptor [first] (see 7.8.17.2)

••
•

•• • Third-party copy descriptor [last] (see 7.8.17.2)

n

The PERIPHERAL QUALIFIER field, PERIPHERAL DEVICE TYPE field, and PAGE LENGTH field are defined in 7.8.2.

The PAGE CODE field is defined in 7.8.2 and shall be set as shown in table 639 for the Third-party Copy VPD
page.

The third-party copy descriptors shall be returned in ascending order based on third-party copy descriptor type
values (see 7.8.17.3).

7.8.17.2 Third-party copy descriptor format

Each third-party copy descriptor shall have the format shown in table 640.

Table 640 — Third-party copy descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
THIRD-PARTY COPY DESCRIPTOR TYPE
1 (LSB)
2 (MSB)
THIRD-PARTY COPY DESCRIPTOR LENGTH (n-3)
3 (LSB)
4
•• • Third-party copy parameters
n

786 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The THIRD-PARTY COPY DESCRIPTOR TYPE field is described in 7.8.17.3.

The THIRD-PARTY COPY DESCRIPTOR LENGTH field indicates the number of bytes of third-party copy parameters
that follow. All third-party copy descriptor lengths are a multiple of four.

The contents of the third-party copy parameters are indicated by the contents of the THIRD-PARTY COPY
DESCRIPTOR TYPE field (see 7.8.17.3).

7.8.17.3 Third-party copy descriptor type codes

Third-party copy descriptor type codes (see table 641) indicate which third-party copy descriptor is being
returned.

Table 641 — Third-party copy descriptor type codes

Third-party copy descriptor name Code Reference Support a

Block Device ROD Limits 0000h SBC-3 See b
Supported Commands 0001h 7.8.17.4 Mandatory
Parameter Data 0004h 7.8.17.5 See c
Supported Descriptors 0008h 7.8.17.6 See c
Supported CSCD Descriptor IDs 000Ch 7.8.17.7 See c
ROD Token Features 0106h 7.8.17.8 See d
Supported ROD Token and ROD Types 0108h 7.8.17.9 See d
General Copy Operations 8001h 7.8.17.10 Mandatory
Stream Copy Operations 9101h 7.8.17.11 See e
Held Data C001h 7.8.17.12 See f
Restricted (see applicable command standard) E000h to EFFFh
Reserved All other codes
a
Applicable only if the Third-party Copy VPD page is supported.
b
Mandatory as defined by the applicable command standard.
c
Mandatory if the EXTENDED COPY(LID4) command (see 6.4) or EXTENDED COPY(LID1)
command (see 6.5) is supported.
d Mandatory if the EXTENDED COPY command ROD CSCD descriptor (see 6.4.5.9) is supported
or as defined by the applicable command standard.
e
Mandatory if any EXTENDED COPY command stream segment descriptor (see 6.4.6.1) is
supported.
f
Mandatory if the RECEIVE COPY DATA(LID4) command (see 6.20) or the RECEIVE COPY
DATA(LID1) command (see 6.21) is supported.

Working Draft SCSI Primary Commands - 4 (SPC-4) 787

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.17.4 Supported Commands third-party copy descriptor

7.8.17.4.1 Supported Commands third-party copy descriptor overview

The Supported Commands third-party copy descriptor (see table 642) indicates which commands (i.e., combi-
nations of operation code and service action) (see 5.16.3) the copy manager supports.

Table 642 — Supported Commands third-party copy descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
THIRD-PARTY COPY DESCRIPTOR TYPE (0001h)
1 (LSB)
2 (MSB)
THIRD-PARTY COPY DESCRIPTOR LENGTH (n-3)
3 (LSB)
4 COMMANDS SUPPORTED LIST LENGTH (m-4)
Commands supported list
5
Command support descriptor (see table 643)
•• •
[first]

••
•

Command support descriptor (see table 643)

•• •
[last]
m
m+1
•• • DESCRIPTOR PAD (if any)
n

The THIRD-PARTY COPY DESCRIPTOR TYPE field is described in 7.8.17.3 and shall be set as shown in table 642
for the Supported Commands third-party copy descriptor.

The THIRD-PARTY COPY DESCRIPTOR LENGTH field is described in 7.8.17.2.

The COMMANDS SUPPORTED LIST LENGTH field indicates the length, in bytes, of the commands supported list.

Each command support descriptor (see 7.8.17.4.2) lists the service actions that the copy manager supports
for a specific operation code. The Supported Commands third-party copy descriptor shall contain command
support descriptors for at least the following operation codes in ascending order by operation code value:

1) 83h (e.g., the EXTENDED COPY(LID4) command (see 6.4)); and

2) 84h (e.g., the RECEIVE COPY STATUS(LID4) command (see 6.24)).

The DESCRIPTOR PAD field shall contain zero to three bytes set to zero such that the total length of the
Supported Commands third-party copy descriptor is a multiple of four.

788 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.8.17.4.2 Command support descriptor format

Each command support descriptor (see table 643) indicates one or more third-party copy commands (see
5.16.3) that the copy manager supports using one operation code and all supported service actions for that
operation code.

Table 643 — Command support descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 SUPPORTED OPERATION CODE

1 SUPPORTED SERVICE ACTIONS LIST LENGTH (m-1)

2
•• • List of supported service actions
m

The SUPPORTED OPERATION CODE field indicates the operation code for which a list of supported service
actions is being returned.

The SUPPORTED SERVICE ACTIONS LIST LENGTH field indicates the length, in bytes, of the list of supported
services actions.

The list of supported service actions contains one byte for each service action of the operation code indicated
by the SUPPORTED OPERATION CODE field that the copy manager supports, with a unique supported service
action in each byte. The service actions shall appear in the list in ascending numerical order.

Working Draft SCSI Primary Commands - 4 (SPC-4) 789

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.17.5 Parameter Data third-party copy descriptor

The Parameter Data third-party copy descriptor (see table 644) indicates the limits that the copy manager
places on the contents of the EXTENDED COPY command parameter data.

Table 644 — Parameter Data third-party copy descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
THIRD-PARTY COPY DESCRIPTOR TYPE (0004h)
1 (LSB)
2 (MSB)
THIRD-PARTY COPY DESCRIPTOR LENGTH (001Ch)
3 (LSB)
4
•• • Reserved
7
8 (MSB)
MAXIMUM CSCD DESCRIPTOR COUNT
9 (LSB)
10 (MSB)
MAXIMUM SEGMENT DESCRIPTOR COUNT
11 (LSB)
12 (MSB)
•• • MAXIMUM DESCRIPTOR LIST LENGTH
15 (LSB)
16 (MSB)
•• • MAXIMUM INLINE DATA LENGTH
19 (LSB)
20
•• • Reserved
31

The THIRD-PARTY COPY DESCRIPTOR TYPE field is described in 7.8.17.3 and shall be set as shown in table 644
for the Parameter Data third-party copy descriptor.

The THIRD-PARTY COPY DESCRIPTOR LENGTH field is described in 7.8.17.2 and shall be set as shown in table
644 for the Parameter Data third-party copy descriptor.

The MAXIMUM CSCD DESCRIPTOR COUNT field indicates the maximum number of CSCD descriptors that the
copy manager allows in an EXTENDED COPY parameter list (see 5.16.7.1).

The MAXIMUM SEGMENT COUNT field indicates the maximum number of segment descriptors that the copy
manager allows in an EXTENDED COPY parameter list (see 5.16.7.1).

The MAXIMUM DESCRIPTOR LIST LENGTH field indicates the maximum length, in bytes, of the CSCD descriptor
list and segment descriptor list that the copy manager allows in an EXTENDED COPY command parameter
list (see 5.16.7.1).

790 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The MAXIMUM INLINE DATA LENGTH field indicates the length, in bytes, of the largest amount of inline data (see
6.4.3.6) that the copy manager supports in an EXTENDED COPY parameter list (see 5.16.7.1). The MAXIMUM
INLINE DATA LENGTH field shall be set to zero if the copy manager does not support segment descriptor type
code 04h (see 6.4.6.6).

7.8.17.6 Supported Descriptors third-party copy descriptor

The Supported Descriptors third-party copy descriptor (see table 645) indicates which CSCD descriptors (see
6.4.5.1) and segment descriptors (see 6.4.6.1) the copy manager supports.

Table 645 — Supported Descriptors third-party copy descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
THIRD-PARTY COPY DESCRIPTOR TYPE (0008h)
1 (LSB)
2 (MSB)
THIRD-PARTY COPY DESCRIPTOR LENGTH (n-3)
3 (LSB)
4 SUPPORTED DESCRIPTOR LIST LENGTH (m-4)
5
•• • List of supported descriptor type codes
m
m+1
•• • DESCRIPTOR PAD (if any)
n

The THIRD-PARTY COPY DESCRIPTOR TYPE field is described in 7.8.17.3 and shall be set as shown in table 645
for the Supported Descriptors third-party copy descriptor.

The THIRD-PARTY COPY DESCRIPTOR LENGTH field is described in 7.8.17.2.

The SUPPORTED DESCRIPTOR LIST LENGTH field indicates the length, in bytes, of the list of supported descriptor
type codes.

The list of supported descriptor type codes contains one byte for each CSCD descriptor and segment
descriptor DESCRIPTOR TYPE CODE value (see 6.4.4) supported by the copy manager, with a unique supported
DESCRIPTOR TYPE CODE value in each byte. The descriptor type code values shall appear in the list in
ascending numerical order.

The DESCRIPTOR PAD field shall contain zero to three bytes set to zero such that the total length of the
Supported Descriptors third-party copy descriptor is a multiple of four.

Working Draft SCSI Primary Commands - 4 (SPC-4) 791

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.17.7 Supported CSCD Descriptor IDs third-party copy descriptor

The Supported CSCD Descriptor IDs third-party copy descriptor (see table 646) indicates which CSCD
descriptor IDs (see table 133 in 6.4.5.1) other than 0000h to 07FFh the copy manager supports.

Table 646 — Supported CSCD Descriptor IDs third-party copy descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
THIRD-PARTY COPY DESCRIPTOR TYPE (000Ch)
1 (LSB)
2 (MSB)
THIRD-PARTY COPY DESCRIPTOR LENGTH (n-3)
3 (LSB)
4 (MSB) SUPPORTED CSCD DESCRIPTOR IDS LIST LENGTH
5 (m-5) (LSB)
Supported CSCD descriptor ID list
6 (MSB)
SUPPORTED CSCD DESCRIPTOR ID [first]
7 (LSB)
••
•
m-1 (MSB)
SUPPORTED CSCD DESCRIPTOR ID [last]
m (LSB)
m+1
•• • DESCRIPTOR PAD (if any)
n

The THIRD-PARTY COPY DESCRIPTOR TYPE field is described in 7.8.17.3 and shall be set as shown in table 646
for the Supported CSCD Descriptor IDs third-party copy descriptor.

The THIRD-PARTY COPY DESCRIPTOR LENGTH field is described in 7.8.17.2.

The SUPPORTED CSCD DESCRIPTOR IDS LIST LENGTH field indicates the length, in bytes, of the list of supported
CSCD descriptor IDs.

Each SUPPORTED CSCD DESCRIPTOR ID field indicates one unique CSCD descriptor ID (see table 150 in 6.4.6.1)
with a value greater than 07FFh that is supported by the copy manger. The CSCD descriptor IDs shall appear
in the list in ascending numerical order.

In addition to the CSCD descriptor IDs listed in the Supported CSCD Descriptor IDs third-party copy
descriptor, the copy manager shall support each CSCD descriptor ID between zero and one less than the
value in the MAXIMUM CSCD DESCRIPTOR COUNT field in the Parameter Data third-party copy descriptor (see
7.8.17.5).

792 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If the TOKEN_IN bit is set to one in any ROD token descriptor in the Supported ROD Types third-party copy
descriptor (see 7.8.17.9), then F800h shall be included in the CSCD descriptor IDs list. F800h shall not be
included in the CSCD descriptor IDs list if:

a) the Supported ROD Types third-party copy descriptor is not included in the Third-party Copy VPD
page; or
b) the TOKEN_IN bit is set to zero in all the ROD token descriptors in the Supported ROD Types
third-party copy descriptor.

The DESCRIPTOR PAD field shall contain zero to three bytes set to zero such that the total length of the
Supported CSCD Descriptor IDs Descriptors third-party copy descriptor is a multiple of four.

Working Draft SCSI Primary Commands - 4 (SPC-4) 793

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.17.8 ROD Token Features third-party copy descriptor

7.8.17.8.1 ROD Token Features third-party copy descriptor overview

The ROD Token Features third-party copy descriptor (see table 647) indicates the limits that the copy
manager places on processing of ROD tokens by copy operations (see 5.16.4.3).

Table 647 — ROD Token Features third-party copy descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
THIRD-PARTY COPY DESCRIPTOR TYPE (0106h)
1 (LSB)
2 (MSB)
THIRD-PARTY COPY DESCRIPTOR LENGTH (n-3)
3 (LSB)
4 Reserved REMOTE TOKENS

5
•• • Reserved
15
16 (MSB)
•• • MINIMUM TOKEN LIFETIME
19 (LSB)
20 (MSB)
•• • MAXIMUM TOKEN LIFETIME
23 (LSB)
24 (MSB)
•• • MAXIMUM TOKEN INACTIVITY TIMEOUT
27 (LSB)
28
•• • Reserved
45
46 (MSB) ROD DEVICE TYPE SPECIFIC FEATURES
47 DESCRIPTORS LENGTH (m-47) (LSB)
ROD device type specific features descriptors
48
ROD device type specific features descriptor
•• •
[first]

••
•

ROD device type specific features descriptor

•• •
[last]
m
m+1
•• • DESCRIPTOR PAD (if any)
n

794 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The THIRD-PARTY COPY DESCRIPTOR TYPE field is described in 7.8.17.3 and shall be set as shown in table 647
for the ROD Token Features third-party copy descriptor.

The THIRD-PARTY COPY DESCRIPTOR LENGTH field is described in 7.8.17.2.

The REMOTE TOKENS field (see table 648) indicates the level of support the copy manager provides for ROD
tokens (see 5.16.6) that are not created by the copy manager that is processing the copy operation (see
5.16.4.3).

Table 648 — REMOTE TOKENS field

Code Description
0h The copy manager:
a) supports the use of ROD tokens created by itself or any other copy manager in
the same SCSI target device as copy sources and copy destinations; and
b) does not support creation of ROD tokens that represent any bytes other than
those accessible to its logical unit (e.g., a ROD CSCD descriptor (see 6.4.5.9)
in which the ROD TYPE field is set to zero and the ROD PRODUCER CSCD
DESCRIPTOR ID field specifies a copy manager producer of the ROD that is not
the copy manager that is processing the EXTENDED COPY command).
4h The copy manager:
a) supports the use of ROD tokens created by itself or any other copy manager in
any SCSI target device as copy sources and copy destinations; and
b) does not support creation of ROD tokens that represent any bytes other than
those accessible to its logical unit.
6h The copy manager supports:
a) the use of ROD tokens created by itself or any other copy manager in any SCSI
target device as copy sources and copy destinations; and
b) the creation of ROD tokens that represent bytes that are accessible or not
accessible to its logical unit.
all others Reserved

The MINIMUM TOKEN LIFETIME field indicates the smallest lifetime, in seconds, that the copy manager supports
for a ROD token. If a ROD token lifetime is requested (e.g., if the REQUESTED ROD TOKEN LIFETIME field in a
ROD CSCD descriptor (see 6.4.5.9) specifies a value) that is less than the value in the MINIMUM TOKEN
LIFETIME field, then the ROD token lifetime may be set to the value in the MINIMUM TOKEN LIFETIME field.

The MAXIMUM TOKEN LIFETIME field indicates the largest lifetime, in seconds, that the copy manager supports
for a ROD token. If a ROD token lifetime is requested (e.g., if the REQUESTED ROD TOKEN LIFETIME field in a
ROD CSCD descriptor (see 6.4.5.9) specifies a value) that is greater than the value in the MAXIMUM TOKEN
LIFETIME field, then the copy manager shall terminate (see 6.4.5.9) the copy operation (see 5.16.4.3).

The MAXIMUM TOKEN INACTIVITY TIMEOUT field indicates the largest inactivity timeout value, in seconds, that the
copy manager supports for a ROD token. If a ROD token inactivity timeout is requested (e.g., if the REQUESTED
ROD TOKEN INACTIVITY TIMEOUT field in a ROD CSCD descriptor (see 6.4.5.9) specifies a value) that is greater
than the value in the MAXIMUM TOKEN INACTIVITY TIMEOUT field, then the copy manager shall terminate (see
6.4.5.9) the copy operation (see 5.16.4.3). The MAXIMUM TOKEN INACTIVITY TIMEOUT field is also used by the
POPULATE TOKEN command (see SBC-3).

The ROD DEVICE TYPE SPECIFIC FEATURES DESCRIPTORS LENGTH field indicates the length, in bytes, of the ROD
device type specific features descriptors.

Working Draft SCSI Primary Commands - 4 (SPC-4) 795

T10/BSR INCITS 513 Revision 37 17 May 2014

Each ROD device type specific features descriptor provides support information for internal RODs and ROD
tokens associated with a specific device type. The ROD device type specific features descriptors shall be
included in the ROD Token Features third-party copy descriptor in the following order:

1) zero or one block ROD device type specific features descriptors (see 7.8.17.8.2);
2) zero or one stream ROD device type specific features descriptors (see 7.8.17.8.3); and
3) zero or one copy manager ROD device type specific features descriptors (see 7.8.17.8.4).

ROD device type specific features descriptors:

a) shall be included for each device type for which internal RODs or ROD tokens may be generated by
the copy manager; and
b) shall not be included for any device type for which the copy manager does not generate internal
RODs or ROD tokens.

7.8.17.8.2 Block ROD device type specific features descriptor

The block ROD device type specific features descriptor (see table 649) provides support information for ROD
tokens associated with block type devices.

Table 649 — Block ROD device type specific features descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR FORMAT (000b) PERIPHERAL DEVICE TYPE (00h)
1 Reserved
2 (MSB)
DESCRIPTOR LENGTH (002Ch)
3 (LSB)
4
Reserved
5
6 (MSB)
OPTIMAL BLOCK ROD LENGTH GRANULARITY
7 (LSB)
8 (MSB)
•• • MAXIMUM BYTES IN BLOCK ROD
15 (LSB)
16 (MSB)
•• • OPTIMAL BYTES IN BLOCK ROD TRANSFER
23 (LSB)
24 (MSB)
•• • OPTIMAL BYTES TO TOKEN PER SEGMENT
31 (LSB)
32 (MSB)
•• • OPTIMAL BYTES FROM TOKEN PER SEGMENT
39 (LSB)
40
•• • Reserved
47

796 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The DESCRIPTOR FORMAT field indicates the format of the descriptor and shall be set as shown in table 649 for
the block ROD device type specific features descriptor.

The PERIPHERAL DEVICE TYPE field indicates the device type associated with the descriptor and shall be set as
shown in table 649 for the block ROD device type specific features descriptor.

The DESCRIPTOR LENGTH field indicates the number of bytes that follow in the descriptor and shall be set as
shown in table 649 for the block ROD device type specific features descriptor.

The OPTIMAL BLOCK ROD LENGTH GRANULARITY field indicates the optimal size granularity in logical blocks for a
ROD or ROD token. RODs or ROD tokens with sizes not equal to a multiple of this value may incur processing
delays with adverse effects. If the OPTIMAL BLOCK ROD LENGTH GRANULARITY field is set to zero, then the copy
manager does not report the optimal ROD or ROD token length granularity for a block device.

The MAXIMUM BYTES IN BLOCK ROD field indicates the largest number of bytes the copy manager supports in an
internal ROD or ROD token for a block device. If a third-party copy command (see 5.16.3) attempts to
populate an internal ROD or ROD token with more than the indicated number of bytes, then the copy manager
shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST. If the
MAXIMUM BYTES IN BLOCK ROD field is set to zero, then the copy manager does not report the largest number of
bytes the copy manager supports in an internal ROD or ROD token for a block device.

The OPTIMAL BYTES IN BLOCK ROD TRANSFER field indicates the optimal number of bytes the copy manager is
able to transfer in a single third-party copy command (see 5.16.3) or EXTENDED COPY segment descriptor
(see 6.4.6). Processing delays with adverse effects may be incurred if a third-party copy command attempts to
transfer more bytes than indicated by the OPTIMAL BYTES IN BLOCK ROD TRANSFER field to or from a ROD
associated with a block device. If the OPTIMAL BYTES IN BLOCK ROD TRANSFER field is set to zero, then the copy
manager does not report the optimal number of bytes the copy manager is able to transfer in a single
third-party copy command for a block device. If the OPTIMAL BYTES IN BLOCK ROD TRANSFER field is set to
FFFF FFFF FFFF FFFFh, then there is no limit on the optimal number of bytes the copy manager is able to
transfer in a single third-party copy command.

The OPTIMAL BYTES TO TOKEN PER SEGMENT field indicates the optimal number of bytes of user data the copy
manager is able to transfer into a ROD associated with a block device in a single segment descriptor (see
6.4.6) or block device range descriptor (see SBC-3). Processing delays with adverse effects may be incurred
if a third-party copy command attempts to transfer more bytes of user data in a single descriptor than indicated
by the OPTIMAL BYTES TO TOKEN PER SEGMENT field to a ROD associated with a block device. If the OPTIMAL
BYTES TO TOKEN PER SEGMENT field is set to zero, then the copy manager does not report the optimal number
of bytes the copy manager is able to transfer in a single descriptor for a block device. If the OPTIMAL BYTES TO
TOKEN PER SEGMENT field is set to FFFF FFFF FFFF FFFFh, then there is no limit on the optimal number of
bytes the copy manager is able to transfer in a single descriptor.

The OPTIMAL BYTES FROM TOKEN PER SEGMENT field indicates the optimal number of bytes of user data the
copy manager is able to transfer from a ROD associated with a block device in a single segment descriptor
(see 6.4.6) or block device range descriptor (see SBC-3). Processing delays with adverse effects may be
incurred if a third-party copy command attempts to transfer more bytes of user data in a single descriptor than
indicated by the OPTIMAL BYTES FROM TOKEN PER SEGMENT field from a ROD associated with a block device. If
the OPTIMAL BYTES FROM TOKEN PER SEGMENT field is set to zero, then the copy manager does not report the
optimal number of bytes the copy manager is able to transfer in a single descriptor for a block device. If the
OPTIMAL BYTES FROM TOKEN PER SEGMENT field is set to FFFF FFFF FFFF FFFFh, then there is no limit on the
optimal number of bytes the copy manager is able to transfer in a single descriptor.

Working Draft SCSI Primary Commands - 4 (SPC-4) 797

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.17.8.3 Stream ROD token device type features descriptor

The stream ROD device type specific features descriptor (see table 650) provides support information for
ROD tokens associated with stream type devices.

Table 650 — Stream ROD device type specific features descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR FORMAT (000b) PERIPHERAL DEVICE TYPE (01h)
1 Reserved
2 (MSB)
DESCRIPTOR LENGTH (002Ch)
3 (LSB)
4
•• • Reserved
7
8 (MSB)
•• • MAXIMUM BYTES IN STREAM ROD
15 (LSB)
16 (MSB)
•• • OPTIMAL BYTES IN STREAM ROD TRANSFER
23 (LSB)

24
•• • Reserved
47

The DESCRIPTOR FORMAT field indicates the format of the descriptor and shall be set as shown in table 650 for
the stream ROD device type specific features descriptor.

The PERIPHERAL DEVICE TYPE field indicates the device type associated with the descriptor and shall be set as
shown in table 650 for the stream ROD device type specific features descriptor.

The DESCRIPTOR LENGTH field indicates the number of bytes that follow in the descriptor and shall be set as
shown in table 650 for the stream ROD device type specific features descriptor.

The MAXIMUM BYTES IN STREAM ROD field indicates the largest number of bytes the copy manager supports in
an internal ROD or ROD token for a stream device. If third-party copy command (see 5.16.3) attempts to
populate an internal ROD or ROD token with more than the indicated number of bytes, then the copy manager
shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST. If the
MAXIMUM BYTES IN STREAM ROD field is set to zero, then the copy manager does not report a largest number of
bytes the copy manager supports in an internal ROD or ROD token for a stream device.

The OPTIMAL BYTES IN STREAM ROD TRANSFER field indicates the optimal number of bytes the copy manager is
able to transfer in a single third-party copy command (see 5.16.3) or EXTENDED COPY segment descriptor
(see 6.4.6). Processing delays with adverse effects may be incurred if a third-party copy command attempts to
transfer more bytes than indicated by the OPTIMAL BYTES IN STREAM TOKEN TRANSFER field to or from a stream
device. If the OPTIMAL BYTES IN STREAM ROD TRANSFER field is set to zero, then the copy manager does not
report the optimal number of bytes the copy manager is able to transfer in a single third-party copy command

798 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

for a stream device. If the OPTIMAL BYTES IN STREAM ROD TRANSFER field is set to FFFF FFFF FFFF FFFFh,
then there is no limit on the optimal number of bytes the copy manager is able to transfer in a single third-party
copy command.

7.8.17.8.4 Copy manager ROD token device type features descriptor

The copy manager ROD device type specific features descriptor (see table 651) provides support information
for ROD tokens associated with copy manager only devices (e.g., devices for which the device server
associated with the copy manager reports a peripheral device type of 03h (i.e., processor) as described in
5.16.2).

Table 651 — Copy manager ROD device type specific features descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 DESCRIPTOR FORMAT (000b) PERIPHERAL DEVICE TYPE (03h)
1 Reserved
2 (MSB)
DESCRIPTOR LENGTH (002Ch)
3 (LSB)
4
•• • Reserved
7
8 (MSB)
•• • MAXIMUM BYTES IN PROCESSOR ROD
15 (LSB)
16 (MSB)
•• • OPTIMAL BYTES IN PROCESSOR ROD TRANSFER
23 (LSB)

24
•• • Reserved
47

The DESCRIPTOR FORMAT field indicates the format of the descriptor and shall be set as shown in table 651 for
the copy manager ROD device type specific features descriptor.

The PERIPHERAL DEVICE TYPE field indicates the device type associated with the descriptor and shall be set as
shown in table 651 for the copy manager ROD device type specific features descriptor.

The DESCRIPTOR LENGTH field indicates the number of bytes that follow in the descriptor and shall be set as
shown in table 651 for the copy manager ROD device type specific features descriptor.

The MAXIMUM BYTES IN PROCESSOR ROD field indicates the largest number of bytes the copy manager supports
in an internal ROD or ROD token for a copy manager only device. If a third-party copy command (see 5.16.3)
attempts to populate an internal ROD or ROD token with more than the indicated number of bytes, then the
copy manager shall terminate the copy operation (see 5.16.4.3) with CHECK CONDITION status, with the
sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER
LIST. If the MAXIMUM BYTES IN PROCESSOR ROD field is set to zero, then the copy manager does not report a
largest number of bytes the copy manager supports in an internal ROD or ROD token for a copy manager only
device.

Working Draft SCSI Primary Commands - 4 (SPC-4) 799

T10/BSR INCITS 513 Revision 37 17 May 2014

The OPTIMAL BYTES IN PROCESSOR ROD TRANSFER field indicates the optimal number of bytes the copy
manager is able to transfer in a single third-party copy command (see 5.16.3) or EXTENDED COPY segment
descriptor (see 6.4.6). Processing delays with adverse effects may be incurred if a third-party copy command
attempts to transfer more bytes than indicated by the OPTIMAL BYTES IN PROCESSOR ROD TRANSFER field to or
from a copy manager only device. If the OPTIMAL BYTES IN PROCESSOR ROD TRANSFER field is set to zero, then
the copy manager does not report the optimal number of bytes the copy manager is able to transfer in a single
third-party copy command for a copy manager only device. If the OPTIMAL BYTES IN PROCESSOR ROD TRANSFER
field is set to FFFF FFFF FFFF FFFFh, then there is no limit on the optimal number of bytes the copy
manager is able to transfer in a single third-party copy command.

7.8.17.9 Supported ROD Types third-party copy descriptor

The Supported ROD Types third-party copy descriptor (see table 652) indicates which ROD types (see
5.16.6.2) the copy manager supports and the processing characteristics supported for those types.

Table 652 — Supported ROD Types third-party copy descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
THIRD-PARTY COPY DESCRIPTOR TYPE (0108h)
1 (LSB)
2 (MSB)
THIRD-PARTY COPY DESCRIPTOR LENGTH (n-3)
3 (LSB)
4
Reserved
5
6 (MSB)
ROD TYPE DESCRIPTORS LENGTH (m-7)
7 (LSB)
ROD type descriptors
8
•• • ROD type descriptor (see table 653) [first]

•
••

•• • ROD type descriptor (see table 653) [last]

m
m+1
•• • DESCRIPTOR PAD (if any)
n

The THIRD-PARTY COPY DESCRIPTOR TYPE field is described in 7.8.17.3 and shall be set as shown in table 652
for the Supported ROD Token and ROD Types third-party copy descriptor.

The THIRD-PARTY COPY DESCRIPTOR LENGTH field is described in 7.8.17.2.

The ROD TYPE DESCRIPTORS LENGTH field indicates the length, in bytes, of the ROD type descriptors.

800 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Each ROD type descriptor (see table 653) indicates what support the copy manager provides for a specific
ROD type (see 5.16.6.2).

The ROD type descriptors shall appear in ascending numerical order based on the contents of the ROD TYPE
field (see table 653).

The DESCRIPTOR PAD field shall contain zero to three bytes set to zero such that the total length of the
Supported ROD Types third-party copy descriptor is a multiple of four.

The copy manager’s support for a ROD type (see 5.16.6.2) and the ROD token, if any, associated with that
ROD type is indicated by the ROD type descriptor (see table 653).

Table 653 — ROD type descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
•• • ROD TYPE
3 (LSB)
4 ECPY_INT Reserved TOKEN_IN TOKEN_OUT

5 Reserved
6
PREFERENCE INDICATOR
7
8
•• • Reserved
63

The ROD TYPE field indicates the ROD type (see table 111 in 5.16.6.2) for which this ROD type descriptor
indicates copy manager support.

The copy manager shall support a ROD TYPE field set to zero in a ROD CSCD descriptor (see 6.4.5.9), shall
include a ROD type descriptor with the ROD TYPE field set to zero in the Supported ROD Types third-party copy
descriptor (see 7.8.17.9), and shall include CSCD descriptor ID F800h in the Supported CSCD Descriptor IDs
third-party copy descriptor (see 7.8.17.7), if:

a) the ROD CSCD descriptor is supported; and

b) any ROD type descriptor contains:
A) a non-zero value in the ROD TYPE field; and
B) the TOKEN_IN bit set to one.

An ECPY_INT bit set to one indicates that the copy manager supports use of the ROD type indicated by the ROD
TYPE field for internal RODs in the EXTENDED COPY command (see 5.16.7). An ECPY_INT bit set to zero
indicates that the copy manager does not support use of the ROD type indicated by the ROD TYPE field for
internal RODs in the EXTENDED COPY command.

A TOKEN_IN bit set to one indicates that the copy manager supports the receipt of ROD tokens (see 5.16.6)
that have the ROD type indicated by the ROD TYPE field by one or more commands that the copy manager
processes. A TOKEN_IN bit set to zero indicates that the copy manager does not support the receipt of ROD
tokens that have the ROD type indicated by the ROD TYPE field.

Working Draft SCSI Primary Commands - 4 (SPC-4) 801

T10/BSR INCITS 513 Revision 37 17 May 2014

A TOKEN_OUT bit set to one indicates that the copy manager supports the generation and returning of ROD
tokens (see 5.16.6) that have the ROD type indicated by the ROD TYPE field by one or more commands that
the copy manager processes. A TOKEN_OUT bit set to zero indicates that the copy manager does not support
the generation and returning of ROD tokens that have the ROD type indicated by the ROD TYPE field.

If the ROD TYPE field is set to FFFF 0001h (i.e., if the ROD type is the one used by the block device zero ROD
token (see SBC-3)), then the TOKEN_OUT bit shall be set to zero (i.e., the return of block device zero ROD
tokens is prohibited).

The PREFERENCE INDICATOR field indicates the degree of preference the copy manager provides for the
services (e.g., number of RODs supported as active at the one time, number of ROD tokens supported as
active at the one time, maximum ROD lifetimes supported, performance associated with any aspect of ROD
processing) that are associated with the ROD type indicated by the ROD TYPE field. Except for zero, values in
the PREFERENCE INDICATOR field provide this indication as follows:

a) larger values indicate a higher degree of preference for the ROD related services; and
b) smaller value indicate a lower degree of preference for the same ROD related services.

A PREFERENCE INDICATOR field set to zero indicates that:

a) no ROD preference information is provided, if all PREFERENCE INDICATOR fields in all ROD type
descriptors are set to zero; or
b) no valid comparison is possible between the preference for the ROD type indicated by the ROD TYPE
field and other ROD types supported by the copy manager, if at least one PREFERENCE INDICATOR field
is not set to zero in another ROD type descriptor.

The sum of the values in all PREFERENCE INDICATOR fields in all ROD type descriptors shall be equal to either
zero or FFFFh.

EXAMPLE – An instance where some PREFERENCE INDICATOR field values are zero and other are non-zero concerns the
block device zero ROD token (see SBC-3). Suppose several copy on reference ROD types are supported in addition to
the block device zero ROD token. Each supported ROD type has a ROD type descriptor, including the ROD type used by
the block device zero ROD token. Further suppose that support for the block device zero ROD token requires so few
resources that its preference is infinite for all practical purposes. Setting the PREFERENCE INDICATOR field values to zero in
the ROD type descriptor for the block device zero ROD token allows the copy manager to better reflect the preferences
among the various copy on reference ROD types.

802 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.8.17.10 General Copy Operations third-party copy descriptor

The General Copy Operations third-party copy descriptor (see table 656) indicates the limits that the copy
manager places on processing of copy operations (see 5.16.4.3).

Table 654 — General Copy Operations third-party copy descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
THIRD-PARTY COPY DESCRIPTOR TYPE (8001h)
1 (LSB)
2 (MSB)
THIRD-PARTY COPY DESCRIPTOR LENGTH (0020h)
3 (LSB)
4 (MSB)
•• • TOTAL CONCURRENT COPIES
7 (LSB)
8 (MSB)
•• • MAXIMUM IDENTIFIED CONCURRENT COPIES
11 (LSB)
12 (MSB)
MAXIMUM SEGMENT LENGTH
15 (LSB)
16 DATA SEGMENT GRANULARITY (log 2)
17 INLINE DATA GRANULARITY (log 2)
18
•• • Reserved
35

The THIRD-PARTY COPY DESCRIPTOR TYPE field is described in 7.8.17.3 and shall be set as shown in table 654
for the General Copy Operations third-party copy descriptor.

The THIRD-PARTY COPY DESCRIPTOR LENGTH field is described in 7.8.17.2 and shall be set as shown in table
654 for the General Copy Operations third-party copy descriptor.

The TOTAL CONCURRENT COPIES field indicates the maximum number of third-party copy commands (see
5.16.3) that are supported for concurrent processing by the copy manager.

The MAXIMUM IDENTIFIED CONCURRENT COPIES field indicates the maximum number of third-party copy
commands (see 5.16.3) that are not an EXTENDED COPY command with the LIST ID USAGE field (see 6.4.3.2)
set to 11b that are supported for concurrent processing by the copy manager.

The contents of the TOTAL CONCURRENT COPIES field shall be greater than or equal to the contents of the
MAXIMUM IDENTIFIED CONCURRENT COPIES field.

The MAXIMUM SEGMENT LENGTH field indicates the length, in bytes, of the largest amount of data that the copy
manager supports writing via a single segment. Bytes introduced as a result of the PAD bit being set to one
(see 5.16.7.2) are not counted towards this limit. A value of zero indicates that the copy manager places no
limits on the amount of data written by a single segment.

Working Draft SCSI Primary Commands - 4 (SPC-4) 803

T10/BSR INCITS 513 Revision 37 17 May 2014

The DATA SEGMENT GRANULARITY field indicates the length of the smallest data block that the copy manager
permits in a non-inline segment descriptor (i.e., segment descriptors with type codes other than 04h). The
amount of data transferred by a single segment descriptor shall be a multiple of the granularity. The DATA
SEGMENT GRANULARITY value is expressed as a power of two. Bytes introduced as a result of the PAD bit being
set to one (see 5.16.7.2) are not counted towards the data length granularity.

The INLINE DATA GRANULARITY field indicates the length of the smallest block of inline data that the copy
manager permits being written by a segment descriptor containing the 04h descriptor type code (see 6.4.6.6).
The amount of inline data written by a single segment descriptor shall be a multiple of the granularity. The
INLINE DATA GRANULARITY value is expressed as a power of two. Bytes introduced as a result of the PAD bit
being set to one (see 5.16.7.2) are not counted towards the length granularity.

If the copy manager encounters a data or inline segment descriptor that violates either the data segment
granularity or the inline data granularity, then the copy manager shall terminate the copy operation (see
5.16.4.3) with CHECK CONDITION status, with the sense key set to COPY ABORTED, and the additional
sense code set to COPY SEGMENT GRANULARITY VIOLATION.

7.8.17.11 Stream Copy Operations third-party copy descriptor

The Stream Copy Operations third-party copy descriptor (see table 656) indicates the limits that the copy
manager places on processing of copy operations (see 5.16.4.3) that affect stream devices.

Table 655 — Stream Copy Operations third-party copy descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
THIRD-PARTY COPY DESCRIPTOR TYPE (9101h)
1 (LSB)
2 (MSB)
THIRD-PARTY COPY DESCRIPTOR LENGTH (000Ch)
3 (LSB)
4 (MSB)
•• • MAXIMUM STREAM DEVICE TRANSFER SIZE
7 (LSB)
8
•• • Reserved
15

The THIRD-PARTY COPY DESCRIPTOR TYPE field is described in 7.8.17.3 and shall be set as shown in table 655
for the Stream Copy Operations third-party copy descriptor.

The THIRD-PARTY COPY DESCRIPTOR LENGTH field is described in 7.8.17.2 and shall be set as shown in table
655 for the Stream Copy Operations third-party copy descriptor.

The MAXIMUM STREAM DEVICE TRANSFER SIZE field indicates the maximum transfer size, in bytes, supported for
stream devices.

804 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

7.8.17.12 Held Data third-party copy descriptor

The Held Data third-party copy descriptor (see table 656) indicates the limits that the copy manager places on
held data (see 5.16.4.5).

Table 656 — Held Data third-party copy descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
THIRD-PARTY COPY DESCRIPTOR TYPE (C001h)
1 (LSB)
2 (MSB)
THIRD-PARTY COPY DESCRIPTOR LENGTH (001Ch)
3 (LSB)
4 (MSB)
•• • HELD DATA LIMIT
7 (LSB)
8 HELD DATA GRANULARITY (log 2)
9
•• • Reserved
31

The THIRD-PARTY COPY DESCRIPTOR TYPE field is described in 7.8.17.3 and shall be set as shown in table 656
for the Held Data third-party copy descriptor.

The THIRD-PARTY COPY DESCRIPTOR LENGTH field is described in 7.8.17.2 and shall be set as shown in table
656 for the Held Data third-party copy descriptor.

The HELD DATA LIMIT field indicates the length, in bytes, of the minimum amount of data the copy manager
shall hold for return to the application client as described in 5.16.4.5.

The HELD DATA GRANULARITY field indicates the length of the smallest block of held data (see 5.16.4.5) that the
copy manager shall transfer to the application client in response to a RECEIVE COPY DATA(LID4) command
(see 6.20) or a RECEIVE COPY DATA(LID1) command (see 6.21). The amount of data held by the copy
manager in response to any one function (e.g., one segment descriptor (see 6.4.6)) in a copy operation (see
5.16.4.3) shall be a multiple of this granularity. The HELD DATA GRANULARITY value is expressed as a power of
two.

Working Draft SCSI Primary Commands - 4 (SPC-4) 805

T10/BSR INCITS 513 Revision 37 17 May 2014

7.8.18 Unit Serial Number VPD page

The Unit Serial Number VPD page (see table 657) provides a product serial number for the SCSI target device
or logical unit.

Table 657 — Unit Serial Number VPD page

Bit
7 6 5 4 3 2 1 0
Byte
0 PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE

1 PAGE CODE (80h)

2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4 (MSB)
•• • PRODUCT SERIAL NUMBER
n (LSB)

The PERIPHERAL QUALIFIER field, PERIPHERAL DEVICE TYPE field, and PAGE LENGTH field are defined in 7.8.2.

The PAGE CODE field is defined in 7.8.2 and shall be set as shown in table 657 for the Unit Serial Number VPD
page.

The PRODUCT SERIAL NUMBER field contains right-aligned ASCII data (see 4.3.1) that is a vendor specific serial
number. If the product serial number is not available, the device server shall return ASCII spaces (20h) in this
field.

806 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

8 Well known logical units

8.1 Model for well known logical units

Well known logical units are addressed using the well known logical unit addressing method of extended
logical unit addressing (see SAM-5). Each well known logical unit has a well known logical unit number as
shown in table 658.

Table 658 — Well known logical unit numbers

W-LUN a Description Reference

00h Reserved
01h REPORT LUNS well known logical unit 8.2
02h ACCESS CONTROLS well known logical unit 8.3
03h TARGET LOG PAGES well known logical unit 8.4
04h SECURITY PROTOCOL well known logical unit 8.5
05h MANAGEMENT PROTOCOL well known logical unit 8.6
06h to FFh Reserved
a
well known logical unit number

If a well known logical unit is supported within a SCSI target device, then that logical unit shall support all the
commands defined for it.

Access to well known logical units shall not be affected by access controls.

The SCSI device name of the SCSI target device that contains a well known logical unit may be determined by
issuing an INQUIRY command (see 6.6) requesting the Device Identification VPD page (see 7.8.6).

All well known logical units shall support the INQUIRY command’s Device Identification VPD page as defined
in 7.8.6.2.2.

8.2 REPORT LUNS well known logical unit

The REPORT LUNS well known logical unit shall only process the commands listed in table 659. If a
command is received by the REPORT LUNS well known logical unit that is not listed in table 659, then the
device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID COMMAND OPERATION CODE.

Table 659 — Commands for the REPORT LUNS well known logical unit

Operation
Command code Support Reference
INQUIRY 12h M 6.6
REPORT LUNS A0h M 6.33
REQUEST SENSE 03h M 6.39
TEST UNIT READY 00h M 6.47
Key:
M = Command implementation is mandatory.

Working Draft SCSI Primary Commands - 4 (SPC-4) 807

T10/BSR INCITS 513 Revision 37 17 May 2014

8.3 ACCESS CONTROLS well known logical unit

8.3.1 Access controls model

8.3.1.1 Access controls commands

The ACCESS CONTROLS well known logical unit shall only process the commands listed in table 660. If a
command is received by the ACCESS CONTROLS well know logical unit that is not listed in table 660, then
the device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID COMMAND OPERATION CODE.

Table 660 — Commands for the ACCESS CONTROLS well known logical unit

Operation
Command code Support Reference
ACCESS CONTROL IN 86h M 8.3.2
ACCESS CONTROL OUT 87h M 8.3.3
INQUIRY 12h M 6.6
REQUEST SENSE 03h M 6.39
TEST UNIT READY 00h M 6.47
Key:
M = Command implementation is mandatory.

8.3.1.2 Access controls overview

Access controls are a SCSI target device feature that application clients may use to restrict logical unit access
to specified initiator ports or groups of initiator ports.

Access controls shall not allow restrictions to be placed on access to well known logical units. Access controls
shall not cause new well known logical units to be defined.

Access controls are handled in the SCSI target device by an access controls coordinator contained in the
ACCESS CONTROLS well known logical unit. The access controls coordinator also may be accessible via
LUN 0. The access controls coordinator associates a specific LUN to a specific logical unit depending on
which initiator port accesses the SCSI target device and whether the initiator port has access rights to the
logical unit.

Access rights to a logical unit affects whether the LUN appears in the parameter data returned by a REPORT
LUNS command and how the logical unit responds to INQUIRY commands.

The access controls coordinator maintains the ACL as described in 8.3.1.3 to supply information about:

a) which initiator ports are allowed access to which logical units; and
b) which LUN value is used by a specific initiator port when accessing a specific logical unit.

The format of the ACL is vendor specific.

To support third party commands (e.g., EXTENDED COPY), the access controls coordinator may provide
proxy tokens (see 8.3.1.6.2) to allow an application client to pass its access capabilities to the application
client for another initiator port.

808 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

An application client manages the access controls state of the SCSI target device using the ACCESS
CONTROL IN command (see 8.3.2) and the ACCESS CONTROL OUT command (see 8.3.3).

A SCSI target device has access controls disabled when it is manufactured and after successful completion of
the ACCESS CONTROL OUT command with DISABLE ACCESS CONTROLS service action (see 8.3.3.3). If
access controls are disabled, then:

a) the ACL contains no entries;

b) the management identifier key (see 8.3.1.8) is set to zero; and
c) access to logical units is not affected by the access controls model.

The first successful ACCESS CONTROL OUT command with MANAGE ACL service action (see 8.3.3.2)
shall enable access controls. If access controls are enabled, all logical units, except LUN 0 and all well known
logical units, shall be inaccessible to all initiator ports unless the ACL (see 8.3.1.3) allows access.

The access controls coordinator allows an initiator port access to a logical unit if the ACL contains an ACE
(see 8.3.1.3) with an access identifier (see 8.3.1.3.2) associated with the initiator port and that ACE contains a
LUACD (see 8.3.1.3.3) that references the logical unit.

If the access controls coordinator allows access to a logical unit, the REPORT LUNS command parameter
data bytes representing that logical unit shall contain the LUN value found in the LUACD that references that
logical unit and the application client for the initiator port shall use the same LUN value when sending
commands to the logical unit.

An initiator port also may be allowed access to a logical unit through the use of a proxy token (see 8.3.1.6.2).

Once access controls are enabled, they shall remain enabled until:

a) successful completion of an ACCESS CONTROL OUT command with DISABLE ACCESS

CONTROLS service action; or
b) vendor specific physical intervention.

Successful downloading of microcode (see 6.49) may result in access controls being disabled.

Once access controls are enabled, power cycles, hard resets, logical unit resets, and I_T nexus losses shall
not disable them.

8.3.1.3 Access Control List

8.3.1.3.1 ACL overview

The specific access controls for a SCSI target device are instantiated by the access controls coordinator using
data in an ACL. The ACL contains zero or more ACEs and zero or more proxy tokens (see 8.3.1.6.2.1).

Each ACE contains the following:

a) one access identifier (see 8.3.1.3.2) that identifies the initiator port(s) to which the ACE applies; and
b) a list of LUACDs (see 8.3.1.3.3) that identify the logical units to which the identified initiator port(s)
have access rights and the LUNs used to access those logical units via those initiator port(s). Each
LUACD contains the following:
A) a vendor specific logical unit reference; and
B) a LUN value.

Working Draft SCSI Primary Commands - 4 (SPC-4) 809

T10/BSR INCITS 513 Revision 37 17 May 2014

Figure 19 shows the logical structure of an ACL.

ACL ACE LUACD

ACE
Access
ACE Identifier
ACE Logical Unit
LUACD
ACE Reference
LUACD
LUN
LUACD
Proxy LUACD
Token LUACD
Proxy
Token
Proxy
Token

Figure 19 — ACL Structure

8.3.1.3.2 Access identifiers

Initiator ports are identified in an ACE using one of the following types of access identifiers:

a) AccessID: based on initiator port enrollment;

b) TransportID: based on protocol specific identification of initiator ports; or
c) vendor specific access identifiers.

An initiator port is allowed access to the logical units in an ACE containing an AccessID type access identifier
if that initiator port is enrolled as described in 8.3.1.5. An initiator port that has not previously enrolled uses the
ACCESS CONTROL OUT command with ACCESS ID ENROLL service action to enroll including the
AccessID in parameter data as defined in 8.3.3.4.

An initiator port is associated with an AccessID type access identifier if that initiator port is in the enrolled state
or pending-enrolled state with respect to that AccessID (see 8.3.1.5). At any instant in time, an initiator port is
allowed to be associated with at most one AccessID. All initiator ports enrolled using a specific AccessID
share the same ACE and access to all the logical units described by the LUACDs contained in that ACE.

TransportID access identifiers are SCSI transport protocol specific as described in 7.6.4.

An initiator port is allowed access to the logical units in an ACE containing a TransportID type access identifier
if the identification for the initiator port matches that found in the TransportID in a way that is consistent with
the TransportID definition (see 7.6.4). The information required to obtain logical unit access based on a
Transport ID is provided by the SCSI transport protocol layer.

The formats of access identifiers are defined in 8.3.1.13.

810 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

8.3.1.3.3 Logical Unit Access Control Descriptor

Each LUACD in an ACE identifies one logical unit to which the initiator ports associated with the access
identifier are allowed access and specifies the LUN value used when accessing the logical unit via those
initiator ports. The format of a LUACD is vendor specific.

The identification of a logical unit in a LUACD is vendor specific. The logical unit identified by a LUACD shall
not be a well known logical unit. A logical unit shall be referenced in no more than one LUACD per ACE.

The LUN value shall conform to the requirements defined in SAM-5. A specific LUN value shall appear in no
more than one LUACD per ACE.

8.3.1.4 Managing the ACL

8.3.1.4.1 ACL management overview

The contents of the ACL are managed by an application client using the ACCESS CONTROL OUT command
with MANAGE ACL service action and ACCESS CONTROL OUT command with DISABLE ACCESS
CONTROLS service action. The ACCESS CONTROL OUT command with MANAGE ACL service action (see
8.3.3.2) is used to add, remove, or modify ACEs thus adding, revoking, or changing the allowed access of
initiator ports to logical units. The ACCESS CONTROL OUT command with DISABLE ACCESS CONTROLS
service action (see 8.3.3.3) disables access controls and discards the ACL.

8.3.1.4.2 Authorizing ACL management

Successful completion of specific access controls service actions (e.g., ACCESS CONTROL OUT command
with MANAGE ACL service action and ACCESS CONTROL OUT command with DISABLE ACCESS
CONTROLS service action) requires delivery of the correct management identifier key value (see 8.3.1.8) in
the ACCESS CONTROL OUT parameter data. The service actions that require the correct management
identifier key are shown in table 661 and table 662.

Table 661 — ACCESS CONTROL OUT management identifier key requirements

ACCESS CONTROL OUT command Management Identifier

service action Key Required Reference
ACCESS ID ENROLL No 8.3.3.4
ASSIGN PROXY LUN No 8.3.3.11
CANCEL ENROLLMENT No 8.3.3.5
CLEAR ACCESS CONTROLS LOG Yes 8.3.3.6
DISABLE ACCESS CONTROLS Yes 8.3.3.3
MANAGE ACL Yes 8.3.3.2
MANAGE OVERRIDE LOCKOUT TIMER Yes/No 8.3.3.7
OVERRIDE MGMT ID KEY No 8.3.3.8
RELEASE PROXY LUN No 8.3.3.12
REVOKE ALL PROXY TOKENS No 8.3.3.10
REVOKE PROXY TOKEN No 8.3.3.9

Working Draft SCSI Primary Commands - 4 (SPC-4) 811

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 662 — ACCESS CONTROL IN management identifier key requirements

ACCESS CONTROL IN command Management Identifier

service action Key Required Reference
REPORT ACCESS CONTROLS LOG Yes 8.3.2.4
REPORT ACL Yes 8.3.2.2
REPORT LU DESCRIPTORS Yes 8.3.2.3
REPORT OVERRIDE LOCKOUT TIMER Yes 8.3.2.5
REQUEST PROXY TOKEN No 8.3.2.6

8.3.1.4.3 Identifying logical units during ACL management

The access controls coordinator shall identify each logical unit of a SCSI target device with a unique default
LUN value. The default LUN values used by the access controls coordinator shall be the same LUN values
returned by the REPORTS LUNS command if access controls are disabled.

An application client discovers the default LUN values using the ACCESS CONTROL IN command with
REPORT LU DESCRIPTORS service action (see 8.3.2.3) or ACCESS CONTROL IN command with REPORT
ACL service action (see 8.3.2.2) and then supplies those default LUN values to the access controls
coordinator using the ACCESS CONTROL OUT command with MANAGE ACL service action.

The association between default LUN values and logical units is managed by the access controls coordinator
and may change for vendor specific reasons. To track such changes, the access controls coordinator
maintains the default LUNs generation (DLgeneration) counter as described in 8.3.1.4.4.

8.3.1.4.4 Tracking changes in logical unit identification

The access controls coordinator shall implement a DLgeneration counter to track changes in the association
between default LUN values and logical units. The DLgeneration counter is a wrapping counter.

When access controls are disabled the DLgeneration counter shall be set to zero. When access controls are
first enabled (see 8.3.1.2) the DLgeneration counter shall be set to one. While access controls are enabled,
the access controls coordinator shall increment the DLgeneration counter by one every time the association
between default LUN values and logical units changes (e.g., following the creation of a new logical unit,
deletion of an existing logical unit, or removal and recreation of an existing logical unit). If the incremented the
DLgeneration counter is greater than FFFFh, the DLgeneration counter shall be set to 0001h.

The access controls coordinator shall include the current DLgeneration value in the parameter data returned
by an ACCESS CONTROL IN command with REPORT LU DESCRIPTORS service action (see 8.3.2.3) or
ACCESS CONTROL IN command with REPORT ACL service action (see 8.3.2.2). The application client shall
supply the DLgeneration value for the default LUN values it is using in the parameter data for an ACCESS
CONTROL OUT command with MANAGE ACL service action (see 8.3.3.2).

Before processing the ACL change information in the parameter list provided by an ACCESS CONTROL OUT
command with MANAGE ACL service action, the access controls coordinator shall verify that the
DLgeneration value in the parameter data matches the current value of the DLgeneration counter. If the
DLgeneration value verification finds a mismatch, the command shall be terminated with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN
PARAMETER LIST.

812 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

8.3.1.5 Enrolling AccessIDs

8.3.1.5.1 Enrollment states

8.3.1.5.1.1 Summary of enrollment states

Application clients enroll an initiator port AccessID with the access controls coordinator to be allowed to
access logical units listed in the ACE having the same AccessID type access identifier. The ACCESS
CONTROL OUT command with ACCESS ID ENROLL service action (see 8.3.3.4) is used to enroll an
AccessID. An initiator port shall be in one of three states with respect to such an enrollment:

a) Not-enrolled: the state for an initiator port before the first ACCESS CONTROL OUT command with
ACCESS ID ENROLL service action is sent to the access controls coordinator or the state for an
initiator port following successful completion of an ACCESS CONTROL OUT command with CANCEL
ENROLLMENT service action (see 8.3.3.5);
b) Enrolled: the state for an initiator port following successful completion of an ACCESS CONTROL
OUT command with ACCESS ID ENROLL service action; or
c) Pending-enrolled: the state for an enrolled initiator port following:
A) events described in 8.3.1.12; or
B) successful completion of an ACCESS CONTROL OUT command with MANAGE ACL service
action from any initiator port with the FLUSH bit set to one (see 8.3.3.2).

8.3.1.5.1.2 Not-enrolled state

The access controls coordinator shall place an initiator port in the not-enrolled state when it first detects the
receipt of a SCSI command or task management function from that initiator port. The initiator port shall remain
in the not-enrolled state until successful completion of an ACCESS CONTROL OUT command with ACCESS
ID ENROLL service action (see 8.3.3.5).

While in the not-enrolled state, an initiator port shall only have access to logical units on the basis of a
TransportID (see 8.3.1.3.2) or on the basis of proxy tokens (see 8.3.1.6.2.1).

The access controls coordinator changes an initiator port from the enrolled state or pending-enrolled state to
the not-enrolled state in response to the following events:

a) successful completion of the ACCESS CONTROL OUT command with CANCEL ENROLLMENT
service action (see 8.3.3.5) shall change the state to not-enrolled; or
b) successful completion of an ACCESS CONTROL OUT command with MANAGE ACL service action
(see 8.3.3.2) that replaces the ACL entry for the enrolled AccessID as follows:
A) if the NOCNCL bit (see 8.3.3.2.2) is set to zero in the ACCESS CONTROL OUT command with
MANAGE ACL service action parameter data, then the state shall change to not-enrolled; or
B) if the NOCNCL bit is set to one, then the state may change to not-enrolled based on vendor specific
considerations.

An application client for an enrolled initiator port may discover that the initiator port has transitioned to the
not-enrolled state as a result of actions taken by a third party (e.g., an ACCESS CONTROL OUT command
with MANAGE ACL service action performed by another initiator port or a logical unit reset).

Placing an enrolled initiator in the not-enrolled state indicates that the ACE defining that initiator port’s logical
unit access has changed (e.g., previous relationships between logical units and LUN values may no longer
apply).

If an application client detects the loss of enrollment for an initiator port as described in this subclause (e.g.,
based on vendor specific considerations if the NOCNCL bit (see 8.3.3.2.2) is set to one in an ACCESS

Working Draft SCSI Primary Commands - 4 (SPC-4) 813

T10/BSR INCITS 513 Revision 37 17 May 2014

CONTROL OUT command with MANAGE ACL service action), then the application client should proceed with
caution to avoid creating a disagreement between the device server and the application client regarding the
contents of the ACL.

If the NOCNCL bit set to one, the access controls coordinator:

a) honors the recommendation, causing the minimum effects on SCSI initiator devices and requiring no
extra actions on the part of the access controls coordinator;
b) ignores the recommendation and always place initiator ports in the non-enrolled state, causing the
maximum disruption for SCSI initiator devices, but requiring no extra resources on the part of the
access controls coordinator; or
c) ignores the recommendation and examine the current and new ACEs to determine if an initiator port
should be placed in the non-enrolled state.

If the application client that sends the ACCESS CONTROL OUT command with MANAGE ACL service action
is unable to determine whether the ACE logical unit relationships are altered as a result of processing the
command, then the application client should set the NOCNCL bit to zero and should coordinate the ACL change
with the application clients for affected initiator ports to ensure proper data integrity.

8.3.1.5.1.3 Enrolled state

The access controls coordinator shall place an initiator port in the enrolled state (i.e., enroll the initiator port)
following successful completion of the ACCESS CONTROL OUT command with ACCESS ID ENROLL
service action (see 8.3.3.4). The ACCESS CONTROL OUT command with ACCESS ID ENROLL service
action is successful only if:

a) the initiator port was in the not-enrolled state and the AccessID in the ACCESS CONTROL OUT
command with ACCESS ID ENROLL service action parameter data matches the access identifier in
an ACE. This results in the initiator port being enrolled and allowed access to the logical units
specified in the LUACDs in the ACE (see 8.3.1.3); or
b) the initiator port was in the enrolled state or pending-enrolled state and the AccessID in the ACCESS
CONTROL OUT command with ACCESS ID ENROLL service action parameter data matches the
current enrolled AccessID for the initiator port.

If the initiator port was in the enrolled state or pending-enrolled state and the AccessID in the ACCESS
CONTROL OUT command with ACCESS ID ENROLL service action parameter data does not match the
current enrolled AccessID for the initiator port, then the command shall be terminated with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
ACCESS DENIED - ENROLLMENT CONFLICT. If the initiator port was in the enrolled state, the initiator port
shall be transitioned to the pending-enrolled state.

Transitions from the enrolled state to the not-enrolled state are described in 8.3.1.5.1.2. Transitions from the
enrolled state to the pending-enrolled state are described in 8.3.1.5.1.4.

NOTE 65 - This standard does not preclude implicit enrollments through mechanisms in a service delivery
subsystem. Such mechanisms should perform implicit enrollments after identification by TransportID and
should fail in the case where there are ACL conflicts as described in 8.3.1.5.2.

8.3.1.5.1.4 Pending-enrolled state

The access controls coordinator shall place an initiator port in the pending-enrolled state if that initiator port
currently is in the enrolled state, and in response to the following:

a) a logical unit reset;

814 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

b) an I_T nexus loss associated with that initiator port; or

c) successful completion of an ACCESS CONTROL OUT command with MANAGE ACL service action
where the FLUSH bit is set to one (see 8.3.3.2).

While in the pending-enrolled state, the initiator port’s access to logical units is limited as described in 8.3.1.7.

8.3.1.5.2 ACL LUN conflict resolution

ACL LUN conflicts may occur if:

a) an application client for an initiator port in the not-enrolled state attempts to enroll an AccessID using
the ACCESS CONTROL OUT command with ACCESS ID ENROLL service action (see 8.3.3.4); or
b) an ACCESS CONTROL OUT command with MANAGE ACL service action (see 8.3.3.2) attempts to
change the ACL with the result that it conflicts with existing enrollments (see 8.3.1.5) or proxy LUN
assignments (see 8.3.1.6.2.2).

The following types of ACL LUN conflicts may occur:

a) the TransportID ACE (see 8.3.1.3) and the AccessID ACE for the initiator port each contain a LUACD
with the same LUN value but with different logical unit references;
b) the TransportID ACE and the AccessID ACE for the initiator port each contain a LUACD with the
different LUN values but with the same logical unit references; or
c) the enrolling initiator port has proxy access rights to a logical unit addressed with a LUN value that
equals a LUN value in a LUACD in the AccessID ACE for the initiator port.

If an ACL LUN conflict occurs during the processing of an ACCESS CONTROL OUT command with MANAGE
ACL service action, then the command shall be terminated with CHECK CONDITION status (see 8.3.3.2.2).

If an ACL LUN conflict occurs during the processing of an ACCESS CONTROL OUT command with ACCESS
ID ENROLL service action, then the following shall occur:

a) the ACCESS CONTROL OUT command with ACCESS ID ENROLL service action shall be
terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the
additional sense code set to ACCESS DENIED - ACL LUN CONFLICT;
b) the initiator port shall remain in the not-enrolled state; and
c) if the ACL LUN conflict is not the result of proxy access rights, the access controls coordinator shall
record the event in the access controls log as described in 8.3.1.10.

8.3.1.6 Granting and revoking access rights

8.3.1.6.1 Non-proxy access rights

The ACCESS CONTROL OUT command with MANAGE ACL service action (see 8.3.3.2) adds or replaces
ACEs in the ACL (see 8.3.1.3). One ACE describes the logical unit access allowed by one access identifier
(see 8.3.1.3.2) and the LUN values to be used in addressing the accessible logical units. The access identifier
specifies the initiator port(s) permitted access to the logical units described by the ACE.

With the exception of proxy access rights (see 8.3.1.6.2), access rights are granted by:

a) adding a new ACE to the ACL; or

b) replacing an existing ACE with an ACE that includes additional LUACDs.

Working Draft SCSI Primary Commands - 4 (SPC-4) 815

T10/BSR INCITS 513 Revision 37 17 May 2014

With the exception of proxy access rights, access rights are revoked by:

a) removing an ACE from the ACL; or

b) replacing an existing ACE with an ACE that removes one or more LUACDs.

If an ACE is added or replaced, the requirements stated in 8.3.1.5.1.2 and 8.3.1.11 shall apply.

8.3.1.6.2 Proxy access

8.3.1.6.2.1 Proxy tokens

An application client with access rights to a logical unit via an initiator port on the basis of an ACE in the ACL
(see 8.3.1.6.1) may temporarily share that access with third parties using proxy access. The application client
uses the ACCESS CONTROL IN command with REQUEST PROXY TOKEN service action (see 8.3.2.6) to
request that the access control coordinator generate a proxy token for the logical unit specified by the LUN
value in the CDB.

The access controls coordinator generates the proxy token in a vendor specific manner. For a specific SCSI
target device, all active proxy token values should be unique. Proxy token values should be reused as
infrequently as possible to prevent proxy tokens that have been used and released from being given
unintended meaning.

Power cycles, hard resets, logical unit resets, and I_T nexus losses shall not affect the validity and proxy
access rights of proxy tokens (see 8.3.1.12). A proxy token shall remain valid and retain the same proxy
access rights until one of the following occurs:

a) an application client with access rights to a logical unit via an initiator port based on an ACE in the
ACL revokes the proxy token using:
A) the ACCESS CONTROL OUT command with REVOKE PROXY TOKEN service action (see
8.3.3.9); or
B) the ACCESS CONTROL OUT command with REVOKE ALL PROXY TOKENS service action
(see 8.3.3.10);
or
b) an application client issues the ACCESS CONTROL OUT command with MANAGE ACL service
action (see 8.3.3.2) with parameter data containing the Revoke Proxy Token ACE page (see
8.3.3.2.4) or Revoke All Proxy Tokens ACE page (see 8.3.3.2.5).

8.3.1.6.2.2 Proxy LUNs

To extend proxy access rights to a third party, an application client forwards a proxy token (see 8.3.1.6.2.2) to
the third party (e.g., in a target descriptor in the parameter data of the EXTENDED COPY command).

The third party sends the access controls coordinator an ACCESS CONTROL OUT command with ASSIGN
PROXY LUN service action (see 8.3.3.11) specifying the proxy token to request creation of a proxy access
right to the referenced logical unit. The access controls coordinator determines the referenced logical unit
from the proxy token value.

The parameter data for the ACCESS CONTROL OUT command with ASSIGN PROXY LUN service action
includes the LUN value that the third party intends to use when accessing the referenced logical unit. The
resulting LUN value is called a proxy LUN. If the ACCESS CONTROL OUT command with ASSIGN PROXY
LUN service action is successful, the proxy LUN becomes the third party’s mechanism for accessing the
logical unit by proxy.

816 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Once assigned, a proxy LUN shall remain valid until one of the following occurs:

a) the third party releases the proxy LUN value using the ACCESS CONTROL OUT command with
RELEASE PROXY LUN service action (see 8.3.3.12);
b) the proxy token is made invalid as described in 8.3.1.6.2.1; or
c) a logical unit reset or I_T nexus loss of the I_T nexus used to assign the proxy LUN (see 8.3.1.12).

The third party may reissue the ACCESS CONTROL OUT command with ASSIGN PROXY LUN service
action in an attempt to re-establish its proxy access rights. The access controls coordinator shall process the
request as described in 8.3.1.6.2.1 without reference to any previous assignment of the proxy LUN value.

8.3.1.7 Verifying access rights

While access controls are enabled (see 8.3.1.2), access rights for an initiator port shall be validated as
described in this subclause.

Relationships between access controls and commands in a task set are described in 8.3.1.11.1.

All commands shall be processed as if access controls were not present if the ACL (see 8.3.1.3) allows the
initiator port access to the addressed logical unit as a result of one of the following conditions:

a) the ACL contains an ACE containing a TransportID type access identifier (see 8.3.1.3.2) for the
initiator port and that ACE includes a LUACD with LUN value matching the addressed LUN;
b) the initiator port is in the enrolled state (see 8.3.1.5.1.3) under an AccessID, the ACL contains an ACE
containing that AccessID as an access identifier, and that ACE includes a LUACD with LUN value
matching the addressed LUN; or
c) the addressed LUN matches a proxy LUN value (see 8.3.1.6.2.2) assigned using the ACCESS
CONTROL OUT command with ASSIGN PROXY LUN service action (see 8.3.3.11) and the proxy
token (see 8.3.1.6.2.1) used to assign the proxy LUN value is still valid.

If the initiator port is in the pending-enrolled state (see 8.3.1.5.1.4) under an AccessID, the ACL contains an
ACE containing that AccessID as an access identifier, and that ACE includes a LUACD with LUN value
matching the addressed LUN, then commands shall be processed as follows:

a) INQUIRY commands, REPORT LUNS commands, ACCESS CONTROL OUT commands, and
ACCESS CONTROL IN commands shall be processed as if access controls were not present;
b) a REQUEST SENSE command (see 6.39) shall be processed as if access controls were not present,
except in cases where parameter data containing pollable sense data (see 5.10.2) is able to be
returned. In these cases, device server shall terminate the REQUEST SENSE command with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST and the additional sense code set
to ACCESS DENIED - INITIATOR PENDING-ENROLLED; and
c) any other command shall be terminated with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to ACCESS DENIED - INITIATOR
PENDING-ENROLLED.

An application client should respond to the ACCESS DENIED - INITIATOR PENDING-ENROLLED additional
sense code by sending an ACCESS CONTROL OUT command with ACCESS ID ENROLL service action. If
that command succeeds, the application client may retry the terminated command.

If an INQUIRY command is addressed to a LUN for which there is no matching LUN value in any LUACD in
any ACE allowing the initiator port logical unit access rights, then the standard INQUIRY data (see 6.6.2)
PERIPHERAL DEVICE TYPE field shall be set to 1Fh and PERIPHERAL QUALIFIER field shall be set to 011b (i.e., the
device server is not capable of supporting a device at this logical unit).

Working Draft SCSI Primary Commands - 4 (SPC-4) 817

T10/BSR INCITS 513 Revision 37 17 May 2014

The parameter data returned in response to a REPORT LUNS command addressed to LUN 0 or to the
REPORT LUNS well known logical unit shall contain only the list of LUN values that are associated to
accessible logical units for which the initiator port is in:

a) the enrolled state or pending-enrolled state, then the REPORT LUNS parameter data shall include
any LUN values found in LUACDs in the ACE containing the AccessID enrolled by the initiator port; or
b) any enrollment state and has:
A) a TransportID found in the access identifier of an ACE, then the REPORT LUNS parameter data
shall include any LUN values found in LUACDs in that ACE; and
B) access to any proxy LUNs (see 8.3.1.6.2.2), then those LUN values shall be included in the
REPORT LUNS parameter data.

The parameter data returned in response to a REPORT LUNS command that describes well known logical
units shall not be affected by access controls.

If the initiator port is in the not-enrolled state and is not allowed access to any logical unit as result of its
TransportID or as a result of a proxy LUN assignment, then the REPORT LUNS parameter data shall include
only LUN 0 and well known logical units, as defined in 6.33.

Except while access controls are disabled, all cases not described in this subclause shall result in termination
of the command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the
additional sense code set to LOGICAL UNIT NOT SUPPORTED.

8.3.1.8 The management identifier key

8.3.1.8.1 Management identifier key usage

The management identifier key identifies the application that is responsible for managing access controls for a
SCSI target device. This identification occurs when the application client specifies a new management
identifier key value in each ACCESS CONTROL OUT command with the MANAGE ACL service action (see
8.3.3.2), and when the last specified management identifier key value is specified in the ACCESS CONTROL
IN and ACCESS CONTROL OUT service actions as required in 8.3.1.4.2.

To allow for failure scenarios where the management identifier key value has been lost, an override procedure
is described in 8.3.1.8.2.

Use of the management identifier key has the following features:

a) management of access controls is associated with those application clients that provide the correct
management identifier key without regard for the initiator port from which the command was received;
and
b) only an application client that has knowledge of the management identifier key may change the ACL,
allowing the management of access controls to be limited to specific application clients.

8.3.1.8.2 Overriding the management identifier key

8.3.1.8.2.1 The OVERRIDE MGMT ID KEY service action

If a new management identifier key is required and the current management identifier key is not available,
then the ACCESS CONTROL OUT command with OVERRIDE MGMT ID KEY service action (see 8.3.3.8)
may be used to force the management identifier key to a known value.

818 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The ACCESS CONTROL OUT command with OVERRIDE MGMT ID KEY service action should be used only
for failure recovery. If failure recovery is not required, the ACCESS CONTROL OUT command with MANAGE
ACL service action should be used.

To protect the management identifier key from unauthorized overrides, the access controls coordinator shall
restrict use of the ACCESS CONTROL OUT command with OVERRIDE MGMT ID KEY service action based
on the value of the override lockout timer (see 8.3.1.8.2.2).

While the override lockout timer is not set to zero, an ACCESS CONTROL OUT command with OVERRIDE
MGMT ID KEY service action shall be terminated with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

While the override lockout timer is set to zero, an ACCESS CONTROL OUT command with OVERRIDE
MGMT ID KEY service action shall be processed as described in 8.3.3.8.

The access controls coordinator shall log the receipt of each ACCESS CONTROL OUT command with
OVERRIDE MGMT ID KEY service action and its success or failure as described in 8.3.1.10.

8.3.1.8.2.2 The override lockout timer

The access controls coordinator shall maintain the override lockout timer capable of counting up to 65 535
seconds. While the override lockout timer is not set to zero it shall be decreased by one nominally once per
second but no more frequently than once every 800 milliseconds until the value reaches zero. While the
override lockout timer is set to zero, it shall not be changed except as the result of commands sent by an
application client.

The ACCESS CONTROL OUT command with MANAGE OVERRIDE LOCKOUT TIMER service action
manages the state of the override lockout timer (see 8.3.3.7), performing one of the following functions:

a) if no parameter list or the incorrect management identifier key is supplied, the access controls
coordinator shall reset the override lockout timer to the last accepted initial override lockout timer
value; or
b) if the correct management identifier key is supplied, then the access controls coordinator shall do the
following:
1) save the initial override lockout timer value supplied in the parameter data; and
2) reset the override lockout timer to the new initial value.

Setting the initial override lockout timer value to zero disables the override lockout timer and allows the
ACCESS CONTROL OUT command with OVERRIDE MGMT KEY service action to succeed at any time.

Any application client that knows the management identifier key may establish an initial override lockout timer
value of sufficient duration (i.e., up to about 18 hours). Maintaining a non-zero override lockout timer value
may be accomplished without knowing the management identifier key or transporting the management
identifier key on a service delivery subsystem. Attempts to establish a zero initial override lockout timer value
that are not accompanied by the correct management identifier key result in decreasing the probability that a
subsequent ACCESS CONTROL OUT command with OVERRIDE MGMT ID KEY service action is able to
succeed by resetting the override lockout timer.

After a logical unit reset, the override lock timer shall be set to the initial override lockout timer value within ten
seconds of the non-volatile memory containing the initial override lockout timer value becoming available.

The ACCESS CONTROL IN command with REPORT OVERRIDE LOCKOUT TIMER may be used to
discover the state of the override lockout timer.

Working Draft SCSI Primary Commands - 4 (SPC-4) 819

T10/BSR INCITS 513 Revision 37 17 May 2014

8.3.1.9 Reporting access control information

Specific service actions of the ACCESS CONTROL IN command may be used by an application client to
request a report from the access controls coordinator about its access controls data and state.

The ACCESS CONTROL IN command with REPORT ACL service action (see 8.3.2.2) returns the ACL (see
8.3.1.3). The information reported includes the following:

a) the list of access identifiers (see 8.3.1.3.2) and the associated LUACDs (see 8.3.1.3.3) currently in
effect; and
b) the list of proxy tokens (see 8.3.1.6.2.1) currently in effect.

The ACCESS CONTROL IN command with REPORT ACCESS CONTROLS LOG service action (see 8.3.2.4)
returns the contents of the access controls log (see 8.3.1.10).

The ACCESS CONTROL IN command with REPORT OVERRIDE LOCKOUT TIMER service action (see
8.3.2.5) reports on the state of the override lockout timer (see 8.3.1.8.2.2).

8.3.1.10 Access controls log

The access controls log is a record of events maintained by the access controls coordinator.

The access controls log has three portions, each recording a different class of events:

c) invalid key events: mismatches between the management identifier key (see 8.3.1.8) specified by a
service action and the current value maintained by the access controls coordinator;
d) key override events: attempts to override the management identifier key (see 8.3.1.8.2.1), whether
the attempt fails or succeeds; and
e) ACL LUN conflict events: (see 8.3.1.5.2).

Each portion of the log is required to contain a saturating counter of the corresponding events. When a SCSI
target device is manufactured, all event counters shall be set to zero. While access controls are disabled, all
event counters except the Key Override events counter shall be set to zero. Each event counter shall be
incremented by one whenever the corresponding event occurs.

Each log portion may contain additional records with more specific information about each event. If the
resources for additional log records are exhausted, the access controls coordinator shall preserve the most
recently added log records in preference to older log records.

Log records contain a TIME STAMP field whose contents are vendor specific. If the access controls coordinator
has no time stamp resources, the TIME STAMP field shall be set to zero. If time stamp values are provided, the
same timing clock and time stamp format shall be used for all access controls log entries.

Invalid key events occur whenever an access controls command requires the checking of an application client
supplied management identifier key against the current management identifier key saved by the access
controls coordinator and the two values fail to match. If such an event occurs, the access controls coordinator
shall increment the Invalid Keys events counter by one. If the log has additional resources to record event
details, the access controls coordinator shall add an invalid keys log record (containing the information
defined in 8.3.2.4.2.3) describing the event.

If the access controls coordinator processes an ACCESS CONTROL OUT command with OVERRIDE MGMT
KEY service action (see 8.3.3.8), then the access controls coordinator shall increment the Key Overrides
events counter by one without regard for whether the command succeeds or fails. If the log has additional
resources to record event details, the access controls coordinator shall add a key overrides log record

820 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

(containing the information defined in 8.3.2.4.2.2) describing the event.

ACL LUN conflict events occur as defined in 8.3.1.5.2. If such an event occurs, the access controls
coordinator shall increment the ACL LUN Conflicts events counter by one. If the log has additional resources
to record event details, the access controls coordinator shall add an ACL LUN conflicts log record (containing
the information defined in 8.3.2.4.2.4) describing the event.

Selected portions of the access controls log may be requested by an application client using the ACCESS
CONTROL IN command with REPORT ACCESS CONTROLS LOG service action (see 8.3.2.4). With the
exception of the key overrides portion, selected portions of the log may be cleared and the event counters
reset to zero using the ACCESS CONTROL OUT command with CLEAR ACCESS CONTROLS LOG service
action (see 8.3.3.6).

8.3.1.11 Interactions of access controls and other features

8.3.1.11.1 Task set management and access controls

Upon successful completion of an ACCESS CONTROL OUT command with MANAGE ACL service action
(see 8.3.3.2), the specified ACL (see 8.3.1.3) shall apply to all commands that subsequently enter the enabled
command state (see SAM-5). Commands that have modified SCSI target device state information (e.g.,
media, mode pages, and log pages) shall not be affected by an ACCESS CONTROL OUT command that
subsequently enters the enabled command state. Commands in the enabled command state that have not
modified SCSI target device state information may or may not be affected by an ACCESS CONTROL OUT
command that subsequently enters the enabled command state. The ACL in effect prior to the time at which
the ACCESS CONTROL OUT command with MANAGE ACL or DISABLE ACCESS CONTROLS service
action entered the enabled command state shall apply to all commands that are not affected by the ACCESS
CONTROL OUT command.

All the operations performed by a command shall complete under the control of a single ACL, either the state
in effect prior to processing of the ACCESS CONTROL OUT command or the state in effect following
processing of the ACCESS CONTROL OUT command. After a command enters the enabled command state
for the first time changing the access control state from disabled to enabled (see 8.3.1.2) shall have no effect
on the command.

Multiple access control commands, both ACCESS CONTROL IN and ACCESS CONTROL OUT, may be in
the task set concurrently. The order of processing of such commands is defined by the task set management
requirements (see SAM-5), but each command shall be processed as a single indivisible command without
any interleaving of actions that may be required by other access control commands.

8.3.1.11.2 Existing reservations and ACL changes

If a logical unit is reserved by one I_T nexus and that logical unit becomes accessible to another I_T nexus as
a result of an access control command, then there shall be no changes in the reservation of that logical unit.

If a logical unit is reserved by an I_T nexus and that logical unit becomes inaccessible to that I_T nexus as a
result of an access control command or other access control related event, then there shall be no changes in
the reservation. Existing persistent reservations mechanisms allow for other SCSI initiator devices with
access to that logical unit to clear the reservation.

Working Draft SCSI Primary Commands - 4 (SPC-4) 821

T10/BSR INCITS 513 Revision 37 17 May 2014

8.3.1.12 Access controls information persistence and memory usage requirements

If a SCSI target device supports access controls, then the SCSI target device shall contain an access controls
coordinator that shall maintain the following information in nonvolatile memory:

a) whether access controls are enabled or disabled; and

b) the access controls data that table 663 and table 664 require to persist across power cycles, hard
resets, and logical unit resets.

If the access control coordinator’s nonvolatile memory is not ready and the access controls coordinator is
unable to determine that access controls are disabled, then the device servers for all logical units shall
terminate all commands except INQUIRY commands and REQUEST SENSE commands with CHECK
CONDITION status, with the sense key set to NOT READY, and the additional sense code set as described in
table 336 (see 6.47). If a device server in any logical unit receives an INQUIRY command or a REQUEST
SENSE command while the access control coordinator’s nonvolatile memory is not ready and the access
controls coordinator is unable to determine that access controls are disabled, then the device server shall
process the command.

Following an I_T nexus loss, a previously enrolled initiator port shall be placed in the pending-enrolled state if
that initiator port was associated with the lost I_T nexus. Following a logical unit reset, all previously enrolled
initiator ports shall be placed in the pending-enrolled state.

The information shown in table 663 shall be maintained by the access controls coordinator.

Table 663 — Mandatory access controls resources

Persistent
Across Power
Cycles, Hard
Resets, and
Size Logical Unit
Information Description (in bits) Resets
One ACL (see 8.3.1.3) containing at least one ACE contain- VS Yes
ing one access identifier (see 8.3.1.3.2), and at least one
LUACD (see 8.3.1.3.3)
The Enrollment State for each initiator port (see 8.3.1.5.1) VS Yes
Management Identifier Key (see 8.3.1.8) 64 Yes
Default LUNs Generation (DLgeneration, see 8.3.1.4.4) 32 Yes
Override Lockout Timer (see 8.3.1.8.2.2) 16 No
Initial Override Lockout Timer value (see 8.3.1.8.2.2) 16 Yes
Access Controls Log Event Counters (see 8.3.1.10) contain- Yes
ing at least the following:
a) Key Override events counter; 16 Yes
b) Invalid Key events counter; and 16 Yes
c) ACL LUN Conflict events counter 16 Yes

822 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The access controls coordinator may maintain the information shown in table 664.

Table 664 — Optional access controls resources

Persistent Across
Power Cycles,
Hard Resets, and
Size Logical Unit
Information Description (in bits) Resets
One or more proxy tokens (see 8.3.1.6.2.1) 64 Yes
One or more proxy LUNs (see 8.3.1.6.2.2) 64 No
Access controls log event records (see 8.3.1.10) for:
a) Key Override events; (see 8.3.2.4.2.2) Yes
b) Invalid Key events; and (see 8.3.2.4.2.3) Yes
c) ACL LUN Conflict events (see 8.3.2.4.2.4) Yes

At the time of manufacturer, the ACL shall be empty, all values shown in table 663 shall be zero, additional
access control log structures shall be empty and there shall be no valid proxy tokens.

8.3.1.13 Access identifier formats

8.3.1.13.1 Access identifier type

The ACCESS IDENTIFIER TYPE field (see table 665) indicates the format and usage of the access identifier (see
8.3.1.3.2).

Table 665 — ACCESS IDENTIFIER TYPE field

Code Access Identifier Name Reference

00h AccessID 8.3.1.13.2
01h TransportID 7.6.4
02h to 7Fh Reserved
80h to FFh Vendor specific

8.3.1.13.2 AccessID access identifiers

AccessID access identifiers shall have the format shown in table 666.

Table 666 — AccessID access identifier format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • ACCESSID
15
16
•• • Reserved
23

The ACCESSID field contains a value that identifies the AccessID type ACE in which the AccessID access
identifier appears. Within the ACL, no two ACEs shall contain the same AccessID.

Working Draft SCSI Primary Commands - 4 (SPC-4) 823

T10/BSR INCITS 513 Revision 37 17 May 2014

8.3.2 ACCESS CONTROL IN command

8.3.2.1 ACCESS CONTROL IN introduction

The service actions of the ACCESS CONTROL IN command (see table 667) are used to obtain information
about the access controls that are active within the access controls coordinator and to perform other access
control functions (see 8.3.1). If the ACCESS CONTROL IN command is implemented, the ACCESS
CONTROL OUT command also shall be implemented. The ACCESS CONTROL IN command shall not be
affected by access controls.

Table 667 — ACCESS CONTROL IN service actions

Service
action code Service action name Support Reference
00h REPORT ACL M 8.3.2.2
01h REPORT LU DESCRIPTORS M 8.3.2.3
02h REPORT ACCESS CONTROLS LOG M 8.3.2.4
03h REPORT OVERRIDE LOCKOUT TIMER M 8.3.2.5
04h REQUEST PROXY TOKEN O 8.3.2.6
05h to 17h Reserved
18h to 1Fh Vendor specific
Key:
M = Service action implementation is mandatory if ACCESS CONTROL IN is
implemented.
O = Service action implementation is optional.

If an ACCESS CONTROL IN command is received by a device server contained in any logical unit (e.g., LUN
0 or LUN 7) whose standard INQUIRY data (see 6.6.2) has the ACC bit set to one, then the ACCESS
CONTROL IN command shall be processed in the same manner as if the command had been received by the
ACCESS CONTROLS well known logical unit. If an ACCESS CONTROL IN command is received by a device
server whose standard INQUIRY data has the ACC bit set to zero, then the device server shall terminate the
command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID COMMAND OPERATION CODE.

824 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

8.3.2.2 REPORT ACL service action

8.3.2.2.1 REPORT ACL introduction

The ACCESS CONTROL IN command with REPORT ACL service action (see table 668) is used to query the
ACL (see 8.3.1.3) maintained by the access controls coordinator.

Table 668 — ACCESS CONTROL IN command with REPORT ACL service action

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (86h)
1 Reserved SERVICE ACTION (00h)
2 (MSB)
•• • MANAGEMENT IDENTIFIER KEY
9 (LSB)
10 (MSB)
•• • ALLOCATION LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 668 for the ACCESS
CONTROL IN command with REPORT ACL service action.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 668 for the ACCESS
CONTROL IN command with REPORT ACL service action.

If access controls are disabled, the device server shall ignore the MANAGEMENT IDENTIFIER KEY field and shall
complete the command with GOOD status returning the eight byte parameter data header defined in 8.3.2.2.2
subject to the allocation length limitation described in 4.2.5.6.

If access controls are enabled and the contents of the MANAGEMENT IDENTIFIER KEY field do not match the
current management identifier key (see 8.3.1.8) maintained by the access controls coordinator, then
parameter data shall not be returned and the command shall be terminated with CHECK CONDITION status,
with the sense key set to ILLEGAL REQUEST, and the additional sense code set to ACCESS DENIED -
INVALID MGMT ID KEY. This event shall be recorded in the invalid keys portion of the access controls log
(see 8.3.1.10).

The ALLOCATION LENGTH field is defined in 4.2.5.6. The ALLOCATION LENGTH field value should be at least eight.

The CONTROL byte is defined in SAM-5.

Working Draft SCSI Primary Commands - 4 (SPC-4) 825

T10/BSR INCITS 513 Revision 37 17 May 2014

8.3.2.2.2 REPORT ACL parameter data format

8.3.2.2.2.1 REPORT ACL parameter data introduction

The format of the parameter data for an ACCESS CONTROL IN command with REPORT ACL service actions
is shown in table 669.

Table 669 — ACCESS CONTROL IN with REPORT ACL parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
Parameter data header
0 (MSB)
•• • ACL DATA LENGTH (n-3)
3 (LSB)
4 (MSB)
•• • DLGENERATION
7 (LSB)
ACL data pages
8
•• • ACL data page 0

••
•

•• • ACL data page x

n

The ACL DATA LENGTH field shall contain a count of the number of bytes in the remaining parameter data. If
access controls are disabled, the ACL DATA LENGTH field shall be set to four. The contents of the ACL DATA
LENGTH field are not altered based on the allocation length (see 4.2.5.6).

The DLGENERATION field shall contain the current DLgeneration value (see 8.3.1.4.4).

The ACL data pages contain a description of the ACL (see 8.3.1.3) maintained by the access controls
coordinator. Each ACL data page describes one ACE in the ACL or one proxy token (see 8.3.1.6.2). Every
ACE and every proxy token managed by the access controls coordinator shall have an ACL data page in the
parameter data. The content and format of an ACL data page is indicated by a page code. Table 670 lists the
ACL data page codes.

Table 670 — ACL data page codes

Page Code ACL Data Page Name Reference

00h Granted 8.3.2.2.2.2
01h Granted All 8.3.2.2.2.3
02h Proxy Tokens 8.3.2.2.2.4
03h to EFh Reserved
F0h to FFh Vendor specific

826 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

8.3.2.2.2.2 Granted ACL data page format

The Granted ACL data page (see table 671) describes an ACE that allows access to a specific set of logical
units via a list of LUACDs (see 8.3.1.3.3).

Table 671 — Granted ACL data page format

Bit
7 6 5 4 3 2 1 0
Byte
0 PAGE CODE (00h)
1 Reserved
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4 Reserved
5 ACCESS IDENTIFIER TYPE

6 (MSB)
ACCESS IDENTIFIER LENGTH (m-7)
7 (LSB)
8
•• • ACCESS IDENTIFIER
m
LUACD Descriptors
m+1
•• • LUACD descriptor 0
m+20
••
•
n-19
•• • LUACD descriptor x
n

The PAGE CODE field indicates the type of ACL data page that follows and shall be set as shown in table 671
for the Granted ACL data page.

The PAGE LENGTH field indicates the number of additional bytes required for this ACL data page. The contents
of the PAGE LENGTH field are not altered based on the allocation length (see 4.2.5.6).

The ACCESS IDENTIFIER TYPE field (see 8.3.1.13) indicates the format and usage of the access identifier.

The ACCESS IDENTIFIER LENGTH field indicates the number of bytes following taken up by the ACCESS IDENTIFIER
field. The access identifier length shall be at least 24 and shall be a multiple of four.

The ACCESS IDENTIFIER field contains the identifier that the access controls coordinator uses to select the
initiator port(s) that are allowed access to the logical units named by the LUACD descriptors in this ACL data
page. The format of the ACCESS IDENTIFIER field is defined in table 665 (see 8.3.1.13). One Granted ACL data
page or Granted All ACL data page (see 8.3.2.2.2.3) shall be returned for a specific pair of values in the
ACCESS IDENTIFIER TYPE field and ACCESS IDENTIFIER field.

Working Draft SCSI Primary Commands - 4 (SPC-4) 827

T10/BSR INCITS 513 Revision 37 17 May 2014

Each LUACD descriptor (see table 672) describes the access allowed to one logical unit based on the access
identifier. There shall be one LUACD descriptor for each logical unit to which the access identifier allows
access.

Table 672 — Granted ACL data page LUACD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 ACCESS MODE

1
2 Reserved
3
4
•• • LUN VALUE
11
12
•• • DEFAULT LUN
19

The ACCESS MODE field (see table 673) indicates the type of access allowed to the logical unit referenced by
the DEFAULT LUN field and addressable at the specified LUN value.

Table 673 — ACCESS MODE field

Code Description
00h Normal access
01h to EFh Reserved
F0h to FFh Vendor specific

The LUN VALUE field indicates the LUN value an accessing application client uses to access the logical unit via
the initiator port to which the LUACD descriptor applies.

The DEFAULT LUN field identifies the logical unit to which access is allowed using the default LUN value
described in 8.3.1.4.3. The value in the DEFAULT LUN field shall be consistent with the DLGENERATION field
value returned in the parameter data header (see 8.3.2.2.2).

The LUN VALUE field and DEFAULT LUN field may contain the same value.

8.3.2.2.2.3 Granted All ACL data page format

The Granted All ACL data page (see table 674) describes an ACE that allows access to all the SCSI target
device’s logical units with the default LUN values being used as the accessing LUN values. Initiator ports that

828 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

have access via the access identifier in a Granted All ACL data page are allowed to access the SCSI target
device as if access controls were disabled.

Table 674 — Granted All ACL data page format

Bit
7 6 5 4 3 2 1 0
Byte
0 PAGE CODE (01h)
1 Reserved
2 (MSB)
PAGE LENGTH (m-3)
3 (LSB)
4 Reserved
5 ACCESS IDENTIFIER TYPE

6 (MSB)
ACCESS IDENTIFIER LENGTH (m-7)
7 (LSB)
8
•• • ACCESS IDENTIFIER
m

The PAGE CODE field indicates the type of ACL data page that follows and shall be set as shown in table 674
for the Granted All ACL data page.

The PAGE LENGTH field, ACCESS IDENTIFIER TYPE field, and ACCESS IDENTIFIER LENGTH field are described in
8.3.2.2.2.2.

The ACCESS IDENTIFIER field contains the identifier that the access controls coordinator uses to select the
initiator port(s) that are allowed access to all the SCSI target device’s logical units with the default LUN values
being used as the accessing LUN values. The format of the ACCESS IDENTIFIER field is defined in table 665
(see 8.3.1.13). One Granted ACL data page (see 8.3.2.2.2.2) or Granted All ACL data page shall be returned
for a specific pair of values in the ACCESS IDENTIFIER TYPE field and ACCESS IDENTIFIER field.

Working Draft SCSI Primary Commands - 4 (SPC-4) 829

T10/BSR INCITS 513 Revision 37 17 May 2014

8.3.2.2.2.4 Proxy Tokens ACL data page format

The Proxy Tokens ACL data page (see table 675) describes the proxy tokens (see 8.3.1.6.2) maintained by
the access controls coordinator.

Table 675 — Proxy Tokens ACL data page format

Bit
7 6 5 4 3 2 1 0
Byte
0 PAGE CODE (02h)
1 Reserved
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
Proxy token descriptors
4
•• • Proxy token descriptor 0
23
••
•
n-19
•• • Proxy token descriptor x
n

The PAGE CODE field indicates the type of ACL data page that follows and shall be set as shown in table 675
for the Proxy Tokens ACL data page.

The PAGE LENGTH field indicates the number of bytes that follow in this ACL data page. The contents of the
PAGE LENGTH field are not altered based on the allocation length (see 4.2.5.6).

If there are no active proxy tokens, the access controls coordinator may either not include the Proxy Tokens
ACL data page in the parameter data or may include one such ACL data page containing no proxy token
descriptors.

No more than one Proxy Tokens ACL data page shall be included in the parameter data.

830 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Each proxy token descriptor (see table 676) describes the access allowed to one logical unit based on one
proxy token. There shall be one proxy token descriptor for each active proxy token maintained by the access
controls coordinator.

Table 676 — Proxy token descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • Reserved
3
4
•• • PROXY TOKEN
11
12
•• • DEFAULT LUN
19

The PROXY TOKEN field indicates the proxy token to which this proxy token descriptor applies.

The DEFAULT LUN field identifies the logical unit to which this proxy token allows access using the default LUN
value described in 8.3.1.4.3. The value in the DEFAULT LUN field shall be consistent with the DLGENERATION
field value returned in the parameter data header (see 8.3.2.2.2).

The same default LUN value may appear in multiple proxy token descriptors, if multiple proxy tokens are valid
for the same logical unit.

8.3.2.3 REPORT LU DESCRIPTORS service action

8.3.2.3.1 REPORT LU DESCRIPTORS introduction

The ACCESS CONTROL IN command with REPORT LU DESCRIPTORS service action (see table 677)
reports the inventory of logical units for which access controls may be established.

Table 677 — ACCESS CONTROL IN command with REPORT LU DESCRIPTORS service action

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (86h)
1 Reserved SERVICE ACTION (01h)
2 (MSB)
•• • MANAGEMENT IDENTIFIER KEY
9 (LSB)
10 (MSB)
•• • ALLOCATION LENGTH
13 (LSB)
14 Reserved
15 CONTROL

Working Draft SCSI Primary Commands - 4 (SPC-4) 831

T10/BSR INCITS 513 Revision 37 17 May 2014

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 677 for the ACCESS
CONTROL IN command with REPORT LU DESCRIPTORS service action.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 677 for the ACCESS
CONTROL IN command with REPORT LU DESCRIPTORS service action.

If access controls are disabled, the device server shall ignore the MANAGEMENT IDENTIFIER KEY field and shall
complete the command with GOOD status returning the 20-byte parameter data header as defined in
8.3.2.3.2 subject to the ALLOCATION LENGTH limitation described in 4.2.5.6.

NOTE 66 - While access controls are disabled, the logical unit inventory may be obtained using commands
such as REPORT LUNS (see 6.33). To facilitate access controls management, the ACCESS CONTROL IN
command with REPORT LU DESCRIPTORS service action returns more information than the REPORT
LUNS command. While access controls are disabled additional commands such as INQUIRY (see 6.6) are
required to obtain all the information provided by the ACCESS CONTROL IN command with REPORT LU
DESCRIPTORS service action.

If access controls are enabled and the contents of the MANAGEMENT IDENTIFIER KEY field do not match the
current management identifier key (see 8.3.1.8) maintained by the access controls coordinator, then
parameter data shall not be returned and the command shall be terminated with CHECK CONDITION status,
with the sense key set to ILLEGAL REQUEST, and the additional sense code set to ACCESS DENIED -
INVALID MGMT ID KEY. This event shall be recorded in the invalid keys portion of the access controls log
(see 8.3.1.10).

The ALLOCATION LENGTH field is defined in 4.2.5.6. The ALLOCATION LENGTH field value should be at least 20.

The CONTROL byte is defined in SAM-5.

832 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

8.3.2.3.2 REPORT LU DESCRIPTORS parameter data format

The format of the parameter data for an ACCESS CONTROL IN command with REPORT LU DESCRIPTORS
service actions is shown in table 678.

Table 678 — ACCESS CONTROL IN with REPORT LU DESCRIPTORS parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
Parameter data header
0 (MSB)
•• • LU INVENTORY LENGTH (n-3)
3 (LSB)
4 (MSB)
•• • NUMBER OF LOGICAL UNITS
7 (LSB)
8
•• • SUPPORTED LUN MASK FORMAT
15
16 (MSB)
•• • DLGENERATION
19 (LSB)
Logical Unit descriptor list
20
•• • Logical Unit descriptor 0

••
•

•• • Logical Unit descriptor x

n

The LU INVENTORY LENGTH field shall contain a count of the number of bytes in the remaining parameter data.
If access controls are disabled, the LU INVENTORY LENGTH field shall be set to 16. The contents of the LU
INVENTORY LENGTH field are not altered based on the allocation length (see 4.2.5.6).

The NUMBER OF LOGICAL UNITS field shall contain a count of the number of logical units managed by the access
controls coordinator. The value in NUMBER OF LOGICAL UNITS field shall be the same as the number of Logical
Unit descriptors that follow in the Logical Unit descriptor list.

Working Draft SCSI Primary Commands - 4 (SPC-4) 833

T10/BSR INCITS 513 Revision 37 17 May 2014

The SUPPORTED LUN MASK FORMAT field (see table 679) contains a summary of the LUN values (see 8.3.1.3.3)
that the access controls coordinator supports. LUN values are exchanged between application clients and the
access controls coordinator by several service actions (e.g., the ACCESS CONTROL IN command with
REPORT ACL service action described in 8.3.2.2 and the ACCESS CONTROL OUT command with
MANAGE ACL service action described in 8.3.3.2). The format of the SUPPORTED LUN MASK FORMAT field uses
the eight byte LUN structure defined for dependent logical units by SAM-5.

Table 679 — SUPPORTED LUN MASK FORMAT field format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
FIRST LEVEL LUN MASK
1 (LSB)
2 (MSB)
SECOND LEVEL LUN MASK
3 (LSB)
4 (MSB)
THIRD LEVEL LUN MASK
5 (LSB)
6 (MSB)
FOURTH LEVEL LUN MASK
7 (LSB)

The LUN MASK at each level indicates the approximate range of the logical unit number values the access
controls coordinator supports. A bit set to zero in a LUN MASK field indicates that the access controls
coordinator prohibits setting that bit to one in a LUN value. A bit set to one in a LUN MASK field indicates that
the access controls coordinator may allow setting that bit to one in a LUN value.

EXAMPLE – If the access controls coordinator only supports level one LUN values with LUN values ranging from 0 to 255,
then the SUPPORTED LUN MASK FORMAT field shall contain 00FF 0000 0000 0000h. If only LUN values ranging from 0 to 200
were supported, the SUPPORTED LUN MASK FORMAT field still would contain 00FF 0000 0000 0000h.

The value in the SUPPORT LUN MASK FORMAT field only summarizes the supported LUN values and is not a
complete description. The value in the SUPPORT LUN MASK FORMAT field should be used as a guideline for
specifying LUN values in service actions (e.g., ACCESS CONTROL OUT command with MANAGE ACL
service action). LUN values that appear valid based on the contents of the SUPPORT LUN MASK FORMAT field
may still be rejected.

The DLGENERATION field shall contain the current DLgeneration value (see 8.3.1.4.4).

834 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Each Logical Unit descriptor (see table 680) contains information about one logical unit managed by the
access controls coordinator. There shall be one Logical Unit descriptor for every logical unit managed by the
access controls coordinator.

Table 680 — Logical Unit descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 Reserved PERIPHERAL DEVICE TYPE

1 Reserved
2 (MSB)
DESCRIPTOR LENGTH (n-3)
3 (LSB)
4
•• • DEFAULT LUN
11
12 Reserved
13 EVPD DESIGNATION DESCRIPTOR LENGTH

14 Reserved
15 DEVICE IDENTIFIER LENGTH

16
•• • EVPD DESIGNATION DESCRIPTOR
47
48 (MSB)
•• • DEVICE IDENTIFIER
79 (LSB)
80
•• • DEVICE TYPE SPECIFIC DATA
n

The PERIPHERAL DEVICE TYPE field is as defined in 6.6.2.

The DESCRIPTOR LENGTH field indicates the total number of bytes remaining in the descriptor. If the PERIPHERAL
DEVICE TYPE field contains 00h, 04h, or 07h, the DESCRIPTOR LENGTH field shall contain 92 if the descriptor
includes the DEVICE TYPE SPECIFIC DATA field and 80 if it does not. If the PERIPHERAL DEVICE TYPE field contains
any value other than 00h, 04h, or 07h, the DESCRIPTOR LENGTH field shall contain 76. The contents of the
DESCRIPTOR LENGTH field are not altered based on the allocation length (see 4.2.5.6).

The DEFAULT LUN field contains the default LUN value (see 8.3.1.4.3) for the logical unit described by this
logical unit descriptor. The value in the DEFAULT LUN field shall be consistent with the DLGENERATION field
value returned in the parameter data header (see 8.3.2.3.2). The value in the DEFAULT LUN field shall not
identify a well known logical unit.

The EVPD DESIGNATION DESCRIPTOR LENGTH field indicates the number of non pad bytes in the EVPD
DESIGNATION DESCRIPTOR field.

The DEVICE IDENTIFIER LENGTH field indicates the number of non pad bytes in the DEVICE IDENTIFIER field.

Working Draft SCSI Primary Commands - 4 (SPC-4) 835

T10/BSR INCITS 513 Revision 37 17 May 2014

The EVPD DESIGNATION DESCRIPTOR field shall be derived from one of the Device Identification VPD page (see
7.8.6) designation descriptors having 00b in the ASSOCIATION field as follows:

a) if the designation descriptor has a length less than 32 bytes, then the EVPD DESIGNATION DESCRIPTOR
field shall be set to the zero-padded (see 4.3.2) designation descriptor value. The EVPD DESIGNATION
DESCRIPTOR LENGTH field shall be set to the length of the designation descriptor not including pad
bytes; or
b) if the designation descriptor has a length greater than or equal to 32 bytes, then the EVPD DESIGNATION
DESCRIPTOR field shall be set to the first 32 bytes of the designation descriptor. The EVPD DESIGNATION
DESCRIPTOR LENGTH field shall be set to 32.

If there are several designation descriptors having 00b in the ASSOCIATION field, the choice of which descriptor
to copy to the EVPD DESIGNATION DESCRIPTOR field is vendor specific. However, all ACCESS CONTROL IN
commands with the REPORT LU DESCRIPTORS service action shall return the same EVPD DESIGNATION
DESCRIPTOR field contents for a specific logical unit.

If a device identifier has been set for the logical unit using the SET IDENTIFYING INFORMATION command
(see 6.43) and that device identifier has a length that is:

a) length less than 32 bytes, then the DEVICE IDENTIFIER field shall be set to the zero-padded (see 4.3.2)
device identifier value. The DEVICE IDENTIFIER LENGTH field shall be set to the length of the device
identifier not including pad bytes; or
b) greater than or equal to 32 bytes, then the DEVICE IDENTIFIER field shall be set to the first 32 bytes of
the identifier. The DEVICE IDENTIFIER LENGTH field shall be set to 32.

If no device identifier has been established by a SET IDENTIFYING INFORMATION command, then the
DEVICE IDENTIFIER LENGTH field shall be set to zero and the DEVICE IDENTIFIER field shall be set to zero.

If the PERIPHERAL DEVICE TYPE field contains any value other than 00h, 04h, or 07h, the DEVICE TYPE SPECIFIC
DATA field shall not be present in the Logical Unit descriptor.

The Logical Unit descriptor shall include the DEVICE TYPE SPECIFIC DATA field if:

a) the PERIPHERAL DEVICE TYPE field contains 00h;

b) the logical unit supports the READ CAPACITY(16) command (see SBC-3); and
c) the logical unit standard INQUIRY data (see 6.6.2) has the RMB bit set to zero.

If the Logical Unit descriptor includes the DEVICE TYPE SPECIFIC DATA field, then the size of the DEVICE TYPE
SPECIFIC DATA field shall be 12 bytes and the field shall contain data equivalent to the first 12 bytes of
parameter data returned by a successful READ CAPACITY(16) command.

836 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

8.3.2.4 REPORT ACCESS CONTROLS LOG service action

8.3.2.4.1 REPORT ACCESS CONTROLS LOG introduction

The ACCESS CONTROL IN command with REPORT ACCESS CONTROLS LOG service action (see table
681) is used to obtain the access controls log (see 8.3.1.10).

Table 681 — ACCESS CONTROL IN command REPORT ACCESS CONTROLS LOG service action

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (86h)
1 Reserved SERVICE ACTION (02h)
2 (MSB)
•• • MANAGEMENT IDENTIFIER KEY
9 (LSB)
10 Reserved LOG PORTION

11 Reserved
12 (MSB)
ALLOCATION LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 681 for the ACCESS
CONTROL IN command with REPORT ACCESS CONTROLS LOG service action.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 681 for the ACCESS
CONTROL IN command with REPORT ACCESS CONTROLS LOG service action.

If access controls are disabled, the device server shall ignore the MANAGEMENT IDENTIFIER KEY field and shall
complete the command with GOOD status returning the eight byte parameter data header as defined in
8.3.2.4.2.1 subject to the ALLOCATION LENGTH limitation described in 4.2.5.6.

The Key Overrides portion of the log is maintained while access controls are disabled (see 8.3.3.3) and may
be retrieved by enabling access controls and issuing an ACCESS CONTROL IN command with REPORT
ACCESS CONTROLS LOG service action.

If access controls are enabled and table 682 specifies that the management identifier key is not required then
the device server shall ignore the contents of the MANAGEMENT IDENTIFIER KEY field.

If access controls are enabled, table 682 specifies that the management key identifier is required, and the
contents of the MANAGEMENT IDENTIFIER KEY field do not match the current management identifier key (see
8.3.1.8) maintained by the access controls coordinator, then the parameter data shall not be returned and the
command shall be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to ACCESS DENIED - INVALID MGMT ID KEY. This event shall
be recorded in the invalid keys portion of the access controls log (see 8.3.1.10).

Working Draft SCSI Primary Commands - 4 (SPC-4) 837

T10/BSR INCITS 513 Revision 37 17 May 2014

The LOG PORTION field (see table 682) specifies the access controls log portion being requested.

Table 682 — CDB LOG PORTION field

Management Identifier
Code Description Key Required
00b Key Overrides portion No
01b Invalid Keys portion Yes
10b ACL LUN Conflicts portion Yes
11b Reserved

The ALLOCATION LENGTH field is defined in 4.2.5.6. The ALLOCATION LENGTH field value should be at least eight.

The CONTROL byte is defined in SAM-5.

8.3.2.4.2 REPORT ACCESS CONTROLS LOG parameter data format

8.3.2.4.2.1 REPORT ACCESS CONTROLS LOG parameter data introduction

The format of the parameter data for an ACCESS CONTROL IN command with REPORT ACCESS
CONTROLS LOG service actions is shown in table 683.

Table 683 — ACCESS CONTROL IN with REPORT ACCESS CONTROLS LOG parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
Parameter data header
0 (MSB)
•• • LOG LIST LENGTH (n-3)
3 (LSB)
4 Reserved
5 Reserved LOG PORTION

6 (MSB)
COUNTER
7 (LSB)
Access Controls Log portion pages
8
•• • Access Controls Log portion page 0

•
••

•• • Access Controls Log portion page x

n

The LOG LIST LENGTH field shall contain a count of the number of bytes in the remaining parameter data. If
access controls are disabled, the LOG LIST LENGTH field shall be set to four. The contents of the LOG LIST
LENGTH field are not altered based on the allocation length (see 4.2.5.6).

838 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The LOG PORTION field (see table 684) indicates the access controls log portion being returned, the contents of
the COUNTER field, and the type of access controls log portion pages being returned.

Table 684 — Parameter data LOG PORTION field

Access controls log Access controls log

Code portion being returned COUNTER field contents page format reference
00b Key Overrides portion Key Override events counter 8.3.2.4.2.2
01b Invalid Keys portion Invalid Key events counter 8.3.2.4.2.3
11b ACL LUN Conflicts portion ACL LUN Conflict events counter 8.3.2.4.2.4
11b Reserved

The COUNTER field contains the events counter value (see 8.3.1.10) for the access controls log portion
indicated by the LOG PORTION field (see table 684).

The format of the access controls log portion pages is indicated by the value in the LOG PORTION field (see
table 684). All the access controls log portion pages returned in a single parameter data shall have the same
format. If the access controls coordinator does not support access controls log portion pages in the portion of
the access controls log indicated by the LOG PORTION field, then the parameter data shall only contain the
parameter data header.

8.3.2.4.2.2 Key Overrides access controls log portion page format

The Key Overrides access controls log portion page (see table 685) contains details of logged attempts to
override the management identifier key (see 8.3.1.10) using the ACCESS CONTROL OUT command with
OVERRIDE MGMT ID KEY service action (see 8.3.3.8) whether those attempts were successful or not.

Table 685 — Key Overrides access controls log portion page format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
TRANSPORTID ADDITIONAL LENGTH (m-32)
1 (LSB)
2 Reserved
3 Reserved SUCCESS

4 (MSB)
•• • TIME STAMP
7 (LSB)
8
•• • TransportID
m-1
m (MSB)
INITIAL OVERRIDE LOCKOUT TIMER
m+1 (LSB)
m+2 (MSB)
OVERRIDE LOCKOUT TIMER
m+3 (LSB)

The TRANSPORTID ADDITIONAL LENGTH field indicates the additional length of the TransportID beyond the
minimum length of 24 bytes. The TransportID additional length shall be a multiple of four.

Working Draft SCSI Primary Commands - 4 (SPC-4) 839

T10/BSR INCITS 513 Revision 37 17 May 2014

A SUCCESS bit set to one indicates that the specific ACCESS CONTROL OUT command with OVERRIDE
MGMT ID KEY service action event recorded in the access controls log successfully overrode the
management identifier key. A SUCCESS bit set to zero indicates that the command was terminated.

The TIME STAMP field shall contain zero or an indication of the time at which the ACCESS CONTROL OUT
command with OVERRIDE MGMT ID KEY service action was processed as described in 8.3.1.10.

The TransportID indicates the TransportID of the initiator port from which the command was received.

The INITIAL OVERRIDE LOCKOUT TIMER field shall contain the access controls coordinator’s initial override
lockout timer value (see 8.3.1.8.2.2) at the time when the key override event was logged.

The OVERRIDE LOCKOUT TIMER field shall contain the access controls coordinator’s override lockout timer value
(see 8.3.1.8.2.2) at the time when the key override event was logged.

8.3.2.4.2.3 Invalid Keys access controls log portion page format

The Invalid Keys access controls log portion page (see table 686) contains details of logged receipts of
ACCESS CONTROL IN command or ACCESS CONTROL OUT command specifying an incorrect
management identifier key (see 8.3.1.10).

Table 686 — Invalid Keys access controls log portion page format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
TRANSPORTID ADDITIONAL LENGTH (m-32)
1 (LSB)
2 OPERATION CODE

3 Reserved SERVICE ACTION

4 (MSB)
•• • TIME STAMP
7 (LSB)
8
•• • TransportID
m-1
m (MSB)
•• • INVALID MANAGEMENT IDENTIFIER KEY
m+7 (LSB)

The TRANSPORTID ADDITIONAL LENGTH field indicates the additional length of the TransportID beyond the
minimum length of 24 bytes. The TransportID additional length shall be a multiple of four.

The OPERATION CODE field and SERVICE ACTION field shall be set to the respective values from the CDB of the
access controls command that specified the invalid management identifier key.

The TIME STAMP field shall contain zero or an indication of the time at which the ACCESS CONTROL IN or
ACCESS CONTROL OUT command was processed as described in 8.3.1.10.

The TransportID indicates the TransportID of the initiator port from which the command was received.

840 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The INVALID MANAGEMENT IDENTIFIER KEY field shall be set to the value of the invalid management identifier key
detected by the access controls coordinator.

NOTE 67 - The management identifier key is typically in the CDB for ACCESS CONTROL IN commands and
in the parameter data for ACCESS CONTROL OUT commands.

8.3.2.4.2.4 ACL LUN Conflicts access controls log portion page format

The ACL LUN Conflicts access controls log portion page (see table 687) contains details of logged ACL LUN
conflicts (see 8.3.1.10) encountered by the access controls coordinator if a previously not-enrolled initiator
port sends an ACCESS CONTROL OUT command with ACCESS ID ENROLL service action (see 8.3.3.4).

Table 687 — ACL LUN Conflicts access controls log portion page format

Bit
7 6 5 4 3 2 1 0
Byte
0 (MSB)
TRANSPORTID ADDITIONAL LENGTH (m-32)
1 (LSB)
2
Reserved
3
4 (MSB)
•• • TIME STAMP
7 (LSB)
8
•• • TransportID
m-1
m (MSB)
•• • ACCESSID
m+23 (LSB)

The TRANSPORTID ADDITIONAL LENGTH field indicates the additional length of the TransportID beyond the
minimum length of 24 bytes. The TransportID additional length shall be a multiple of four.

The TIME STAMP field shall contain zero or an indication of the time at which the ACCESS CONTROL OUT
command with ACCESS ID ENROLL service action was processed as described in 8.3.1.10.

The TransportID indicates the TransportID of the initiator port from which the command was received that
resulted in the ACL LUN conflict.

The A CCESS ID field shall be set to the AccessID that the initiator port attempted to enroll. This shall
correspond to an access identifier in ACL entry at the time the ACL LUN conflict event occurred.

Working Draft SCSI Primary Commands - 4 (SPC-4) 841

T10/BSR INCITS 513 Revision 37 17 May 2014

8.3.2.5 REPORT OVERRIDE LOCKOUT TIMER service action

The ACCESS CONTROL IN command with REPORT OVERRIDE LOCKOUT TIMER service action (see
table 688) is used query the value of the override lockout timer (see 8.3.1.8.2.2).

Table 688 — ACCESS CONTROL IN command REPORT OVERRIDE LOCKOUT TIMER service action

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (86h)
1 Reserved SERVICE ACTION (03h)
2 (MSB)
•• • MANAGEMENT IDENTIFIER KEY
9 (LSB)
10 (MSB)
•• • ALLOCATION LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 688 for the ACCESS
CONTROL IN command with REPORT OVERRIDE LOCKOUT TIMER service action.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 688 for the ACCESS
CONTROL IN command with REPORT OVERRIDE LOCKOUT TIMER service action.

If access controls are disabled, eight bytes of zeros shall be returned subject to the allocation length
limitations described in 4.2.5.6 and the command shall be completed with GOOD status.

If access controls are enabled and the contents of the MANAGEMENT IDENTIFIER KEY field do not match the
current management identifier key (see 8.3.1.8) maintained by the access controls coordinator, then
parameter data shall not be returned, the command shall be terminated with CHECK CONDITION status, with
the sense key set to ILLEGAL REQUEST, and the additional sense code set to ACCESS DENIED - INVALID
MGMT ID KEY. This event shall be recorded in the invalid keys portion of the access controls log (see
8.3.1.10).

The ALLOCATION LENGTH field is defined in 4.2.5.6. The ALLOCATION LENGTH field value should be at least eight.

The CONTROL byte is defined in SAM-5.

842 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If access controls are enabled, the parameter data for the ACCESS CONTROL IN command with REPORT
OVERRIDE LOCKOUT TIMER service action shall have the format shown in table 689.

Table 689 — ACCESS CONTROL IN with REPORT OVERRIDE LOCKOUT TIMER parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0
Reserved
1
2 (MSB)
CURRENT OVERRIDE LOCKOUT TIMER
3 (LSB)
4 (MSB)
INITIAL OVERRIDE LOCKOUT TIMER
5 (LSB)
6 (MSB)
KEY OVERRIDES COUNTER
7 (LSB)

The CURRENT OVERRIDE LOCKOUT TIMER field shall be set to the current value of the override lockout timer (see
8.3.1.8.2.2).

The INITIAL OVERRIDE LOCKOUT TIMER field shall be set to the initial override lockout timer value (see
8.3.1.8.2.2) established by the last successful ACCESS CONTROL OUT command with MANAGE
OVERRIDE LOCKOUT TIMER service action (see 8.3.3.7).

The KEY OVERRIDES COUNTER field shall be set to the value of the Key Override events counter in the access
controls log (see 8.3.1.10).

8.3.2.6 REQUEST PROXY TOKEN service action

The ACCESS CONTROL IN command with REQUEST PROXY TOKEN service action (see table 690) is used
to obtain a proxy token (see 8.3.1.6.2) for a logical unit to which that initiator port has non-proxy access rights.
The returned proxy token may be used to pass temporary access to the logical unit to a third party that may
use other proxy related service actions of the ACCESS CONTROL IN command and ACCESS CONTROL
OUT command to gain access to the logical unit. If the ACCESS CONTROL IN command with REQUEST
PROXY TOKEN service action is not supported, the command shall be terminated with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN
CDB.

Working Draft SCSI Primary Commands - 4 (SPC-4) 843

T10/BSR INCITS 513 Revision 37 17 May 2014

Table 690 — ACCESS CONTROL IN command with REQUEST PROXY TOKEN service action

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (86h)
1 Reserved SERVICE ACTION (04h)
2 (MSB)
•• • LUN VALUE
9 (LSB)
10 (MSB)
•• • ALLOCATION LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 690 for the ACCESS
CONTROL IN command with REQUEST PROXY TOKEN service action.

The SERVICE ACTION field is defined in 4.2.5.2 and shall be set as shown in table 690 for the ACCESS
CONTROL IN command with REQUEST PROXY TOKEN service action.

If access controls are disabled, the command shall be terminated with CHECK CONDITION status, with the
sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

NOTE 68 - If access controls are disabled, all logical units are accessible and all initiator ports share the
same LUN values for addressing. A proxy token is not needed because sharing LUN values is sufficient.

The LUN VALUE field shall contain the LUN value the application client uses to access the logical unit via the
initiator port over which the proxy token is requested.

If the LUN value corresponds to a logical unit that is accessible to the requesting initiator port either through a
TransportID or through the AccessID under which the initiator port is currently in the enrolled state (see
8.3.1.5.1), and the access controls coordinator has sufficient resources to create and manage a new proxy
token, then the parameter data shown in table 691 shall be returned.

If the LUN value does not correspond to an accessible logical unit or corresponds to a logical unit accessible
only through a proxy token, then the parameter data shall not be returned and the command shall be
terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to ACCESS DENIED - INVALID LU IDENTIFIER.

If the LUN value corresponds to a logical unit accessible only through an enrolled AccessID and the initiator
port is in the pending-enrolled state, then the parameter data shall not be returned and the command shall be
terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to ACCESS DENIED - INITIATOR PENDING-ENROLLED.

If the access controls coordinator does not have enough resources to create and manage a new proxy token,
then the command shall be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INSUFFICIENT ACCESS CONTROL RESOURCES.

The ALLOCATION LENGTH field is defined in 4.2.5.6. The ALLOCATION LENGTH field value should be at least eight.

844 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The CONTROL byte is defined in SAM-5.

The format of the parameter data for the ACCESS CONTROL IN command with REQUEST PROXY TOKEN
service action is shown in table 691.

Table 691 — ACCESS CONTROL IN with REQUEST PROXY TOKEN parameter data

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • PROXY TOKEN
7

8.3.3 ACCESS CONTROL OUT command

8.3.3.1 ACCESS CONTROL OUT introduction

The service actions of the ACCESS CONTROL OUT command (see table 692) are used to request service
actions by the access controls coordinator to limit or grant access to the logical units by initiator ports. If the
ACCESS CONTROL OUT command is implemented, the ACCESS CONTROL IN command also shall be
implemented. The ACCESS CONTROL OUT command shall not be affected by access controls.

Table 692 — ACCESS CONTROL OUT service actions

Service
action code Service action name Support Reference
00h MANAGE ACL M 8.3.3.2
01h DISABLE ACCESS CONTROLS M 8.3.3.3
02h ACCESS ID ENROLL M 8.3.3.4
03h CANCEL ENROLLMENT M 8.3.3.5
04h CLEAR ACCESS CONTROLS LOG M 8.3.3.6
05h MANAGE OVERRIDE LOCKOUT TIMER M 8.3.3.7
06h OVERRIDE MGMT ID KEY M 8.3.3.8
07h REVOKE PROXY TOKEN O 8.3.3.9
08h REVOKE ALL PROXY TOKENS O 8.3.3.10
09h ASSIGN PROXY LUN O 8.3.3.11
0Ah RELEASE PROXY LUN O 8.3.3.12
0Bh to 17h Reserved
18h to 1Fh Vendor specific
Key:
M = Service action implementation is mandatory if ACCESS CONTROL OUT is
implemented.
O = Service action implementation is optional.

If an ACCESS CONTROL OUT command is received by a device server contained in any logical unit (e.g.,
LUN 0 or LUN 7) whose standard INQUIRY data (see 6.6.2) has the ACC bit set to one, then the ACCESS
CONTROL OUT command shall be processed in the same manner as if the command had been received by
the ACCESS CONTROLS well known logical unit. If an ACCESS CONTROL OUT command is received by a
device server whose standard INQUIRY data has the ACC bit set to zero, then the command shall be

Working Draft SCSI Primary Commands - 4 (SPC-4) 845

T10/BSR INCITS 513 Revision 37 17 May 2014

terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID COMMAND OPERATION CODE.

If an ACCESS CONTROL OUT command is received while an IKEv2-SCSI CCS is in progress (see 5.13.4),
then the command shall be terminated with CHECK CONDITION status, with the sense key NOT READY, and
the additional sense code set to LOGICAL UNIT NOT READY, SA CREATION IN PROGRESS. The sense
key specific additional sense data may be set as described in 5.13.5.

The CDB format used by all ACCESS CONTROL OUT service actions is shown in table 693.

Table 693 — ACCESS CONTROL OUT command format

Bit
7 6 5 4 3 2 1 0
Byte
0 OPERATION CODE (87h)
1 Reserved SERVICE ACTION (see table 692)
2
•• • Reserved
9
10 (MSB)
•• • PARAMETER LIST LENGTH
13 (LSB)
14 Reserved
15 CONTROL

The OPERATION CODE field is defined in 4.2.5.1 and shall be set as shown in table 693 for the ACCESS
CONTROL OUT command.

The SERVICE ACTION field is defined in 4.2.5.2 and table 692.

The PARAMETER LIST LENGTH field indicates the amount of data being sent to the access controls coordinator in
the Data-Out Buffer. The format of the parameter list is specific to each service action.

The CONTROL byte is defined in SAM-5.

8.3.3.2 MANAGE ACL service action

8.3.3.2.1 MANAGE ACL introduction

The ACCESS CONTROL OUT command with MANAGE ACL service action is used to authorize access or
revoke access to a logical unit or logical units by initiator ports. The ACCESS CONTROL OUT command with
MANAGE ACL service action adds, changes, or removes an entry or multiple entries in the access controls
coordinator’s ACL (see 8.3.1.3).

The format of the CDB for the ACCESS CONTROL OUT command with MANAGE ACL service action is
shown in table 693 (see 8.3.3.1).

If the PARAMETER LIST LENGTH field in the CDB is set to zero, the access controls coordinator shall take no
action and the command shall be completed with GOOD status.

846 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If the value in the PARAMETER LIST LENGTH field is less than 20 or results in truncation of any ACE page (see
table 695), then the command shall be terminated with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to PARAMETER LIST LENGTH ERROR.

If the access controls coordinator is unable to complete the ACCESS CONTROL OUT command with
MANAGE ACL service action because it has insufficient resources, then the access controls coordinator shall
take no action and not change any of its state and the command shall be terminated with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
INSUFFICIENT ACCESS CONTROL RESOURCES.

The format of the parameter data for the ACCESS CONTROL OUT command with MANAGE ACL service
action is shown in table 694.

Table 694 — ACCESS CONTROL OUT with MANAGE ACL parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
Parameter list header
0
•• • Reserved
3
4 (MSB)
•• • MANAGEMENT IDENTIFIER KEY
11 (LSB)
12 (MSB)
•• • NEW MANAGEMENT IDENTIFIER KEY
19 (LSB)
20 Reserved
21 FLUSH Reserved
22 Reserved
23 Reserved
24 (MSB)
•• • DLGENERATION
27 (LSB)
ACE pages
28
•• • ACE page 0

•
••

•• • ACE page x
n

If access controls are enabled and the contents of the MANAGEMENT IDENTIFIER KEY field do not match the
current management identifier key (see 8.3.1.8) maintained by the access controls coordinator, then the
access controls coordinator’s state shall not be altered, the command shall be terminated with CHECK

Working Draft SCSI Primary Commands - 4 (SPC-4) 847

T10/BSR INCITS 513 Revision 37 17 May 2014

CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
ACCESS DENIED - INVALID MGMT ID KEY. This event shall be recorded in the invalid keys portion of the
access controls log (see 8.3.1.10).

If the contents of the MANAGEMENT IDENTIFIER KEY field match the current management identifier key
maintained by the access controls coordinator, then the access controls coordinator shall set its management
identifier key to the value specified in the NEW MANAGEMENT IDENTIFIER KEY field and if access controls are
disabled the access controls coordinator shall enable them.

The FLUSH bit set to one specifies that the access controls coordinator shall place every initiator port in the
enrolled state into the pending-enrolled state (see 8.3.1.5.1.4).

The DLGENERATION field specifies the DLgeneration value (see 8.3.1.4.4) associated with the default LUN
values in the Grant/Revoke ACE pages in the parameter data.

The ACE pages that may follow the parameter list header provide additional changes to the ACL. Each ACE
page describes one ACE in the ACL that is to be added, modified, or removed. The content and format of an
ACE page is indicated by a page code (see table 695).

Table 695 — ACE page codes

Page Code ACE Page Name Reference

00h Grant/Revoke 8.3.3.2.2
01h Grant All 8.3.3.2.3
02h Revoke Proxy Token 8.3.3.2.4
03h Revoke All Proxy Tokens 8.3.3.2.5
04h to EFh Reserved
F0h to FFh Vendor specific

The following requirements apply to the processing of changes to the access control state:

a) no change to the access control state shall occur if the ACCESS CONTROL OUT command with
MANAGE ACL service action completes with a status other than GOOD status; and
b) if the ACCESS CONTROL OUT command with MANAGE ACL service action completes with GOOD
status, then the following shall have been performed as a single indivisible event:
1) changes resulting from the contents of fields in the parameter list header shall be processed; and
2) changes resulting from the contents of ACE pages shall be processed;
a) multiple ACE pages shall be processed sequentially;
b) if an ACE page contains conflicting information in LUACD descriptors, the information in the
last LUACD descriptor within the ACE page shall take precedence; and
c) if an ACE containing an AccessID type access identifier (see 8.3.1.3.2) is replaced and the
ACE page that caused the change has the NOCNCL bit (see 8.3.3.2.2) set to zero, then any
initiator port in the enrolled state or pending-enrolled state under the AccessID in that ACE
shall be placed in the not-enrolled state (see 8.3.1.5.1.2).

An ACE page contains conflicting information if either of the following is true:

a) two LUACD descriptors are present with the same LUN value and different default LUN values; or
b) two LUACD descriptors are present with different LUN values and the same default LUN value.

848 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

8.3.3.2.2 The Grant/Revoke ACE page

The Grant/Revoke ACE page (see table 696) is used to add, modify, or remove an ACE from the ACL (see
8.3.1.3).

Table 696 — Grant/Revoke ACE page format

Bit
7 6 5 4 3 2 1 0
Byte
0 PAGE CODE (00h)
1 Reserved
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4 NOCNCL Reserved
5 ACCESS IDENTIFIER TYPE

6 (MSB)
ACCESS IDENTIFIER LENGTH (m-7)
7 (LSB)
8
•• • ACCESS IDENTIFIER
m
LUACD descriptors
m+1
•• • LUACD descriptor 0
m+20
••
•
n-19
•• • LUACD descriptor x
n

The PAGE CODE field specifies the type of ACE page that follows (see table 695) and shall be set as shown in
table 696 for the Grant/Revoke ACE page.

The PAGE LENGTH field specifies the number of additional bytes present in this ACE page.

A no changes to current logical unit access (NOCNCL) bit set to one specifies that the application client is telling
the access controls coordinator that this ACE page makes no changes to the existing logical unit access
conditions in the ACL. A NOCNCL bit set to zero specifies that the ACE page may or may not change existing
logical unit access conditions. If the ACCESS IDENTIFIER TYPE specifies a TransportID (see 8.3.2.2.2.2), the
NOCNCL bit shall be ignored.

The ACCESS IDENTIFIER TYPE field and ACCESS IDENTIFIER LENGTH field are described in 8.3.2.2.2.2.

The ACCESS IDENTIFIER field contains the identifier that the access controls coordinator uses to select the ACE
that is to be added, modified, or removed. The format of the ACCESS IDENTIFIER field is defined in table 665
(see 8.3.1.13).

Working Draft SCSI Primary Commands - 4 (SPC-4) 849

T10/BSR INCITS 513 Revision 37 17 May 2014

Any of the following conditions in the parameter header or any Grant/Revoke ACE page or Grant All ACE
page shall cause the access coordinator to not change its state and shall cause the command to be
terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID FIELD IN PARAMETER LIST:

a) the value in the DLGENERATION field in the parameter list header (see 8.3.3.2.1) does not match the
current value of the DLgeneration counter (see 8.3.1.4.4) maintained by the access controls
coordinator;
b) an ACCESS IDENTIFIER TYPE field specifies an unsupported value;
c) an ACCESS IDENTIFIER TYPE field contains 01h (see 8.3.1.3.2) with an ACCESS IDENTIFIER field that
contains an invalid TransportID (see 8.3.1.3.2) as defined for the applicable protocol standard;
d) two ACE pages that have the same values in the ACCESS IDENTIFIER TYPE and ACCESS IDENTIFIER
fields; or
e) changes in the ACL that result in an ACL LUN conflict (see 8.3.1.5.2).

The application client should obtain the current association of default LUN values to logical units and the
DLgeneration value for that association prior to sending this service action. The ACCESS CONTROL IN
command with REPORT LU DESCRIPTORS service action (see 8.3.2.3) returns this information.

Each LUACD descriptor (see table 697) describes the access to be allowed to one logical unit based on the
access identifier in the ACE page. An ACE page may contain zero or more LUACD descriptors.

Table 697 — ACE page LUACD descriptor format

Bit
7 6 5 4 3 2 1 0
Byte
0 ACCESS MODE

1
2 Reserved
3
4
•• • LUN VALUE
11
12
•• • DEFAULT LUN
19

The ACCESS MODE field is described in 8.3.2.2.2.2.

The LUN VALUE field specifies the LUN value an accessing application client uses to access the logical unit via
the initiator port to which the LUACD descriptor applies.

The DEFAULT LUN field specifies the logical unit to which the value in the LUN VALUE allows access. The
DEFAULT LUN field shall contain a default LUN value (see 8.3.1.4.3). The value in the DEFAULT LUN field shall be
consistent with the DLGENERATION field value specified in the parameter list header (see 8.3.3.2.1). If the
DEFAULT LUN field references a well known logical unit, the access controls coordinator’s state shall not be
modified and the command shall be terminated with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

If the specified access mode is not supported or if the DEFAULT LUN field contains a value that is not valid or the
LUN VALUE field contains a value that the access controls coordinator does not support as a valid LUN, then

850 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

the access controls coordinator’s state shall not be modified and the command shall be terminated with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, the additional sense code set to
ACCESS DENIED - INVALID LU IDENTIFIER, and the sense key specific information shall be set as
described for the ILLEGAL REQUEST sense key in 4.5.2.4.2. If the error is an unsupported value in the LUN
VALUE field, then the access controls coordinator should determine a suggested LUN value that is unlikely to
produce an error while also minimizing the absolute value of the difference of the erroneous default LUN value
and the suggested LUN value. If a suggested LUN value is determined, the first four bytes of the suggested
LUN value shall be returned in the INFORMATION field (see 4.5.4) and the last four bytes shall be returned in the
COMMAND-SPECIFIC INFORMATION field (see 4.5.5) the sense data.

Based on the access identifier and the presence or absence of LUACD descriptors, the access controls
coordinator shall add, modify, or remove an ACE in the ACL as shown in table 698.

Table 698 — Access Coordinator Grant/Revoke ACE page actions

ACL already contains an ACE with the access

identifier matching the one in the ACE page?

Yes No

ACE page Modify the existing ACE in Add a new ACE to the
Yes
includes the ACL. ACL.
LUCAD Remove the existing ACE Take no action; this shall
descriptors? No from the ACL. not be considered an
error.

If the ACCESS IDENTIFIER TYPE indicates type AccessID, the enrollment state (see 8.3.1.5.1) of any initiator port
that is enrolled under the specified AccessID, shall be affected as follows:

a) if the ACE containing the AccessID is removed, the initiator port shall be placed in the not-enrolled
state; or
b) if the ACE containing the AccessID is modified by a Grant/Revoke ACE page or a Grant All ACE
page, then;
A) if the NOCNCL bit is set to zero in that ACE page, the initiator port shall be placed in the
not-enrolled state; or
B) if the NOCNCL bit is set to one in that ACE page, the enrollment state of the initiator port may be left
unchanged or the initiator port may be placed in the not-enrolled state (see 8.3.1.5.1.2) based on
vendor specific considerations.

Working Draft SCSI Primary Commands - 4 (SPC-4) 851

T10/BSR INCITS 513 Revision 37 17 May 2014

8.3.3.2.3 The Grant All ACE page

The Grant All ACE page (see table 699) is used to add or modify an ACE in the ACL (see 8.3.1.3). An ACE
added or modified using the Grant All ACE page allows initiator ports with the specified access identifier to
access the SCSI target device as if access controls were disabled.

Table 699 — Grant All ACE page format

Bit
7 6 5 4 3 2 1 0
Byte
0 PAGE CODE (01h)
1 Reserved
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4 NOCNCL Reserved
5 ACCESS IDENTIFIER TYPE

6 (MSB)
ACCESS IDENTIFIER LENGTH (m-7)
7 (LSB)
8
•• • ACCESS IDENTIFIER
n

The PAGE CODE field specifies the type of ACE page that follows (see table 695) and shall be set as shown in
table 699 for the Grant All ACE page.

The PAGE LENGTH field, NOCNCL bit, ACCESS IDENTIFIER TYPE field, ACCESS IDENTIFIER LENGTH field, and ACCESS
IDENTIFIER field are defined in 8.3.3.2.2.

The Grant All ACE page shall be processed as if it is a Grant/Revoke ACE page (see 8.3.3.2.2) with one
LUACD descriptor for every logical unit managed by the access controls coordinator with the fields in each
LUACD containing:

a) an access mode of 00h (see 8.3.2.2.2.2);

b) a LUN VALUE field whose contents match the contents of the DEFAULT LUN field; and
c) a DEFAULT LUN field whose contents reference the logical unit appropriate to the DLgeneration value
(see 8.3.1.4.4).

852 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

8.3.3.2.4 The Revoke Proxy Token ACE page

The Revoke Proxy Token ACE page (see table 700) is used to revoke one or more proxy tokens (see
8.3.1.6.2).

Table 700 — Revoke Proxy Token ACE page format

Bit
7 6 5 4 3 2 1 0
Byte
0 PAGE CODE (02h)
1 Reserved
2 (MSB)
PAGE LENGTH (n-3)
3 (LSB)
4
•• • PROXY TOKEN 0
11
•
••

n-7
•• • PROXY TOKEN x
n

The PAGE CODE field specifies the type of ACE page that follows (see table 695) and shall be set as shown in
table 700 for the Revoke Proxy Token ACE page.

The PAGE LENGTH field specifies the number of additional bytes present in this ACE page. If the page length is
less than eight or not a multiple of eight, the command shall be terminated with CHECK CONDITION status,
with the sense key set to ILLEGAL REQUEST, and the additional sense set to PARAMETER LIST LENGTH
ERROR.

The PROXY TOKEN field(s) specify the proxy tokens to be revoked. The access controls coordinator shall
revoke each proxy token listed in a PROXY TOKEN field. If the contents of a PROXY TOKEN field do not identify a
valid proxy token, the field shall be ignored and this shall not be considered an error.

Multiple Revoke Proxy Token ACE pages may be included in the parameter data.

Working Draft SCSI Primary Commands - 4 (SPC-4) 853

T10/BSR INCITS 513 Revision 37 17 May 2014

8.3.3.2.5 The Revoke All Proxy Tokens ACE page

The Revoke All Proxy Tokens ACE page (see table 701) is used to revoke all currently valid proxy tokens (see
8.3.1.6.2).

Table 701 — Revoke All Proxy Tokens ACE page format

Bit
7 6 5 4 3 2 1 0
Byte
0 PAGE CODE (03h)
1 Reserved
2 (MSB)
PAGE LENGTH (0000h)
3 (LSB)

The PAGE CODE field specifies the type of ACE page that follows (see table 695) and shall be set as shown in
table 701 for the Revoke All Proxy Tokens ACE page.

Multiple Revoke All Proxy Tokens ACE pages may be included in the parameter data.

8.3.3.3 DISABLE ACCESS CONTROLS service action

The ACCESS CONTROL OUT command with DISABLE ACCESS CONTROLS service action is used to
place the access controls coordinator in the access controls disabled state.

The format of the CDB for the ACCESS CONTROL OUT command with DISABLE ACCESS CONTROLS
service action is shown in table 693 (see 8.3.3.1).

If access controls are disabled or if the PARAMETER LIST LENGTH field in the CDB is set to zero, the access
controls coordinator shall take no action and the command shall be completed with GOOD status.

If the PARAMETER LIST LENGTH field is not set to zero or 12, the command shall be terminated with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
PARAMETER LIST LENGTH ERROR.

If the PARAMETER LIST LENGTH field is set to 12, the parameter list shall have the format shown in table 702.

Table 702 — ACCESS CONTROL OUT with DISABLE ACCESS CONTROLS parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • Reserved
3
4 (MSB)
•• • MANAGEMENT IDENTIFIER KEY
11 (LSB)

If access controls are enabled and the contents of the MANAGEMENT IDENTIFIER KEY field do not match the
current management identifier key (see 8.3.1.8) maintained by the access controls coordinator, then the
access controls coordinator’s states shall not be altered, the command shall be terminated with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to

854 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

ACCESS DENIED - INVALID MGMT ID KEY. This event shall be recorded in the invalid keys portion of the
access controls log (see 8.3.1.10).

In response to an ACCESS CONTROL OUT command with DISABLE ACCESS CONTROLS service action
with correct management identifier key value the access controls coordinator shall:

a) disable access controls;

b) clear the ACL (see 8.3.1.3);
c) place all initiator ports into the not-enrolled state (see 8.3.1.5.1);
d) set the management identifier key to zero (see 8.3.1.8);
e) set the override lockout timer to zero (see 8.3.1.8.2.2);
f) set the initial override lockout timer value to zero (see 8.3.1.8.2.2);
g) clear the access controls log, including resetting the events counters to zero, with the exception of the
key overrides portion of the access controls log (see 8.3.1.10);
h) allow all initiator port’s access to all logical units at their default LUN value;
i) set the DLgeneration counter as defined in 8.3.1.4.4; and
j) establish a unit attention condition for the initiator port associated with every I_T nexus in each logical
unit in the SCSI target device, with the additional sense code set to REPORTED LUNS DATA HAS
CHANGED.

8.3.3.4 ACCESS ID ENROLL service action

The ACCESS ID ENROLL service action of the ACCESS CONTROL OUT command is used by an application
client to enroll an AccessID for an initiator port with the access controls coordinator.

The format of the CDB for the ACCESS CONTROL OUT command with ACCESS ID ENROLL service action
is shown in table 693 (see 8.3.3.1).

If access controls are disabled or if the PARAMETER LIST LENGTH field in the CDB is set to zero, the access
controls coordinator shall take no action and the command shall be completed with GOOD status.

If the PARAMETER LIST LENGTH field is not set to zero or 24, the command shall be terminated with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
PARAMETER LIST LENGTH ERROR.

If the PARAMETER LIST LENGTH field is set to 24, the parameter list shall have the format shown in table 703.

Table 703 — ACCESS CONTROL OUT with ACCESS ID ENROLL parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • ACCESSID
15
16
•• • Reserved
23

The ACCESSID field is described in 8.3.1.13.

Working Draft SCSI Primary Commands - 4 (SPC-4) 855

T10/BSR INCITS 513 Revision 37 17 May 2014

If the initiator port is in the enrolled state or pending-enrolled state (see 8.3.1.5.1) under a specific AccessID
and the ACCESSID field contains a different AccessID, then:

a) the access controls coordinator shall place the initiator port in the pending-enrolled state; and
b) the command shall be terminated with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to ACCESS DENIED - ENROLLMENT
CONFLICT.

If the initiator port is in the enrolled state or pending-enrolled state under a specific AccessID and the
ACCESSID field contains a matching AccessID, then the access controls coordinator shall place the initiator
port in the enrolled state and make no other changes.

If the initiator port is in the not-enrolled state and the ACCESSID field contents do not match the AccessID in
any ACE in the ACL (see 8.3.1.3), then the initiator port shall remain in the not-enrolled state and the
command shall be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to ACCESS DENIED - NO ACCESS RIGHTS.

If the initiator port is in the not-enrolled state and the ACCESSID field contents matches the AccessID in an
ACE in the ACL, then the actions taken depend on whether enrolling the initiator port would create an ACL
LUN conflict (see 8.3.1.5.2). If there is no ACL LUN conflict, the initiator port shall be placed in the enrolled
state (see 8.3.1.5.1.3). If there is an ACL LUN conflict, then the initiator port shall remain in the not-enrolled
state and the command shall be terminated with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to ACCESS DENIED - ACL LUN CONFLICT. This
event shall be recorded in the ACL LUN conflicts portion of the access controls log (see 8.3.1.10).

If a command is terminated with the ACCESS DENIED - ACL LUN CONFLICT additional sense code, the
application client should remove any proxy access rights it has acquired using the ACCESS CONTROL OUT
command with RELEASE PROXY LUN service action and retry the enrollment request. If the ACL LUN
conflict resulted from proxy access, the retried enrollment succeeds. Otherwise, the mechanisms for resolving
ACL LUN conflicts are outside the scope of this standard.

8.3.3.5 CANCEL ENROLLMENT service action

The ACCESS CONTROL OUT command with CANCEL ENROLLMENT service action is used to remove an
initiator port’s enrollment with the access controls coordinator (see 8.3.1.5). Successful completion of this
command changes the state of the initiator port to the not-enrolled state.

The ACCESS CONTROL OUT command with CANCEL ENROLLMENT service action should be used by an
application client prior to any period where use of its accessible logical units may be suspended for a lengthy
period of time (e.g., when a host is preparing to shutdown). This allows the access controls coordinator to free
any resources allocated to manage the enrollment for the initiator port.

The format of the CDB for the ACCESS CONTROL OUT command with CANCEL ENROLLMENT service
action is shown in table 693 (see 8.3.3.1).

If access controls are disabled, the access controls coordinator shall take no action and the command shall be
completed with GOOD status.

There is no parameter data for the ACCESS CONTROL OUT command with CANCEL ENROLLMENT
service action. If the PARAMETER LIST LENGTH field in the CDB is not set to zero, the initiator port’s enrollment
shall not be changed and the command shall be terminated with CHECK CONDITION status, with the sense
key set to ILLEGAL REQUEST, and the additional sense code set to PARAMETER LIST LENGTH ERROR.

856 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

If the PARAMETER LIST LENGTH field in the CDB is set to zero, the initiator port shall be placed in the not-enrolled
state (see 8.3.1.5.1.2) and any subsequent commands addressed to the logical units no longer accessible are
handled according to the requirements stated in 8.3.1.7.

8.3.3.6 CLEAR ACCESS CONTROLS LOG service action

The ACCESS CONTROL OUT command with CLEAR ACCESS CONTROLS LOG service action is used to
instruct the access controls coordinator to reset a specific access control events counter to zero and to clear a
portion of the access controls log (see 8.3.1.10).

The format of the CDB for the ACCESS CONTROL OUT command with CLEAR ACCESS CONTROLS LOG
service action is shown in table 693 (see 8.3.3.1).

If access controls are disabled or if the PARAMETER LIST LENGTH field in the CDB is set to zero, the access
controls coordinator shall take no action and the command shall be completed with GOOD status.

If the PARAMETER LIST LENGTH field is not set to zero or 12, the command shall be terminated with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
PARAMETER LIST LENGTH ERROR.

If the PARAMETER LIST LENGTH field is set to 12, the parameter list shall have the format shown in table 704.

Table 704 — ACCESS CONTROL OUT with CLEAR ACCESS CONTROLS LOG parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0
1 Reserved
2
3 Reserved LOG PORTION

4 (MSB)
•• • MANAGEMENT IDENTIFIER KEY
11 (LSB)

The LOG PORTION field (see table 705) specifies the access controls log portion to be cleared.

Table 705 — CLEAR ACCESS CONTROLS LOG LOG PORTION field

Code Description
00b Reserved
01b Invalid Keys portion
10b ACL LUN Conflicts portion
11b Reserved

If access controls are enabled and the contents of the MANAGEMENT IDENTIFIER KEY field do not match the
current management identifier key (see 8.3.1.8) maintained by the access controls coordinator, then:

a) the access controls coordinator’s states shall not be altered; and

b) the command shall be terminated with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to ACCESS DENIED - INVALID MGMT ID
KEY. This event shall be recorded in the invalid keys portion of the access controls log (see 8.3.1.10).

Working Draft SCSI Primary Commands - 4 (SPC-4) 857

T10/BSR INCITS 513 Revision 37 17 May 2014

In response to an ACCESS CONTROL OUT command with CLEAR ACCESS CONTROLS LOG service
action with correct management identifier key value the access controls coordinator shall perform the
following to clear the portion of the access controls log identified by the LOG PORTION field (see table 705) in
the parameter data:

a) set the events counter for the specified log portion to zero; and
b) if the specified log portion contains log records, remove the log records from the specified log portion.

8.3.3.7 MANAGE OVERRIDE LOCKOUT TIMER service action

The ACCESS CONTROL OUT command with MANAGE OVERRIDE LOCKOUT TIMER service action is
used to manage the override lockout timer (see 8.3.1.8.2.2).

If access controls are disabled, the access controls coordinator shall take no action and the command shall be
completed with GOOD status.

The format of the CDB for the ACCESS CONTROL OUT command with MANAGE OVERRIDE LOCKOUT
TIMER service action is shown in table 693 (see 8.3.3.1).

If the PARAMETER LIST LENGTH field in the CDB is set to zero, the access controls coordinator shall reset the
override lockout timer to the current initial override lockout timer value maintained by the access controls
coordinator.

If the PARAMETER LIST LENGTH field is not set to zero or 12, the command shall be terminated with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
PARAMETER LIST LENGTH ERROR.

If the PARAMETER LIST LENGTH field is set to 12, the parameter list shall have the format shown in table 706.

Table 706 — ACCESS CONTROL OUT command MANAGE OVERRIDE LOCKOUT TIMER service
action parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0
Reserved
1
2 (MSB)
NEW INITIAL OVERRIDE LOCKOUT TIMER
3 (LSB)
4 (MSB)
•• • MANAGEMENT IDENTIFIER KEY
11 (LSB)

The NEW INITIAL OVERRIDE LOCKOUT TIMER field specifies the value that access controls coordinator shall
maintain for initial override lockout timer if the specified management identifier key is correct.

If access controls are enabled and the contents of the MANAGEMENT IDENTIFIER KEY field do not match the
current management identifier key (see 8.3.1.8) maintained by the access controls coordinator, then the
access controls coordinator shall not change the initial override lockout timer value but shall set the override
lockout timer to the unaltered current initial override lockout timer value. The command shall be terminated
with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense
code set to ACCESS DENIED - INVALID MGMT ID KEY. This event shall be recorded in the invalid keys

858 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

portion of the access controls log (see 8.3.1.10).

In response to an ACCESS CONTROL OUT command with MANAGE OVERRIDE LOCKOUT TIMER service
action with correct management identifier key value the access controls coordinator shall:

a) replace the currently saved initial override lockout timer with the value in the NEW INITIAL OVERRIDE
LOCKOUT TIMER field; and
b) set the override lockout timer to the new initial value.

8.3.3.8 OVERRIDE MGMT ID KEY service action

The ACCESS CONTROL OUT command with OVERRIDE MGMT ID KEY service action is used to override
the current management identifier key (see 8.3.1.4.2) maintained by the access controls coordinator. The
ACCESS CONTROL OUT command with OVERRIDE MGMT ID KEY service action should be used in a
failure situation where the application client no longer has access to its copy of the current management
identifier key.

Successful use of the ACCESS CONTROL OUT command with OVERRIDE MGMT ID KEY service action is
constrained by the override lockout timer (see 8.3.1.8.2.2).

The format of the CDB for the ACCESS CONTROL OUT command with OVERRIDE MGMT ID KEY service
action is shown in table 693 (see 8.3.3.1).

If access controls are disabled or if the PARAMETER LIST LENGTH field in the CDB is set to zero, the access
controls coordinator shall take no action and the command shall be completed with GOOD status.

If access controls are enabled, the access controls coordinator shall log every ACCESS CONTROL OUT
command with OVERRIDE MGMT ID KEY service action processed whether successful or not in the access
controls log as defined in 8.3.1.10.

If the PARAMETER LIST LENGTH field is not set to zero or 12, the command shall be terminated with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
PARAMETER LIST LENGTH ERROR.

If the PARAMETER LIST LENGTH field is set to 12, the parameter data shall have the format shown in table 707.

Table 707 — ACCESS CONTROL OUT with OVERRIDE MGMT ID KEY parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • Reserved
3
4 (MSB)
•• • NEW MANAGEMENT IDENTIFIER KEY
11 (LSB)

The NEW MANAGEMENT IDENTIFIER KEY field specifies a new management identifier key.

If the override lockout timer managed by the access controls coordinator is not zero, then:

a) the access controls coordinator’s states shall not be altered; and

Working Draft SCSI Primary Commands - 4 (SPC-4) 859

T10/BSR INCITS 513 Revision 37 17 May 2014

b) the command shall be terminated with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

If the override lockout timer managed by the access controls coordinator is zero, then the access controls
coordinator shall replace the current management identifier key with the value in the to the NEW MANAGEMENT
IDENTIFIER KEY field.

8.3.3.9 REVOKE PROXY TOKEN service action

An application client for an initiator port uses the ACCESS CONTROL OUT command with REVOKE PROXY
TOKEN service action to cancel all proxy access rights to a logical unit that have been granted under the
specified proxy token (see 8.3.1.6.2). If this service action is not supported, the command shall be terminated
with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense
code set to INVALID FIELD IN CDB.

The format of the CDB for the ACCESS CONTROL OUT command with REVOKE PROXY TOKEN service
action is shown in table 693 (see 8.3.3.1).

If access controls are disabled or if the PARAMETER LIST LENGTH field in the CDB is set to zero, the access
controls coordinator shall take no action and the command shall be completed with GOOD status.

If the PARAMETER LIST LENGTH field is not set to zero or eight, the command shall be terminated with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
PARAMETER LIST LENGTH ERROR.

If the PARAMETER LIST LENGTH field is set to eight, the parameter data shall have the format shown in table 708.

Table 708 — ACCESS CONTROL OUT with REVOKE PROXY TOKEN parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • PROXY TOKEN
7

If the PROXY TOKEN field does not contain a valid proxy token previously obtained via the initiator port, no
action is taken by the access controls coordinator. This shall not be considered an error.

If the proxy token is valid, the access controls coordinator shall take the following actions:

a) invalidate the proxy token; and

b) deny access to the associated logical unit by any initiator port whose rights were granted under that
proxy token using an ACCESS CONTROL OUT command with ASSIGN PROXY LUN service action
(see 8.3.3.11) according to the requirements stated in 8.3.1.7.

8.3.3.10 REVOKE ALL PROXY TOKENS service action

An application client for an initiator port uses the ACCESS CONTROL OUT command with REVOKE ALL
PROXY TOKENS service action to cancel all proxy access rights to a specified logical unit that it obtained with
zero or more proxy tokens (see 8.3.1.6.2). If this service action is not supported, the command shall be
terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional
sense code set to INVALID FIELD IN CDB.

860 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

The format of the CDB for the ACCESS CONTROL OUT command with REVOKE ALL PROXY TOKENS
service action is shown in table 693 (see 8.3.3.1).

If access controls are disabled or if the PARAMETER LIST LENGTH field in the CDB is set to zero, the access
controls coordinator shall take no action and the command shall be completed with GOOD status.

If the PARAMETER LIST LENGTH field is not set to zero nor eight, the command shall be terminated with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
PARAMETER LIST LENGTH ERROR.

If the PARAMETER LIST LENGTH field is set to eight, the parameter data shall have the format shown in table 709.

Table 709 — ACCESS CONTROL OUT with REVOKE ALL PROXY TOKENS parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • LUN VALUE
7

If the LUN in the LUN VALUE field is not associated to a logical unit to which the requesting initiator port has
non-proxy access rights based on the contents of an ACE (see 8.3.1.3) or if the LUN value is based on a
proxy token (see 8.3.1.6.2), then no further action is taken by the access controls coordinator. This shall not
be considered an error.

If the LUN value is associated to a logical unit to which the requesting initiator port has non-proxy access
rights, then the access controls coordinator shall:

a) invalidate all proxy tokens for the initiator port for the logical unit specified by the LUN VALUE field;
b) deny access to that logical unit by any initiator port whose rights were granted under any of the
invalidated proxy tokens via an ACCESS CONTROL OUT command with ASSIGN PROXY LUN
service action (see 8.3.3.11) according to the requirements stated in 8.3.1.7.

8.3.3.11 ASSIGN PROXY LUN service action

The ACCESS CONTROL OUT command with ASSIGN PROXY LUN service action is used to request access
to a logical unit under the rights of a proxy token (see 8.3.1.6.2) and to assign that logical unit a particular LUN
value for addressing by the requesting initiator port. If this service action is not supported, the command shall
be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the
additional sense code set to INVALID FIELD IN CDB.

The format of the CDB for the ACCESS CONTROL OUT command with ASSIGN PROXY LUN service action
is shown in table 693 (see 8.3.3.1).

If the PARAMETER LIST LENGTH field in the CDB is set to zero, the access controls coordinator shall take no
action and the command shall be completed with GOOD status.

If the PARAMETER LIST LENGTH field is not set to zero nor 16, the command shall be terminated with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
PARAMETER LIST LENGTH ERROR.

Working Draft SCSI Primary Commands - 4 (SPC-4) 861

T10/BSR INCITS 513 Revision 37 17 May 2014

If the PARAMETER LIST LENGTH field is set to 16, the parameter data shall have the format shown in table 710.

Table 710 — ACCESS CONTROL OUT with ASSIGN PROXY LUN parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • PROXY TOKEN
7
8
•• • LUN VALUE
15

The PROXY TOKEN field contains a proxy token. If the contents of the PROXY TOKEN field are not valid, then the
command shall be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to ACCESS DENIED - INVALID PROXY TOKEN.

NOTE 69 - If access controls are disabled, there are no valid proxy tokens and the device server always
responds with the specified error information. This differs from the behavior of many other ACCESS
CONTROL OUT service actions where the response is GOOD status while access controls are disabled. The
difference in behavior is intended to inform the application client that its request for the new LUN assignment
failed.

The LUN VALUE field specifies the LUN value the application client intends to use while accessing the logical
unit described by the proxy token.

If the proxy token is valid but the access controls coordinator is unable to assign the requested LUN value to
the associated logical unit (e.g., the LUN value already is associated with a logical unit for the initiator port, or
the LUN value is not a supported logical unit address), then:

a) access rights shall not be granted; and

b) the command shall be terminated with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to ACCESS DENIED - INVALID LU
IDENTIFIER, and the sense key specific information shall be set as described for the ILLEGAL
REQUEST sense key in 4.5.2.4.2.

The access controls coordinator should determine a suggested LUN value that is unlikely to produce an error
while also minimizing the absolute value of the difference of the erroneous default LUN value and the
suggested LUN value. If a suggested LUN value is determined, the first four bytes of the suggested LUN value
shall be returned in the INFORMATION field (see 4.5.4) and the last four bytes shall be returned in the
COMMAND-SPECIFIC INFORMATION field (see 4.5.5) the sense data.

If the proxy token is valid but the access controls coordinator has insufficient resources to manage proxy
logical unit access, then the command shall be terminated with CHECK CONDITION status, with the sense
key set to ILLEGAL REQUEST, and the additional sense code set to INSUFFICIENT ACCESS CONTROL
RESOURCES.

If the proxy token is valid and the access controls coordinator has sufficient resources, the initiator port shall
be allowed proxy access to the referenced logical unit at the specified LUN value.

862 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

8.3.3.12 RELEASE PROXY LUN service action

The ACCESS CONTROL OUT command with RELEASE PROXY LUN service action is used to release proxy
access to a logical unit created with a proxy token (see 8.3.1.6.2) and the ACCESS CONTROL OUT
command with ASSIGN PROXY LUN service action (see 8.3.3.11). If this service action is not supported, the
command shall be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL
REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

The ACCESS CONTROL OUT command with RELEASE PROXY LUN service action should be used if an
application client no longer requires the logical unit access rights granted to an initiator port under a proxy
token (e.g., when a copy manager has completed a specific third party copy operation under a proxy token) to
allow the access controls coordinator to free any resources allocated to manage the proxy access.

The format of the CDB for the ACCESS CONTROL OUT command with RELEASE PROXY LUN service
action is shown in table 693 (see 8.3.3.1).

If the PARAMETER LIST LENGTH field in the CDB is set to zero, the access controls coordinator shall take no
action and the command shall be completed with GOOD status.

If the PARAMETER LIST LENGTH field is not set to zero nor eight, the command shall be terminated with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
PARAMETER LIST LENGTH ERROR.

If the PARAMETER LIST LENGTH field is set to eight, the parameter data shall have the format shown in table 711.

Table 711 — ACCESS CONTROL OUT with RELEASE PROXY LUN parameter data format

Bit
7 6 5 4 3 2 1 0
Byte
0
•• • LUN VALUE
7

The LUN VALUE field specifies a LUN value that was associated with a logical unit based on a proxy token
using an ACCESS CONTROL OUT command with ASSIGN PROXY LUN service action. If the LUN value
was not assigned to a logical unit by an ACCESS CONTROL OUT command with ASSIGN PROXY LUN
service action, then the command shall be terminated with CHECK CONDITION status, with the sense key
set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.

NOTE 70 - If access controls are disabled, there are no valid proxy tokens or associated LUN values
available for assignment to a logical unit by an ACCESS CONTROL OUT command with ASSIGN PROXY
LUN service action. As a result, the device server responds with the specified error information. This differs
from the behavior of many other ACCESS CONTROL OUT service actions where the response is GOOD
status while access controls are disabled. The difference in behavior is intended to inform the application
client that the LUN value remains as a valid address for the logical unit.

If the LUN value was assigned to a logical unit by an ACCESS CONTROL OUT command with ASSIGN
PROXY LUN service action, then the access controls coordinator shall not allow access to the logical unit at
the specified LUN value.

Working Draft SCSI Primary Commands - 4 (SPC-4) 863

T10/BSR INCITS 513 Revision 37 17 May 2014

8.4 TARGET LOG PAGES well known logical unit

The TARGET LOG PAGES well known logical unit shall only process the commands listed in table 712. If a
command is received by the TARGET LOG PAGES well know logical unit that is not listed in table 712, then
the device server shall terminate the command with CHECK CONDITION status, with the sense key set to
ILLEGAL REQUEST, and the additional sense code set to INVALID COMMAND OPERATION CODE.

Table 712 — Commands for the TARGET LOG PAGES well known logical unit

Operation
Command code Support Reference
INQUIRY 12h M 6.6
LOG SELECT 4Ch M 6.7
LOG SENSE 4Dh M 6.8
REQUEST SENSE 03h M 6.39
TEST UNIT READY 00h M 6.43
Key:
M = Command implementation is mandatory.

The TARGET LOG PAGES well known logical unit shall support the Protocol Specific Port log page (see
7.3.14) and may support other log pages with parameters that apply to the SCSI target device.

8.5 SECURITY PROTOCOL well known logical unit

The SECURITY PROTOCOL well known logical unit shall only process the commands listed in table 713. If a
command is received by the SECURITY PROTOCOL well known logical unit that is not listed in table 713,
then the device server shall terminate the command with CHECK CONDITION status, with the sense key set
to ILLEGAL REQUEST, and the additional sense code set to INVALID COMMAND OPERATION CODE.

Table 713 — Commands for the SECURITY PROTOCOL well known logical unit

Operation
Command code Support Reference
INQUIRY 12h M 6.6
REQUEST SENSE 03h M 6.39
SECURITY PROTOCOL IN A2h M 6.40
SECURITY PROTOCOL OUT B5h M 6.41
TEST UNIT READY 00h M 6.47
Key:
M = Command implementation is mandatory.

8.6 MANAGEMENT PROTOCOL well known logical unit

The MANAGEMENT PROTOCOL well known logical unit shall only process the commands listed in table 714.
If a command is received by the MANAGEMENT PROTOCOL well known logical unit that is not listed in table

864 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

714, then the device server shall terminate the command with CHECK CONDITION status, with the sense key
set to ILLEGAL REQUEST, and the additional sense code set to INVALID COMMAND OPERATION CODE.

Table 714 — Commands for the MANAGEMENT PROTOCOL well known logical unit

Operation
Command code Support Reference
INQUIRY 12h M 6.6
MANAGEMENT PROTOCOL IN A3h/10h a M 6.9
MANAGEMENT PROTOCOL OUT A4h/10h a M 6.10
REQUEST SENSE 03h M 6.39
TEST UNIT READY 00h M 6.47
Key:
M = Command implementation is mandatory.
a
This command is defined by a combination of operation code and service action. The
operation code value is shown preceding the slash and the service action value is shown
after the slash.

Working Draft SCSI Primary Commands - 4 (SPC-4) 865

T10/BSR INCITS 513 Revision 37 17 May 2014

9 Security manager command set

A security manager (see 5.13.6.7.2) shall only process the commands listed in table 715. If a command is
received by the security manager that is not listed in table 715, the device server shall terminate the command
with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense
code set to INVALID COMMAND OPERATION CODE.

Table 715 — Commands for a security manager

Operation
Command code Support Reference
INQUIRY 12h M 6.6
a
RECEIVE CREDENTIAL 7Fh/1800 M 6.26
REPORT LUNS A0h M 6.33
REQUEST SENSE 03h M 6.39
SECURITY PROTOCOL IN A2h M 6.40
SECURITY PROTOCOL OUT B5h M 6.41
TEST UNIT READY 00h M 6.47
Key:
M = Command implementation is mandatory.
a
This command is defined by a combination of operation code and service action. The operation code
value is shown preceding the slash and the service action value is shown after the slash.

866 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Annex A
(Informative)

Terminology mapping

Table A.1 lists changes in terminology between SPC-2 and this standard.

Table A.1 — This standard to SPC-2 terminology mapping

Equivalent term in this standard SPC-2 term

initiator port identifier initiator identifier
queue task set
command task
command identifier task tag
SCSI initiator port initiator
SCSI port port
target port identifier or
device identifier
initiator port identifier
target port identifier or
SCSI identifier
initiator port identifier
SCSI target port target
target port identifier target identifier

Working Draft SCSI Primary Commands - 4 (SPC-4) 867

T10/BSR INCITS 513 Revision 37 17 May 2014

Annex B
(Informative)

REPORT LUNS command examples

This annex contains examples of logical unit inventory reporting. For the examples in this annex, a logical unit
inventory of the 11 LUNs shown in table B.1 is assumed.

Table B.1 — Example logical unit inventory

Logical
unit LU_CONG
name LUN bit Description
A 0000 0000 0000 0000h 0 LUN 0
B 0001 0000 0000 0000h 0 Single level peripheral device addressing LUN
C D201 0020 0000 0000h 0 Single level extended flat space addressing LUN
D 0130 0000 0000 0000h 1 Administrative logical unit contained in a logical unit
conglomerate
E 0180 0000 0000 0000h 1 Administrative logical unit contained in a logical unit
conglomerate
F 0180 0001 0000 0000h 1 Subsidiary logical unit contained in the logical unit
conglomerate for which logical unit E is the adminis-
trative logical unit.
G 0180 0180 0000 0000h 1 Subsidiary logical unit contained in the logical unit
conglomerate for which logical unit E is the adminis-
trative logical unit.
J 0181 0000 0000 0000h 1 Administrative logical unit contained in a logical unit
conglomerate
K 0181 017F 0000 0000h 1 Subsidiary logical unit contained in the logical unit
conglomerate for which logical unit J is the adminis-
trative logical unit.
L 0181 0180 0000 0000h 1 Subsidiary logical unit contained in the logical unit
conglomerate for which logical unit J is the adminis-
trative logical unit.
N C105 0000 0000 0000h 0 MANAGEMENT PROTOCOL well-known logical unit
at level 1
a The LU_CONG bit is described in the standard INQUIRY data (see 6.6.2).

868 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Figure B.1 shows a representation of these example logical units.

A
D J K L

B
N
E F G

Key:

 Single level logical unit Logical unit conglomerate

 Administrative logical unit  Subsidiary logical unit

Figure B.1 — Example logical unit representation

Table A.2 shows the returned LUN list returned by a REPORT LUNS command (see 6.33) for various select
report types when addressed to various logical unit numbers.

Table B.2 — REPORT LUNS command returned LUN list (part 1 of 3)

SELECT Logical unit list returned

Logical unit to which REPORT
a
command is addressed field Name Number
A 0000 0000 0000 0000h
B 0001 0000 0000 0000h
C D201 0020 0000 0000h
D 0130 0000 0000 0000h
E 0180 0000 0000 0000h
A b 0000 0000 0000 0000h 00h
F 0180 0001 0000 0000h
G 0180 0180 0000 0000h
J 0181 0000 0000 0000h
K 0181 017F 0000 0000h
L 0181 0180 0000 0000h
a The SELECT REPORT field is described in the REPORT LUNS command (see 6.33).
b Commands addressed to the REPORT LUNS well-known logical unit (i.e. C101
0000 0000 0000h), if supported, return the same logical unit number list returned
by commands addressed to LUN 0 (i.e., logical unit A).

Working Draft SCSI Primary Commands - 4 (SPC-4) 869

T10/BSR INCITS 513 Revision 37 17 May 2014

Table B.2 — REPORT LUNS command returned LUN list (part 2 of 3)

SELECT Logical unit list returned

Logical unit to which REPORT
a
command is addressed field Name Number
A b 0000 0000 0000 0000h 01h N C105 0000 0000 0000h
A 0000 0000 0000 0000h
B 0001 0000 0000 0000h
C D201 0020 0000 0000h
D 0130 0000 0000 0000h
E 0180 0000 0000 0000h
b
A 0000 0000 0000 0000h 02h F 0180 0001 0000 0000h
G 0180 0180 0000 0000h
J 0181 0000 0000 0000h
K 0181 017F 0000 0000h
L 0181 0180 0000 0000h
N C105 0000 0000 0000h
D 0130 0000 0000 0000h
b
A 0000 0000 0000 0000h 10h E 0180 0000 0000 0000h
J 0181 0000 0000 0000h
A 0000 0000 0000 0000h
B 0001 0000 0000 0000h
C D201 0020 0000 0000h
A b 0000 0000 0000 0000h 11h
D 0130 0000 0000 0000h
E 0180 0000 0000 0000h
J 0181 0000 0000 0000h
b
A 0000 0000 0000 0000h 12h null
B 0001 0000 0000 0000h 00h to 02h Vendor specific
B 0001 0000 0000 0000h 10h to 12h null
E 0180 0000 0000 0000h 00h to 02h Vendor specific
E 0180 0000 0000 0000h 10h to 11h null
E 0180 0000 0000 0000h
E 0180 0000 0000 0000h 12h F 0180 0001 0000 0000h
G 0180 0180 0000 0000h
a
The SELECT REPORT field is described in the REPORT LUNS command (see 6.33).
b
Commands addressed to the REPORT LUNS well-known logical unit (i.e. C101
0000 0000 0000h), if supported, return the same logical unit number list returned
by commands addressed to LUN 0 (i.e., logical unit A).

870 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table B.2 — REPORT LUNS command returned LUN list (part 3 of 3)

SELECT Logical unit list returned

Logical unit to which REPORT
a
command is addressed field Name Number
F 0180 0001 0000 0000h 10h to 12h null
G 0180 0180 0000 0000h 10h to 12h null
J 0181 0000 0000 0000h 10h to 11h null
J 0181 0000 0000 0000h
J 0181 0000 0000 0000h 12h K 0181 017F 0000 0000h
L 0181 0180 0000 0000h
K 0181 017F 0000 0000h 10h to 12h null
L 0181 0180 0000 0000h 10h to 12h null
a
The SELECT REPORT field is described in the REPORT LUNS command (see 6.33).
b
Commands addressed to the REPORT LUNS well-known logical unit (i.e. C101
0000 0000 0000h), if supported, return the same logical unit number list returned
by commands addressed to LUN 0 (i.e., logical unit A).

Working Draft SCSI Primary Commands - 4 (SPC-4) 871

T10/BSR INCITS 513 Revision 37 17 May 2014

Annex C
(Informative)

Replacing RESERVE/RELEASE functionality with PERSISTENT RESERVE

IN/OUT equivalents

C.1 Introduction

This annex specifies the PERSISTENT RESERVE OUT command features necessary to replace the
reserve/release management method (see SPC-2) and provides guidance on how to perform a third party
reservation using persistent reservations. The PERSISTENT RESERVE IN command is not used to replace
any feature of the reserve/release management method.

C.2 Replacing the reserve/release method with the PERSISTENT RESERVE OUT
COMMAND

The minimum PERSISTENT RESERVE OUT command (see 6.16) features necessary to replace the
reserve/release management method (see SPC-2) are shown in table C.1.

Table C.1 — PERSISTENT RESERVE OUT command features

PERSISTENT RESERVE OUT command features Replaces

reserve/release
REGISTER Yes a
RESERVE Yes
RELEASE Yes
Service CLEAR Yes b
action PREEMPT No
PREEMPT AND ABORT No
REGISTER AND IGNORE EXISTING KEY Yes a
REGISTER AND MOVE Yes c
Scope LU_SCOPE Yes
Write Exclusive No
Exclusive Access Yes
Write Exclusive – Registrants Only No
Type
Exclusive Access – Registrants Only No
Write Exclusive – All Registrants No
Exclusive Access – All Registrants No
a
An implementation uses either the REGISTER service action or REGISTER
AND IGNORE EXISTING KEY service action.
b
Necessary to clear the registration and reservation (e.g, a failed initiator).
c Necessary only for third party reservations.

872 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

C.3 Third party reservations

For some uses of the EXTENDED COPY(LID4) command (see 6.4) and EXTENDED COPY(LID1) command
(see 6.5), the application client performs a locking function to maintain data integrity on the source and may
also lock the destination device prior to starting the copy operation. The persistent reservation management
method may be used to perform the locking function. Other methods (e.g., access controls (see 8.3)) may
also perform the locking function.

To accomplish a third party persistent reservation the following steps are recommended:

1) the application client uses the REGISTER service action to register an I_T nexus with a logical unit
(e.g., a tape drive logical unit);
2) the application client uses the RESERVE service action to establish a persistent reservation with the
Exclusive Access type;
3) the application client prepares the logical unit for access (e.g., medium is loaded and positioned);
4) the application client uses the REGISTER AND MOVE service action to register the I_T nexus that
the copy manager is expected to use and to move the persistent reservation to that I_T nexus;
5) the application client sends the EXTENDED COPY command to the copy manager that includes a
third party persistent reservations source I_T nexus segment descriptor (see 6.4.6.18);
6) copy manager processes all segment descriptors in the received EXTENDED COPY command
except the third party persistent reservations source I_T nexus segment descriptor; and
7) the copy manager issues a REGISTER AND MOVE service action, using the reservation key and I_T
nexus specified in the third party persistent reservations source I_T nexus segment descriptor sent by
the application client (see step 5), to move the persistent reservation back to the original I_T nexus.

Working Draft SCSI Primary Commands - 4 (SPC-4) 873

T10/BSR INCITS 513 Revision 37 17 May 2014

Annex D
(Informative)

Third-party copy implementation and usage

D.1 Embedded and dedicated copy manager implementations

D.1.1 Overview

Although a copy manager is always contained in a logical unit, the logical unit may:

a) have a function (e.g., providing access to a block storage device) in addition to the copy manager
function (i.e., the copy manager is embedded (see D.1.2) in another device type); or
b) be dedicated to providing the copy manager function (i.e., the copy manager is contained in a
dedicated (see D.1.3) logical unit).

In both implementations:

a) the device server processes commands (e.g., the INQUIRY command) that are not third-party copy
commands (see 5.16.3), and the copy manager processes third-party copy commands; and
b) the standard INQUIRY data (see 6.6.2) indicates a logical unit that is accessible, and has a defined
device type.

D.1.2 Embedded copy manager implementations

The device type indicated by the standard INQUIRY data (see 6.6.2) for an embedded copy manager is the
device type appropriate to the device in which the copy manager is embedded.

In addition to whatever copy manager commands are supported, the commands associated with the device
type (e.g., reads and writes) are supported and processed by the device server.

The copy manager is able to support and translate the FFFFh CSCD descriptor ID value (i.e., this logical unit)
shown in table 150 (see 6.4.6.1) to the logical unit and device type in which the copy manager is embedded.

D.1.3 Dedicated copy manager implementations

The device type indicated by the standard INQUIRY data (see 6.6.2) for a dedicated copy manager is not
constrained by other uses of the logical unit. Any defined device type may be indicated in standard INQUIRY
data. One device type often used by dedicated copy managers is the processor device type (see SPC-2).

Very few commands beyond the commands those that table 120 shows to be mandatory for all device types
(see 6.1) are supported by the logical unit for a dedicated copy manager.

In most cases, a dedicated copy manager is not able to support and translate the FFFFh CSCD descriptor ID
value (i.e., this logical unit) shown in table 150 (see 6.4.6.1).

874 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

D.2 Tracking copy operation progress

D.2.1 Overview

The following third-party copy commands provide information that tracks the progress of a copy operation:

a) the RECEIVE COPY STATUS(LID4) command (see 6.24);

b) the RECEIVE COPY DATA(LID4) command (see 6.20); and
c) the RECEIVE ROD TOKEN INFORMATION command (see 6.28).

D.2.2 Detecting lack of progress in active copy operations

Although there is way to determine the progress of an individual data transfer command performed by the
copy manager (e.g., in response to the contents of a segment descriptor (see 5.16.7)), the OPERATION
COUNTER field in the parameter data for all the commands listed in D.2.1 allows the determination of progress
for an active copy operation as follows:

a) each time the copy operation completes processing on a data transfer command that moves data the
OPERATION COUNTER field is incremented;
b) this continues as long as the copy manager is able to move data;
c) if the OPERATION COUNTER field reaches the maximum value allowed in the field, the value wraps to
zero and the OPERATION COUNTER field continues to be incremented as described in a); and
d) if the copy manager stops being able to move data, the value in the OPERATION COUNTER field should
stop changing.

Working Draft SCSI Primary Commands - 4 (SPC-4) 875

T10/BSR INCITS 513 Revision 37 17 May 2014

Annex E
(Informative)

Variations between this standard and equivalent security protocols

E.1 IKEv2 protocol details and variations for IKEv2-SCSI

The IKEv2 protocol details and variations defined in RFC 4306 apply to IKEv2-SCSI (i.e., this standard) as
follows:

a) any SECURITY PROTOCOL OUT command with a transfer length of up to 16 384 bytes is not
terminated with an error due to the number of bytes transferred;
b) the timeout and retransmission mechanisms defined in RFC 4306 are not used by this standard,
instead a new payload is defined to transfer appropriate timeout values to the device server;
c) each SCSI command used by this standard completes by conveying a status from the device server
to the application client;
d) the IKEv2 header EXCHANGE TYPE field is reserved in this standard as a result of equivalent
information being transferred in the SECURITY PROTOCOL OUT command and SECURITY
PROTOCOL IN command CDBs;
e) the IKEv2 header VERSION bit is reserved in this standard;
f) this standard uses the Notify payload (see 7.7.3.5.9) only to provide initial contact information;
g) this standard uses the pseudo-random functions defined by RFC 4306;
h) the key derivation functions defined and used by this standard (see 5.13.3) are equivalent to the
PRF+ found in RFC 4306;
i) the SA creation transactions defined by this standard are not overlapped. If an application client
attempts to start a second SA creation transaction before the first is completed, then the offending
command is terminated as described in 5.13.4.1, but this does not affect the SA creation transaction
that is already in progress;
j) the NO_PROPOSAL_CHOSEN notify error type and INVALID_KE_PAYLOAD notify error type are
replaced by the SA CREATION PARAMETER VALUE INVALID additional sense code (see 7.7.3.9)
because IKEv2-SCSI has a different negotiation structure. As defined in RFC 4306, an IKEv2 initiator
offers one or more proposals to a responder without knowing what is acceptable to the responder, and
chooses a DH group without knowing whether it is acceptable to the responder. These two notify error
types allow the responder to inform the initiator that one or more of its choices are not acceptable. In
contrast, an IKEv2-SCSI application client obtains the device server capabilities in the Device
Capabilities step (see 5.13.4.5) and selects algorithms from them in the Key Exchange step (see
5.13.4.6). An error only occurs if the application client has made an invalid selection, the response to
which includes the SA CREATION PARAMETER VALUE INVALID additional sense code;
k) IKEv2 version numbers (see RFC 4306) are used by this standard (see 7.7.3.4), but the ability to
respond to an unsupported version number with the highest version number to be used is not
supported, and this standard does not include checks for version downgrade attacks;
l) IKEv2 cookies (see RFC 4306) are not used by this standard;
m) IKEv2 cryptographic algorithm negotiation (see RFC 4306) is replaced by the Device Server
Capabilities step (see 5.13.4.5) and the Key Exchange step (see 5.13.4.6) (i.e., the IKEv2 proposal
construct is not used by this standard);
n) in this standard an SA is rekeyed by replacing it with a new SA:
A) CHILD_SAs are not used by this standard;
B) the RFC 4306 discussion of CHILD_SAs does not apply to this standard;
C) coexistence of the original SA and the new SA is achieved for rekeying purposes by restricting the
device server's ability to delete SAs to the following cases:
a) expiration of a timeout (see 7.7.3.5.15);
b) processing of an IKEv2-SCSI Delete function (see 5.13.4.11); and
c) responding to an initial contact notification (see 7.7.3.5.9);

876 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

and
D) IKEv2 does not support rekeying notification for IKE_SAs, therefore this standard does not
support rekeying notification;
o) the choice of authentication methods for both transfer directions is negotiated using the
SA_AUTH_OUT IKEv2-SCSI cryptographic algorithm descriptor and SA_AUTH_IN IKEv2-SCSI
cryptographic algorithm descriptor (see 7.7.3.6.6) during the Key Exchange step (see 5.13.4.6);
p) the usage of Certificate Encodings in the Certificate payload (see 7.7.3.5.5) and Certificate Request
payload (see 7.7.3.5.6) are constrained as follows:
A) in accordance with the recommendations in RFC 4718, Certificate Encoding values 01h-03h and
05h-0Ah are prohibited;
B) this standard forbids the use of URL-based Certificate Encodings (i.e., Certificate Encodings
values 0Ch and 0Dh); and
C) certificate Encoding values that RFC 4306 defines as vendor specific are reserved in this
standard;
q) deleting an SA requires knowing the SAIs (i.e., SPIs) in both directions and including both SAIs in the
Delete payload. The RFC 4306 description of the Delete payload is vague enough to allow this. The
requirement is consistent with the SCSI model for SAs;
r) the Vendor ID payload is not used by this standard;
s) Traffic Selectors (see RFC 4306) are not used by this standard;
t) the requirements in RFC 4306 on nonces are be followed for the random nonces defined by this
standard;
u) the RFC 4306 requirements on address and port agility are specific to the user datagram protocol and
the IP protocol and do not apply to this standard;
v) keys for the Authentication step are generated as defined in RFC 4306;
w) this standard uses a slightly modified version of the authentication calculations in RFC 4306 (see
7.7.3.5.7);
x) the RFC 4306 sections that describe the following features are not used by this standard:
A) extensible authentication protocol methods;
B) generating keying Material for CHILD_SAs;
C) rekeying an IKE SA using CREATE_CHILD_SA;
D) requesting an internal address;
E) requesting the peer's version;
F) IPComp;
G) NAT traversal; and
H) explicit congestion notification;
y) IKEv2 Error Handling (see RFC 4306) is replaced by the use of CHECK CONDITION status and
sense data by this standard. See 7.7.3.9 for details of how errors reported in the Notify payload are
translated to sense data;
z) IETF standards omit the Integrity transform instead of using AUTH_COMBINED;
aa) the command-response architecture of SCSI makes it difficult to protect the device server against
denial of service attacks, and no such protection is defined by this standard. Protection against denial
of service attacks against the application client is described in 7.7.3.8;
ab) IKEv2-SCSI requires Encrypted Payloads be padded to at least the 4 byte minimum alignment
required by ESP-SCSI, whereas IKEv2 imposes no such requirement;
ac) the critical (CRIT) bit is set to one in all IKEv2-SCSI payloads defined in this standard and these
payloads are required to be recognized by all IKEv2-SCSI implementations. RFC 4306 sets the
Critical (C) bit to zero in all IKEv2 payloads defined in RFC 4306, and requires that all IKEv2
implementations recognize all payloads defined in RFC 4306; and
ad) use of the Identification payloads is required by IKEv2-SCSI, whereas IKEv2 allows the Identification
payloads to be omitted.

Working Draft SCSI Primary Commands - 4 (SPC-4) 877

T10/BSR INCITS 513 Revision 37 17 May 2014

Where this standard uses IKE payload names (see 7.7.3.4) RFC 4306 uses the shorthand notation shown in
table E.1.

Table E.1 — IKE payload names shorthand

IKE payload name in this standard a RFC 4306 shorthand b

Security Association SAi or SAr
Key Exchange KEi or KEr
Identification – Application Client IDi
Identification – Device Server IDr
Certificate CERTi or CERTr
Certificate Request CERTREQi
Authentication AUTHi or AUTHr
Nonce NONCEi or NONCEr
Notify N-ICi or N-ICr
Delete Di
Vendor ID Vi or Vr
Traffic Selector – Application Client TSi
Traffic Selector – Device Server TSr
Encrypted Ei or Er
Configuration CPi or CPr
Extensible Authentication EAPi or EAPr
a To facilitate future enhancements, all IKE payloads are listed in this table, but
not all entries in this table are used in this standard.
b
In RFC 4306 the lowercase i indicates initiator and r indicates responder. In this
standard, the initiator is the application client and all such IKE payloads (e.g.,
KEi) appear in a SECURITY PROTOCOL OUT parameter list. The responder is
always the device server in this standard and all such IKE payloads (e.g.,
AUTHr) appear in SECURITY PROTOCOL IN parameter data.

878 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

E.2 ESP protocol details and variations for ESP-SCSI

The IKEv2 protocol details and variations defined in RFC 4303 apply to ESP-SCSI (i.e., this standard) as
follows:

a) this standard requires an integrity check value (e.g., INTEGRITY CHECK VALUE fields), whereas ESP
allows support of confidentiality-only;
b) this standard does not support traffic flow confidentiality;
c) this standard does not support the TCP/IP aspects of ESP (e.g., IP addresses, multicast);
d) this standard requires anti-replay detection using the sequence number, whereas ESP makes this
optional;
e) this standard does not support the Next Header field, but does reserve space for it in the MUST BE
ZERO field (see table 94 in 5.13.7.3);
f) this standard requires verification of the padding bytes, when possible;
g) there is no provision in this standard for generating "dummy packets"; and
h) this standard does not support out-of-order parameter data.

Working Draft SCSI Primary Commands - 4 (SPC-4) 879

T10/BSR INCITS 513 Revision 37 17 May 2014

Annex F
(Informative)

Numeric order codes

F.1 Numeric order codes introduction

This annex contains SCSI additional sense codes, operation codes, diagnostic page codes, log page codes,
mode page codes, VPD page codes, version descriptor values, and T10 IEEE binary identifiers in numeric
order as a reference. In the event of a conflict with between the codes or usage requirements in this annex
and equivalent information in the body of this standard or in any command standard, the normative codes and
usage information is correct.

The information in this annex was complete and accurate at the time of publication. However, the information
is subject to change. Technical Committee T10 of INCITS maintains an electronic copy of this information on
its world wide web site (http://www.t10.org/). In the event that the T10 world wide web site is no longer active,
access may be possible via the INCITS world wide web site (http://www.incits.org), the ANSI world wide web
site (http://www.ansi.org), the IEC site (http://www.iec.ch/), the ISO site (http://www.iso.ch/), or the ISO/IEC
JTC 1 web site (http://www.jtc1.org/).

F.2 Additional sense codes

Table F.1 is a numerical order listing of the additional sense codes (i.e., the ADDITIONAL SENSE CODE field and
ADDITIONAL SENSE CODE QUALIFIER field values returned in sense data).

Table F.1 — ASC and ASCQ assignments (part 1 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
00h 00h DT L P WROM AE B KV F NO ADDITIONAL SENSE INFORMATION
00h 01h T FILEMARK DETECTED
00h 02h T END-OF-PARTITION/MEDIUM DETECTED
00h 03h T SETMARK DETECTED
00h 04h T BEGINNING-OF-PARTITION/MEDIUM DETECTED
00h 05h TL END-OF-DATA DETECTED
00h 06h DT L P WROM AE B KV F I/O PROCESS TERMINATED
00h 07h T PROGRAMMABLE EARLY WARNING DETECTED
00h 11h R AUDIO PLAY OPERATION IN PROGRESS
00h 12h R AUDIO PLAY OPERATION PAUSED
00h 13h R AUDIO PLAY OPERATION SUCCESSFULLY COMPLETED
00h 14h R AUDIO PLAY OPERATION STOPPED DUE TO ERROR

880 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.1 — ASC and ASCQ assignments (part 2 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
00h 15h R NO CURRENT AUDIO STATUS TO RETURN
00h 16h DT L P WROM AE B KV F OPERATION IN PROGRESS
00h 17h DT L WROM AE B KV F CLEANING REQUESTED
00h 18h T ERASE OPERATION IN PROGRESS
00h 19h T LOCATE OPERATION IN PROGRESS
00h 1Ah T REWIND OPERATION IN PROGRESS
00h 1Bh T SET CAPACITY OPERATION IN PROGRESS
00h 1Ch T VERIFY OPERATION IN PROGRESS
00h 1Dh DT B ATA PASS THROUGH INFORMATION AVAILABLE
00h 1Eh DT R M AE B KV CONFLICTING SA CREATION REQUEST
00h 1Fh DT B LOGICAL UNIT TRANSITIONING TO ANOTHER POWER CONDITION
00h 20h DT P B EXTENDED COPY INFORMATION AVAILABLE
00h 21h D ATOMIC COMMAND ABORTED DUE TO ACA
01h 00h D W O BK NO INDEX/SECTOR SIGNAL
02h 00h D WRO BK NO SEEK COMPLETE
03h 00h DT L W O BK PERIPHERAL DEVICE WRITE FAULT
03h 01h T NO WRITE CURRENT
03h 02h T EXCESSIVE WRITE ERRORS
04h 00h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE
04h 01h DT L P WROM AE B KV F LOGICAL UNIT IS IN PROCESS OF BECOMING READY
04h 02h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, INITIALIZING COMMAND REQUIRED
04h 03h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED
04h 04h DT L RO B LOGICAL UNIT NOT READY, FORMAT IN PROGRESS
04h 05h DT W O A B K F LOGICAL UNIT NOT READY, REBUILD IN PROGRESS
04h 06h DT W O A BK LOGICAL UNIT NOT READY, RECALCULATION IN PROGRESS
04h 07h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, OPERATION IN PROGRESS
04h 08h R LOGICAL UNIT NOT READY, LONG WRITE IN PROGRESS
04h 09h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, SELF-TEST IN PROGRESS
LOGICAL UNIT NOT ACCESSIBLE, ASYMMETRIC ACCESS STATE
04h 0Ah DT L P WROM AE B KV F
TRANSITION
04h 0Bh DT L P WROM AE B KV F LOGICAL UNIT NOT ACCESSIBLE, TARGET PORT IN STANDBY STATE
LOGICAL UNIT NOT ACCESSIBLE, TARGET PORT IN UNAVAILABLE
04h 0Ch DT L P WROM AE B KV F
STATE
04h 0Dh F LOGICAL UNIT NOT READY, STRUCTURE CHECK REQUIRED
04h 0Eh DT R M AE B KV F LOGICAL UNIT NOT READY, SECURITY SESSION IN PROGRESS
04h 10h DT WROM B LOGICAL UNIT NOT READY, AUXILIARY MEMORY NOT ACCESSIBLE
04h 11h DT WRO AE B V F LOGICAL UNIT NOT READY, NOTIFY (ENABLE SPINUP) REQUIRED
04h 12h M V LOGICAL UNIT NOT READY, OFFLINE
04h 13h DT R M AE B KV LOGICAL UNIT NOT READY, SA CREATION IN PROGRESS
04h 14h D B LOGICAL UNIT NOT READY, SPACE ALLOCATION IN PROGRESS
04h 15h M LOGICAL UNIT NOT READY, ROBOTICS DISABLED

Working Draft SCSI Primary Commands - 4 (SPC-4) 881

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.1 — ASC and ASCQ assignments (part 3 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
04h 16h M LOGICAL UNIT NOT READY, CONFIGURATION REQUIRED
04h 17h M LOGICAL UNIT NOT READY, CALIBRATION REQUIRED
04h 18h M LOGICAL UNIT NOT READY, A DOOR IS OPEN
04h 19h M LOGICAL UNIT NOT READY, OPERATING IN SEQUENTIAL MODE
LOGICAL UNIT NOT READY, START STOP UNIT COMMAND IN
04h 1Ah D B
PROGRESS
04h 1Bh D B LOGICAL UNIT NOT READY, SANITIZE IN PROGRESS
LOGICAL UNIT NOT READY, ADDITIONAL POWER USE NOT YET
04h 1Ch DT M AE B
GRANTED
04h 1Dh D LOGICAL UNIT NOT READY, CONFIGURATION IN PROGRESS
04h 1Eh D LOGICAL UNIT NOT READY, MICROCODE ACTIVATION REQUIRED
04h 1Fh DT L P WROM AE B KV F LOGICAL UNIT NOT READY, MICROCODE DOWNLOAD REQUIRED
04h 20h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, LOGICAL UNIT RESET REQUIRED
04h 21h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, HARD RESET REQUIRED
04h 22h DT L P WROM AE B KV F LOGICAL UNIT NOT READY, POWER CYCLE REQUIRED
05h 00h DT L WROM AE B KV F LOGICAL UNIT DOES NOT RESPOND TO SELECTION
06h 00h D WROM BK NO REFERENCE POSITION FOUND
07h 00h DT L WROM BK MULTIPLE PERIPHERAL DEVICES SELECTED
08h 00h DT L WROM AE B KV F LOGICAL UNIT COMMUNICATION FAILURE
08h 01h DT L WROM AE B KV F LOGICAL UNIT COMMUNICATION TIME-OUT
08h 02h DT L WROM AE B KV F LOGICAL UNIT COMMUNICATION PARITY ERROR
08h 03h DT ROM BK LOGICAL UNIT COMMUNICATION CRC ERROR (ULTRA-DMA/32)
08h 04h DT L P WRO K UNREACHABLE COPY TARGET
09h 00h DT WRO B TRACK FOLLOWING ERROR
09h 01h WRO K TRACKING SERVO FAILURE
09h 02h WRO K FOCUS SERVO FAILURE
09h 03h WRO SPINDLE SERVO FAILURE
09h 04h DT WRO B HEAD SELECT FAULT
0Ah 00h DT L P WROM AE B KV F ERROR LOG OVERFLOW
0Bh 00h DT L P WROM AE B KV F WARNING
0Bh 01h DT L P WROM AE B KV F WARNING - SPECIFIED TEMPERATURE EXCEEDED
0Bh 02h DT L P WROM AE B KV F WARNING - ENCLOSURE DEGRADED
0Bh 03h DT L P WROM AE B KV F WARNING - BACKGROUND SELF-TEST FAILED
0Bh 04h DT L P WRO AE B KV F WARNING - BACKGROUND PRE-SCAN DETECTED MEDIUM ERROR
WARNING - BACKGROUND MEDIUM SCAN DETECTED MEDIUM
0Bh 05h DT L P WRO AE B KV F
ERROR
0Bh 06h DT L P WROM AE B KV F WARNING - NON-VOLATILE CACHE NOW VOLATILE
0Bh 07h DT L P WROM AE B KV F WARNING - DEGRADED POWER TO NON-VOLATILE CACHE
0Bh 08h DT L P WROM AE B KV F WARNING - POWER LOSS EXPECTED
0Bh 09h D WARNING - DEVICE STATISTICS NOTIFICATION ACTIVE
0Ch 00h T R WRITE ERROR

882 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.1 — ASC and ASCQ assignments (part 4 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
0Ch 01h K WRITE ERROR - RECOVERED WITH AUTO REALLOCATION
0Ch 02h D W O BK WRITE ERROR - AUTO REALLOCATION FAILED
0Ch 03h D W O BK WRITE ERROR - RECOMMEND REASSIGNMENT
0Ch 04h DT W O B COMPRESSION CHECK MISCOMPARE ERROR
0Ch 05h DT W O B DATA EXPANSION OCCURRED DURING COMPRESSION
0Ch 06h DT W O B BLOCK NOT COMPRESSIBLE
0Ch 07h R WRITE ERROR - RECOVERY NEEDED
0Ch 08h R WRITE ERROR - RECOVERY FAILED
0Ch 09h R WRITE ERROR - LOSS OF STREAMING
0Ch 0Ah R WRITE ERROR - PADDING BLOCKS ADDED
0Ch 0Bh DT WROM B AUXILIARY MEMORY WRITE ERROR
0Ch 0Ch DT L P WRO AE B KV F WRITE ERROR - UNEXPECTED UNSOLICITED DATA
0Ch 0Dh DT L P WRO AE B KV F WRITE ERROR - NOT ENOUGH UNSOLICITED DATA
0Ch 0Eh DT W O BK MULTIPLE WRITE ERRORS
0Ch 0Fh R DEFECTS IN ERROR WINDOW
0Dh 00h DT L P WRO A K ERROR DETECTED BY THIRD PARTY TEMPORARY INITIATOR
0Dh 01h DT L P WRO A K THIRD PARTY DEVICE FAILURE
0Dh 02h DT L P WRO A K COPY TARGET DEVICE NOT REACHABLE
0Dh 03h DT L P WRO A K INCORRECT COPY TARGET DEVICE TYPE
0Dh 04h DT L P WRO A K COPY TARGET DEVICE DATA UNDERRUN
0Dh 05h DT L P WRO A K COPY TARGET DEVICE DATA OVERRUN
0Eh 00h DT P WROM AE B K F INVALID INFORMATION UNIT
0Eh 01h DT P WROM AE B K F INFORMATION UNIT TOO SHORT
0Eh 02h DT P WROM AE B K F INFORMATION UNIT TOO LONG
0Eh 03h DT P R M AE B K F INVALID FIELD IN COMMAND INFORMATION UNIT
0Fh 00h
10h 00h D W O BK ID CRC OR ECC ERROR
10h 01h DT W O LOGICAL BLOCK GUARD CHECK FAILED
10h 02h DT W O LOGICAL BLOCK APPLICATION TAG CHECK FAILED
10h 03h DT W O LOGICAL BLOCK REFERENCE TAG CHECK FAILED
LOGICAL BLOCK PROTECTION ERROR ON RECOVER BUFFERED
10h 04h T
DATA
10h 05h T LOGICAL BLOCK PROTECTION METHOD ERROR
11h 00h DT WRO BK UNRECOVERED READ ERROR
11h 01h DT WRO BK READ RETRIES EXHAUSTED
11h 02h DT WRO BK ERROR TOO LONG TO CORRECT
11h 03h DT W O BK MULTIPLE READ ERRORS
11h 04h D W O BK UNRECOVERED READ ERROR - AUTO REALLOCATE FAILED
11h 05h WRO B L-EC UNCORRECTABLE ERROR
11h 06h WRO B CIRC UNRECOVERED ERROR
11h 07h W O B DATA RE-SYNCHRONIZATION ERROR

Working Draft SCSI Primary Commands - 4 (SPC-4) 883

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.1 — ASC and ASCQ assignments (part 5 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
11h 08h T INCOMPLETE BLOCK READ
11h 09h T NO GAP FOUND
11h 0Ah DT O BK MISCORRECTED ERROR
11h 0Bh D W O BK UNRECOVERED READ ERROR - RECOMMEND REASSIGNMENT
11h 0Ch D W O BK UNRECOVERED READ ERROR - RECOMMEND REWRITE THE DATA
11h 0Dh DT WRO B DE-COMPRESSION CRC ERROR
11h 0Eh DT WRO B CANNOT DECOMPRESS USING DECLARED ALGORITHM
11h 0Fh R ERROR READING UPC/EAN NUMBER
11h 10h R ERROR READING ISRC NUMBER
11h 11h R READ ERROR - LOSS OF STREAMING
11h 12h DT WROM B AUXILIARY MEMORY READ ERROR
11h 13h DT L P WRO AE B KV F READ ERROR - FAILED RETRANSMISSION REQUEST
11h 14h D READ ERROR - LBA MARKED BAD BY APPLICATION CLIENT
11h 15h D WRITE AFTER SANITIZE REQUIRED
12h 00h D W O BK ADDRESS MARK NOT FOUND FOR ID FIELD
13h 00h D W O BK ADDRESS MARK NOT FOUND FOR DATA FIELD
14h 00h DT L WRO BK RECORDED ENTITY NOT FOUND
14h 01h DT WRO BK RECORD NOT FOUND
14h 02h T FILEMARK OR SETMARK NOT FOUND
14h 03h T END-OF-DATA NOT FOUND
14h 04h T BLOCK SEQUENCE ERROR
14h 05h DT W O BK RECORD NOT FOUND - RECOMMEND REASSIGNMENT
14h 06h DT W O BK RECORD NOT FOUND - DATA AUTO-REALLOCATED
14h 07h T LOCATE OPERATION FAILURE
15h 00h DT L WROM BK RANDOM POSITIONING ERROR
15h 01h DT L WROM BK MECHANICAL POSITIONING ERROR
15h 02h DT WRO BK POSITIONING ERROR DETECTED BY READ OF MEDIUM
16h 00h D W O BK DATA SYNCHRONIZATION MARK ERROR
16h 01h D W O BK DATA SYNC ERROR - DATA REWRITTEN
16h 02h D W O BK DATA SYNC ERROR - RECOMMEND REWRITE
16h 03h D W O BK DATA SYNC ERROR - DATA AUTO-REALLOCATED
16h 04h D W O BK DATA SYNC ERROR - RECOMMEND REASSIGNMENT
17h 00h DT WRO BK RECOVERED DATA WITH NO ERROR CORRECTION APPLIED
17h 01h DT WRO BK RECOVERED DATA WITH RETRIES
17h 02h DT WRO BK RECOVERED DATA WITH POSITIVE HEAD OFFSET
17h 03h DT WRO BK RECOVERED DATA WITH NEGATIVE HEAD OFFSET
17h 04h WRO B RECOVERED DATA WITH RETRIES AND/OR CIRC APPLIED
17h 05h D WRO BK RECOVERED DATA USING PREVIOUS SECTOR ID
17h 06h D W O BK RECOVERED DATA WITHOUT ECC - DATA AUTO-REALLOCATED
17h 07h D WRO BK RECOVERED DATA WITHOUT ECC - RECOMMEND REASSIGNMENT
17h 08h D WRO BK RECOVERED DATA WITHOUT ECC - RECOMMEND REWRITE

884 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.1 — ASC and ASCQ assignments (part 6 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
17h 09h D WRO BK RECOVERED DATA WITHOUT ECC - DATA REWRITTEN
18h 00h DT WRO BK RECOVERED DATA WITH ERROR CORRECTION APPLIED
18h 01h D WRO BK RECOVERED DATA WITH ERROR CORR. & RETRIES APPLIED
18h 02h D WRO BK RECOVERED DATA - DATA AUTO-REALLOCATED
18h 03h R RECOVERED DATA WITH CIRC
18h 04h R RECOVERED DATA WITH L-EC
18h 05h D WRO BK RECOVERED DATA - RECOMMEND REASSIGNMENT
18h 06h D WRO BK RECOVERED DATA - RECOMMEND REWRITE
18h 07h D W O BK RECOVERED DATA WITH ECC - DATA REWRITTEN
18h 08h R RECOVERED DATA WITH LINKING
19h 00h D O K DEFECT LIST ERROR
19h 01h D O K DEFECT LIST NOT AVAILABLE
19h 02h D O K DEFECT LIST ERROR IN PRIMARY LIST
19h 03h D O K DEFECT LIST ERROR IN GROWN LIST
1Ah 00h DT L P WROM AE B KV F PARAMETER LIST LENGTH ERROR
1Bh 00h DT L P WROM AE B KV F SYNCHRONOUS DATA TRANSFER ERROR
1Ch 00h D O BK DEFECT LIST NOT FOUND
1Ch 01h D O BK PRIMARY DEFECT LIST NOT FOUND
1Ch 02h D O BK GROWN DEFECT LIST NOT FOUND
1Dh 00h DT WRO BK MISCOMPARE DURING VERIFY OPERATION
1Dh 01h D B MISCOMPARE VERIFY OF UNMAPPED LBA
1Eh 00h D W O BK RECOVERED ID WITH ECC CORRECTION
1Fh 00h D O K PARTIAL DEFECT LIST TRANSFER
20h 00h DT L P WROM AE B KV F INVALID COMMAND OPERATION CODE
20h 01h DT P WROM AE B K ACCESS DENIED - INITIATOR PENDING-ENROLLED
20h 02h DT P WROM AE B K ACCESS DENIED - NO ACCESS RIGHTS
20h 03h DT P WROM AE B K ACCESS DENIED - INVALID MGMT ID KEY
20h 04h T ILLEGAL COMMAND WHILE IN WRITE CAPABLE STATE
20h 05h T Obsolete
20h 06h T ILLEGAL COMMAND WHILE IN EXPLICIT ADDRESS MODE
20h 07h T ILLEGAL COMMAND WHILE IN IMPLICIT ADDRESS MODE
20h 08h DT P WROM AE B K ACCESS DENIED - ENROLLMENT CONFLICT
20h 09h DT P WROM AE B K ACCESS DENIED - INVALID LU IDENTIFIER
20h 0Ah DT P WROM AE B K ACCESS DENIED - INVALID PROXY TOKEN
20h 0Bh DT P WROM AE B K ACCESS DENIED - ACL LUN CONFLICT
20h 0Ch T ILLEGAL COMMAND WHEN NOT IN APPEND-ONLY MODE
21h 00h DT WRO BK LOGICAL BLOCK ADDRESS OUT OF RANGE
21h 01h DT WROM BK INVALID ELEMENT ADDRESS
21h 02h R INVALID ADDRESS FOR WRITE
21h 03h R INVALID WRITE CROSSING LAYER JUMP
21h 04h D UNALIGNED WRITE COMMAND

Working Draft SCSI Primary Commands - 4 (SPC-4) 885

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.1 — ASC and ASCQ assignments (part 7 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
21h 05h D WRITE BOUNDARY VIOLATION
21h 06h D ATTEMPT TO READ INVALID DATA
21h 07h D READ BOUNDARY VIOLATION
22h 00h D ILLEGAL FUNCTION (USE 20 00, 24 00, OR 26 00)
23h 00h DT P B INVALID TOKEN OPERATION, CAUSE NOT REPORTABLE
23h 01h DT P B INVALID TOKEN OPERATION, UNSUPPORTED TOKEN TYPE
INVALID TOKEN OPERATION, REMOTE TOKEN USAGE NOT
23h 02h DT P B
SUPPORTED
INVALID TOKEN OPERATION, REMOTE ROD TOKEN CREATION NOT
23h 03h DT P B
SUPPORTED
23h 04h DT P B INVALID TOKEN OPERATION, TOKEN UNKNOWN
23h 05h DT P B INVALID TOKEN OPERATION, TOKEN CORRUPT
23h 06h DT P B INVALID TOKEN OPERATION, TOKEN REVOKED
23h 07h DT P B INVALID TOKEN OPERATION, TOKEN EXPIRED
23h 08h DT P B INVALID TOKEN OPERATION, TOKEN CANCELLED
23h 09h DT P B INVALID TOKEN OPERATION, TOKEN DELETED
23h 0Ah DT P B INVALID TOKEN OPERATION, INVALID TOKEN LENGTH
24h 00h DT L P WROM AE B KV F INVALID FIELD IN CDB
24h 01h DT L P WRO AE B KV F CDB DECRYPTION ERROR
24h 02h T Obsolete
24h 03h T Obsolete
24h 04h F SECURITY AUDIT VALUE FROZEN
24h 05h F SECURITY WORKING KEY FROZEN
24h 06h F NONCE NOT UNIQUE
24h 07h F NONCE TIMESTAMP OUT OF RANGE
24h 08h DT R M AE B KV INVALID XCDB
25h 00h DT L P WROM AE B KV F LOGICAL UNIT NOT SUPPORTED
26h 00h DT L P WROM AE B KV F INVALID FIELD IN PARAMETER LIST
26h 01h DT L P WROM AE B KV F PARAMETER NOT SUPPORTED
26h 02h DT L P WROM AE B KV F PARAMETER VALUE INVALID
26h 03h DT L P WROM AE K THRESHOLD PARAMETERS NOT SUPPORTED
26h 04h DT L P WROM AE B KV F INVALID RELEASE OF PERSISTENT RESERVATION
26h 05h DT L P WRO A B K DATA DECRYPTION ERROR
26h 06h DT L P WRO K TOO MANY TARGET DESCRIPTORS
26h 07h DT L P WRO K UNSUPPORTED TARGET DESCRIPTOR TYPE CODE
26h 08h DT L P WRO K TOO MANY SEGMENT DESCRIPTORS
26h 09h DT L P WRO K UNSUPPORTED SEGMENT DESCRIPTOR TYPE CODE
26h 0Ah DT L P WRO K UNEXPECTED INEXACT SEGMENT
26h 0Bh DT L P WRO K INLINE DATA LENGTH EXCEEDED
26h 0Ch DT L P WRO K INVALID OPERATION FOR COPY SOURCE OR DESTINATION
26h 0Dh DT L P WRO K COPY SEGMENT GRANULARITY VIOLATION

886 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.1 — ASC and ASCQ assignments (part 8 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
26h 0Eh DT P WROM AE B K INVALID PARAMETER WHILE PORT IS ENABLED
26h 0Fh F INVALID DATA-OUT BUFFER INTEGRITY CHECK VALUE
26h 10h T DATA DECRYPTION KEY FAIL LIMIT REACHED
26h 11h T INCOMPLETE KEY-ASSOCIATED DATA SET
26h 12h T VENDOR SPECIFIC KEY REFERENCE NOT FOUND
27h 00h DT WRO BK WRITE PROTECTED
27h 01h DT WRO BK HARDWARE WRITE PROTECTED
27h 02h DT WRO BK LOGICAL UNIT SOFTWARE WRITE PROTECTED
27h 03h T R ASSOCIATED WRITE PROTECT
27h 04h T R PERSISTENT WRITE PROTECT
27h 05h T R PERMANENT WRITE PROTECT
27h 06h R F CONDITIONAL WRITE PROTECT
27h 07h D B SPACE ALLOCATION FAILED WRITE PROTECT
27h 08h D ZONE IS READ ONLY
28h 00h DT L P WROM AE B KV F NOT READY TO READY CHANGE, MEDIUM MAY HAVE CHANGED
28h 01h DT WROM B IMPORT OR EXPORT ELEMENT ACCESSED
28h 02h R FORMAT-LAYER MAY HAVE CHANGED
28h 03h M IMPORT/EXPORT ELEMENT ACCESSED, MEDIUM CHANGED
29h 00h DT L P WROM AE B KV F POWER ON, RESET, OR BUS DEVICE RESET OCCURRED
29h 01h DT L P WROM AE B KV F POWER ON OCCURRED
29h 02h DT L P WROM AE B KV F SCSI BUS RESET OCCURRED
29h 03h DT L P WROM AE B KV F BUS DEVICE RESET FUNCTION OCCURRED
29h 04h DT L P WROM AE B KV F DEVICE INTERNAL RESET
29h 05h DT L P WROM AE B KV F TRANSCEIVER MODE CHANGED TO SINGLE-ENDED
29h 06h DT L P WROM AE B KV F TRANSCEIVER MODE CHANGED TO LVD
29h 07h DT L P WROM AE B KV F I_T NEXUS LOSS OCCURRED
2Ah 00h DT L WROM AE B KV F PARAMETERS CHANGED
2Ah 01h DT L WROM AE B KV F MODE PARAMETERS CHANGED
2Ah 02h DT L WROM AE K LOG PARAMETERS CHANGED
2Ah 03h DT L P WROM AE K RESERVATIONS PREEMPTED
2Ah 04h DT L P WROM AE RESERVATIONS RELEASED
2Ah 05h DT L P WROM AE REGISTRATIONS PREEMPTED
2Ah 06h DT L P WROM AE B KV F ASYMMETRIC ACCESS STATE CHANGED
2Ah 07h DT L P WROM AE B KV F IMPLICIT ASYMMETRIC ACCESS STATE TRANSITION FAILED
2Ah 08h DT WROM AE B KV F PRIORITY CHANGED
2Ah 09h D CAPACITY DATA HAS CHANGED
2Ah 0Ah DT ERROR HISTORY I_T NEXUS CLEARED
2Ah 0Bh DT ERROR HISTORY SNAPSHOT RELEASED
2Ah 0Ch F ERROR RECOVERY ATTRIBUTES HAVE CHANGED
2Ah 0Dh T DATA ENCRYPTION CAPABILITIES CHANGED
2Ah 10h DT M E V TIMESTAMP CHANGED

Working Draft SCSI Primary Commands - 4 (SPC-4) 887

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.1 — ASC and ASCQ assignments (part 9 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
DATA ENCRYPTION PARAMETERS CHANGED BY ANOTHER I_T
2Ah 11h T
NEXUS
DATA ENCRYPTION PARAMETERS CHANGED BY VENDOR SPECIFIC
2Ah 12h T
EVENT
2Ah 13h T DATA ENCRYPTION KEY INSTANCE COUNTER HAS CHANGED
2Ah 14h DT R M AE B KV SA CREATION CAPABILITIES DATA HAS CHANGED
2Ah 15h T M V MEDIUM REMOVAL PREVENTION PREEMPTED
2Bh 00h DT L P WRO K COPY CANNOT EXECUTE SINCE HOST CANNOT DISCONNECT
2Ch 00h DT L P WROM AE B KV F COMMAND SEQUENCE ERROR
2Ch 01h TOO MANY WINDOWS SPECIFIED
2Ch 02h INVALID COMBINATION OF WINDOWS SPECIFIED
2Ch 03h R CURRENT PROGRAM AREA IS NOT EMPTY
2Ch 04h R CURRENT PROGRAM AREA IS EMPTY
2Ch 05h B ILLEGAL POWER CONDITION REQUEST
2Ch 06h R PERSISTENT PREVENT CONFLICT
2Ch 07h DT L P WROM AE B KV F PREVIOUS BUSY STATUS
2Ch 08h DT L P WROM AE B KV F PREVIOUS TASK SET FULL STATUS
2Ch 09h DT L P WROM E B KV F PREVIOUS RESERVATION CONFLICT STATUS
2Ch 0Ah F PARTITION OR COLLECTION CONTAINS USER OBJECTS
2Ch 0Bh T NOT RESERVED
2Ch 0Ch D ORWRITE GENERATION DOES NOT MATCH
2Dh 00h T OVERWRITE ERROR ON UPDATE IN PLACE
2Eh 00h D WROM B INSUFFICIENT TIME FOR OPERATION
2Eh 01h D W OM B COMMAND TIMEOUT BEFORE PROCESSING
2Eh 02h D W OM B COMMAND TIMEOUT DURING PROCESSING
COMMAND TIMEOUT DURING PROCESSING DUE TO ERROR
2Eh 03h D W OM B
RECOVERY
2Fh 00h DT L P WROM AE B KV F COMMANDS CLEARED BY ANOTHER INITIATOR
2Fh 01h D COMMANDS CLEARED BY POWER LOSS NOTIFICATION
2Fh 02h DT L P WROM AE B KV F COMMANDS CLEARED BY DEVICE SERVER
2Fh 03h DT L P WROM AE B KV F SOME COMMANDS CLEARED BY QUEUING LAYER EVENT
30h 00h DT WROM BK INCOMPATIBLE MEDIUM INSTALLED
30h 01h DT WRO BK CANNOT READ MEDIUM - UNKNOWN FORMAT
30h 02h DT WRO BK CANNOT READ MEDIUM - INCOMPATIBLE FORMAT
30h 03h DT R M K CLEANING CARTRIDGE INSTALLED
30h 04h DT WRO BK CANNOT WRITE MEDIUM - UNKNOWN FORMAT
30h 05h DT WRO BK CANNOT WRITE MEDIUM - INCOMPATIBLE FORMAT
30h 06h DT WRO B CANNOT FORMAT MEDIUM - INCOMPATIBLE MEDIUM
30h 07h DT L WROM AE B KV F CLEANING FAILURE
30h 08h R CANNOT WRITE - APPLICATION CODE MISMATCH
30h 09h R CURRENT SESSION NOT FIXATED FOR APPEND

888 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.1 — ASC and ASCQ assignments (part 10 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
30h 0Ah DT WRO AE B K CLEANING REQUEST REJECTED
30h 0Ch T WORM MEDIUM - OVERWRITE ATTEMPTED
30h 0Dh T WORM MEDIUM - INTEGRITY CHECK
30h 10h R MEDIUM NOT FORMATTED
30h 11h M INCOMPATIBLE VOLUME TYPE
30h 12h M INCOMPATIBLE VOLUME QUALIFIER
30h 13h M CLEANING VOLUME EXPIRED
31h 00h DT WRO BK MEDIUM FORMAT CORRUPTED
31h 01h D L RO B FORMAT COMMAND FAILED
31h 02h R ZONED FORMATTING FAILED DUE TO SPARE LINKING
31h 03h D B SANITIZE COMMAND FAILED
32h 00h D W O BK NO DEFECT SPARE LOCATION AVAILABLE
32h 01h D W O BK DEFECT LIST UPDATE FAILURE
33h 00h T TAPE LENGTH ERROR
34h 00h DT L P WROM AE B KV F ENCLOSURE FAILURE
35h 00h DT L P WROM AE B KV F ENCLOSURE SERVICES FAILURE
35h 01h DT L P WROM AE B KV F UNSUPPORTED ENCLOSURE FUNCTION
35h 02h DT L P WROM AE B KV F ENCLOSURE SERVICES UNAVAILABLE
35h 03h DT L P WROM AE B KV F ENCLOSURE SERVICES TRANSFER FAILURE
35h 04h DT L P WROM AE B KV F ENCLOSURE SERVICES TRANSFER REFUSED
35h 05h DT L WROM AE B KV F ENCLOSURE SERVICES CHECKSUM ERROR
36h 00h L RIBBON, INK, OR TONER FAILURE
37h 00h DT L WROM AE B KV F ROUNDED PARAMETER
38h 00h B EVENT STATUS NOTIFICATION
38h 02h B ESN - POWER MANAGEMENT CLASS EVENT
38h 04h B ESN - MEDIA CLASS EVENT
38h 06h B ESN - DEVICE BUSY CLASS EVENT
38h 07h D THIN PROVISIONING SOFT THRESHOLD REACHED
39h 00h DT L WROM AE K SAVING PARAMETERS NOT SUPPORTED
3Ah 00h DT L WROM BK MEDIUM NOT PRESENT
3Ah 01h DT WROM BK MEDIUM NOT PRESENT - TRAY CLOSED
3Ah 02h DT WROM BK MEDIUM NOT PRESENT - TRAY OPEN
3Ah 03h DT WROM B MEDIUM NOT PRESENT - LOADABLE
3Ah 04h DT WRO B MEDIUM NOT PRESENT - MEDIUM AUXILIARY MEMORY ACCESSIBLE
3Bh 00h TL SEQUENTIAL POSITIONING ERROR
3Bh 01h T TAPE POSITION ERROR AT BEGINNING-OF-MEDIUM
3Bh 02h T TAPE POSITION ERROR AT END-OF-MEDIUM
3Bh 03h L TAPE OR ELECTRONIC VERTICAL FORMS UNIT NOT READY
3Bh 04h L SLEW FAILURE
3Bh 05h L PAPER JAM
3Bh 06h L FAILED TO SENSE TOP-OF-FORM

Working Draft SCSI Primary Commands - 4 (SPC-4) 889

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.1 — ASC and ASCQ assignments (part 11 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
3Bh 07h L FAILED TO SENSE BOTTOM-OF-FORM
3Bh 08h T REPOSITION ERROR
3Bh 09h READ PAST END OF MEDIUM
3Bh 0Ah READ PAST BEGINNING OF MEDIUM
3Bh 0Bh POSITION PAST END OF MEDIUM
3Bh 0Ch T POSITION PAST BEGINNING OF MEDIUM
3Bh 0Dh DT WROM BK MEDIUM DESTINATION ELEMENT FULL
3Bh 0Eh DT WROM BK MEDIUM SOURCE ELEMENT EMPTY
3Bh 0Fh R END OF MEDIUM REACHED
3Bh 11h DT WROM BK MEDIUM MAGAZINE NOT ACCESSIBLE
3Bh 12h DT WROM BK MEDIUM MAGAZINE REMOVED
3Bh 13h DT WROM BK MEDIUM MAGAZINE INSERTED
3Bh 14h DT WROM BK MEDIUM MAGAZINE LOCKED
3Bh 15h DT WROM BK MEDIUM MAGAZINE UNLOCKED
3Bh 16h R MECHANICAL POSITIONING OR CHANGER ERROR
3Bh 17h F READ PAST END OF USER OBJECT
3Bh 18h M ELEMENT DISABLED
3Bh 19h M ELEMENT ENABLED
3Bh 1Ah M DATA TRANSFER DEVICE REMOVED
3Bh 1Bh M DATA TRANSFER DEVICE INSERTED
TOO MANY LOGICAL OBJECTS ON PARTITION TO SUPPORT
3Bh 1Ch T
OPERATION
3Ch 00h
3Dh 00h DT L P WROM AE K INVALID BITS IN IDENTIFY MESSAGE
3Eh 00h DT L P WROM AE B KV F LOGICAL UNIT HAS NOT SELF-CONFIGURED YET
3Eh 01h DT L P WROM AE B KV F LOGICAL UNIT FAILURE
3Eh 02h DT L P WROM AE B KV F TIMEOUT ON LOGICAL UNIT
3Eh 03h DT L P WROM AE B KV F LOGICAL UNIT FAILED SELF-TEST
3Eh 04h DT L P WROM AE B KV F LOGICAL UNIT UNABLE TO UPDATE SELF-TEST LOG
3Fh 00h DT L P WROM AE B KV F TARGET OPERATING CONDITIONS HAVE CHANGED
3Fh 01h DT L P WROM AE B KV F MICROCODE HAS BEEN CHANGED
3Fh 02h DT L P WROM BK CHANGED OPERATING DEFINITION
3Fh 03h DT L P WROM AE B KV F INQUIRY DATA HAS CHANGED
3Fh 04h DT WROM AE B K COMPONENT DEVICE ATTACHED
3Fh 05h DT WROM AE B K DEVICE IDENTIFIER CHANGED
3Fh 06h DT WROM AE B REDUNDANCY GROUP CREATED OR MODIFIED
3Fh 07h DT WROM AE B REDUNDANCY GROUP DELETED
3Fh 08h DT WROM AE B SPARE CREATED OR MODIFIED
3Fh 09h DT WROM AE B SPARE DELETED
3Fh 0Ah DT WROM AE B K VOLUME SET CREATED OR MODIFIED
3Fh 0Bh DT WROM AE B K VOLUME SET DELETED

890 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.1 — ASC and ASCQ assignments (part 12 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
3Fh 0Ch DT WROM AE B K VOLUME SET DEASSIGNED
3Fh 0Dh DT WROM AE B K VOLUME SET REASSIGNED
3Fh 0Eh DT L P WROM AE REPORTED LUNS DATA HAS CHANGED
3Fh 0Fh DT L P WROM AE B KV F ECHO BUFFER OVERWRITTEN
3Fh 10h DT WROM B MEDIUM LOADABLE
3Fh 11h DT WROM B MEDIUM AUXILIARY MEMORY ACCESSIBLE
3Fh 12h DT L P WR M AE B K F iSCSI IP ADDRESS ADDED
3Fh 13h DT L P WR M AE B K F iSCSI IP ADDRESS REMOVED
3Fh 14h DT L P WR M AE B K F iSCSI IP ADDRESS CHANGED
3Fh 15h DT L P WR M AE B K INSPECT REFERRALS SENSE DESCRIPTORS
3Fh 16h DT P WROM AE B KV F MICROCODE HAS BEEN CHANGED WITHOUT RESET
40h 00h D RAM FAILURE (SHOULD USE 40 NN)
40h NNh DT L P WROM AE B KV F DIAGNOSTIC FAILURE ON COMPONENT NN (80h-FFh)
41h 00h D DATA PATH FAILURE (SHOULD USE 40 NN)
42h 00h D POWER-ON OR SELF-TEST FAILURE (SHOULD USE 40 NN)
43h 00h DT L P WROM AE B KV F MESSAGE ERROR
44h 00h DT L P WROM AE B KV F INTERNAL TARGET FAILURE
44h 01h DT P M AE B KV F PERSISTENT RESERVATION INFORMATION LOST
44h 71h DT B ATA DEVICE FAILED SET FEATURES
45h 00h DT L P WROM AE B KV F SELECT OR RESELECT FAILURE
46h 00h DT L P WROM BK UNSUCCESSFUL SOFT RESET
47h 00h DT L P WROM AE B KV F SCSI PARITY ERROR
47h 01h DT L P WROM AE B KV F DATA PHASE CRC ERROR DETECTED
47h 02h DT L P WROM AE B KV F SCSI PARITY ERROR DETECTED DURING ST DATA PHASE
47h 03h DT L P WROM AE B KV F INFORMATION UNIT iuCRC ERROR DETECTED
47h 04h DT L P WROM AE B KV F ASYNCHRONOUS INFORMATION PROTECTION ERROR DETECTED
47h 05h DT L P WROM AE B KV F PROTOCOL SERVICE CRC ERROR
47h 06h DT M AE B KV F PHY TEST FUNCTION IN PROGRESS
47h 7Fh DT P WROM AE B K SOME COMMANDS CLEARED BY ISCSI PROTOCOL EVENT
48h 00h DT L P WROM AE B KV F INITIATOR DETECTED ERROR MESSAGE RECEIVED
49h 00h DT L P WROM AE B KV F INVALID MESSAGE ERROR
4Ah 00h DT L P WROM AE B KV F COMMAND PHASE ERROR
4Bh 00h DT L P WROM AE B KV F DATA PHASE ERROR
4Bh 01h DT P WROM AE B K INVALID TARGET PORT TRANSFER TAG RECEIVED
4Bh 02h DT P WROM AE B K TOO MUCH WRITE DATA
4Bh 03h DT P WROM AE B K ACK/NAK TIMEOUT
4Bh 04h DT P WROM AE B K NAK RECEIVED
4Bh 05h DT P WROM AE B K DATA OFFSET ERROR
4Bh 06h DT P WROM AE B K INITIATOR RESPONSE TIMEOUT
4Bh 07h DT P WROM AE B K F CONNECTION LOST
4Bh 08h DT P WROM AE B K F DATA-IN BUFFER OVERFLOW - DATA BUFFER SIZE

Working Draft SCSI Primary Commands - 4 (SPC-4) 891

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.1 — ASC and ASCQ assignments (part 13 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
4Bh 09h DT P WROM AE B K F DATA-IN BUFFER OVERFLOW - DATA BUFFER DESCRIPTOR AREA
4Bh 0Ah DT P WROM AE B K F DATA-IN BUFFER ERROR
4Bh 0Bh DT P WROM AE B K F DATA-OUT BUFFER OVERFLOW - DATA BUFFER SIZE
4Bh 0Ch DT P WROM AE B K F DATA-OUT BUFFER OVERFLOW - DATA BUFFER DESCRIPTOR AREA
4Bh 0Dh DT P WROM AE B K F DATA-OUT BUFFER ERROR
4Bh 0Eh DT P WROM AE B K F PCIE FABRIC ERROR
4Bh 0Fh DT P WROM AE B K F PCIE COMPLETION TIMEOUT
4Bh 10h DT P WROM AE B K F PCIE COMPLETER ABORT
4Bh 11h DT P WROM AE B K F PCIE POISONED TLP RECEIVED
4Bh 12h DT P WROM AE B K F PCIE ECRC CHECK FAILED
4Bh 13h DT P WROM AE B K F PCIE UNSUPPORTED REQUEST
4Bh 14h DT P WROM AE B K F PCIE ACS VIOLATION
4Bh 15h DT P WROM AE B K F PCIE TLP PREFIX BLOCKED
4Ch 00h DT L P WROM AE B KV F LOGICAL UNIT FAILED SELF-CONFIGURATION
4Dh NNh DT L P WROM AE B KV F TAGGED OVERLAPPED COMMANDS (NN = TASK TAG)
4Eh 00h DT L P WROM AE B KV F OVERLAPPED COMMANDS ATTEMPTED
4Fh 00h
50h 00h T WRITE APPEND ERROR
50h 01h T WRITE APPEND POSITION ERROR
50h 02h T POSITION ERROR RELATED TO TIMING
51h 00h DT RO ERASE FAILURE
51h 01h D R ERASE FAILURE - INCOMPLETE ERASE OPERATION DETECTED
52h 00h T CARTRIDGE FAULT
53h 00h DT L WROM BK MEDIA LOAD OR EJECT FAILED
53h 01h T UNLOAD TAPE FAILURE
53h 02h DT WROM BK MEDIUM REMOVAL PREVENTED
53h 03h M MEDIUM REMOVAL PREVENTED BY DATA TRANSFER ELEMENT
53h 04h T MEDIUM THREAD OR UNTHREAD FAILURE
53h 05h M VOLUME IDENTIFIER INVALID
53h 06h M VOLUME IDENTIFIER MISSING
53h 07h M DUPLICATE VOLUME IDENTIFIER
53h 08h M ELEMENT STATUS UNKNOWN
53h 09h M DATA TRANSFER DEVICE ERROR - LOAD FAILED
53h 0Ah M DATA TRANSFER DEVICE ERROR - UNLOAD FAILED
53h 0Bh M DATA TRANSFER DEVICE ERROR - UNLOAD MISSING
53h 0Ch M DATA TRANSFER DEVICE ERROR - EJECT FAILED
53h 0Dh M DATA TRANSFER DEVICE ERROR - LIBRARY COMMUNICATION FAILED
54h 00h P SCSI TO HOST SYSTEM INTERFACE FAILURE
55h 00h P SYSTEM RESOURCE FAILURE
55h 01h D O BK SYSTEM BUFFER FULL
55h 02h DT L P WROM AE K INSUFFICIENT RESERVATION RESOURCES

892 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.1 — ASC and ASCQ assignments (part 14 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
55h 03h DT L P WROM AE K INSUFFICIENT RESOURCES
55h 04h DT L P WROM AE K INSUFFICIENT REGISTRATION RESOURCES
55h 05h DT P WROM AE B K INSUFFICIENT ACCESS CONTROL RESOURCES
55h 06h DT WROM B AUXILIARY MEMORY OUT OF SPACE
55h 07h F QUOTA ERROR
MAXIMUM NUMBER OF SUPPLEMENTAL DECRYPTION KEYS
55h 08h T
EXCEEDED
55h 09h M MEDIUM AUXILIARY MEMORY NOT ACCESSIBLE
55h 0Ah M DATA CURRENTLY UNAVAILABLE
55h 0Bh DT L P WROM AE B KV F INSUFFICIENT POWER FOR OPERATION
55h 0Ch DT P B INSUFFICIENT RESOURCES TO CREATE ROD
55h 0Dh DT P B INSUFFICIENT RESOURCES TO CREATE ROD TOKEN
56h 00h
57h 00h R UNABLE TO RECOVER TABLE-OF-CONTENTS
58h 00h O GENERATION DOES NOT EXIST
59h 00h O UPDATED BLOCK READ
5Ah 00h DT L P WRO BK OPERATOR REQUEST OR STATE CHANGE INPUT
5Ah 01h DT WROM BK OPERATOR MEDIUM REMOVAL REQUEST
5Ah 02h DT WRO A B K OPERATOR SELECTED WRITE PROTECT
5Ah 03h DT WRO A B K OPERATOR SELECTED WRITE PERMIT
5Bh 00h DT L P WROM K LOG EXCEPTION
5Bh 01h DT L P WROM K THRESHOLD CONDITION MET
5Bh 02h DT L P WROM K LOG COUNTER AT MAXIMUM
5Bh 03h DT L P WROM K LOG LIST CODES EXHAUSTED
5Ch 00h D O RPL STATUS CHANGE
5Ch 01h D O SPINDLES SYNCHRONIZED
5Ch 02h D O SPINDLES NOT SYNCHRONIZED
5Dh 00h DT L P WROM AE B KV F FAILURE PREDICTION THRESHOLD EXCEEDED
5Dh 01h R B MEDIA FAILURE PREDICTION THRESHOLD EXCEEDED
5Dh 02h R LOGICAL UNIT FAILURE PREDICTION THRESHOLD EXCEEDED
5Dh 03h R SPARE AREA EXHAUSTION PREDICTION THRESHOLD EXCEEDED
5Dh 10h D B HARDWARE IMPENDING FAILURE GENERAL HARD DRIVE FAILURE
5Dh 11h D B HARDWARE IMPENDING FAILURE DRIVE ERROR RATE TOO HIGH
5Dh 12h D B HARDWARE IMPENDING FAILURE DATA ERROR RATE TOO HIGH
5Dh 13h D B HARDWARE IMPENDING FAILURE SEEK ERROR RATE TOO HIGH
5Dh 14h D B HARDWARE IMPENDING FAILURE TOO MANY BLOCK REASSIGNS
5Dh 15h D B HARDWARE IMPENDING FAILURE ACCESS TIMES TOO HIGH
5Dh 16h D B HARDWARE IMPENDING FAILURE START UNIT TIMES TOO HIGH
5Dh 17h D B HARDWARE IMPENDING FAILURE CHANNEL PARAMETRICS
5Dh 18h D B HARDWARE IMPENDING FAILURE CONTROLLER DETECTED
5Dh 19h D B HARDWARE IMPENDING FAILURE THROUGHPUT PERFORMANCE

Working Draft SCSI Primary Commands - 4 (SPC-4) 893

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.1 — ASC and ASCQ assignments (part 15 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
5Dh 1Ah D B HARDWARE IMPENDING FAILURE SEEK TIME PERFORMANCE
5Dh 1Bh D B HARDWARE IMPENDING FAILURE SPIN-UP RETRY COUNT
HARDWARE IMPENDING FAILURE DRIVE CALIBRATION RETRY
5Dh 1Ch D B
COUNT
5Dh 20h D B CONTROLLER IMPENDING FAILURE GENERAL HARD DRIVE FAILURE
5Dh 21h D B CONTROLLER IMPENDING FAILURE DRIVE ERROR RATE TOO HIGH
5Dh 22h D B CONTROLLER IMPENDING FAILURE DATA ERROR RATE TOO HIGH
5Dh 23h D B CONTROLLER IMPENDING FAILURE SEEK ERROR RATE TOO HIGH
5Dh 24h D B CONTROLLER IMPENDING FAILURE TOO MANY BLOCK REASSIGNS
5Dh 25h D B CONTROLLER IMPENDING FAILURE ACCESS TIMES TOO HIGH
5Dh 26h D B CONTROLLER IMPENDING FAILURE START UNIT TIMES TOO HIGH
5Dh 27h D B CONTROLLER IMPENDING FAILURE CHANNEL PARAMETRICS
5Dh 28h D B CONTROLLER IMPENDING FAILURE CONTROLLER DETECTED
5Dh 29h D B CONTROLLER IMPENDING FAILURE THROUGHPUT PERFORMANCE
5Dh 2Ah D B CONTROLLER IMPENDING FAILURE SEEK TIME PERFORMANCE
5Dh 2Bh D B CONTROLLER IMPENDING FAILURE SPIN-UP RETRY COUNT
CONTROLLER IMPENDING FAILURE DRIVE CALIBRATION RETRY
5Dh 2Ch D B
COUNT
DATA CHANNEL IMPENDING FAILURE GENERAL HARD DRIVE
5Dh 30h D B
FAILURE
5Dh 31h D B DATA CHANNEL IMPENDING FAILURE DRIVE ERROR RATE TOO HIGH
5Dh 32h D B DATA CHANNEL IMPENDING FAILURE DATA ERROR RATE TOO HIGH
5Dh 33h D B DATA CHANNEL IMPENDING FAILURE SEEK ERROR RATE TOO HIGH
5Dh 34h D B DATA CHANNEL IMPENDING FAILURE TOO MANY BLOCK REASSIGNS
5Dh 35h D B DATA CHANNEL IMPENDING FAILURE ACCESS TIMES TOO HIGH
5Dh 36h D B DATA CHANNEL IMPENDING FAILURE START UNIT TIMES TOO HIGH
5Dh 37h D B DATA CHANNEL IMPENDING FAILURE CHANNEL PARAMETRICS
5Dh 38h D B DATA CHANNEL IMPENDING FAILURE CONTROLLER DETECTED
5Dh 39h D B DATA CHANNEL IMPENDING FAILURE THROUGHPUT PERFORMANCE
5Dh 3Ah D B DATA CHANNEL IMPENDING FAILURE SEEK TIME PERFORMANCE
5Dh 3Bh D B DATA CHANNEL IMPENDING FAILURE SPIN-UP RETRY COUNT
DATA CHANNEL IMPENDING FAILURE DRIVE CALIBRATION RETRY
5Dh 3Ch D B
COUNT
5Dh 40h D B SERVO IMPENDING FAILURE GENERAL HARD DRIVE FAILURE
5Dh 41h D B SERVO IMPENDING FAILURE DRIVE ERROR RATE TOO HIGH
5Dh 42h D B SERVO IMPENDING FAILURE DATA ERROR RATE TOO HIGH
5Dh 43h D B SERVO IMPENDING FAILURE SEEK ERROR RATE TOO HIGH
5Dh 44h D B SERVO IMPENDING FAILURE TOO MANY BLOCK REASSIGNS
5Dh 45h D B SERVO IMPENDING FAILURE ACCESS TIMES TOO HIGH
5Dh 46h D B SERVO IMPENDING FAILURE START UNIT TIMES TOO HIGH
5Dh 47h D B SERVO IMPENDING FAILURE CHANNEL PARAMETRICS

894 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.1 — ASC and ASCQ assignments (part 16 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
5Dh 48h D B SERVO IMPENDING FAILURE CONTROLLER DETECTED
5Dh 49h D B SERVO IMPENDING FAILURE THROUGHPUT PERFORMANCE
5Dh 4Ah D B SERVO IMPENDING FAILURE SEEK TIME PERFORMANCE
5Dh 4Bh D B SERVO IMPENDING FAILURE SPIN-UP RETRY COUNT
5Dh 4Ch D B SERVO IMPENDING FAILURE DRIVE CALIBRATION RETRY COUNT
5Dh 50h D B SPINDLE IMPENDING FAILURE GENERAL HARD DRIVE FAILURE
5Dh 51h D B SPINDLE IMPENDING FAILURE DRIVE ERROR RATE TOO HIGH
5Dh 52h D B SPINDLE IMPENDING FAILURE DATA ERROR RATE TOO HIGH
5Dh 53h D B SPINDLE IMPENDING FAILURE SEEK ERROR RATE TOO HIGH
5Dh 54h D B SPINDLE IMPENDING FAILURE TOO MANY BLOCK REASSIGNS
5Dh 55h D B SPINDLE IMPENDING FAILURE ACCESS TIMES TOO HIGH
5Dh 56h D B SPINDLE IMPENDING FAILURE START UNIT TIMES TOO HIGH
5Dh 57h D B SPINDLE IMPENDING FAILURE CHANNEL PARAMETRICS
5Dh 58h D B SPINDLE IMPENDING FAILURE CONTROLLER DETECTED
5Dh 59h D B SPINDLE IMPENDING FAILURE THROUGHPUT PERFORMANCE
5Dh 5Ah D B SPINDLE IMPENDING FAILURE SEEK TIME PERFORMANCE
5Dh 5Bh D B SPINDLE IMPENDING FAILURE SPIN-UP RETRY COUNT
5Dh 5Ch D B SPINDLE IMPENDING FAILURE DRIVE CALIBRATION RETRY COUNT
5Dh 60h D B FIRMWARE IMPENDING FAILURE GENERAL HARD DRIVE FAILURE
5Dh 61h D B FIRMWARE IMPENDING FAILURE DRIVE ERROR RATE TOO HIGH
5Dh 62h D B FIRMWARE IMPENDING FAILURE DATA ERROR RATE TOO HIGH
5Dh 63h D B FIRMWARE IMPENDING FAILURE SEEK ERROR RATE TOO HIGH
5Dh 64h D B FIRMWARE IMPENDING FAILURE TOO MANY BLOCK REASSIGNS
5Dh 65h D B FIRMWARE IMPENDING FAILURE ACCESS TIMES TOO HIGH
5Dh 66h D B FIRMWARE IMPENDING FAILURE START UNIT TIMES TOO HIGH
5Dh 67h D B FIRMWARE IMPENDING FAILURE CHANNEL PARAMETRICS
5Dh 68h D B FIRMWARE IMPENDING FAILURE CONTROLLER DETECTED
5Dh 69h D B FIRMWARE IMPENDING FAILURE THROUGHPUT PERFORMANCE
5Dh 6Ah D B FIRMWARE IMPENDING FAILURE SEEK TIME PERFORMANCE
5Dh 6Bh D B FIRMWARE IMPENDING FAILURE SPIN-UP RETRY COUNT
5Dh 6Ch D B FIRMWARE IMPENDING FAILURE DRIVE CALIBRATION RETRY COUNT
5Dh FFh DT L P WROM AE B KV F FAILURE PREDICTION THRESHOLD EXCEEDED (FALSE)
5Eh 00h DT L P WRO A K LOW POWER CONDITION ON
5Eh 01h DT L P WRO A K IDLE CONDITION ACTIVATED BY TIMER
5Eh 02h DT L P WRO A K STANDBY CONDITION ACTIVATED BY TIMER
5Eh 03h DT L P WRO A K IDLE CONDITION ACTIVATED BY COMMAND
5Eh 04h DT L P WRO A K STANDBY CONDITION ACTIVATED BY COMMAND
5Eh 05h DT L P WRO A K IDLE_B CONDITION ACTIVATED BY TIMER
5Eh 06h DT L P WRO A K IDLE_B CONDITION ACTIVATED BY COMMAND
5Eh 07h DT L P WRO A K IDLE_C CONDITION ACTIVATED BY TIMER
5Eh 08h DT L P WRO A K IDLE_C CONDITION ACTIVATED BY COMMAND

Working Draft SCSI Primary Commands - 4 (SPC-4) 895

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.1 — ASC and ASCQ assignments (part 17 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
5Eh 09h DT L P WRO A K STANDBY_Y CONDITION ACTIVATED BY TIMER
5Eh 0Ah DT L P WRO A K STANDBY_Y CONDITION ACTIVATED BY COMMAND
5Eh 41h B POWER STATE CHANGE TO ACTIVE
5Eh 42h B POWER STATE CHANGE TO IDLE
5Eh 43h B POWER STATE CHANGE TO STANDBY
5Eh 45h B POWER STATE CHANGE TO SLEEP
5Eh 47h BK POWER STATE CHANGE TO DEVICE CONTROL
5Fh 00h
60h 00h LAMP FAILURE
61h 00h VIDEO ACQUISITION ERROR
61h 01h UNABLE TO ACQUIRE VIDEO
61h 02h OUT OF FOCUS
62h 00h SCAN HEAD POSITIONING ERROR
63h 00h R END OF USER AREA ENCOUNTERED ON THIS TRACK
63h 01h R PACKET DOES NOT FIT IN AVAILABLE SPACE
64h 00h R ILLEGAL MODE FOR THIS TRACK
64h 01h R INVALID PACKET SIZE
65h 00h DT L P WROM AE B KV F VOLTAGE FAULT
66h 00h AUTOMATIC DOCUMENT FEEDER COVER UP
66h 01h AUTOMATIC DOCUMENT FEEDER LIFT UP
66h 02h DOCUMENT JAM IN AUTOMATIC DOCUMENT FEEDER
66h 03h DOCUMENT MISS FEED AUTOMATIC IN DOCUMENT FEEDER
67h 00h A CONFIGURATION FAILURE
67h 01h A CONFIGURATION OF INCAPABLE LOGICAL UNITS FAILED
67h 02h A ADD LOGICAL UNIT FAILED
67h 03h A MODIFICATION OF LOGICAL UNIT FAILED
67h 04h A EXCHANGE OF LOGICAL UNIT FAILED
67h 05h A REMOVE OF LOGICAL UNIT FAILED
67h 06h A ATTACHMENT OF LOGICAL UNIT FAILED
67h 07h A CREATION OF LOGICAL UNIT FAILED
67h 08h A ASSIGN FAILURE OCCURRED
67h 09h A MULTIPLY ASSIGNED LOGICAL UNIT
67h 0Ah DT L P WROM AE B KV F SET TARGET PORT GROUPS COMMAND FAILED
67h 0Bh DT B ATA DEVICE FEATURE NOT ENABLED
68h 00h A LOGICAL UNIT NOT CONFIGURED
68h 01h D SUBSIDIARY LOGICAL UNIT NOT CONFIGURED
69h 00h A DATA LOSS ON LOGICAL UNIT
69h 01h A MULTIPLE LOGICAL UNIT FAILURES
69h 02h A PARITY/DATA MISMATCH
6Ah 00h A INFORMATIONAL, REFER TO LOG
6Bh 00h A STATE CHANGE HAS OCCURRED

896 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.1 — ASC and ASCQ assignments (part 18 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
6Bh 01h A REDUNDANCY LEVEL GOT BETTER
6Bh 02h A REDUNDANCY LEVEL GOT WORSE
6Ch 00h A REBUILD FAILURE OCCURRED
6Dh 00h A RECALCULATE FAILURE OCCURRED
6Eh 00h A COMMAND TO LOGICAL UNIT FAILED
COPY PROTECTION KEY EXCHANGE FAILURE - AUTHENTICATION
6Fh 00h R
FAILURE
6Fh 01h R COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT PRESENT
COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT
6Fh 02h R
ESTABLISHED
6Fh 03h R READ OF SCRAMBLED SECTOR WITHOUT AUTHENTICATION
6Fh 04h R MEDIA REGION CODE IS MISMATCHED TO LOGICAL UNIT REGION
DRIVE REGION MUST BE PERMANENT/REGION RESET COUNT
6Fh 05h R
ERROR
6Fh 06h R INSUFFICIENT BLOCK COUNT FOR BINDING NONCE RECORDING
6Fh 07h R CONFLICT IN BINDING NONCE RECORDING
70h NNh T DECOMPRESSION EXCEPTION SHORT ALGORITHM ID OF NN
71h 00h T DECOMPRESSION EXCEPTION LONG ALGORITHM ID
72h 00h R SESSION FIXATION ERROR
72h 01h R SESSION FIXATION ERROR WRITING LEAD-IN
72h 02h R SESSION FIXATION ERROR WRITING LEAD-OUT
72h 03h R SESSION FIXATION ERROR - INCOMPLETE TRACK IN SESSION
72h 04h R EMPTY OR PARTIALLY WRITTEN RESERVED TRACK
72h 05h R NO MORE TRACK RESERVATIONS ALLOWED
72h 06h R RMZ EXTENSION IS NOT ALLOWED
72h 07h R NO MORE TEST ZONE EXTENSIONS ARE ALLOWED
73h 00h R CD CONTROL ERROR
73h 01h R POWER CALIBRATION AREA ALMOST FULL
73h 02h R POWER CALIBRATION AREA IS FULL
73h 03h R POWER CALIBRATION AREA ERROR
73h 04h R PROGRAM MEMORY AREA UPDATE FAILURE
73h 05h R PROGRAM MEMORY AREA IS FULL
73h 06h R RMA/PMA IS ALMOST FULL
73h 10h R CURRENT POWER CALIBRATION AREA ALMOST FULL
73h 11h R CURRENT POWER CALIBRATION AREA IS FULL
73h 17h R RDZ IS FULL
74h 00h T SECURITY ERROR
74h 01h T UNABLE TO DECRYPT DATA
74h 02h T UNENCRYPTED DATA ENCOUNTERED WHILE DECRYPTING
74h 03h T INCORRECT DATA ENCRYPTION KEY
74h 04h T CRYPTOGRAPHIC INTEGRITY VALIDATION FAILED

Working Draft SCSI Primary Commands - 4 (SPC-4) 897

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.1 — ASC and ASCQ assignments (part 19 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
74h 05h T ERROR DECRYPTING DATA
74h 06h T UNKNOWN SIGNATURE VERIFICATION KEY
74h 07h T ENCRYPTION PARAMETERS NOT USEABLE
74h 08h DT R M E V F DIGITAL SIGNATURE VALIDATION FAILURE
74h 09h T ENCRYPTION MODE MISMATCH ON READ
74h 0Ah T ENCRYPTED BLOCK NOT RAW READ ENABLED
74h 0Bh T INCORRECT ENCRYPTION PARAMETERS
74h 0Ch DT R M AE B KV UNABLE TO DECRYPT PARAMETER LIST
74h 0Dh T ENCRYPTION ALGORITHM DISABLED
74h 10h DT R M AE B KV SA CREATION PARAMETER VALUE INVALID
74h 11h DT R M AE B KV SA CREATION PARAMETER VALUE REJECTED
74h 12h DT R M AE B KV INVALID SA USAGE
74h 21h T DATA ENCRYPTION CONFIGURATION PREVENTED
74h 30h DT R M AE B KV SA CREATION PARAMETER NOT SUPPORTED
74h 40h DT R M AE B KV AUTHENTICATION FAILED
74h 61h V EXTERNAL DATA ENCRYPTION KEY MANAGER ACCESS ERROR
74h 62h V EXTERNAL DATA ENCRYPTION KEY MANAGER ERROR
74h 63h V EXTERNAL DATA ENCRYPTION KEY NOT FOUND
74h 64h V EXTERNAL DATA ENCRYPTION REQUEST NOT AUTHORIZED
74h 6Eh T EXTERNAL DATA ENCRYPTION CONTROL TIMEOUT
74h 6Fh T EXTERNAL DATA ENCRYPTION CONTROL ERROR
74h 71h DT R M E V LOGICAL UNIT ACCESS NOT AUTHORIZED
74h 79h D SECURITY CONFLICT IN TRANSLATED DEVICE
75h 00h
76h 00h
77h 00h
78h 00h
79h 00h
7Ah 00h
7Bh 00h
7Ch 00h
7Dh 00h
7Eh 00h

898 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.1 — ASC and ASCQ assignments (part 20 of 20)

.D – Direct Access Block Device (SBC-3) Device Column key

. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ASC ASCQ DT L P WROM AE B KV F Description
7Fh 00h

80h xxh \
Through > Vendor specific
FFh xxh /

xxh 80h \
Through > Vendor specific qualification of standard ASC
xxh FFh /
All codes not shown are reserved.

Working Draft SCSI Primary Commands - 4 (SPC-4) 899

T10/BSR INCITS 513 Revision 37 17 May 2014

F.3 Operation codes

F.3.1 Operation codes

Table F.2 is a numerical order listing of the command operation codes.

Table F.2 — Operation codes (part 1 of 6)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) M = Mandatory
. L – Printer Device (SSC) O = Optional
. P – Processor Device (SPC-2) V = Vendor specific
. . W – Write Once Block Device (SBC) Z = Obsolete
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
OP D T L PWR OM A E B K V F Description
00h MMMMMMMMMMMMMM TEST UNIT READY
01h M REWIND
01h Z V ZZZZ REZERO UNIT
02h VVVVVV V
03h MMMMMMMMMMOMMM REQUEST SENSE
04h M OO FORMAT UNIT
04h O FORMAT MEDIUM
04h O FORMAT
05h VMV V V V V READ BLOCK LIMITS
06h VVVVVV V
07h OV V O OV REASSIGN BLOCKS
07h O INITIALIZE ELEMENT STATUS
08h ZMV O OV READ(6)
08h O RECEIVE
08h GET MESSAGE(6)
09h VVVVVV V
0Ah ZO O OV WRITE(6)
0Ah M SEND(6)
0Ah SEND MESSAGE(6)
0Ah M PRINT
0Bh Z ZOZ V SEEK(6)
0Bh O SET CAPACITY
0Bh O SLEW AND PRINT
0Ch VVVVVV V
0Dh VVVVVV V
0Eh VVVVVV V
0Fh VOV V V V V READ REVERSE(6)
10h VM V V V WRITE FILEMARKS(6)
10h O SYNCHRONIZE BUFFER
11h VMV V V V SPACE(6)
12h MMMMMMMMMMMMMM INQUIRY
13h V VVVV
13h O VERIFY(6)
14h V OO V V V RECOVER BUFFERED DATA
15h OMO O O O O O O O MODE SELECT(6)

900 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.2 — Operation codes (part 2 of 6)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) M = Mandatory
. L – Printer Device (SSC) O = Optional
. P – Processor Device (SPC-2) V = Vendor specific
. . W – Write Once Block Device (SBC) Z = Obsolete
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
OP D T L PWR OM A E B K V F Description
16h Z Z M Z O OOO Z O RESERVE(6)
16h Z RESERVE ELEMENT(6)
17h Z Z M Z O OOO Z O RELEASE(6)
17h Z RELEASE ELEMENT(6)
18h Z Z Z ZOZO Z COPY
19h VMV V V V ERASE(6)
1Ah OMO O O O O O O O MODE SENSE(6)
1Bh O O O O O MO O START STOP UNIT
1Bh O M LOAD UNLOAD
1Bh SCAN
1Bh O STOP PRINT
1Bh O OPEN/CLOSE IMPORT/EXPORT ELEMENT
1Ch O O O O O O O OM O O O RECEIVE DIAGNOSTIC RESULTS
1Dh MMMMM MMOM MMM SEND DIAGNOSTIC
1Eh OO OOOO O O PREVENT ALLOW MEDIUM REMOVAL
1Fh
20h V VVV V
21h V VVV V
22h V VVV V
23h V V V V
23h O READ FORMAT CAPACITIES
24h V VV SET WINDOW
25h M M M M READ CAPACITY(10)
25h O READ CAPACITY
25h M READ CARD CAPACITY
25h GET WINDOW
26h V VV
27h V VV
28h M MOM MM READ(10)
28h GET MESSAGE(10)
29h V V VO READ GENERATION
2Ah O MOM MO WRITE(10)
2Ah SEND(10)
2Ah SEND MESSAGE(10)
2Bh Z OOO O SEEK(10)
2Bh M LOCATE(10)
2Bh O POSITION TO ELEMENT
2Ch V OO ERASE(10)
2Dh O READ UPDATED BLOCK
2Dh V
2Eh O OOO MO WRITE AND VERIFY(10)
2Fh O OOO VERIFY(10)

Working Draft SCSI Primary Commands - 4 (SPC-4) 901

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.2 — Operation codes (part 3 of 6)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) M = Mandatory
. L – Printer Device (SSC) O = Optional
. P – Processor Device (SPC-2) V = Vendor specific
. . W – Write Once Block Device (SBC) Z = Obsolete
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
OP D T L PWR OM A E B K V F Description
30h Z ZZZ SEARCH DATA HIGH(10)
31h Z ZZZ SEARCH DATA EQUAL(10)
31h OBJECT POSITION
32h Z ZZZ SEARCH DATA LOW(10)
33h Z OZO SET LIMITS(10)
34h O O O O PRE-FETCH(10)
34h M READ POSITION
34h GET DATA BUFFER STATUS
35h O OOO MO SYNCHRONIZE CACHE(10)
36h Z O O O LOCK UNLOCK CACHE(10)
37h O O READ DEFECT DATA(10)
37h O INITIALIZE ELEMENT STATUS WITH RANGE
38h O O O MEDIUM SCAN
39h Z Z Z ZOZO Z COMPARE
3Ah Z Z Z ZOZO Z COPY AND VERIFY
3Bh O O O O O O O O O OMO O O WRITE BUFFER
3Ch O O O O O O O O O O O O O READ BUFFER
3Dh O UPDATE BLOCK
3Eh O O O READ LONG(10)
3Fh O O O WRITE LONG(10)
40h Z Z Z ZOZOZ CHANGE DEFINITION
41h O WRITE SAME(10)
42h O UNMAP
42h O READ SUB-CHANNEL
43h O READ TOC/PMA/ATIP
44h M M REPORT DENSITY SUPPORT
44h READ HEADER
45h O PLAY AUDIO(10)
46h M GET CONFIGURATION
47h O PLAY AUDIO MSF
48h O O SANITIZE
49h
4Ah M GET EVENT STATUS NOTIFICATION
4Bh O PAUSE/RESUME
4Ch O O O O O O O O O O O O LOG SELECT
4Dh O O O O O O O O O OMO LOG SENSE
4Eh O STOP PLAY/SCAN
4Fh
50h Z XDWRITE(10)
51h O XPWRITE(10)
51h O READ DISC INFORMATION
52h Z XDREAD(10)

902 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.2 — Operation codes (part 4 of 6)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) M = Mandatory
. L – Printer Device (SSC) O = Optional
. P – Processor Device (SPC-2) V = Vendor specific
. . W – Write Once Block Device (SBC) Z = Obsolete
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
OP D T L PWR OM A E B K V F Description
52h O READ TRACK INFORMATION
53h O XDWRITEREAD(10)
53h O RESERVE TRACK
54h O SEND OPC INFORMATION
55h O O O OMO O O OMOMO MODE SELECT(10)
56h Z Z M Z O OOO Z RESERVE(10)
56h Z RESERVE ELEMENT(10)
57h Z Z M Z O OOO Z RELEASE(10)
57h Z RELEASE ELEMENT(10)
58h O REPAIR TRACK
59h
5Ah O O O OMO O O OMOMO MODE SENSE(10)
5Bh O CLOSE TRACK/SESSION
5Ch O READ BUFFER CAPACITY
5Dh O SEND CUE SHEET
5Eh OMO O O O O O O M PERSISTENT RESERVE IN
5Fh OMO O O O O O O M PERSISTENT RESERVE OUT
7Eh OO O OOOO O extended CDB
7Fh O M variable length CDB (more than 16 bytes)
80h Z XDWRITE EXTENDED(16)
80h M WRITE FILEMARKS(16)
81h Z REBUILD(16)
81h O READ REVERSE(16)
82h Z REGENERATE(16)
82h O ALLOW OVERWRITE
83h OOOOO O OO Third-party Copy OUT
84h OOOOO O OO Third-party Copy IN
85h O O ATA PASS-THROUGH(16)
86h OO OO OOOOOOO ACCESS CONTROL IN
87h OO OO OOOOOOO ACCESS CONTROL OUT
88h MO O O O READ(16)
89h O COMPARE AND WRITE
8Ah OO O O O WRITE(16)
8Bh O ORWRITE
8Ch OO O OO O M READ ATTRIBUTE
8Dh OO O OO O O WRITE ATTRIBUTE
8Eh O O O O WRITE AND VERIFY(16)
8Fh OO O O O VERIFY(16)
90h O O O O PRE-FETCH(16)
91h O O O O SYNCHRONIZE CACHE(16)
91h O SPACE(16)
92h Z O O LOCK UNLOCK CACHE(16)

Working Draft SCSI Primary Commands - 4 (SPC-4) 903

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.2 — Operation codes (part 5 of 6)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) M = Mandatory
. L – Printer Device (SSC) O = Optional
. P – Processor Device (SPC-2) V = Vendor specific
. . W – Write Once Block Device (SBC) Z = Obsolete
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
OP D T L PWR OM A E B K V F Description
92h M LOCATE(16)
93h O WRITE SAME(16)
93h M ERASE(16)
94h [usage proposed by SCSI Socket Services project]
95h [usage proposed by SCSI Socket Services project]
96h [usage proposed by SCSI Socket Services project]
97h [usage proposed by SCSI Socket Services project]
98h
99h
9Ah
9Bh
9Ch O WRITE ATOMIC(16)
9Dh SERVICE ACTION BIDIRECTIONAL
9Eh SERVICE ACTION IN(16)
9Fh M SERVICE ACTION OUT(16)
A0h MMO O O OMMM OMO REPORT LUNS
A1h O BLANK
A1h O O ATA PASS-THROUGH(12)
A2h OO O O SECURITY PROTOCOL IN
A3h O O O O O OMO O OM MAINTENANCE IN
A3h O SEND KEY
A4h OOO O OOOOOOO MAINTENANCE OUT
A4h O REPORT KEY
A5h Z O OM MOVE MEDIUM
A5h O PLAY AUDIO(12)
A6h O EXCHANGE MEDIUM
A6h O LOAD/UNLOAD C/DVD
A7h ZZ O O MOVE MEDIUM ATTACHED
A7h O SET READ AHEAD
A8h O OOO READ(12)
A8h GET MESSAGE(12)
A9h O SERVICE ACTION OUT(12)
AAh O OOO WRITE(12)
AAh SEND MESSAGE(12)
ABh O O SERVICE ACTION IN(12)
ACh O ERASE(12)
ACh O GET PERFORMANCE
ADh O READ DVD STRUCTURE
AEh O O O WRITE AND VERIFY(12)
AFh O O O VERIFY(12)
B0h ZZZ SEARCH DATA HIGH(12)
B1h ZZZ SEARCH DATA EQUAL(12)

904 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.2 — Operation codes (part 6 of 6)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) M = Mandatory
. L – Printer Device (SSC) O = Optional
. P – Processor Device (SPC-2) V = Vendor specific
. . W – Write Once Block Device (SBC) Z = Obsolete
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
OP D T L PWR OM A E B K V F Description
B2h ZZZ SEARCH DATA LOW(12)
B3h Z OZO SET LIMITS(12)
B4h ZZ OZO READ ELEMENT STATUS ATTACHED
B5h OO O O SECURITY PROTOCOL OUT
B5h O REQUEST VOLUME ELEMENT ADDRESS
B6h O SEND VOLUME TAG
B6h O SET STREAMING
B7h O O READ DEFECT DATA(12)
B8h Z O Z OM READ ELEMENT STATUS
B9h O READ CD MSF
BAh O O O OMO REDUNDANCY GROUP (IN)
BAh O SCAN
BBh O O OOOO REDUNDANCY GROUP (OUT)
BBh O SET CD SPEED
BCh O O O OMO SPARE (IN)
BDh O O OOOO SPARE (OUT)
BDh O MECHANISM STATUS
BEh O O O OMO VOLUME SET (IN)
BEh O READ CD
BFh O O OOOO VOLUME SET (OUT)
BFh O SEND DVD STRUCTURE

Working Draft SCSI Primary Commands - 4 (SPC-4) 905

T10/BSR INCITS 513 Revision 37 17 May 2014

F.3.2 Additional operation codes for devices with the ENCSERV bit set to one

Table F.3 is a numerical order listing of the additional command operation codes used by devices that have
the ENCSERV bit set to one in their standard INQUIRY data. The operation codes listed in table F.3 are in
addition to the operation codes listed in F.3.1 for the device type indicated by the standard INQUIRY data
having the ENCSERV bit set to one.

Table F.3 — Additional operation codes for devices with the ENCSERV bit set to one
D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) M = Mandatory
. L – Printer Device (SSC) O = Optional
. P – Processor Device (SPC-2) V = Vendor specific
. . W – Write Once Block Device (SBC) Z = Obsolete
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
OP D T L PWR OM A E B K V F Description
1C MMMMMMMMMMMMMM RECEIVE DIAGNOSTIC RESULTS
1D MMMMMMMMMMMMMM SEND DIAGNOSTIC

906 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

F.3.3 MAINTENANCE IN service actions and MAINTENANCE OUT service actions

The assignment of service action codes for the MAINTENANCE IN operation codes and MAINTENANCE
OUT operation codes by this standard is shown in table F.4. The MAINTENANCE IN service actions and
MAINTENANCE OUT service actions that may be assigned by other command standards are noted as
restricted but their specific usage is not described.

Table F.4 — MAINTENANCE IN service actions and MAINTENANCE OUT service actions

Service
Action Description
MAINTENANCE IN [operation code A3h]
00h to 04h Restricted (see SCC-2)
05h REPORT IDENTIFYING INFORMATION
06h to 09h Restricted (see SCC-2)
0Ah REPORT TARGET PORT GROUPS
0Bh REPORT ALIASES
0Ch REPORT SUPPORTED OPERATION CODES
0Dh REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS
0Eh REPORT PRIORITY
0Fh REPORT TIMESTAMP
10h MANAGEMENT PROTOCOL IN
11h to 1Ch Reserved
1Dh to 1Eh Restricted (see SSC-5 and ADC-3)
1Fh Vendor specific
MAINTENANCE OUT [operation code A4h]
00h to 05h Restricted (see SCC-2)
06h SET IDENTIFYING INFORMATION
07h to 09h Restricted (see SCC-2)
0Ah SET TARGET PORT GROUPS
0Bh CHANGE ALIASES
0Ch REMOVE I_T NEXUS
0Dh Reserved
0Eh SET PRIORITY
0Fh SET TIMESTAMP
10h MANAGEMENT PROTOCOL OUT
11h to 1Ch Reserved
1Dh to 1Eh Restricted (see SSC-5, ADC-3, and SMC-3)
1Fh Vendor specific

Working Draft SCSI Primary Commands - 4 (SPC-4) 907

T10/BSR INCITS 513 Revision 37 17 May 2014

F.3.4 SERVICE ACTION IN service actions and SERVICE ACTION OUT service actions

The assignment of service action codes for the SERVICE ACTION IN(12) operation codes and SERVICE
ACTION OUT(12) operation codes by this standard is shown in table F.5. The SERVICE ACTION IN(12)
service actions and SERVICE ACTION OUT(12) service actions that may be assigned by other command
standards are noted as restricted but their specific usage is not described.

Table F.5 — SERVICE ACTION IN(12) service actions and SERVICE ACTION OUT(12) service actions

Service
Action Description
SERVICE ACTION IN(12) [operation code ABh]
00h Reserved
01h READ MEDIA SERIAL NUMBER
02h to 1Fh Reserved
SERVICE ACTION OUT(12) [operation code A9h]
00h to 1Eh Reserved
1Fh Restricted (see applicable command standard)

The assignment of service action codes for the SERVICE ACTION IN(16) operation codes and SERVICE
ACTION OUT(16) operation codes by this standard is shown in table F.6. The SERVICE ACTION IN(16)
service actions and SERVICE ACTION OUT(16) service actions that may be assigned by other command
standards are noted as restricted but their specific usage is not described.

Table F.6 — SERVICE ACTION IN(16) service actions and SERVICE ACTION OUT(16) service actions

Service
Action Description
SERVICE ACTION IN(16) [operation code 9Eh]
00h to 0Fh Reserved
10h to 1Fh Restricted (see applicable command standard)
SERVICE ACTION OUT(16) [operation code 9Fh]
00h to 0Fh Reserved
10h to 1Fh Restricted (see applicable command standard)

908 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

F.3.5 SERVICE ACTION BIDIRECTIONAL service actions

The assignment of service action codes for the SERVICE ACTION BIDIRECTIONAL operation codes by this
standard is shown in table F.7. The SERVICE ACTION BIDIRECTIONAL service actions that may be
assigned by other command standards are noted as restricted but their specific usage is not described.

Table F.7 — SERVICE ACTION BIDIRECTIONAL service actions

Service
Action Description
SERVICE ACTION BIDIRECTIONAL [operation code 9Dh]
00h to 0Fh Reserved
10h to 1Fh Restricted (see applicable command standard)

Working Draft SCSI Primary Commands - 4 (SPC-4) 909

T10/BSR INCITS 513 Revision 37 17 May 2014

F.3.6 Variable length CDB service action codes

Only one operation code is assigned to the variable length CDB (see 4.2.3). Therefore, the service action
code is effectively the operation code for variable length CDB uses. To allow command standards to assign
uses of the variable length CDB without consulting this standard, ranges of service action codes are assigned
to command sets as shown in table F.8.

Table F.8 — Variable Length CDB Service Action Code Ranges

Service Action
Code Range Doc. Description
0000h to 07FFh SBC-3 Direct access block device (e.g., magnetic disk)
0800h to 0FFFh SSC-4 Sequential-access device (e.g., magnetic tape)
1000h to 17FFh SSC Printer device
1800h to 1FFFh this standard Commands for all device types (see table F.9)
2000h to 27FFh Reserved
2800h to 2FFFh MMC-6 CD-ROM device
3800h to 3FFFh Reserved
4000h to 47FFh SMC-3 Media changer device (e.g., jukeboxes)
5000h to 5FFFh Defined by ASC IT8 (Graphic arts pre-press devices)
6000h to 67FFh SCC-2 Storage array controller device (e.g., RAID)
7000h to 77FFh RBC Simplified direct-access device (e.g., magnetic disk)
7800h to 7FFFh OCRW Optical card reader/writer device
8800h to 8FFFh OSD-2 Object-based Storage Device
3000h to 37FFh Reserved
4800h to 4FFFh Reserved
6800h to 6FFFh Reserved
8000h to 87FFh Reserved
9000h to F7FFh Reserved
F800h to FFFFh Vendor specific

The variable length CDB service action codes assigned by this standard are shown in table F.9.

Table F.9 — Variable Length CDB Service Action Codes Used by All Device Types

Service Action
Code Description
1800h RECEIVE CREDENTIAL command
1801h to 1FF7h Reserved
1FF8h to 1FFFh Restricted (see FC-SB-4)

910 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

F.4 Diagnostic page codes

Table F.10 is a numerical order listing of the diagnostic page codes.

Table F.10 — Diagnostic page codes

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
Diagnostic
. . . . .
Page Code
DT L P WROM AE B KV F Diagnostic Page Name
00h DT L P WROM AE KV F Supported Diagnostic Pages
01h E Configuration
02h E Enclosure Status/Control
03h E Help Text
04h E String In/Out
05h E Threshold In/Out
06h E Obsolete
07h E Element Descriptor
08h E Short Enclosure Status
09h E Enclosure Busy
0Ah E Additional Element Status
0Bh E Subenclosure Help Text
0Ch E Subenclosure String In/Out
0Dh E Supported SES Diagnostic Pages
0Eh E Download Microcode Status/Control
0Fh E Subenclosure Nickname Status/Control
10h to 1Fh SES vendor specific

3Fh Protocol Specific diagnostic page

40h D W O Translate Address In/Out

41h D W O Device Status In/Out
42h D Rebuild Assist

80h to FFh Vendor specific

All codes not shown are restricted or reserved.

Working Draft SCSI Primary Commands - 4 (SPC-4) 911

T10/BSR INCITS 513 Revision 37 17 May 2014

F.5 Log page codes

Table F.11 is a numerical order listing of the log page codes.

Table F.11 — Log page codes (part 1 of 2)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
Log . . . . . F – Object-based Storage Device (OSD-2)
Log
Subpage . . . . .
Page Code
Code DT L P WROM AE B KV F Log Page Name
00h 00h DT L P WROM AE KV F Supported Log Pages
00h FFh DT L P WROM AE KV F Supported Log Pages and Subpages
01h to 3Fh FFh DT L P WROM AE KV F Supported Subpages
01h 00h DT L P WRO A KV F Buffer Over-Run/Under-Run
02h 00h DT WRO KV Write Error Counters
03h 00h DT WRO KV Read Error Counters
04h 00h T V Read Reverse Error Counters
05h 00h DT WRO KV Verify Error Counters
06h 00h DT L P WROM AE KV F Non-Medium Error
07h 00h DT L P WROM AE KV F Last n Error Events
08h 00h D W O V Format Status
09h 00h to FEh O Reserved to the MS59 Std. (contact AIIM C21 comm.)
0Ah 00h to FEh O Reserved to the MS59 Std. (contact AIIM C21 comm.)
0Bh 00h DT L P WROM AE V F Last n Deferred Error or Asynchronous Events
0Ch 00h D Logical Block Provisioning
0Ch 00h T V Sequential-Access Device
0Dh 00h DT L P WROM AE V Temperature
0Eh 00h DT L P WROM AE V Start-Stop Cycle Counter
0Fh 00h DT L P WROM AE V Application Client
10h 00h DT L P WROM AE V Self-Test Results
11h 00h D Solid State Media
11h 00h T V DT Device Status
12h 00h V TapeAlert Response
13h 00h V Requested Recovery
14h 00h T V Device Statistics
15h 00h D Background Scan Results
15h 00h V Service Buffers Information
16h 00h D ATA PASS-THROUGH Results
16h 00h T V Tape Diagnostic Data
17h 00h D Non-Volatile Cache
17h 00h to 0Fh T Volume Statistics
18h xxh DT L P WROM AE KV Protocol Specific Port (see table F.12)
19h 00h D General Statistics and Performance
19h 01h D Group Statistics and Performance (1)
19h 02h D Group Statistics and Performance (2)
19h 03h D Group Statistics and Performance (3)

912 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.11 — Log page codes (part 2 of 2)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
Log . . . . . F – Object-based Storage Device (OSD-2)
Log
Subpage . . . . .
Page Code
Code DT L P WROM AE B KV F Log Page Name
19h 04h D Group Statistics and Performance (4)
19h 05h D Group Statistics and Performance (5)
19h 06h D Group Statistics and Performance (6)
19h 07h D Group Statistics and Performance (7)
19h 08h D Group Statistics and Performance (8)
19h 09h D Group Statistics and Performance (9)
19h 0Ah D Group Statistics and Performance (10)
19h 0Bh D Group Statistics and Performance (11)
19h 0Ch D Group Statistics and Performance (12)
19h 0Dh D Group Statistics and Performance (13)
19h 0Eh D Group Statistics and Performance (14)
19h 0Fh D Group Statistics and Performance (15)
19h 10h D Group Statistics and Performance (16)
19h 11h D Group Statistics and Performance (17)
19h 12h D Group Statistics and Performance (18)
19h 13h D Group Statistics and Performance (19)
19h 14h D Group Statistics and Performance (20)
19h 15h D Group Statistics and Performance (21)
19h 16h D Group Statistics and Performance (22)
19h 17h D Group Statistics and Performance (23)
19h 18h D Group Statistics and Performance (24)
19h 19h D Group Statistics and Performance (25)
19h 1Ah D Group Statistics and Performance (26)
19h 1Bh D Group Statistics and Performance (27)
19h 1Ch D Group Statistics and Performance (28)
19h 1Dh D Group Statistics and Performance (29)
19h 1Eh D Group Statistics and Performance (30)
19h 1Fh D Group Statistics and Performance (31)
1Ah 00h DT L P WRO A K Power Condition Transitions
1Bh 00h T Data Compression
2Dh 00h T Current Service Information
2Eh 00h T M TapeAlert
2Fh 00h DT L P WROM AE KV Informational Exceptions

30h to 3Eh 00h to FEh Vendor specific

3Fh 00h to FEh Reserved

All codes not shown here or in table F.12

are restricted or reserved.

Working Draft SCSI Primary Commands - 4 (SPC-4) 913

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.12 is a numerical order listing of the log page codes used by SCSI transport protocols.

Table F.12 — Transport protocol specific log page codes

F – Fibre Channel Protocol for SCSI (FCP-4) Device Column key
. S – SAS Serial SCSI Protocol (SPL-3) blank = code not used
. V – Automation/Drive Interface Transport Protocol (ADT-2) not blank = code used
Log Log . U – USB Attached SCSI (UAS-2)
Page Subpage . .
Code Code F SVU Log Page Name
18h 00h S Protocol Specific Port

See table F.11 for information on the codes not shown here.

914 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

F.6 Mode page codes

Table F.13 is a numerical order listing of the mode page codes.

Table F.13 — Mode page codes (part 1 of 2)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
Mode . . . . . F – Object-based Storage Device (OSD-2)
Mode Page
Subpage . . . . .
Code
Code DT L P WROM AE B KV F Mode Page Name
01h 00h DT WRO K Read-Write Error Recovery
02h 00h DT L WROM AE KV F Disconnect-Reconnect
03h 00h D Format Device
03h 00h L Parallel Printer Interface
03h 00h R MRW CD-RW
04h 00h D Rigid Disk Geometry
04h 00h L Serial Printer Interface
05h 00h D Flexible Disk
05h 00h L Printer Options
05h 00h R Write Parameters
06h 00h W O Optical Memory
06h 00h B RBC Device Parameters
07h 00h D W O K Verify Error Recovery
08h 00h D WRO K Caching
09h 00h DT L WRO AE K obsolete
0Ah 00h DT L WROM AE KV F Control
0Ah 01h DT L WROM AE KV F Control Extension
0Ah 02h D Application Tag
0Ah F0h T Control Data Protection
0Ah F1h D PATA Control
0Bh 00h D W O K Medium Types Supported
0Ch 00h D Notch and Partition
0Dh 00h D obsolete
0Dh 00h R CD Device Parameters
0Eh 00h R CD Audio Control
0Eh 01h V Target Device
0Eh 02h V DT Device Primary Port
0Eh 03h V Logical Unit
0Eh 04h V Target Device Serial Number
0Fh 00h T Data Compression
10h 00h D XOR Control
10h 00h T Device Configuration
10h 01h T Device Configuration Extension
11h 00h T Medium Partition (1)
12h
13h

Working Draft SCSI Primary Commands - 4 (SPC-4) 915

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.13 — Mode page codes (part 2 of 2)

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
Mode . . . . . F – Object-based Storage Device (OSD-2)
Mode Page
Subpage . . . . .
Code
Code DT L P WROM AE B KV F Mode Page Name
14h 00h DT P WROM AE B K F Enclosure Services Management
15h Extended
16h Extended Device-Type Specific
17h
18h xxh DT L WROM AE V F Protocol Specific Logical Unit (see table F.14)
19h xxh DT L WROM AE V F Protocol Specific Port (see table F.14)
1Ah 00h DT L WROM A V Power Condition
1Ah 01h DT Power Consumption
1Ah F1h D B ATA Power Condition
1Bh 00h A LUN Mapping
1Ch 00h D AE Informational Exceptions Control
1Ch 00h T M V Informational Exceptions Control (tapes-specific format)
1Ch 00h R Fault/Failure Reporting
1Ch 00h L Informational Exceptions Control (see SSC)
1Ch 00h W O Informational Exceptions Control (see SBC)
1Ch 01h D Background Control
1Ch 02h D Logical Block Provisioning
1Dh 00h T Medium Configuration
1Dh 00h R C/DVD Time-Out and Protect
1Dh 00h M Element Address Assignments
1Eh 00h M Transport Geometry Parameters
1Fh 00h M Device Capabilities

00h Vendor specific (does not require page format)

20h to 29h Device-type specific (vendor specific in common usage)

2Ah DT L W OM AE B KV F Device-type specific (vendor specific in common usage)

2Ah 00h R CD Capabilities and Mechanical Status

2Bh to 3Eh Device-type specific (vendor specific in common usage)

3Fh xxh Return all pages and/or subpages (MODE SENSE only)
xxh FFh Return all subpages (MODE SENSE only)

All codes not shown here or in table F.14

are restricted or reserved.

916 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.14 is a numerical order listing of the mode page codes used by SCSI transport protocols.

Table F.14 — Transport protocol specific mode page codes

F – Fibre Channel Protocol for SCSI (FCP-4) Device Column key
. S – SAS Serial SCSI Protocol (SPL-3) blank = code not used
. V – Automation/Drive Interface Transport Protocol (ADT-2) not blank = code used
Mode Mode . U – USB Attached SCSI (UAS-2)
Page Subpage . .
Code Code F SVU Mode Page Name
18h 00h FS Protocol Specific Logical Unit
19h 00h FS Protocol Specific Port
19h 01h S Phy Control And Discover
19h 02h S Shared Port Control

See table F.13 for information on the codes not shown here.

Working Draft SCSI Primary Commands - 4 (SPC-4) 917

T10/BSR INCITS 513 Revision 37 17 May 2014

F.7 VPD page codes

Table F.15 is a numerical order listing of the VPD page codes.

Table F.15 — VPD page codes

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
VPD Page
. . . . .
Code
DT L P WROM AE B KV F VPD Page Name
00h DT L P WROM AE B KV F Supported VPD Pages
01h to 7Fh DT L P WROM AE B KV F ASCII Information
80h DT L P WROM AE B KV F Unit Serial Number
81h DT L P WROM AE B KV F Obsolete
82h DT L P WROM AE B KV F Obsolete
83h DT L P WROM AE B KV F Device Identification
84h DT L P WROM AE B KV F Software Interface Identification
85h DT L P WROM AE B KV F Management Network Addresses
86h DT L P WROM AE B KV F Extended INQUIRY Data
87h DT L P WROM AE B KV F Mode Page Policy
88h DT L P WROM AE B KV F SCSI Ports
89h D ATA Information
8Ah DT L P WRO A K Power Condition
8Bh T M Device Constituents
8Ch D B CFA Profile Information
8Dh DT Power Consumption
8Fh DT P R B Third-party Copy

90h DT L WROM AE V F Protocol Specific Logical Unit Information

91h DT L WROM AE V F Protocol Specific Port Information

B0h D Block Limits

B0h T Sequential-access Device Capabilities
B0h F OSD information
B1h D Block Device Characteristics
B1h T V Manufacturer-assigned Serial Number
B1h F Security Token
B2h D Logical Block Provisioning
B2h T TapeAlert Supported Flags
B3h D Referrals
B3h T Automation Device Serial Number
B4h T Data Transfer Device Element Address

C0h to FFh Vendor specific

All codes not shown here or in table F.16 are restricted or reserved.

918 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.14 is a numerical order listing of the VPD page codes used by SCSI transport protocols.

Table F.16 — Transport protocol specific VPD page codes

F – Fibre Channel Protocol for SCSI (FCP-4) Device Column key
. S – SAS Serial SCSI Protocol (SPL-3) blank = code not used
. V – Automation/Drive Interface Transport Protocol (ADT-2) not blank = code used
. U – USB Attached SCSI (UAS-2)
VPD Page
. .
Code
F SVU VPD Page Name
90h S Protocol Specific Logical Unit Information
91h S Protocol Specific Port Information

See table F.15 for information on the codes not shown here.

Working Draft SCSI Primary Commands - 4 (SPC-4) 919

T10/BSR INCITS 513 Revision 37 17 May 2014

F.8 ROD type codes

Table F.17 is a numerical order listing of the ROD types.

Table F.17 — ROD type codes

D – Direct Access Block Device (SBC-3) Device Column key
. T – Sequential Access Device (SSC-4) blank = code not used
. L – Printer Device (SSC) not blank = code used
. P – Processor Device (SPC-2)
. . W – Write Once Block Device (SBC)
. . R – C/DVD Device (MMC-6)
. . O – Optical Memory Block Device (SBC)
. . . M – Media Changer Device (SMC-3)
. . . A – Storage Array Device (SCC-2)
. . . E – SCSI Enclosure Services Device (SES-3)
. . . . B – Simplified Direct-Access (Reduced Block) device (RBC)
. . . . K – Optical Card Reader/Writer device (OCRW)
. . . . V – Automation/Device Interface device (ADC-3)
. . . . . F – Object-based Storage Device (OSD-2)
. . . . .
ROD Type
. . . . . ROD tokens allowed
Code
DT L P WROM AE B KV F ROD type Output Input
0000 0000h DT Internal use ROD or unused ROD type No No

0001 0000h DT Access upon reference Yes Yes

0080 0000h DT Point in time copy – default Yes Yes
0080 0001h DT Point in time copy – change vulnerable Yes Yes
0080 0002h DT Point in time copy – persistent Yes Yes
0080 FFFFh DT Point in time copy – any Yes Yes

FFFF 0001h D Block device zero ROD token Yes a Yes

All codes not shown are restricted or reserved.

a Output of this ROD type code is allowed only in the ROD tokens returned by the POPULATE TOKEN command
(see SBC-3).

920 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

F.9 Version descriptor values

Table F.18 is a numerical order listing of the version descriptor values used in the standard INQUIRY data.
Each version descriptor value is computed from a coded value identifying the standard and a coded value
representing the revision of the standard. The formula is ((standard32)+revision). Table F.18 shows all three
code values and the associated standard name. The version descriptor code is shown in both decimal and
hexadecimal.

Table F.18 — Version descriptor assignments (part 1 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

0 0 0 0000h Version Descriptor Not Supported or No Standard Identified

1 0 32 0020h SAM (no version claimed)

1 27 59 003Bh SAM T10/0994-D revision 18

1 28 60 003Ch SAM ANSI INCITS 270-1996

2 0 64 0040h SAM-2 (no version claimed)

2 20 84 0054h SAM-2 T10/1157-D revision 23

2 21 85 0055h SAM-2 T10/1157-D revision 24

2 28 92 005Ch SAM-2 ANSI INCITS 366-2003

2 30 94 005Eh SAM-2 ISO/IEC 14776-412

3 0 96 0060h SAM-3 (no version claimed)

3 2 98 0062h SAM-3 T10/1561-D revision 7

3 21 117 0075h SAM-3 T10/1561-D revision 13

3 22 118 0076h SAM-3 T10/1561-D revision 14

3 23 119 0077h SAM-3 ANSI INCITS 402-2005

4 0 128 0080h SAM-4 (no version claimed)

4 7 135 0087h SAM-4 T10/1683-D revision 13

4 11 139 008Bh SAM-4 T10/1683-D revision 14

4 16 144 0090h SAM-4 ANSI INCITS 447-2008

4 18 146 0092h SAM-4 ISO/IEC 14776-414

5 0 160 00A0h SAM-5 (no version claimed)

5 2 162 00A2h SAM-5 T10/2104-D revision 4

9 0 288 0120h SPC (no version claimed)

9 27 315 013Bh SPC T10/0995-D revision 11a

9 28 316 013Ch SPC ANSI INCITS 301-1997

Working Draft SCSI Primary Commands - 4 (SPC-4) 921

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.18 — Version descriptor assignments (part 2 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

10 0 320 0140h MMC (no version claimed)

10 27 347 015Bh MMC T10/1048-D revision 10a

10 28 348 015Ch MMC ANSI INCITS 304-1997

11 0 352 0160h SCC (no version claimed)

11 27 379 017Bh SCC T10/1047-D revision 06c

11 28 380 017Ch SCC ANSI INCITS 276-1997

12 0 384 0180h SBC (no version claimed)

12 27 411 019Bh SBC T10/0996-D revision 08c

12 28 412 019Ch SBC ANSI INCITS 306-1998

13 0 416 01A0h SMC (no version claimed)

13 27 443 01BBh SMC T10/0999-D revision 10a

13 28 444 01BCh SMC ANSI INCITS 314-1998

13 30 446 01BEh SMC ISO/IEC 14776-351

14 0 448 01C0h SES (no version claimed)

14 27 475 01DBh SES T10/1212-D revision 08b

14 28 476 01DCh SES ANSI INCITS 305-1998

14 29 477 01DDh SES T10/1212 revision 08b w/ Amendment ANSI

INCITS.305/AM1-2000

14 30 478 01DEh SES ANSI INCITS 305-1998 w/ Amendment ANSI

INCITS.305/AM1-2000

15 0 480 01E0h SCC-2 (no version claimed)

15 27 507 01FBh SCC-2 T10/1125-D revision 04

15 28 508 01FCh SCC-2 ANSI INCITS 318-1998

16 0 512 0200h SSC (no version claimed)

16 1 513 0201h SSC T10/0997-D revision 17

16 7 519 0207h SSC T10/0997-D revision 22

16 28 540 021Ch SSC ANSI INCITS 335-2000

17 0 544 0220h RBC (no version claimed)

17 24 568 0238h RBC T10/1240-D revision 10a

17 28 572 023Ch RBC ANSI INCITS 330-2000

922 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.18 — Version descriptor assignments (part 3 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

18 0 576 0240h MMC-2 (no version claimed)

18 21 597 0255h MMC-2 T10/1228-D revision 11

18 27 603 025Bh MMC-2 T10/1228-D revision 11a

18 28 604 025Ch MMC-2 ANSI INCITS 333-2000

19 0 608 0260h SPC-2 (no version claimed)

19 7 615 0267h SPC-2 T10/1236-D revision 12

19 9 617 0269h SPC-2 T10/1236-D revision 18

19 21 629 0275h SPC-2 T10/1236-D revision 19

19 22 630 0276h SPC-2 T10/1236-D revision 20

19 23 631 0277h SPC-2 ANSI INCITS 351-2001

19 24 632 0278h SPC-2 ISO/IEC 14776-452

20 0 640 0280h OCRW (no version claimed)

20 30 670 029Eh OCRW ISO/IEC 14776-381

21 0 672 02A0h MMC-3 (no version claimed)

21 21 693 02B5h MMC-3 T10/1363-D revision 9

21 22 694 02B6h MMC-3 T10/1363-D revision 10g

21 24 696 02B8h MMC-3 ANSI INCITS 360-2002

23 0 736 02E0h SMC-2 (no version claimed)

23 21 757 02F5h SMC-2 T10/1383-D revision 5

23 28 764 02FCh SMC-2 T10/1383-D revision 6

23 29 765 02FDh SMC-2 T10/1383-D revision 7

23 30 766 02FEh SMC-2 ANSI INCITS 382-2004

24 0 768 0300h SPC-3 (no version claimed)

24 1 769 0301h SPC-3 T10/1416-D revision 7

24 7 775 0307h SPC-3 T10/1416-D revision 21

24 15 783 030Fh SPC-3 T10/1416-D revision 22

24 18 786 0312h SPC-3 T10/1416-D revision 23

24 20 788 0314h SPC-3 ANSI INCITS 408-2005

24 22 790 0316h SPC-3 ISO/IEC 14776-453

Working Draft SCSI Primary Commands - 4 (SPC-4) 923

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.18 — Version descriptor assignments (part 4 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

25 0 800 0320h SBC-2 (no version claimed)

25 2 802 0322h SBC-2 T10/1417-D revision 5a

25 4 804 0324h SBC-2 T10/1417-D revision 15

25 27 827 033Bh SBC-2 T10/1417-D revision 16

25 29 829 033Dh SBC-2 ANSI INCITS 405-2005

25 30 830 033Eh SBC-2 ISO/IEC 14776-322

26 0 832 0340h OSD (no version claimed)

26 1 833 0341h OSD T10/1355-D revision 0

26 2 834 0342h OSD T10/1355-D revision 7a

26 3 835 0343h OSD T10/1355-D revision 8

26 4 836 0344h OSD T10/1355-D revision 9

26 21 853 0355h OSD T10/1355-D revision 10

26 22 854 0356h OSD ANSI INCITS 400-2004

27 0 864 0360h SSC-2 (no version claimed)

27 20 884 0374h SSC-2 T10/1434-D revision 7

27 21 885 0375h SSC-2 T10/1434-D revision 9

27 29 893 037Dh SSC-2 ANSI INCITS 380-2003

28 0 896 0380h BCC (no version claimed)

29 0 928 03A0h MMC-4 (no version claimed)

29 16 944 03B0h MMC-4 T10/1545-D revision 5

29 17 945 03B1h MMC-4 T10/1545-D revision 5a

29 29 957 03BDh MMC-4 T10/1545-D revision 3

29 30 958 03BEh MMC-4 T10/1545-D revision 3d

29 31 959 03BFh MMC-4 ANSI INCITS 401-2005

30 0 960 03C0h ADC (no version claimed)

30 21 981 03D5h ADC T10/1558-D revision 6

30 22 982 03D6h ADC T10/1558-D revision 7

30 23 983 03D7h ADC ANSI INCITS 403-2005

31 0 992 03E0h SES-2 (no version claimed)

924 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.18 — Version descriptor assignments (part 5 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

31 1 993 03E1h SES-2 T10/1559-D revision 16

31 7 999 03E7h SES-2 T10/1559-D revision 19

31 11 1003 03EBh SES-2 T10/1559-D revision 20

31 16 1008 03F0h SES-2 ANSI INCITS 448-2008

31 18 1010 03F2h SES-2 ISO/IEC 14776-372

32 0 1024 0400h SSC-3 (no version claimed)

32 3 1027 0403h SSC-3 T10/1611-D revision 04a

32 7 1031 0407h SSC-3 T10/1611-D revision 05

32 9 1033 0409h SSC-3 ANSI INCITS 467-2011

33 0 1056 0420h MMC-5 (no version claimed)

33 15 1071 042Fh MMC-5 T10/1675-D revision 03

33 17 1073 0431h MMC-5 T10/1675-D revision 03b

33 18 1074 0432h MMC-5 T10/1675-D revision 04

33 20 1076 0434h MMC-5 ANSI INCITS 430-2007

34 0 1088 0440h OSD-2 (no version claimed)

34 4 1092 0444h OSD-2 T10/1729-D revision 4

34 6 1094 0446h OSD-2 T10/1729-D revision 5

34 8 1096 0448h OSD-2 ANSI INCITS 458-2011

35 0 1120 0460h SPC-4 (no version claimed)

35 1 1121 0461h SPC-4 T10/BSR INCITS 513 revision 16

35 2 1122 0462h SPC-4 T10/BSR INCITS 513 revision 18

35 3 1123 0463h SPC-4 T10/BSR INCITS 513 revision 23

35 6 1126 0466h SPC-4 T10/BSR INCITS 513 revision 36

35 8 1128 0468h SPC-4 T10/BSR INCITS 513 revision 37

36 0 1152 0480h SMC-3 (no version claimed)

36 2 1154 0482h SMC-3 T10/1730-D revision 15

36 4 1156 0484h SMC-3 T10/1730-D revision 16

36 6 1158 0486h SMC-3 ANSI INCITS 484-2012

37 0 1184 04A0h ADC-2 (no version claimed)

Working Draft SCSI Primary Commands - 4 (SPC-4) 925

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.18 — Version descriptor assignments (part 6 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

37 7 1191 04A7h ADC-2 T10/1741-D revision 7

37 10 1194 04AAh ADC-2 T10/1741-D revision 8

37 12 1196 04ACh ADC-2 ANSI INCITS 441-2008

38 0 1216 04C0h SBC-3 (no version claimed)

38 3 1219 04C3h SBC-3 T10/BSR INCITS 514 revision 35

38 5 1221 04C5h SBC-3 T10/BSR INCITS 514 revision 36

39 0 1248 04E0h MMC-6 (no version claimed)

39 3 1251 04E3h MMC-6 T10/1836-D revision 02b

39 5 1253 04E5h MMC-6 T10/1836-D revision 02g

39 6 1254 04E6h MMC-6 ANSI INCITS 468-2010

39 7 1255 04E7h MMC-6 ANSI INCITS 468-2010 + MMC-6/AM1 ANSI

INCITS 468-2010/AM 1

40 0 1280 0500h ADC-3 (no version claimed)

40 2 1282 0502h ADC-3 T10/1895-D revision 04

40 4 1284 0504h ADC-3 T10/1895-D revision 05

40 6 1286 0506h ADC-3 T10/1895-D revision 05a

40 10 1290 050Ah ADC-3 ANSI INCITS 497-2012

41 0 1312 0520h SSC-4 (no version claimed)

41 3 1315 0523h SSC-4 T10/BSR INCITS 516 revision 2

41 5 1317 0525h SSC-4 T10/BSR INCITS 516 revision 3

41 7 1319 0527h SSC-4 ANSI INCITS 516-2013

43 0 1376 0560h OSD-3 (no version claimed)

44 0 1408 0580h SES-3 (no version claimed)

45 0 1440 05A0h SSC-5 (no version claimed)

46 0 1472 05C0h SPC-5 (no version claimed)

47 0 1504 05E0h SFSC (no version claimed)

48 0 1536 0600h SBC-4 (no version claimed)

49 0 1568 0620h ZBC (no version claimed)

65 0 2080 0820h SSA-TL2 (no version claimed)

926 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.18 — Version descriptor assignments (part 7 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

65 27 2107 083Bh SSA-TL2 T10.1/1147-D revision 05b

65 28 2108 083Ch SSA-TL2 ANSI INCITS 308-1998

66 0 2112 0840h SSA-TL1 (no version claimed)

66 27 2139 085Bh SSA-TL1 T10.1/0989-D revision 10b

66 28 2140 085Ch SSA-TL1 ANSI INCITS 295-1996

67 0 2144 0860h SSA-S3P (no version claimed)

67 27 2171 087Bh SSA-S3P T10.1/1051-D revision 05b

67 28 2172 087Ch SSA-S3P ANSI INCITS 309-1998

68 0 2176 0880h SSA-S2P (no version claimed)

68 27 2203 089Bh SSA-S2P T10.1/1121-D revision 07b

68 28 2204 089Ch SSA-S2P ANSI INCITS 294-1996

69 0 2208 08A0h SIP (no version claimed)

69 27 2235 08BBh SIP T10/0856-D revision 10

69 28 2236 08BCh SIP ANSI INCITS 292-1997

70 0 2240 08C0h FCP (no version claimed)

70 27 2267 08DBh FCP T10/0993-D revision 12

70 28 2268 08DCh FCP ANSI INCITS 269-1996

71 0 2272 08E0h SBP-2 (no version claimed)

71 27 2299 08FBh SBP-2 T10/1155-D revision 04

71 28 2300 08FCh SBP-2 ANSI INCITS 325-1998

72 0 2304 0900h FCP-2 (no version claimed)

72 1 2305 0901h FCP-2 T10/1144-D revision 4

72 21 2325 0915h FCP-2 T10/1144-D revision 7

72 22 2326 0916h FCP-2 T10/1144-D revision 7a

72 23 2327 0917h FCP-2 ANSI INCITS 350-2003

72 24 2328 0918h FCP-2 T10/1144-D revision 8

73 0 2336 0920h SST (no version claimed)

73 21 2357 0935h SST T10/1380-D revision 8b

74 0 2368 0940h SRP (no version claimed)

Working Draft SCSI Primary Commands - 4 (SPC-4) 927

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.18 — Version descriptor assignments (part 8 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

74 20 2388 0954h SRP T10/1415-D revision 10

74 21 2389 0955h SRP T10/1415-D revision 16a

74 28 2396 095Ch SRP ANSI INCITS 365-2002

75 0 2400 0960h iSCSI (no version claimed)

75 1 to 31 2401 0961h
to to iSCSI (versions as described via RFC 7144)
2431 097Fh

76 0 2432 0980h SBP-3 (no version claimed)

76 2 2434 0982h SBP-3 T10/1467-D revision 1f

76 20 2452 0994h SBP-3 T10/1467-D revision 3

76 26 2458 099Ah SBP-3 T10/1467-D revision 4

76 27 2459 099Bh SBP-3 T10/1467-D revision 5

76 28 2460 099Ch SBP-3 ANSI INCITS 375-2004

78 0 2496 09C0h ADP (no version claimed)

79 0 2528 09E0h ADT (no version claimed)

79 25 2553 09F9h ADT T10/1557-D revision 11

79 26 2554 09FAh ADT T10/1557-D revision 14

79 29 2557 09FDh ADT ANSI INCITS 406-2005

80 0 2560 0A00h FCP-3 (no version claimed)

80 7 2567 0A07h FCP-3 T10/1560-D revision 3f

80 15 2575 0A0Fh FCP-3 T10/1560-D revision 4

80 17 2577 0A11h FCP-3 ANSI INCITS 416-2006

80 28 2588 0A1Ch FCP-3 ISO/IEC 14776-223

81 0 2592 0A20h ADT-2 (no version claimed)

81 2 2594 0A22h ADT-2 T10/1742-D revision 06

81 7 2599 0A27h ADT-2 T10/1742-D revision 08

81 8 2600 0A28h ADT-2 T10/1742-D revision 09

81 11 2603 0A2Bh ADT-2 ANSI INCITS 472-2011

82 0 2624 0A40h FCP-4 (no version claimed)

82 2 2626 0A42h FCP-4 T10/1828-D revision 01

928 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.18 — Version descriptor assignments (part 9 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

82 4 2628 0A44h FCP-4 T10/1828-D revision 02

82 5 2629 0A45h FCP-4 T10/1828-D revision 02b

82 6 2630 0A46h FCP-4 ANSI INCITS 481-2012

85 0 2720 0AA0h SPI (no version claimed)

85 25 2745 0AB9h SPI T10/0855-D revision 15a

85 26 2746 0ABAh SPI ANSI INCITS 253-1995

85 27 2747 0ABBh SPI T10/0855-D revision 15a with SPI Amnd revision 3a

85 28 2748 0ABCh SPI ANSI INCITS 253-1995 with SPI Amnd ANSI INCITS
253/AM1-1998

86 0 2752 0AC0h Fast-20 (no version claimed)

86 27 2779 0ADBh Fast-20 T10/1071 revision 06

86 28 2780 0ADCh Fast-20 ANSI INCITS 277-1996

87 0 2784 0AE0h SPI-2 (no version claimed)

87 27 2811 0AFBh SPI-2 T10/1142-D revision 20b

87 28 2812 0AFCh SPI-2 ANSI INCITS 302-1999

88 0 2816 0B00h SPI-3 (no version claimed)

88 24 2840 0B18h SPI-3 T10/1302-D revision 10

88 25 2841 0B19h SPI-3 T10/1302-D revision 13a

88 26 2842 0B1Ah SPI-3 T10/1302-D revision 14

88 28 2844 0B1Ch SPI-3 ANSI INCITS 336-2000

89 0 2848 0B20h EPI (no version claimed)

89 27 2875 0B3Bh EPI T10/1134 revision 16

89 28 2876 0B3Ch EPI ANSI INCITS TR-23 1999

90 0 2880 0B40h SPI-4 (no version claimed)

90 20 2900 0B54h SPI-4 T10/1365-D revision 7

90 21 2901 0B55h SPI-4 T10/1365-D revision 9

90 22 2902 0B56h SPI-4 ANSI INCITS 362-2002

90 25 2905 0B59h SPI-4 T10/1365-D revision 10

91 0 2912 0B60h SPI-5 (no version claimed)

Working Draft SCSI Primary Commands - 4 (SPC-4) 929

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.18 — Version descriptor assignments (part 10 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

91 25 2937 0B79h SPI-5 T10/1525-D revision 3

91 26 2938 0B7Ah SPI-5 T10/1525-D revision 5

91 27 2939 0B7Bh SPI-5 T10/1525-D revision 6

91 28 2940 0B7Ch SPI-5 ANSI INCITS 367-2003

95 0 3040 0BE0h SAS (no version claimed)

95 1 3041 0BE1h SAS T10/1562-D revision 01

95 21 3061 0BF5h SAS T10/1562-D revision 03

95 26 3066 0BFAh SAS T10/1562-D revision 04

95 27 3067 0BFBh SAS T10/1562-D revision 04

95 28 3068 0BFCh SAS T10/1562-D revision 05

95 29 3069 0BFDh SAS ANSI INCITS 376-2003

96 0 3072 0C00h SAS-1.1 (no version claimed)

96 7 3079 0C07h SAS-1.1 T10/1601-D revision 9

96 15 3087 0C0Fh SAS-1.1 T10/1601-D revision 10

96 17 3089 0C11h SAS-1.1 ANSI INCITS 417-2006

96 18 3090 0C12h SAS-1.1 ISO/IEC 14776-151

97 0 3104 0C20h SAS-2 (no version claimed)

97 3 3107 0C23h SAS-2 T10/1760-D revision 14

97 7 3111 0C27h SAS-2 T10/1760-D revision 15

97 8 3112 0C28h SAS-2 T10/1760-D revision 16

97 10 3114 0C2Ah SAS-2 ANSI INCITS 457-2010

98 0 3136 0C40h SAS-2.1 (no version claimed)

98 8 3144 0C48h SAS-2.1 T10/2125-D revision 04

98 10 3146 0C4Ah SAS-2.1 T10/2125-D revision 06

98 11 3147 0C4Bh SAS-2.1 T10/2125-D revision 07

98 14 3150 0C4Eh SAS-2.1 ANSI INCITS 478-2011

98 15 3151 0C4Fh SAS-2.1 ANSI INCITS 478-2011 w/ Amnd 1 ANSI INCITS

478/AM1-2014

99 0 3168 0C60h SAS-3 (no version claimed)

930 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.18 — Version descriptor assignments (part 11 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

99 3 3171 0C63h SAS-3 T10/BSR INCITS 519 revision 05a

99 5 3173 0C65h SAS-3 T10/BSR INCITS 519 revision 06

100 0 3200 0C80h SAS-4 (no version claimed)

105 0 3360 0D20h FC-PH (no version claimed)

105 27 3387 0D3Bh FC-PH ANSI INCITS 230-1994

105 28 3388 0D3Ch FC-PH ANSI INCITS 230-1994 with Amnd 1 ANSI INCITS
230/AM1-1996

106 0 3392 0D40h FC-AL (no version claimed)

106 28 3420 0D5Ch FC-AL ANSI INCITS 272-1996

107 0 3424 0D60h FC-AL-2 (no version claimed)

107 1 3425 0D61h FC-AL-2 T11/1133-D revision 7.0

107 3 3427 0D63h FC-AL-2 ANSI INCITS 332-1999 with AM1-2003 &
AM2-2006

107 4 3428 0D64h FC-AL-2 ANSI INCITS 332-1999 with Amnd 2 AM2-2006

107 5 3429 0D65h FC-AL-2 ISO/IEC 14165-122 with AM1 & AM2

107 28 3452 0D7Ch FC-AL-2 ANSI INCITS 332-1999

107 29 3453 0D7Dh FC-AL-2 ANSI INCITS 332-1999 with Amnd 1 AM1-2003

108 0 3456 0D80h FC-PH-3 (no version claimed)

108 28 3484 0D9Ch FC-PH-3 ANSI INCITS 303-1998

109 0 3488 0DA0h FC-FS (no version claimed)

109 23 3511 0DB7h FC-FS T11/1331-D revision 1.2

109 24 3512 0DB8h FC-FS T11/1331-D revision 1.7

109 28 3516 0DBCh FC-FS ANSI INCITS 373-2003

109 29 3517 0DBDh FC-FS ISO/IEC 14165-251

110 0 3520 0DC0h FC-PI (no version claimed)

110 28 3548 0DDCh FC-PI ANSI INCITS 352-2002

111 0 3552 0DE0h FC-PI-2 (no version claimed)

111 2 3554 0DE2h FC-PI-2 T11/1506-D revision 5.0

111 4 3556 0DE4h FC-PI-2 ANSI INCITS 404-2006

112 0 3584 0E00h FC-FS-2 (no version claimed)

Working Draft SCSI Primary Commands - 4 (SPC-4) 931

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.18 — Version descriptor assignments (part 12 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

112 2 3586 0E02h FC-FS-2 ANSI INCITS 242-2007

112 3 3587 0E03h FC-FS-2 ANSI INCITS 242-2007 with AM1 ANSI INCITS
242/AM1-2007

113 0 3616 0E20h FC-LS (no version claimed)

113 1 3617 0E21h FC-LS T11/1620-D revision 1.62

113 9 3625 0E29h FC-LS ANSI INCITS 433-2007

114 0 3648 0E40h FC-SP (no version claimed)

114 2 3650 0E42h FC-SP T11/1570-D revision 1.6

114 5 3653 0E45h FC-SP ANSI INCITS 426-2007

115 0 3680 0E60h FC-PI-3 (no version claimed)

115 2 3682 0E62h FC-PI-3 T11/1625-D revision 2.0

115 8 3688 0E68h FC-PI-3 T11/1625-D revision 2.1

115 10 3690 0E6Ah FC-PI-3 T11/1625-D revision 4.0

115 14 3694 0E6Eh FC-PI-3 ANSI INCITS 460-2011

116 0 3712 0E80h FC-PI-4 (no version claimed)

116 2 3714 0E82h FC-PI-4 T11/1647-D revision 8.0

116 8 3720 0E88h FC-PI-4 ANSI INCITS 450-2009

117 0 3744 0EA0h FC 10GFC (no version claimed)

117 2 3746 0EA2h FC 10GFC ANSI INCITS 364-2003

117 3 3747 0EA3h FC 10GFC ISO/IEC 14165-116

117 5 3749 0EA5h FC 10GFC ISO/IEC 14165-116 with AM1

117 6 3750 0EA6h FC 10GFC ANSI INCITS 364-2003 with AM1 ANSI INCITS
364/AM1-2007

118 0 3776 0EC0h FC-SP-2 (no version claimed)

119 0 3808 0EE0h FC-FS-3 (no version claimed)

119 2 3810 0EE2h FC-FS-3 T11/1861-D revision 0.9

119 7 3815 0EE7h FC-FS-3 T11/1861-D revision 1.0

119 9 3817 0EE9h FC-FS-3 T11/1861-D revision 1.10

119 11 3819 0EEBh FC-FS-3 ANSI INCITS 470-2011

120 0 3840 0F00h FC-LS-2 (no version claimed)

932 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.18 — Version descriptor assignments (part 13 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

120 3 3843 0F03h FC-LS-2 T11/2103-D revision 2.11

120 5 3845 0F05h FC-LS-2 T11/2103-D revision 2.21

120 7 3847 0F07h FC-LS-2 ANSI INCITS 477-2011

121 0 3872 0F20h FC-PI-5 (no version claimed)

121 7 3879 0F27h FC-PI-5 T11/2118-D revision 2.00

121 8 3880 0F28h FC-PI-5 T11/2118-D revision 3.00

121 10 3882 0F2Ah FC-PI-5 T11/2118-D revision 6.00

121 11 3883 0F2Bh FC-PI-5 T11/2118-D revision 6.10

121 14 3886 0F2Eh FC-PI-5 ANSI INCITS 479-2011

122 0 3904 0F40h FC-PI-6 (no version claimed)

123 0 3936 0F60h FC-FS-4 (no version claimed)

124 0 3968 0F80h FC-LS-3 (no version claimed)

149 0 4768 12A0h FC-SCM (no version claimed)

149 3 4771 12A3h FC-SCM T11/1824DT revision 1.0

149 5 4773 12A5h FC-SCM T11/1824DT revision 1.1

149 7 4775 12A7h FC-SCM T11/1824DT revision 1.4

149 10 4778 12AAh FC-SCM INCITS TR-47 2012

150 0 4800 12C0h FC-DA-2 (no version claimed)

150 3 4803 12C3h FC-DA-2 T11/1870DT revision 1.04

150 5 4805 12C5h FC-DA-2 T11/1870DT revision 1.06

150 9 4809 12C9h FC-DA-2 INCITS TR-49 2012

151 0 4832 12E0h FC-DA (no version claimed)

151 2 4834 12E2h FC-DA T11/1513-DT revision 3.1

151 8 4840 12E8h FC-DA ANSI INCITS TR-36 2004

151 9 4841 12E9h FC-DA ISO/IEC 14165-341

152 0 4864 1300h FC-Tape (no version claimed)

152 1 4865 1301h FC-Tape T11/1315 revision 1.16

152 27 4891 131Bh FC-Tape T11/1315 revision 1.17

152 28 4892 131Ch FC-Tape ANSI INCITS TR-24 1999

Working Draft SCSI Primary Commands - 4 (SPC-4) 933

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.18 — Version descriptor assignments (part 14 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

153 0 4896 1320h FC-FLA (no version claimed)

153 27 4923 133Bh FC-FLA T11/1235 revision 7

153 28 4924 133Ch FC-FLA ANSI INCITS TR-20 1998

154 0 4928 1340h FC-PLDA (no version claimed)

154 27 4955 135Bh FC-PLDA T11/1162 revision 2.1

154 28 4956 135Ch FC-PLDA ANSI INCITS TR-19 1998

155 0 4960 1360h SSA-PH2 (no version claimed)

155 27 4987 137Bh SSA-PH2 T10.1/1145-D revision 09c

155 28 4988 137Ch SSA-PH2 ANSI INCITS 293-1996

156 0 4992 1380h SSA-PH3 (no version claimed)

156 27 5019 139Bh SSA-PH3 T10.1/1146-D revision 05b

156 28 5020 139Ch SSA-PH3 ANSI INCITS 307-1998

165 0 5280 14A0h IEEE 1394 (no version claimed)

165 29 5309 14BDh ANSI IEEE 1394-1995

166 0 5312 14C0h IEEE 1394a (no version claimed)

167 0 5344 14E0h IEEE 1394b (no version claimed)

175 0 5600 15E0h ATA/ATAPI-6 (no version claimed)

175 29 5629 15FDh ATA/ATAPI-6 ANSI INCITS 361-2002

176 0 5632 1600h ATA/ATAPI-7 (no version claimed)

176 2 5634 1602h ATA/ATAPI-7 T13/1532-D revision 3

176 28 5660 161Ch ATA/ATAPI-7 ANSI INCITS 397-2005

176 30 5662 161Eh ATA/ATAPI-7 ISO/IEC 24739

177 0 5664 1620h ATA/ATAPI-8 ATA8-AAM (no version claimed)

177 1 5665 1621h ATA/ATAPI-8 ATA8-APT Parallel Transport (no version

claimed)

177 2 5666 1622h ATA/ATAPI-8 ATA8-AST Serial Transport (no version

claimed)

177 3 5667 1623h ATA/ATAPI-8 ATA8-ACS ATA/ATAPI Command Set (no

version claimed)

177 8 5672 1628h ATA/ATAPI-8 ATA8-AAM ANSI INCITS 451-2008

934 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.18 — Version descriptor assignments (part 15 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

177 10 5674 162Ah ATA/ATAPI-8 ATA8-ACS ANSI INCITS 452-2009 w/

Amendment 1

185 8 5928 1728h Universal Serial Bus Specification, Revision 1.1

185 9 5929 1729h Universal Serial Bus Specification, Revision 2.0

185 16 5936 1730h USB Mass Storage Class Bulk-Only Transport, Revision 1.0

186 0 5952 1740h UAS (no version claimed)

186 3 5955 1743h UAS T10/2095-D revision 02

186 7 5959 1747h UAS T10/2095-D revision 04

186 8 5960 1748h UAS ANSI INCITS 471-2010

187 1 5985 1761h ACS-2 (no version claimed)

187 2 5986 1762h ACS-2 ANSI INCITS 482-2013

187 5 5989 1765h ACS-3 (no version claimed)

188 0 6016 1780h UAS-2 (no version claimed)

245 0 7840 1EA0h SAT (no version claimed)

245 7 7847 1EA7h SAT T10/1711-D revision 8

245 11 7851 1EABh SAT T10/1711-D revision 9

245 13 7853 1EADh SAT ANSI INCITS 431-2007

246 0 7872 1EC0h SAT-2 (no version claimed)

246 4 7876 1EC4h SAT-2 T10/1826-D revision 06

246 8 7880 1EC8h SAT-2 T10/1826-D revision 09

246 10 7882 1ECAh SAT-2 ANSI INCITS 465-2010

247 0 7904 1EE0h SAT-3 (no version claimed)

247 2 7906 1EE2h SAT-3 T10/BSR INCITS 517 revision 4

248 0 7936 1F00h SAT-4 (no version claimed)

261 0 8352 20A0h SPL (no version claimed)

261 3 8355 20A3h SPL T10/2124-D revision 6a

261 5 8357 20A5h SPL T10/2124-D revision 7

261 7 8359 20A7h SPL ANSI INCITS 476-2011

261 8 8360 20A8h SPL ANSI INCITS 476-2011 + SPL AM1 INCITS 476/AM1
2012

Working Draft SCSI Primary Commands - 4 (SPC-4) 935

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.18 — Version descriptor assignments (part 16 of 16)

Version
Standard Revision Descriptor Code
Code Code decimal hex Standard

261 10 8362 20AAh SPL ISO/IEC 14776-261:2012

262 0 8384 20C0h SPL-2 (no version claimed)

262 2 8386 20C2h SPL-2 T10/BSR INCITS 505 revision 4

262 4 8388 20C4h SPL-2 T10/BSR INCITS 505 revision 5

262 8 8392 20C8h SPL-2 ANSI INCITS 505-2013

263 0 8416 20E0h SPL-3 (no version claimed)

263 4 8420 20E4h SPL-3 T10/BSR INCITS 492 revision 6

263 6 8422 20E6h SPL-3 T10/BSR INCITS 492 revision 7

264 0 8448 2100h SPL-4 (no version claimed)

271 0 8672 21E0h SOP (no version claimed)

271 4 8676 21E4h SOP T10/BSR INCITS 489 revision 4

271 6 8678 21E6h SOP T10/BSR INCITS 489 revision 5

272 0 8704 2200h PQI (no version claimed)

272 4 8708 2204h PQI T10/BSR INCITS 490 revision 6

272 6 8710 2206h PQI T10/BSR INCITS 490 revision 7

273 0 8736 2220h SOP-2 (no version claimed)

274 0 8768 2240h PQI-2 (no version claimed)

2046 0 65472 FFC0h IEEE 1667 (no version claimed)

2046 1 65473 FFC1h IEEE 1667-2006

2046 2 65474 FFC2h IEEE 1667-2009

936 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.19 shows the guidelines used by T10 when selecting a coded value for a standard.

Table F.19 — Standard code value guidelines (part 1 of 5)

Standard
Code Standard or standards family
0 Version Descriptor Not Supported
1 to 8 Architecture Model
1 SAM
2 SAM-2
3 SAM-3
4 SAM-4
5 SAM-5
9 to 64 Command Set
9 SPC
10 MMC
11 SCC
12 SBC
13 SMC
14 SES
15 SCC-2
16 SSC
17 RBC
18 MMC-2
19 SPC-2
20 OCRW
21 MMC-3
22 obsolete
23 SMC-2
24 SPC-3
25 SBC-2
26 OSD
27 SSC-2
28 obsolete
29 MMC-4
30 ADC

Working Draft SCSI Primary Commands - 4 (SPC-4) 937

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.19 — Standard code value guidelines (part 2 of 5)

Standard
Code Standard or standards family
31 SES-2
32 SSC-3
33 MMC-5
34 OSD-2
35 SPC-4
36 SMC-3
37 ADC-2
38 SBC-3
39 MMC-6
40 ADC-3
41 SSC-4
43 OSD-3
44 SES-3
45 SSC-5
46 SPC-5
47 SFSC
48 SBC-4
49 ZBC
65 to 84 Physical Mapping Protocol
65 SSA-TL2
66 SSA-TL1
67 SSA-S3P
68 SSA-S2P
69 SIP
70 FCP
71 SBP-2
72 FCP-2
73 SST
74 SRP
75 iSCSI
76 SBP-3

938 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.19 — Standard code value guidelines (part 3 of 5)

Standard
Code Standard or standards family
77 obsolete
78 ADP
79 ADT
80 FCP-3
81 ADT-2
82 FCP-4
85 to 94 Parallel SCSI Physical
85 SPI and SPI Amendment
86 Fast-20
87 SPI-2
88 SPI-3
89 EPI
90 SPI-4
91 SPI-5
95 to 104 Serial Attached SCSI
95 SAS
96 SAS-1.1
97 SAS-2
98 SAS-2.1
99 SAS-3
100 SAS-4
105 to 154 Fibre Channel
105 FC-PH and FC-PH Amendment
106 FC-AL
107 FC-AL-2
108 FC-PH-3
109 FC-FS
110 FC-PI
111 FC-PI-2
112 FC-FS-2
113 FC-LS

Working Draft SCSI Primary Commands - 4 (SPC-4) 939

T10/BSR INCITS 513 Revision 37 17 May 2014

Table F.19 — Standard code value guidelines (part 4 of 5)

Standard
Code Standard or standards family
114 FC-SP
115 FC-PI-3
116 FC-PI-4
117 FC 10GFC
118 FC-SP-2
119 FC-FS-3
120 FC-LS-2
121 FC-PI-5
122 FC-PI-6
123 FC-FS-4
124 FC-LS-3
149 FC-SCM
150 FC-DA-2
151 FC-DA
152 FC-Tape
153 FC-FLA
154 FC-PLDA
155 to 164 SSA
155 SSA-PH2
156 SSA-PH3
165 to 174 IEEE 1394
165 IEEE 1394:1995
166 IEEE 1394a
167 IEEE 1394b
175 to 200 ATAPI & USB
175 ATA/ATAPI-6
176 ATA/ATAPI-7
177 ATA/ATAPI-8
185 USB
186 UAS
187 ACS-x

940 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table F.19 — Standard code value guidelines (part 5 of 5)

Standard
Code Standard or standards family
188 UAS-2
201 to 224 Networking
225 to 244 ATM
245 to 260 Translators
245 SAT
246 SAT-2
247 SAT-3
248 SAT-4
261 to 270 SAS Transport Protocols
261 SPL
262 SPL-2
263 SPL-3
264 SPL-4
271 to 290 SCSI over PCI Express Transport Protocols
271 SOP
272 PQI
273 SOP-2
274 PQI-2
291 to 2045 Reserved for Expansion
2046 IEEE 1667
2047 Reserved

Working Draft SCSI Primary Commands - 4 (SPC-4) 941

T10/BSR INCITS 513 Revision 37 17 May 2014

F.10 T10 IEEE binary identifiers

The IEEE binary identifiers assigned to T10 standards are shown in table F.20.

Table F.20 — IEEE binary identifiers assigned by T10

IEEE Binary Identifier T10 Standard

0060 9E01 03E0h SBP (obsolete)
0060 9E01 0483h SBP-2
0060 9E01 04D8h SPC-2
0060 9E01 05BBh SBP-3
0060 9E01 0800h SRP revision 10
0060 9E01 0801h ANSI SRP

942 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Annex G
(Informative)

T10 vendor identification

This annex contains the list of T10 vendor identifications (see table G.1) as of the date of this document. The
purpose of this list is to help avoid redundant usage of T10 vendor identifications. Technical Committee T10 of
Accredited Standards Committee INCITS maintains an informal list of T10 vendor identifications currently in
use. The T10 web site, http://www.t10.org, provides a convenient means to request an identification code. If
problems are encountered using the T10 web site, please contact the chairman of T10 prior to using a new
T10 vendor identification to avoid conflicts.

The information in this annex was complete and accurate at the time of publication. However, the information
is subject to change. Technical Committee T10 of INCITS maintains an electronic copy of this information on
its world wide web site (http://www.t10.org/). In the event that the T10 world wide web site is no longer active,
access may be possible via the INCITS world wide web site (http://www.incits.org), the ANSI world wide web
site (http://www.ansi.org), the IEC site (http://www.iec.ch/), the ISO site (http://www.iso.ch/), or the ISO/IEC
JTC 1 web site (http://www.jtc1.org/).

Table G.1 — T10 vendor identification list (part 1 of 17)

ID Organization
0B4C MOOSIK Ltd.
13FE PHISON
2AI 2AI (Automatisme et Avenir Informatique)
3M 3M Company
3nhtech 3NH Technologies
3PARdata 3PARdata, Inc. (now HP)
A-Max A-Max Technology Co., Ltd
ABSOLUTE Absolute Analysis
ACARD ACARD Technology Corp.
Accusys Accusys INC.
Acer Acer, Inc.
ACL Automated Cartridge Librarys, Inc.
Actifio Actifio
Acuid Acuid Corporation Ltd.
AcuLab AcuLab, Inc. (Tulsa, OK)
ADAPTEC Adaptec (now PMC-Sierra)
ADIC Advanced Digital Information Corporation
ADSI Adaptive Data Systems, Inc. (a Western Digital subsidiary)
ADTX ADTX Co., Ltd.
ADVA ADVA Optical Networking AG
AEM AEM Performance Electronics
AERONICS Aeronics, Inc.
AGFA AGFA
Agilent Agilent Technologies
AIC Advanced Industrial Computer, Inc.
AIPTEK AIPTEK International Inc.
Alcohol Alcohol Soft
ALCOR Alcor Micro, Corp.

Working Draft SCSI Primary Commands - 4 (SPC-4) 943

T10/BSR INCITS 513 Revision 37 17 May 2014

Table G.1 — T10 vendor identification list (part 2 of 17)

ID Organization
AMCC Applied Micro Circuits Corporation
AMCODYNE Amcodyne
Amgeon Amgeon LLC
AMI American Megatrends, Inc.
AMPEX Ampex Data Systems
Amphenol Amphenol
Amtl Tenlon Technology Co.,Ltd
ANAMATIC Anamartic Limited (England)
Ancor Ancor Communications, Inc.
ANCOT ANCOT Corp.
ANDATACO Andataco (now nStor)
andiamo Andiamo Systems, Inc.
ANOBIT Anobit
ANRITSU Anritsu Corporation
ANTONIO Antonio Precise Products Manufactory Ltd.
AoT Art of Technology AG
APPLE Apple Computer, Inc.
ARCHIVE Archive
ARDENCE Ardence Inc
Areca Areca Technology Corporation
Arena MaxTronic International Co., Ltd.
ARIO Ario Data Networks, Inc.
ARISTOS Aristos Logic Corp. (now part of PMC Sierra)
ARK ARK Research Corporation
ARTECON Artecon Inc. (Obs. - now Dot Hill)
Artistic Artistic Licence (UK) Ltd
ARTON Arton Int.
ASACA ASACA Corp.
ASC Advanced Storage Concepts, Inc.
ASPEN Aspen Peripherals
AST AST Research
ASTEK Astek Corporation
ASTK Alcatel STK A/S
ASTUTE Astute Networks, Inc.
AT&T AT&T
ATA SCSI / ATA Translator Software (Organization Not Specified)
ATARI Atari Corporation
ATech ATech electronics
ATG CYG ATG Cygnet Inc.
ATL Quantum|ATL Products
ATTO ATTO Technology Inc.
ATTRATEC Attratech Ltd liab. Co
ATX Alphatronix
AURASEN Aurasen Limited
AVC AVC Technology Ltd
AVIDVIDR AVID Technologies, Inc.
AVR Advanced Vision Research

944 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table G.1 — T10 vendor identification list (part 3 of 17)

ID Organization
AXSTOR AXSTOR
Axxana Axxana Ltd.
BALLARD Ballard Synergy Corp.
Barco Barco
BAROMTEC Barom Technologies Co., Ltd.
Bassett Bassett Electronic Systems Ltd
BDT BDT AG
BECEEM Beceem Communications, Inc
BENQ BENQ Corporation.
BERGSWD Berg Software Design
BEZIER Bezier Systems, Inc.
BHTi Breece Hill Technologies
biodata Biodata Devices SL
BIOS BIOS Corporation
BIR Bio-Imaging Research, Inc.
BiT BiT Microsystems (obsolete, new ID: BITMICRO)
BITMICRO BiT Microsystems, Inc.
Blendlgy Blendology Limited
BLOOMBAS Bloombase Technologies Limited
BlueArc BlueArc Corporation
BME-HVT Broadband Infocommunicatons and Electromagnetic Theory Department
BNCHMARK Benchmark Tape Systems Corporation
Bosch Robert Bosch GmbH
Botman Botmanfamily Electronics
BoxHill Box Hill Systems Corporation (Obs. - now Dot Hill)
BRDGWRKS Bridgeworks Ltd.
BREA BREA Technologies, Inc.
BREECE Breece Hill LLC
BreqLabs BreqLabs Inc.
Broadcom Broadcom Corporation
BROCADE Brocade Communications Systems, Incorporated
BUFFALO BUFFALO INC.
BULL Bull Peripherals Corp.
BUSLOGIC BusLogic Inc.
BVIRTUAL B-Virtual N.V.
CalComp CalComp, A Lockheed Company
CALCULEX CALCULEX, Inc.
CALIPER Caliper (California Peripheral Corp.)
CAMBEX Cambex Corporation
CAMEOSYS Cameo Systems Inc.
CANDERA Candera Inc.
CAPTION CAPTION BANK
CAST Advanced Storage Tech
CATALYST Catalyst Enterprises
CCDISK iSCSI Cake
CDC Control Data or MPI
CDP Columbia Data Products

Working Draft SCSI Primary Commands - 4 (SPC-4) 945

T10/BSR INCITS 513 Revision 37 17 May 2014

Table G.1 — T10 vendor identification list (part 4 of 17)

ID Organization
Celsia A M Bromley Limited
CenData Central Data Corporation
Cereva Cereva Networks Inc.
CERTANCE Certance
Chantil Chantil Technology
CHEROKEE Cherokee Data Systems
CHINON Chinon
CHRISTMA Christmann Informationstechnik + Medien GmbH & Co KG
CIE&YED YE Data, C.Itoh Electric Corp.
CIPHER Cipher Data Products
Ciprico Ciprico, Inc.
CIRRUSL Cirrus Logic Inc.
CISCO Cisco Systems, Inc.
CLOVERLF Cloverleaf Communications, Inc
CLS Celestica
CMD CMD Technology Inc.
CMTechno CMTech
CNGR SFW Congruent Software, Inc.
CNSi Chaparral Network Storage, Inc.
CNT Computer Network Technology
COBY Coby Electronics Corporation, USA
COGITO Cogito
COMPAQ Compaq Computer Corporation (now HP)
COMPELNT Compellent Technologies, Inc. (now Dell)
COMPORT Comport Corp.
COMPSIG Computer Signal Corporation
COMPTEX Comptex Pty Limited
CONNER Conner Peripherals
COPANSYS COPAN SYSTEMS INC
CORAID Coraid, Inc
CORE Core International, Inc.
CORERISE Corerise Electronics
COVOTE Covote GmbH & Co KG
COWON COWON SYSTEMS, Inc.
CPL Cross Products Ltd
CPU TECH CPU Technology, Inc.
CREO Creo Products Inc.
CROSFLD Crosfield Electronics (now FujiFilm Electonic Imaging Ltd)
CROSSRDS Crossroads Systems, Inc.
crosswlk Crosswalk, Inc.
CSCOVRTS Cisco - Veritas
CSM, INC Computer SM, Inc.
Cunuqui CUNUQUI SLU
CYBERNET Cybernetics
Cygnal Dekimo
D Bit Digby’s Bitpile, Inc. DBA D Bit
DALSEMI Dallas Semiconductor

946 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table G.1 — T10 vendor identification list (part 5 of 17)

ID Organization
DANEELEC Dane-Elec
DANGER Danger Inc.
DAT-MG DAT Manufacturers Group
Data Com Data Com Information Systems Pty. Ltd.
DATABOOK Databook, Inc.
DATACOPY Datacopy Corp.
DataCore DataCore Software Corporation
DataG DataGravity
DATAPT Datapoint Corp.
DATARAM Dataram Corporation
DAVIS Daviscomms (S) Pte Ltd
DDN DataDirect Networks, Inc.
DDRDRIVE DDRdrive LLC
DE Dimension Engineering LLC
DEC Digital Equipment Corporation (now HP)
DEI Digital Engineering, Inc.
DELL Dell, Inc.
Dell(tm) Dell, Inc
DELPHI Delphi Data Div. of Sparks Industries, Inc.
DENON Denon/Nippon Columbia
DenOptix DenOptix, Inc.
DEST DEST Corp.
DFC DavioFranke.com
DGC Data General Corp.
DIGIDATA Digi-Data Corporation
DigiIntl Digi International
Digital Digital Equipment Corporation (now HP)
DILOG Distributed Logic Corp.
DISC Document Imaging Systems Corp.
DiscSoft Disc Soft Ltd
DLNET Driveline
DNS Data and Network Security
DNUK Digital Networks Uk Ltd
DotHill Dot Hill Systems Corp.
DP Dell, Inc.
DPT Distributed Processing Technology
Drewtech Drew Technologies, Inc.
DROBO Data Robotics, Inc.
DSC DigitalStream Corporation
DSI Data Spectrum, Inc.
DSM Deterner Steuerungs- und Maschinenbau GmbH & Co.
DSNET Cleversafe, Inc.
DT Double-Take Software, INC.
DTC QUME Data Technology Qume
DXIMAGIN DX Imaging
E-Motion E-Motion LLC
EARTHLAB EarthLabs

Working Draft SCSI Primary Commands - 4 (SPC-4) 947

T10/BSR INCITS 513 Revision 37 17 May 2014

Table G.1 — T10 vendor identification list (part 6 of 17)

ID Organization
EarthLCD Earth Computer Technologies, Inc.
ECCS ECCS, Inc.
ECMA European Computer Manufacturers Association
EDS Embedded Data Systems
ELE Intl ELE International
ELEGANT Elegant Invention, LLC
Elektron Elektron Music Machines MAV AB
elipsan Elipsan UK Ltd.
Elms Elms Systems Corporation
ELSE ELSE Ltd.
ELSEC Littlemore Scientific
EMASS EMASS, Inc.
EMC EMC Corp.
EMiT EMiT Conception Eletronique
EMTEC EMTEC Magnetics
EMULEX Emulex
ENERGY-B Energybeam Corporation
ENGENIO Engenio Information Technologies, Inc.
ENMOTUS Enmotus Inc
Entacore Entacore
EPOS EPOS Technologies Ltd.
EPSON Epson
EQLOGIC EqualLogic
Eris/RSI RSI Systems, Inc.
ETERNE EterneData Technology Co.,Ltd.(China PRC.)
EuroLogc Eurologic Systems Limited (now part of PMC Sierra)
evolve Evolution Technologies, Inc
EXABYTE Exabyte Corp. (now part of Tandberg)
EXATEL Exatelecom Co., Ltd.
EXAVIO Exavio, Inc.
Exsequi Exsequi Ltd
Exxotest Annecy Electronique
FAIRHAVN Fairhaven Health, LLC
FALCON FalconStor, Inc.
FFEILTD FujiFilm Electonic Imaging Ltd
Fibxn Fiberxon, Inc.
FID First International Digital, Inc.
FILENET FileNet Corp.
FirmFact Firmware Factory Ltd
FLYFISH Flyfish Technologies
FOXCONN Foxconn Technology Group
FRAMDRV FRAMEDRIVE Corp.
FREECION Nable Communications, Inc.
FRESHDTK FreshDetect GmbH
FSC Fujitsu Siemens Computers
FTPL Frontline Technologies Pte Ltd
FUJI Fuji Electric Co., Ltd. (Japan)

948 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table G.1 — T10 vendor identification list (part 7 of 17)

ID Organization
FUJIFILM Fuji Photo Film, Co., Ltd.
FUJITSU Fujitsu
FUNAI Funai Electric Co., Ltd.
FUSIONIO Fusion-io Inc.
FUTURED Future Domain Corp.
G&D Giesecke & Devrient GmbH
G.TRONIC Globaltronic - Electronica e Telecomunicacoes, S.A.
Gadzoox Gadzoox Networks, Inc. (now part of Broadcom)
Gammaflx Gammaflux L.P.
GDI Generic Distribution International
GEMALTO gemalto
Gen_Dyn General Dynamics
Generic Generic Technology Co., Ltd.
GENSIG General Signal Networks
GEO Green Energy Options Ltd
GIGATAPE GIGATAPE GmbH
GIGATRND GigaTrend Incorporated
Global Global Memory Test Consortium
Gnutek Gnutek Ltd.
Goidelic Goidelic Precision, Inc.
GoldKey GoldKey Security Corporation
GoldStar LG Electronics Inc.
GORDIUS Gordius
GOULD Gould
HAGIWARA Hagiwara Sys-Com Co., Ltd.
HAPP3 Inventec Multimedia and Telecom co., ltd
HDS Horizon Data Systems, Inc.
Heydays Mazo Technology Co., Ltd.
HGST HGST a Western Digital Company
HI-TECH HI-TECH Software Pty. Ltd.
HITACHI Hitachi America Ltd or Nissei Sangyo America Ltd
HL-DT-ST Hitachi-LG Data Storage, Inc.
HONEYWEL Honeywell Inc.
Hoptroff HexWax Ltd
HORIZONT Horizontigo Software
HP Hewlett Packard
HPQ Hewlett Packard
HUASY Huawei Symantec Technologies Co., Ltd.
HYUNWON HYUNWON inc
i-cubed i-cubed ltd.
IBM International Business Machines
Icefield Icefield Tools Corporation
Iceweb Iceweb Storage Corp
ICL ICL
ICP ICP vortex Computersysteme GmbH
IDE International Data Engineering, Inc.
IDG Interface Design Group

Working Draft SCSI Primary Commands - 4 (SPC-4) 949

T10/BSR INCITS 513 Revision 37 17 May 2014

Table G.1 — T10 vendor identification list (part 8 of 17)

ID Organization
IET ISCSI ENTERPRISE TARGET
IFT Infortrend Technology, Inc.
IGR Intergraph Corp.
IMAGINE Imagine Communications Corp.
IMAGO IMAGO SOFTWARE SL
IMATION Imation
IMPLTD Integrated Micro Products Ltd.
IMPRIMIS Imprimis Technology Inc.
INCIPNT Incipient Technologies Inc.
INCITS InterNational Committee for Information Technology
INDCOMP Industrial Computing Limited
Indigita Indigita Corporation
INITIO Initio Corporation
INRANGE INRANGE Technologies Corporation
Insight L-3 Insight Technology Inc
INSITE Insite Peripherals
integrix Integrix, Inc.
INTEL Intel Corporation
Intransa Intransa, Inc.
IOC I/O Concepts, Inc.
iofy iofy Corporation
IOMEGA Iomega
IOT IO Turbine, Inc.
iPaper intelliPaper, LLC
iqstor iQstor Networks, Inc.
iQue iQue
ISi Information Storage inc.
Isilon Isilon Systems, Inc.
ISO International Standards Organization
iStor iStor Networks, Inc.
ITC International Tapetronics Corporation
iTwin iTwin Pte Ltd
IVIVITY iVivity, Inc.
IVMMLTD InnoVISION Multimedia Ltd.
JABIL001 Jabil Circuit
JETWAY Jetway Information Co., Ltd
JMR JMR Electronics Inc.
JOFEMAR Jofemar
JOLLYLOG Jolly Logic
JPC Inc. JPC Inc.
JSCSI jSCSI Project
Juniper Juniper Networks
JVC JVC Information Products Co.
KASHYA Kashya, Inc.
KENNEDY Kennedy Company
KENWOOD KENWOOD Corporation
KEWL Shanghai KEWL Imp&Exp Co., Ltd.

950 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table G.1 — T10 vendor identification list (part 9 of 17)

ID Organization
Key Tech Key Technologies, Inc
KMNRIO Kaminario Technologies Ltd.
KODAK Eastman Kodak
KONAN Konan
koncepts koncepts International Ltd.
KONICA Konica Japan
KOVE KOVE
KSCOM KSCOM Co. Ltd.,
KUDELSKI Nagravision SA - Kudelski Group
Kyocera Kyocera Corporation
Lapida Gonmalo Electronics
LAPINE Lapine Technology
LASERDRV LaserDrive Limited
LASERGR Lasergraphics, Inc.
LeapFrog LeapFrog Enterprises, Inc.
LEFTHAND LeftHand Networks (now HP)
Leica Leica Camera AG
Lexar Lexar Media, Inc.
LEYIO LEYIO
LG LG Electronics Inc.
LGE LG Electronics Inc.
LIBNOVA LIBNOVA, SL Digital Preservation Systems
LION Lion Optics Corporation
LMS Laser Magnetic Storage International Company
LoupTech Loup Technologies, Inc.
LSI LSI Corp. (was LSI Logic Corp.)
LSILOGIC LSI Logic Storage Systems, Inc.
LTO-CVE Linear Tape - Open, Compliance Verification Entity
LUXPRO Luxpro Corporation
MacroSAN MacroSAN Technologies Co., Ltd.
Malakite Malachite Technologies (New VID is: Sandial)
MarcBoon marcboon.com
Marner Marner Storage Technologies, Inc.
MARVELL Marvell Semiconductor, Inc.
Matrix Matrix Orbital Corp.
MATSHITA Matsushita
MAXELL Hitachi Maxell, Ltd.
MAXIM-IC Maxim Integrated Products
MaxOptix Maxoptix Corp.
MAXSTRAT Maximum Strategy, Inc.
MAXTOR Maxtor Corp.
MaXXan MaXXan Systems, Inc.
MAYCOM maycom Co., Ltd.
MBEAT K-WON C&C Co.,Ltd
MCC Measurement Computing Corporation
McDATA McDATA Corporation
MCUBE Mcube Technology Co., Ltd.

Working Draft SCSI Primary Commands - 4 (SPC-4) 951

T10/BSR INCITS 513 Revision 37 17 May 2014

Table G.1 — T10 vendor identification list (part 10 of 17)

ID Organization
MDI Micro Design International, Inc.
MEADE Meade Instruments Corporation
mediamat mediamatic
MegaElec Mega Electronics Ltd
MEII Mountain Engineering II, Inc.
MELA Mitsubishi Electronics America
MELCO Mitsubishi Electric (Japan)
mellanox Mellanox Technologies Ltd.
MEMOREX Memorex Telex Japan Ltd.
MEMREL Memrel Corporation
MEMTECH MemTech Technology
MendoCno Mendocino Software
MERIDATA Oy Meridata Finland Ltd
METHODEI Methode Electronics India pvt ltd
METRUM Metrum, Inc.
MHTL Matsunichi Hi-Tech Limited
MICROBTX Microbotics Inc.
Microchp Microchip Technology, Inc.
MICROLIT Microlite Corporation
MICRON Micron Technology, Inc.
MICROP Micropolis
MICROTEK Microtek Storage Corp
Minitech Minitech (UK) Limited
Minolta Minolta Corporation
MINSCRIB Miniscribe
MiraLink MiraLink Corporation
Mirifica Mirifica s.r.l.
MITSUMI Mitsumi Electric Co., Ltd.
MKM Mitsubishi Kagaku Media Co., LTD.
Mobii Mobii Systems (Pty.) Ltd.
MOL Petrosoft Sdn. Bhd.
MOSAID Mosaid Technologies Inc.
MOTOROLA Motorola
MP-400 Daiwa Manufacturing Limited
MPC MPC Corporation
MPCCORP MPC Computers
MPEYE Touchstone Technology Co., Ltd
MPIO DKT Co.,Ltd
MPM Mitsubishi Paper Mills, Ltd.
MPMan MPMan.com, Inc.
MSFT Microsoft Corporation
MSI Micro-Star International Corp.
MST Morning Star Technologies, Inc.
MSystems M-Systems Flash Disk Pioneers
MTI MTI Technology Corporation
MTNGATE MountainGate Data Systems
MXI Memory Experts International

952 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table G.1 — T10 vendor identification list (part 11 of 17)

ID Organization
nac nac Image Technology Inc.
NAGRA Nagravision SA - Kudelski Group
NAI North Atlantic Industries
NAKAMICH Nakamichi Corporation
NatInst National Instruments
NatSemi National Semiconductor Corp.
NCITS InterNational Committee for Information Technology Standards (INCITS)
NCL NCL America
NCR NCR Corporation
NDBTECH NDB Technologie Inc.
Neartek Neartek, Inc.
NEC NEC
NETAPP NetApp, Inc. (was Network Appliance)
NetBSD The NetBSD Foundation
Netcom Netcom Storage
NETENGIN NetEngine, Inc.
NEWISYS Newisys Data Storage
Newtech Newtech Co., Ltd.
NEXSAN Nexsan Technologies, Ltd.
NFINIDAT Infinidat Ltd.
NHR NH Research, Inc.
Nike Nike, Inc.
Nimble Nimble Storage
NISCA NISCA Inc.
NISHAN Nishan Systems Inc.
Nitz Nitz Associates, Inc.
NKK NKK Corp.
NRC Nakamichi Research Corporation
NSD Nippon Systems Development Co.,Ltd.
NSM NSM Jukebox GmbH
nStor nStor Technologies, Inc.
NT Northern Telecom
NUCONNEX NuConnex
NUSPEED NuSpeed, Inc.
NVIDIA NVIDIA Corporation
NVMe NVM Express Working Group
OAI Optical Access International
OCE Oce Graphics
OHDEN Ohden Co., Ltd.
OKI OKI Electric Industry Co.,Ltd (Japan)
Olidata Olidata S.p.A.
OMI Optical Media International
OMNIFI Rockford Corporation - Omnifi Media
OMNIS OMNIS Company (FRANCE)
Ophidian Ophidian Designs
opslag Tyrone Systems
Optelec Optelec BV

Working Draft SCSI Primary Commands - 4 (SPC-4) 953

T10/BSR INCITS 513 Revision 37 17 May 2014

Table G.1 — T10 vendor identification list (part 12 of 17)

ID Organization
Optiarc Sony Optiarc Inc.
OPTIMEM Cipher/Optimem
OPTOTECH Optotech
ORACLE Oracle Corporation
ORANGE Orange Micro, Inc.
ORCA Orca Technology
Origin Origin Energy
OSI Optical Storage International
OSNEXUS OS NEXUS, Inc.
OTL OTL Engineering
OVERLAND Overland Storage Inc.
pacdigit Pacific Digital Corp
Packard Parkard Bell
Panasas Panasas, Inc.
PARALAN Paralan Corporation
PASCOsci Pasco Scientific
PATHLGHT Pathlight Technology, Inc.
PCS Pro Charging Systems, LLC
PerStor Perstor
PERTEC Pertec Peripherals Corporation
PFTI Performance Technology Inc.
PFU PFU Limited
Phigment Phigment Technologies
PHILIPS Philips Electronics
PICO Packard Instrument Company
PIK TECHNILIENT & MCS
Pillar Pillar Data Systems
PIONEER Pioneer Electronic Corp.
Pirus Pirus Networks
PIVOT3 Pivot3, Inc.
PLASMON Plasmon Data
Pliant Pliant Technology, Inc.
PMCSIERA PMC-Sierra
PME Precision Measurement Engineering
PNNMed PNN Medical SA
POKEN Poken SA
POLYTRON PT. HARTONO ISTANA TEKNOLOGI
PRAIRIE PrairieTek
PREPRESS PrePRESS Solutions
PRESOFT PreSoft Architects
PRESTON Preston Scientific
PRIAM Priam
PRIMAGFX Primagraphics Ltd
PRIMOS Primos
PROCOM Procom Technology
PROLIFIC Prolific Technology Inc.
PROMISE PROMISE TECHNOLOGY, Inc

954 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table G.1 — T10 vendor identification list (part 13 of 17)

ID Organization
PROSTOR ProStor Systems, Inc.
PROSUM PROSUM
PROWARE Proware Technology Corp.
PTI Peripheral Technology Inc.
PTICO Pacific Technology International
PURE PURE Storage
Qi-Hardw Qi Hardware
QIC Quarter-Inch Cartridge Drive Standards, Inc.
QLogic QLogic Corporation
QNAP QNAP Systems
Qsan QSAN Technology, Inc.
QUALSTAR Qualstar
QUANTEL Quantel Ltd.
QUANTUM Quantum Corp.
QUIX Quix Computerware AG
R-BYTE R-Byte, Inc.
RACALREC Racal Recorders
RADITEC Radikal Technologies Deutschland GmbH
RADSTONE Radstone Technology
RASSYS Rasilient Systems Inc.
RASVIA Rasvia Systems, Inc.
rave-mp Go Video
RDKMSTG MMS Dipl. Ing. Rolf-Dieter Klein
Readboy Readboy Ltd Co.
Realm Realm Systems
realtek Realtek Semiconductor Corp.
REDUXIO Reduxio Systems Ltd.
REKA REKA HEALTH PTE LTD
RELDATA RELDATA Inc
RENAGmbH RENA GmbH
ReThinkM RETHINK MEDICAL, INC
Revivio Revivio, Inc.
RGBLaser RGB Lasersysteme GmbH
RGI Raster Graphics, Inc.
RHAPSODY Rhapsody Networks, Inc.
RHS Racal-Heim Systems GmbH
RICOH Ricoh
RODIME Rodime
Royaltek RoyalTek company Ltd.
RPS RPS
RTI Reference Technology
S-D Sauer-Danfoss
S-flex Storageflex Inc
S-SYSTEM S-SYSTEM
S1 storONE
SAMSUNG Samsung Electronics Co., Ltd.
SAN Storage Area Networks, Ltd.

Working Draft SCSI Primary Commands - 4 (SPC-4) 955

T10/BSR INCITS 513 Revision 37 17 May 2014

Table G.1 — T10 vendor identification list (part 14 of 17)

ID Organization
Sandial Sandial Systems, Inc.
SanDisk SanDisk Corporation
SANKYO Sankyo Seiki
SANRAD SANRAD Inc.
SANYO SANYO Electric Co., Ltd.
SC.Net StorageConnections.Net
SCALE Scale Computing, Inc.
SCIENTEK SCIENTEK CORP
SCInc. Storage Concepts, Inc.
SCREEN Dainippon Screen Mfg. Co., Ltd.
SDI Storage Dimensions, Inc.
SDS Solid Data Systems
SEAC SeaChange International, Inc.
SEAGATE Seagate
SEAGRAND SEAGRAND In Japan
Seanodes Seanodes
Sec. Key SecureKey Technologies Inc.
SEQUOIA Sequoia Advanced Technologies, Inc.
SGI Silicon Graphics International
Shinko Shinko Electric Co., Ltd.
SIEMENS Siemens
SigmaTel SigmaTel, Inc.
SII Seiko Instruments Inc.
SIMPLE SimpleTech, Inc. (Obs - now STEC, Inc.)
SIVMSD IMAGO SOFTWARE SL
SKhynix SK hynix Inc.
SLCNSTOR SiliconStor, Inc.
SLI Sierra Logic, Inc.
SMCI Super Micro Computer, Inc.
SmrtStor Smart Storage Systems
SMS Scientific Micro Systems/OMTI
SMSC SMSC Storage, Inc.
SMX Smartronix, Inc.
SNYSIDE Sunnyside Computing Inc.
SoftLock Softlock Digital Security Provider
SolidFir SolidFire, Inc.
SONIC Sonic Solutions
SoniqCas SoniqCast
SONY Sony Corporation Japan
SOUL Soul Storage Technology (Wuxi) Co., Ltd
SPD Storage Products Distribution, Inc.
SPECIAL Special Computing Co.
SPECTRA Spectra Logic, a Division of Western Automation Labs, Inc.
SPERRY Sperry (now Unisys Corp.)
Spintso Spintso International AB
STARBORD Starboard Storage Systems, Inc.
STARWIND StarWind Software, Inc.

956 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table G.1 — T10 vendor identification list (part 15 of 17)

ID Organization
STEC STEC, Inc.
Sterling Sterling Diagnostic Imaging, Inc.
STK Storage Technology Corporation
STNWOOD Stonewood Group
STONEFLY StoneFly Networks, Inc.
STOR StorageNetworks, Inc.
STORAPP StorageApps, Inc. (now HP)
STORCOMP Storage Computer Corporation
STORM Storm Technology, Inc.
StorMagc StorMagic
Stratus Stratus Technologies
StrmLgc StreamLogic Corp.
SUMITOMO Sumitomo Electric Industries, Ltd.
SUN Sun Microsystems, Inc.
SUNCORP SunCorporation
suntx Suntx System Co., Ltd
Swinxs Swinxs BV
SYMANTEC Symantec Corporation
SYMBIOS Symbios Logic Inc.
SYMWAVE Symwave, Inc.
SYNCSORT Syncsort Incorporated
SYNERWAY Synerway
SYNOLOGY Synology, Inc.
SyQuest SyQuest Technology, Inc.
SYSGEN Sysgen
T-MITTON Transmitton England
T-MOBILE T-Mobile USA, Inc.
T11 INCITS Technical Committee T11
TALARIS Talaris Systems, Inc.
TALLGRAS Tallgrass Technologies
TANDBERG Tandberg Data A/S
TANDEM Tandem (now HP)
TANDON Tandon
TCL TCL Shenzhen ASIC MIcro-electronics Ltd
TDK TDK Corporation
TEAC TEAC Japan
TECOLOTE Tecolote Designs
TEGRA Tegra Varityper
Teilch Teilch
Tek Tektronix
TELLERT Tellert Elektronik GmbH
TENTIME Laura Technologies, Inc.
TFDATACO TimeForge
TGEGROUP TGE Group Co.,LTD.
Thecus Thecus Technology Corp.
TI-DSG Texas Instruments
TiGi TiGi Corporation

Working Draft SCSI Primary Commands - 4 (SPC-4) 957

T10/BSR INCITS 513 Revision 37 17 May 2014

Table G.1 — T10 vendor identification list (part 16 of 17)

ID Organization
TILDESGN Tildesign bv
Tite Tite Technology Limited
TKS Inc. TimeKeeping Systems, Inc.
TLMKS Telemakus LLC
TMS Texas Memory Systems, Inc.
TMS100 TechnoVas
TOLISGRP The TOLIS Group
TOSHIBA Toshiba Japan
TOYOU TOYOU FEIJI ELECTRONICS CO.,LTD.
Tracker Tracker, LLC
TRIOFLEX Trioflex Oy
TRIPACE Tripace
TRLogger TrueLogger Ltd.
TROIKA Troika Networks, Inc.
TRULY TRULY Electronics MFG. LTD.
TRUSTED Trusted Data Corporation
TSSTcorp Toshiba Samsung Storage Technology Corporation
TZM TZ Medical
UD-DVR Bigstone Project.
UDIGITAL United Digital Limited
UIT United Infomation Technology
ULTRA UltraStor Corporation
UNISTOR Unistor Networks, Inc.
UNISYS Unisys
USCORE Underscore, Inc.
USDC US Design Corp.
VASCO Vasco Data Security
VDS Victor Data Systems Co., Ltd.
VELDANA VELDANA MEDICAL SA
Verari Verari Systems, Inc.
VERBATIM Verbatim Corporation
Vercet Vercet LLC
VERITAS VERITAS Software Corporation
VEXCEL VEXCEL IMAGING GmbH
VicomSys Vicom Systems, Inc.
VIDEXINC Videx, Inc.
VIOLIN Violin Memory, Inc.
VIRIDENT Virident Systems, Inc.
VITESSE Vitesse Semiconductor Corporation
VIXEL Vixel Corporation (now part of Emulex)
VLS Van Lent Systems BV
VMAX VMAX Technologies Corp.
VMware VMware Inc.
Vobis Vobis Microcomputer AG
VOLTAIRE Voltaire Ltd.
VRC Vermont Research Corp.
VRugged Vanguard Rugged Storage

958 Working Draft SCSI Primary Commands - 4 (SPC-4)

17 May 2014 T10/BSR INCITS 513 Revision 37

Table G.1 — T10 vendor identification list (part 17 of 17)

ID Organization
VTGadget Vermont Gadget Company
Waitec Waitec NV
WangDAT WangDAT
WANGTEK Wangtek
Wasabi Wasabi Systems
WAVECOM Wavecom
WD Western Digital Corporation
WDC Western Digital Corporation
WDIGTL Western Digital
WDTI Western Digital Technologies, Inc.
WEARNES Wearnes Technology Corporation
WeeraRes Weera Research Pte Ltd
Wildflwr Wildflower Technologies, Inc.
WSC0001 Wisecom, Inc.
X3 InterNational Committee for Information Technology Standards (INCITS)
XEBEC Xebec Corporation
XENSRC XenSource, Inc.
Xerox Xerox Corporation
XIOtech XIOtech Corporation
XIRANET Xiranet Communications GmbH
XIV XIV (now IBM)
XtremIO XtremIO
XYRATEX Xyratex
YINHE NUDT Computer Co.
YIXUN Yixun Electronic Co.,Ltd.
YOTTA YottaYotta, Inc.
Zarva Zarva Digital Technology Co., Ltd.
ZETTA Zetta Systems, Inc.
ZVAULT Zetavault

Working Draft SCSI Primary Commands - 4 (SPC-4) 959

T10/BSR INCITS 513 Revision 37 17 May 2014

Bibliography

ANSI INCITS 519-2014, Serial Attached SCSI - 3 (SAS-3)

ISO/IEC 14776-321, SCSI Block Commands (SBC) [ANSI INCITS 306-1998-R2008]

NOTE 71 - SBC is the only published standard that defines write once devices and optical memory devices.

ANSI INCITS 494-2012, Automation/Drive Interface - Commands - 3 (ADC-3)

ANSI INCITS 309-1998, Serial Storage Architecture SCSI-3 Protocol (SSA-S3P)

ANSI INCITS 441-2008, Automation/Drive Interface - Transport Protocol - 2 (ADT-2)

ANSI INCITS 466-2011, Single-Byte Command Code Sets-4 Mapping Protocol (FC-SB-4)

ISO/IEC 24739 (all parts), Information technology – (all parts) AT Attachment with Packet Interface - 7
(AT/ATAPI-7)

RFC 793, Transmission Control Protocol - DARPA Internet Program - Protocol Specification

RFC 1035, Domain Names - Implementation and Specification

RFC 1591, Domain Name System Structure and Delegation

RFC 2753, A Framework for Policy-based Admission Control

RFC 3447, Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1

RFC 3552, Guidelines for Writing RFC Text on Security Considerations

RFC 3986, Uniform Resource Identifier (URI): Generic Syntax

NOTE 72 - Copies of the IETF standards may be obtained through at www.ietf.org.

JEDEC JESD220A, Universal Flash Storage (UFS 1.1) standard

NOTE 73 - Copies of the following standards may be obtained from JEDEC®1) at www.jedec.org.

OMG Unified Modeling Language (UML) Specification Version 1.5, March 2003

NOTE 74 - Copies of the OMG specifications may be obtained through the Object Management Group
(OMG) at www.omg.org.

1) JEDEC® is a registered trademark of the JEDEC Solid State Technology Association. This
information is given for the convenience of users of this document and does not constitute an
endorsement by ISO.

960 Working Draft SCSI Primary Commands - 4 (SPC-4)