ANSI INCITS 357-2002 Information Technology - Fibre Channel - Virtual Interface Architecture Mapping Protocol (FC-VI).pdf

《ANSI INCITS 357-2002 Information Technology - Fibre Channel - Virtual Interface Architecture Mapping Protocol (FC-VI).pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS 357-2002 Information Technology - Fibre Channel - Virtual Interface Architecture Mapping Protocol (FC-VI).pdf（106页珍藏版）》请在麦多课文档分享上搜索。

1、ANSI INCITS 357-2002for Information Technology Fibre Channel Virtual Interface Architecture Mapping Protocol (FC-VI)ANSIINCITS357-2002ANSIINCITS 357-2002American National Standardfor Information Technology Fibre Channel Virtual Interface ArchitectureMapping Protocol (FC-VI)SecretariatInformation Tec

2、hnology Industry Council (ITI)Approved November 25, 2002American National Standards Institute, Inc.AbstractThis standard defines the Fibre Channel mapping protocol for the Virtual Interface (VI) Architecture (FC-VI).Approval of an American National Standard requires review by ANSI that therequiremen

3、ts for due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is established when, in the judgement of the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially affected interests. Substantial agreement mean

4、s much more thana simple majority, but not necessarily unanimity. Consensus requires that allviews and objections be considered, and that a concerted effort be madetowards their resolution.The use of American National Standards is completely voluntary; theirexistence does not in any respect preclude

5、 anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstances give an interpretation of any A

6、merican NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secretariat or sponsor whose name appears on the

7、titlepage of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American National Stand

8、ards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2002 by Information Technology Industry Council (ITI)A

9、ll rights reserved.No part of this publication 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 AmericaCAUTION: The developers of this standard have requeste

10、d that holders of patents that may berequired 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 identifywhich, if any, patents may apply to this standard. As of the date of publi

11、cation of this standardand following calls for the identification of patents that may be required for the implementation ofthe 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 m

12、ade or impliedthat licenses are not required to avoid infringement in the use of this standard.iContentsPageForeword vi1 Scope 12 Normative references 12.1 Approved references 12.2 References under development .22.3 Other References .22.3.1 VI Architecture 1.0 Reference Specifications .22.3.2 Miscel

13、laneous .23 Definitions and abbreviations 23.1 FC-VI Definitions 23.2 VI Definitions 33.3 Abbreviations .43.4 Editorial conventions 54 Structure and Concepts 64.1 Fibre Channel Structure and Concepts 64.2 FC-VI Structure and Concepts .65 FC-VI protocol Overview .105.1 FC-VI Information Units .105.2

14、FC-VI Message Transfer Operation .105.2.1 FC-VI Message Transfer 105.2.2 FC-VI Send Message Transfer Operation 115.2.3 FC-VI RDMA Write Message Transfer Operation 125.2.4 FC-VI RDMA Read Message Transfer Operation 145.2.5 IU Reception at an FC-VI Endpoint 155.3 FC-VI Connection Setup Operation .165.

15、3.1 FC-VI Client-Server and Peer-Peer Connection Setup 165.3.2 FC-VI Client-Server Connection Setup .175.3.3 FC-VI Peer-to-Peer Connection Establishment 185.3.4 FC_VI Concurrent Peer-to-Peer Connection Setup .205.3.5 FC-VI Disconnect Operation .225.4 Exchange ID Reuse .235.5 Sequence ID Reuse .235.6

16、 Frame Synonym Detection 245.7 VI Message Length 255.8 FC-FS Header Usage for FC-VI .255.8.1 FC-FS Header Usage .255.8.2 CS_CTL Field .265.8.3 TYPE field .265.8.4 F_CTL field .265.8.5 DF_CTL field 265.8.6 SEQ_CNT field .265.8.7 Parameter Field 265.9 FC-VI Device_Header 275.9.1 FC-VI Device_Header De

17、scription .275.9.2 FCVI_HANDLE Field 275.9.3 FCVI_OPCODE Field .285.9.4 FCVI_FLAGS Field .285.9.4.1 FCVI_FLAGS Field Description 285.9.4.2 FCVI_FLAGS for Message Request IUs. 285.9.4.3 FCVI_FLAGS for Message Response IUs 285.9.4.4 FCVI_FLAGS for Connect Request IUs 29iiPage5.9.4.5 FCVI_FLAGS for Con

18、nect Response IUs 305.9.4.6 FCVI_FLAGS for Disconnect IUs . 315.9.5 Reserved Fields . 325.9.6 FCVI_MSG_ID Field 325.9.7 FCVI_PARAMETER Field 325.9.7.1 FCVI_PARAMETER Field Format 325.9.7.2 Connect Response Reason Codes 345.9.7.2.1 Connect Response Non-error Reason Codes. 345.9.7.2.2 Connect Response

19、 Error Reason Codes 345.9.7.3 Message Response / Disconnect Reason Codes 345.9.7.3.1 Descriptor Error Reason Codes 345.9.7.3.2 Remote FC-VI Port Non-Descriptor Errors 355.9.7.3.3 Reserved for Future Expansion. 355.9.7.3.4 Vendor Unique Reason Codes 355.9.8 FCVI_RMT_VA Field . 365.9.9 FCVI_RMT_VA_HAN

20、DLE Field . 365.9.10 FCVI_TOT_LEN Field / FCVI_CONNECTION_ID Field 366 FC-VI Information Unit (IU) Formats . 376.1 FC-VI IU Overview 376.2 FCVI_SEND_RQST IU . 376.2.1 FCVI_SEND_RQST IU Description . 376.2.2 FCVI_SEND_RQST Device_Header Information 376.3 FCVI_SEND_RESP IU 376.3.1 FCVI_SEND_RESP IU De

21、scription . 376.3.2 FCVI_SEND_RESP Device_Header Information 376.4 FCVI_WRITE_RQST IU 386.4.1 FCVI_WRITE_RQST IU Overview . 386.4.2 FCVI_WRITE_RQST IU Device_Header Information 386.5 FCVI_WRITE_RESP IU 386.5.1 FCVI_WRITE_RESP IU Description 386.5.2 FCVI_WRITE_RESP IU Device_Header Information 396.6

22、FCVI_READ_RQST IU . 396.6.1 FCVI_READ_RQST IU Description . 396.6.2 FCVI_READ_RQST IU Device_Header Information . 396.7 FCVI_READ_RESP IU 406.7.1 FCVI_READ_RESP IU Description . 406.7.2 FCVI_READ_RESP IU Device_Header Information 406.8 FCVI_CONNECT_RQST IU 406.8.1 FCVI_CONNECT_RQST IU Description .

23、406.8.2 FCVI_CONNECT_RQST Device_Header Information 416.8.3 FCVI_CONNECT_RQST Payload Information 416.9 FCVI_CONNECT_RESP1 IU 426.9.1 FCVI_CONNECT_RESP1 IU Description 426.9.2 FCVI_CONNECT_RESP1 Device_Header Information 426.9.3 FCVI_CONNECT_RESP1 Payload Information 436.10 FCVI_CONNECT_RESP2 IU 446

24、.10.1 FCVI_CONNECT_RESP2 IU Description 446.10.2 FCVI_CONNECT_RESP2 Device_Header Information 446.11 FCVI_CONNECT_RESP3 IU 446.11.1 FCVI_CONNECT_RESP3 IU Description 446.11.2 FCVI_CONNECT_RESP3 Device_Header Information 446.12 FCVI_DISCONNECT_RQST IU 45iiiPage6.12.1 FCVI_DISCONNECT_RQST IU Descripti

25、on 456.12.2 FCVI_DISCONNECT_RQST Device_Header Information .456.13 FCVI_DISCONNECT_RESP IU .466.13.1 FCVI_DISCONNECT_RESP IU Description 466.13.2 FCVI_DISCONNECT_RESP Device_Header Information .467 FC-VI Addressing and Naming .477.1 FC-VI Addressing and Naming Overview 477.2 FCVI_NET_ADDRESS Format

26、477.3 FCVI_ATTRIBUTES Format 487.4 FC-VI Address Resolution .507.5 FARP ELS 517.6 Name Server Queries 527.7 Validation of Host Address to N_Port Identifier Mappings .527.7.1 Address Mapping Overview 527.7.2 Point-to-Point Topology 527.7.3 Private Loop Topology 527.7.4 Public Loop Topology .537.7.5 F

27、abric Topology 538 FC-VI Error Detection and Recovery 548.1 FC-VI Error Detection and Recovery Overview .548.2 FC-VI Endpoint States .548.3 FCVI_ULP_TIMEOUT Definition 548.4 Message Transfer Error Detection and Recovery Rules .558.4.1 Message Error Detection 558.4.2 Message Transfer Error Recovery .

28、558.5 Connection Setup Error Detection and Recovery Rules 568.5.1 Connection Setup Error Handling Overview .568.5.2 Connection Setup Error Detection 568.5.3 Connection Setup Error Recovery 568.5.4 Connection Setup Originator Retry Rules 578.6 Disconnect Operation Error Detection and Recovery Rules 5

29、78.6.1 Disconnect Operation Error Handling Overview .578.6.2 Disconnect Operation Error Detection 578.6.3 Disconnect Operation Error Recovery Rules 58AnnexesA Concurrent Matching Peer Requests Examples.59B FC-VI Message Transfer Error Handling Examples .64C Connection Setup Error Handling Examples 7

30、3D Disconnect Operation Error Handling Examples 86E Message Streaming for Reliable Reception .89F Enabling Message Transmission in the FC-VI NIC.90ivPageTables1 FC-VI Information Unit Summary 102 Peer B Actions Based on Connect Responses from Peer A . 233 16-Byte FC-VI Device_Header . 274 32-Byte FC

31、-VI Device_Header . 275 FCVI_FLAGS Bit Definitions for Message Request IUs 286 FCVI_FLAGS Bit Definitions for Message Response IUs . 297 FCVI_FLAGS Bit Definitions for Connect Request IUs . 298 FC-VI Connection Mode Definition 309 FCVI_FLAGS Bit Definitions for Connect Response IUs 3010 FCVI_FLAGS B

32、it Definitions for Disconnect IUs . 3111 FCVI_PARAMETER Field for Connect Response and Disconnect IUs 3212 Reason Code for CONN_STS 3313 FCVI_CONNECT_RQST IU Payload Format . 4114 FCVI_CONNECT_RESP1 IU Payload Format . 4315 FCVI_NET_ADDRESS Format 4816 FCVI_ATTRIBUTES Format . 4817 Format of FCVI_AT

33、TR_FLAGS in FCVI_ATTRIBUTES . 4918 FCVI_QOS Format 49vPageFigures1 FC-VI Addressing Objects .92 FC-VI Send for Unreliable Delivery or Reliable Delivery .113 FC-VI Send for Reliable Reception 124 FC-VI RDMA Write for Unreliable Delivery or Reliable Delivery 135 FC-VI RDMA Write for Reliable Reception

34、 146 FC-VI RDMA Read for Reliable Reception and Reliable Delivery .157 Concurrent Receive Streams at a FC-VI Endpoint 168 FC-VI Client-Server Connection Setup 179 Peer-to-Peer Connection Setup .1910 Peer-to-Peer Connection Setup, Concurrent Matching Peer Requests 2111 FC-VI Disconnect Operation 2312

35、 FC-FS Header for Send Operation 25viForeword (This foreword is not part of ANSI INCITS 357-2002.)This standard describes the mapping of the Virtual Interface Architecture onto FibreChannel. Fibre Channel is described in ANSI INCITS 230-1994, Fibre Channel -Physical and Signaling Interface (FC-PH).T

36、his standard was developed by Task Group T11 of Accredited Standards Commit-tee INCITS during 19982001. The standards approval process started in 2001.This standard contains six annexes. Only annex A is normative and is consideredpart of this standard. The rest of the annexes are informative and are

37、 not consideredpart of this standard.Requests for interpretation, suggestions for improvements or addenda, or defect re-ports are welcome. They should be sent to the INCITS Secretariat, Information Tech-nology Industry Council, 1250 Eye Street, NW, Suite 200, Washington, DC 20005-3922.This standard

38、was processed and approved for submittal to ANSI by the InterNation-al Committee for Information Technology Standards (INCITS). Committee approvalof the standard does not necessarily imply that all committee members voted for ap-proval. At the time it approved this standard, INCITS had the following

39、 members:Karen Higginbottom, ChairRuss Richards, Vice-ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeApple Computer, Inc. David MichaelWanda Cox (Alt.)Hewlett-Packard Company .Karen HigginbottomScott Jameson (Alt.)Steve Mills (Alt.)Hitachi America, LtdJohn NeumannHaruk

40、azu Miyamoto (Alt.)IBM CorporationRonald F. SillettiChuck Adams (Alt.)Institute for Certification of Computer Professionals.Kenneth M. ZemrowskiThomas Kurihara (Alt.)Intel Corporation .Gregory KisorMichelle Stamnes (Alt.)Philip Wennblom (Alt.)Microsoft Corporation .Mike KsarJoseph Zajaczkowski (Alt.

41、)Mike Deese (Alt.)National Institute of Standards & Technology Michael HoganWilliam LaPlant, Jr. (Alt.)Oracle Corporation Donald R. DeutschJim Melton (Alt.)Panasonic Technologies, Inc. .Terence NelsonRudolf Vitti (Alt.)Purdue UniversityStephen ElliottSHARE Inc. Dave ThewlisSony Electronics, Inc. .Ed

42、 BarrettJean Baronas (Alt.)Sun Microsystems, IncJohn HillRoger Martin (Alt.)Douglas Johnson (Alt.)Unisys Corporation .Arnold F. WinklerWalt Korzeniowski (Alt.)US Department of Defense/DISA .Russ RichardsJerry Smith (Alt.)viiOrganization Represented Name of RepresentativeXerox Corporation. Kathleen O

43、ReillyKenneth H. Klein (Alt.)Technical Committee T11 on Lower Level Interfaces, which reviewed this standard,had the following members:Robert Snively, ChairEdward Grivna, Vice-ChairNeil Wanamaker, SecretaryOrganization Represented Name of Representative3M. Tad SzostakRonald Bossard (Alt.)Adaptec. Ne

44、il MacLeanBill Lynn (Alt.)Agilent. Matt WakeleyLise Wilson (Alt.)Akara Neil WanamakerAmdahl Joe GrubaGary Gold (Alt.)AMP Charles BrillBob Atkinson (Alt.)Amphenol Michael WingardBill Mable (Alt.)Ancot. Jan V. DedekBart Raudebaugh (Alt.)Andiamo Claudio DeSantiDinesh Dutt (Alt.)Boeing. Michael S. Foste

45、rMike Dorsett (Alt.)Jack E. Keller (Alt.)Brocade Comms. Kumar MalavalliSteven L. Wilson (Alt.)Robert Snively (Alt.)Cisco. David PetersonCMD Adrienne TurenneStephen ONeil (Alt.)CNT Bret KetchumMike Morandi (Alt.)Bill Collette (Alt.)Compaq Bill HamMark Hamel (Alt.)Connecty Solns . Robert W. KembelJuli

46、e Ann Kembel (Alt.)Corning Inc. Leonard YoungDoug Coleman (Alt.)Crossroads Sys. . Robert GriswoldJohn Tyndall (Alt.)Bill Moody (Alt.)Cypress Semi . Edward GrivnaEMC Gary S. RobinsonGreg McSorley (Alt.)Emulex David BaldwinBob Nixon (Alt.)Exabyte. Roger RoseRoy Funderburk (Alt.)FSI Gary R. StephensRal

47、ph Weber (Alt.)Fujikura America. Hari NaiduSuresh Roy (Alt.)Fujitsu . Mike FitzpatrickGadzoox . William R. MartinWayne Rickard (Alt.)General Dynamics Robert K. PedersenMichael Lamatsch (Alt.)viiiOrganization Represented Name of RepresentativeGennum Ken Lazaris-BrunnerBharat Tailor (Alt.)Hirose .Karl

48、 KwiatTatsua Arai (Alt.)HICAM Naoki WatanabeHewlett PackardPredrag SpasicIBM .John ScheibleBob Dugan (Alt.)George Penokie (Alt.)INFINEON.Thomas MurphyRichard Johnson (Alt.)INFINITY I/O .Edward M. FrymoyerAlan Land (Alt.)InrangeHarry V. PaulGregory Koellner (Alt.)Brad Solomon (Alt.)Intel .Rich Tabore

49、kSchelto van Doorn (Alt.)Interphase.Doug McCammishRob Stalnaker (Alt.)JNI Craig StuberChuck Mcknett (Alt.)Lightsand Murali RajagopalAndy Heuand (Alt.)Lockheed Martin .Rick AllisonLSI Logic.Curtis A. RidgewayMike Jenkins (Alt.)John Lohmeyer (Alt.)Lucent .Elizabeth G. RodriguezTerry Cobb (Alt.)Madison CableMichael J. KargJie Fan (Alt.)McData .Michael ODonnellScott Kipp (Alt.)Molex Jay H. NeerTony Whitlow (Alt.)Netapp David FordNishan.Charles MoniaNTT.Etsuji SugitaShinichi Iwano (Alt.)Osamu Ishida (Alt.)Panasonic .Johann SafarPirusCharles BinfordGlenn Virball (Alt.)QLogic Cra