《ANSI-INCITS-366-2003.pdf》由会员分享，可在线阅读，更多相关《ANSI-INCITS-366-2003.pdf（116页珍藏版）》请在三一文库上搜索。
1、ANSI INCITS 366-2003 for Information Technology SCSI Architecture Model - 2 (SAM-2) ANSI INCITS 366-2003 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:16:29 MDTNo reproduc
2、tion or networking permitted without license from IHS -,-,- Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:16:29 MDTNo reproduction or networking permitted without license
3、from IHS -,-,- ANSI INCITS 366-2003 American National Standard for Information Technology SCSI Architecture Model - 2 (SAM-2) Secretariat Information Technology Industry Council (ITI) Approved April 2, 2003 American National Standards Institute, Inc. Abstract This standard specifies the SCSI Archite
4、cture Model. The purpose of the architecture is to provide a com- mon basis for the coordination of SCSI standards and to specify those aspects of SCSI I/O system behav- ior that are independent of a particular technology and common to all implementations. Copyright American National Standards Insti
5、tute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:16:29 MDTNo reproduction or networking permitted without license from IHS -,-,- Approval of an American National Standard requires review by ANSI that the requirements
6、for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgement of the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement mea
7、ns much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made towards their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect pr
8、eclude 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 an interpretatio
9、n of 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 a
10、ppears 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 Amer
11、ican National Standards may receive current information on all standards by calling or writing the American National Standards Institute. American National Standard Published by American National Standards Institute, Inc. 25 West 43rd Street, New York, NY 10036 Copyright 2003 by Information Technolo
12、gy 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, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of America CAUTION: The developers
13、 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
14、 standard. As of the date of publication of this standard and 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 de- veloper or publisher in respect to any standard
15、 it processes. No representation is made or implied that licenses are not required to avoid infringement in the use of this standard. Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29
16、/2007 13:16:29 MDTNo reproduction or networking permitted without license from IHS -,-,- i Contents Page Foreword.vi 1 Scope. 1 1.1 Introduction. 1 1.2 Requirements precedence . 1 1.3 SCSI standards family 2 2 Normative references. 5 2.1 Normative references. 5 2.2 Approved references 5 2.3 Referenc
17、es under development . 5 3 Definitions, symbols, abbreviations, and conventions . 6 3.1 Definitions. 6 3.2 Acronyms 13 3.3 Keywords 13 3.4 Editorial conventions 14 3.5 Numeric conventions 14 3.6 Notation conventions 15 3.6.1 Hierarchy diagram conventions. 15 3.6.2 Notation for procedures and functio
18、ns. 15 3.6.3 Notation for state diagrams . 16 4 SCSI Architecture Model 18 4.1 Introduction. 18 4.2 The SCSI distributed service model. 19 4.3 The SCSI client-server model. 20 4.4 The SCSI structural model . 21 4.5 SCSI domain 23 4.6 The service delivery subsystem . 23 4.6.1 The service delivery sub
19、system object 23 4.6.2 Synchronizing client and server states 24 4.6.3 Request/Response ordering 24 4.7 SCSI devices 25 4.7.1 SCSI initiator device 25 4.7.2 SCSI target device. 26 4.7.3 SCSI target/initiator device 27 4.7.4 SCSI port identifier 27 4.7.5 SCSI task router 28 4.7.6 SCSI device name. 28
20、 4.7.7 SCSI port name. 28 4.8 Logical units 29 4.9 Logical unit numbers 30 4.9.1 Logical unit numbers overview 30 4.9.2 LUN 0 address. 30 4.9.3 Single level logical unit number structure 30 4.9.4 Eight byte logical unit number structure 32 4.9.5 Logical unit addressing method. 34 4.9.6 Peripheral de
21、vice addressing method . 34 4.9.7 Flat space addressing method 35 4.9.8 Extended logical unit addressing. 36 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:16:29 MDTNo repr
22、oduction or networking permitted without license from IHS -,-,- ii 4.9.9 Well known logical unit addressing 38 4.10 Tasks 39 4.10.1 The task object 39 4.10.2 Task tags. 39 4.11 The nexus object 40 4.12 SCSI ports 41 4.12.1 SCSI port configurations 41 4.12.2 SCSI devices with multiple ports . 41 4.12
23、.3 Multiple port target SCSI device structure. 42 4.12.4 Multiple port initiator SCSI device structure. 43 4.12.5 Multiple port target/initiator SCSI device structure 44 4.12.6 SCSI initiator device view of a multiple port SCSI target device . 45 4.12.7 SCSI target device view of a multiple port SCS
24、I initiator device . 47 4.13 Model for dependent logical units. 48 4.14 The SCSI model for distributed communications . 50 5 SCSI Command Model 53 5.1 The Execute Command remote procedure 53 5.2 Command descriptor block (CDB) 55 5.2.1 CDB format 55 5.2.2 OPERATION CODE byte. 55 5.2.3 CONTROL byte. 5
25、6 5.3 Status . 57 5.3.1 Status codes 57 5.3.2 Status precedence. 59 5.4 SCSI transport protocol services in support of Execute Command 60 5.4.1 Overview 60 5.4.2 Execute Command request/confirmation SCSI transport protocol services 60 5.4.3 Data transfer SCSI transport protocol services . 62 5.4.3.1
26、 Introduction. 62 5.4.3.2 Data-In delivery service 63 5.4.3.3 Data-Out delivery service . 64 5.5 Task and command lifetimes 64 5.6 Task management function lifetime 65 5.7 Aborting tasks. 65 5.7.1 Mechanisms that cause tasks to be aborted . 65 5.7.2 When a SCSI initiator port aborts its own tasks 66
27、 5.7.3 When a SCSI initiator port aborts tasks from other SCSI initiator ports 66 5.8 Command processing examples 67 5.8.1 Unlinked command example. 67 5.8.2 Linked command example. 68 5.9 Command processing considerations and exception conditions 69 5.9.1 Contingent allegiance (CA) and auto conting
28、ent allegiance (ACA). 69 5.9.1.1 Overview. 69 5.9.1.2 Establishing a CA or ACA. 70 5.9.1.3 Handling tasks when neither CA or ACA is in effect. 71 5.9.1.4 Handling new tasks from the faulted initiator port when CA or ACA is in effect . 71 5.9.1.5 Handling new tasks from non-faulted initiator ports wh
29、en CA or ACA is in effect 72 5.9.1.5.1 Commands permitted from non-faulted initiator ports during CA or ACA 72 5.9.1.5.2 Handling new tasks from non-faulted initiator ports when CA or ACA is in effect . 73 5.9.1.6 Clearing a CA condition 75 5.9.1.7 Clearing an ACA condition . 75 5.9.2 Overlapped com
30、mands . 75 5.9.3 Incorrect logical unit selection . 76 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:16:29 MDTNo reproduction or networking permitted without license from
31、IHS -,-,- iii 5.9.4 Sense data 77 5.9.4.1 Sense data introduction 77 5.9.4.2 Asynchronous event reporting 77 5.9.4.3 Autosense. 78 5.9.5 Unit Attention condition 79 5.9.6 Hard reset 80 5.9.7 Logical unit reset . 80 6 Task management functions 81 6.1 Introduction. 81 6.2 ABORT TASK. 82 6.3 ABORT TASK
32、 SET. 82 6.4 CLEAR ACA . 83 6.5 CLEAR TASK SET . 83 6.6 LOGICAL UNIT RESET 84 6.7 TARGET RESET 84 6.8 WAKEUP 85 6.9 Task management SCSI transport protocol services . 85 6.10 Task management function example 87 7 Task Set Management. 88 7.1 Introduction to task set management . 88 7.2 Controlling ta
33、sk set management. 88 7.3 Task management events 89 7.4 Task states. 89 7.4.1 Overview 89 7.4.1.1 Task state nomenclature 89 7.4.1.2 Suspended information. 89 7.4.2 Enabled task state. 90 7.4.3 Blocked task state . 90 7.4.4 Dormant task state 90 7.4.5 Ended task state 90 7.4.6 Task states and task l
34、ifetimes . 91 7.5 Task attributes 91 7.5.1 Simple task 91 7.5.2 Ordered task 91 7.5.3 Head of queue task . 91 7.5.4 ACA task 92 7.6 Task state transitions 92 7.7 Task set management examples 93 7.7.1 Introduction 93 7.7.2 Head of queue tasks 94 7.7.3 Ordered tasks 96 7.7.4 ACA task 97 Annexes AIdent
35、ifiers and names for objects 98 BTerminology mapping. 102 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:16:29 MDTNo reproduction or networking permitted without license fr
36、om IHS -,-,- iv Tables Page 1 Single level logical unit number structure for 256 or fewer logical units. 30 2 Single level logical unit number structure for 257 to 16 384 logical units. 31 3 Eight byte logical unit number structure adjustments. 32 4 Eight Byte logical unit number structure. 33 5 For
37、mat of addressing fields 33 6 ADDRESS METHOD field values. 34 7 Logical unit addressing. 34 8 Peripheral device addressing. 35 9 Flat space addressing 36 10 Extended logical unit addressing 36 11 LENGTH field values. 36 12 Two byte extended logical unit addressing format. 37 13 Four byte extended lo
38、gical unit addressing format. 37 14 Six byte extended logical unit addressing format. 37 15 Eight byte extended logical unit addressing format 37 16 Logical unit extended address methods. 37 17 Well known logical unit extended address format 38 18 Mapping nexus to SAM-2 identifiers. 40 19 Command De
39、scriptor Block (CDB) Format 55 20 OPERATION CODE byte . 55 21 Group Code values 56 22 CONTROL byte . 56 23 Status codes. 57 24 Autosense, CA, and ACA Interactions . 69 25 Blocking and aborting tasks when a CA or ACA is established . 70 26 Task handling when neither CA nor ACA is in effect 71 27 Hand
40、ling for new tasks from a faulted initiator port during CA. 71 28 Handling for new tasks from a faulted initiator port during ACA. 72 29 Handling for new tasks from non-faulted initiator ports during CA. 73 30 Handling for new tasks from non-faulted initiator ports during ACA. 74 31 Task Management
41、Functions. 81 32 Task State Nomenclature. 89 33 Task attribute and state indications in examples 94 34 Dormant task blocking boundary requirements 96 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not f
42、or Resale, 04/29/2007 13:16:29 MDTNo reproduction or networking permitted without license from IHS -,-,- v Figures Page 1 Requirements precedence .1 2 SCSI document structure .2 3 Example hierarchy diagram15 4 Example state diagram.16 5 Client-Server model19 6 SCSI client-server model20 7 SCSI I/O s
43、ystem and domain model 21 8 Overall SCSI domain model.22 9 SCSI domain model23 10Service delivery subsystem model.23 11SCSI initiator device model 25 12SCSI target device model.26 13 SCSI target/initiator device model27 14 Logical unit model.29 15 Eight Byte logical unit number structure adjustments
44、.32 16 SCSI device functional models.41 17 Multiple port target SCSI device structure model.42 18 Multiple port SCSI initiator device structure model.43 19 Multiple port target/initiator SCSI device structure model.44 20 SCSI target device configured in a single SCSI domain 45 21 SCSI target device
45、configured in multiple SCSI domains.46 22 SCSI target device and SCSI initiator device configured in a single SCSI domain46 23 Dependent logical unit model.48 24 Example of hierarchical system diagram49 25 Protocol service reference model.50 26 Protocol service model.51 27 Request-Response ULP trans
46、action and related LLP services52 28 Model for Data-In and Data-Out data transfers62 29 Command processing events.67 30 Linked command processing events68 31 Task management processing events87 32 Example of Dormant state task behavior91 33 Task states.92 34 Head of queue tasks and blocking boundari
47、es (example 1).94 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:16:29 MDTNo reproduction or networking permitted without license from IHS -,-,- vi 35 Head of queue tasks a
48、nd blocking boundaries (example 2).95 36 Ordered tasks and blocking boundaries .96 37 ACA task example 97 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:16:29 MDTNo reproduction or networking permitted without license from IHS -,-,- vii Foreword (This foreword is not part of ANSI INCITS 366-2003.) The purpose of this standard is to provide a