ANSI INCITS 269-1996 Information Technology Fibre Channel Protocol for SCSI.pdf

《ANSI INCITS 269-1996 Information Technology Fibre Channel Protocol for SCSI.pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS 269-1996 Information Technology Fibre Channel Protocol for SCSI.pdf（77页珍藏版）》请在麦多课文档分享上搜索。

1、ANSI INCITS 269-1996 (R2001)(formerly ANSI X3.269-1996 (R2001)for Information Technology -Fibre Channel Protocol for SCSIANSIX3.269-1996American National Standardfor Information Technology Fibre Channel Protocol for SCSISecretariatInformation Technology Industry CouncilApproved April 8, 1996American

2、 National Standards Institute, Inc.AmericanNationalStandardApproval of an American National Standard requires review by ANSI that therequirements for due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is established when, in the judgment of the

3、ANSI Board of StandardsReview, substantial agreement has been reached by directly and materiallyaffected interests. Substantial agreement means much more than a simplemajority, but not necessarily unanimity. Consensus requires that all views andobjections be considered, and that a concerted effort b

4、e made toward theirresolution.The use of American National Standards is completely voluntary; their existencedoes not in any respect preclude anyone, whether he has approved the standardsor not, from manufacturing, marketing, purchasing, or using products, processes,or procedures not conforming to t

5、he standards.The American National Standards Institute does not develop standards and will inno circumstances give an interpretation of any American National Standard.Moreover, no person shall have the right or authority to issue an interpretation ofan American National Standard in the name of the A

6、merican National StandardsInstitute. Requests for interpretations should be addressed to the secretariat orsponsor whose name appears on the title page of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National Sta

7、ndardsInstitute require that action be taken periodically to reaffirm, revise, or withdrawthis standard. Purchasers of American National Standards may receive currentinformation on all standards by calling or writing the American National StandardsInstitute.CAUTION: The developers of this standard h

8、ave requested that holders of patents that may be required for theimplementation of the standard disclose such patents to the publisher. However, neither the developers nor the publisherhave undertaken a patent search in order to identify which, if any, patents may apply to this standard. As of the

9、date ofpublication of this standard and following calls for the identification of patents that may be required for the implementationof the standard, no such claims have been made. No further patent search is conducted by the developer or publisher inrespect to any standard it processes. No represen

10、tation is made or implied that licenses are not required to avoidinfringement in the use of this standard.Published byAmerican National Standards Institute11 West 42nd Street, New York, New York 10036Copyright 1996 by Information Technology Industry Council (ITI)All rights reserved.No part of this p

11、ublication may be reproduced in anyform, 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 AmericaiContentsPageForewordvIntroduction .ix1Scope 12Normative references 13Definitions and abbrev

12、iations 13.1 Definitions 13.2 Abbreviations. 33.3 Editorial conventions . 34General 34.1 Structure and concepts . 34.2 Device management . 54.3 Task management. 64.4 Process login/logout 64.5 Link management 75FCP protocol overview 85.1 FCP addressing and exchange identification 85.2 SCSI address fo

13、rmat for FCP 85.2.1 PA_VAL 95.2.2 FCP_Port identifier 95.2.3 Process associator 95.3 FCP information units 105.4 FCP standard formats . 115.5 FC-PH mappings to SCSI-3 functionality 125.5.1 R_CTL. 125.5.2 D_ID 125.5.3 S_ID 125.5.4 TYPE. 125.5.5 F_CTL. 135.5.6 SEQ_ID. 135.5.7 DF_CTL 135.5.8 SEQ_CNT. 1

14、35.5.9 OX_ID . 135.5.10 RX_ID 135.5.11 RLTV_OFF 136FCP link-level protocol 146.1 Overview of process login/logout 146.2 Process login (PRLI) . 146.2.1 PRLI with IPA required by originator and responder. 156.2.2 PRLI with IPA required by originator and supported by responder. 156.2.3 PRLI with IPA su

15、pported by originator and required by responder. 156.2.4 PRLI with IPA not supported by originator or responder. 166.2.5 New or repeated PRLI 166.2.6 FCP service parameter page for PRLI request. 176.2.6.1 Word 0, Bits 3124: FCP specific code. 17iiPage6.2.6.2 Word 0, Bit 15: ORIGINATORPROCESSASSOCIAT

16、ORVALID176.2.6.3 Word 0, Bit 14: RESPONDERPROCESSASSOCIATORVALID176.2.6.4 Word 0, Bit 13: ESTABLISHIMAGEPAIR176.2.6.5 Word 1: originator process associator .186.2.6.6 Word 2: responder process associator 186.2.6.7 Word 3, Bit 6: DATAOVERLAYALLOWED186.2.6.8 Word 3, Bit 5: INITIATORFUNCTION186.2.6.9 W

17、ord 3, Bit 4: TARGETFUNCTION186.2.6.10 Word 3, Bit 3: COMMAND/DATAMIXEDALLOWED.186.2.6.11 Word 3, Bit 2: DATA/RESPONSEMIXEDALLOWED196.2.6.12 Word 3, Bit 1: READXFER_RDY DISABLED196.2.6.13 Word 3, Bit 0: WRITEXFER_RDY DISABLED.196.2.7 Service parameters for PRLI accept206.2.7.1 Word 0, Bit 13: IMAGEP

18、AIRESTABLISHED206.2.7.2 PRLI ACCEPTRESPONSECODE206.3 Process logout (PRLO) 216.3.1 FCP service parameter page for PRLO request226.3.2 FCP service parameter page for PRLO accept.226.3.2.1 PRLO ACCEPTRESPONSECODE237FCP information unit (IU) formats .247.1 FCP_CMND IU 247.1.1 FCP_LUN 247.1.2 FCP_CNTL25

19、7.1.2.1 Task Codes, Byte 1267.1.2.2 Task management flags, Byte 2 267.1.2.3 Other task management functions.287.1.2.4 Execution management codes, Byte 3 287.1.2.5 Recovery abort.287.1.3 FCP_CDB297.1.4 FCP_DL.297.2 FCP_XFER_RDY IU 297.2.1 DATA_RO.307.2.2 BURST_LEN .307.3 FCP_DATA IU307.4 FCP_RSP IU31

20、7.4.1 FCP_STATUS .317.4.2 FCP_RESID 327.4.3 FCP_SNS_LEN.337.4.4 FCP_RSP_LEN.337.4.5 FCP_RSP_INFO .337.4.6 FCP_SNS_INFO .34Tables1SCSI and FCP functions .42Task management functions, SCSI-3 to FCP .63Definitions of fully qualified exchange identifier 84FCP format for third-party FCP_Port addressabili

21、ty85FCP information units sent to targets106FCP information units sent to initiators .117FCP frame header.12iiiPage8FCP service parameter page, PRLI request. 179Valid and invalid combinations of bits 3 and 0 of word 3 1910FCP service parameter page, PRLI accept 2011FCP service parameter page, PRLO r

22、equest. 2212FCP service parameter page, PRLO accept 2213FCP_CMND payload 2414FCP_CNTL field format 2515TASKATTRIBUTEvalues . 2616FCP_XFER_RDY payload 2917FCP_RSP IU. 3118FCP_STATUS field format 3219FCP_RSP_INFO field format 3420RSP_CODE definitions. 34A.1Extended link service command codes . 36A.2Ex

23、tended link service information units . 36A.3PRLI payload. 39A.4PRLI service parameter page format. 40A.5PRLI accept payload . 41A.6PRLI accept service parameter response page format . 42A.7PRLI accept response code 43A.8PRLO payload . 46A.9PRLO logout parameter page format 47A.10PRLO accept payload

24、. 48A.11PRLO accept logout parameter response page format 48A.12PRLO accept response code 49B.1FCP read operation, example 50B.2FCP write operation, example . 51B.3FCP operation without data transfer, example 51B.4FCP read operation with FCP_XFER_RDY disabled, example 52B.5FCP write operation with F

25、CP_XFER_RDY disabled, example 52B.6FCP linked commands, example. 53B.7FCP read operation with combined data and response, example. 53B.8FCP write operation with combined command and data out, example . 54B.9FCP task management function, example. 54C.1FCP_LUN format, SCSI-3 storage array example. 59C

26、.2FCP_LUN_X format, SCSI-3 storage array example 59C.3Address_Method values 60ivPageFiguresA.1Images/groups of related processes36A.2Image pairs 38B.1Example of class 2 FCP write I/O operation 55B.2Example of class 2 FCP_DATA write sequence56B.3Example of class 2 FCP read I/O operation.57B.4Example

27、of class 2 FCP_DATA read sequence 58C.1SCSI-3 storage array example.60C.2SCSI-3 storage array addressing.61C.3SCSI-3 storage array unit addressing62C.4SCSI-3 storage array diagnostic addressing .62AnnexesAExtended link services 36A.1Extended link service command codes36A.2Process login .36A.2.1 Impl

28、icit process login 37A.2.2 Explicit process login 37A.2.3 PRLI/PRLO relationships42A.2.4 Process login, mode of operation .44A.2.5 Process login, protocol .44A.3Process logout .45A.3.1 PRLO Operation .49BFCP examples.50B.1 Examples of the use of FCP information units.50B.1.1 SCSI FCP read operation.

29、50B.1.2 SCSI FCP write operation.51B.1.3 SCSI FCP operation with no data transfer or with check condition 51B.1.4 SCSI FCP read operation FCP_XFR_RDY disabled52B.1.5 SCSI FCP write operation with FCP_XFR_RDY disabled52B.1.6 SCSI linked commands 53B.1.7 SCSI FCP read operation with combined data in a

30、nd response 53B.1.8 SCSI FCP write operation with combined command and data out.53B.1.9 SCSI FCP task management function54B.2 FCP write example, frame level .55B.3 FCP read example, frame level .57C Logical Unit Number example .59C.1 Logical Unit Number definition .59C.2 Definition of SCSI-3 Contro

31、ller Commands (SCC) addressing model .59C.3 Use of logical unit number in a SCSI-3 storage array61C.3.1 Addressing of SCSI disk array (SCSI-3 storage array): example.61C.3.2 Addressing of volume set logical unit: example61C.3.3 Addressing of peripheral device logical unit: example62D Bibliography 63

32、vThe Fibre Channel Protocol for SCSI (FCP) defines a Fibre Channel map-ping layer (FC-4) that uses the services defined by ANSI X3.230-1994,Fibre Channel Physical and Signaling Interface (FC-PH), to transmitSCSI command, data, and status information between a SCSI initiator anda SCSI target. The use

33、 of the standard enables the transmission of stan-dard SCSI command formats, the transmission of standard SCSI data andparameter strings, and the receipt of SCSI status and sense informationacross the Fibre Channel using only the standard Fibre Channel frame andsequence formats. The FCP will operate

34、 with Fibre Channel Classes ofService 1, 2, and 3 and will operate across Fibre Channel fabrics and arbi-trated loops.Requests for interpretation, suggestions for improvement or addenda, ordefect reports are welcome. They should be sent to the X3 Secretariat,Information Technology Industry Council,

35、1250 Eye Street, NW, Suite 200,Washington DC 20005-3922.This standard was processed and approved for submittal to ANSI by theAccredited Standards Committee on Information Technology, X3.Committee approval of this standard does not necessarily imply that allcommittee members voted for its approval. A

36、t the time it approved thisstandard, the X3 Committee had the following members:James D. Converse, ChairDonald C. Loughry, Vice-ChairKate McMillan, SecretaryOrganization Represented Name of RepresentativeAmerican Nuclear SocietyGeraldine C. MainSally Hartzell (Alt.)AMP, Inc. Edward KellyCharles Bril

37、l (Alt.)Apple Computer, IncDavid K. MichaelJerry Kellenbenz (Alt.)AT&T Global Information Systems .Thomas F. FrostClyde Robichaux (Alt.)Bull HN Information Systems, Inc.Patrick L. HarrisCompaq Computers.Ed OlkkolaDigital Equipment Corporation .Scott K. JamesonRichard Hovey (Alt.)Eastman Kodak Compan

38、yJames D. ConverseMichael Nier (Alt.)Hewlett-Packard Donald C. LaughryKaren Higginbottom (Alt.)Hitachi America, Ltd. .John NeumannKei Yamashita (Alt.)Hughes Aircraft Company Harold ZebrackIBM Corporation Joel UrmanMary Anne Lawler (Alt.)Institute for Certification of Computer Professionals (ICCP).Ke

39、nneth ZemrowskiNational Communications Systems Dennis BodsonGranger Kelley (Alt.)National Institute of Standards and TechnologyMichael D. HoganJames H. Burrows (Alt.)Northern Telecom, Inc. Mel WoinskyJohn Pugh (Alt.)Share, Inc. Gary AinsworthDavid Thewlis (Alt.)Foreword (This foreword is not part of

40、 American National Standard X3.269-1996.)viStorage Technology CorporationJoseph S. ZajaczkowskiSamuel D. Cheatham (Alt.)Sun Microsystems, Inc.Gary S. RobinsonSybase, Inc. Donald R. DeutschTexas Instruments, Inc. .Clyde CampFritz Whittington (Alt.)3M Company .Eddie T. MoriokaPaul D. Jahnke (Alt.)Unis

41、ys CorporationJohn L. HillStephen P. Oksala (Alt.)U.S. Department of Defense Jerry L. SmithC. J. Pasquariello (Alt.)U.S. Department of Energy Carol S. BlackstonBruce R. White (Alt.)Xerox Corporation .John FlanneryRoy Pierce (Alt.)Organization Represented Name of RepresentativeviiSubcommittee X3T10 o

42、n Lower-Level Interfaces, which developed thisstandard, had the following members:John B. Lohmeyer, ChairLawrence J. Lamers, Vice-ChairRalph Weber, SecretaryJason AlbanusI. Dal AllanPaul D. AloisiBruce AndersonGeoffrey BartonRobert BellinoCharles BrillPeter BrownMichael BryanJoe ChenJoe DambachJan V

43、. DedekPeter DoughertyStephen G. FinchBill GallowayLouis GranthamNorm HarrisEdward HaskeStephen F. HeilPeter JohanssonGerry JohnsenSkip JonesRay KallioSam KarunanithiNick LadasEdward LappinDavid LawsonRobert LiuBob MastersonDavid McFaddenJames McGrathPatrick MercerCharles MoniaIan MorrellJohn MoyEri

44、ch OettingAlan R. OlsonDennis PakDuncan PenmanGeorge PenokieDoug PiperDonna PopeRon RobertsJeff RosaRobbie ShergillScott SmyersRobert N. SnivelyJeff StaiGary R. StephensClifford E. Strang, Jr.Dean WallaceHarvey WaltersdorfNeil T. WanamakerDavid WangJeffrey L. WilliamsMark WoitheEzra Alcudia (Alt.)Mi

45、chael Alexenko (Alt.)David Andreatta (Alt.)Tak Asami (Alt.)Akram Atallah (Alt.)Paul Boulay (Alt.)Gary Brandvold (Alt.)Ken Bush (Alt.)John Cannon (Alt.)Kurt Chan (Alt.)Shufan Chan (Alt.)Ting Le Chan (Alt.)William Clemmey (Alt.)Dan Colegrove (Alt.)Roger Cummings (Alt.)William Dallas (Alt.)Kim Davies (

46、Alt.)Varouj Der-Hacopian (Alt.)Timothy Feldman (Alt.)Edward A. Gardner (Alt.)John Geldman (Alt.)Chuck Grant (Alt.)Douglas Hagerman (Alt.)Kenneth J. Hallam (Alt.)William Harn (Alt.)Tom Hanan (Alt.)Rick Heidick (Alt.)Mike Hetzel (Alt.)Gerald Houlder (Alt.)Brian Johnson (Alt.)Mark Jordan (Alt.)Richard

47、Kalish (Alt.)Greg Kapraun (Alt.)Prabhas Kejriwal (Alt.)Dan Kennedy (Alt.)Thomas J. Kulesza (Alt.)Dennis Lang (Alt.)Joe Lawlor (Alt.)Gerald Marazas (Alt.)John Masiewicz (Alt.)Pete McLean (Alt.)Daniel E. Moczarny (Alt.)E. J. Mondor (Alt.)Vit Novak (Alt.)Kevin R. Pokorney (Alt.)Gary Porter (Alt.)Steven

48、 Ramberg (Alt.)Mark Raymond (Alt.)Simone Sadri (Alt.)John P. Scheible (Alt.)Stan Sharp (Alt.)Michael Smith (Alt.)Allen Spalding (Alt.)Arlan P. Stone (Alt.)Joe Stoupa (Alt.)George Su (Alt.)Nicos Syrimis (Alt.)Rich Taborek (Alt.)Pete Tobias (Alt.)Harvey Toyama (Alt.)Adrienne Turenne (Alt.)Joel Urban (

49、Alt.)Joseph Wach (Alt.)Roger Wang (Alt.)Dave Weber (Alt.)Bob Whiteman (Alt.)Michael Wingard (Alt.)Kurt Witte (Alt.)Devon Worrell (Alt.)Charles I. Yang (Alt.)Mike Yokoyama (Alt.)viiiSubcommittee X3T11 on Device Level Interfaces, which contributed agreat deal of analysis, review, and content to this standard, had the follow-ing members:Roger Cummings, ChairCarl Zeitler, Vice-ChairNeil Wanamaker, SecretaryJ. AlbanoD. AllanR. AndersonT. AndersonK. AnnamalaiC. BarronB. BeachA. BediB. BellinoH. BrandtC. BrillR. BrownM. CarboniB. CarlsonK. ChanK. ChennappanB. CookJ. ConnellB. CorneliusS. DeanD