《ANSI-INCITS-447-2008.pdf》由会员分享，可在线阅读，更多相关《ANSI-INCITS-447-2008.pdf（154页珍藏版）》请在三一文库上搜索。
1、American National Standard Developed by for Information Technology SCSI Architecture Model - 4 SAM-4 INCITS 447-2008 INCITS 447-2008 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=HP Monitoring/1111111164 Not for Resale, 04/06/2009 03:02:54 MDTNo rep
2、roduction or networking permitted without license from IHS -,-,- Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=HP Monitoring/1111111164 Not for Resale, 04/06/2009 03:02:54 MDTNo reproduction or networking permitted without license from IHS -,-,- INC
3、ITS 447-2008 American National Standard for Information Technology SCSI Architecture Model - 4 (SAM-4) Secretariat Information Technology Industry Council Approved November 14, 2008 American National Standards Institute, Inc. Abstract This standard specifies the SCSI Architecture Model. The purpose
4、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. Copyright American National Standards Institute Provided by IHS under li
5、cense with ANSI Licensee=HP Monitoring/1111111164 Not for Resale, 04/06/2009 03:02:54 MDTNo reproduction or networking permitted without license from IHS -,-,- Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and other criteria for a
6、pproval 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 means much more than a simple majority, but not necessa
7、rily 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 preclude anyone, whether he has approved the standards
8、 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 interpretation of any American National Standard. Moreover, no pe
9、rson 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 N
10、OTICE: 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 informat
11、ion 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 2008 by Information Technology Industry Council (ITI) All rights reserved. No pa
12、rt 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 of this standard have requested that holders of pat
13、ents 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 sta
14、ndard 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 it processes. No representation is made or implied
15、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=HP Monitoring/1111111164 Not for Resale, 04/06/2009 03:02:54 MDTNo reproduction or networking permitted without license f
16、rom IHS -,-,- i Contents Page Foreword .xi Introduction .xiv 1 Scope. 1 1.1 Introduction 1 1.2 Requirements precedence. 1 1.3 SCSI standards family . 2 2 References. 4 2.1 Normative references. 4 2.2 Approved references 4 2.3 References under development. 4 2.4 Other references 4 3 Definitions, symb
17、ols, abbreviations, and conventions . 5 3.1 Definitions 5 3.2 Acronyms. 12 3.3 Keywords. 12 3.4 Editorial conventions 13 3.5 Numeric conventions . 13 3.6 Notation conventions . 14 3.6.1 UML notation conventions . 14 3.6.1.1 Notation conventions overview 14 3.6.1.2 Constraint and note conventions . 1
18、4 3.6.1.3 Class diagram conventions 14 3.6.1.4 Object diagram conventions 18 3.6.2 Notation for procedure calls. 20 3.6.3 Notation for state diagrams 20 4 SCSI architecture model 22 4.1 Introduction 22 4.2 The SCSI distributed service model. 22 4.3 The SCSI client-server model 23 4.3.1 SCSI client-s
19、erver model overview 23 4.3.2 Synchronizing client and server states 24 4.3.3 Request/Response ordering 24 4.4 The SCSI structural model. 25 4.5 SCSI classes 26 4.5.1 SCSI classes overview 26 4.5.2 SCSI Domain class 27 4.5.3 Service Delivery Subsystem class. 28 4.5.4 SCSI Device class . 29 4.5.4.1 S
20、CSI Device class overview 29 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=HP Monitoring/1111111164 Not for Resale, 04/06/2009 03:02:54 MDTNo reproduction or networking permitted without license from IHS -,-,- ii Page 4.5.4.2 SCSI Device Name attrib
21、ute 29 4.5.5 SCSI Port class 30 4.5.5.1 SCSI Port class overview 30 4.5.5.2 Relative Port Identifier attribute . 31 4.5.6 SCSI Target Port class 31 4.5.6.1 SCSI Target Port class overview. 31 4.5.6.2 Target Port Identifier attribute 31 4.5.6.3 Target Port Name attribute 31 4.5.7 SCSI Initiator Port
22、class. 32 4.5.7.1 SCSI Initiator Port class overview 32 4.5.7.2 Initiator Port Identifier attribute. 32 4.5.7.3 Initiator Port Name attribute. 32 4.5.8 Task Router class 32 4.5.9 SCSI Initiator Device class 33 4.5.10 Application Client class 34 4.5.11 Application Client Task Management Function clas
23、s 34 4.5.11.1 Application Client Task Management Function class overview. 34 4.5.11.2 Function Identifier attribute 34 4.5.11.3 Nexus attribute. 34 4.5.11.4 Service Response attribute 34 4.5.11.5 Additional Response Information attribute. 34 4.5.12 Application Client Task Set class. 35 4.5.13 Applic
24、ation Client Command class 35 4.5.13.1 Application Client Command class overview. 35 4.5.13.2 I_T_L_Q Nexus attribute 35 4.5.13.3 CDB attribute . 35 4.5.13.4 Task Attribute attribute. 35 4.5.13.5 Status attribute. 35 4.5.13.6 Service Response attribute 35 4.5.13.7 Data-In Buffer attribute 35 4.5.13.
25、8 Data-In Buffer Size attribute 35 4.5.13.9 Data-Out Buffer attribute 35 4.5.13.10 Data-Out Buffer size attribute 36 4.5.13.11 CRN attribute. 36 4.5.13.12 Command Priority attribute 36 4.5.13.13 First Burst Enabled attribute 36 4.5.13.14 Sense Data attribute 36 4.5.13.15 Sense Data Length attribute
26、36 4.5.13.16 Status Qualifier attribute 36 4.5.14 SCSI Target Device class 36 4.5.15 Level 1 Hierarchical Logical Unit class 37 4.5.16 Level 2 Hierarchical Logical Unit class 39 4.5.17 Level 3 Hierarchical Logical Unit class 39 4.5.18 Level 4 Hierarchical Logical Unit class 39 4.5.19 Logical Unit cl
27、ass. 40 4.5.19.1 Logical Unit class overview 40 4.5.19.2 LUN attribute 42 4.5.19.3 Logical Unit Name attribute . 42 4.5.19.4 Dependent Logical Unit attribute . 42 4.5.20 Device Server class. 43 4.5.21 Task Manager class. 43 4.5.22 Task Set class . 43 Copyright American National Standards Institute P
28、rovided by IHS under license with ANSI Licensee=HP Monitoring/1111111164 Not for Resale, 04/06/2009 03:02:54 MDTNo reproduction or networking permitted without license from IHS -,-,- iii Page 4.5.23 Command class .43 4.5.23.1 Command class overview 43 4.5.23.2 I_T_L_Q Nexus attribute43 4.5.23.3 Task
29、 Attribute attribute.43 4.5.23.4 CDB attribute44 4.5.23.5 CRN attribute .44 4.5.23.6 Command Priority attribute 44 4.5.23.7 Status attribute.44 4.5.23.8 Sense Data attribute 44 4.5.23.9 Sense Data Length attribute 44 4.5.23.10 Service Response attribute44 4.5.23.11 Status Qualifier attribute.44 4.5.
30、23.12 First Burst Enabled attribute.44 4.5.23.13 Device Server Buffer attribute44 4.5.23.14 Application Client Buffer Offset attribute 44 4.5.23.15 Request Byte Count attribute.44 4.5.23.16 Delivery Result attribute.44 4.5.24 Task Management Function class .45 4.5.24.1 Task Management Function class
31、 overview 45 4.5.24.2 Function Identifier attribute.45 4.5.24.3 Nexus attribute.45 4.5.24.4 Service Response attribute45 4.5.24.5 Additional Response Information attribute .45 4.5.25 Well Known Logical Unit class .45 4.6 Logical unit number (LUN) .46 4.6.1 Introduction 46 4.6.2 Logical unit represen
32、tation format46 4.6.3 LUNs overview.46 4.6.4 Minimum LUN addressing requirements46 4.6.5 Single level LUN structure46 4.6.6 Eight byte LUN structure48 4.6.7 Peripheral device addressing method51 4.6.8 Flat space addressing method.52 4.6.9 Logical unit addressing method .53 4.6.10 Extended logical un
33、it addressing .54 4.6.11 Well known logical unit addressing 57 4.6.12 Extended flat space addressing method57 4.6.13 Logical unit not specified addressing .58 4.7 Nexus.58 4.7.1 Nexus overview58 4.7.2 Command identifier59 4.7.3 Nexus usage rules .59 4.8 SCSI ports59 4.8.1 SCSI port configurations 59
34、 4.8.2 SCSI devices with multiple ports60 4.8.3 Multiple port SCSI target device structure60 4.8.4 Multiple port SCSI initiator device structure .61 4.8.5 Multiple port SCSI device structure62 4.8.6 SCSI initiator device view of a multiple port SCSI target device63 4.8.7 SCSI target device view of a
35、 multiple port SCSI initiator device66 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=HP Monitoring/1111111164 Not for Resale, 04/06/2009 03:02:54 MDTNo reproduction or networking permitted without license from IHS -,-,- iv Page 4.9 The SCSI model fo
36、r distributed communications. 66 5 SCSI command model. 71 5.1 The Execute Command procedure call . 71 5.2 Command descriptor block (CDB). 72 5.3 Status. 73 5.3.1 Status codes 73 5.3.2 Status qualifier. 74 5.3.3 Status precedence. 76 5.4 SCSI transport protocol services in support of Execute Command.
37、 77 5.4.1 Overview 77 5.4.2 Command and status SCSI transport protocol services 77 5.4.2.1 Command and status SCSI transport protocol services overview. 77 5.4.2.2 Send SCSI Command SCSI transport protocol service request 78 5.4.2.3 SCSI Command Received SCSI transport protocol service indication. 7
38、8 5.4.2.4 Send Command Complete SCSI transport protocol service response. 79 5.4.2.5 Command Complete Received SCSI transport protocol service confirmation 79 5.4.3 Data transfer SCSI transport protocol services . 80 5.4.3.1 Introduction 80 5.4.3.2 Data-In delivery service . 82 5.4.3.2.1 Send Data-I
39、n SCSI transport protocol service request 82 5.4.3.2.2 Data-In Delivered SCSI transport protocol service confirmation . 82 5.4.3.3 Data-Out delivery service 82 5.4.3.3.1 Receive Data-Out SCSI transport protocol service request 82 5.4.3.3.2 Data-Out Received SCSI transport protocol service confirmati
40、on. 83 5.4.3.4 Terminate Data Transfer service . 83 5.4.3.4.1 Terminate Data Transfer SCSI transport protocol service request 83 5.4.3.4.2 Data Transfer Terminated SCSI transport protocol service confirmation 84 5.5 Command lifetimes 84 5.6 Aborting commands. 85 5.7 Command processing example . 89 5
41、.8 Commands that complete with CHECK CONDITION status. 90 5.8.1 Overview 90 5.8.2 Handling commands when ACA is not in effect. 90 5.8.3 Aborting commands terminated with a CHECK CONDITION status without establishing an ACA. 90 5.9 Auto contingent allegiance (ACA) 91 5.9.1 ACA overview 91 5.9.2 Estab
42、lishing an ACA 92 5.9.3 Handling new commands received on the faulted I_T nexus when ACA is in effect 92 5.9.4 Handling new commands received on non-faulted I_T nexuses when ACA is in effect 93 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=HP Monito
43、ring/1111111164 Not for Resale, 04/06/2009 03:02:54 MDTNo reproduction or networking permitted without license from IHS -,-,- v Page 5.9.4.1 Command processing permitted for commands received on non-faulted I_T nexuses during ACA 93 5.9.4.2 Handling new commands received on non-faulted I_T nexuses w
44、hen ACA is in effect93 5.9.5 Clearing an ACA condition.94 5.10 Overlapped commands95 5.11 Incorrect logical unit .95 5.12 Task attribute exception conditions95 5.13 Sense data.96 5.14 Unit attention condition.96 6 SCSI events and event notification model .100 6.1 SCSI events overview100 6.2 Establis
45、hing a unit attention condition subsequent to detection of an event 102 6.3 Conditions resulting from SCSI events 103 6.3.1 Power on103 6.3.2 Hard reset 104 6.3.3 Logical unit reset104 6.3.4 I_T nexus loss104 6.3.5 Power loss expected105 6.4 Event notification SCSI transport protocol services .105 7
46、 Task management functions107 7.1 Task management function procedure calls 107 7.2 ABORT TASK 108 7.3 ABORT TASK SET 109 7.4 CLEAR ACA.109 7.5 CLEAR TASK SET.109 7.6 I_T NEXUS RESET110 7.7 LOGICAL UNIT RESET .110 7.8 QUERY TASK110 7.9 QUERY TASK SET111 7.10 QUERY ASYNCHRONOUS EVENT111 7.11 Task mana
47、gement function lifetime .112 7.12 Task management SCSI transport protocol services.113 7.12.1 Task management SCSI transport protocol services overview113 7.12.2 Send Task Management Request SCSI transport protocol service request113 7.12.3 Task Management Request Received SCSI transport protocol s
48、ervice indication.114 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=HP Monitoring/1111111164 Not for Resale, 04/06/2009 03:02:54 MDTNo reproduction or networking permitted without license from IHS -,-,- vi Page 7.12.4 Task Management Function Executed SCSI transport protocol service response. 114 7.12.5 Received Task Management Function Executed SCSI transport protocol service confirmation 115 7.13 Task management function example. 115 8 Task