`
`(formerly ANSI X3.270-1996 (R2001))
`
`for Information Technology –
`SCSI-3 Architecture Model
`
`
` CROSSROADS EXHIBIT 2047
` Cisco Systems et al v Crossroads Systems, Inc.
` IPR2014-01544
`
`1 of 78
`
`
`
`ANSI INCITS 270-1996 (R2001)
`
`(formerly ANSI X3.270-1996 (R2001))
`
`for Information Technology –
`SCSI-3 Architecture Model
`
`1 of 78
`
`
`
`ANSI@
`X3.270-1 996
`
`American National Standard
`for Information Technology
`-
`
`SCSI-3 Architecture Model
`
`Secretariat
`Information Technology
`
`Industry Council
`
`Approved April 8, 1996
`American National Standards
`-
`_
`
`Institute,
`
`Inc.
`
`Abstract
`
`is to pro-
`Model. The purpose of the architecture
`the SCSI Architecture
`specifies
`This standard
`for the coordination
`of SCSI-3
`standards
`and
`to specify
`those aspects of
`vide a common basis
`SCSI-3
`I/O system behavior
`that are
`independent
`of a particular
`technology
`and common
`to all
`implementations.
`
`2 of 78
`
`
`
`American
`National
`Standard
`
`Approval of an American National Standard requires review 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 a concerted 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 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 interpretation 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 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 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 developer or 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 West 42nd Street, New York, New York 10036
`
`Copyright (cid:211) 1996 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, 1250 Eye Street NW,
`Washington, DC 20005.
`
`Printed in the United States of America
`
`3 of 78
`
`
`
`Contents
`
`Foreword
`0
`
`1
`
`1.1
`1.2
`1.3
`1.3.1
`1.3.2
`1.3.3
`1.3.4
`
`2
`
`3
`
`3.1
`3.2
`3.3
`3.4
`3.5
`3.6
`3.7
`3.7.1
`3.7.2
`3.7.3
`3.7.4
`3.8
`3.9
`
`4
`
`4.1
`4.2
`4.3
`4.4
`4.5
`4.6
`4.6.1
`4.6.2
`4.7
`4.7.1
`4.7.2
`4.7.3
`4.7.4
`4.8
`
`5
`
`5.1
`5.1.1
`5.1.2
`5.2
`5.3
`
`Page
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
`
`Introduction
`
`.................................................................................
`
`Scope of the Architecture
`
`.............................................................
`
`........................................................
`Scope of SCSI-3 Standards
`...............................................................
`Architecture
`Standard..
`...........................................................
`implementation
`Standards
`.................................................................................
`Commands
`............................................................
`Device Access Methods..
`..........................................................
`SCSI-3 Protocol Standards
`..............................................................
`Interconnect
`Standards
`
`Normative References..
`
`..............................................................
`
`Glossary and Conventions..
`
`........................................................
`
`.....................................................................................
`Glossary
`...................................................
`to SCSI Standards
`References
`.....................................................
`Acronyms
`and Abbreviations:
`..................................................................
`Editorial Conventions
`.................................................................
`Numeric Conventions
`Reserved Fields and Codes..
`......................................................
`.......................................................
`Objects and Object Notation
`..................................................................
`Notation
`for Objects..
`and Identifiers..
`.............................................
`Object Addresses
`.................................................................
`Predefined Objects..
`................................................................
`Hierarchy Diagrams..
`....................................
`and Functions..
`Notation
`for Procedures
`.........................................................................
`State Diagram
`
`SCSI-3 Architecture Model
`
`.......................................................
`
`............................................................................
`Introduction..
`....................................
`The SCSI-3 Distributed Service Model..
`...............................................
`The SCSI-3 Client-Server Model
`....................................................
`The SCSI-3 Structural Model
`...........................................................................
`SCSI Domain
`.............................................
`The Service Delivery Subsystem..
`...................................
`Synchronizing
`Client and Server States..
`...................................................
`Request/Response
`Ordering..
`...............................................................
`SCSI Device Models..
`.................................................................
`Initiator Model
`SCSI
`...........................................................................
`SCSI Target..
`..................................................................
`The Task Manager..
`Logical Unit.. ............................................................................
`..................
`The SCSI-3 Model
`for Distributed Communications..
`
`SCSI Command Model
`
`.............................................................
`
`Command Descriptor Block.. .....................................................
`......................................................................
`Operation Code..
`............................................................................
`Control Field
`......................................................................................
`Status
`Protocol Services
`in Support of Execute Command..
`
`..................
`
`1
`
`1
`
`.2
`.3
`3
`3
`.3
`3
`.3
`
`.4
`
`.4
`
`4
`.8
`.8
`9
`.9
`.9
`.9
`.9
`.I0
`.I0
`.I0
`.I1
`.I3
`
`.I4
`
`.I4
`.I5
`.I6
`.18
`.20
`.21
`.22
`.22
`.23
`.25
`.25
`.26
`.26
`.28
`
`.31
`
`.33
`.34
`.35
`.36
`.37
`
`I
`
`4 of 78
`
`
`
`5.3.1
`5.3.2
`5.3.3
`5.4
`5.5
`5.5.1
`. 5.5.2
`5.6
`5.6.1
`5.6.2
`5.6.3
`5.6.4
`5.6.5
`5.6.6
`
`..............................................
`Data Transfer Protocol Services..
`Data-In Delivery Service..
`.........................................................
`..........................................................
`Data-Out Delivery service
`Task and Command Lifetimes..
`.................................................
`Command Processing Examples..
`.............................................
`Unlinked Command Example..
`..................................................
`Linked Command Example
`.......................................................
`Command Processing Considerations
`and Exception Conditions
`Auto Contingent Allegiance..
`.....................................................
`Overlapped Commands
`............................................................
`Incorrect Logical Unit Selection..
`...............................................
`Sense Data ..............................................................................
`Unit Attention Condition..
`..........................................................
`Hard Reset..
`.............................................................................
`
`6
`
`Task Management
`
`Functions
`
`....................................................
`
`.........................................................................
`ABORT TASK..
`ABORT TASK SET ...................................................................
`CLEAR ACA..
`...........................................................................
`CLEAR TASK SET.. ..................................................................
`......................................................................
`TARGET RESET
`TERMINATE
`TASK..
`.................................................................
`Task Management
`Protocol Services
`........................................
`Task Management
`Function Example..
`......................................
`
`Task Set Management..
`
`............................................................
`
`...........................................................................
`Terminology..
`Task Management
`Events..
`.......................................................
`Task Abort Events
`....................................................................
`Task States
`..............................................................................
`Enabled
`...................................................................................
`Blocked..
`..................................................................................
`...................................................................................
`Dormant
`Ended..
`....................................................................................
`Task Attributes..
`.......................................................................
`SIMPLE Task..
`.........................................................................
`ORDERED
`Task..
`....................................................................
`HEAD OF QUEUE Task..
`..........................................................
`ACA Task.. ...............................................................................
`Task State Transitions..
`.............................................................
`Transition SO:Sl
`(ordered
`task)
`................................................
`Transition SO:Sl
`(simple
`task)
`..................................................
`Transition SO:S3; S2:S3
`...........................................................
`Transiiton Sl :S2 .......................................................................
`Transition Sl :S3.. .....................................................................
`Transition S2:Sl..
`.....................................................................
`Task Set Management
`Examples
`..............................................
`Blocking Boundaries..
`...............................................................
`HEAD OF QUEUE Tasks
`..........................................................
`Ordered Tasks
`.........................................................................
`ACA Task.. ...............................................................................
`Deferred Task Completion
`........................................................
`
`6.1
`6.2
`.e 6.3
`6.4
`6.5
`6.6
`6.7
`
`--$.8
`
`7
`
`4-
`
`-_
`
`--
`
`_
`
`7.1
`7.2
`7.3
`7.4
`7.4.1
`7.4.2
`7.4.3
`7.4.4
`7.5
`7.5.1
`7.5.2
`7.5.3
`7.5.4
`7.6
`7.6.1
`7.6.2
`7.6.3
`7.6.4
`7.6.5
`7.6.6
`7.7
`7.7.1
`7.7.2
`7.7.3
`7.7.4
`7.7.5
`
`ii
`
`Page
`.38
`.39
`40
`.40
`.41
`.41
`.42
`..4 4
`.44
`.45
`.46
`.46
`.48
`.49
`
`.49
`
`.51
`.51
`.52
`.52
`.52
`.52
`.53
`.54
`
`.55
`
`.56
`.56
`.57
`.57
`.57
`.58
`.58
`.58
`.58
`.59
`.59
`.59
`.59
`59
`.60
`.60
`.61
`.61
`.61
`.61
`.61
`.61
`.62
`.63
`.65
`.66
`
`5 of 78
`
`
`
`Page
`
`Object Definitions
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`SCSI Domain
`
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
`
`Service Delivery Subsystem
`
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
`
`SCSI Device
`
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
`
`Initiator
`
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
`
`Target
`
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
`
`Logical Unit
`
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
`
`Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
`
`Figures
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`Requirements
`
`Precedence..
`
`............................................................
`
`Functional Scope of SCSI-3 Standards..
`
`..........................................
`
`Example of Hierarchy Diagram
`
`......................................................
`
`State Diagram..
`
`.............................................................................
`
`Client-Server Model
`
`......................................................................
`
`SCSI Client-Server Model
`
`.............................................................
`
`SCSI
`
`I/O System and Domain Model..
`
`............................................
`
`SCSI Hierarchy..
`
`...........................................................................
`
`Domain Functional Model..
`
`............................................................
`
`10
`
`Domain Hierarchy
`
`.........................................................................
`
`.l
`
`.2
`
`.12
`
`.14
`
`.16
`
`.I7
`
`.18
`
`.19
`
`.20
`
`.20
`
`-_
`
`--
`
`-.
`
`z
`
`4-
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`Service Delivery Subsystem Hierarchy..
`
`.........................................
`
`SCSI Device Functional Models..
`
`...................................................
`
`SCSI Device Hierarchy Diagram..
`
`..................................................
`
`Target Object Hierarchy
`
`................................................................
`
`Logical Unit Object Hierarchy
`
`........................................................
`
`Protocol Service Reference Model..
`
`...............................................
`
`Protocol Service Model
`
`.................................................................
`
`.21
`
`.23
`
`.24
`
`.25
`
`.26
`
`.29
`
`.30
`
`Request-Response
`
`ULP Transaction
`
`and Related LLP Services..
`
`.. ..3 1
`
`Model
`
`for buffered data transfers
`
`...................................................
`
`Command processing
`
`events..
`
`.......................................................
`
`Linked Command Processing Events..
`
`...........................................
`
`Task Management
`
`Request Processing
`
`.........................................
`
`Example of Dormant Task Behavior..
`
`.............................................
`
`Task States
`
`..................................................................................
`
`HEAD OF QUEUE Tasks
`
`..............................................................
`
`HEAD OF QUEUE Tasks and Blocking Boundaries..
`
`.......................
`
`.38
`
`.42
`
`.43
`
`.55
`
`.58
`
`.60
`
`.62
`
`.63
`
`...
`III
`
`6 of 78
`
`
`
`Ordered Tasks and Blocking Boundaries..
`
`......................................
`
`ACA Task Example
`
`.......................................................................
`
`Example of Deferred Task Completion
`
`...........................................
`
`27
`
`28
`
`29
`
`Tables
`
`. 1
`
`Format of Command Descriptor Block..
`
`..........................................
`
`2
`
`3
`
`4
`
`Operation Code
`
`............................................................................
`
`Control Field..
`
`...............................................................................
`
`Status Codes..
`
`..............................................................................
`
`Page
`.64
`
`.65
`
`.66
`
`.34
`
`.35
`
`.35
`
`.36
`
`-_
`
`--
`
`-.-
`
`-_
`
`4-
`
`iv
`
`7 of 78
`
`
`
`Foreword
`
`(This foreword
`
`is not part of American National Standard X3.270-1996.)
`
`of
`for the coordination
`is to provide a basis
`The purpose of this standard
`and to define
`requirements,
`common
`to all
`SCSI-3 standards
`development
`SCSI-3
`technologies
`and implementations,
`which are essential
`for compat-
`ibility with host SCSI-3 application
`software
`and device-resident
`firmware
`across all SCSI-3 protocols. These
`requirements
`are defined
`through a ref-
`erence model which specifies
`the behavior
`and abstract
`structure which
`is
`generic
`to all SCSI-3
`I/O system
`implementations.
`
`of inter-
`there may arise questions
`document,
`technical
`As with any other
`are
`implemented.
`The X3 Committee
`has
`pretation
`as new products
`established
`procedures
`to issue
`technical
`opinions
`concerning
`the stan-
`dards developed
`by the X3 organization.
`These procedures may result
`in
`SCSI Technical
`Information
`Bulletins
`being published
`by X3.
`
`Committee
`of the Technical
`the opinion
`reflecting
`while
`These bulletins,
`solely as supplementary
`infor-
`are intended
`the standard,
`which developed
`mation
`to other users of the standard.
`This standard, ANSI X3.270-1996,
`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 con-
`tents of these Technical
`Information
`Bulletins.
`
`Requests
`
`for
`
`interpretation,
`
`suggestions
`
`for
`
`improvement
`
`or addenda,
`
`or
`
`to ANSI by the
`for submittal
`and approved
`This standard was processed
`Accreditel
`~Standards~ Comr.G++-
`Illlree
`onlnformatron
`~Techr;oto~gy;~)(3;~
`of this standard
`does not necessarily
`imply
`that all
`approval
`Committee
`voted
`for
`its approval.
`At the
`time
`it approved
`this
`committee members
`standard,
`the X3 Committee
`had the following members:
`
`James D. Converse, Chair
`Donald C. Loughry, Vice-Chair
`Kate McMillan, Secretary
`
`Represented
`Organization
`American Nuclear Society
`
`AMP,
`
`Apple Computer,
`
`AT&T Global
`
`Information Systems
`
`Bmpaq
`
`Eastman Kodak Company
`
`Hewlett-Packard
`
`Hitachi America,
`
`Hughes Aircraft Company
`
`Name of Representative
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Geraldine C. Main
`Sally Hartzell
`(Alt.)
`Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Edward Kelly
`Charles Brill (Alt.)
`Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . David K. Michael
`Jerry Kellenbenz
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Thomas F. Frost
`Clyde Robichaux
`Inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Patrick L. Harris
`Bull HN Information Systems,
`Computers
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . ;;.;..~.;.;.;.;.;;.;;..
`..; . . . . ;. Ed Cikkoia
`Digital Equipment Corporation
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scott K. Jameson
`Richard Hovey
`(Alt.)
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . James D. Converse
`Michael Nier (Alt.)
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Donald C. Loughry
`Karen Higginbottom
`Ltd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . John Neumann
`Kei Yamashita
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Harold Zebrack
`
`(Alt.)
`
`(Alt.)
`
`(Alt.)
`
`(Alt.)
`
`V
`
`8 of 78
`
`
`
`Name of Representative
`Represented
`Organization
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Joel Urman
`IBM Corporation
`Mary Anne Lawler
`
`(Ah.)
`
`National
`
`Institute of Standards
`
`and Technology
`
`1 Northern Telecom,
`
`Share,
`
`Storage Technology Corporation
`
`(AIL)
`
`(Alt.)
`
`(Alt.)
`
`(AIL)
`
`(Alt.)
`
`(Alt.)
`
`(Alt.)
`
`of Computer
`for Certification
`Institute
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kenneth Zemrowski
`(ICCP)
`Professionals
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dennis Bodson
`Systems
`National Communications
`Granger Kelley
`. . . . . . . . . . . . . . . . . . Michael Hogan
`James H. Burrows
`Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mel Woinsky
`John Pugh (Alt.)
`Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gary Ainsworth
`(Alt.)
`David Thewlis
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Joseph S. Zajaczkowski
`Samuel D. Cheatham
`Inc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gary S. Robinson
`Sun Microsystems,
`Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Donald Ft. Deutsch
`Sybase,
`Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clyde Camp
`Texas
`Instruments,
`Fritz Whittington
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Eddie T. Morioka
`Paul D. Jahnke
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . John L. Hill
`Stephen P. Oksala
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Jerry L. Smith
`C. J. Pasquariello
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carol S. Blackston
`Bruce Ft. White (Alt.)
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . John Flannery
`Roy Pierce
`(Alt.)
`
`3M Company
`
`Unisys Corporation
`
`U.S. Department
`
`of Defense
`
`*L
`
`U.S. Department
`
`of Energy
`
`Xerox Corporation
`
`-_
`
`-..
`
`-- -
`
`*
`
`4-
`
`vi
`
`9 of 78
`
`
`
`X3TlO on Lower Level
`Committee
`Technical
`this standard,
`had the following members:
`
`Interfaces, which developed
`
`John B. Lohmeyer, Chairman
`Lawrence
`J. Lamers, Vice-Chairman
`Ralph 0. Weber, Secretary
`
`Dal Allan
`Paul D. Aloisi
`Ron Apt
`Geoffrey Barton
`Robert Bellino
`Charles Brilla
`Peter Brown
`Michael Bryan
`Joe Chen
`Chris D’lorio
`Joe Dambach
`Jan V. Dedek
`Stephen G. Finch
`Edward Fong
`Louis Grantham
`Norm Harris
`Edward Haske
`Dennis R. Haynes
`Stephen F. Heil
`Stephen Holmstead
`David Hudson
`Peter Johansson
`Gerry Johnsen
`Skip Jones
`Edward Lappin
`Joe Lawlor
`David Lawson
`Robert Liu
`Bob Masterson
`David McFadden
`James McGrath
`Pete McLean
`Patrick Mercer
`Gene Milligan
`Charles Monia
`Dennis P. Moore
`Ian Morrell
`John Moy
`S. Nadershahi
`Erich Oetting
`Alan R. Olson
`Dennis Pak
`Duncan Penman
`George Penokie
`Doug Piper
`
`Donna Pope
`Robert Reiseh
`Scott Smyers
`Robert N. Snively
`Jeff Stai
`Gary R. Stephens
`Clifford E. Strang Jr.
`Thomas
`‘Rick’ Tewell
`Dean Wallace
`Harvey Waltersdorf
`Gary M. Watson
`Michael Wingard
`Mark Woithe
`(Alt.)
`Ezra Alcudia
`(AIL)
`Michael Alexenko
`Steven A. Anderson
`(Alt.)
`David Andreatta
`(AIL)
`Tak Asami
`(Alt.)
`Akram Atallah
`(AIL)
`Paul Boulay
`(AIL)
`Kevin Calvert
`(Alt.)
`John Cannon
`(AIL)
`Kurt Chan (Alt.)
`Shufan Chan (AIL)
`Ting Li Chan (Alt.)
`Mike Chenery
`(Alt.)
`Nancy Cheng
`(AIL)
`William Clemmey
`(Alt.)
`Dan Colegrove
`(Alt.)
`Roger Cummings
`(Alt.)
`Zane Daggett
`(Alt.)
`William Dallas
`(Alt.)
`Varouj Der-Hacopian
`Dhiru N. Desai (Alt.)
`Mike Eneboe
`(Alt.)
`Timothy Feldman
`(Alt.)
`Edward A. Gardner
`(Alt.)
`John Geldman
`(Alt.)
`Chuck Grant (Alt.)
`Peter Haas (Alt.)
`Douglas Hagerman
`Kenneth J. Hallam
`William Ham (Alt.)
`Tom Hanan
`(Alt.)
`Rick Heidick
`(Alt.)
`
`(Alt.)
`(Alt.)
`
`(AIL)
`
`(Alt.)
`
`(AIL)
`
`(Alt.)
`Mike Hetzel
`Gerald Houlder
`(Alt.)
`Paul Jackson
`(AIL)
`Kevin James
`(Alt.)
`Brian Johnson
`(Alt.)
`Mark Jordan
`(Alt.)
`Richard Kalish
`(Alt.)
`Greg Kapraun
`(AIL)
`Thomas J. Kulesza
`Dennis Lang (AIL)
`Bill Mable
`(Alt.)
`(Alt.)
`Gerald Marazas
`(Alt.)
`John Masiewicz
`Daniel E. Moczarny
`(Alt.)
`E.J. Mondor
`(Alt.)
`Jay Neer (Alt.)
`Tim Norman
`(AIL)
`Vit Novak
`(Alt.)
`Kevin R. Pokorney
`Gary Porter
`(AIL)
`Doug Prins (Alt.)
`(AIL)
`Steven Ramberg
`Ron Roberts
`(Alt.)
`John P. Scheible
`(AIL)
`J. R. Sims (Alt.)
`Michael Smith
`(Alt.)
`Allen Spalding
`(AIL)
`Arlan P. Stone
`(Alt.)
`Joe Stoupa
`(Alt.)
`George Su (Alt.)
`Nicos Syrimis
`(Alt.)
`Pete Tobias
`(AIL)
`Adrienne Turenne
`Joseph Wach
`(Alt.)
`Roger Wang
`(Alt.)
`Dave Weber
`(Alt.)
`Bob Whiteman
`(Alt.)
`Jeffrey L. Williams
`(Alt.)
`Kurt Witte (Alt.)
`Devon Worrell
`(Alt.)
`Charles
`I. Yang
`(Alt.)
`Danny Yeung
`(Alt.)
`Mike Yokoyama
`(AIL)
`
`(Alt.)
`
`vii
`
`10 of 78
`
`
`
`11 of78
`
`11 of 78
`
`
`
`AMERICAN
`
`NATIONAL
`
`STANDARD
`
`ANSI X3.270-1 996
`
`American National Standard
`for information Technology
`-
`
`SCSI-3 Architecture Model
`
`0
`
`Introduction
`
`to SCSI-3
`of standards applicable
`for the coordination
`describes a reference model
`This specification
`requirements which are essential
`for the development
`I/O systems and a set of common behavioral
`of host software and device
`firmware
`that can interoperate with any SCSI-3
`interconnect
`or protocol.
`
`1 Scope of the architecture
`
`consists of the SCSI-3 Architecture Model
`The set of SCSI-3 standards
`SGZI-3
`implementation
`standards described
`in 1 .l.
`
`(this specification)
`
`and
`
`the
`
`implementation
`to SCSI-3
`requirements, which pertain
`This standard defines generic
`An
`implementation
`requirement
`specifies
`behavior
`implementation
`requirements.
`measurable
`or observable
`parameters
`which apply directly
`to an
`implementation.
`impLamentation
`requirements
`defined
`in this document
`are
`the command
`descriptor
`-- 2nd
`the status values
`to be returned upon command completion.
`
`and
`standards,
`of
`in
`terms
`of
`Examples
`block
`format
`
`-_
`
`to
`transformed
`are
`requirements
`Gmric
`standard. An example of a generic
`requirement
`
`by an
`requirements
`implementation
`is the hard reset behavior specified
`
`implementation
`in 5.6.6.
`
`SCSI-3 Architecture Model
`
`SCSI-3 mplmwltaaon
`sMd.,d
`
`sCY-3 lmplmrnron
`Standard
`
`t
`
`SCSI-3
`lmpbmontaion
`
`Figure 1 - Requirements
`
`precedence
`
`requirements
`the generic
`reflect
`shall
`standards
`implementation
`in figure 1, all SCSI-3
`As shown
`claiming SCSI-3 compliance
`shall conform
`to
`the
`implementation
`defined
`herein.
`In addition,
`an
`applicable
`implementation
`requirements
`defined
`in
`this standard
`and
`the appropriate
`SCSI-3
`implementation
`standards.
`In the event of a conflict
`between
`this document
`and other SCSI-3
`standards
`under
`the jurisdiction
`of technical
`committee
`X3T10,
`the
`requirements
`of this standard
`shall apply.
`
`12 of 78
`
`
`
`ANSI X3.270-1996
`
`1.1 Scope of SCSI-3 standards
`
`set of specifications
`Figure 2 uses a representative
`relationships
`among SCSI-3 standards.
`
`to show
`
`the
`
`functional
`
`partitions
`
`and
`
`the
`
`Figure 2 - Functional
`
`scope of SCSI-3 standards
`
`The functional
`
`areas define
`
`the scope of each standard as follows:
`
`SCSI Architecture Model: Defines
`standard
`set and
`requirements
`standards.
`
`the SCSI systems model,
`applicable
`to all SCSI-3
`
`partitioning
`the functional
`implementations
`and
`
`of the SCSI-3
`implementation
`
`for
`a device model
`including
`standards which define device classes
`Implementation
`Commands:
`specify
`the required
`commands
`and behavior
`that
`is common
`to all
`each class. These standards
`devices or unique
`to a given class of devices and prescribe
`the rules
`to be followed by an
`initiator
`when sending commands
`to a device.
`
`Common Access Method:
`services
`for device access.
`
`Implementation
`
`standard which defines a host architecture
`
`and set of
`
`standards which define
`Implementation
`Protocols:
`different SCSI-3 devices can communicate.
`
`the
`
`rules
`
`for exchanging
`
`information
`
`so
`
`that
`
`the electrical and signaling
`standards which define
`Implementation
`Interconnects:
`devices
`to interoperate
`over a given physical
`interconnect.
`
`rules essential
`
`for
`
`of
`The diagram
`standards
`included
`standards currently
`
`The
`category.
`each
`fit within
`listed below
`the standards
`figure 2 shows how
`in the diagram are meant
`to serve as examples and may not reflect
`the full set of
`in force.
`
`2
`
`13 of 78
`
`
`
`ANSI X3.270-1 996
`
`1.2 Architecture Standard
`
`(SAM): Defines
`(X3.270-1996)
`SCSI-3 Architecture Model
`the functional
`model
`for SCSI-3
`l/O system and device behavior which applies
`to all SCSI
`access methods, and devices.
`
`partitions and specifies a
`interconnects,
`protocols,
`
`1.3‘
`
`Implementation
`
`Standards
`
`1.3.1 Commands
`
`SCSI-3 Primary Commands
`all SCSI-3
`target devices.
`
`(X3TlO-995D)
`
`(SPC)‘) - Commands
`
`and device behavior
`
`common
`
`to
`
`SCSI-3 Block Commands
`
`(X3TlO-996D)
`
`(SBC)‘)
`
`- Block oriented SCSI-3 devices
`
`(e.g., disks).
`
`SCSI-3 Stream Commands
`
`(X3TlO-997D)
`
`(SSC)‘)
`
`- Stream-oriented
`
`SCSI-3 devices (e.g., tape).
`
`SCSI-3 Graphics Commands
`(e,g., printers).
`
`(X3TlO-998D)
`
`(SGC)‘)
`
`- Graphical
`
`input or output SCSI-3 devices
`
`SCSI-3 Medium Changer Commands
`CD/ROM carousels.
`
`(X3TlO-999D)
`
`(SMC)‘)
`
`- SCSI-3 media changers such as
`
`-
`
`Commands
`SCSI-3 Controller
`_ __tirray
`device controller.
`
`f
`
`(X3TlO-XXXD)
`
`(SCC)‘) - SCSI-3
`
`I/O subsystem
`
`controllers
`
`such as a
`
`1.34; Device Access Methods
`
`(X3.332-199x)‘)
`SCSI-3 Common Access Method
`device
`I/O. CAM defines a layered environment
`language, which allow device drivers
`to be written
`operating
`systems, and host platforms.
`
`a
`
`_
`
`1.3.3 SCSI-3 Protocol Standards
`
`(CAM): A host architecture
`for performing SCSI
`and set of services, based on
`the C computer
`that are independent
`of interconnects,
`protocols,
`
`is a representative
`The