ANSI INCITS 419-2008 Information Technology C Fibre Channel C Backbone - 4 (FC-BB-4).pdf

《ANSI INCITS 419-2008 Information Technology C Fibre Channel C Backbone - 4 (FC-BB-4).pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS 419-2008 Information Technology C Fibre Channel C Backbone - 4 (FC-BB-4).pdf（91页珍藏版）》请在麦多课文档分享上搜索。

1、American National StandardDeveloped byfor Information Technology Fibre Channel Backbone - 4(FC-BB-4)ANSI INCITS 419-2008ANSI INCITS 419-2008ANSIINCITS 419-2008American National Standardfor Information Technology Fibre Channel Backbone - 4(FC-BB-4)SecretariatInformation Technology Industry CouncilApp

2、roved August 25, 2008American National Standards Institute, Inc.AbstractThis standard defines the functions and mappings necessary to tunnel Fibre Channel links, or bridge FibreChannel networks, across Wide Area Networks.Approval of an American National Standard requires review by ANSI that therequi

3、rements 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

4、 means 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 pre

5、clude 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

6、any American 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

7、 the 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

8、Standards 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 2008 by Information Technology Industry Council (

9、ITI)All 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 req

10、uested that holders of patents that may be re-quired for the implementation of the standard disclose such patents to the publisher. However, nei-ther the developers nor the publisher have undertaken a patent search in order to identify which, ifany, patents may apply to this standard. As of the date

11、 of publication of this standard, followingcalls for the identification of patents that may be required for the implementation of the standard,notice of one or more such claims has been received. By publication of this standard, no positionis taken with respect to the validity of this claim or of an

12、y rights in connection therewith. The knownpatent holder(s) has (have), however, filed a statement of willingness to grant a license underthese rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to ob-tain such a license. Details may be obtained from the publisher

13、. No further patent search is con-ducted by the developer or publisher in respect to any standard it processes. No representation ismade or implied that this is the only license that may be required to avoid infringement in the use ofthis standard.iContentsPageForeword viIntroduction x1 Scope 12 Nor

14、mative References . 52.1 Overview 52.2 Approved references 52.3 References under development . 62.4 ITU-T references 62.5 IETF references . 63 Definitions and conventions . 83.1 Common definitions . 83.2 FC-BB_IP definitions 93.3 FC-BB_GFPT definitions . 113.4 FC-BB_PW definitions . 123.5 Editorial

15、Conventions . 123.6 List of commonly used acronyms and abbreviations . 133.6.1 General 133.6.2 FC-BB_IP . 143.6.3 FC-BB_GFPT . 143.6.4 FC-BB_PW 143.7 Symbols . 143.8 Keywords . 154 FC-BB-4 Structure and Concepts 164.1 FC-BB-4 backbone mappings 164.2 FC-BB-4 reference models 164.3 FC-BB-4 models over

16、view . 194.3.1 FC-BB_IP . 194.3.2 FC-BB_GFPT . 204.3.3 FC-BB_PW 204.4 FC-BB-4 requirements . 214.4.1 Fibre Channel Class support . 214.4.2 Payload transparency 214.4.2.1 FC-BB_IP 214.4.2.2 Transparent FC-BB (FC-BB_GFPT and FC-BB_PW) 214.4.3 Latency delay and timeout value . 224.4.4 QoS and bandwidth

17、 . 224.4.5 In-order delivery . 224.4.6 Flow control 224.5 FC-BB-4 SW_ILS codes 23iiPage5 FC-BB_IP Structure and Concepts 245.1 FC-BB_IP overview . 245.2 VE_Port functional model 255.2.1 FC-BB_IP interface protocol layers . 255.2.2 E_Port/F_Port FC interface . 275.2.3 FC Switching Element (SE) with F

18、C routing 275.2.4 FC-BB_IP protocol interface 275.2.4.1 Major components 275.2.4.2 FC and FCIP Entities 275.2.4.3 VE_Port Virtual ISL exchanges 305.2.4.4 Control and Service Module (CSM) 305.2.4.5 Platform Management Module (PMM) 305.2.5 IP network interface . 335.3 B_Access functional model 335.3.1

19、 FC-BB_IP interface protocol layers . 335.3.2 B_Port FC interface . 335.3.3 FC-BB_IP protocol interface 335.3.3.1 Major components 335.3.3.2 FC and FCIP Entities 345.3.3.3 B_Access Virtual ISL exchanges 365.3.3.4 B_Port Control and Service Module (CSM) 405.3.3.5 B_Port Platform Management Module (PM

20、M) 405.3.4 IP Network Interface 405.4 FC-BB_IP Network Topologies 415.5 Mapping and message encapsulation using TCP/IP . 435.5.1 Encapsulated frame structures 435.5.1.1 FC frame encapsulation structure. 435.5.1.2 Encapsulated FCIP Special Frame (FSF) structure . 445.5.2 TCP/IP encapsulation 455.6 FC

21、-BB_IP Protocol Procedures . 465.6.1 Overview 465.6.2 Procedures for platform management . 465.6.2.1 Function 465.6.2.2 Procedures for discovery 465.6.2.3 Procedures for extending FC-SP security 465.6.3 Procedures for connection management . 485.6.3.1 Function 485.6.3.2 Procedures for link setup 485

22、.6.3.3 Procedures for data transfer . 495.6.3.4 Procedures for FCIP Link disconnection 495.6.3.5 Procedures for multiple connection management 505.6.4 Procedures for error detection recovery 505.6.4.1 Procedures for handling invalid FC frames. 505.6.4.2 Procedures for error recovery. 505.6.5 FC-BB_I

23、P system parameters . 515.6.5.1 FC timers 515.6.5.2 TCP timers 515.6.5.3 Maximum number of attempts to complete an encapsulated FC frame transmission 51iiiPage5.6.5.4 Maximum number of outstanding encapsulated FC frames 515.7 FC-BB_IP service considerations 515.7.1 Latency delay . 515.7.2 Throughput

24、 . 525.7.2.1 How timeouts affect throughput 525.7.2.2 How loss affects throughput 525.7.2.3 Other factors that affect throughput 525.7.3 Reliability 525.7.3.1 Loss of connectivity. 525.7.3.2 Loss of synchronization. 535.7.3.3 Loss or corruption of TCP segments. 535.7.3.4 Loss or corruption of FC fra

25、mes 535.7.3.5 FCIP error reporting 535.7.4 Quality of Service (QoS) 545.7.5 Delivery order . 545.7.6 IP multicast and broadcast . 545.7.7 Security and authentication 546 Transparent FC-BB (FC-BB_GFPT and FC-BB_PW) Structure and Concepts 556.1 Applicability 556.2 FC-BB_GFPT overview 556.3 FC-BB_PW ov

26、erview . 566.4 Transparent FC-BB functional model . 576.4.1 Transparent FC-BB initialization 576.4.2 Transparent FC-BB initialization state machine . 576.4.2.1 Initialization state machine keywords 576.4.2.2 Initialization state machine 576.4.3 Login Exchange Monitors . 626.4.4 Port initialization p

27、arameter observation and modification . 666.4.5 Handling of BB_SCs, BB_SCr, and R_RDY Primitive Signals and BB_Credit initialization 666.4.6 Transparent FC-BB Primitive Signals 686.4.7 Transparent FC-BB flow control . 686.4.7.1 Overview . 686.4.7.2 FC-BB_GFPT Alternate Simple Flow Control (ASFC) 686

28、.4.7.3 PING and PING_ACK signals . 696.4.8 Adaptation of FC information for Transparent FC-BB 716.4.8.1 Adaptation of FC information for GFPT transport in FC-BB_GFPT 716.4.8.2 Adaptation of FC information for PW transport in FC-BB_PW 736.4.9 WAN Holdoff Timeout Value (WAN_HOLDOFF_TOV) 756.4.10 Trans

29、parent FC-BB frame compression encoding . 756.4.10.1 FC-BB_GFPT FC frame compression 756.4.10.2 FC-BB_PW FC frame compression 766.4.10.3 LZS compression algorithm 76Tables1 FC-BB-4 organization. 12 ISO and American Conventions. 13ivPage3 Models and resident FC_Port types 174 FC-BB-4 SW_ILS codes 235

30、 FC-BB-4 ELS codes 236 EBP request payload . 377 EBP accept payload 378 EBP reject reason code explanation 389 TCP/IP Segment structure carrying encapsulated FC frame. 4310 Encapsulated FC frame structure 4311 TCP/IP Segment structure carrying encapsulated FSF. 4412 Encapsulated FSF structure 4413 A

31、SF request payload . 4714 ASF accept response payload. 4815 Transparent FC-BB initialization state machine keywords 5716 Login Exchange Monitor (LEM) state machine 6517 Values of FC-BB_GFPT ASFC_PAUSE and ASFC_RESUME Primitive Signals 6918 FC-BB_GFPT PING and PING_ACK Primitive Signal values . 7019

32、FC-BB_GFPT PING and PING_ACK CCC bit field values 7020 FC-BB_PW PING and PING_ACK control frame payload values . 7121 FC-BB_PW error indication control frame payload values 75Figures1 Scope and components of FC-BB_IP model . 22 Scope and components of FC-BB_GFPT model. 33 Scope and components of FC-

33、BB_PW model. 44 FC-BB_IP reference model 175 FC-BB_GFPT reference model . 186 FC-BB_PW reference model . 197 FC-BB_IP network configuration . 248 FC-BB_IP VE_Port functional model . 269 FC-BB_IP Protocol Layers. 2810 Scope of VE_Port Virtual ISL. 3011 Security layers . 3212 FC-BB_IP B_Access functio

34、nal model 3513 Scope of B_Access Virtual ISL 3614 B_Access initialization state machine 39vPage15 FC-BB_IP network topologies 4216 TCP/IP encapsulation of an encapsulated FC frame . 4517 FC-BB_GFPT protocol levels and layers . 5518 FC-BB_PW protocol levels and layers . 5619 Transparent FC-BB initial

35、ization state machine . 5820 Example port initialization process. 6721 FC-BB_PW PING and PING_ACK control frame format . 7122 FC-BB_PW error indication control frame format. 75AnnexA FC-BB_GFPT Interoperability Guidelines . 77A.1 GFPT-specific interoperability guidelines . 77viForeword (This forewor

36、d is not part of American National Standard ANSI INCITS 419-2008.)This standard defines the functions and mappings necessary to tunnel Fibre Channellinks, or bridge Fibre Channel networks, across Wide Area Networks.This standard was developed by Task Group T11.3 of Accredited Standards Organi-zation

37、 INCITS during 2006 - 2007. The standards approval process started in 2007.This document includes one annex, which is informative and is not considered part ofthe standard.Requests for interpretation, suggestions for improvements or addenda, or defect re-ports are welcome. They should be sent to the

38、 INCITS Secretariat, Information Tech-nology Industry Council, 1250 Eye Street, NW, Suite 200, Washington, DC 20005-3922.This standard was processed and approved for submittal to ANSI by the InterNation-al Committee for Information Technology Standards (INCITS). Committee approvalof the standard doe

39、s not necessarily imply that all committee members voted for itsapproval. At the time it approved this standard, INCITS had the following members:Karen Higginbottom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe Systems, Inc. Steve ZillesScott Foshee (Alt.)AIM G

40、lobal Dan MullenCharles Biss (Alt.)Apple Computer, Inc. Kwok LauHelene Workman (Alt.)David Singer (Alt.)Distributed Managment Task Force . Tony DiCenzoElectronic Industries Alliance . Edward Mikoski, Jr.EMC Corporation Gary RobinsonFarance, Inc. Frank FaranceTimothy Schoechle (Alt.)Google Zaheda Bho

41、ratRobert Tai (Alt.)GS1 US Ray DelnickiFrank Sharkey (Alt.)James Chronowski (Alt.)Mary Wilson (Alt.)Hewlett-Packard Company. Karen HigginbottomSteve Mills (Alt.)Scott Jameson (Alt.)IBM Corporation . Ronald F. SillettiRobert Weir (Alt.)Sandy Block (Alt.)Richard Schwerdtfeger (Alt.)IEEE . Judith Gorma

42、nTerry DeCourcelle (Alt.)Bill Ash (Alt.)Jodi Haasz (Alt.)Bob Labelle (Alt.)Susan Tatiner (Alt.)Intel. Philip WennblomDave Thewlis (Alt.)Grace Wei (Alt.)Lexmark International. Don WrightDwight Lewis (Alt.)Paul Menard (Alt.)viiOrganization Represented Name of RepresentativeMicrosoft CorporationJim Hug

43、hesDave Welsh (Alt.)Isabelle Valet-Harper (Alt.)National Institute of Standards b) approved and draft international and regional standards (ISO and IEC); andc) approved foreign standards (JIS and DIN).For further information, contact the ANSI Customer Service Department:Phone +1 212-642-4900Fax: +1

44、212-302-1286Web: http:/www.ansi.orgE-mail: ansionlineansi.orgor the InterNational Committee for Information Technology Standards (INCITS):Phone 202-626-5738Web: http:/www.incits.orgE-mail: incitsitic.orgAdditional availability contact information is provided below as needed.2.2 Approved referencesAN

45、SI T1.105-2001, Synchronous Optical Network (SONET) - Basic Description Including Multi-plex Structures, Rates, and Formats.ANSI INCITS 419-20086ANSI INCITS 424-2007, Fibre Channel - Framing and Signaling - 2 (FC-FS-2).ANSI INCITS 418-2006, Fibre Channel - Switch Fabric - 4 (FC-SW-4).ANSI INCITS 426

46、-2007, Fibre Channel - Security Protocols (FC-SP).ANSI INCITS 433-2006, Fibre Channel - Link Services (FC-LS).ANSI INCITS 241-1994 (R1999), Data Compression Method Adaptive Coding with Sliding Win-dow for Information Interchange.2.3 References under developmentAt the time of publication, the followi

47、ng referenced standards were still under development. Forinformation on the current status of the documents, or regarding availability, contact the relevantstandards body or other organization as indicated.For electronic copies of references under development by INCITS T11, see www.t11.org.T11/Proje

48、ct 1822-D, Fibre Channel - Switch Fabric - 5 (FC-SW-5).T11/Project 1835-D, Fibre Channel - Security Protocol - 2 (FC-SP-2).For electronic copies of references under development by the Internet Engineering Task Force(IETF), see www.ietf.org.Roth, Solomon, Tsurusawa, “Encapsulation Methods for Transpo

49、rt of Fibre Channel frames overMPLS Networks“, draft-ietf-pwe3-fc-encap-07.txt (RFC reference and date to be added duringstandards action).2.4 ITU-T referencesCopies of the following approved ITU-T standards may be obtained through the ITU-T Publicationsdepartment at http:/www.itu.int.ITU-T Rec. G.707/Y.1322, (2007)