ANSI INCITS TR-39-2005 Information Technology Fibre Channel Methodologies for Interconnects - 2 (FC-MI-2)《信息技术.光纤信道.互连用方法论-2(FC-MI-2)》.pdf

1、American National StandardDeveloped byINCITS Technical Reportfor Information Technology Fibre Channel Methodologies for Interconnects - 2(FC-MI-2)INCITS TR-39-2005INCITS TR-39-2005Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or

2、networking permitted without license from IHS-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-INCITS TR-39-2005INCITS Technical Reportfor Information Technology Fibre Channel

3、 Methodologies for Interconnects - 2(FC-MI-2)SecretariatInformation Technology Industry CouncilAbstractThis technical report specifies common methodologies for both Arbitrated Loop and Switched environ-ments. The goal of this technical report is to facilitate interoperability between devices whether

4、 they areconnected in a loop or Fabric topology.Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Published byAmerican National Standards Institute25 West 43rd Street, New York, Ne

5、w York 10036Copyright 2005 by Information Technology Industry Council (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 the publisher.Printed in the United States of AmericaINCITS Tec

6、hnical Report SeriesThis Technical Report is one in a series produced by the International Committeefor Information Technology Standards (INCITS). The secretariat for INCITS is heldby the Information Technology Industry Council (ITI), 1250 Eye Street, NW, Suite200, Washington, DC 2005.As a by-produc

7、t of the standards development process and the resources ofknowledge devoted to it, INCITS from time to time produces Technical Reports.Such Technical Reports are not standards, nor are they intended to be used assuch.INCITS Technical Reports are produced in some cases to disseminate thetechnical an

8、d logical concepts reflected in standards already published or underdevelopment. In other cases, they derive from studies in areas where it is foundpremature to develop a standard due to a still changing technology, orinappropriate to develop a rigorous standard due to the existence of a number ofvi

9、able options, the choice of which depends on the users particular requirements.These Technical Reports, thus, provide guidelines, the use of which can result ingreater consistency and coherence of information processing systems.When the draft Technical Report is completed, the Technical Committee ap

10、provalprocess is the same as for a draft standard. Processing by INCITS is also similarto that for a draft standard.PatentStatementCAUTION: The developers of this Technical Report have requested that holdersof patents that may be required for the implementation of the standard, disclosesuch patents

11、to the publisher. However, neither the developers nor the publisherhave undertaken a patent search in order to identify which, if any, patents mayapply to this Technical Report. As of the date of publication of this Technical Report and following calls for theidentification of patents that may be re

12、quired for the implementation of theTechnical Report, no such claims have been made. No further patent search isconducted by the developer or the publisher in respect to any Technical Report itprocesses. No representation is made or implied that licenses are not required toavoid infringement in the

13、use of this Technical Report.Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSINot for Resale

14、No reproduction or networking permitted without license from IHS-,-,-ContentsPageForeword vIntroduction x1 Scope . 12 Normative References . 22.1 Overview . 22.2 Approved References . 22.3 References under Development . 33 Definitions and Conventions 43.1 Overview . 43.2 Definitions 43.3 Editorial C

15、onventions 73.4 Abbreviations, Acronyms and Symbols. 73.5 Symbols 93.6 Keywords . 93.7 Applicability and Use of this Technical Report 103.8 Feature Set Table Terms, Definitions, and Abbreviations. 103.8.1 Overview . 103.8.2 Feature Set Table Terms and Definitions . 113.8.3 Feature Set Table Abbrevia

16、tions. 113.9 Feature Testing Compliance . 123.10 Timing Constraints 124 Structure and Concepts . 134.1 Interoperability Environment . 135 Loop Behaviors 145.1 Loop Initialization 145.1.1 Power-On Behavior. 145.1.2 Loop Failure 145.1.3 Initialization at Power-On 145.1.4 FL_Port Time-Out during Initia

17、lization. 145.1.5 LIP Generation 155.1.6 Response to LIP 155.1.7 Origination of LISM Frames 155.1.8 Forwarding of LISM frames. 155.1.9 Address Selection . 155.1.10 Multiport Initialization. 165.1.11 AL_PA Position Map Support 165.1.12 Availability after LIP. 16iCopyright American National Standards

18、Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Page5.2 Post Initialization 165.2.1 LIP Generation 165.2.2 FL_Port Unfair Behavior and Transfer Behavior. 175.2.3 Responses to OPN . 175.2.4 No response to OPN. 176 Fx_

19、Port Behaviors 186.1 Fx_Port Login Responses. 186.1.1 FLOGI ACC Features and Parameters for Fx_Ports 186.1.2 Nx_Port PLOGI . 196.1.3 Fx_Port Common Service Parameters (FLOGI ACC). 196.1.4 Fx_Port Class 2 Service Parameters (FLOGI ACC) . 216.1.5 Fx_Port Class 3 Service Parameters (FLOGI ACC) . 226.2

20、Link Services. 246.2.1 Basic Link Services. 246.2.2 ELS Requirements for Well-Known Addresses. 246.2.3 Extended Link Service Replies . 246.3 FC-AL-2 Features for FL_Ports. 256.4 Loop Fabric Address. 277 Fabric Behaviors 287.1 Overview . 287.2 Switch-to-Switch Requirements 297.2.1 Overview . 297.2.2

21、Switch Port Types . 327.2.3 Exchange Link Parameters (ELP). 337.2.4 Principal Switch Selection. 357.2.5 Fabric Shortest Path First (FSPF). 357.2.6 Distributed Services 367.2.7 Zoning . 427.2.8 Distributed Event Notification 437.2.9 Additional Switch Requirements . 437.3 Fabric Service Requirements 4

22、47.3.1 Overview . 447.3.2 Name Server. 457.3.3 Fabric Configuration Server 497.3.4 Fabric Zone Server . 507.3.5 Registered State Change Notification. 537.4 Domain Controller and Well-Known Addresses 557.4.1 Domain controller and Well-Known Address Support Requirements for Fabrics . 557.4.2 N_Port Do

23、main Controller and Well-Known Address Usage 567.4.3 Domain Controller and Well-Known Address (WKA) ELS Login and Address Assignment Requirements 578 Discovery and Management 628.1 Overview . 62iiCopyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo

24、reproduction or networking permitted without license from IHS-,-,-Page8.2 Management of Interconnect Components . 628.2.1 Overview . 628.2.2 Switch 628.2.3 Managed Hub 638.2.4 Gateway/Bridge. 639 Conformance Environments 64Tables1 ISO and American Conventions . 72 Feature Set table terms and definit

25、ions 113 Feature Set table key abbreviations . 114 Feature testing compliance relationship to definitions 125 FLOGI ACC features and parameters for Fx_Ports 186 Fx_Port Common Service Parameters (FLOGI ACC) 197 Class 2 Service Parameters (FLOGI ACC) 218 Class 3 Service Parameters (FLOGI ACC) 229 Ext

26、ended Link Service Replies . 2410 FC-AL features for FL_Ports. 2511 FC-SW-3 Fabric Support Summary 2912 Switch Port Type Usage . 3213 ELP SW_ILS Parameters . 3314 Flow Control Parameters 3515 FC-SW-3 Defined Name Server Requests . 3616 FC-GS-4 Defined Name Server Requests 3617 FC-GS-4 Common Request

27、s 3818 Name Server Object Usage Summary . 3919 FC-SW-3 Defined Management Server Requests 4020 FC-GS-4 Defined Management Server Requests 4021 Zoning Support . 4222 FC-GS-4 Fabric Support. 4423 Name Server Request Support. 4524 Common Request Support . 4725 Fabric Configuration Server Request Suppor

28、t 4926 Fabric Zone Server Basic Zoning Request Support . 5027 Fabric Zone Server Enhanced Zoning Request Support 5128 Domain Controller and Well-Known Address Support Requirements for Fabrics . 55iiiCopyright American National Standards Institute Provided by IHS under license with ANSINot for Resale

29、No reproduction or networking permitted without license from IHSPage29 ELS requirements for domain controller and well-known addresses 5630 Broadcast WKA (FFFFFFh) ELS login requirements . 5831 Fabric F_Port WKA (FFFFFEh) ELS address assignment requirements. 5832 Fabric Controller WKA (FFFFFDh) ELS

30、login requirements 5933 Directory Service WKA (FFFFFCh) ELS login requirements 5934 Management Service WKA (FFFFFAh) ELS login requirements . 6035 Domain Controller (FFFCxxh) ELS login requirements 6136 Loop Fabric Address ELS login requirements 6137 Switch Support Summary. 6238 Conformance Environm

31、ents. 64iv-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Foreword (This foreword is not part of American National Standard INCITS TR-39-2005.)The Fibre Channel Methodologie

32、s for Interconnects -2 (FC-MI-2) Technical Reportdescribes common methodologies for facilitating interoperability in both loop andFabric environments.This technical report was developed by Task Group T11 of Accredited StandardsCommittee T11 during 2002-2005. The approval process started in 2005.Requ

33、ests 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 technical report was processed and approved for su

34、bmittal to ANSI by the Inter-National Committee for Information Technology Standards (INCITS). Committee ap-proval of the technical report does not necessarily imply that all committee membersvoted for its approval. At the time it approved this technical report, INCITS had thefollowing members:Karen

35、 Higginbottom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAIM Global Dan Mullen Charles Biss (Alt.)American National Standards Institute . Lisa Rajchel Apple Computer, Inc. David Michael Electronic Industries Alliance Edward Mikoski, Jr. Henry Cuschieri (Alt.)EMC C

36、orporation Gary Robinson Farance, Inc. Frank Farance Hewlett-Packard Company. Karen Higginbottom Steve Mills (Alt.)Scott Jameson (Alt.)IBM Corporation Ronald F. Silletti Institute for Certification of Computer Professionals. Kenneth M. Zemrowski Thomas Kurihara (Alt.)IEEE . Judith Gorman Richard Hol

37、leman (Alt.)Robert Pritchard (Alt.)Intel Norbert Mikula Dave Thewlis (Alt.)Philip Wennblom (Alt.)Lexmark International . Don Wright Dwight Lewis (Alt.)Paul Menard (Alt.)Microsoft Corporation . Isabelle Valet-Harper Don Stanwyck (Alt.)Mike Ksar (Alt.)National Institute of Standards equiv-alent to the

38、 phrase “it is strongly recommended”.-,-,-INCITS TR-39-20053.7 Applicability and Use of this Technical ReportCopyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS10This technical report sp

39、ecifies which features shall be used (i.e., required) and which features shallnot be used (i.e., prohibited) by interoperating compliant Fibre Channel implementations. Use ofsome features is optional (i.e., allowed). The use of such functions is either negotiated in a fixed andstandard manner or the

40、 availability of the functions for use shall be determined in a standard manner.The relationship between use as specified in this technical report and support as implemented by aproduct is subtle. If this technical report specifies that a feature shall be used, then a compliant imple-mentation shall

41、 support it. In some cases, this technical report is asymmetric: to ensure interoperabil-ity when an optional feature is used, this technical report requires support for the infrastructurerequired to use the feature without specifying that the feature be used to conform to this technical re-port.The

42、 requirements of this technical report are a proper subset of the various relevant standards. Thistechnical report prohibits use of many features and options in these standards. Use of prohibited fea-tures may prevent interoperability with Fibre Channel devices complying to this technical report. Th

43、istechnical report does not prohibit implementation of features, only their use. Functions that are man-datory in the appropriate base standard are assumed to be implemented. Implementations may sup-port features whose use is prohibited by this technical report and such prohibited features may bereq

44、uired for compliance with the relevant standards or other technical reports.3.8 Feature Set Table Terms, Definitions, and Abbreviations3.8.1 OverviewFeatures in this technical report are summarized in the form of Feature Set tables. These tables indi-cate whether the feature is Required, Prohibited,

45、 Invocable, or Allowed for compliance with this tech-nical report; or whether a parameter is Required to be a particular value for compliance with thistechnical report. Features or parameters that are not listed do not affect interoperability.In several tables within this technical report, there are

46、 references to notes associated with the table.These notes are normative and are mandatory requirements of this technical report.-,-,-INCITS TR-39-20053.8.2 Feature Set Table Terms and DefinitionsCopyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo

47、reproduction or networking permitted without license from IHS-,-,-11Terms and definitions that are used to define usage of reference features or options provided by theapplicable standards are described in table 2.3.8.3 Feature Set Table AbbreviationsTable 3 contains the key of table abbreviations u

48、sed within this technical report.Table 2 Feature Set table terms and definitionsTerm DefinitionProhibitedA feature that shall not be used between Fibre Channel devices compliant with this technical report. An implementation may use the feature to communicate with non-compliant implementations. This technical report does not prohibit the implementation of features, only their use between Fibre Channel devices compliant with this technical report. Use of a prohibited feature may prevent interoperabilit