logo资料库

SCSI协议族子协议 SCSI Architecture Model (SAM5)最新版本.pdf

第1页 / 共152页
第2页 / 共152页
第3页 / 共152页
第4页 / 共152页
第5页 / 共152页
第6页 / 共152页
第7页 / 共152页
第8页 / 共152页
资料共152页,剩余部分请下载后查看
Points of Contact
Revision Information
R.1 Revision SAM-5r00 (24 September 2008)
R.2 Revision SAM-5r01 (28 January 2009)
R.3 Revision SAM-5r02 (22 July 2009)
R.4 Revision SAM-5r03 (18 November 2009)
R.5 Revision SAM-5r04 (20 January 2010)
R.6 Revision SAM-5r05 (19 May 2010)
Contents
Tables
Figures
Foreword
Introduction
SCSI standards family
1 Scope
1.1 Introduction
2 Normative references
2.1 Normative references
2.2 Approved references
2.3 References under development
2.4 Other references
3 Definitions, symbols, abbreviations, and conventions
3.1 Definitions
ACA command:
additional sense code:
aggregation:
application client:
argument:
association:
attribute:
auto contingent allegiance (ACA):
background operation:
blocked command state:
blocking boundary:
byte:
class:
class diagram:
client-server:
client:
command:
command descriptor block (CDB):
command identifier:
command priority:
command standard:
completed command:
confirmation:
confirmed SCSI transport protocol service:
constraint:
copy manager:
current command:
deferred error:
dependency:
dependent logical unit:
device model:
device server:
device service request:
device service response:
domain:
dormant command state:
enabled command state:
extended logical unit addressing:
faulted I_T nexus:
faulted task set:
faulting command:
field:
generalization:
hard reset:
hierarchical logical unit:
I_T nexus:
I_T nexus loss:
I_T nexus loss event:
I_T_L nexus:
I_T_L_Q nexus:
I_T_L_Q nexus transaction:
I_T_L_x nexus:
I/O operation:
implementation specific:
incorrect logical unit number:
incorrect logical unit:
initiator port identifier:
initiator port name:
instance:
in transit:
implicit head of queue:
layer:
link:
logical unit:
logical unit inventory:
logical unit name:
logical unit number (LUN):
logical unit reset:
logical unit reset event:
multiplicity:
name:
nexus:
non-faulted I_T nexus:
object:
object diagram:
operation:
peer entities:
power cycle:
power loss expected:
power loss expected event:
power on:
power on event:
procedure:
procedure call:
protocol:
queue:
receiver:
reference model:
relative port identifier:
request:
request-response transaction:
reset event:
response:
role:
SCSI application layer (SAL):
SCSI device:
SCSI device name:
SCSI event:
SCSI I/O system:
SCSI initiator device:
SCSI initiator port:
SCSI port:
SCSI port identifier:
SCSI target device:
SCSI target port:
SCSI transport protocol layer (STPL):
SCSI transport protocol service confirmation:
SCSI transport protocol service indication:
SCSI transport protocol service request:
SCSI transport protocol service response:
SCSI transport protocol specific:
sender:
sense data:
sense key:
server:
service:
service delivery failure:
service delivery subsystem:
service delivery transaction:
standard INQUIRY data:
target port identifier:
target port name:
task:
task attribute:
task management function:
task management request:
task management response:
task manager:
task router:
task set:
task tag:
transaction:
unconfirmed SCSI transport protocol service:
well known logical unit:
well known logical unit number (W-LUN):
3.2 Acronyms
3.3 Keywords
invalid:
mandatory:
may:
may not:
obsolete:
option, optional:
prohibited:
reserved:
restricted:
shall:
should:
vendor specific:
3.4 Editorial conventions
3.5 Numeric conventions
3.6 Notation conventions
3.6.1 UML notation conventions
3.6.1.1 Notation conventions overview
3.6.1.2 Constraint and note conventions
3.6.1.3 Class diagram conventions
3.6.1.4 Object diagram conventions
3.6.2 Notation for procedure calls
3.6.3 Notation for state diagrams
4 SCSI architecture model
4.1 Introduction
4.2 Compliance requirements
4.3 The SCSI distributed service model
4.4 The SCSI client-server model
4.4.1 SCSI client-server model overview
4.4.2 Synchronizing client and server states
4.4.3 Request/Response ordering
4.5 The SCSI structural model
4.6 SCSI classes
4.6.1 SCSI classes overview
4.6.2 SCSI Domain class
4.6.3 Service Delivery Subsystem class
4.6.4 SCSI Device class
4.6.4.1 SCSI Device class overview
4.6.4.2 SCSI Device Name attribute
4.6.5 SCSI Port class
4.6.5.1 SCSI Port class overview
4.6.5.2 Relative Port Identifier attribute
4.6.6 SCSI Target Port class
4.6.6.1 SCSI Target Port class overview
4.6.6.2 Target Port Identifier attribute
4.6.6.3 Target Port Name attribute
4.6.7 SCSI Initiator Port class
4.6.7.1 SCSI Initiator Port class overview
4.6.7.2 Initiator Port Identifier attribute
4.6.7.3 Initiator Port Name attribute
4.6.8 Task Router class
4.6.9 SCSI Initiator Device class
4.6.10 Application Client class
4.6.11 Application Client Task Management Function class
4.6.11.1 Application Client Task Management Function class overview
4.6.11.2 Function Identifier attribute
4.6.11.3 Nexus attribute
4.6.11.4 Service Response attribute
4.6.11.5 Additional Response Information attribute
4.6.12 Application Client Task Set class
4.6.13 Application Client Command class
4.6.13.1 Application Client Command class overview
4.6.13.2 I_T_L_Q Nexus attribute
4.6.13.3 CDB attribute
4.6.13.4 Task Attribute attribute
4.6.13.5 Status attribute
4.6.13.6 Service Response attribute
4.6.13.7 Data-In Buffer attribute
4.6.13.8 Data-In Buffer Size attribute
4.6.13.9 Data-Out Buffer attribute
4.6.13.10 Data-Out Buffer size attribute
4.6.13.11 CRN attribute
4.6.13.12 Command Priority attribute
4.6.13.13 First Burst Enabled attribute
4.6.13.14 Sense Data attribute
4.6.13.15 Sense Data Length attribute
4.6.13.16 Status Qualifier attribute
4.6.14 SCSI Target Device class
4.6.15 Level 1 Hierarchical Logical Unit class
4.6.16 Level 2 Hierarchical Logical Unit class
4.6.17 Level 3 Hierarchical Logical Unit class
4.6.18 Level 4 Hierarchical Logical Unit class
4.6.19 Logical Unit class
4.6.19.1 Logical Unit class overview
4.6.19.2 LUN attribute
4.6.19.3 Logical Unit Name attribute
4.6.19.4 Dependent Logical Unit attribute
4.6.20 Device Server class
4.6.21 Copy Manager class
4.6.22 Task Manager class
4.6.23 Task Set class
4.6.24 Command class
4.6.24.1 Command class overview
4.6.24.2 I_T_L_Q Nexus attribute
4.6.24.3 Task Attribute attribute
4.6.24.4 CDB attribute
4.6.24.5 CRN attribute
4.6.24.6 Command Priority attribute
4.6.24.7 Status attribute
4.6.24.8 Sense Data attribute
4.6.24.9 Sense Data Length attribute
4.6.24.10 Service Response attribute
4.6.24.11 Status Qualifier attribute
4.6.24.12 First Burst Enabled attribute
4.6.24.13 Device Server Buffer attribute
4.6.24.14 Application Client Buffer Offset attribute
4.6.24.15 Request Byte Count attribute
4.6.24.16 Delivery Result attribute
4.6.25 Task Management Function class
4.6.25.1 Task Management Function class overview
4.6.25.2 Function Identifier attribute
4.6.25.3 Nexus attribute
4.6.25.4 Service Response attribute
4.6.25.5 Additional Response Information attribute
4.6.26 Well Known Logical Unit class
4.7 Logical unit number (LUN)
4.7.1 Introduction
4.7.2 Logical unit representation format
4.7.3 LUNs overview
4.7.4 Minimum LUN addressing requirements
4.7.5 Single level LUN structure
4.7.6 Eight byte LUN structure
4.7.7 Peripheral device addressing method
4.7.8 Flat space addressing method
4.7.9 Logical unit addressing method
4.7.10 Extended logical unit addressing
4.7.11 Well known logical unit addressing
4.7.12 Extended flat space addressing method
4.7.13 Logical unit not specified addressing
4.8 Nexus
4.8.1 Nexus overview
4.8.2 Command identifier
4.8.3 Nexus usage rules
4.9 SCSI ports
4.9.1 SCSI port configurations
4.9.2 SCSI devices with multiple ports
4.9.3 Multiple port SCSI target device structure
4.9.4 Multiple port SCSI initiator device structure
4.9.5 Multiple port SCSI device structure
4.9.6 SCSI initiator device view of a multiple port SCSI target device
4.9.7 SCSI target device view of a multiple port SCSI initiator device
4.10 The SCSI model for distributed communications
5 SCSI command model
5.1 The Execute Command procedure call
5.2 Command descriptor block (CDB)
5.3 Status
5.3.1 Status codes
5.3.2 Status qualifier
5.3.3 Status precedence
5.4 SCSI transport protocol services in support of Execute Command
5.4.1 Overview
5.4.2 Command and status SCSI transport protocol services
5.4.2.1 Command and status SCSI transport protocol services overview
5.4.2.2 Send SCSI Command SCSI transport protocol service request
5.4.2.3 SCSI Command Received SCSI transport protocol service indication
5.4.2.4 Send Command Complete SCSI transport protocol service response
5.4.2.5 Command Complete Received SCSI transport protocol service confirmation
5.4.3 Data transfer SCSI transport protocol services
5.4.3.1 Introduction
5.4.3.2 Data-In delivery service
5.4.3.2.1 Send Data-In SCSI transport protocol service request
5.4.3.2.2 Data-In Delivered SCSI transport protocol service confirmation
5.4.3.3 Data-Out delivery service
5.4.3.3.1 Receive Data-Out SCSI transport protocol service request
5.4.3.3.2 Data-Out Received SCSI transport protocol service confirmation
5.4.3.4 Terminate Data Transfer service
5.4.3.4.1 Terminate Data Transfer SCSI transport protocol service request
5.4.3.4.2 Data Transfer Terminated SCSI transport protocol service confirmation
5.5 Command lifetime
5.6 Aborting commands
5.7 Command processing example
5.8 Commands that complete with CHECK CONDITION status
5.8.1 Overview
5.8.2 Handling commands when ACA is not in effect
5.8.3 Aborting commands terminated with a CHECK CONDITION status without establishing an ACA
5.9 Auto contingent allegiance (ACA)
5.9.1 ACA overview
5.9.2 Establishing an ACA
5.9.3 Handling new commands received on the faulted I_T nexus when ACA is in effect
5.9.4 Handling new commands received on non-faulted I_T nexuses when ACA is in effect
5.9.4.1 Command processing that is permitted for commands received on a non-faulted I_T nexuses during ACA
5.9.4.2 Handling new commands received on non-faulted I_T nexuses when ACA is in effect
5.9.5 Clearing an ACA condition
5.10 Overlapped commands
5.11 Incorrect logical unit
5.12 Task attribute exception conditions
5.13 Sense data
5.13.1 Command terminated sense data or polled sense data
5.13.2 Command completed sense data
5.14 Unit attention condition
6 SCSI events and event notification model
6.1 SCSI events overview
6.2 Establishing a unit attention condition subsequent to detection of an event
6.3 Conditions resulting from SCSI events
6.3.1 Power on
6.3.2 Hard reset
6.3.3 Logical unit reset
6.3.4 I_T nexus loss
6.3.5 Power loss expected
6.4 Event notification SCSI transport protocol services
7 Task management functions
7.1 Task management function procedure calls
7.2 ABORT TASK
7.3 ABORT TASK SET
7.4 CLEAR ACA
7.5 CLEAR TASK SET
7.6 I_T NEXUS RESET
7.7 LOGICAL UNIT RESET
7.8 QUERY TASK
7.9 QUERY TASK SET
7.10 QUERY ASYNCHRONOUS EVENT
7.11 Task management function lifetime
7.12 Task management SCSI transport protocol services
7.12.1 Task management SCSI transport protocol services overview
7.12.2 Send Task Management Request SCSI transport protocol service request
7.12.3 Task Management Request Received SCSI transport protocol service indication
7.12.4 Task Management Function Executed SCSI transport protocol service response
7.12.5 Received Task Management Function Executed SCSI transport protocol service confirmation
7.13 Task management function example
8 Task set management
8.1 Introduction to task set management
8.2 Implicit head of queue
8.3 Command management model
8.4 Command management events
8.5 Command states
8.5.1 Overview
8.5.1.1 Command state nomenclature
8.5.1.2 Suspended information
8.5.2 Enabled command state
8.5.3 Blocked command state
8.5.4 Dormant command state
8.5.5 Completed command state
8.5.6 Command states and command lifetimes
8.6 Task attributes
8.6.1 Overview
8.6.2 Commands having the simple task attribute
8.6.3 Commands having the ordered task attribute
8.6.4 Commands having the head of queue task attribute
8.6.5 Commands having the aca task attribute
8.7 Command priority
8.8 Command state transitions
8.9 Task set management examples
8.9.1 Introduction
8.9.2 Commands having the head of queue task attribute
8.9.3 Commands having the ordered task attribute
8.9.4 Commands having the aca task attribute
Annex A
Identifiers and names for objects
A.1 Identifiers and names overview
A.2 Identifiers and names
Annex B
SCSI Initiator Port attributes and SCSI Target Port attributes supported by SCSI transport protocols
Annex C
Terminology mapping to SAM-3
Annex D
SCSI transport protocol acronyms
EUI-64 (Extended Unique Identifier, a 64-bit globally unique identifier):
NAA:
SAS-2SPL SSP:
UTF-8:
Working Draft American National Standard Project T10/2104-D Revision 05 19 May 2010 Information technology - SCSI Architecture Model - 5 (SAM-5) 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: George Penokie LSI Corporation 3033 41st Street NW, Suite 100 Rochester, MN 55901 USA Telephone: 507-328-9017 Email: george.penokie@lsi.com Reference number ISO/IEC 14776-415:201x ANSI INCITS ***-201x Printed 2:06 PM Tuesday 11 May 2010
T10/2104-D Revision 05 19 May 2010 Points of Contact International Committee for Information Technology Standards (INCITS) T10 Technical Committee T10 Chair John B. Lohmeyer LSI Logic 4420 Arrows West Drive Colorado Springs, CO 80907-3444 USA T10 Vice-Chair Mark S. Evans Western Digital Corporation 5863 Rue Ferrari San Jose, CA 95138 USA Telephone: Email: (719) 533-7560 lohmeyer@t10.org Telephone: (408) 363-5257 Email: mark.evans@wdc.com T10 Web Site: http://www.t10.org T10 E-mail reflector: Server: majordomo@t10.org To subscribe send e-mail with ‘subscribe’ in message body To unsubscribe send e-mail with ‘unsubscribe’ in message body INCITS Secretariat Suite 610 1101 K Street, NW Washington, DC 20005 USA Telephone: Web site: Email: 202-737-8888 http://www.incits.org incits@itic.org Information Technology Industry Council Web site: http://www.itic.org Document Distribution INCITS Online Store managed by Techstreet 1327 Jones Drive Ann Arbor, MI 48105 USA Web site: Telephone: http://www.techstreet.com/incitsgate.tmpl (734) 302-7801 or (800) 699-9277 Global Engineering Documents, an IHS Company 15 Inverness Way East Englewood, CO 80112-5704 USA Web site: Telephone: http://global.ihs.com (303) 397-7956 or (303) 792-2181 or (800) 854-7179 ii Working Draft SCSI Architecture Model - 5 (SAM-5)
19 May 2010 T10/2104-D Revision 05 SCSI Architecture Model - 5 (SAM-5) American National Standard for Information Technology Secretariat Information Technology Industry Council Approved mm.dd.yy American National Standards Institute, Inc. ABSTRACT This standard specifies the SCSI Architecture Model. The purpose of the architecture is to provide a common basis for the coordination of SCSI standards and to specify those aspects of SCSI I/O system behavior that are independent of a particular technology and common to all implementations. Working Draft SCSI Architecture Model - 5 (SAM-5) iii
T10/2104-D Revision 05 19 May 2010 American National Standard Approval of an American National Standard requires verification by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgment of 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 towards their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and will in no circumstances give interpretation on any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an 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 patents, if any, 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, no such claims have been made. 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 11 W. 42nd Street, New York, New York 10036 Copyright © 2010 by Information Technology Industry Council (ITI). All rights reserved. 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. Printed in the United States of America iv Working Draft SCSI Architecture Model - 5 (SAM-5)
19 May 2010 Revision Information T10/2104-D Revision 05 R.1 Revision SAM-5r00 (24 September 2008) First release of SAM-5. Same content as SAM-4 revision 14. R.2 Revision SAM-5r01 (28 January 2009) The following T10 approved proposals were incorporated in SAM-5 in this revision: a) 08-327r2 - Restrict SPC-4 and SAM-5 codes to FC-SB-4 use [Butt]; b) 08-450r1 - Add Restricted keyword to the Style Guide [Weber]; c) 09-003r0 - Correct redundant text in command state transition figure [Knight]; and d) 09-017r1 - QUERY TASK TMF Progress Indicator [Knight]. R.3 Revision SAM-5r02 (22 July 2009) The following T10 approved proposals were incorporated in SAM-5 in this revision: a) 09-159r1 - SAM5 - CLEAR_ACA status when no ACA condition exists [Knight]; b) An error was corrected that was induced in SAM-4 that was pointed out in the following e-mail from Rob Elliott on 03/05/2009: “SAM-4 no longer has 06-411r2 (REPORTED LUNS DATA HAS CHANGED unit attention clearing) incorporated correctly. In 5.14, items c) and d) are supposed to be paragraphs inside b), as they only apply to the REPORT LUNS command. c) if the UA_INTLCK_CTRL field in the Control mode page is set to 00b (see SPC-4), the SCSI target device shall clear any pending unit attention condition with an additional sense code of REPORTED LUNS DATA HAS CHANGED established for the SCSI initiator port associated with that I_T nexus in each logical unit accessible by the I_T nexus on which the REPORT LUNS command was received. Other pending unit attention conditions shall not be cleared; d) if the UA_INTLCK_CTRL field in the Control mode page contains 10b or 11b, the SCSI target device shall not clear any unit attention condition(s); i) if a device server reports a unit attention condition with a CHECK CONDITION status and the UA_INTLCK_CTRL field in the Control mode page contains 00b (see SPC-4), then the device server shall clear the reported unit attention condition for the SCSI initiator port associated with that I_T nexus on the logical unit. If the unit attention condition has an additional sense code of REPORTED LUNS DATA HAS CHANGED, the SCSI target device shall clear any pending unit attention conditions with an additional sense code of REPORTED LUNS DATA HAS CHANGED established for the I_T nexus on which the command was received in each logical unit accessible by that I_T nexus. If the UA_INTLCK_CTRL field contains 10b or 11b, the device server shall not clear unit attention conditions reported with a CHECK CONDITION status. Everything was correct from sam4r08 through sam4r13c, where this section was in section 5.8.7. It was broken in sam4r14d when the section was renumbered to 5.14. It looks like every top level paragraph in that list got changed to an UnorderedList0, including the unnumbered ones. f) and i) are also wrong.” c) An error in a cross reference between SAM-5 and SPC-4 was pointed out in the following e-mail from Fred Knight on 03/09/2009. “SAM5r1 4.5.4.2 - SCSI Device Name attribute - last paragraph -...may be reported in a target device name designation descriptor in the Device Identification VPD page (see SPC-4). SPC4r18 - target device name - doesn't exist/.” This was corrected by changing the reference in subclause 4.5.4.2 SCSI Device Name attribute and subclause 4.5.25 Well Known Logical Unit class to the following: "in the Device Identification VPD pages designation descriptor for SCSI target devices (see SPC-4)." d) An error in the incorporation of 09-017r1 was pointed out by Mark Evens in the following e-mail: Working Draft SCSI Architecture Model - 5 (SAM-5) v
T10/2104-D Revision 05 19 May 2010 “While going through SAM-5r01 I noticed that you put the new Additional Response Information argument definition in QUERY TASK SET. Isn’t this supposed to be in QUERY TASK?” The answer is yes it should have been in QUERY TASK. e) Moved section 1.2 Requirements precedence to a new section 4.2 Compliance requirements. This was a request from ISO to remove requirements from the scope section. f) Moved section 1.3 SCSI standards family into the front matter just before section 1. This was a request from ISO; Editorial conventions; g) Added in a more specific set of rules to ordered and unordered lists in section 3.4 Editorial conventions; h) Added the statement “notes are numbered consecutively throughout this standard” in section 3.4 i) Moved the annex acronyms and bibliography from annex A to a new Annex to conform to ISO styles; j) Created a real table for the command management events in section 8.4; and k) Removed the statement “in previous versions of this standard” and replaced that wording with a reference to the actual standard. In all cases that was either SAM-2 or SAM-3. Added SAM-2 and SAM-3 to the acronyms and bibliography. 09-017r1 - QUERY TASK TMF Progress Indicator [Knight]. l) R.4 Revision SAM-5r03 (18 November 2009) The following T10 approved proposals were incorporated in SAM-5 in this revision: a) 09-373r0 - Help for those who cannot find initiator/target ports in SAM-5 [Weber]; and b) 09-381r2 - Adding a Copy Manager class into SAM-5 [Penokie]. R.5 Revision SAM-5r04 (20 January 2010) The following T10 approved proposals were incorporated in SAM-5 in this revision: a) 09-241r6 - SCSI Referrals [Penokie] Added in as much of the UAS name and identifier information into annex A as is known at this time. R.6 Revision SAM-5r05 (19 May 2010) The following T10 approved proposals were incorporated in SAM-5 in this revision: a) 10-163r1 - SAM5: Aborted command reporting ambiguity [Martin]. The following comment from the SPL letter ballot was accepted with fixes to Annex B and Annex D: Comments for the SPL editor to forward to the SAM-5 editor to keep SAM-5 in sync with SPL/SAS-2.1: a) Update all SAM-5 references to SAS-2 to SAS-2.1 and/or SPL (probably mostly SPL). b) Annex A has been updated in sam5r04, but annex B and D have not. c) Annex B still uses "SAS-2" as a column header. d) Annex D still refers to "SAS-2 SSP". vi Working Draft SCSI Architecture Model - 5 (SAM-5)
19 May 2010 Contents T10/2104-D Revision 05 Page Points of Contact.................................................................................................................................................... ii Contents................................................................................................................................................................vii Tables ...................................................................................................................................................................xii Figures .................................................................................................................................................................xiv Foreword.............................................................................................................................................................. xv Introduction ..........................................................................................................................................................xvi SCSI standards family .........................................................................................................................................xvi 1 Scope.................................................................................................................................................................. 1 1.1 Introduction.................................................................................................................................................... 1 2 Normative references.......................................................................................................................................... 2 2.1 Normative references .................................................................................................................................... 2 2.2 Approved references ..................................................................................................................................... 2 2.3 References under development .................................................................................................................... 2 2.4 Other references ........................................................................................................................................... 2 3 Definitions, symbols, abbreviations, and conventions ........................................................................................ 2 3.1 Definitions...................................................................................................................................................... 2 3.2 Acronyms ...................................................................................................................................................... 9 3.3 Keywords..................................................................................................................................................... 10 3.4 Editorial conventions ................................................................................................................................... 11 3.5 Numeric conventions................................................................................................................................... 11 3.6 Notation conventions................................................................................................................................... 12 3.6.1 UML notation conventions ..................................................................................................................... 12 3.6.1.1 Notation conventions overview......................................................................................................... 12 3.6.1.2 Constraint and note conventions...................................................................................................... 12 3.6.1.3 Class diagram conventions .............................................................................................................. 12 3.6.1.4 Object diagram conventions............................................................................................................. 17 3.6.2 Notation for procedure calls................................................................................................................... 18 3.6.3 Notation for state diagrams.................................................................................................................... 18 4 SCSI architecture model ................................................................................................................................... 20 4.1 Introduction.................................................................................................................................................. 20 4.2 Compliance requirements ........................................................................................................................... 20 4.3 The SCSI distributed service model ............................................................................................................ 21 4.4 The SCSI client-server model ..................................................................................................................... 22 4.4.1 SCSI client-server model overview........................................................................................................ 22 4.4.2 Synchronizing client and server states .................................................................................................. 23 4.4.3 Request/Response ordering .................................................................................................................. 23 4.5 The SCSI structural model .......................................................................................................................... 23 4.6 SCSI classes ............................................................................................................................................... 24 4.6.1 SCSI classes overview .......................................................................................................................... 24 4.6.2 SCSI Domain class................................................................................................................................ 25 4.6.3 Service Delivery Subsystem class......................................................................................................... 26 4.6.4 SCSI Device class ................................................................................................................................. 27 4.6.4.1 SCSI Device class overview............................................................................................................. 27 4.6.4.2 SCSI Device Name attribute ............................................................................................................ 27 4.6.5 SCSI Port class...................................................................................................................................... 28 4.6.5.1 SCSI Port class overview................................................................................................................. 28 4.6.5.2 Relative Port Identifier attribute........................................................................................................ 28 4.6.6 SCSI Target Port class .......................................................................................................................... 29 4.6.6.1 SCSI Target Port class overview...................................................................................................... 29 4.6.6.2 Target Port Identifier attribute........................................................................................................... 29 4.6.6.3 Target Port Name attribute............................................................................................................... 29 4.6.7 SCSI Initiator Port class......................................................................................................................... 29 Working Draft SCSI Architecture Model - 5 (SAM-5) vii
T10/2104-D Revision 05 19 May 2010 4.6.7.1 SCSI Initiator Port class overview .................................................................................................... 29 4.6.7.2 Initiator Port Identifier attribute ......................................................................................................... 30 4.6.7.3 Initiator Port Name attribute ............................................................................................................. 30 4.6.8 Task Router class .................................................................................................................................. 30 4.6.9 SCSI Initiator Device class..................................................................................................................... 30 4.6.10 Application Client class........................................................................................................................ 31 4.6.11 Application Client Task Management Function class .......................................................................... 32 4.6.11.1 Application Client Task Management Function class overview...................................................... 32 4.6.11.2 Function Identifier attribute............................................................................................................. 32 4.6.11.3 Nexus attribute ............................................................................................................................... 32 4.6.11.4 Service Response attribute ............................................................................................................ 32 4.6.11.5 Additional Response Information attribute ..................................................................................... 32 4.6.12 Application Client Task Set class......................................................................................................... 32 4.6.13 Application Client Command class ...................................................................................................... 33 4.6.13.1 Application Client Command class overview.................................................................................. 33 4.6.13.2 I_T_L_Q Nexus attribute ................................................................................................................ 33 4.6.13.3 CDB attribute.................................................................................................................................. 33 4.6.13.4 Task Attribute attribute ................................................................................................................... 33 4.6.13.5 Status attribute ............................................................................................................................... 33 4.6.13.6 Service Response attribute ............................................................................................................ 33 4.6.13.7 Data-In Buffer attribute................................................................................................................... 33 4.6.13.8 Data-In Buffer Size attribute........................................................................................................... 33 4.6.13.9 Data-Out Buffer attribute ................................................................................................................ 33 4.6.13.10 Data-Out Buffer size attribute....................................................................................................... 33 4.6.13.11 CRN attribute................................................................................................................................ 33 4.6.13.12 Command Priority attribute........................................................................................................... 33 4.6.13.13 First Burst Enabled attribute......................................................................................................... 33 4.6.13.14 Sense Data attribute .................................................................................................................... 34 4.6.13.15 Sense Data Length attribute ........................................................................................................ 34 4.6.13.16 Status Qualifier attribute............................................................................................................... 34 4.6.14 SCSI Target Device class.................................................................................................................... 34 4.6.15 Level 1 Hierarchical Logical Unit class ................................................................................................ 34 4.6.16 Level 2 Hierarchical Logical Unit class ................................................................................................ 36 4.6.17 Level 3 Hierarchical Logical Unit class ................................................................................................ 36 4.6.18 Level 4 Hierarchical Logical Unit class ................................................................................................ 36 4.6.19 Logical Unit class................................................................................................................................. 37 4.6.19.1 Logical Unit class overview ............................................................................................................ 37 4.6.19.2 LUN attribute .................................................................................................................................. 39 4.6.19.3 Logical Unit Name attribute............................................................................................................ 39 4.6.19.4 Dependent Logical Unit attribute.................................................................................................... 39 4.6.20 Device Server class ............................................................................................................................. 40 4.6.21 Copy Manager class ............................................................................................................................ 40 4.6.22 Task Manager class............................................................................................................................. 40 4.6.23 Task Set class ..................................................................................................................................... 40 4.6.24 Command class ................................................................................................................................... 40 4.6.24.1 Command class overview .............................................................................................................. 40 4.6.24.2 I_T_L_Q Nexus attribute ................................................................................................................ 40 4.6.24.3 Task Attribute attribute ................................................................................................................... 40 4.6.24.4 CDB attribute.................................................................................................................................. 40 4.6.24.5 CRN attribute.................................................................................................................................. 41 4.6.24.6 Command Priority attribute............................................................................................................. 41 4.6.24.7 Status attribute ............................................................................................................................... 41 4.6.24.8 Sense Data attribute ...................................................................................................................... 41 4.6.24.9 Sense Data Length attribute .......................................................................................................... 41 4.6.24.10 Service Response attribute .......................................................................................................... 41 4.6.24.11 Status Qualifier attribute............................................................................................................... 41 4.6.24.12 First Burst Enabled attribute......................................................................................................... 41 viii Working Draft SCSI Architecture Model - 5 (SAM-5)
分享到:
收藏