ANSI INCITS 462 AMD 1-2012 Information Technology C Fibre Channel C Backbone - 5 (FC-BB-5) C Amendment 1.pdf

1、American National StandardDeveloped byfor Information Technology Fibre Channel Backbone - 5 (FC-BB-5) Amendment 1INCITS 462-2010/AM1-2012INCITS 462-2010/AM1-2012INCITS 462-2010/AM1-2012Amendment toINCITS 462-2010American National Standardfor Information Technology Fibre Channel Backbone - 5 (FC-BB-5

2、) Amendment 1SecretariatInformation Technology Industry CouncilApproved July 25, 2012American National Standards Institute, Inc.Approval of an American National Standard requires review by ANSI that therequirements for due process, consensus, and other criteria for approval havebeen met by the stand

3、ards 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 means much more thana simple majority, but not necessarily unanimity. Consensus requires tha

4、t 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 anyone, whether he has approvedthe standards or not, from manufacturing, marketing, pur

5、chasing, 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 American NationalStandard. Moreover, no person shall have the right or authority to issue

6、 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 titlepage of this standard.CAUTION NOTICE: This American National Standard may be revise

7、d 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 Standards mayreceive current information on all standards by calling or writing the AmericanN

8、ational Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2012 by Information Technology Industry Council (ITI)All rights reserved.No part of this publication may be reproduced in anyform, in an elect

9、ronic 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 standard have requested that holders of patents that may berequired for the implementation of the sta

10、ndard 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 publication of this standardand following calls for the identification of patents th

11、at 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 made or impliedthat licenses are not required to avoid infringement in the use o

12、f this standard.iForeword (This foreword is not part of American National Standard INCITS 462-2010/AM1-2012.)This amendment is issued in response to questions that have been raised regardingcertain specifications contained in the content of: INCITS 462-2010, Information technology - Fibre Channel Ba

13、ckbone - 5 (FC-BB-5)This amendment was prepared by Technical Committee INCITS/T11 that is responsi-ble for the maintenance of that standard, and was approved by INCITS in order toprovide corrections as quickly as possible in response to questions raised. This amendment is to be considered as part of

14、 the standard and must be used inconjunction with that standard. The amendment may alter the meaning of the stan-dard. Any subsequent revision, erratum, or amendment to the standard may or maynot reflect the contents of this amendment.Replace the existing clauses and subclauses with the following cl

15、auses and sub-clauses:Subclause 2.2Subclause 2.3Subclause 2.5Subclause 2.6Subclause 3.1.13Subclause 3.1.15Subclause 4.3.2Subclause 4.3.3Subclause 4.4.2.2Subclause 4.4.6Clause 6 Requests for interpretation, suggestions for improvement or addenda, or defect re-ports are welcome. They should be sent to

16、 InterNational Committee for InformationTechnology Standards (INCITS), ITI, 1101 K Street, NW, Suite 610, Washington, DC20005.This standard was processed and approved for submittal to ANSI by INCITS. Com-mittee approval of this standard does not necessarily imply that all committee mem-bers voted fo

17、r its approval. At the time it approved this standard, INCITS had thefollowing members:Don Wright, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe Systems Inc. Scott Foshee Steve Zilles (Alt.)AIM Global, Inc. Steve HallidayApple Helene WorkmanDavid Singer (Alt.)Di

18、stributed Management Task Force John Crandall Jeff Hilland (Alt.)iiOrganization Represented Name of RepresentativeEMC Corporation . Gary Robinson Stephen Diamond (Alt.)Farance, Inc Frank Farance Timothy Schoechle (Alt.)Futurewei Technologies, Inc. Yi ZhaoTimothy Jeffreies (Alt.)Wilbert Adams (Alt.)G

19、S1 US . Frank SharkeyCharles Biss (Alt.)Hewlett-Packard Company Karen Higginbottom Paul Jeran (Alt.)IBM Corporation Alexander TarpinianRobert Weir (Alt.)Arnaud Le Hors (Alt.)Debra Boland (Alt.)Steve Holbrook (Alt.)Gerald Lane (Alt.)IEEE . Jodie HaaszTerry deCourcelle (Alt.)Bob Labelle (Alt.)Intel Ph

20、ilip 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 Calhoon (Alt.)National Institute of Standards b) outside intervention requesting an initializatio

21、n event; orc) a vendor-specific initialization event.State S1: WAN Down. In this state, Transparent FC-BB devices shall:a) initiate establishment of WAN links, either Transport Trail with a fully operational GFP server inboth directions (see 6.4.8.1) or PW;b) send the Not Operational (NOS) Primitive

22、 Sequence to attached FC_Ports, if any;c) discard any Primitive Signals, Primitive Sequences, or frames received from attachedFC_Ports; andd) discard any prior history of Login Exchange Monitor (LEM) information (see 6.4.3).Transition S1:S1 Any other event. This transition occurs when an event other

23、 than what isspecified in state S1 occurs.Transition S1:S3 WAN link up. This transition occurs when a WAN link up event is detected.State S3: WAN Link Up. In this state, the Transparent FC-BB device shall transmit one or morePING signals to the remote Transparent FC-BB device.Transition S3:S2 PING_A

24、CK/Sufficient buffer resources. This transition occurs upon reception ofat least one PING_ACK signal from the remote Transparent FC-BB device and sufficient bufferresources are available to prevent data loss (see 6.4.7). This transition is not coordinated betweenthe Transparent FC-BB devices at each

25、 end of the WAN link.Transition S3:S1 PING_ACK/Insufficient buffer resources. This transition occurs upon receptionof at least one PING_ACK signal from the remote Transparent FC-BB device and WAN latencymeasurements indicate insufficient buffer resources are available within the device to prevent da

26、taloss (see 6.4.7).State S2: WAN Up. In this state, the WAN link is normally (i.e., excluding WAN protection events)operational and the attached FC_Ports at either end of the link are permitted to communicate witheach other. Validated (see 6.4.8.1) Primitive Sequences received from the attached FC_P

27、orts shall betransmitted between attached FC_Ports by the Transparent FC-BB devices according to the rateadaptation and other rules described in 6.4.8.1.If a Primitive Sequence is received from an attached FC_Port while a Transparent FC-BB device hasceased transmitting information across the WAN lin

28、k because it has received one or more PAUSEs,the Transparent FC-BB device shall:a) flush its WAN-facing buffer;b) clear the WAN pause condition; andc) transmit the Primitive Sequence to the remote Transparent FC-BB device.If a Primitive Sequence is received from a remote Transparent FC-BB device whi

29、le a TransparentFC-BB device is unable to transmit frames to an attached FC_Port because it has no availableBB_Credit, the Transparent FC-BB device shall:INCITS 462-2010/AM1-201211a) flush its attached FC_Port-facing buffer; andb) transmit the Primitive Sequence to the attached FC_Port.When FC-BB_GF

30、PT devices have no data to transmit to the WAN, the FC-BB_GFPT device shallfollow the rules specified in ITU-T Rec. G.7041/Y.1303.Transition S2:S1 WAN down or insufficient buffer resources. This transition occurs when:a) a WAN down event is detected. A WAN down event occurs when GFPT_WAN recovery do

31、esnot occur within WAN_HOLDOFF_TOV (see 6.4.9) of the time the GFPT_WAN failure is de-tected; orb) WAN latency measurements (i.e., using PING and PING_ACK signals) indicate insufficient buf-fer resources are available within the device to prevent data loss (see 6.4.7).This transition is not coordina

32、ted between the Transparent FC-BB devices at each end of the WANlink.Transition S2:S2 WAN failure detected. This transition occurs when WAN failure is detected. WANfailure is detected according to criteria that are WAN specific and outside the scope of this standard(e.g., LOS, LOP, AIS, in the case

33、of SONET/SDH, see ITU-T Rec. G.806 and ITU-T Rec. G.783, orRFI, LDP signaling failure in the case of PW, see RFC 4447) (see 6.4.8.1).The Transparent FC-BB device shall start the WAN_HOLDOFF_TOV timer (see 6.4.9) upondetection of a WAN failure.WAN link interruptions or protection events may be concea

34、led from the attached FC equipment in amanner beyond the scope of this standard. During such interruptions, the Transparent FC-BB devicemay operate as though the WAN link were operational and transmit to attached FC_Ports:a) the Primitive Sequence that they were transmitting at the time the WAN fail

35、ure was detected; b) Idles if they were not transmitting a Primitive Sequence at the time the WAN failure was detect-ed; orc) for an FC-BB_GFPT device, 8B/10B-encoded interpretations of 10B_ERR characters (seeITU-T Rec. G.7041/Y.1303). Transition S2:S2 WAN-Error. For an FC-BB_GFPT device, this trans

36、ition occurs when a 10B_ERRcharacter is received from the WAN (see 6.4.8.1). For an FC-BB_PW device, this transition occurswhen an errored frame (see FC-FS-3) or error indication control frame is received from the WAN (see6.4.8.2).Transition S2:S2 WAN-Buffer overrun. This transition occurs when a bu

37、ffer overrun is detected.This transition is not expected to occur, but if it does, the number of dropped FC frames shall becounted.Transition S2:S2 WAN-PSeq=LR,LRR. This transition occurs when a LR or LRR PrimitiveSequence is received from the WAN. BB_Credit_CNT shall be set to zero, and BB_Credit s

38、hall beset to the value that was established by the last LEM (see 6.4.3).Transition S2:S2 WAN-PSeq=NOS,OLS. This transition occurs when a NOS or OLS PrimitiveSequence is received from the WAN. Any existing history of LEM information shall be discarded,BB_Credit_CNT shall be set to zero, and BB_Credi

39、t shall be set to one.INCITS 462-2010/AM1-201212Transition S2:S2 WAN-PSeq/PSig=Arb-Loop or FC-PSeq/PSig=Arb-Loop or WAN-PSig=(R_RDY,BB_SCr,BB_SCs). This transition occurs when an Arbitrated Loop PrimitiveSequence or Primitive Signal is received from the WAN or the attached FC_Port, or when an R_RDY,

40、BB_SCr, or BB_SCs Primitive Signal is received from the WAN. These Primitive Sequences andPrimitive Signals are not expected and shall be discarded.Transition S2:S2 WAN-PSig=Idle or FC-PSig=Idle. This transition occurs when an Idle PrimitiveSignal is received from the WAN or from the attached FC_Por

41、t.Idle Primitive Signals shall be handled in the same manner as Primitive Sequences when they arereceived by a Transparent FC-BB device in a direction of propagation that has most recently seenreception of a Primitive Sequence, as opposed to a frame or FC Primitive Signal. At all other times(i.e., w

42、hen they appear in a direction of propagation that has most recently seen reception of a frameor FC Primitive Signal, as opposed to a Primitive Sequence), Idle Primitive Signals shall bea) discarded by FC-BB_PW devices; orb) discarded or transported end-to-end by FC-BB_GFPT devices without impeding

43、the forwardingof FC frames and other Primitive Signals, which have higher priority.In all circumstances, Idle Primitive Signals shall be generated as required for forwarding to attachedFC_Ports, consistent with the rules defined in FC-FS-3.Transition S2:S2 WAN-PSig!=(R_RDY,BB_SCr,BB_SCs,Idle) or WAN

44、-EOF or WAN-SOF,Dataor FC-PSig!=(R_RDY,BB_SCr,BB_SCs,Idle) or FC-EOF or FC-SOF,Data. This transition occurswhen a Primitive Signal other than R_RDY, BB_SCr, BB_SCs, or Idle, an EOF, or SOF withsubsequent data is received from the WAN or a Primitive Signal other than R_RDY, BB_SCr,BB_SCs, or Idle, an

45、 EOF, or SOF with subsequent data is received from the attached FC_Port.These Primitive Signals, Ordered Sets, and data shall be transported end-to-end without modificationin the order in which they were received, except when flow control conditions require the flushing ofbuffers. The Ordered Sets s

46、hall be transported using the rate adaptation rules described in 6.4.8.1.If a valid ELP, FLOGI, or PLOGI request frame (see FC-SW-5 and FC-LS-2) is received from theWAN or the attached FC_Port, the Transparent FC-BB device shall follow the Login ExchangeMonitor (LEM) rules specified in 6.4.3.Valid E

47、LP, FLOGI, PLOGI, SW_ACC, and LS_ACC frames, may be modified by Transparent FC-BBdevices according to the rules specified in 6.4.4, but only when such frames open or close a LEM asspecified in 6.4.3.Transition S2:S2 WAN-PAUSE. This transition occurs when a PAUSE signal is received from theWAN. Trans

48、mission of frames and Primitive Signals over the WAN shall be paused. See 6.4.7.Transition S2:S2 WAN-RESUME. This transition occurs when a RESUME signal is received fromthe WAN. Transmission of frames and Primitive Signals over the WAN shall resume. See 6.4.7.Transition S2:S2 WAN-PING. This transiti

49、on occurs when a PING signal is received from the WAN.The Transparent FC-BB device shall transmit a PING_ACK to the remote Transparent FC-BB device.See 6.4.7.Transition S2:S2 WAN-PING_ACK. This transition occurs when a PING_ACK signal is receivedfrom the WAN. See 6.4.7.INCITS 462-2010/AM1-201213Transition S2:S2 FC-LossSig or FC-LossSync. This transition occurs when Loss of Signal or Lossof Synchronization (see FC-FS-3) is detected on the link to the attached FC_Port for a period of timegreater than R_T_TOV. The Transparent FC-BB device shall transmit the NOS Primitive Sequencefor