1、American National StandardDeveloped byfor Information Technology Fibre Channel Inter-Fabric Routing (FC-IFR)INCITS 475-2011INCITS 475-2011INCITS 475-2011American National Standardfor Information Technology Fibre Channel Inter-Fabric Routing (FC-IFR)SecretariatInformation Technology Industry CouncilA
2、pproved November 14, 2011American National Standards Institute, Inc.AbstractThis standard defines the protocols, functions, and mappings for the routing of Fibre Channel frames be-tween physically or logically separated Fabrics.Approval of an American National Standard requires review by ANSI that t
3、herequirements 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 ag
4、reement 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 resp
5、ect preclude 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 interpretat
6、ion of 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 app
7、ears on 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 Na
8、tional 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 2011 by Information Technology Industry Co
9、uncil (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, 1101 K Street NW, Suite 610 Washington, DC 20005. Printed in the United States of AmericaCAUTION: The developers of this st
10、andard have requested 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.
11、 As of the date 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
12、 claim or of any 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 fro
13、m the publisher. 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 .vIntroduction
14、.x1 Scope. 12 Normative references. 22.1 Overview 22.2 Approved references 22.3 References under development. 22.4 Other references 23 Definitions and conventions. 33.1 Common definitions . 33.2 Editorial Conventions. 43.3 List of commonly used acronyms and abbreviations . 53.3.1 General 53.4 Keywor
15、ds . 54 Structure and concepts 74.1 Inter-Fabric Router overview 74.2 Inter-Fabric Router simple mode operation . 74.3 Inter-Fabric Router NAT mode operation. 94.4 Inter-Fabric Router logical components. 104.4.1 Overview 104.4.2 Front Domain Switches 114.4.3 Translate Domain Switches . 114.4.4 Routi
16、ng Function 115 Inter-Fabric Router operational requirements 125.1 Overview 125.2 Inter-Fabric Router architectural model . 125.3 Operation of Inter-Fabric Router internal Switches 125.4 Interconnection of Inter-Fabric Router components. 135.5 IFR Management Function 135.6 Inter-Fabric Router discov
17、ery. 135.6.1 IFR discovery protocol overview 135.6.2 Name Server registration. 135.6.3 Name Server requirements 145.6.4 IFR neighbor discovery 145.6.5 IFR adjacency establishment. 145.6.6 IFR discovery state machine 155.6.6.1 Overview 155.6.6.2 IFR discovery state machine states and transitions. 16i
18、iPage5.6.7 Inter-Fabric Router switch support discovery 175.7 Class 2/F support. 175.7.1 Overview 175.7.2 F_RJT and F_BSY processing for Class 2/F. 185.8 Enc_Header and IFR_Header processing. 195.8.1 Overview 195.8.2 Enc_Header field processing. 195.8.3 IFR_Header field processing . 195.8.3.1 DF_ID
19、field. 195.8.3.2 SF_ID field . 195.8.3.3 Exp_Time field . 195.8.3.4 Hop_Cnt field . 195.9 Operation of the Routing Function. 205.9.1 Overview 205.9.2 Ingress Routing Function role 205.9.3 Egress Routing Function role 215.9.4 Combined ingress and egress Routing Function role 215.10 Link Service proce
20、ssing. 225.10.1 Overview 225.10.2 ELS with embedded N_Port_ID processing requirements 225.10.3 FC-4 Link Service with embedded N_Port_ID processing requirements 235.10.4 ELS Receive Data_Field Size processing . 245.10.5 Link Service Exchange Context storage requirements 246 Fabric addressing 256.1 F
21、abric_Identifiers . 256.2 Worldwide_Name and Domain_ID usage 256.3 Routing Function N_Port_IDs 257 Inter-Fabric Router Internal Link Services (IFR_ILS). 267.1 IFR_ILS Overview 267.2 Inter-Fabric IFR_ILS (IF_ILS) requests . 267.2.1 Inter-Fabric IFR_ILS request overview 267.2.2 IF_ILS_REQ Header forma
22、t 277.2.3 IF_ILS Hello (IF_ILS_HLO) subcommand . 277.2.4 IF_ILS Topology Database Send (IF_ILS_TDS) subcommand. 287.2.4.1 IF_ILS_TDS overview 287.2.4.2 IFR Nx_Port Descriptor 297.2.5 IF_ILS Topology Database ACK (IF_ILS_TD_ACK) subcommand. 297.2.6 IF_ILS Zone Database Send (IF_ILS_ZDS) subcommand .
23、307.2.6.1 IF_ILS_ZDS overview 307.2.6.2 IF_Zone Descriptor 307.2.6.3 IF Device Descriptor 317.2.7 IF_ILS Zone Database ACK (IF_ILS_ZD_ACK) subcommand . 327.2.7.1 IF_ILS_ZD_ACK overview. 327.2.7.2 IF_Zone ACK Descriptor 33iiiPage7.3 Front Domain IFR_ILS (FD_ILS) requests. 337.3.1 Front Domain ILS req
24、uest overview. 337.3.2 FD_ILS_REQ Header format . 347.3.3 Front Domain Hello (FD_ILS_HLO) subcommand. 357.3.3.1 FD_ILS_HLO subcommand overview 357.3.3.2 Fabric Descriptor format. 367.3.3.3 Translate Port Descriptors . 377.3.4 Front Domain Zone Database Send (FD_ILS_ZDS) subcommand . 377.3.5 Front Do
25、main Zone Database ACK (FD_ILS_ZD_ACK) subcommand 377.3.5.1 FD_ILS_ZD_ACK subcommand overview . 377.3.5.2 IF_Zone ACK Descriptor 387.3.5.3 Device Descriptor. 397.3.6 Front Domain Staging Context (FD_ILS_SC) subcommand 397.3.7 Front Domain Staging Context ACK (FD_ILS_ASC_ACK) subcommand 407.3.8 Front
26、 Domain Staging Context Delete (FD_ILS_SCD) subcommand 408 Inter-Fabric Router Zone Protocol (IFR_ZP) 428.1 Overview 428.1.1 IF_Zone synchronization 438.1.1.1 IF_Zone synchronization exceptions 448.1.2 IFR Nx_Ports and Inter-Fabric Router Zones 448.1.2.1 IFR Nx_Port roles. 448.1.2.2 IFR Nx_Port stat
27、es. 458.1.2.3 Pair-match condition 458.1.2.4 Inter-Fabric Router Zone IFR Nx_Port state machine 468.1.2.5 Inter-Fabric Router Zone IFR Nx_Port state machine states and transitions. 469 Redundant Inter-Fabric Router operation 489.1 Overview 489.1.1 Owner selection state machine 489.1.2 Link Service E
28、xchange context storage processing. 4910 Timers and constants. 5010.1 Inter-Fabric Router time-out values 50Tables1 ISO, French, and American conventions . 52 ELS with embedded N_Port_IDs . 223 FC-4 Link Service with embedded N_Port_ID processing requirements 234 Frame_Header field values for IFR_IL
29、S frames. 265 IF_ILS_REQ Header format. 276 IF_ILS_REQ Subcommand values 277 IF_ILS_HLO payload format 288 IF_ILS_TDS payload format. 28ivPage9 IFR Nx_Port Descriptor format 2910 IF_ILS_TD_ACK payload format . 2911 IF_ILS_ZDS payload format 3012 IF_Zone Descriptor format. 3013 IF Device Descriptor f
30、ormat . 3114 Port State field values 3215 IF_ILS_ZD_ACK payload format . 3316 IF_ILS_ZD_ACK Descriptor format . 3317 FD_ILS_REQ Header format. 3418 FD_ILS_REQ Subcommand values 3419 FD_ILS_HLO payload format 3520 Fabric Descriptor format 3621 Fabric Reachable Flag field values 3622 Translate Port De
31、scriptor format 3723 FD_ILS_ZDS payload format. 3724 FD_ILS_ZD_ACK subcommand payload format . 3825 IF_Zone ACK Descriptor format 3826 Device Descriptor format . 3927 FD_ILS_SC payload format. 3928 FD_ILS_SC_ACK payload format . 4029 FD_ILS_SCD payload format 4130 Inter-Fabric Router time-out values
32、 . 50Figures1 Example simple mode Inter-Fabric Router configuration. 82 Example NAT mode Inter-Fabric Router configuration 93 Inter-Fabric Router logical components. 104 Inter-Fabric Router architectural model . 125 IFR discovery state machine . 166 Inter-Fabric Router Class 2/F F_RJT/F_BSY example
33、187 Example IFR_ZP operation . 438 Inter-Fabric Router Zone IFR Nx_Port state machine . 469 Owner selection state machine 48vForeword (This foreword is not part of American National Standard INCITS 475-2011.)The Fibre Channel Inter-Fabric Routing (FC-IFR) standard defines the protocols,functions, an
34、d mappings for the routing of Fibre Channel frames between physicallyor logically separated Fabrics.This standard was developed by Task Group T11.3 of Accredited Standards Commit-tee INCITS during 2004-2010. The standards approval process started in 2009.Requests for interpretation, suggestions for
35、improvements or addenda, or defect re-ports are welcome. They should be sent to the INCITS Secretariat, Information Tech-nology Industry Council, 1101 K Street, NW, Suite 610, Washington, DC 20005.This standard was processed and approved for submittal to ANSI by the InternationalCommittee for Inform
36、ation Technology Standards (INCITS). Committee approval ofthe standard does not necessarily imply that all committee members voted for its ap-proval. At the time it approved this standard, INCITS had the following members:Don Wright, ChairJennifer Garner, SecretaryOrganization Represented Name of Re
37、presentativeAdobe Systems, Inc Scott Foshee Steve Zilles (Alt.)AIM Global, Inc. . Steve HallidayApple Computer, Inc. . Helene WorkmanDavid Singer (Alt.)Distributed Management Task Force John Crandall Jeff Hilland (Alt.)Electronic Industries Alliance . Edward Mikoski, Jr. Henry Cuschieri (Alt.)EMC Co
38、rporation . Gary RobinsonFarance, Inc Frank FaranceTimothy Schoechle (Alt.)GS1 US . Frank SharkeyCharles Biss (Alt.)Hewlett-Packard Company Karen Higginbottom Paul Jeran (Alt.)IBM Corporation Gerald Lane Robert Weir (Alt.)Arnaud Le Hors (Alt.)Debra Boland (Alt.)Steve Holbrook (Alt.)Alexander Tarpini
39、an (Alt.)IEEE . Terry deCourcelleJodie Haasz (Alt.)Bob Labelle (Alt.)Joan Woolery (Alt.)Intel Philip Wennblom Grace Wei (Alt.)Stephen Balogh (Alt.)Lexmark International . Don Wright Dwight Lewis (Alt.)Paul Menard (Alt.)Jerry Thrasher (Alt.)Microsoft Corporation . Jim Hughes Dick Brackney (Alt.)John
40、Calhoun (Alt.)viOrganization Represented Name of RepresentativeNational Institute of Standards equivalent to the phrase “it is strongly recommended”.3.4.11 x or xx: The value of the bit or field is not relevant.INCITS 475-201174 Structure and concepts4.1 Inter-Fabric Router overviewThis standard des
41、cribes the architectural model and specification for a Fibre Channel Inter-FabricRouter. An Inter-Fabric Router is a Fibre Channel device that permits attached Fibre ChannelNx_Ports to be shared among multiple independent Fibre Channel Fabrics.An Inter-Fabric Router, or a series of Inter-Fabric Rout
42、ers, connects Fabrics and provides thefunctionality required to present a Native Nx_Port to each Fabric as a Proxy N_Port. The entireinterconnection of Fabrics and Inter-Fabric Routers is referred to as a Fibre Channel Inter-Fabric.Two modes of operation are specified for Inter-Fabric Routers, simpl
43、e mode and network addresstranslation (NAT) mode. From the perspective of the requirements placed on Inter-Fabric Routers,the NAT mode of operation is a proper subset of the requirements of the simple mode of operation.The frames that pass between Inter-Fabric Routers that are bound for Native Nx_Po
44、rts are referredto as Routable Frames. This term distinguishes these frames from other frames that pass betweenInter-Fabric Routers such as the frames related to Inter-Fabric route discovery.Fabrics operate independently. Consequently, there is no assurance that these Fabrics will selectDomain IDs t
45、hat are unique across all Fabrics within the Inter-Fabric. Therefore, the N_Port_IDs arenot necessarily the same between Proxy N_Ports and their corresponding Native Nx_Ports (i.e.,different N_Port_IDs are likely to be the case). Inter-Fabric Routers perform the necessary translationof N_Port_IDs wi
46、thin the Fibre Channel frames as they pass through the intervening Inter-FabricRouters.No translation of WWNs is performed. Therefore, a Proxy N_Port and its corresponding NativeNx_Port may appear on the Fibre Channel Inter-Fabric with different N_Port_IDs but will always havethe same WWN.Each Fabri
47、c within the Inter-Fabric is identified by a 12-bit Fabric Identifier.4.2 Inter-Fabric Router simple mode operationSimple mode operation allows for the use of a single Inter-Fabric Router (i.e., no hop Inter-Fabricrouting), or two Inter-Fabric Routers (i.e., single hop Inter-Fabric routing) to conne
48、ct Fabrics.An example of the supported simple mode Inter-Fabric Router configurations (i.e., no hop and singlehop) is shown in figure 1.INCITS 475-20118Figure 1 Example simple mode Inter-Fabric Router configurationIn figure 1, the individual Fabrics are represented as Fabrics 1, 2, and 3. Three Nati
49、ve Nx_Ports areshown, A, B, and C, and their Native Fabrics are Fabric 1, Fabric 2, and Fabric 3, respectively. In thisexample, Native Nx_Port A, which is attached to Fabric 1, is communicating with Native Nx_Ports Band C. Inter-Fabric Router-1 presents Proxy N_Port B and Proxy N_Port C to Fabric 1. Any FibreChannel frames originated by Native Nx_Port A and addressed to Proxy N_Port B transit throughFabric 1, Inter-Fabric Router-1, and Fabric 2 to Native Nx_Port B (i.e., no hop communication). AnyFibre Channel frames originated by Native Nx_Port A and addressed to Proxy N_Port C trans
