ANSI INCITS TR-47-2012 Information Technology C Fibre Channel C Simplified Configuration and Management Specification (FC-SCM)《光纤通道.简化配置和管理》.pdf

《ANSI INCITS TR-47-2012 Information Technology C Fibre Channel C Simplified Configuration and Management Specification (FC-SCM)《光纤通道.简化配置和管理》.pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS TR-47-2012 Information Technology C Fibre Channel C Simplified Configuration and Management Specification (FC-SCM)《光纤通道.简化配置和管理》.pdf（62页珍藏版）》请在麦多课文档分享上搜索。

1、American National StandardDeveloped byINCITS Technical Reportfor Information Technology Fibre Channel Simplified Configurationand Management Specification(FC-SCM)INCITS TR-47-2012INCITSTR-47-2012Reaffirmed as INCITS/TR-47-2012 (R2017)INCITS TR-47-2012INCITS Technical Reportfor Information Technology

2、 Fibre Channel Simplified Configurationand Management(FC-SCM)SecretariatInformation Technology Industry CouncilThis Technical Report is one in a series produced by the InternationalCommittee for Information Technology Standards (INCITS). The secretariatfor INCITS is held by the Information Technolog

3、y Industry Council (ITI), 1101K Street, NW, Suite 610, Washington, DC 20005.As a by-product of the standards development process and the resources ofknowledge devoted to it, INCITS from time to time produces TechnicalReports. Such Technical Reports are not standards, nor are they intended tobe used

4、as such.INCITS Technical Reports are produced in some cases to disseminate thetechnical and logical concepts reflected in standards already published orunder development. In other cases, they derive from studies in areas whereit is found premature to develop a standard due to a still-changing techno

5、logyor inappropriate to develop a rigorous standard due to the existence of anumber of viable options, the choice of which depends on the users particularrequirements. These Technical Reports, thus, provide guidelines, the use ofwhich can result in greater consistency and coherence of informationpro

6、cessing systems.When the draft Technical Report is completed, the Technical Committeeapproval process is the same as for a draft standard. Processing by INCITSis also similar to that of a draft standard.INCITSTechnical ReportSeriesPublished byAmerican National Standards Institute, Inc.25 West 43rd S

7、treet, 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 electronic retrieval system or otherwise,without prior written permission of ITI, 1101 K Street NW, Suite 610, Washington, DC 20

8、005. Printed in the United States of AmericaCAUTION: The developers of this Technical Report have requested that holders of patents thatmay be required for the implementation of the standard disclose such patents to the publisher.However, neither the developers nor the publisher have undertaken a pa

9、tent search in order toidentify which, if any, patents may apply to this standard. As of the date of publication of this Tech-nical Report, following calls for the identification of patents that may be required for the implemen-tation of the standard, notice of one or more such claims has been recei

10、ved. By publication of thisTechnical Report, no position is taken with respect to the validity of this claim or of any rights inconnection therewith. The known patent holder(s) has (have), however, filed a statement of willing-ness to grant a license under these rights on reasonable and nondiscrimin

11、atory terms and condi-tions to applicants desiring to obtain such a license. Details may be obtained from the publisher.No further patent search is conducted by the developer or publisher in respect to any standard itprocesses. No representation is made or implied that this is the only license that

12、may be requiredto avoid infringement in the use of this Technical Report.iContents PageForeword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vIntroduction . . . . . . . . . . . . . . . . . . . . . . . . .

13、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii1Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Normative References . . . . . . . . . . . . . . . . . . . . . . . . .

14、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.1 Normative references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2 Approved references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15、. . . . . . . . . 22.3 References under development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Definitions, symbols, abbreviations, and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.1 Definitions . . . . . . . . . . . . . . . . .

16、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.2 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.3 State Machine notation . . . . . . . . . . . . . . . . . . . . . . . . .

17、 . . . . . . . . . . . . . . . . . . . . . . . . . 53.4 Editorial conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53.5 Feature Set table terms, definitions, and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . 74 St

18、ructure and Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Management Tool Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.1 Overview . . . . . . . . . . . . . . . . . . . .

19、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.2 Generic Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.2.1 Management Tool Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

20、 . . . . . . . . . . . . 105.2.2 Management Tool Requirements on Other Elements . . . . . . . . . . . . . . . . . . . . . 105.3 HBA Requirements to support the Management Tool . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Requirements for hosts . . . . . . . . . . . . . . . . . . . . . . .

21、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136.2 Generic Services Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22、. . . . . . . . . 136.3 Requirements for initiator FCP_Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146.3.2 Initiator FCP_Port operation

23、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Requirements for Fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24、 . . . . . . . . . . . . . . . . . . . . . . 237.2 Generic Service requirements for a Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237.2.1 Mandatory Name Server Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237.2.2 Mandatory Fabric Confi

25、guration Server attributes and requests . . . . . . . . . . . . . 247.2.3 Mandatory Unzoned Name Server requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267.2.4 Mandatory Zone Server requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267.2.5 Mandatory HB

26、A Management Server attributes and requests . . . . . . . . . . . . . . 277.3 Switch operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 Requirements for storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

27、. . . . . . . . . . . . . . . . . 378.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378.2 Generic Services Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378.3 T

28、arget FCP_Port state machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388.3.1 overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388.3.2 Initialization state machine . . . . . . . . . .

29、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40ii8.3.3 PLOGI/PRLI state machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438.3.4 RSCN state machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

30、438.3.5 Target internal change state machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 Requirements for an FCP_Port with initiator and target functions . . . . . . . . . . . . . . . . . 459.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31、 . . . . . . . . . . . . . . . . . . . . . . . . 459.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Annex A (Normative) Retry Rules - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

32、- -46A.1 Summary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -46A.2 Initiator FCP_Ports or target FCP_Ports - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -46A.2.1 LS_RJT or Reject CT_IU - - - - - - - - - - -

33、- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -46A.2.2 Timeout - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -46A.2.3 Reject reason code handling - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -46A.2

34、.3.1 Summary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -46A.2.3.2 LS_RJT retryable Reason Codes - - - - - - - - - - - - - - - - - - - - - - - - - - - - -47A.2.3.3 Reject CT_IU retryable Reason Codes - - - - - - - - - - - - - - - - - - - - - - - - - -47

35、A.2.3.4 Directory Service specific Reject CT_IU retryable Reason Codes - - - - - - -48iiiTable PageTable 1 Numbering Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Table 2 Name Server attributes provided to host by HBA. . . . . . . . . .

36、. . . . . . . . . . . . . . . . . . .11Table 3 Fabric Configuration Server attributes provided to host by HBA . . . . . . . . . . . . . . . . .11Table 4 HBA Management Server HBA attributes provided per port to host by HBA . . . . . . . .12Table 5 HBA Management Server HBA attributes provided to hos

37、t by HBA. . . . . . . . . . . . . . .12Table 6 Name Server attributes registered by host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Table 7 Fabric Configuration Server attributes registered by host . . . . . . . . . . . . . . . . . . . . . .13Table 8 HBA Management Server HB

38、A per-port attributes registered by host . . . . . . . . . . . . .14Table 9 HBA Management Server HBA attributes registered by host. . . . . . . . . . . . . . . . . . . .14Table 10 Name Server requests supported by switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Table 11 Fab

39、ric Configuration Server attributes supported by switch. . . . . . . . . . . . . . . . . . . . .24Table 12 Fabric Configuration Server requests supported by switch . . . . . . . . . . . . . . . . . . . . .25Table 13 Zone Server Attributes supported by switch. . . . . . . . . . . . . . . . . . . . .

40、. . . . . . . . . . . .26Table 14 Zone Server requests supported by switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Table 15 HBA Management Server HBA attributes supported by switch . . . . . . . . . . . . . . . . . .27Table 16 HBA Management Server requests supported by sw

41、itch. . . . . . . . . . . . . . . . . . . . . . .27Table 17 Name Server attributes registered by storage device . . . . . . . . . . . . . . . . . . . . . . . . .37Table 18 Fabric Configuration Server attributes registered by storage device . . . . . . . . . . . . . .38Table 19 Retryable LS_RJT Reaso

42、n Codes/Reason Code Explanations. . . . . . . . . . . . . . . . . .47Table 20 Retryable Reject CT_IU Reason Codes/Reason Code Explanations . . . . . . . . . . . . .47Table 21 Directory Service retryable Reject codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48ivFigure Page

43、1 Sample State Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Interoperability Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 Initiator FCP_Port state machine . . . . . . . . . .

44、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164 Switch state machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295 Target FCP_Port state machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39vFo

45、reword (This foreword is not part of Technical Report INCITS TR-47-2012.)The Fibre Channel Simplified Configuration and Management (FC-SCM) technicalreport describes the Fibre Channel requirements for an easy-to-use limited SAN con-figuration.This technical report was developed by Task Group T11 of

46、Accredited StandardsCommittee INCITS during 2007-2011. The technical report approval process startedin 2010. This document includes one annex that is informative and is not consideredpart of the technical report.Requests for interpretation, suggestions for improvements or addenda, or defect re-ports

47、 are welcome. They should be sent to the INCITS Secretariat, Information Tech-nology Industry Council, 1101 K Street NW Suite 610, Washington, DC 20005-3922.This technical report was processed and approved for submittal to ANSI by the Inter-national Committee for Information Technology Standards (IN

48、CITS). Committee ap-proval of the technical report does not necessarily imply that all committee membersvoted for approval. At the time it approved this technical report, INCITS had the fol-lowing members:Don Wright, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe

49、 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 Corporation . Gary RobinsonStephen Diamond (Alt.)Farance, Inc. Frank FaranceTimothy Schoechle (Alt.)GS1 US . Frank SharkeyCharles Biss (Alt.)Hewlett-Packard Company Karen Higginbott